Generated: 2025.04.08 09:04:48 +0000

• -python-pysmi-lextudio (1.0.4-5 to -)
  • Migration status for -python-pysmi-lextudio (1.0.4-5 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Package not in unstable, will try to remove
• -rust-core-foundation (0.9.1-2 to -)
  • Migration status for -rust-core-foundation (0.9.1-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Package not in unstable, will try to remove
• 3dchess/arm64 (0.8.1-22 to 0.8.1-22)
  • Migration status for 3dchess/arm64 (0.8.1-22 to 0.8.1-22): Will attempt migration (Any information below is purely informational)
• acct/arm64 (6.6.4-5 to 6.6.4-5)
  • Migration status for acct/arm64 (6.6.4-5 to 6.6.4-5): Will attempt migration (Any information below is purely informational)
• acct/riscv64 (6.6.4-5 to 6.6.4-5)
  • Migration status for acct/riscv64 (6.6.4-5 to 6.6.4-5): Will attempt migration (Any information below is purely informational)
• actor-framework/armhf (0.17.6-3.1 to 0.17.6-3.1)
  • Migration status for actor-framework/armhf (0.17.6-3.1 to 0.17.6-3.1): Will attempt migration (Any information below is purely informational)
• algobox/arm64 (1.1.1+dfsg-1 to 1.1.1+dfsg-1)
  • Migration status for algobox/arm64 (1.1.1+dfsg-1 to 1.1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ams/arm64 (2.2.1-1 to 2.2.1-1)
  • Migration status for ams/arm64 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
• analog/arm64 (2:6.0.17-3 to 2:6.0.17-3)
  • Migration status for analog/arm64 (2:6.0.17-3 to 2:6.0.17-3): Will attempt migration (Any information below is purely informational)
• and/arm64 (1.2.2-4.3 to 1.2.2-4.3)
  • Migration status for and/arm64 (1.2.2-4.3 to 1.2.2-4.3): Will attempt migration (Any information below is purely informational)
• antiword/riscv64 (0.37-16 to 0.37-16)
  • Migration status for antiword/riscv64 (0.37-16 to 0.37-16): Will attempt migration (Any information below is purely informational)
• aoetools/arm64 (36-6 to 36-6)
  • Migration status for aoetools/arm64 (36-6 to 36-6): Will attempt migration (Any information below is purely informational)
• ascdc/riscv64 (0.3-15.1 to 0.3-15.1)
  • Migration status for ascdc/riscv64 (0.3-15.1 to 0.3-15.1): Will attempt migration (Any information below is purely informational)
• ataqv/riscv64 (1.3.1+ds-2 to 1.3.1+ds-2)
  • Migration status for ataqv/riscv64 (1.3.1+ds-2 to 1.3.1+ds-2): Will attempt migration (Any information below is purely informational)
• atop_pu (2.11.1-1 to 2.8.1-1+deb12u1)
  • Migration status for atop_pu (2.11.1-1 to 2.8.1-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: atop is newer in the target suite (2.11.1-1 2.8.1-1+deb12u1)
• audmes/riscv64 (2024.02.18-1 to 2024.02.18-1)
  • Migration status for audmes/riscv64 (2024.02.18-1 to 2024.02.18-1): Will attempt migration (Any information below is purely informational)
• avra/riscv64 (1.4.2+dfsg-1 to 1.4.2+dfsg-1)
  • Migration status for avra/riscv64 (1.4.2+dfsg-1 to 1.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• baycomusb/riscv64 (0.10-15 to 0.10-15)
  • Migration status for baycomusb/riscv64 (0.10-15 to 0.10-15): Will attempt migration (Any information below is purely informational)
• bb/riscv64 (1.3rc1-13 to 1.3rc1-13)
  • Migration status for bb/riscv64 (1.3rc1-13 to 1.3rc1-13): Will attempt migration (Any information below is purely informational)
• bcalm/riscv64 (2.2.3-5 to 2.2.3-5)
  • Migration status for bcalm/riscv64 (2.2.3-5 to 2.2.3-5): Will attempt migration (Any information below is purely informational)
• bibtool/riscv64 (2.68+ds-1 to 2.68+ds-1)
  • Migration status for bibtool/riscv64 (2.68+ds-1 to 2.68+ds-1): Will attempt migration (Any information below is purely informational)
• bitseq/riscv64 (0.7.5+dfsg-6 to 0.7.5+dfsg-6)
  • Migration status for bitseq/riscv64 (0.7.5+dfsg-6 to 0.7.5+dfsg-6): Will attempt migration (Any information below is purely informational)
• blkreplay/riscv64 (1.0-3.1 to 1.0-3.1)
  • Migration status for blkreplay/riscv64 (1.0-3.1 to 1.0-3.1): Will attempt migration (Any information below is purely informational)
• blockout2/riscv64 (2.5+dfsg1-1 to 2.5+dfsg1-1)
  • Migration status for blockout2/riscv64 (2.5+dfsg1-1 to 2.5+dfsg1-1): Will attempt migration (Any information below is purely informational)
• bowtie/arm64 (1.3.1-3 to 1.3.1-3)
  • Migration status for bowtie/arm64 (1.3.1-3 to 1.3.1-3): Will attempt migration (Any information below is purely informational)
• braa/riscv64 (0.82-7 to 0.82-7)
  • Migration status for braa/riscv64 (0.82-7 to 0.82-7): Will attempt migration (Any information below is purely informational)
• bsd-mailx/riscv64 (8.1.2-0.20220412cvs-1 to 8.1.2-0.20220412cvs-1)
  • Migration status for bsd-mailx/riscv64 (8.1.2-0.20220412cvs-1 to 8.1.2-0.20220412cvs-1): Will attempt migration (Any information below is purely informational)
• bti/riscv64 (034-6 to 034-6)
  • Migration status for bti/riscv64 (034-6 to 034-6): Will attempt migration (Any information below is purely informational)
• bumprace/arm64 (1.5.8-1 to 1.5.8-1)
  • Migration status for bumprace/arm64 (1.5.8-1 to 1.5.8-1): Will attempt migration (Any information below is purely informational)
• bwbar/riscv64 (1.2.3-7 to 1.2.3-7)
  • Migration status for bwbar/riscv64 (1.2.3-7 to 1.2.3-7): Will attempt migration (Any information below is purely informational)
• caps2esc/arm64 (0.3.2-1 to 0.3.2-1)
  • Migration status for caps2esc/arm64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• caps2esc/riscv64 (0.3.2-1 to 0.3.2-1)
  • Migration status for caps2esc/riscv64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• cdebootstrap/amd64 (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/amd64 (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/amd64 cdebconf (not considered)
    • Invalidated by built-using
• cdebootstrap/arm64 (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/arm64 (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/arm64 cdebconf (not considered)
    • Invalidated by built-using
• cdebootstrap/armel (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/armel (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/armel cdebconf (not considered)
    • Invalidated by built-using
• cdebootstrap/armhf (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/armhf (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/armhf cdebconf (not considered)
    • Invalidated by built-using
• cdebootstrap/i386 (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/i386 (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/i386 cdebconf (not considered)
    • Invalidated by built-using
• cdebootstrap/mips64el (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/mips64el (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/mips64el cdebconf (not considered)
    • Invalidated by built-using
• cdebootstrap/ppc64el (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/ppc64el (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/ppc64el cdebconf (not considered)
    • Invalidated by built-using
• cdebootstrap/riscv64 (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/riscv64 (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/riscv64 cdebconf (not considered)
    • Invalidated by built-using
• cdebootstrap/s390x (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/s390x (0.7.8 to 0.7.8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: cdebootstrap/s390x cdebconf (not considered)
    • Invalidated by built-using
• chemtool/riscv64 (1.6.14-6 to 1.6.14-6)
  • Migration status for chemtool/riscv64 (1.6.14-6 to 1.6.14-6): Will attempt migration (Any information below is purely informational)
• chip-seq/riscv64 (1.5.5-3 to 1.5.5-3)
  • Migration status for chip-seq/riscv64 (1.5.5-3 to 1.5.5-3): Will attempt migration (Any information below is purely informational)
• chromium_pu (135.0.7049.52-1 to 135.0.7049.52-1~deb12u1)
  • Migration status for chromium_pu (135.0.7049.52-1 to 135.0.7049.52-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: chromium is newer in the target suite (135.0.7049.52-1 135.0.7049.52-1~deb12u1)
• cjk/riscv64 (4.8.5-1 to 4.8.5-1)
  • Migration status for cjk/riscv64 (4.8.5-1 to 4.8.5-1): Will attempt migration (Any information below is purely informational)
• clustalw/riscv64 (2.1+lgpl-7 to 2.1+lgpl-7)
  • Migration status for clustalw/riscv64 (2.1+lgpl-7 to 2.1+lgpl-7): Will attempt migration (Any information below is purely informational)
• cppzmq/armel (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/armel (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cscope/arm64 (15.9-2 to 15.9-2)
  • Migration status for cscope/arm64 (15.9-2 to 15.9-2): Will attempt migration (Any information below is purely informational)
• ctwm/armhf (4.1.0-1 to 4.1.0-1)
  • Migration status for ctwm/armhf (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• cwdaemon/armhf (0.10.2-3 to 0.10.2-3)
  • Migration status for cwdaemon/armhf (0.10.2-3 to 0.10.2-3): Will attempt migration (Any information below is purely informational)
• dd2/arm64 (0.2.2-4 to 0.2.2-4)
  • Migration status for dd2/arm64 (0.2.2-4 to 0.2.2-4): Will attempt migration (Any information below is purely informational)
• deepin-screen-recorder/arm64 (5.8.0.46-3 to 5.8.0.46-3)
  • Migration status for deepin-screen-recorder/arm64 (5.8.0.46-3 to 5.8.0.46-3): Will attempt migration (Any information below is purely informational)
• devtodo/arm64 (0.1.20+git20200830.0ad52b0-3 to 0.1.20+git20200830.0ad52b0-3)
  • Migration status for devtodo/arm64 (0.1.20+git20200830.0ad52b0-3 to 0.1.20+git20200830.0ad52b0-3): Will attempt migration (Any information below is purely informational)
• dma/armhf (0.13-1 to 0.13-1)
  • Migration status for dma/armhf (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
• dnssec-trigger/arm64 (0.17+repack-5.3 to 0.17+repack-5.3)
  • Migration status for dnssec-trigger/arm64 (0.17+repack-5.3 to 0.17+repack-5.3): Will attempt migration (Any information below is purely informational)
• dosbox/arm64 (0.74-3-5 to 0.74-3-5)
  • Migration status for dosbox/arm64 (0.74-3-5 to 0.74-3-5): Will attempt migration (Any information below is purely informational)
• dvd+rw-tools/arm64 (7.1-14 to 7.1-14)
  • Migration status for dvd+rw-tools/arm64 (7.1-14 to 7.1-14): Will attempt migration (Any information below is purely informational)
• dynamite/arm64 (0.1.1-2 to 0.1.1-2)
  • Migration status for dynamite/arm64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• e-mem/arm64 (1.0.1-5 to 1.0.1-5)
  • Migration status for e-mem/arm64 (1.0.1-5 to 1.0.1-5): Will attempt migration (Any information below is purely informational)
• eos-sdk/armel (0~git20230107+ds-5.1 to 0~git20230107+ds-5.1)
  • Migration status for eos-sdk/armel (0~git20230107+ds-5.1 to 0~git20230107+ds-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libendless-bin/armel has unsatisfiable dependency
• epic4/armhf (1:2.10.10-1.2 to 1:2.10.10-1.2)
  • Migration status for epic4/armhf (1:2.10.10-1.2 to 1:2.10.10-1.2): Will attempt migration (Any information below is purely informational)
• exim4_pu (4.98.2-1 to 4.96-15+deb12u7)
  • Migration status for exim4_pu (4.98.2-1 to 4.96-15+deb12u7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: exim4 is newer in the target suite (4.98.2-1 4.96-15+deb12u7)
• fabulous/arm64 (0.4.0+dfsg1-1 to 0.4.0+dfsg1-1)
  • Migration status for fabulous/arm64 (0.4.0+dfsg1-1 to 0.4.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
• fetchmail/arm64 (6.4.39-1 to 6.4.39-1)
  • Migration status for fetchmail/arm64 (6.4.39-1 to 6.4.39-1): Will attempt migration (Any information below is purely informational)
• firefox-esr_pu (128.9.0esr-2 to 128.9.0esr-1~deb12u1)
  • Migration status for firefox-esr_pu (128.9.0esr-2 to 128.9.0esr-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: firefox-esr is newer in the target suite (128.9.0esr-2 128.9.0esr-1~deb12u1)
• flpsed/armhf (0.7.3-9 to 0.7.3-9)
  • Migration status for flpsed/armhf (0.7.3-9 to 0.7.3-9): Will attempt migration (Any information below is purely informational)
• fractalnow/arm64 (0.8.2-5 to 0.8.2-5)
  • Migration status for fractalnow/arm64 (0.8.2-5 to 0.8.2-5): Will attempt migration (Any information below is purely informational)
• freetype_pu (2.13.3+dfsg-1 to 2.12.1+dfsg-5+deb12u4)
  • Migration status for freetype_pu (2.13.3+dfsg-1 to 2.12.1+dfsg-5+deb12u4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: freetype is newer in the target suite (2.13.3+dfsg-1 2.12.1+dfsg-5+deb12u4)
• fsa/arm64 (1.15.9+dfsg-6 to 1.15.9+dfsg-6)
  • Migration status for fsa/arm64 (1.15.9+dfsg-6 to 1.15.9+dfsg-6): Will attempt migration (Any information below is purely informational)
• gargoyle-free/arm64 (2023.1+dfsg-4 to 2023.1+dfsg-4)
  • Migration status for gargoyle-free/arm64 (2023.1+dfsg-4 to 2023.1+dfsg-4): Will attempt migration (Any information below is purely informational)
• gbonds/arm64 (2.0.3-17 to 2.0.3-17)
  • Migration status for gbonds/arm64 (2.0.3-17 to 2.0.3-17): Will attempt migration (Any information below is purely informational)
• generator-scripting-language/arm64 (4.1.5-4 to 4.1.5-4)
  • Migration status for generator-scripting-language/arm64 (4.1.5-4 to 4.1.5-4): Will attempt migration (Any information below is purely informational)
• gentoo/armhf (0.20.7-3 to 0.20.7-3)
  • Migration status for gentoo/armhf (0.20.7-3 to 0.20.7-3): Will attempt migration (Any information below is purely informational)
• ghostscript_pu (10.05.0~dfsg-1 to 10.0.0~dfsg-11+deb12u7)
  • Migration status for ghostscript_pu (10.05.0~dfsg-1 to 10.0.0~dfsg-11+deb12u7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ghostscript is newer in the target suite (10.05.0~dfsg-1 10.0.0~dfsg-11+deb12u7)
• gss_pu (1.0.4-4 to 1.0.4-1+deb12u1)
  • Migration status for gss_pu (1.0.4-4 to 1.0.4-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: gss is newer in the target suite (1.0.4-4 1.0.4-1+deb12u1)
• hinge/armhf (0.5.0-7 to 0.5.0-7)
  • Migration status for hinge/armhf (0.5.0-7 to 0.5.0-7): Will attempt migration (Any information below is purely informational)
• hnb/arm64 (1.9.18+ds1-3 to 1.9.18+ds1-3)
  • Migration status for hnb/arm64 (1.9.18+ds1-3 to 1.9.18+ds1-3): Will attempt migration (Any information below is purely informational)
• hp48cc/arm64 (1.3-7 to 1.3-7)
  • Migration status for hp48cc/arm64 (1.3-7 to 1.3-7): Will attempt migration (Any information below is purely informational)
• hpanel/arm64 (0.3.2-8 to 0.3.2-8)
  • Migration status for hpanel/arm64 (0.3.2-8 to 0.3.2-8): Will attempt migration (Any information below is purely informational)
• iannix/arm64 (0.9.20~dfsg1-1 to 0.9.20~dfsg1-1)
  • Migration status for iannix/arm64 (0.9.20~dfsg1-1 to 0.9.20~dfsg1-1): Will attempt migration (Any information below is purely informational)
• igtf-policy-bundle_pu (1.134-1 to 1.133-1~deb12u1)
  • Migration status for igtf-policy-bundle_pu (1.134-1 to 1.133-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: igtf-policy-bundle is newer in the target suite (1.134-1 1.133-1~deb12u1)
• ike-scan/arm64 (1.9.5-2 to 1.9.5-2)
  • Migration status for ike-scan/arm64 (1.9.5-2 to 1.9.5-2): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• jetty9_pu (9.4.57-1 to 9.4.57-0+deb12u1)
  • Migration status for jetty9_pu (9.4.57-1 to 9.4.57-0+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: jetty9 is newer in the target suite (9.4.57-1 9.4.57-0+deb12u1)
• kdesvn/arm64 (2.1.0-3 to 2.1.0-3)
  • Migration status for kdesvn/arm64 (2.1.0-3 to 2.1.0-3): Will attempt migration (Any information below is purely informational)
• keurocalc/arm64 (1.3.0-4 to 1.3.0-4)
  • Migration status for keurocalc/arm64 (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• kexec-tools_pu (1:2.0.29-2 to 1:2.0.25-3+deb12u2)
  • Migration status for kexec-tools_pu (1:2.0.29-2 to 1:2.0.25-3+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: kexec-tools is newer in the target suite (1:2.0.29-2 1:2.0.25-3+deb12u2)
• kst/arm64 (2.0.8-6 to 2.0.8-6)
  • Migration status for kst/arm64 (2.0.8-6 to 2.0.8-6): Will attempt migration (Any information below is purely informational)
• lagan/arm64 (2.0-10 to 2.0-10)
  • Migration status for lagan/arm64 (2.0-10 to 2.0-10): Will attempt migration (Any information below is purely informational)
• libai-fann-perl/arm64 (0.10-5 to 0.10-5)
  • Migration status for libai-fann-perl/arm64 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• libalgorithm-svm-perl/arm64 (0.13-4 to 0.13-4)
  • Migration status for libalgorithm-svm-perl/arm64 (0.13-4 to 0.13-4): Will attempt migration (Any information below is purely informational)
• libalgorithm-svm-perl/armhf (0.13-4 to 0.13-4)
  • Migration status for libalgorithm-svm-perl/armhf (0.13-4 to 0.13-4): Will attempt migration (Any information below is purely informational)
• libanyevent-perl/armhf (7.170-2 to 7.170-2)
  • Migration status for libanyevent-perl/armhf (7.170-2 to 7.170-2): Will attempt migration (Any information below is purely informational)
• libaudio-cd-perl/arm64 (0.05-13 to 0.05-13)
  • Migration status for libaudio-cd-perl/arm64 (0.05-13 to 0.05-13): Will attempt migration (Any information below is purely informational)
• libaudio-cd-perl/armhf (0.05-13 to 0.05-13)
  • Migration status for libaudio-cd-perl/armhf (0.05-13 to 0.05-13): Will attempt migration (Any information below is purely informational)
• libauthen-sasl-xs-perl/arm64 (1.00-3 to 1.00-3)
  • Migration status for libauthen-sasl-xs-perl/arm64 (1.00-3 to 1.00-3): Will attempt migration (Any information below is purely informational)
• libbio-scf-perl/arm64 (1.03-7 to 1.03-7)
  • Migration status for libbio-scf-perl/arm64 (1.03-7 to 1.03-7): Will attempt migration (Any information below is purely informational)
• libcgi-struct-xs-perl/armhf (1.04-3 to 1.04-3)
  • Migration status for libcgi-struct-xs-perl/armhf (1.04-3 to 1.04-3): Will attempt migration (Any information below is purely informational)
• libconvert-scalar-perl/armhf (1.12-2 to 1.12-2)
  • Migration status for libconvert-scalar-perl/armhf (1.12-2 to 1.12-2): Will attempt migration (Any information below is purely informational)
• libconvert-uulib-perl/arm64 (1:1.8+dfsg-1 to 1:1.8+dfsg-1)
  • Migration status for libconvert-uulib-perl/arm64 (1:1.8+dfsg-1 to 1:1.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• libdate-pcalc-perl/arm64 (6.1-7 to 6.1-7)
  • Migration status for libdate-pcalc-perl/arm64 (6.1-7 to 6.1-7): Will attempt migration (Any information below is purely informational)
• libdate-pcalc-perl/armhf (6.1-7 to 6.1-7)
  • Migration status for libdate-pcalc-perl/armhf (6.1-7 to 6.1-7): Will attempt migration (Any information below is purely informational)
• libdevice-serialport-perl/armhf (1.04-4 to 1.04-4)
  • Migration status for libdevice-serialport-perl/armhf (1.04-4 to 1.04-4): Will attempt migration (Any information below is purely informational)
• libdevice-usb-perl/arm64 (0.38-3 to 0.38-3)
  • Migration status for libdevice-usb-perl/arm64 (0.38-3 to 0.38-3): Will attempt migration (Any information below is purely informational)
• libdigest-md4-perl/armhf (1.9+dfsg-3 to 1.9+dfsg-3)
  • Migration status for libdigest-md4-perl/armhf (1.9+dfsg-3 to 1.9+dfsg-3): Will attempt migration (Any information below is purely informational)
• libfile-extattr-perl/armhf (1.09-6 to 1.09-6)
  • Migration status for libfile-extattr-perl/armhf (1.09-6 to 1.09-6): Will attempt migration (Any information below is purely informational)
• libfilesys-smbclient-perl/arm64 (3.2-4 to 3.2-4)
  • Migration status for libfilesys-smbclient-perl/arm64 (3.2-4 to 3.2-4): Will attempt migration (Any information below is purely informational)
• libfilesys-smbclient-perl/armhf (3.2-4 to 3.2-4)
  • Migration status for libfilesys-smbclient-perl/armhf (3.2-4 to 3.2-4): Will attempt migration (Any information below is purely informational)
• libfuse-perl/arm64 (0.16.1+20180422git6becd92d7fce3fc411d7c-6 to 0.16.1+20180422git6becd92d7fce3fc411d7c-6)
  • Migration status for libfuse-perl/arm64 (0.16.1+20180422git6becd92d7fce3fc411d7c-6 to 0.16.1+20180422git6becd92d7fce3fc411d7c-6): Will attempt migration (Any information below is purely informational)
• libfuse-perl/armhf (0.16.1+20180422git6becd92d7fce3fc411d7c-6 to 0.16.1+20180422git6becd92d7fce3fc411d7c-6)
  • Migration status for libfuse-perl/armhf (0.16.1+20180422git6becd92d7fce3fc411d7c-6 to 0.16.1+20180422git6becd92d7fce3fc411d7c-6): Will attempt migration (Any information below is purely informational)
• libgdf/amd64 (0.1.3-11.1 to 0.1.3-11.1)
  • Migration status for libgdf/amd64 (0.1.3-11.1 to 0.1.3-11.1): Will attempt migration (Any information below is purely informational)
• libgdf/armhf (0.1.3-11.1 to 0.1.3-11.1)
  • Migration status for libgdf/armhf (0.1.3-11.1 to 0.1.3-11.1): Will attempt migration (Any information below is purely informational)
• libgraphics-libplot-perl/arm64 (2.2.4-1 to 2.2.4-1)
  • Migration status for libgraphics-libplot-perl/arm64 (2.2.4-1 to 2.2.4-1): Will attempt migration (Any information below is purely informational)
• libgssapi-perl/arm64 (0.28-4 to 0.28-4)
  • Migration status for libgssapi-perl/arm64 (0.28-4 to 0.28-4): Will attempt migration (Any information below is purely informational)
• libheimdal-kadm5-perl/armhf (0.08-6 to 0.08-6)
  • Migration status for libheimdal-kadm5-perl/armhf (0.08-6 to 0.08-6): Will attempt migration (Any information below is purely informational)
• libhtml-tidy-perl/armhf (1.60-5 to 1.60-5)
  • Migration status for libhtml-tidy-perl/armhf (1.60-5 to 1.60-5): Will attempt migration (Any information below is purely informational)
• libimager-qrcode-perl/arm64 (0.033-1.2 to 0.033-1.2)
  • Migration status for libimager-qrcode-perl/arm64 (0.033-1.2 to 0.033-1.2): Will attempt migration (Any information below is purely informational)
• libio-aio-perl/armhf (4.81-1 to 4.81-1)
  • Migration status for libio-aio-perl/armhf (4.81-1 to 4.81-1): Will attempt migration (Any information below is purely informational)
• libio-epoll-perl/armhf (0.03-3 to 0.03-3)
  • Migration status for libio-epoll-perl/armhf (0.03-3 to 0.03-3): Will attempt migration (Any information below is purely informational)
• liblinux-inotify2-perl/arm64 (1:2.3-2 to 1:2.3-2)
  • Migration status for liblinux-inotify2-perl/arm64 (1:2.3-2 to 1:2.3-2): Will attempt migration (Any information below is purely informational)
• liblinux-inotify2-perl/armhf (1:2.3-2 to 1:2.3-2)
  • Migration status for liblinux-inotify2-perl/armhf (1:2.3-2 to 1:2.3-2): Will attempt migration (Any information below is purely informational)
• libmath-int128-perl/arm64 (0.22-5 to 0.22-5)
  • Migration status for libmath-int128-perl/arm64 (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• libmidi-alsa-perl/arm64 (1.22-2 to 1.22-2)
  • Migration status for libmidi-alsa-perl/arm64 (1.22-2 to 1.22-2): Will attempt migration (Any information below is purely informational)
• libmusicbrainz-discid-perl/armhf (0.06-1 to 0.06-1)
  • Migration status for libmusicbrainz-discid-perl/armhf (0.06-1 to 0.06-1): Will attempt migration (Any information below is purely informational)
• libnet-freedb-perl/arm64 (0.10-5 to 0.10-5)
  • Migration status for libnet-freedb-perl/arm64 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• libnet-z3950-zoom-perl/armhf (1.32-2 to 1.32-2)
  • Migration status for libnet-z3950-zoom-perl/armhf (1.32-2 to 1.32-2): Will attempt migration (Any information below is purely informational)
• libnetaddr-ip-perl/arm64 (4.079+dfsg-2 to 4.079+dfsg-2)
  • Migration status for libnetaddr-ip-perl/arm64 (4.079+dfsg-2 to 4.079+dfsg-2): Will attempt migration (Any information below is purely informational)
• libnetaddr-ip-perl/armhf (4.079+dfsg-2 to 4.079+dfsg-2)
  • Migration status for libnetaddr-ip-perl/armhf (4.079+dfsg-2 to 4.079+dfsg-2): Will attempt migration (Any information below is purely informational)
• liboverload-filecheck-perl/arm64 (0.013-2 to 0.013-2)
  • Migration status for liboverload-filecheck-perl/arm64 (0.013-2 to 0.013-2): Will attempt migration (Any information below is purely informational)
• liboverload-filecheck-perl/armhf (0.013-2 to 0.013-2)
  • Migration status for liboverload-filecheck-perl/armhf (0.013-2 to 0.013-2): Will attempt migration (Any information below is purely informational)
• libpam-abl/arm64 (0.6.0-7 to 0.6.0-7)
  • Migration status for libpam-abl/arm64 (0.6.0-7 to 0.6.0-7): Will attempt migration (Any information below is purely informational)
• libperl-destruct-level-perl/arm64 (0.02-3 to 0.02-3)
  • Migration status for libperl-destruct-level-perl/arm64 (0.02-3 to 0.02-3): Will attempt migration (Any information below is purely informational)
• libpoe-filter-ssl-perl/arm64 (0.41-3 to 0.41-3)
  • Migration status for libpoe-filter-ssl-perl/arm64 (0.41-3 to 0.41-3): Will attempt migration (Any information below is purely informational)
• libpoe-filter-ssl-perl/armhf (0.41-3 to 0.41-3)
  • Migration status for libpoe-filter-ssl-perl/armhf (0.41-3 to 0.41-3): Will attempt migration (Any information below is purely informational)
• libpromise-xs-perl/armhf (0.20-1 to 0.20-1)
  • Migration status for libpromise-xs-perl/armhf (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
• libsdl-sge/armel (030809dfsg-11 to 030809dfsg-11)
  • Migration status for libsdl-sge/armel (030809dfsg-11 to 030809dfsg-11): Will attempt migration (Any information below is purely informational)
• libsereal-decoder-perl/armhf (5.004+ds-1 to 5.004+ds-1)
  • Migration status for libsereal-decoder-perl/armhf (5.004+ds-1 to 5.004+ds-1): Will attempt migration (Any information below is purely informational)
• libsgml-parser-opensp-perl/armhf (0.994-7 to 0.994-7)
  • Migration status for libsgml-parser-opensp-perl/armhf (0.994-7 to 0.994-7): Will attempt migration (Any information below is purely informational)
• libsocket6-perl/armhf (0.29-3 to 0.29-3)
  • Migration status for libsocket6-perl/armhf (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• libsort-key-perl/arm64 (1.33-3 to 1.33-3)
  • Migration status for libsort-key-perl/arm64 (1.33-3 to 1.33-3): Will attempt migration (Any information below is purely informational)
• libsort-key-perl/armhf (1.33-3 to 1.33-3)
  • Migration status for libsort-key-perl/armhf (1.33-3 to 1.33-3): Will attempt migration (Any information below is purely informational)
• libstring-similarity-perl/arm64 (1.04-3 to 1.04-3)
  • Migration status for libstring-similarity-perl/arm64 (1.04-3 to 1.04-3): Will attempt migration (Any information below is purely informational)
• libterm-slang-perl/arm64 (0.07-15 to 0.07-15)
  • Migration status for libterm-slang-perl/arm64 (0.07-15 to 0.07-15): Will attempt migration (Any information below is purely informational)
• libtext-reflow-perl/armhf (1.17-2 to 1.17-2)
  • Migration status for libtext-reflow-perl/armhf (1.17-2 to 1.17-2): Will attempt migration (Any information below is purely informational)
• libtfbs-perl/arm64 (0.7.1+ds-4 to 0.7.1+ds-4)
  • Migration status for libtfbs-perl/arm64 (0.7.1+ds-4 to 0.7.1+ds-4): Will attempt migration (Any information below is purely informational)
• libtfbs-perl/armhf (0.7.1+ds-4 to 0.7.1+ds-4)
  • Migration status for libtfbs-perl/armhf (0.7.1+ds-4 to 0.7.1+ds-4): Will attempt migration (Any information below is purely informational)
• libunicode-linebreak-perl/armhf (0.0.20190101-1 to 0.0.20190101-1)
  • Migration status for libunicode-linebreak-perl/armhf (0.0.20190101-1 to 0.0.20190101-1): Will attempt migration (Any information below is purely informational)
• libunicode-map-perl/armhf (0.112-13 to 0.112-13)
  • Migration status for libunicode-map-perl/armhf (0.112-13 to 0.112-13): Will attempt migration (Any information below is purely informational)
• libvideo-capture-v4l-perl/arm64 (0.902-5 to 0.902-5)
  • Migration status for libvideo-capture-v4l-perl/arm64 (0.902-5 to 0.902-5): Will attempt migration (Any information below is purely informational)
• libvideo-ivtv-perl/armhf (0.13-10 to 0.13-10)
  • Migration status for libvideo-ivtv-perl/armhf (0.13-10 to 0.13-10): Will attempt migration (Any information below is purely informational)
• libxinerama/arm64 (2:1.1.4-3 to 2:1.1.4-3)
  • Migration status for libxinerama/arm64 (2:1.1.4-3 to 2:1.1.4-3): Will attempt migration (Any information below is purely informational)
• libxml-libxml-perl/armhf (2.0207+dfsg+really+2.0134-5 to 2.0207+dfsg+really+2.0134-5)
  • Migration status for libxml-libxml-perl/armhf (2.0207+dfsg+really+2.0134-5 to 2.0207+dfsg+really+2.0134-5): Will attempt migration (Any information below is purely informational)
• libxslt_pu (1.1.35-1.2 to 1.1.35-1+deb12u1)
  • Migration status for libxslt_pu (1.1.35-1.2 to 1.1.35-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libxslt is newer in the target suite (1.1.35-1.2 1.1.35-1+deb12u1)
• lincity/arm64 (1.13.1-16 to 1.13.1-16)
  • Migration status for lincity/arm64 (1.13.1-16 to 1.13.1-16): Will attempt migration (Any information below is purely informational)
• logrotate/arm64 (3.22.0-1 to 3.22.0-1)
  • Migration status for logrotate/arm64 (3.22.0-1 to 3.22.0-1): Will attempt migration (Any information below is purely informational)
• luckybackup/arm64 (0.5.0-7 to 0.5.0-7)
  • Migration status for luckybackup/arm64 (0.5.0-7 to 0.5.0-7): Will attempt migration (Any information below is purely informational)
• lumpy-sv/armhf (0.3.1+dfsg-7 to 0.3.1+dfsg-7)
  • Migration status for lumpy-sv/armhf (0.3.1+dfsg-7 to 0.3.1+dfsg-7): Will attempt migration (Any information below is purely informational)
• maliit-keyboard/arm64 (2.3.1-6 to 2.3.1-6)
  • Migration status for maliit-keyboard/arm64 (2.3.1-6 to 2.3.1-6): Will attempt migration (Any information below is purely informational)
• man2html/arm64 (1.6g-16 to 1.6g-16)
  • Migration status for man2html/arm64 (1.6g-16 to 1.6g-16): Will attempt migration (Any information below is purely informational)
• matekbd-keyboard-display/arm64 (23.11.1-1 to 23.11.1-1)
  • Migration status for matekbd-keyboard-display/arm64 (23.11.1-1 to 23.11.1-1): Will attempt migration (Any information below is purely informational)
• matekbd-keyboard-display/armhf (23.11.1-1 to 23.11.1-1)
  • Migration status for matekbd-keyboard-display/armhf (23.11.1-1 to 23.11.1-1): Will attempt migration (Any information below is purely informational)
• mblaze/arm64 (1.1-1 to 1.1-1)
  • Migration status for mblaze/arm64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• mcpl/arm64 (1.3.2-3.1 to 1.3.2-3.1)
  • Migration status for mcpl/arm64 (1.3.2-3.1 to 1.3.2-3.1): Will attempt migration (Any information below is purely informational)
• mdp-src/arm64 (1.0.15-1 to 1.0.15-1)
  • Migration status for mdp-src/arm64 (1.0.15-1 to 1.0.15-1): Will attempt migration (Any information below is purely informational)
• mercurial_pu (6.9.5-1 to 6.3.2-1+deb12u1)
  • Migration status for mercurial_pu (6.9.5-1 to 6.3.2-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: mercurial is newer in the target suite (6.9.5-1 6.3.2-1+deb12u1)
• mesa-demos/mips64el (9.0.0-2 to 9.0.0-2)
  • Migration status for mesa-demos/mips64el (9.0.0-2 to 9.0.0-2): Will attempt migration (Any information below is purely informational)
• mesa-demos/ppc64el (9.0.0-2 to 9.0.0-2)
  • Migration status for mesa-demos/ppc64el (9.0.0-2 to 9.0.0-2): Will attempt migration (Any information below is purely informational)
• mew-beta/arm64 (7.0.50~6.8+0.20221129-4 to 7.0.50~6.8+0.20221129-4)
  • Migration status for mew-beta/arm64 (7.0.50~6.8+0.20221129-4 to 7.0.50~6.8+0.20221129-4): Will attempt migration (Any information below is purely informational)
• milter-greylist/arm64 (4.6.4-3 to 4.6.4-3)
  • Migration status for milter-greylist/arm64 (4.6.4-3 to 4.6.4-3): Will attempt migration (Any information below is purely informational)
• mimedefang/armhf (3.5-1 to 3.5-1)
  • Migration status for mimedefang/armhf (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• minia/arm64 (3.2.6-4 to 3.2.6-4)
  • Migration status for minia/arm64 (3.2.6-4 to 3.2.6-4): Will attempt migration (Any information below is purely informational)
• mpdas/arm64 (0.4.5-1 to 0.4.5-1)
  • Migration status for mpdas/arm64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
• mrtrix3/arm64 (3.0.4-1 to 3.0.4-1)
  • Migration status for mrtrix3/arm64 (3.0.4-1 to 3.0.4-1): Will attempt migration (Any information below is purely informational)
• mystiq/arm64 (20.03.23-3 to 20.03.23-3)
  • Migration status for mystiq/arm64 (20.03.23-3 to 20.03.23-3): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• ncrack/arm64 (0.7+debian-6 to 0.7+debian-6)
  • Migration status for ncrack/arm64 (0.7+debian-6 to 0.7+debian-6): Will attempt migration (Any information below is purely informational)
• nethack/arm64 (3.6.7-1 to 3.6.7-1)
  • Migration status for nethack/arm64 (3.6.7-1 to 3.6.7-1): Will attempt migration (Any information below is purely informational)
• netpanzer/arm64 (0.8.7+ds-5 to 0.8.7+ds-5)
  • Migration status for netpanzer/arm64 (0.8.7+ds-5 to 0.8.7+ds-5): Will attempt migration (Any information below is purely informational)
• netrik/arm64 (1.16.1-4 to 1.16.1-4)
  • Migration status for netrik/arm64 (1.16.1-4 to 1.16.1-4): Will attempt migration (Any information below is purely informational)
• network-manager_pu (1.52.0-6 to 1.42.4-1+deb12u1)
  • Migration status for network-manager_pu (1.52.0-6 to 1.42.4-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: network-manager is newer in the target suite (1.52.0-6 1.42.4-1+deb12u1)
• nss-updatedb/arm64 (10-7 to 10-7)
  • Migration status for nss-updatedb/arm64 (10-7 to 10-7): Will attempt migration (Any information below is purely informational)
• numad/arm64 (0.5+20150602-8 to 0.5+20150602-8)
  • Migration status for numad/arm64 (0.5+20150602-8 to 0.5+20150602-8): Will attempt migration (Any information below is purely informational)
• nuntius-linux/arm64 (0.2.0-5 to 0.2.0-5)
  • Migration status for nuntius-linux/arm64 (0.2.0-5 to 0.2.0-5): Will attempt migration (Any information below is purely informational)
• nuntius-linux/armhf (0.2.0-5 to 0.2.0-5)
  • Migration status for nuntius-linux/armhf (0.2.0-5 to 0.2.0-5): Will attempt migration (Any information below is purely informational)
• obs-vintage-filter/arm64 (1.0.0-2 to 1.0.0-2)
  • Migration status for obs-vintage-filter/arm64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• octave-sockets/arm64 (1.4.1-4 to 1.4.1-4)
  • Migration status for octave-sockets/arm64 (1.4.1-4 to 1.4.1-4): Will attempt migration (Any information below is purely informational)
• openigtlink/arm64 (1.11.0-4 to 1.11.0-4)
  • Migration status for openigtlink/arm64 (1.11.0-4 to 1.11.0-4): Will attempt migration (Any information below is purely informational)
• openmrac/arm64 (1.2-3 to 1.2-3)
  • Migration status for openmrac/arm64 (1.2-3 to 1.2-3): Will attempt migration (Any information below is purely informational)
• openmsx-catapult/armhf (19.0-1 to 19.0-1)
  • Migration status for openmsx-catapult/armhf (19.0-1 to 19.0-1): Will attempt migration (Any information below is purely informational)
• opensaml_pu (3.3.1-1 to 3.2.1-3+deb12u1)
  • Migration status for opensaml_pu (3.3.1-1 to 3.2.1-3+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: opensaml is newer in the target suite (3.3.1-1 3.2.1-3+deb12u1)
• openvpn-systemd-resolved/i386 (1.3.0-4 to 1.3.0-4)
  • Migration status for openvpn-systemd-resolved/i386 (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• openvpn-systemd-resolved/mips64el (1.3.0-4 to 1.3.0-4)
  • Migration status for openvpn-systemd-resolved/mips64el (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• otpw/arm64 (1.5-3 to 1.5-3)
  • Migration status for otpw/arm64 (1.5-3 to 1.5-3): Will attempt migration (Any information below is purely informational)
• passwordmaker-cli/arm64 (1.5+dfsg-6 to 1.5+dfsg-6)
  • Migration status for passwordmaker-cli/arm64 (1.5+dfsg-6 to 1.5+dfsg-6): Will attempt migration (Any information below is purely informational)
• pchar/arm64 (1.5-6 to 1.5-6)
  • Migration status for pchar/arm64 (1.5-6 to 1.5-6): Will attempt migration (Any information below is purely informational)
• pd-moonlib/arm64 (0.7-3 to 0.7-3)
  • Migration status for pd-moonlib/arm64 (0.7-3 to 0.7-3): Will attempt migration (Any information below is purely informational)
• pekwm/armhf (0.1.18-1 to 0.1.18-1)
  • Migration status for pekwm/armhf (0.1.18-1 to 0.1.18-1): Will attempt migration (Any information below is purely informational)
• perceptualdiff/arm64 (2.1-7 to 2.1-7)
  • Migration status for perceptualdiff/arm64 (2.1-7 to 2.1-7): Will attempt migration (Any information below is purely informational)
• perl-byacc/arm64 (2.0-10 to 2.0-10)
  • Migration status for perl-byacc/arm64 (2.0-10 to 2.0-10): Will attempt migration (Any information below is purely informational)
• pgagroal/arm64 (1.6.0-1 to 1.6.0-1)
  • Migration status for pgagroal/arm64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• pgqd/arm64 (3.5-2 to 3.5-2)
  • Migration status for pgqd/arm64 (3.5-2 to 3.5-2): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• php8.2_pu (- to 8.2.28-1~deb12u1)
  • Migration status for php8.2_pu (- to 8.2.28-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php8.2-tidy/amd64 has unsatisfiable dependency
    • php8.2-zip/amd64 has unsatisfiable dependency
    • php8.2-tidy/arm64 has unsatisfiable dependency
    • php8.2-zip/arm64 has unsatisfiable dependency
    • libapache2-mod-php8.2/armel has unsatisfiable dependency
    • libphp8.2-embed/armel has unsatisfiable dependency
    • php8.2-cgi/armel has unsatisfiable dependency
    • php8.2-cli/armel has unsatisfiable dependency
    • php8.2-common/armel has unsatisfiable dependency
    • php8.2-curl/armel has unsatisfiable dependency
    • php8.2-dba/armel has unsatisfiable dependency
    • php8.2-fpm/armel has unsatisfiable dependency
    • php8.2-phpdbg/armel has unsatisfiable dependency
    • php8.2-snmp/armel has unsatisfiable dependency
    • php8.2-tidy/armel has unsatisfiable dependency
    • php8.2-zip/armel has unsatisfiable dependency
    • libapache2-mod-php8.2/armhf has unsatisfiable dependency
    • libphp8.2-embed/armhf has unsatisfiable dependency
    • php8.2-cgi/armhf has unsatisfiable dependency
    • php8.2-cli/armhf has unsatisfiable dependency
    • php8.2-common/armhf has unsatisfiable dependency
    • php8.2-curl/armhf has unsatisfiable dependency
    • php8.2-dba/armhf has unsatisfiable dependency
    • php8.2-fpm/armhf has unsatisfiable dependency
    • php8.2-phpdbg/armhf has unsatisfiable dependency
    • php8.2-snmp/armhf has unsatisfiable dependency
    • php8.2-tidy/armhf has unsatisfiable dependency
    • php8.2-zip/armhf has unsatisfiable dependency
    • php8.2-tidy/i386 has unsatisfiable dependency
    • php8.2-zip/i386 has unsatisfiable dependency
    • php8.2-tidy/mips64el has unsatisfiable dependency
    • php8.2-zip/mips64el has unsatisfiable dependency
    • php8.2-tidy/ppc64el has unsatisfiable dependency
    • php8.2-zip/ppc64el has unsatisfiable dependency
    • php8.2-tidy/s390x has unsatisfiable dependency
    • php8.2-zip/s390x has unsatisfiable dependency
    • php8.2 unsatisfiable Build-Depends(-Arch) on amd64: libc-client-dev
    • php8.2 unsatisfiable Build-Depends(-Arch) on arm64: libc-client-dev
    • php8.2 unsatisfiable Build-Depends(-Arch) on armel: libc-client-dev
    • php8.2 unsatisfiable Build-Depends(-Arch) on armhf: libc-client-dev
    • php8.2 unsatisfiable Build-Depends(-Arch) on i386: libc-client-dev
    • php8.2 unsatisfiable Build-Depends(-Arch) on mips64el: libc-client-dev
    • php8.2 unsatisfiable Build-Depends(-Arch) on ppc64el: libc-client-dev
    • php8.2 unsatisfiable Build-Depends(-Arch) on s390x: libc-client-dev
    • Impossible Depends: php8.2_pu -> libicu72/72.1-6/armel
    • Impossible Depends: php8.2_pu -> libicu72/72.1-6/armhf
    • Impossible Depends: php8.2_pu -> libicu72/72.1-6/i386
    • Impossible Depends: php8.2_pu -> libicu72/72.1-6/mips64el
    • Impossible Depends: php8.2_pu -> libicu72/72.1-6/ppc64el
    • Impossible Depends: php8.2_pu -> libicu72/72.1-6/s390x
    • Impossible Depends: php8.2_pu -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: php8.2_pu -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: php8.2_pu -> libldap-2.5-0/2.5.19+dfsg-1/armel
    • Impossible Depends: php8.2_pu -> libldap-2.5-0/2.5.19+dfsg-1/armhf
    • Impossible Depends: php8.2_pu -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: php8.2_pu -> libldap-2.5-0/2.5.19+dfsg-1/mips64el
    • Impossible Depends: php8.2_pu -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: php8.2_pu -> libldap-2.5-0/2.5.19+dfsg-1/s390x
    • NEEDS APPROVAL BY RM
    • Depends: php8.2_pu uw-imap (not considered)
• pirs/arm64 (2.0.2+dfsg-12 to 2.0.2+dfsg-12)
  • Migration status for pirs/arm64 (2.0.2+dfsg-12 to 2.0.2+dfsg-12): Will attempt migration (Any information below is purely informational)
• pizzly/arm64 (0.37.3+ds-9 to 0.37.3+ds-9)
  • Migration status for pizzly/arm64 (0.37.3+ds-9 to 0.37.3+ds-9): Will attempt migration (Any information below is purely informational)
• plasmidseeker/arm64 (1.3+dfsg-3 to 1.3+dfsg-3)
  • Migration status for plasmidseeker/arm64 (1.3+dfsg-3 to 1.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• plasmidseeker/mips64el (1.3+dfsg-3 to 1.3+dfsg-3)
  • Migration status for plasmidseeker/mips64el (1.3+dfsg-3 to 1.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• plasmidseeker/s390x (1.3+dfsg-3 to 1.3+dfsg-3)
  • Migration status for plasmidseeker/s390x (1.3+dfsg-3 to 1.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• proxsmtp/arm64 (1.10-5 to 1.10-5)
  • Migration status for proxsmtp/arm64 (1.10-5 to 1.10-5): Will attempt migration (Any information below is purely informational)
• psignifit/arm64 (2.5.6-8 to 2.5.6-8)
  • Migration status for psignifit/arm64 (2.5.6-8 to 2.5.6-8): Will attempt migration (Any information below is purely informational)
• python-django_pu (3:4.2.20-1 to 3:3.2.19-1+deb12u2)
  • Migration status for python-django_pu (3:4.2.20-1 to 3:3.2.19-1+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: python-django is newer in the target suite (3:4.2.20-1 3:3.2.19-1+deb12u2)
• qbrew/armhf (0.4.1-8 to 0.4.1-8)
  • Migration status for qbrew/armhf (0.4.1-8 to 0.4.1-8): Will attempt migration (Any information below is purely informational)
• qcomicbook/armhf (0.9.1-3 to 0.9.1-3)
  • Migration status for qcomicbook/armhf (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• qjackrcd/arm64 (1.2.0-2 to 1.2.0-2)
  • Migration status for qjackrcd/arm64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• qjackrcd/armhf (1.2.0-2 to 1.2.0-2)
  • Migration status for qjackrcd/armhf (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• qoauth/armhf (2.0.1~1-3 to 2.0.1~1-3)
  • Migration status for qoauth/armhf (2.0.1~1-3 to 2.0.1~1-3): Will attempt migration (Any information below is purely informational)
• qtbase-opensource-src_pu (5.15.15+dfsg-5 to 5.15.8+dfsg-11+deb12u3)
  • Migration status for qtbase-opensource-src_pu (5.15.15+dfsg-5 to 5.15.8+dfsg-11+deb12u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: qtbase-opensource-src is newer in the target suite (5.15.15+dfsg-5 5.15.8+dfsg-11+deb12u3)
• qtop/armhf (2.3.4-3 to 2.3.4-3)
  • Migration status for qtop/armhf (2.3.4-3 to 2.3.4-3): Will attempt migration (Any information below is purely informational)
• quitcount/arm64 (3.1.4-4 to 3.1.4-4)
  • Migration status for quitcount/arm64 (3.1.4-4 to 3.1.4-4): Will attempt migration (Any information below is purely informational)
• qutemol/arm64 (0.4.1~cvs20081111-15 to 0.4.1~cvs20081111-15)
  • Migration status for qutemol/arm64 (0.4.1~cvs20081111-15 to 0.4.1~cvs20081111-15): Will attempt migration (Any information below is purely informational)
• qwt/armhf (6.1.4-2 to 6.1.4-2)
  • Migration status for qwt/armhf (6.1.4-2 to 6.1.4-2): Will attempt migration (Any information below is purely informational)
• qwtplot3d/arm64 (0.2.7+svn191+gcc7-3 to 0.2.7+svn191+gcc7-3)
  • Migration status for qwtplot3d/arm64 (0.2.7+svn191+gcc7-3 to 0.2.7+svn191+gcc7-3): Will attempt migration (Any information below is purely informational)
• r-cran-av/armhf (0.9.0+dfsg-1 to 0.9.0+dfsg-1)
  • Migration status for r-cran-av/armhf (0.9.0+dfsg-1 to 0.9.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-backports/arm64 (1.5.0-2 to 1.5.0-2)
  • Migration status for r-cran-backports/arm64 (1.5.0-2 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
• r-cran-httpuv/arm64 (1.6.15+dfsg-1 to 1.6.15+dfsg-1)
  • Migration status for r-cran-httpuv/arm64 (1.6.15+dfsg-1 to 1.6.15+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-rpf/arm64 (1.0.14+dfsg-1 to 1.0.14+dfsg-1)
  • Migration status for r-cran-rpf/arm64 (1.0.14+dfsg-1 to 1.0.14+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-vctrs/arm64 (0.6.5-1 to 0.6.5-1)
  • Migration status for r-cran-vctrs/arm64 (0.6.5-1 to 0.6.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-warp/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-warp/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ragout/arm64 (2.3-5 to 2.3-5)
  • Migration status for ragout/arm64 (2.3-5 to 2.3-5): Will attempt migration (Any information below is purely informational)
• rails_pu (2:7.2.2.1+dfsg-2 to 2:6.1.7.10+dfsg-1~deb12u1)
  • Migration status for rails_pu (2:7.2.2.1+dfsg-2 to 2:6.1.7.10+dfsg-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: rails is newer in the target suite (2:7.2.2.1+dfsg-2 2:6.1.7.10+dfsg-1~deb12u1)
• 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): Will attempt migration (Any information below is purely informational)
• razor/arm64 (1:2.85-9 to 1:2.85-9)
  • Migration status for razor/arm64 (1:2.85-9 to 1:2.85-9): Will attempt migration (Any information below is purely informational)
• razor/armhf (1:2.85-9 to 1:2.85-9)
  • Migration status for razor/armhf (1:2.85-9 to 1:2.85-9): Will attempt migration (Any information below is purely informational)
• readseq/arm64 (1-15 to 1-15)
  • Migration status for readseq/arm64 (1-15 to 1-15): Will attempt migration (Any information below is purely informational)
• renaissance_pu (0.9.0-6 to 0.9.0-4.1+deb12u1)
  • Migration status for renaissance_pu (0.9.0-6 to 0.9.0-4.1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: renaissance is newer in the target suite (0.9.0-6 0.9.0-4.1+deb12u1)
• repeatmasker-recon/arm64 (1.08-8 to 1.08-8)
  • Migration status for repeatmasker-recon/arm64 (1.08-8 to 1.08-8): Will attempt migration (Any information below is purely informational)
• ripmime/arm64 (1.4.0.10.debian.1-3 to 1.4.0.10.debian.1-3)
  • Migration status for ripmime/arm64 (1.4.0.10.debian.1-3 to 1.4.0.10.debian.1-3): Will attempt migration (Any information below is purely informational)
• rtags/arm64 (2.38-12 to 2.38-12)
  • Migration status for rtags/arm64 (2.38-12 to 2.38-12): Will attempt migration (Any information below is purely informational)
• rtags/armhf (2.38-12 to 2.38-12)
  • Migration status for rtags/armhf (2.38-12 to 2.38-12): Will attempt migration (Any information below is purely informational)
• ruby-rack_pu (3.1.12-1 to 2.2.13-1~deb12u1)
  • Migration status for ruby-rack_pu (3.1.12-1 to 2.2.13-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ruby-rack is newer in the target suite (3.1.12-1 2.2.13-1~deb12u1)
• rust-aes-siv/mips64el (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-aes-siv/mips64el (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-aes-siv/riscv64 (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-aes-siv/riscv64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-aes-siv/s390x (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-aes-siv/s390x (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-alloc-stdlib/ppc64el (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-alloc-stdlib/ppc64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-alloc-stdlib/riscv64 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-alloc-stdlib/riscv64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-ansi-width/s390x (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ansi-width/s390x (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ansiterm/riscv64 (0.12.2-1 to 0.12.2-1)
  • Migration status for rust-ansiterm/riscv64 (0.12.2-1 to 0.12.2-1): Will attempt migration (Any information below is purely informational)
• rust-antidote/armhf (1.0.0-3 to 1.0.0-3)
  • Migration status for rust-antidote/armhf (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
• rust-antidote/riscv64 (1.0.0-3 to 1.0.0-3)
  • Migration status for rust-antidote/riscv64 (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
• rust-argparse/s390x (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-argparse/s390x (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-array-init/riscv64 (2.0.1-1 to 2.0.1-1)
  • Migration status for rust-array-init/riscv64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-assert-cmd/amd64 (2.0.12-1 to 2.0.12-1)
  • Migration status for rust-assert-cmd/amd64 (2.0.12-1 to 2.0.12-1): Will attempt migration (Any information below is purely informational)
• rust-assert-cmd/riscv64 (2.0.12-1 to 2.0.12-1)
  • Migration status for rust-assert-cmd/riscv64 (2.0.12-1 to 2.0.12-1): Will attempt migration (Any information below is purely informational)
• rust-async-compat/arm64 (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-async-compat/arm64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-async-generic/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-async-generic/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-asynchronous-codec/s390x (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-asynchronous-codec/s390x (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-atlatl/armel (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-atlatl/armel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-atomic-waker/mips64el (1.1.2-1 to 1.1.2-1)
  • Migration status for rust-atomic-waker/mips64el (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-atomic-waker/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for rust-atomic-waker/riscv64 (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-atomic-waker/s390x (1.1.2-1 to 1.1.2-1)
  • Migration status for rust-atomic-waker/s390x (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-awaitable-error/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-awaitable-error/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-awaitable-error/riscv64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-awaitable-error/riscv64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-bare-metal/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-bare-metal/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-bare-metal/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-bare-metal/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-bare-metal/s390x (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-bare-metal/s390x (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-base-x/s390x (0.2.11-1 to 0.2.11-1)
  • Migration status for rust-base-x/s390x (0.2.11-1 to 0.2.11-1): Will attempt migration (Any information below is purely informational)
• rust-bcrypt-pbkdf/armhf (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-bcrypt-pbkdf/armhf (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-bcrypt-pbkdf/ppc64el (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-bcrypt-pbkdf/ppc64el (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-bcrypt-pbkdf/riscv64 (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-bcrypt-pbkdf/riscv64 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-binary-heap-plus/s390x (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-binary-heap-plus/s390x (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-binascii/arm64 (0.1.4-3 to 0.1.4-3)
  • Migration status for rust-binascii/arm64 (0.1.4-3 to 0.1.4-3): Will attempt migration (Any information below is purely informational)
• rust-binascii/ppc64el (0.1.4-3 to 0.1.4-3)
  • Migration status for rust-binascii/ppc64el (0.1.4-3 to 0.1.4-3): Will attempt migration (Any information below is purely informational)
• rust-binascii/riscv64 (0.1.4-3 to 0.1.4-3)
  • Migration status for rust-binascii/riscv64 (0.1.4-3 to 0.1.4-3): Will attempt migration (Any information below is purely informational)
• rust-bincode/amd64 (1.3.3-1 to 1.3.3-1)
  • Migration status for rust-bincode/amd64 (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-bincode/arm64 (1.3.3-1 to 1.3.3-1)
  • Migration status for rust-bincode/arm64 (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-bincode/riscv64 (1.3.3-1 to 1.3.3-1)
  • Migration status for rust-bincode/riscv64 (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-binfarce/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-binfarce/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-biquad/mips64el (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-biquad/mips64el (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-biquad/s390x (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-biquad/s390x (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-bit-field/riscv64 (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-bit-field/riscv64 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-bit-utils/amd64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-bit-utils/amd64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-bit-utils/riscv64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-bit-utils/riscv64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-bitvec/mips64el (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-bitvec/mips64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-bitvec/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-bitvec/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-blanket/amd64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-blanket/amd64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-blanket/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-blanket/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-blanket/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-blanket/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-blanket/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-blanket/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-blanket/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-blanket/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-botan-sys/riscv64 (0.10.5-1 to 0.10.5-1)
  • Migration status for rust-botan-sys/riscv64 (0.10.5-1 to 0.10.5-1): Will attempt migration (Any information below is purely informational)
• rust-botan-sys/s390x (0.10.5-1 to 0.10.5-1)
  • Migration status for rust-botan-sys/s390x (0.10.5-1 to 0.10.5-1): Will attempt migration (Any information below is purely informational)
• rust-botan/riscv64 (0.10.7-1 to 0.10.7-1)
  • Migration status for rust-botan/riscv64 (0.10.7-1 to 0.10.7-1): Will attempt migration (Any information below is purely informational)
• rust-build-rs/riscv64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-build-rs/riscv64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-build-rs/s390x (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-build-rs/s390x (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-byte-string/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-byte-string/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-byte-string/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-byte-string/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-byte-tools/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-byte-tools/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-byte-tools/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-byte-tools/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-byte-tools/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-byte-tools/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-bytelines/mips64el (2.4.0-1 to 2.4.0-1)
  • Migration status for rust-bytelines/mips64el (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-bytelines/riscv64 (2.4.0-1 to 2.4.0-1)
  • Migration status for rust-bytelines/riscv64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-bytemuck-derive/armhf (1.5.0-2 to 1.5.0-2)
  • Migration status for rust-bytemuck-derive/armhf (1.5.0-2 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
• rust-byteorder/amd64 (1.5.0-1 to 1.5.0-1)
  • Migration status for rust-byteorder/amd64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-byteorder/armel (1.5.0-1 to 1.5.0-1)
  • Migration status for rust-byteorder/armel (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-bzip2-sys/armel (0.1.11-1 to 0.1.11-1)
  • Migration status for rust-bzip2-sys/armel (0.1.11-1 to 0.1.11-1): Will attempt migration (Any information below is purely informational)
• rust-bzip2-sys/armhf (0.1.11-1 to 0.1.11-1)
  • Migration status for rust-bzip2-sys/armhf (0.1.11-1 to 0.1.11-1): Will attempt migration (Any information below is purely informational)
• rust-bzip2-sys/ppc64el (0.1.11-1 to 0.1.11-1)
  • Migration status for rust-bzip2-sys/ppc64el (0.1.11-1 to 0.1.11-1): Will attempt migration (Any information below is purely informational)
• rust-bzip2-sys/riscv64 (0.1.11-1 to 0.1.11-1)
  • Migration status for rust-bzip2-sys/riscv64 (0.1.11-1 to 0.1.11-1): Will attempt migration (Any information below is purely informational)
• rust-bzip2/riscv64 (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-bzip2/riscv64 (0.4.4-1 to 0.4.4-1): Will attempt migration (Any information below is purely informational)
• rust-cab/ppc64el (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-cab/ppc64el (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-cab/riscv64 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-cab/riscv64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-cached-proc-macro/ppc64el (0.20.0-1 to 0.20.0-1)
  • Migration status for rust-cached-proc-macro/ppc64el (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
• rust-cached-proc-macro/riscv64 (0.20.0-1 to 0.20.0-1)
  • Migration status for rust-cached-proc-macro/riscv64 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
• rust-canonical-path/armhf (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-canonical-path/armhf (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-canonical-path/riscv64 (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-canonical-path/riscv64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-capnpc/amd64 (0.19.0-1 to 0.19.0-1)
  • Migration status for rust-capnpc/amd64 (0.19.0-1 to 0.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-capnpc/armel (0.19.0-1 to 0.19.0-1)
  • Migration status for rust-capnpc/armel (0.19.0-1 to 0.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-capnpc/armhf (0.19.0-1 to 0.19.0-1)
  • Migration status for rust-capnpc/armhf (0.19.0-1 to 0.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-capnpc/i386 (0.19.0-1 to 0.19.0-1)
  • Migration status for rust-capnpc/i386 (0.19.0-1 to 0.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-card-backend-pcsc/i386 (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-card-backend-pcsc/i386 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-card-backend-pcsc/ppc64el (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-card-backend-pcsc/ppc64el (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-card-backend-pcsc/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-card-backend-pcsc/riscv64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-cascade/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-cascade/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-cascade/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-cascade/s390x (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-caseless/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-caseless/riscv64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-cassowary/riscv64 (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-cassowary/riscv64 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-cfb-mode/armhf (0.8.2-1 to 0.8.2-1)
  • Migration status for rust-cfb-mode/armhf (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• rust-cfb-mode/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for rust-cfb-mode/riscv64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• rust-chacha20/armel (0.9.1-1 to 0.9.1-1)
  • Migration status for rust-chacha20/armel (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• rust-chacha20/mips64el (0.9.1-1 to 0.9.1-1)
  • Migration status for rust-chacha20/mips64el (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• rust-chacha20/riscv64 (0.9.1-1 to 0.9.1-1)
  • Migration status for rust-chacha20/riscv64 (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• rust-chacha20/s390x (0.9.1-1 to 0.9.1-1)
  • Migration status for rust-chacha20/s390x (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• rust-chunked-transfer/amd64 (1.4.0-1 to 1.4.0-1)
  • Migration status for rust-chunked-transfer/amd64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-chunked-transfer/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for rust-chunked-transfer/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-cid/armel (0.10.1-2 to 0.10.1-2)
  • Migration status for rust-cid/armel (0.10.1-2 to 0.10.1-2): Will attempt migration (Any information below is purely informational)
• rust-cid/armhf (0.10.1-2 to 0.10.1-2)
  • Migration status for rust-cid/armhf (0.10.1-2 to 0.10.1-2): Will attempt migration (Any information below is purely informational)
• rust-cid/i386 (0.10.1-2 to 0.10.1-2)
  • Migration status for rust-cid/i386 (0.10.1-2 to 0.10.1-2): Will attempt migration (Any information below is purely informational)
• rust-cint/arm64 (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-cint/arm64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-cint/armel (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-cint/armel (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-cint/s390x (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-cint/s390x (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-cipher/i386 (0.4.4-3 to 0.4.4-3)
  • Migration status for rust-cipher/i386 (0.4.4-3 to 0.4.4-3): Will attempt migration (Any information below is purely informational)
• rust-cipher/riscv64 (0.4.4-3 to 0.4.4-3)
  • Migration status for rust-cipher/riscv64 (0.4.4-3 to 0.4.4-3): Will attempt migration (Any information below is purely informational)
• rust-cipher/s390x (0.4.4-3 to 0.4.4-3)
  • Migration status for rust-cipher/s390x (0.4.4-3 to 0.4.4-3): Will attempt migration (Any information below is purely informational)
• rust-clap-complete-fig/amd64 (4.3.1-1 to 4.3.1-1)
  • Migration status for rust-clap-complete-fig/amd64 (4.3.1-1 to 4.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-clap-complete-fig/riscv64 (4.3.1-1 to 4.3.1-1)
  • Migration status for rust-clap-complete-fig/riscv64 (4.3.1-1 to 4.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-clap-complete-fig/s390x (4.3.1-1 to 4.3.1-1)
  • Migration status for rust-clap-complete-fig/s390x (4.3.1-1 to 4.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-clicolors-control/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-clicolors-control/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-clicolors-control/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-clicolors-control/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-cmac/mips64el (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-cmac/mips64el (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-cmac/s390x (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-cmac/s390x (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-cntr-fuse-abi/s390x (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-cntr-fuse-abi/s390x (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-cntr-fuse-sys/riscv64 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-cntr-fuse-sys/riscv64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-color-quant/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-color-quant/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-color-quant/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-color-quant/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-color-spantrace/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-color-spantrace/mips64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-color-spantrace/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-color-spantrace/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-color-spantrace/riscv64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-color-spantrace/riscv64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-color-spantrace/s390x (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-color-spantrace/s390x (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-colorchoice/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-colorchoice/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-colorchoice/riscv64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-colorchoice/riscv64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-colorful/amd64 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-colorful/amd64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-colorful/riscv64 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-colorful/riscv64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-compound-duration/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-compound-duration/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-concat-idents/amd64 (1.1.4-1 to 1.1.4-1)
  • Migration status for rust-concat-idents/amd64 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-concat-idents/armhf (1.1.4-1 to 1.1.4-1)
  • Migration status for rust-concat-idents/armhf (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-concat-idents/riscv64 (1.1.4-1 to 1.1.4-1)
  • Migration status for rust-concat-idents/riscv64 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-concolor/riscv64 (0.0.12-1 to 0.0.12-1)
  • Migration status for rust-concolor/riscv64 (0.0.12-1 to 0.0.12-1): Will attempt migration (Any information below is purely informational)
• rust-condtype/armhf (1.3.0-1 to 1.3.0-1)
  • Migration status for rust-condtype/armhf (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-condtype/ppc64el (1.3.0-1 to 1.3.0-1)
  • Migration status for rust-condtype/ppc64el (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-console-log/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-console-log/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-console-log/armhf (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-console-log/armhf (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-console-log/riscv64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-console-log/riscv64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-content-inspector/riscv64 (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-content-inspector/riscv64 (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-content-inspector/s390x (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-content-inspector/s390x (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-convert-case/arm64 (0.6.0-2 to 0.6.0-2)
  • Migration status for rust-convert-case/arm64 (0.6.0-2 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
• rust-convert-case/armel (0.6.0-2 to 0.6.0-2)
  • Migration status for rust-convert-case/armel (0.6.0-2 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
• rust-convert-case/riscv64 (0.6.0-2 to 0.6.0-2)
  • Migration status for rust-convert-case/riscv64 (0.6.0-2 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
• rust-copyless/mips64el (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-copyless/mips64el (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-copyless/riscv64 (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-copyless/riscv64 (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-cp-r/amd64 (0.5.1-2 to 0.5.1-2)
  • Migration status for rust-cp-r/amd64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• rust-cp-r/armel (0.5.1-2 to 0.5.1-2)
  • Migration status for rust-cp-r/armel (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• rust-cp-r/armhf (0.5.1-2 to 0.5.1-2)
  • Migration status for rust-cp-r/armhf (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• rust-cp-r/i386 (0.5.1-2 to 0.5.1-2)
  • Migration status for rust-cp-r/i386 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• rust-cp-r/mips64el (0.5.1-2 to 0.5.1-2)
  • Migration status for rust-cp-r/mips64el (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• rust-cplus-demangle/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-cplus-demangle/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-cplus-demangle/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-cplus-demangle/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-cpp-syn/arm64 (0.12.0-4 to 0.12.0-4)
  • Migration status for rust-cpp-syn/arm64 (0.12.0-4 to 0.12.0-4): Will attempt migration (Any information below is purely informational)
• rust-cpp-syn/ppc64el (0.12.0-4 to 0.12.0-4)
  • Migration status for rust-cpp-syn/ppc64el (0.12.0-4 to 0.12.0-4): Will attempt migration (Any information below is purely informational)
• rust-cpp-synom/armel (0.12.0-1 to 0.12.0-1)
  • Migration status for rust-cpp-synom/armel (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• rust-cpp-synom/armhf (0.12.0-1 to 0.12.0-1)
  • Migration status for rust-cpp-synom/armhf (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• rust-cpp/armhf (0.5.9-1 to 0.5.9-1)
  • Migration status for rust-cpp/armhf (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• rust-cpuid-bool/armhf (0.1.2-4 to 0.1.2-4)
  • Migration status for rust-cpuid-bool/armhf (0.1.2-4 to 0.1.2-4): Will attempt migration (Any information below is purely informational)
• rust-cpuid-bool/s390x (0.1.2-4 to 0.1.2-4)
  • Migration status for rust-cpuid-bool/s390x (0.1.2-4 to 0.1.2-4): Will attempt migration (Any information below is purely informational)
• rust-crc32c/armel (0.6.8-1 to 0.6.8-1)
  • Migration status for rust-crc32c/armel (0.6.8-1 to 0.6.8-1): Will attempt migration (Any information below is purely informational)
• rust-crc32c/ppc64el (0.6.8-1 to 0.6.8-1)
  • Migration status for rust-crc32c/ppc64el (0.6.8-1 to 0.6.8-1): Will attempt migration (Any information below is purely informational)
• rust-crc32c/s390x (0.6.8-1 to 0.6.8-1)
  • Migration status for rust-crc32c/s390x (0.6.8-1 to 0.6.8-1): Will attempt migration (Any information below is purely informational)
• rust-crossterm-winapi/arm64 (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-crossterm-winapi/arm64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-crossterm-winapi/armel (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-crossterm-winapi/armel (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-crossterm-winapi/armhf (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-crossterm-winapi/armhf (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-crypto-mac/amd64 (0.10.0-2 to 0.10.0-2)
  • Migration status for rust-crypto-mac/amd64 (0.10.0-2 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
• rust-crypto-mac/arm64 (0.10.0-2 to 0.10.0-2)
  • Migration status for rust-crypto-mac/arm64 (0.10.0-2 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
• rust-crypto-mac/armhf (0.10.0-2 to 0.10.0-2)
  • Migration status for rust-crypto-mac/armhf (0.10.0-2 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
• rust-crypto-secretbox/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-crypto-secretbox/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-cssparser/armhf (0.31.2-2 to 0.31.2-2)
  • Migration status for rust-cssparser/armhf (0.31.2-2 to 0.31.2-2): Will attempt migration (Any information below is purely informational)
• rust-cssparser/i386 (0.31.2-2 to 0.31.2-2)
  • Migration status for rust-cssparser/i386 (0.31.2-2 to 0.31.2-2): Will attempt migration (Any information below is purely informational)
• rust-cssparser/ppc64el (0.31.2-2 to 0.31.2-2)
  • Migration status for rust-cssparser/ppc64el (0.31.2-2 to 0.31.2-2): Will attempt migration (Any information below is purely informational)
• rust-ctr/amd64 (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-ctr/amd64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-ctr/arm64 (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-ctr/arm64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-ctr/mips64el (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-ctr/mips64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-ctr/ppc64el (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-ctr/ppc64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-ctr/s390x (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-ctr/s390x (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-cty/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-cty/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-cursive-macros/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-cursive-macros/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-cursive-macros/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-cursive-macros/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-cursive-macros/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-cursive-macros/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-cursive-macros/s390x (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-cursive-macros/s390x (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-cursive-table-view/amd64 (0.15.0-1 to 0.15.0-1)
  • Migration status for rust-cursive-table-view/amd64 (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
• rust-cursive-table-view/armel (0.15.0-1 to 0.15.0-1)
  • Migration status for rust-cursive-table-view/armel (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
• rust-cursive-table-view/armhf (0.15.0-1 to 0.15.0-1)
  • Migration status for rust-cursive-table-view/armhf (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
• rust-cvt/mips64el (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-cvt/mips64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-data-encoding-macro/i386 (0.1.12-1 to 0.1.12-1)
  • Migration status for rust-data-encoding-macro/i386 (0.1.12-1 to 0.1.12-1): Will attempt migration (Any information below is purely informational)
• rust-dateparser/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-dateparser/i386 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-dateparser/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-dateparser/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-dbl/armel (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-dbl/armel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-dbl/armhf (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-dbl/armhf (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-dbus-tree/amd64 (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-dbus-tree/amd64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-dbus-tree/armel (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-dbus-tree/armel (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-dbus-tree/armhf (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-dbus-tree/armhf (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-dbus-tree/mips64el (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-dbus-tree/mips64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-der-derive/arm64 (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-der-derive/arm64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-der-derive/i386 (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-der-derive/i386 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-der-derive/mips64el (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-der-derive/mips64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-derive-where/arm64 (1.2.7-1 to 1.2.7-1)
  • Migration status for rust-derive-where/arm64 (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
• rust-derive-where/armhf (1.2.7-1 to 1.2.7-1)
  • Migration status for rust-derive-where/armhf (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
• rust-destructure-traitobject/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-destructure-traitobject/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-destructure-traitobject/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-destructure-traitobject/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-destructure-traitobject/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-destructure-traitobject/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-devicemapper/arm64 (0.34.4-1 to 0.34.4-1)
  • Migration status for rust-devicemapper/arm64 (0.34.4-1 to 0.34.4-1): Will attempt migration (Any information below is purely informational)
• rust-devicemapper/armel (0.34.4-1 to 0.34.4-1)
  • Migration status for rust-devicemapper/armel (0.34.4-1 to 0.34.4-1): Will attempt migration (Any information below is purely informational)
• rust-devicemapper/i386 (0.34.4-1 to 0.34.4-1)
  • Migration status for rust-devicemapper/i386 (0.34.4-1 to 0.34.4-1): Will attempt migration (Any information below is purely informational)
• rust-devicemapper/ppc64el (0.34.4-1 to 0.34.4-1)
  • Migration status for rust-devicemapper/ppc64el (0.34.4-1 to 0.34.4-1): Will attempt migration (Any information below is purely informational)
• rust-dhcproto-macros/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-dhcproto-macros/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-dhcproto-macros/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-dhcproto-macros/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-dhcproto-macros/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-dhcproto-macros/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-dirs-next/arm64 (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-dirs-next/arm64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-dirs-next/mips64el (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-dirs-next/mips64el (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-dirs-next/s390x (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-dirs-next/s390x (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-dirs-sys-next/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-dirs-sys-next/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-display-error-chain/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-display-error-chain/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-display-error-chain/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-display-error-chain/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-display-error-chain/s390x (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-display-error-chain/s390x (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-displaydoc/arm64 (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-displaydoc/arm64 (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-displaydoc/armel (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-displaydoc/armel (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-displaydoc/armhf (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-displaydoc/armhf (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-displaydoc/mips64el (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-displaydoc/mips64el (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-dlv-list/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-dlv-list/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-dlv-list/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-dlv-list/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-dlv-list/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-dlv-list/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-dns-lookup/armhf (1.0.8-4 to 1.0.8-4)
  • Migration status for rust-dns-lookup/armhf (1.0.8-4 to 1.0.8-4): Will attempt migration (Any information below is purely informational)
• rust-doc-comment/arm64 (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-doc-comment/arm64 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-doc-comment/armhf (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-doc-comment/armhf (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-dockerfile/arm64 (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-dockerfile/arm64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-dockerfile/armel (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-dockerfile/armel (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-dockerfile/armhf (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-dockerfile/armhf (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-document-features/arm64 (0.2.7-3 to 0.2.7-3)
  • Migration status for rust-document-features/arm64 (0.2.7-3 to 0.2.7-3): Will attempt migration (Any information below is purely informational)
• rust-document-features/armel (0.2.7-3 to 0.2.7-3)
  • Migration status for rust-document-features/armel (0.2.7-3 to 0.2.7-3): Will attempt migration (Any information below is purely informational)
• rust-document-features/armhf (0.2.7-3 to 0.2.7-3)
  • Migration status for rust-document-features/armhf (0.2.7-3 to 0.2.7-3): Will attempt migration (Any information below is purely informational)
• rust-dogged/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-dogged/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-dogged/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-dogged/i386 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-dotenvy/armel (0.15.7-1 to 0.15.7-1)
  • Migration status for rust-dotenvy/armel (0.15.7-1 to 0.15.7-1): Will attempt migration (Any information below is purely informational)
• rust-downcast-rs/arm64 (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-downcast-rs/arm64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-downcast-rs/mips64el (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-downcast-rs/mips64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-downcast-rs/s390x (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-downcast-rs/s390x (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-doxygen-rs/arm64 (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-doxygen-rs/arm64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-doxygen-rs/armel (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-doxygen-rs/armel (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-doxygen-rs/mips64el (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-doxygen-rs/mips64el (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-doxygen-rs/ppc64el (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-doxygen-rs/ppc64el (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-doxygen-rs/s390x (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-doxygen-rs/s390x (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-drop-bomb/arm64 (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-drop-bomb/arm64 (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-drop-bomb/s390x (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-drop-bomb/s390x (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-duct/arm64 (0.13.5-2 to 0.13.5-2)
  • Migration status for rust-duct/arm64 (0.13.5-2 to 0.13.5-2): Will attempt migration (Any information below is purely informational)
• rust-duct/i386 (0.13.5-2 to 0.13.5-2)
  • Migration status for rust-duct/i386 (0.13.5-2 to 0.13.5-2): Will attempt migration (Any information below is purely informational)
• rust-duct/s390x (0.13.5-2 to 0.13.5-2)
  • Migration status for rust-duct/s390x (0.13.5-2 to 0.13.5-2): Will attempt migration (Any information below is purely informational)
• rust-easy-cast/arm64 (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-easy-cast/arm64 (0.4.4-1 to 0.4.4-1): Will attempt migration (Any information below is purely informational)
• rust-easy-cast/i386 (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-easy-cast/i386 (0.4.4-1 to 0.4.4-1): Will attempt migration (Any information below is purely informational)
• rust-ecb/armhf (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-ecb/armhf (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-ecb/s390x (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-ecb/s390x (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-ed25519-compact/arm64 (2.0.4-1 to 2.0.4-1)
  • Migration status for rust-ed25519-compact/arm64 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-ed25519-compact/mips64el (2.0.4-1 to 2.0.4-1)
  • Migration status for rust-ed25519-compact/mips64el (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-ed25519-compact/ppc64el (2.0.4-1 to 2.0.4-1)
  • Migration status for rust-ed25519-compact/ppc64el (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-edit-distance/amd64 (2.1.0-1 to 2.1.0-1)
  • Migration status for rust-edit-distance/amd64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-edit-distance/arm64 (2.1.0-1 to 2.1.0-1)
  • Migration status for rust-edit-distance/arm64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-edit-distance/armel (2.1.0-1 to 2.1.0-1)
  • Migration status for rust-edit-distance/armel (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ego-tree/arm64 (0.6.2-1 to 0.6.2-1)
  • Migration status for rust-ego-tree/arm64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
• rust-ego-tree/armhf (0.6.2-1 to 0.6.2-1)
  • Migration status for rust-ego-tree/armhf (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
• rust-ego-tree/mips64el (0.6.2-1 to 0.6.2-1)
  • Migration status for rust-ego-tree/mips64el (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
• rust-ego-tree/ppc64el (0.6.2-1 to 0.6.2-1)
  • Migration status for rust-ego-tree/ppc64el (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
• rust-elf-rs/arm64 (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-elf-rs/arm64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-elf-rs/armel (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-elf-rs/armel (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-elf-rs/armhf (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-elf-rs/armhf (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-enum-ordinalize/arm64 (3.1.13-1 to 3.1.13-1)
  • Migration status for rust-enum-ordinalize/arm64 (3.1.13-1 to 3.1.13-1): Will attempt migration (Any information below is purely informational)
• rust-enum-ordinalize/armhf (3.1.13-1 to 3.1.13-1)
  • Migration status for rust-enum-ordinalize/armhf (3.1.13-1 to 3.1.13-1): Will attempt migration (Any information below is purely informational)
• rust-enum-primitive-derive/arm64 (0.2.2-2 to 0.2.2-2)
  • Migration status for rust-enum-primitive-derive/arm64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• rust-enum-primitive-derive/armhf (0.2.2-2 to 0.2.2-2)
  • Migration status for rust-enum-primitive-derive/armhf (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• rust-enum-primitive-derive/mips64el (0.2.2-2 to 0.2.2-2)
  • Migration status for rust-enum-primitive-derive/mips64el (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• rust-enum-primitive-derive/s390x (0.2.2-2 to 0.2.2-2)
  • Migration status for rust-enum-primitive-derive/s390x (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• rust-enumber/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-enumber/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-enumber/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-enumber/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-epoll/armhf (4.1.0-1 to 4.1.0-1)
  • Migration status for rust-epoll/armhf (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-equivalent/amd64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-equivalent/amd64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-equivalent/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-equivalent/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-equivalent/armel (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-equivalent/armel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-equivalent/armhf (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-equivalent/armhf (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-equivalent/i386 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-equivalent/i386 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-equivalent/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-equivalent/ppc64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-equivalent/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-equivalent/s390x (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-error-chain/arm64 (0.12.4-1 to 0.12.4-1)
  • Migration status for rust-error-chain/arm64 (0.12.4-1 to 0.12.4-1): Will attempt migration (Any information below is purely informational)
• rust-error-chain/i386 (0.12.4-1 to 0.12.4-1)
  • Migration status for rust-error-chain/i386 (0.12.4-1 to 0.12.4-1): Will attempt migration (Any information below is purely informational)
• rust-error-chain/mips64el (0.12.4-1 to 0.12.4-1)
  • Migration status for rust-error-chain/mips64el (0.12.4-1 to 0.12.4-1): Will attempt migration (Any information below is purely informational)
• rust-error-chain/ppc64el (0.12.4-1 to 0.12.4-1)
  • Migration status for rust-error-chain/ppc64el (0.12.4-1 to 0.12.4-1): Will attempt migration (Any information below is purely informational)
• rust-eww-shared-util/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-eww-shared-util/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-eww-shared-util/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-eww-shared-util/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-eww-shared-util/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-eww-shared-util/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-eww-shared-util/s390x (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-eww-shared-util/s390x (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-expat-sys/amd64 (2.1.6-3 to 2.1.6-3)
  • Migration status for rust-expat-sys/amd64 (2.1.6-3 to 2.1.6-3): Will attempt migration (Any information below is purely informational)
• rust-expat-sys/armhf (2.1.6-3 to 2.1.6-3)
  • Migration status for rust-expat-sys/armhf (2.1.6-3 to 2.1.6-3): Will attempt migration (Any information below is purely informational)
• rust-expat-sys/i386 (2.1.6-3 to 2.1.6-3)
  • Migration status for rust-expat-sys/i386 (2.1.6-3 to 2.1.6-3): Will attempt migration (Any information below is purely informational)
• rust-expat-sys/s390x (2.1.6-3 to 2.1.6-3)
  • Migration status for rust-expat-sys/s390x (2.1.6-3 to 2.1.6-3): Will attempt migration (Any information below is purely informational)
• rust-fake-simd/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-fake-simd/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-fake-simd/armel (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-fake-simd/armel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-fake-simd/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-fake-simd/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-fasteval/arm64 (0.2.4-5 to 0.2.4-5)
  • Migration status for rust-fasteval/arm64 (0.2.4-5 to 0.2.4-5): Will attempt migration (Any information below is purely informational)
• rust-fasteval/armhf (0.2.4-5 to 0.2.4-5)
  • Migration status for rust-fasteval/armhf (0.2.4-5 to 0.2.4-5): Will attempt migration (Any information below is purely informational)
• rust-fasteval/s390x (0.2.4-5 to 0.2.4-5)
  • Migration status for rust-fasteval/s390x (0.2.4-5 to 0.2.4-5): Will attempt migration (Any information below is purely informational)
• rust-fax/armhf (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-fax/armhf (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-fax/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-fax/mips64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-fd-lock/armel (3.0.13-1 to 3.0.13-1)
  • Migration status for rust-fd-lock/armel (3.0.13-1 to 3.0.13-1): Will attempt migration (Any information below is purely informational)
• rust-fd-lock/armhf (3.0.13-1 to 3.0.13-1)
  • Migration status for rust-fd-lock/armhf (3.0.13-1 to 3.0.13-1): Will attempt migration (Any information below is purely informational)
• rust-fdlimit/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-fdlimit/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-fdlimit/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-fdlimit/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-ff-derive/arm64 (0.13.0-1 to 0.13.0-1)
  • Migration status for rust-ff-derive/arm64 (0.13.0-1 to 0.13.0-1): Will attempt migration (Any information below is purely informational)
• rust-ff-derive/armel (0.13.0-1 to 0.13.0-1)
  • Migration status for rust-ff-derive/armel (0.13.0-1 to 0.13.0-1): Will attempt migration (Any information below is purely informational)
• rust-ff-derive/armhf (0.13.0-1 to 0.13.0-1)
  • Migration status for rust-ff-derive/armhf (0.13.0-1 to 0.13.0-1): Will attempt migration (Any information below is purely informational)
• rust-ff-derive/s390x (0.13.0-1 to 0.13.0-1)
  • Migration status for rust-ff-derive/s390x (0.13.0-1 to 0.13.0-1): Will attempt migration (Any information below is purely informational)
• rust-file-diff/amd64 (1.0.0-2 to 1.0.0-2)
  • Migration status for rust-file-diff/amd64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• rust-file-diff/arm64 (1.0.0-2 to 1.0.0-2)
  • Migration status for rust-file-diff/arm64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• rust-file-diff/mips64el (1.0.0-2 to 1.0.0-2)
  • Migration status for rust-file-diff/mips64el (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• rust-file-diff/s390x (1.0.0-2 to 1.0.0-2)
  • Migration status for rust-file-diff/s390x (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• rust-file-size/armel (1.0.3-1 to 1.0.3-1)
  • Migration status for rust-file-size/armel (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-file-size/armhf (1.0.3-1 to 1.0.3-1)
  • Migration status for rust-file-size/armhf (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-find-crate/arm64 (0.6.3-1 to 0.6.3-1)
  • Migration status for rust-find-crate/arm64 (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• rust-find-crate/armhf (0.6.3-1 to 0.6.3-1)
  • Migration status for rust-find-crate/armhf (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• rust-find-crate/i386 (0.6.3-1 to 0.6.3-1)
  • Migration status for rust-find-crate/i386 (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• rust-find-crate/mips64el (0.6.3-1 to 0.6.3-1)
  • Migration status for rust-find-crate/mips64el (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• rust-find-crate/s390x (0.6.3-1 to 0.6.3-1)
  • Migration status for rust-find-crate/s390x (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• rust-fix-getters-rules/amd64 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-fix-getters-rules/amd64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-fix-getters-rules/arm64 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-fix-getters-rules/arm64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-fix-getters-rules/armel (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-fix-getters-rules/armel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-fix-getters-rules/armhf (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-fix-getters-rules/armhf (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-flagset/arm64 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-flagset/arm64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-flagset/armhf (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-flagset/armhf (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-flagset/s390x (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-flagset/s390x (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-float-eq-derive/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-float-eq-derive/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-float-eq-derive/armel (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-float-eq-derive/armel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-float-eq-derive/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-float-eq-derive/s390x (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-float-eq/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-float-eq/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-float-eq/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-float-eq/ppc64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-float-eq/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-float-eq/s390x (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-float-ord/armhf (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-float-ord/armhf (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-float-ord/i386 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-float-ord/i386 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-float-ord/mips64el (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-float-ord/mips64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-float-ord/s390x (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-float-ord/s390x (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-fluent-bundle/armel (0.15.2-1 to 0.15.2-1)
  • Migration status for rust-fluent-bundle/armel (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
• rust-fluent-bundle/mips64el (0.15.2-1 to 0.15.2-1)
  • Migration status for rust-fluent-bundle/mips64el (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
• rust-fontconfig-parser/amd64 (0.5.7-1 to 0.5.7-1)
  • Migration status for rust-fontconfig-parser/amd64 (0.5.7-1 to 0.5.7-1): Will attempt migration (Any information below is purely informational)
• rust-fontconfig-parser/i386 (0.5.7-1 to 0.5.7-1)
  • Migration status for rust-fontconfig-parser/i386 (0.5.7-1 to 0.5.7-1): Will attempt migration (Any information below is purely informational)
• rust-fontconfig-parser/mips64el (0.5.7-1 to 0.5.7-1)
  • Migration status for rust-fontconfig-parser/mips64el (0.5.7-1 to 0.5.7-1): Will attempt migration (Any information below is purely informational)
• rust-form-urlencoded/arm64 (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-form-urlencoded/arm64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-form-urlencoded/armhf (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-form-urlencoded/armhf (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-form-urlencoded/s390x (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-form-urlencoded/s390x (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-fragile/armhf (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-fragile/armhf (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-fragile/i386 (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-fragile/i386 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-fragile/mips64el (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-fragile/mips64el (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-fragile/s390x (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-fragile/s390x (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-fs2/arm64 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-fs2/arm64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-fs2/armel (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-fs2/armel (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-fs2/armhf (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-fs2/armhf (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-fs2/mips64el (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-fs2/mips64el (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-fs2/ppc64el (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-fs2/ppc64el (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-fst/amd64 (0.4.7-1 to 0.4.7-1)
  • Migration status for rust-fst/amd64 (0.4.7-1 to 0.4.7-1): Will attempt migration (Any information below is purely informational)
• rust-fst/armel (0.4.7-1 to 0.4.7-1)
  • Migration status for rust-fst/armel (0.4.7-1 to 0.4.7-1): Will attempt migration (Any information below is purely informational)
• rust-fst/i386 (0.4.7-1 to 0.4.7-1)
  • Migration status for rust-fst/i386 (0.4.7-1 to 0.4.7-1): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-cprng/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-fuchsia-cprng/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-cprng/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-fuchsia-cprng/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-cprng/armhf (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-fuchsia-cprng/armhf (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-cprng/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-fuchsia-cprng/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-cprng/s390x (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-fuchsia-cprng/s390x (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-zircon-sys/amd64 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-fuchsia-zircon-sys/amd64 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-zircon-sys/armel (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-fuchsia-zircon-sys/armel (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-zircon-sys/armhf (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-fuchsia-zircon-sys/armhf (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-fuchsia-zircon-sys/mips64el (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-fuchsia-zircon-sys/mips64el (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-fun-time-derive/armel (0.3.4-1 to 0.3.4-1)
  • Migration status for rust-fun-time-derive/armel (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
• rust-fun-time-derive/i386 (0.3.4-1 to 0.3.4-1)
  • Migration status for rust-fun-time-derive/i386 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
• rust-funty/amd64 (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-funty/amd64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-funty/arm64 (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-funty/arm64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-funty/armel (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-funty/armel (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-funty/armhf (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-funty/armhf (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-funty/i386 (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-funty/i386 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-funty/mips64el (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-funty/mips64el (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-funty/s390x (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-funty/s390x (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-futures-codec/armhf (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-futures-codec/armhf (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-futures-codec/s390x (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-futures-codec/s390x (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-futures-locks/arm64 (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-futures-locks/arm64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-futures-locks/armel (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-futures-locks/armel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-futures-locks/armhf (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-futures-locks/armhf (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-futures-locks/ppc64el (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-futures-locks/ppc64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-futures-micro/arm64 (1.0.0~rc0-1 to 1.0.0~rc0-1)
  • Migration status for rust-futures-micro/arm64 (1.0.0~rc0-1 to 1.0.0~rc0-1): Will attempt migration (Any information below is purely informational)
• rust-futures-micro/mips64el (1.0.0~rc0-1 to 1.0.0~rc0-1)
  • Migration status for rust-futures-micro/mips64el (1.0.0~rc0-1 to 1.0.0~rc0-1): Will attempt migration (Any information below is purely informational)
• rust-futures-micro/s390x (1.0.0~rc0-1 to 1.0.0~rc0-1)
  • Migration status for rust-futures-micro/s390x (1.0.0~rc0-1 to 1.0.0~rc0-1): Will attempt migration (Any information below is purely informational)
• rust-futures-ringbuf/amd64 (0.4.0-3 to 0.4.0-3)
  • Migration status for rust-futures-ringbuf/amd64 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• rust-futures-ringbuf/arm64 (0.4.0-3 to 0.4.0-3)
  • Migration status for rust-futures-ringbuf/arm64 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• rust-futures-ringbuf/armel (0.4.0-3 to 0.4.0-3)
  • Migration status for rust-futures-ringbuf/armel (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• rust-futures-ringbuf/i386 (0.4.0-3 to 0.4.0-3)
  • Migration status for rust-futures-ringbuf/i386 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• rust-futures-ringbuf/mips64el (0.4.0-3 to 0.4.0-3)
  • Migration status for rust-futures-ringbuf/mips64el (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• rust-gag/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-gag/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-gag/armhf (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-gag/armhf (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-gat-std-proc/amd64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-gat-std-proc/amd64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-gat-std-proc/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-gat-std-proc/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-gat-std-proc/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-gat-std-proc/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-gat-std-proc/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-gat-std-proc/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-gat-std-proc/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-gat-std-proc/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-genawaiter-macro/arm64 (0.99.1-1 to 0.99.1-1)
  • Migration status for rust-genawaiter-macro/arm64 (0.99.1-1 to 0.99.1-1): Will attempt migration (Any information below is purely informational)
• rust-genawaiter-macro/armel (0.99.1-1 to 0.99.1-1)
  • Migration status for rust-genawaiter-macro/armel (0.99.1-1 to 0.99.1-1): Will attempt migration (Any information below is purely informational)
• rust-genawaiter-macro/mips64el (0.99.1-1 to 0.99.1-1)
  • Migration status for rust-genawaiter-macro/mips64el (0.99.1-1 to 0.99.1-1): Will attempt migration (Any information below is purely informational)
• rust-genetlink/armel (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-genetlink/armel (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-genetlink/ppc64el (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-genetlink/ppc64el (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-genetlink/s390x (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-genetlink/s390x (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-geo-types/armel (0.7.11-2 to 0.7.11-2)
  • Migration status for rust-geo-types/armel (0.7.11-2 to 0.7.11-2): Will attempt migration (Any information below is purely informational)
• rust-geo-types/armhf (0.7.11-2 to 0.7.11-2)
  • Migration status for rust-geo-types/armhf (0.7.11-2 to 0.7.11-2): Will attempt migration (Any information below is purely informational)
• rust-geo-types/mips64el (0.7.11-2 to 0.7.11-2)
  • Migration status for rust-geo-types/mips64el (0.7.11-2 to 0.7.11-2): Will attempt migration (Any information below is purely informational)
• rust-getopts/armel (0.2.21-4 to 0.2.21-4)
  • Migration status for rust-getopts/armel (0.2.21-4 to 0.2.21-4): Will attempt migration (Any information below is purely informational)
• rust-getopts/armhf (0.2.21-4 to 0.2.21-4)
  • Migration status for rust-getopts/armhf (0.2.21-4 to 0.2.21-4): Will attempt migration (Any information below is purely informational)
• rust-getopts/mips64el (0.2.21-4 to 0.2.21-4)
  • Migration status for rust-getopts/mips64el (0.2.21-4 to 0.2.21-4): Will attempt migration (Any information below is purely informational)
• rust-getopts/s390x (0.2.21-4 to 0.2.21-4)
  • Migration status for rust-getopts/s390x (0.2.21-4 to 0.2.21-4): Will attempt migration (Any information below is purely informational)
• rust-gettext-rs/arm64 (0.7.0-3 to 0.7.0-3)
  • Migration status for rust-gettext-rs/arm64 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
• rust-gettext-rs/armel (0.7.0-3 to 0.7.0-3)
  • Migration status for rust-gettext-rs/armel (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
• rust-gettext-rs/i386 (0.7.0-3 to 0.7.0-3)
  • Migration status for rust-gettext-rs/i386 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
• rust-ghash/arm64 (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-ghash/arm64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-ghash/armhf (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-ghash/armhf (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-ghash/mips64el (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-ghash/mips64el (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-ghash/s390x (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-ghash/s390x (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-ghost/armel (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-ghost/armel (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-ghost/armhf (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-ghost/armhf (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-gl-generator/mips64el (0.14.0-1 to 0.14.0-1)
  • Migration status for rust-gl-generator/mips64el (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• rust-gl-generator/s390x (0.14.0-1 to 0.14.0-1)
  • Migration status for rust-gl-generator/s390x (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• rust-glib-build-tools/armel (0.20.0-1 to 0.20.0-1)
  • Migration status for rust-glib-build-tools/armel (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
• rust-glib-build-tools/armhf (0.20.0-1 to 0.20.0-1)
  • Migration status for rust-glib-build-tools/armhf (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
• rust-glib-build-tools/i386 (0.20.0-1 to 0.20.0-1)
  • Migration status for rust-glib-build-tools/i386 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
• rust-glib-build-tools/mips64el (0.20.0-1 to 0.20.0-1)
  • Migration status for rust-glib-build-tools/mips64el (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
• rust-goldenfile/armhf (1.5.2-1 to 1.5.2-1)
  • Migration status for rust-goldenfile/armhf (1.5.2-1 to 1.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-goldenfile/mips64el (1.5.2-1 to 1.5.2-1)
  • Migration status for rust-goldenfile/mips64el (1.5.2-1 to 1.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-gtk-rs-lgpl-docs/amd64 (0.1.12-2 to 0.1.12-2)
  • Migration status for rust-gtk-rs-lgpl-docs/amd64 (0.1.12-2 to 0.1.12-2): Will attempt migration (Any information below is purely informational)
• rust-gtk-rs-lgpl-docs/arm64 (0.1.12-2 to 0.1.12-2)
  • Migration status for rust-gtk-rs-lgpl-docs/arm64 (0.1.12-2 to 0.1.12-2): Will attempt migration (Any information below is purely informational)
• rust-gtk-rs-lgpl-docs/armel (0.1.12-2 to 0.1.12-2)
  • Migration status for rust-gtk-rs-lgpl-docs/armel (0.1.12-2 to 0.1.12-2): Will attempt migration (Any information below is purely informational)
• rust-gtk-rs-lgpl-docs/i386 (0.1.12-2 to 0.1.12-2)
  • Migration status for rust-gtk-rs-lgpl-docs/i386 (0.1.12-2 to 0.1.12-2): Will attempt migration (Any information below is purely informational)
• rust-gzip-header/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-gzip-header/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-gzip-header/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-gzip-header/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-gzip-header/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-gzip-header/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-hash32/amd64 (0.3.1-2 to 0.3.1-2)
  • Migration status for rust-hash32/amd64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• rust-hash32/armhf (0.3.1-2 to 0.3.1-2)
  • Migration status for rust-hash32/armhf (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• rust-hash32/ppc64el (0.3.1-2 to 0.3.1-2)
  • Migration status for rust-hash32/ppc64el (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• rust-heapsize/arm64 (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-heapsize/arm64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-heapsize/armhf (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-heapsize/armhf (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-heapsize/mips64el (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-heapsize/mips64el (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-heck/armhf (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-heck/armhf (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-heck/s390x (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-heck/s390x (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-hex-literal/amd64 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-hex-literal/amd64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-hex-literal/armhf (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-hex-literal/armhf (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-hex-literal/mips64el (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-hex-literal/mips64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-hexf-parse/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-hexf-parse/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-hexf-parse/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-hexf-parse/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-hexf-parse/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-hexf-parse/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-hexf-parse/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-hexf-parse/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-hexf-parse/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-hexf-parse/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-hidapi-sys/arm64 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-hidapi-sys/arm64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-hidapi-sys/armel (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-hidapi-sys/armel (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-hidapi-sys/armhf (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-hidapi-sys/armhf (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-hidapi-sys/i386 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-hidapi-sys/i386 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-hidapi-sys/mips64el (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-hidapi-sys/mips64el (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-hidapi-sys/s390x (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-hidapi-sys/s390x (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-hprof/armel (0.1.3-2 to 0.1.3-2)
  • Migration status for rust-hprof/armel (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• rust-hprof/armhf (0.1.3-2 to 0.1.3-2)
  • Migration status for rust-hprof/armhf (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• rust-hprof/mips64el (0.1.3-2 to 0.1.3-2)
  • Migration status for rust-hprof/mips64el (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• rust-http-body-0.4/arm64 (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-http-body-0.4/arm64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-http-body-0.4/armel (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-http-body-0.4/armel (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-http-body-0.4/armhf (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-http-body-0.4/armhf (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-http-body-0.4/mips64el (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-http-body-0.4/mips64el (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-http-body-0.4/s390x (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-http-body-0.4/s390x (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-httparse/arm64 (1.8.0-1 to 1.8.0-1)
  • Migration status for rust-httparse/arm64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-httparse/i386 (1.8.0-1 to 1.8.0-1)
  • Migration status for rust-httparse/i386 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-httparse/mips64el (1.8.0-1 to 1.8.0-1)
  • Migration status for rust-httparse/mips64el (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-human-format/arm64 (1.0.3-1 to 1.0.3-1)
  • Migration status for rust-human-format/arm64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-human-format/ppc64el (1.0.3-1 to 1.0.3-1)
  • Migration status for rust-human-format/ppc64el (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-human-format/s390x (1.0.3-1 to 1.0.3-1)
  • Migration status for rust-human-format/s390x (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-humantime-serde/arm64 (1.1.1-1 to 1.1.1-1)
  • Migration status for rust-humantime-serde/arm64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-humantime-serde/s390x (1.1.1-1 to 1.1.1-1)
  • Migration status for rust-humantime-serde/s390x (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-hyphenation-commons/amd64 (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-hyphenation-commons/amd64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-hyphenation-commons/arm64 (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-hyphenation-commons/arm64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-hyphenation-commons/armel (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-hyphenation-commons/armel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-hyphenation/armhf (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-hyphenation/armhf (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-hyphenation/mips64el (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-hyphenation/mips64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-iai/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-iai/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-iai/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-iai/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-iai/i386 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-iai/i386 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-iai/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-iai/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-if-chain/amd64 (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-if-chain/amd64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-if-chain/arm64 (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-if-chain/arm64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-if-chain/armel (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-if-chain/armel (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-if-chain/armhf (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-if-chain/armhf (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-if-chain/i386 (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-if-chain/i386 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-if-chain/mips64el (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-if-chain/mips64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-impls/armhf (1.0.3-1 to 1.0.3-1)
  • Migration status for rust-impls/armhf (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-impls/i386 (1.0.3-1 to 1.0.3-1)
  • Migration status for rust-impls/i386 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-include-dir-macros/amd64 (0.7.3-1 to 0.7.3-1)
  • Migration status for rust-include-dir-macros/amd64 (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• rust-include-dir-macros/armel (0.7.3-1 to 0.7.3-1)
  • Migration status for rust-include-dir-macros/armel (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• rust-include-dir-macros/armhf (0.7.3-1 to 0.7.3-1)
  • Migration status for rust-include-dir-macros/armhf (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• rust-include-dir-macros/s390x (0.7.3-1 to 0.7.3-1)
  • Migration status for rust-include-dir-macros/s390x (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• rust-include-dir/armel (0.7.3-1 to 0.7.3-1)
  • Migration status for rust-include-dir/armel (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• rust-include-dir/armhf (0.7.3-1 to 0.7.3-1)
  • Migration status for rust-include-dir/armhf (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• rust-indenter/arm64 (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-indenter/arm64 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-indenter/armhf (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-indenter/armhf (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-indenter/mips64el (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-indenter/mips64el (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-inotify/amd64 (0.9.6-1 to 0.9.6-1)
  • Migration status for rust-inotify/amd64 (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• rust-inotify/arm64 (0.9.6-1 to 0.9.6-1)
  • Migration status for rust-inotify/arm64 (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• rust-inotify/armhf (0.9.6-1 to 0.9.6-1)
  • Migration status for rust-inotify/armhf (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• rust-inotify/i386 (0.9.6-1 to 0.9.6-1)
  • Migration status for rust-inotify/i386 (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• rust-inotify/s390x (0.9.6-1 to 0.9.6-1)
  • Migration status for rust-inotify/s390x (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• rust-inplace-vec-builder/armhf (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-inplace-vec-builder/armhf (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-inplace-vec-builder/i386 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-inplace-vec-builder/i386 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-inplace-vec-builder/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-inplace-vec-builder/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-inplace-vec-builder/s390x (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-inplace-vec-builder/s390x (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-input-event-codes/amd64 (6.2.0-1 to 6.2.0-1)
  • Migration status for rust-input-event-codes/amd64 (6.2.0-1 to 6.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-input-event-codes/s390x (6.2.0-1 to 6.2.0-1)
  • Migration status for rust-input-event-codes/s390x (6.2.0-1 to 6.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-interpolate-name/armhf (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-interpolate-name/armhf (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-intervaltree/arm64 (0.2.7-1 to 0.2.7-1)
  • Migration status for rust-intervaltree/arm64 (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• rust-intervaltree/i386 (0.2.7-1 to 0.2.7-1)
  • Migration status for rust-intervaltree/i386 (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• rust-intervaltree/mips64el (0.2.7-1 to 0.2.7-1)
  • Migration status for rust-intervaltree/mips64el (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• rust-intervaltree/ppc64el (0.2.7-1 to 0.2.7-1)
  • Migration status for rust-intervaltree/ppc64el (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• rust-intervaltree/s390x (0.2.7-1 to 0.2.7-1)
  • Migration status for rust-intervaltree/s390x (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• rust-intl-pluralrules/arm64 (7.0.2-1 to 7.0.2-1)
  • Migration status for rust-intl-pluralrules/arm64 (7.0.2-1 to 7.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-intl-pluralrules/armhf (7.0.2-1 to 7.0.2-1)
  • Migration status for rust-intl-pluralrules/armhf (7.0.2-1 to 7.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-intl-pluralrules/i386 (7.0.2-1 to 7.0.2-1)
  • Migration status for rust-intl-pluralrules/i386 (7.0.2-1 to 7.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-intl-pluralrules/mips64el (7.0.2-1 to 7.0.2-1)
  • Migration status for rust-intl-pluralrules/mips64el (7.0.2-1 to 7.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-intl-pluralrules/s390x (7.0.2-1 to 7.0.2-1)
  • Migration status for rust-intl-pluralrules/s390x (7.0.2-1 to 7.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-ipconfig/arm64 (0.2.2-3 to 0.2.2-3)
  • Migration status for rust-ipconfig/arm64 (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• rust-ipconfig/armhf (0.2.2-3 to 0.2.2-3)
  • Migration status for rust-ipconfig/armhf (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• rust-ipconfig/s390x (0.2.2-3 to 0.2.2-3)
  • Migration status for rust-ipconfig/s390x (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• rust-iri-string/arm64 (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-iri-string/arm64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-iri-string/armhf (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-iri-string/armhf (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-iri-string/i386 (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-iri-string/i386 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-iri-string/mips64el (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-iri-string/mips64el (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-iri-string/s390x (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-iri-string/s390x (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-is-executable/amd64 (1.0.1-3 to 1.0.1-3)
  • Migration status for rust-is-executable/amd64 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• rust-is-executable/armhf (1.0.1-3 to 1.0.1-3)
  • Migration status for rust-is-executable/armhf (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• rust-is-match/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-is-match/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-is-match/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-is-match/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-is-match/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-is-match/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-joinery/arm64 (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-joinery/arm64 (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-joinery/armel (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-joinery/armel (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-joinery/armhf (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-joinery/armhf (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-joinery/mips64el (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-joinery/mips64el (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-joinery/s390x (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-joinery/s390x (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-jpeg-decoder/amd64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-jpeg-decoder/amd64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-jpeg-decoder/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-jpeg-decoder/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-jpeg-decoder/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-jpeg-decoder/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-jpeg-decoder/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-jpeg-decoder/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-jpeg-decoder/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-jpeg-decoder/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-js-int/armel (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-js-int/armel (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-js-int/armhf (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-js-int/armhf (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-js-int/mips64el (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-js-int/mips64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-js-int/s390x (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-js-int/s390x (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-js-sys/mips64el (0.3.64-1 to 0.3.64-1)
  • Migration status for rust-js-sys/mips64el (0.3.64-1 to 0.3.64-1): Will attempt migration (Any information below is purely informational)
• rust-js-sys/s390x (0.3.64-1 to 0.3.64-1)
  • Migration status for rust-js-sys/s390x (0.3.64-1 to 0.3.64-1): Will attempt migration (Any information below is purely informational)
• rust-kdl/arm64 (4.6.0-1 to 4.6.0-1)
  • Migration status for rust-kdl/arm64 (4.6.0-1 to 4.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-kdl/armhf (4.6.0-1 to 4.6.0-1)
  • Migration status for rust-kdl/armhf (4.6.0-1 to 4.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-kdl/ppc64el (4.6.0-1 to 4.6.0-1)
  • Migration status for rust-kdl/ppc64el (4.6.0-1 to 4.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-la-arena/arm64 (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-la-arena/arm64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-la-arena/mips64el (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-la-arena/mips64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-la-arena/s390x (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-la-arena/s390x (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-lab/arm64 (0.11.0-1 to 0.11.0-1)
  • Migration status for rust-lab/arm64 (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
• rust-lab/armhf (0.11.0-1 to 0.11.0-1)
  • Migration status for rust-lab/armhf (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
• rust-lab/mips64el (0.11.0-1 to 0.11.0-1)
  • Migration status for rust-lab/mips64el (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
• rust-language-tags/arm64 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-language-tags/arm64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-language-tags/armel (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-language-tags/armel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-language-tags/armhf (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-language-tags/armhf (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-language-tags/i386 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-language-tags/i386 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-language-tags/mips64el (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-language-tags/mips64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-language-tags/s390x (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-language-tags/s390x (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-lev-distance/i386 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-lev-distance/i386 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-lev-distance/s390x (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-lev-distance/s390x (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-lewton/amd64 (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-lewton/amd64 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-lewton/arm64 (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-lewton/arm64 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-lewton/armel (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-lewton/armel (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-lexical-core/amd64 (0.7.6-2 to 0.7.6-2)
  • Migration status for rust-lexical-core/amd64 (0.7.6-2 to 0.7.6-2): Will attempt migration (Any information below is purely informational)
• rust-lexical-core/i386 (0.7.6-2 to 0.7.6-2)
  • Migration status for rust-lexical-core/i386 (0.7.6-2 to 0.7.6-2): Will attempt migration (Any information below is purely informational)
• rust-lexical-core/mips64el (0.7.6-2 to 0.7.6-2)
  • Migration status for rust-lexical-core/mips64el (0.7.6-2 to 0.7.6-2): Will attempt migration (Any information below is purely informational)
• rust-lexical-parse-float/arm64 (0.8.5-1 to 0.8.5-1)
  • Migration status for rust-lexical-parse-float/arm64 (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• rust-lexical-parse-float/armhf (0.8.5-1 to 0.8.5-1)
  • Migration status for rust-lexical-parse-float/armhf (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• rust-lexical-parse-float/mips64el (0.8.5-1 to 0.8.5-1)
  • Migration status for rust-lexical-parse-float/mips64el (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• rust-lexical-parse-float/ppc64el (0.8.5-1 to 0.8.5-1)
  • Migration status for rust-lexical-parse-float/ppc64el (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• rust-lexiclean/arm64 (0.0.1-1 to 0.0.1-1)
  • Migration status for rust-lexiclean/arm64 (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-lexiclean/armel (0.0.1-1 to 0.0.1-1)
  • Migration status for rust-lexiclean/armel (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-lexiclean/mips64el (0.0.1-1 to 0.0.1-1)
  • Migration status for rust-lexiclean/mips64el (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-lexiclean/ppc64el (0.0.1-1 to 0.0.1-1)
  • Migration status for rust-lexiclean/ppc64el (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-lexiclean/s390x (0.0.1-1 to 0.0.1-1)
  • Migration status for rust-lexiclean/s390x (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-libc-print/amd64 (0.1.20-1 to 0.1.20-1)
  • Migration status for rust-libc-print/amd64 (0.1.20-1 to 0.1.20-1): Will attempt migration (Any information below is purely informational)
• rust-libc-print/arm64 (0.1.20-1 to 0.1.20-1)
  • Migration status for rust-libc-print/arm64 (0.1.20-1 to 0.1.20-1): Will attempt migration (Any information below is purely informational)
• rust-libc-print/armel (0.1.20-1 to 0.1.20-1)
  • Migration status for rust-libc-print/armel (0.1.20-1 to 0.1.20-1): Will attempt migration (Any information below is purely informational)
• rust-libc-print/armhf (0.1.20-1 to 0.1.20-1)
  • Migration status for rust-libc-print/armhf (0.1.20-1 to 0.1.20-1): Will attempt migration (Any information below is purely informational)
• rust-libc-print/s390x (0.1.20-1 to 0.1.20-1)
  • Migration status for rust-libc-print/s390x (0.1.20-1 to 0.1.20-1): Will attempt migration (Any information below is purely informational)
• rust-libflate/arm64 (0.1.25-1 to 0.1.25-1)
  • Migration status for rust-libflate/arm64 (0.1.25-1 to 0.1.25-1): Will attempt migration (Any information below is purely informational)
• rust-libflate/armhf (0.1.25-1 to 0.1.25-1)
  • Migration status for rust-libflate/armhf (0.1.25-1 to 0.1.25-1): Will attempt migration (Any information below is purely informational)
• rust-libflate/mips64el (0.1.25-1 to 0.1.25-1)
  • Migration status for rust-libflate/mips64el (0.1.25-1 to 0.1.25-1): Will attempt migration (Any information below is purely informational)
• rust-libflate/s390x (0.1.25-1 to 0.1.25-1)
  • Migration status for rust-libflate/s390x (0.1.25-1 to 0.1.25-1): Will attempt migration (Any information below is purely informational)
• rust-liblzma/arm64 (0.3.4-1 to 0.3.4-1)
  • Migration status for rust-liblzma/arm64 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
• rust-libnghttp2-sys/armhf (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-libnghttp2-sys/armhf (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-libnghttp2-sys/i386 (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-libnghttp2-sys/i386 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-libnghttp2-sys/s390x (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-libnghttp2-sys/s390x (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-glib-binding/amd64 (2.28.1-1 to 2.28.1-1)
  • Migration status for rust-libpulse-glib-binding/amd64 (2.28.1-1 to 2.28.1-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-glib-binding/arm64 (2.28.1-1 to 2.28.1-1)
  • Migration status for rust-libpulse-glib-binding/arm64 (2.28.1-1 to 2.28.1-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-glib-binding/armhf (2.28.1-1 to 2.28.1-1)
  • Migration status for rust-libpulse-glib-binding/armhf (2.28.1-1 to 2.28.1-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-glib-binding/mips64el (2.28.1-1 to 2.28.1-1)
  • Migration status for rust-libpulse-glib-binding/mips64el (2.28.1-1 to 2.28.1-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-glib-binding/s390x (2.28.1-1 to 2.28.1-1)
  • Migration status for rust-libpulse-glib-binding/s390x (2.28.1-1 to 2.28.1-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-sys/arm64 (1.21.0-1 to 1.21.0-1)
  • Migration status for rust-libpulse-sys/arm64 (1.21.0-1 to 1.21.0-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-sys/armhf (1.21.0-1 to 1.21.0-1)
  • Migration status for rust-libpulse-sys/armhf (1.21.0-1 to 1.21.0-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-sys/mips64el (1.21.0-1 to 1.21.0-1)
  • Migration status for rust-libpulse-sys/mips64el (1.21.0-1 to 1.21.0-1): Will attempt migration (Any information below is purely informational)
• rust-libpulse-sys/s390x (1.21.0-1 to 1.21.0-1)
  • Migration status for rust-libpulse-sys/s390x (1.21.0-1 to 1.21.0-1): Will attempt migration (Any information below is purely informational)
• rust-libraw-rs/arm64 (0.0.4-1 to 0.0.4-1)
  • Migration status for rust-libraw-rs/arm64 (0.0.4-1 to 0.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-libraw-rs/armhf (0.0.4-1 to 0.0.4-1)
  • Migration status for rust-libraw-rs/armhf (0.0.4-1 to 0.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-libraw-rs/mips64el (0.0.4-1 to 0.0.4-1)
  • Migration status for rust-libraw-rs/mips64el (0.0.4-1 to 0.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-libraw-rs/s390x (0.0.4-1 to 0.0.4-1)
  • Migration status for rust-libraw-rs/s390x (0.0.4-1 to 0.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-libssh2-sys/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-libssh2-sys/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-libssh2-sys/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-libssh2-sys/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-libssh2-sys/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-libssh2-sys/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-libssh2-sys/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-libssh2-sys/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-libssh2-sys/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-libssh2-sys/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-libudev-sys/arm64 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-libudev-sys/arm64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-libudev-sys/armel (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-libudev-sys/armel (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-libudev-sys/armhf (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-libudev-sys/armhf (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-libudev-sys/s390x (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-libudev-sys/s390x (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-libudev/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-libudev/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-libudev/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-libudev/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-lifeguard/armhf (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-lifeguard/armhf (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-lifeguard/i386 (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-lifeguard/i386 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-lifeguard/mips64el (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-lifeguard/mips64el (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-lifeguard/s390x (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-lifeguard/s390x (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-line-numbers/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-line-numbers/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-line-numbers/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-line-numbers/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-line-numbers/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-line-numbers/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-line-numbers/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-line-numbers/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-linear-map/amd64 (1.2.0-2 to 1.2.0-2)
  • Migration status for rust-linear-map/amd64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-linear-map/arm64 (1.2.0-2 to 1.2.0-2)
  • Migration status for rust-linear-map/arm64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-linear-map/s390x (1.2.0-2 to 1.2.0-2)
  • Migration status for rust-linear-map/s390x (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-linked-hash-map/armhf (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-linked-hash-map/armhf (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-linked-hash-map/mips64el (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-linked-hash-map/mips64el (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-linkify/armel (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-linkify/armel (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-linkify/mips64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-linkify/mips64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-linkify/ppc64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-linkify/ppc64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-linux-keyutils/armhf (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-linux-keyutils/armhf (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-linux-keyutils/s390x (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-linux-keyutils/s390x (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-litrs/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-litrs/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-litrs/armel (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-litrs/armel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-litrs/armhf (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-litrs/armhf (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-litrs/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-litrs/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-litrs/s390x (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-litrs/s390x (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-locale-config/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-locale-config/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-locale-config/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-locale-config/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-locale-config/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-locale-config/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-lockfree-object-pool/armhf (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-lockfree-object-pool/armhf (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-lockfree-object-pool/i386 (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-lockfree-object-pool/i386 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-lockfree-object-pool/ppc64el (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-lockfree-object-pool/ppc64el (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-log-mdc/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-log-mdc/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-log-mdc/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-log-mdc/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-log-mdc/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-log-mdc/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-log-mdc/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-log-mdc/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-log-mdc/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-log-mdc/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-log-reroute/amd64 (0.1.8-1 to 0.1.8-1)
  • Migration status for rust-log-reroute/amd64 (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
• rust-log-reroute/armhf (0.1.8-1 to 0.1.8-1)
  • Migration status for rust-log-reroute/armhf (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
• rust-log-reroute/mips64el (0.1.8-1 to 0.1.8-1)
  • Migration status for rust-log-reroute/mips64el (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
• rust-log-reroute/s390x (0.1.8-1 to 0.1.8-1)
  • Migration status for rust-log-reroute/s390x (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
• rust-loggerv/armel (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-loggerv/armel (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-loggerv/armhf (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-loggerv/armhf (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-loggerv/i386 (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-loggerv/i386 (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-loggerv/mips64el (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-loggerv/mips64el (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-logos/amd64 (0.14.0-1 to 0.14.0-1)
  • Migration status for rust-logos/amd64 (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• rust-logos/armel (0.14.0-1 to 0.14.0-1)
  • Migration status for rust-logos/armel (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• rust-logos/armhf (0.14.0-1 to 0.14.0-1)
  • Migration status for rust-logos/armhf (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• rust-logos/i386 (0.14.0-1 to 0.14.0-1)
  • Migration status for rust-logos/i386 (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• rust-logos/mips64el (0.14.0-1 to 0.14.0-1)
  • Migration status for rust-logos/mips64el (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• rust-lru-cache/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-lru-cache/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-lru-cache/armel (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-lru-cache/armel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-lru-cache/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-lru-cache/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-lru-cache/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-lru-cache/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-lsp-server/arm64 (0.7.4-1 to 0.7.4-1)
  • Migration status for rust-lsp-server/arm64 (0.7.4-1 to 0.7.4-1): Will attempt migration (Any information below is purely informational)
• rust-lsp-server/armhf (0.7.4-1 to 0.7.4-1)
  • Migration status for rust-lsp-server/armhf (0.7.4-1 to 0.7.4-1): Will attempt migration (Any information below is purely informational)
• rust-lsp-server/s390x (0.7.4-1 to 0.7.4-1)
  • Migration status for rust-lsp-server/s390x (0.7.4-1 to 0.7.4-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-core-derive/arm64 (2.1.1-1 to 2.1.1-1)
  • Migration status for rust-lv2-core-derive/arm64 (2.1.1-1 to 2.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-core-derive/armel (2.1.1-1 to 2.1.1-1)
  • Migration status for rust-lv2-core-derive/armel (2.1.1-1 to 2.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-core-derive/armhf (2.1.1-1 to 2.1.1-1)
  • Migration status for rust-lv2-core-derive/armhf (2.1.1-1 to 2.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-core-derive/mips64el (2.1.1-1 to 2.1.1-1)
  • Migration status for rust-lv2-core-derive/mips64el (2.1.1-1 to 2.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-core/arm64 (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-lv2-core/arm64 (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-core/armel (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-lv2-core/armel (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-core/armhf (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-lv2-core/armhf (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-midi/armhf (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-lv2-midi/armhf (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-lv2-units/arm64 (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-lv2-units/arm64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-lzw/arm64 (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-lzw/arm64 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-lzw/armel (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-lzw/armel (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-lzw/mips64el (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-lzw/mips64el (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-lzw/s390x (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-lzw/s390x (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-mac/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-mac/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-mac/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-mac/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-mac/armhf (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-mac/armhf (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-mac/s390x (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-mac/s390x (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-macro-attr/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-macro-attr/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-macro-attr/armhf (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-macro-attr/armhf (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-macro-attr/s390x (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-macro-attr/s390x (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-maplit/arm64 (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-maplit/arm64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-maplit/ppc64el (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-maplit/ppc64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-markup-proc-macro/arm64 (0.13.1-1 to 0.13.1-1)
  • Migration status for rust-markup-proc-macro/arm64 (0.13.1-1 to 0.13.1-1): Will attempt migration (Any information below is purely informational)
• rust-markup-proc-macro/armel (0.13.1-1 to 0.13.1-1)
  • Migration status for rust-markup-proc-macro/armel (0.13.1-1 to 0.13.1-1): Will attempt migration (Any information below is purely informational)
• rust-markup-proc-macro/i386 (0.13.1-1 to 0.13.1-1)
  • Migration status for rust-markup-proc-macro/i386 (0.13.1-1 to 0.13.1-1): Will attempt migration (Any information below is purely informational)
• rust-matches/arm64 (0.1.8-1 to 0.1.8-1)
  • Migration status for rust-matches/arm64 (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
• rust-matches/mips64el (0.1.8-1 to 0.1.8-1)
  • Migration status for rust-matches/mips64el (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
• rust-matches/ppc64el (0.1.8-1 to 0.1.8-1)
  • Migration status for rust-matches/ppc64el (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
• rust-matches/s390x (0.1.8-1 to 0.1.8-1)
  • Migration status for rust-matches/s390x (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
• rust-matchit/arm64 (0.7.3-2 to 0.7.3-2)
  • Migration status for rust-matchit/arm64 (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• rust-matchit/armel (0.7.3-2 to 0.7.3-2)
  • Migration status for rust-matchit/armel (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• rust-matchit/i386 (0.7.3-2 to 0.7.3-2)
  • Migration status for rust-matchit/i386 (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• rust-mbox/arm64 (0.6.0-2 to 0.6.0-2)
  • Migration status for rust-mbox/arm64 (0.6.0-2 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
• rust-mbox/s390x (0.6.0-2 to 0.6.0-2)
  • Migration status for rust-mbox/s390x (0.6.0-2 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
• rust-memmap/amd64 (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-memmap/amd64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-memmap/arm64 (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-memmap/arm64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-memmap/armhf (0.7.0-1 to 0.7.0-1)
  • Migration status for rust-memmap/armhf (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• rust-memo-map/mips64el (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-memo-map/mips64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-merlin/amd64 (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-merlin/amd64 (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-merlin/armel (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-merlin/armel (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-merlin/i386 (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-merlin/i386 (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-mime-guess/arm64 (2.0.4-2 to 2.0.4-2)
  • Migration status for rust-mime-guess/arm64 (2.0.4-2 to 2.0.4-2): Will attempt migration (Any information below is purely informational)
• rust-mime-guess/armel (2.0.4-2 to 2.0.4-2)
  • Migration status for rust-mime-guess/armel (2.0.4-2 to 2.0.4-2): Will attempt migration (Any information below is purely informational)
• rust-mime-guess/armhf (2.0.4-2 to 2.0.4-2)
  • Migration status for rust-mime-guess/armhf (2.0.4-2 to 2.0.4-2): Will attempt migration (Any information below is purely informational)
• rust-mime-guess/s390x (2.0.4-2 to 2.0.4-2)
  • Migration status for rust-mime-guess/s390x (2.0.4-2 to 2.0.4-2): Will attempt migration (Any information below is purely informational)
• rust-minimal-lexical/armel (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-minimal-lexical/armel (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-minimal-lexical/armhf (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-minimal-lexical/armhf (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-minimal-lexical/mips64el (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-minimal-lexical/mips64el (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-minimal-lexical/s390x (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-minimal-lexical/s390x (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-mio-uds/arm64 (0.6.7-1 to 0.6.7-1)
  • Migration status for rust-mio-uds/arm64 (0.6.7-1 to 0.6.7-1): Will attempt migration (Any information below is purely informational)
• rust-mio-uds/armel (0.6.7-1 to 0.6.7-1)
  • Migration status for rust-mio-uds/armel (0.6.7-1 to 0.6.7-1): Will attempt migration (Any information below is purely informational)
• rust-mio-uds/armhf (0.6.7-1 to 0.6.7-1)
  • Migration status for rust-mio-uds/armhf (0.6.7-1 to 0.6.7-1): Will attempt migration (Any information below is purely informational)
• rust-mio-uds/s390x (0.6.7-1 to 0.6.7-1)
  • Migration status for rust-mio-uds/s390x (0.6.7-1 to 0.6.7-1): Will attempt migration (Any information below is purely informational)
• rust-miow/amd64 (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-miow/amd64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-miow/arm64 (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-miow/arm64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-miow/armhf (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-miow/armhf (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-miow/i386 (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-miow/i386 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-miow/mips64el (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-miow/mips64el (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-miow/ppc64el (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-miow/ppc64el (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-mockall-double/arm64 (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-mockall-double/arm64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-mockall-double/armel (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-mockall-double/armel (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-mockall-double/armhf (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-mockall-double/armhf (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-mockall-double/mips64el (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-mockall-double/mips64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-muldiv/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for rust-muldiv/arm64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• rust-muldiv/armel (1.0.1-2 to 1.0.1-2)
  • Migration status for rust-muldiv/armel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• rust-muldiv/mips64el (1.0.1-2 to 1.0.1-2)
  • Migration status for rust-muldiv/mips64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• rust-muldiv/s390x (1.0.1-2 to 1.0.1-2)
  • Migration status for rust-muldiv/s390x (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• rust-multihash-codetable/amd64 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-multihash-codetable/amd64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-multihash-codetable/arm64 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-multihash-codetable/arm64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-multihash-codetable/armhf (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-multihash-codetable/armhf (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-multihash-codetable/mips64el (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-multihash-codetable/mips64el (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-multihash-codetable/ppc64el (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-multihash-codetable/ppc64el (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-multihash-codetable/s390x (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-multihash-codetable/s390x (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-multihash-derive/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-multihash-derive/arm64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-multihash-derive/mips64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-multihash-derive/mips64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-multihash/amd64 (0.19.1-2 to 0.19.1-2)
  • Migration status for rust-multihash/amd64 (0.19.1-2 to 0.19.1-2): Will attempt migration (Any information below is purely informational)
• rust-multihash/arm64 (0.19.1-2 to 0.19.1-2)
  • Migration status for rust-multihash/arm64 (0.19.1-2 to 0.19.1-2): Will attempt migration (Any information below is purely informational)
• rust-multihash/armel (0.19.1-2 to 0.19.1-2)
  • Migration status for rust-multihash/armel (0.19.1-2 to 0.19.1-2): Will attempt migration (Any information below is purely informational)
• rust-multihash/armhf (0.19.1-2 to 0.19.1-2)
  • Migration status for rust-multihash/armhf (0.19.1-2 to 0.19.1-2): Will attempt migration (Any information below is purely informational)
• rust-multihash/i386 (0.19.1-2 to 0.19.1-2)
  • Migration status for rust-multihash/i386 (0.19.1-2 to 0.19.1-2): Will attempt migration (Any information below is purely informational)
• rust-multihash/mips64el (0.19.1-2 to 0.19.1-2)
  • Migration status for rust-multihash/mips64el (0.19.1-2 to 0.19.1-2): Will attempt migration (Any information below is purely informational)
• rust-multihash/s390x (0.19.1-2 to 0.19.1-2)
  • Migration status for rust-multihash/s390x (0.19.1-2 to 0.19.1-2): Will attempt migration (Any information below is purely informational)
• rust-mutants/armhf (0.0.3-1 to 0.0.3-1)
  • Migration status for rust-mutants/armhf (0.0.3-1 to 0.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-mutants/ppc64el (0.0.3-1 to 0.0.3-1)
  • Migration status for rust-mutants/ppc64el (0.0.3-1 to 0.0.3-1): Will attempt migration (Any information below is purely informational)
• rust-mutate-once/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-mutate-once/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-mutate-once/armhf (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-mutate-once/armhf (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-mutate-once/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-mutate-once/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-mutate-once/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-mutate-once/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-netlink-packet-audit/armel (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-netlink-packet-audit/armel (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-netlink-packet-audit/armhf (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-netlink-packet-audit/armhf (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-netlink-packet-audit/mips64el (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-netlink-packet-audit/mips64el (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-netlink-packet-audit/ppc64el (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-netlink-packet-audit/ppc64el (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-nettle/arm64 (7.3.0-1 to 7.3.0-1)
  • Migration status for rust-nettle/arm64 (7.3.0-1 to 7.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-nettle/armel (7.3.0-1 to 7.3.0-1)
  • Migration status for rust-nettle/armel (7.3.0-1 to 7.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-nettle/armhf (7.3.0-1 to 7.3.0-1)
  • Migration status for rust-nettle/armhf (7.3.0-1 to 7.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-nettle/mips64el (7.3.0-1 to 7.3.0-1)
  • Migration status for rust-nettle/mips64el (7.3.0-1 to 7.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-new-debug-unreachable/armhf (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-new-debug-unreachable/armhf (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-new-debug-unreachable/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-new-debug-unreachable/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-new-debug-unreachable/ppc64el (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-new-debug-unreachable/ppc64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-nibble-vec/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-nibble-vec/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-nibble-vec/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-nibble-vec/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-niffler/mips64el (2.6.0-1 to 2.6.0-1)
  • Migration status for rust-niffler/mips64el (2.6.0-1 to 2.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-nodrop/amd64 (0.1.13-1 to 0.1.13-1)
  • Migration status for rust-nodrop/amd64 (0.1.13-1 to 0.1.13-1): Will attempt migration (Any information below is purely informational)
• rust-nodrop/arm64 (0.1.13-1 to 0.1.13-1)
  • Migration status for rust-nodrop/arm64 (0.1.13-1 to 0.1.13-1): Will attempt migration (Any information below is purely informational)
• rust-nodrop/armel (0.1.13-1 to 0.1.13-1)
  • Migration status for rust-nodrop/armel (0.1.13-1 to 0.1.13-1): Will attempt migration (Any information below is purely informational)
• rust-nodrop/mips64el (0.1.13-1 to 0.1.13-1)
  • Migration status for rust-nodrop/mips64el (0.1.13-1 to 0.1.13-1): Will attempt migration (Any information below is purely informational)
• rust-nom-derive-impl/armel (0.10.0-3 to 0.10.0-3)
  • Migration status for rust-nom-derive-impl/armel (0.10.0-3 to 0.10.0-3): Will attempt migration (Any information below is purely informational)
• rust-nom-derive-impl/armhf (0.10.0-3 to 0.10.0-3)
  • Migration status for rust-nom-derive-impl/armhf (0.10.0-3 to 0.10.0-3): Will attempt migration (Any information below is purely informational)
• rust-nom-derive-impl/i386 (0.10.0-3 to 0.10.0-3)
  • Migration status for rust-nom-derive-impl/i386 (0.10.0-3 to 0.10.0-3): Will attempt migration (Any information below is purely informational)
• rust-nom-derive-impl/ppc64el (0.10.0-3 to 0.10.0-3)
  • Migration status for rust-nom-derive-impl/ppc64el (0.10.0-3 to 0.10.0-3): Will attempt migration (Any information below is purely informational)
• rust-nom-derive-impl/s390x (0.10.0-3 to 0.10.0-3)
  • Migration status for rust-nom-derive-impl/s390x (0.10.0-3 to 0.10.0-3): Will attempt migration (Any information below is purely informational)
• rust-nom/arm64 (7.1.3-1 to 7.1.3-1)
  • Migration status for rust-nom/arm64 (7.1.3-1 to 7.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-nom/armel (7.1.3-1 to 7.1.3-1)
  • Migration status for rust-nom/armel (7.1.3-1 to 7.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-nom/armhf (7.1.3-1 to 7.1.3-1)
  • Migration status for rust-nom/armhf (7.1.3-1 to 7.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-nom/i386 (7.1.3-1 to 7.1.3-1)
  • Migration status for rust-nom/i386 (7.1.3-1 to 7.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-nom/ppc64el (7.1.3-1 to 7.1.3-1)
  • Migration status for rust-nom/ppc64el (7.1.3-1 to 7.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-nomcup/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-nomcup/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-nomcup/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-nomcup/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-nomcup/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-nomcup/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-nomcup/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-nomcup/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-nomcup/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-nomcup/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-nomcup/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-nomcup/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-normpath/armel (1.1.1-1 to 1.1.1-1)
  • Migration status for rust-normpath/armel (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-normpath/armhf (1.1.1-1 to 1.1.1-1)
  • Migration status for rust-normpath/armhf (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-ntapi/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-ntapi/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-ntapi/mips64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-ntapi/mips64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-ntapi/ppc64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-ntapi/ppc64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-num-cpus/armel (1.16.0-1 to 1.16.0-1)
  • Migration status for rust-num-cpus/armel (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-num-cpus/i386 (1.16.0-1 to 1.16.0-1)
  • Migration status for rust-num-cpus/i386 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-num-cpus/mips64el (1.16.0-1 to 1.16.0-1)
  • Migration status for rust-num-cpus/mips64el (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-num-format/arm64 (0.4.0-4 to 0.4.0-4)
  • Migration status for rust-num-format/arm64 (0.4.0-4 to 0.4.0-4): Will attempt migration (Any information below is purely informational)
• rust-num-format/armhf (0.4.0-4 to 0.4.0-4)
  • Migration status for rust-num-format/armhf (0.4.0-4 to 0.4.0-4): Will attempt migration (Any information below is purely informational)
• rust-num-format/i386 (0.4.0-4 to 0.4.0-4)
  • Migration status for rust-num-format/i386 (0.4.0-4 to 0.4.0-4): Will attempt migration (Any information below is purely informational)
• rust-num-iter/amd64 (0.1.42-1 to 0.1.42-1)
  • Migration status for rust-num-iter/amd64 (0.1.42-1 to 0.1.42-1): Will attempt migration (Any information below is purely informational)
• rust-num-iter/armel (0.1.42-1 to 0.1.42-1)
  • Migration status for rust-num-iter/armel (0.1.42-1 to 0.1.42-1): Will attempt migration (Any information below is purely informational)
• rust-num-iter/armhf (0.1.42-1 to 0.1.42-1)
  • Migration status for rust-num-iter/armhf (0.1.42-1 to 0.1.42-1): Will attempt migration (Any information below is purely informational)
• rust-num-iter/mips64el (0.1.42-1 to 0.1.42-1)
  • Migration status for rust-num-iter/mips64el (0.1.42-1 to 0.1.42-1): Will attempt migration (Any information below is purely informational)
• rust-num-iter/ppc64el (0.1.42-1 to 0.1.42-1)
  • Migration status for rust-num-iter/ppc64el (0.1.42-1 to 0.1.42-1): Will attempt migration (Any information below is purely informational)
• rust-number-prefix/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-number-prefix/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-number-prefix/armhf (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-number-prefix/armhf (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-number-prefix/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-number-prefix/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-number-prefix/mips64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-number-prefix/mips64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-onig/amd64 (6.3.2-1 to 6.3.2-1)
  • Migration status for rust-onig/amd64 (6.3.2-1 to 6.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-onig/arm64 (6.3.2-1 to 6.3.2-1)
  • Migration status for rust-onig/arm64 (6.3.2-1 to 6.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-onig/armel (6.3.2-1 to 6.3.2-1)
  • Migration status for rust-onig/armel (6.3.2-1 to 6.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-onig/armhf (6.3.2-1 to 6.3.2-1)
  • Migration status for rust-onig/armhf (6.3.2-1 to 6.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-onig/i386 (6.3.2-1 to 6.3.2-1)
  • Migration status for rust-onig/i386 (6.3.2-1 to 6.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-onig/mips64el (6.3.2-1 to 6.3.2-1)
  • Migration status for rust-onig/mips64el (6.3.2-1 to 6.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-opam-file-rs/armel (0.1.5-2 to 0.1.5-2)
  • Migration status for rust-opam-file-rs/armel (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• rust-opam-file-rs/ppc64el (0.1.5-2 to 0.1.5-2)
  • Migration status for rust-opam-file-rs/ppc64el (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• rust-openssh-mux-client-error/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-openssh-mux-client-error/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-openssh-mux-client-error/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-openssh-mux-client-error/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-openssh-mux-client-error/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-openssh-mux-client-error/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-openssh-sftp-protocol/amd64 (0.24.0-1 to 0.24.0-1)
  • Migration status for rust-openssh-sftp-protocol/amd64 (0.24.0-1 to 0.24.0-1): Will attempt migration (Any information below is purely informational)
• rust-openssh-sftp-protocol/arm64 (0.24.0-1 to 0.24.0-1)
  • Migration status for rust-openssh-sftp-protocol/arm64 (0.24.0-1 to 0.24.0-1): Will attempt migration (Any information below is purely informational)
• rust-openssh-sftp-protocol/armel (0.24.0-1 to 0.24.0-1)
  • Migration status for rust-openssh-sftp-protocol/armel (0.24.0-1 to 0.24.0-1): Will attempt migration (Any information below is purely informational)
• rust-openssl-probe/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-openssl-probe/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-openssl-probe/mips64el (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-openssl-probe/mips64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-ordered-stream/armel (0.2.0-2 to 0.2.0-2)
  • Migration status for rust-ordered-stream/armel (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-ordered-stream/ppc64el (0.2.0-2 to 0.2.0-2)
  • Migration status for rust-ordered-stream/ppc64el (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-ordermap/arm64 (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-ordermap/arm64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-ordermap/armel (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-ordermap/armel (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-ordermap/armhf (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-ordermap/armhf (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-ordermap/mips64el (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-ordermap/mips64el (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-ordermap/s390x (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-ordermap/s390x (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-os-display/arm64 (0.1.3-3 to 0.1.3-3)
  • Migration status for rust-os-display/arm64 (0.1.3-3 to 0.1.3-3): Will attempt migration (Any information below is purely informational)
• rust-os-display/armel (0.1.3-3 to 0.1.3-3)
  • Migration status for rust-os-display/armel (0.1.3-3 to 0.1.3-3): Will attempt migration (Any information below is purely informational)
• rust-os-display/mips64el (0.1.3-3 to 0.1.3-3)
  • Migration status for rust-os-display/mips64el (0.1.3-3 to 0.1.3-3): Will attempt migration (Any information below is purely informational)
• rust-ouroboros/arm64 (0.15.6-1 to 0.15.6-1)
  • Migration status for rust-ouroboros/arm64 (0.15.6-1 to 0.15.6-1): Will attempt migration (Any information below is purely informational)
• rust-ouroboros/armel (0.15.6-1 to 0.15.6-1)
  • Migration status for rust-ouroboros/armel (0.15.6-1 to 0.15.6-1): Will attempt migration (Any information below is purely informational)
• rust-ouroboros/i386 (0.15.6-1 to 0.15.6-1)
  • Migration status for rust-ouroboros/i386 (0.15.6-1 to 0.15.6-1): Will attempt migration (Any information below is purely informational)
• rust-output-vt100/arm64 (0.1.2-2 to 0.1.2-2)
  • Migration status for rust-output-vt100/arm64 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• rust-output-vt100/armel (0.1.2-2 to 0.1.2-2)
  • Migration status for rust-output-vt100/armel (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• rust-output-vt100/mips64el (0.1.2-2 to 0.1.2-2)
  • Migration status for rust-output-vt100/mips64el (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• rust-overload/amd64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-overload/amd64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-overload/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-overload/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-overload/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-overload/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-overload/armhf (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-overload/armhf (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-overload/i386 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-overload/i386 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-overload/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-overload/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-overload/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-overload/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-owning-ref/mips64el (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-owning-ref/mips64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-p256/amd64 (0.13.2-1 to 0.13.2-1)
  • Migration status for rust-p256/amd64 (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
• rust-p256/arm64 (0.13.2-1 to 0.13.2-1)
  • Migration status for rust-p256/arm64 (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
• rust-pam-sys/arm64 (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-pam-sys/arm64 (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-pam-sys/armel (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-pam-sys/armel (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-pam-sys/armhf (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-pam-sys/armhf (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-pam-sys/mips64el (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-pam-sys/mips64el (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-pam-sys/ppc64el (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-pam-sys/ppc64el (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-pamsm/amd64 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-pamsm/amd64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-pamsm/arm64 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-pamsm/arm64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-pamsm/armel (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-pamsm/armel (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-pamsm/armhf (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-pamsm/armhf (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-pamsm/i386 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-pamsm/i386 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-pamsm/mips64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-pamsm/mips64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-parity-scale-codec-derive/arm64 (3.6.4-1 to 3.6.4-1)
  • Migration status for rust-parity-scale-codec-derive/arm64 (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-parity-scale-codec-derive/armel (3.6.4-1 to 3.6.4-1)
  • Migration status for rust-parity-scale-codec-derive/armel (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-parity-scale-codec-derive/armhf (3.6.4-1 to 3.6.4-1)
  • Migration status for rust-parity-scale-codec-derive/armhf (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-parity-scale-codec-derive/ppc64el (3.6.4-1 to 3.6.4-1)
  • Migration status for rust-parity-scale-codec-derive/ppc64el (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-parity-scale-codec/armel (3.6.4-1 to 3.6.4-1)
  • Migration status for rust-parity-scale-codec/armel (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-parity-scale-codec/armhf (3.6.4-1 to 3.6.4-1)
  • Migration status for rust-parity-scale-codec/armhf (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-parity-scale-codec/i386 (3.6.4-1 to 3.6.4-1)
  • Migration status for rust-parity-scale-codec/i386 (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-parity-scale-codec/mips64el (3.6.4-1 to 3.6.4-1)
  • Migration status for rust-parity-scale-codec/mips64el (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-parse-arg/arm64 (0.1.4-2 to 0.1.4-2)
  • Migration status for rust-parse-arg/arm64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• rust-parse-arg/i386 (0.1.4-2 to 0.1.4-2)
  • Migration status for rust-parse-arg/i386 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• rust-parse-arg/ppc64el (0.1.4-2 to 0.1.4-2)
  • Migration status for rust-parse-arg/ppc64el (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• rust-parse-zoneinfo/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-parse-zoneinfo/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-parse-zoneinfo/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-parse-zoneinfo/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-parse-zoneinfo/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-parse-zoneinfo/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-parse-zoneinfo/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-parse-zoneinfo/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-parse-zoneinfo/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-parse-zoneinfo/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-patiencediff/amd64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-patiencediff/amd64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-patiencediff/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-patiencediff/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-patiencediff/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-patiencediff/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-patiencediff/ppc64el (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-patiencediff/ppc64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-pbkdf2/arm64 (0.12.2-1 to 0.12.2-1)
  • Migration status for rust-pbkdf2/arm64 (0.12.2-1 to 0.12.2-1): Will attempt migration (Any information below is purely informational)
• rust-pbkdf2/armel (0.12.2-1 to 0.12.2-1)
  • Migration status for rust-pbkdf2/armel (0.12.2-1 to 0.12.2-1): Will attempt migration (Any information below is purely informational)
• rust-pbkdf2/armhf (0.12.2-1 to 0.12.2-1)
  • Migration status for rust-pbkdf2/armhf (0.12.2-1 to 0.12.2-1): Will attempt migration (Any information below is purely informational)
• rust-pbkdf2/mips64el (0.12.2-1 to 0.12.2-1)
  • Migration status for rust-pbkdf2/mips64el (0.12.2-1 to 0.12.2-1): Will attempt migration (Any information below is purely informational)
• rust-pe-unwind-info/arm64 (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-pe-unwind-info/arm64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-pe-unwind-info/i386 (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-pe-unwind-info/i386 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-perfrecord-mach-ipc-rendezvous/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-perfrecord-mach-ipc-rendezvous/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-pest-generator/armel (2.7.4-1 to 2.7.4-1)
  • Migration status for rust-pest-generator/armel (2.7.4-1 to 2.7.4-1): Will attempt migration (Any information below is purely informational)
• rust-pest-generator/armhf (2.7.4-1 to 2.7.4-1)
  • Migration status for rust-pest-generator/armhf (2.7.4-1 to 2.7.4-1): Will attempt migration (Any information below is purely informational)
• rust-pest-generator/mips64el (2.7.4-1 to 2.7.4-1)
  • Migration status for rust-pest-generator/mips64el (2.7.4-1 to 2.7.4-1): Will attempt migration (Any information below is purely informational)
• rust-petgraph/arm64 (0.6.4-1 to 0.6.4-1)
  • Migration status for rust-petgraph/arm64 (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-petgraph/armel (0.6.4-1 to 0.6.4-1)
  • Migration status for rust-petgraph/armel (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-petgraph/armhf (0.6.4-1 to 0.6.4-1)
  • Migration status for rust-petgraph/armhf (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-petgraph/i386 (0.6.4-1 to 0.6.4-1)
  • Migration status for rust-petgraph/i386 (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-picky-asn1/arm64 (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-picky-asn1/arm64 (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-picky-asn1/armel (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-picky-asn1/armel (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-picky-asn1/mips64el (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-picky-asn1/mips64el (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-picky-asn1/ppc64el (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-picky-asn1/ppc64el (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-pidfile-rs/arm64 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-pidfile-rs/arm64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-pidfile-rs/armhf (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-pidfile-rs/armhf (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-pin-project-internal/amd64 (1.1.3-1 to 1.1.3-1)
  • Migration status for rust-pin-project-internal/amd64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-pin-project-internal/arm64 (1.1.3-1 to 1.1.3-1)
  • Migration status for rust-pin-project-internal/arm64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-pin-project-internal/mips64el (1.1.3-1 to 1.1.3-1)
  • Migration status for rust-pin-project-internal/mips64el (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-pin-project-internal/ppc64el (1.1.3-1 to 1.1.3-1)
  • Migration status for rust-pin-project-internal/ppc64el (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-pin-project-lite/armel (0.2.13-1 to 0.2.13-1)
  • Migration status for rust-pin-project-lite/armel (0.2.13-1 to 0.2.13-1): Will attempt migration (Any information below is purely informational)
• rust-pin-project-lite/armhf (0.2.13-1 to 0.2.13-1)
  • Migration status for rust-pin-project-lite/armhf (0.2.13-1 to 0.2.13-1): Will attempt migration (Any information below is purely informational)
• rust-pin-project-lite/mips64el (0.2.13-1 to 0.2.13-1)
  • Migration status for rust-pin-project-lite/mips64el (0.2.13-1 to 0.2.13-1): Will attempt migration (Any information below is purely informational)
• rust-pkcs1/armel (0.7.5-1 to 0.7.5-1)
  • Migration status for rust-pkcs1/armel (0.7.5-1 to 0.7.5-1): Will attempt migration (Any information below is purely informational)
• rust-pkcs1/armhf (0.7.5-1 to 0.7.5-1)
  • Migration status for rust-pkcs1/armhf (0.7.5-1 to 0.7.5-1): Will attempt migration (Any information below is purely informational)
• rust-pkcs5/armel (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-pkcs5/armel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-pkcs5/i386 (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-pkcs5/i386 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-pkcs5/mips64el (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-pkcs5/mips64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-pkg-version-impl/armhf (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-pkg-version-impl/armhf (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-pkg-version-impl/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-pkg-version-impl/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-pktparse/armhf (0.7.1-2 to 0.7.1-2)
  • Migration status for rust-pktparse/armhf (0.7.1-2 to 0.7.1-2): Will attempt migration (Any information below is purely informational)
• rust-pktparse/mips64el (0.7.1-2 to 0.7.1-2)
  • Migration status for rust-pktparse/mips64el (0.7.1-2 to 0.7.1-2): Will attempt migration (Any information below is purely informational)
• rust-platforms/armel (3.1.2-1 to 3.1.2-1)
  • Migration status for rust-platforms/armel (3.1.2-1 to 3.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-platforms/mips64el (3.1.2-1 to 3.1.2-1)
  • Migration status for rust-platforms/mips64el (3.1.2-1 to 3.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-pocket-resources/arm64 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-pocket-resources/arm64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-pocket-resources/armel (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-pocket-resources/armel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-pocket-resources/armhf (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-pocket-resources/armhf (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-pocket-resources/i386 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-pocket-resources/i386 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-podio/amd64 (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-podio/amd64 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-podio/armel (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-podio/armel (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-podio/i386 (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-podio/i386 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-podio/mips64el (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-podio/mips64el (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-pollster/armel (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-pollster/armel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-pollster/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-pollster/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-pollster/mips64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-pollster/mips64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-poly1305/arm64 (0.8.0-1 to 0.8.0-1)
  • Migration status for rust-poly1305/arm64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-poly1305/armhf (0.8.0-1 to 0.8.0-1)
  • Migration status for rust-poly1305/armhf (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-polyval/amd64 (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-polyval/amd64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-polyval/mips64el (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-polyval/mips64el (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-polyval/ppc64el (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-polyval/ppc64el (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-pool/amd64 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-pool/amd64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-pool/arm64 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-pool/arm64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-pool/armel (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-pool/armel (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-pool/armhf (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-pool/armhf (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-pool/ppc64el (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-pool/ppc64el (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-powerfmt-macros/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-powerfmt-macros/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-powerfmt-macros/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-powerfmt-macros/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-powerfmt-macros/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-powerfmt-macros/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-powerfmt/amd64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-powerfmt/amd64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-powerfmt/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-powerfmt/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-powerfmt/armel (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-powerfmt/armel (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-powerfmt/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-powerfmt/i386 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-powerfmt/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-powerfmt/mips64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-prettyplease/amd64 (0.2.6-1 to 0.2.6-1)
  • Migration status for rust-prettyplease/amd64 (0.2.6-1 to 0.2.6-1): Will attempt migration (Any information below is purely informational)
• rust-prettyplease/armel (0.2.6-1 to 0.2.6-1)
  • Migration status for rust-prettyplease/armel (0.2.6-1 to 0.2.6-1): Will attempt migration (Any information below is purely informational)
• rust-prettyplease/mips64el (0.2.6-1 to 0.2.6-1)
  • Migration status for rust-prettyplease/mips64el (0.2.6-1 to 0.2.6-1): Will attempt migration (Any information below is purely informational)
• rust-primal-bit/mips64el (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-primal-bit/mips64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-print-bytes/arm64 (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-print-bytes/arm64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-print-bytes/armel (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-print-bytes/armel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-print-bytes/armhf (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-print-bytes/armhf (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-print-bytes/i386 (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-print-bytes/i386 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-print-bytes/mips64el (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-print-bytes/mips64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-probe/arm64 (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-probe/arm64 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-error/amd64 (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-proc-macro-error/amd64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-error/arm64 (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-proc-macro-error/arm64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-error/armhf (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-proc-macro-error/armhf (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-error/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-proc-macro-error/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-error/mips64el (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-proc-macro-error/mips64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-nested/armel (0.1.3-2 to 0.1.3-2)
  • Migration status for rust-proc-macro-nested/armel (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-nested/armhf (0.1.3-2 to 0.1.3-2)
  • Migration status for rust-proc-macro-nested/armhf (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-nested/i386 (0.1.3-2 to 0.1.3-2)
  • Migration status for rust-proc-macro-nested/i386 (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• rust-proc-macro-nested/mips64el (0.1.3-2 to 0.1.3-2)
  • Migration status for rust-proc-macro-nested/mips64el (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• rust-proc-quote-impl/amd64 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-proc-quote-impl/amd64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-proc-quote-impl/armel (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-proc-quote-impl/armel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-proc-quote-impl/armhf (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-proc-quote-impl/armhf (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-proc-quote-impl/i386 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-proc-quote-impl/i386 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-proc-quote-impl/mips64el (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-proc-quote-impl/mips64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-codegen-pure/armel (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protobuf-codegen-pure/armel (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-codegen-pure/i386 (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protobuf-codegen-pure/i386 (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-codegen-pure/mips64el (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protobuf-codegen-pure/mips64el (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-codegen-pure/ppc64el (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protobuf-codegen-pure/ppc64el (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-support/arm64 (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-protobuf-support/arm64 (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-support/armel (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-protobuf-support/armel (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-support/armhf (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-protobuf-support/armhf (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-support/i386 (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-protobuf-support/i386 (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-support/mips64el (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-protobuf-support/mips64el (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-protoc-rust/amd64 (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protoc-rust/amd64 (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protoc-rust/arm64 (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protoc-rust/arm64 (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protoc-rust/armel (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protoc-rust/armel (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protoc-rust/mips64el (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protoc-rust/mips64el (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-pty-process/amd64 (0.4.0-2 to 0.4.0-2)
  • Migration status for rust-pty-process/amd64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• rust-pty-process/armel (0.4.0-2 to 0.4.0-2)
  • Migration status for rust-pty-process/armel (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• rust-pty-process/armhf (0.4.0-2 to 0.4.0-2)
  • Migration status for rust-pty-process/armhf (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• rust-pty-process/i386 (0.4.0-2 to 0.4.0-2)
  • Migration status for rust-pty-process/i386 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• rust-pty-process/mips64el (0.4.0-2 to 0.4.0-2)
  • Migration status for rust-pty-process/mips64el (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• rust-pulsectl-rs/amd64 (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-pulsectl-rs/amd64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-pulsectl-rs/armel (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-pulsectl-rs/armel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-pulsectl-rs/mips64el (0.3.2-1 to 0.3.2-1)
  • Migration status for rust-pulsectl-rs/mips64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-quick-protobuf/armel (0.8.1-1 to 0.8.1-1)
  • Migration status for rust-quick-protobuf/armel (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• rust-quick-protobuf/mips64el (0.8.1-1 to 0.8.1-1)
  • Migration status for rust-quick-protobuf/mips64el (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• rust-quitters/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-quitters/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-radix-trie/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-radix-trie/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-radix-trie/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-radix-trie/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-radix-trie/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-radix-trie/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-radix-trie/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-radix-trie/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-radix-trie/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-radix-trie/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-rand-distr/arm64 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-rand-distr/arm64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-rand-distr/i386 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-rand-distr/i386 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-rand-distr/mips64el (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-rand-distr/mips64el (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-rand-xorshift/amd64 (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-rand-xorshift/amd64 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-rand-xorshift/arm64 (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-rand-xorshift/arm64 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-rand-xorshift/armhf (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-rand-xorshift/armhf (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-rand-xorshift/i386 (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-rand-xorshift/i386 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-rand-xorshift/mips64el (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-rand-xorshift/mips64el (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-random-trait/amd64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-random-trait/amd64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-random-trait/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-random-trait/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-random-trait/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-random-trait/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-random-trait/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-random-trait/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-rawloader/amd64 (0.37.1-2 to 0.37.1-2)
  • Migration status for rust-rawloader/amd64 (0.37.1-2 to 0.37.1-2): Will attempt migration (Any information below is purely informational)
• rust-rawloader/arm64 (0.37.1-2 to 0.37.1-2)
  • Migration status for rust-rawloader/arm64 (0.37.1-2 to 0.37.1-2): Will attempt migration (Any information below is purely informational)
• rust-rawloader/armel (0.37.1-2 to 0.37.1-2)
  • Migration status for rust-rawloader/armel (0.37.1-2 to 0.37.1-2): Will attempt migration (Any information below is purely informational)
• rust-rawloader/armhf (0.37.1-2 to 0.37.1-2)
  • Migration status for rust-rawloader/armhf (0.37.1-2 to 0.37.1-2): Will attempt migration (Any information below is purely informational)
• rust-rawloader/i386 (0.37.1-2 to 0.37.1-2)
  • Migration status for rust-rawloader/i386 (0.37.1-2 to 0.37.1-2): Will attempt migration (Any information below is purely informational)
• rust-rawloader/ppc64el (0.37.1-2 to 0.37.1-2)
  • Migration status for rust-rawloader/ppc64el (0.37.1-2 to 0.37.1-2): Will attempt migration (Any information below is purely informational)
• rust-rb-sys-env/amd64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-rb-sys-env/amd64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-rb-sys-env/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-rb-sys-env/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-rb-sys-env/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-rb-sys-env/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-rb-sys-env/mips64el (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-rb-sys-env/mips64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-reference-counted-singleton/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-reference-counted-singleton/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-reference-counted-singleton/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-reference-counted-singleton/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-reference-counted-singleton/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-reference-counted-singleton/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-regex-cursor/amd64 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-regex-cursor/amd64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-regex-cursor/arm64 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-regex-cursor/arm64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-regex-cursor/armel (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-regex-cursor/armel (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-regex-cursor/i386 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-regex-cursor/i386 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-result-like/amd64 (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-result-like/amd64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-result-like/armel (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-result-like/armel (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-result-like/armhf (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-result-like/armhf (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-result-like/i386 (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-result-like/i386 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-result-like/mips64el (0.4.6-1 to 0.4.6-1)
  • Migration status for rust-result-like/mips64el (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• rust-rfc2047/amd64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-rfc2047/amd64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-rfc2047/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-rfc2047/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-rfc2047/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-rfc2047/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-rfc2047/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-rfc2047/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-rfc822-sanitizer/armel (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-rfc822-sanitizer/armel (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-rfc822-sanitizer/armhf (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-rfc822-sanitizer/armhf (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-rfc822-sanitizer/i386 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-rfc822-sanitizer/i386 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-rfc822-sanitizer/mips64el (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-rfc822-sanitizer/mips64el (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-ringbuf/amd64 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-ringbuf/amd64 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-ringbuf/arm64 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-ringbuf/arm64 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-ringbuf/armel (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-ringbuf/armel (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-ringbuf/i386 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-ringbuf/i386 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-ringbuf/ppc64el (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-ringbuf/ppc64el (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-rlimit/i386 (0.8.3-1 to 0.8.3-1)
  • Migration status for rust-rlimit/i386 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• rust-rlimit/ppc64el (0.8.3-1 to 0.8.3-1)
  • Migration status for rust-rlimit/ppc64el (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• rust-rlp/armhf (0.5.2-2 to 0.5.2-2)
  • Migration status for rust-rlp/armhf (0.5.2-2 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
• rust-roaring/i386 (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-roaring/i386 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-roaring/mips64el (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-roaring/mips64el (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-ropey/arm64 (1.6.1-1 to 1.6.1-1)
  • Migration status for rust-ropey/arm64 (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-ropey/ppc64el (1.6.1-1 to 1.6.1-1)
  • Migration status for rust-ropey/ppc64el (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-rpassword/armel (7.2.0-1 to 7.2.0-1)
  • Migration status for rust-rpassword/armel (7.2.0-1 to 7.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-rpassword/armhf (7.2.0-1 to 7.2.0-1)
  • Migration status for rust-rpassword/armhf (7.2.0-1 to 7.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-rpassword/mips64el (7.2.0-1 to 7.2.0-1)
  • Migration status for rust-rpassword/mips64el (7.2.0-1 to 7.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-rpds/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-rpds/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-rpds/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-rpds/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest-macros/amd64 (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest-macros/amd64 (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest-macros/armel (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest-macros/armel (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest-macros/armhf (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest-macros/armhf (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest-macros/mips64el (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest-macros/mips64el (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest-macros/ppc64el (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest-macros/ppc64el (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest/amd64 (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest/amd64 (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest/armel (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest/armel (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest/armhf (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest/armhf (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest/i386 (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest/i386 (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rstest/ppc64el (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rstest/ppc64el (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rtoolbox/armel (0.0.1-1 to 0.0.1-1)
  • Migration status for rust-rtoolbox/armel (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-rtoolbox/mips64el (0.0.1-1 to 0.0.1-1)
  • Migration status for rust-rtoolbox/mips64el (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-rtoolbox/ppc64el (0.0.1-1 to 0.0.1-1)
  • Migration status for rust-rtoolbox/ppc64el (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-ruma-macros/amd64 (0.10.5-1 to 0.10.5-1)
  • Migration status for rust-ruma-macros/amd64 (0.10.5-1 to 0.10.5-1): Will attempt migration (Any information below is purely informational)
• rust-ruma-macros/armel (0.10.5-1 to 0.10.5-1)
  • Migration status for rust-ruma-macros/armel (0.10.5-1 to 0.10.5-1): Will attempt migration (Any information below is purely informational)
• rust-ruma-push-gateway-api/amd64 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-ruma-push-gateway-api/amd64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-ruma-push-gateway-api/arm64 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-ruma-push-gateway-api/arm64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-ruma-push-gateway-api/mips64el (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-ruma-push-gateway-api/mips64el (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-runtime-format/armhf (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-runtime-format/armhf (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-hex/armel (2.1.0-1 to 2.1.0-1)
  • Migration status for rust-rustc-hex/armel (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-hex/armhf (2.1.0-1 to 2.1.0-1)
  • Migration status for rust-rustc-hex/armhf (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-hex/i386 (2.1.0-1 to 2.1.0-1)
  • Migration status for rust-rustc-hex/i386 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-core/armel (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-rustc-std-workspace-core/armel (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-core/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-rustc-std-workspace-core/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-core/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-rustc-std-workspace-core/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-core/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-rustc-std-workspace-core/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-std/amd64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-rustc-std-workspace-std/amd64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-std/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-rustc-std-workspace-std/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-std/armel (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-rustc-std-workspace-std/armel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-std/mips64el (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-rustc-std-workspace-std/mips64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-std-workspace-std/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-rustc-std-workspace-std/ppc64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-workspace-hack/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-rustc-workspace-hack/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-workspace-hack/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-rustc-workspace-hack/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustc-workspace-hack/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-rustc-workspace-hack/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-rusticata-macros/armhf (4.1.0-2 to 4.1.0-2)
  • Migration status for rust-rusticata-macros/armhf (4.1.0-2 to 4.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-rusticata-macros/i386 (4.1.0-2 to 4.1.0-2)
  • Migration status for rust-rusticata-macros/i386 (4.1.0-2 to 4.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-rusticata-macros/mips64el (4.1.0-2 to 4.1.0-2)
  • Migration status for rust-rusticata-macros/mips64el (4.1.0-2 to 4.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-rusticata-macros/ppc64el (4.1.0-2 to 4.1.0-2)
  • Migration status for rust-rusticata-macros/ppc64el (4.1.0-2 to 4.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-rustix-openpty/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-rustix-openpty/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-rustix-openpty/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-rustix-openpty/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-rustpython-ast/amd64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-rustpython-ast/amd64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustpython-ast/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-rustpython-ast/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustpython-ast/armel (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-rustpython-ast/armel (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustpython-ast/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-rustpython-ast/mips64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-rusty-fork/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-rusty-fork/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-rusty-fork/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-rusty-fork/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-rusty-fork/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-rusty-fork/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustyline-derive/arm64 (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-rustyline-derive/arm64 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-rustyline-derive/i386 (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-rustyline-derive/i386 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-ryu-floating-decimal/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ryu-floating-decimal/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ryu-floating-decimal/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ryu-floating-decimal/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ryu-floating-decimal/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ryu-floating-decimal/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-salsa20/armhf (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-salsa20/armhf (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-same-file/amd64 (1.0.6-1 to 1.0.6-1)
  • Migration status for rust-same-file/amd64 (1.0.6-1 to 1.0.6-1): Will attempt migration (Any information below is purely informational)
• rust-same-file/i386 (1.0.6-1 to 1.0.6-1)
  • Migration status for rust-same-file/i386 (1.0.6-1 to 1.0.6-1): Will attempt migration (Any information below is purely informational)
• rust-schannel/arm64 (0.1.19-1 to 0.1.19-1)
  • Migration status for rust-schannel/arm64 (0.1.19-1 to 0.1.19-1): Will attempt migration (Any information below is purely informational)
• rust-schannel/armel (0.1.19-1 to 0.1.19-1)
  • Migration status for rust-schannel/armel (0.1.19-1 to 0.1.19-1): Will attempt migration (Any information below is purely informational)
• rust-schannel/mips64el (0.1.19-1 to 0.1.19-1)
  • Migration status for rust-schannel/mips64el (0.1.19-1 to 0.1.19-1): Will attempt migration (Any information below is purely informational)
• rust-scoped-threadpool/amd64 (0.1.9-1 to 0.1.9-1)
  • Migration status for rust-scoped-threadpool/amd64 (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• rust-scoped-threadpool/arm64 (0.1.9-1 to 0.1.9-1)
  • Migration status for rust-scoped-threadpool/arm64 (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• rust-scoped-threadpool/armel (0.1.9-1 to 0.1.9-1)
  • Migration status for rust-scoped-threadpool/armel (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• rust-scoped-tls/amd64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-scoped-tls/amd64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-scoped-tls/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-scoped-tls/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-scoped-tls/i386 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-scoped-tls/i386 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-scoped-tls/mips64el (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-scoped-tls/mips64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-scoped-tls/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-scoped-tls/ppc64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-scopetime/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-scopetime/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-scopetime/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-scopetime/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-scopetime/mips64el (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-scopetime/mips64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-scrypt/arm64 (0.11.0-1 to 0.11.0-1)
  • Migration status for rust-scrypt/arm64 (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
• rust-scrypt/armel (0.11.0-1 to 0.11.0-1)
  • Migration status for rust-scrypt/armel (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
• rust-sct/amd64 (0.7.1-3 to 0.7.1-3)
  • Migration status for rust-sct/amd64 (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• rust-sct/armel (0.7.1-3 to 0.7.1-3)
  • Migration status for rust-sct/armel (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• rust-sct/armhf (0.7.1-3 to 0.7.1-3)
  • Migration status for rust-sct/armhf (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• rust-sct/mips64el (0.7.1-3 to 0.7.1-3)
  • Migration status for rust-sct/mips64el (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• rust-sct/ppc64el (0.7.1-3 to 0.7.1-3)
  • Migration status for rust-sct/ppc64el (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• rust-seahash/armel (4.1.0-1 to 4.1.0-1)
  • Migration status for rust-seahash/armel (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-seahash/i386 (4.1.0-1 to 4.1.0-1)
  • Migration status for rust-seahash/i386 (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-seahash/ppc64el (4.1.0-1 to 4.1.0-1)
  • Migration status for rust-seahash/ppc64el (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-seccomp-sys/arm64 (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-seccomp-sys/arm64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-seccomp-sys/armhf (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-seccomp-sys/armhf (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-seccomp-sys/i386 (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-seccomp-sys/i386 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-seccomp-sys/ppc64el (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-seccomp-sys/ppc64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-secrecy/armhf (0.8.0-1 to 0.8.0-1)
  • Migration status for rust-secrecy/armhf (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-section-testing/amd64 (0.0.4-2 to 0.0.4-2)
  • Migration status for rust-section-testing/amd64 (0.0.4-2 to 0.0.4-2): Will attempt migration (Any information below is purely informational)
• rust-section-testing/armhf (0.0.4-2 to 0.0.4-2)
  • Migration status for rust-section-testing/armhf (0.0.4-2 to 0.0.4-2): Will attempt migration (Any information below is purely informational)
• rust-section-testing/mips64el (0.0.4-2 to 0.0.4-2)
  • Migration status for rust-section-testing/mips64el (0.0.4-2 to 0.0.4-2): Will attempt migration (Any information below is purely informational)
• rust-selectors/amd64 (0.25.0-2 to 0.25.0-2)
  • Migration status for rust-selectors/amd64 (0.25.0-2 to 0.25.0-2): Will attempt migration (Any information below is purely informational)
• rust-selectors/armel (0.25.0-2 to 0.25.0-2)
  • Migration status for rust-selectors/armel (0.25.0-2 to 0.25.0-2): Will attempt migration (Any information below is purely informational)
• rust-selectors/i386 (0.25.0-2 to 0.25.0-2)
  • Migration status for rust-selectors/i386 (0.25.0-2 to 0.25.0-2): Will attempt migration (Any information below is purely informational)
• rust-selectors/mips64el (0.25.0-2 to 0.25.0-2)
  • Migration status for rust-selectors/mips64el (0.25.0-2 to 0.25.0-2): Will attempt migration (Any information below is purely informational)
• rust-selectors/ppc64el (0.25.0-2 to 0.25.0-2)
  • Migration status for rust-selectors/ppc64el (0.25.0-2 to 0.25.0-2): Will attempt migration (Any information below is purely informational)
• rust-sendfd/arm64 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-sendfd/arm64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-sendfd/armel (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-sendfd/armel (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-sendfd/armhf (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-sendfd/armhf (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-sendfd/mips64el (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-sendfd/mips64el (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-sendfd/ppc64el (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-sendfd/ppc64el (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-sensors/mips64el (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-sensors/mips64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-separator/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-separator/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-separator/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-separator/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-separator/mips64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-separator/mips64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-separator/ppc64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-separator/ppc64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-serde-regex/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-serde-regex/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-serde-regex/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-serde-regex/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-serde-regex/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-serde-regex/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-serde-stacker/arm64 (0.1.10-1 to 0.1.10-1)
  • Migration status for rust-serde-stacker/arm64 (0.1.10-1 to 0.1.10-1): Will attempt migration (Any information below is purely informational)
• rust-serde-stacker/armel (0.1.10-1 to 0.1.10-1)
  • Migration status for rust-serde-stacker/armel (0.1.10-1 to 0.1.10-1): Will attempt migration (Any information below is purely informational)
• rust-serde-stacker/i386 (0.1.10-1 to 0.1.10-1)
  • Migration status for rust-serde-stacker/i386 (0.1.10-1 to 0.1.10-1): Will attempt migration (Any information below is purely informational)
• rust-serde-stacker/mips64el (0.1.10-1 to 0.1.10-1)
  • Migration status for rust-serde-stacker/mips64el (0.1.10-1 to 0.1.10-1): Will attempt migration (Any information below is purely informational)
• rust-serde-test/amd64 (1.0.171-1 to 1.0.171-1)
  • Migration status for rust-serde-test/amd64 (1.0.171-1 to 1.0.171-1): Will attempt migration (Any information below is purely informational)
• rust-serde-test/armel (1.0.171-1 to 1.0.171-1)
  • Migration status for rust-serde-test/armel (1.0.171-1 to 1.0.171-1): Will attempt migration (Any information below is purely informational)
• rust-serde-test/armhf (1.0.171-1 to 1.0.171-1)
  • Migration status for rust-serde-test/armhf (1.0.171-1 to 1.0.171-1): Will attempt migration (Any information below is purely informational)
• rust-serde-test/mips64el (1.0.171-1 to 1.0.171-1)
  • Migration status for rust-serde-test/mips64el (1.0.171-1 to 1.0.171-1): Will attempt migration (Any information below is purely informational)
• rust-serial-core/amd64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-serial-core/amd64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-serial-core/armhf (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-serial-core/armhf (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-serial-core/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-serial-core/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-serial-core/mips64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-serial-core/mips64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-serial-core/ppc64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-serial-core/ppc64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-serial/amd64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-serial/amd64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-serial/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-serial/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-serial/armel (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-serial/armel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha1-asm/armel (0.5.1-2 to 0.5.1-2)
  • Migration status for rust-sha1-asm/armel (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• rust-sha1-asm/mips64el (0.5.1-2 to 0.5.1-2)
  • Migration status for rust-sha1-asm/mips64el (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• rust-sha1-asm/ppc64el (0.5.1-2 to 0.5.1-2)
  • Migration status for rust-sha1-asm/ppc64el (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• rust-sha1-checked/amd64 (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-sha1-checked/amd64 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha1-checked/armel (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-sha1-checked/armel (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha1-checked/i386 (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-sha1-checked/i386 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha1-checked/mips64el (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-sha1-checked/mips64el (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha1-smol/amd64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-sha1-smol/amd64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha1-smol/armel (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-sha1-smol/armel (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha1-smol/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-sha1-smol/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha1-smol/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-sha1-smol/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-sha2-asm/armel (0.6.2-2 to 0.6.2-2)
  • Migration status for rust-sha2-asm/armel (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• rust-sha2-asm/i386 (0.6.2-2 to 0.6.2-2)
  • Migration status for rust-sha2-asm/i386 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• rust-sha2-asm/ppc64el (0.6.2-2 to 0.6.2-2)
  • Migration status for rust-sha2-asm/ppc64el (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• rust-shared-library/amd64 (0.1.9-2 to 0.1.9-2)
  • Migration status for rust-shared-library/amd64 (0.1.9-2 to 0.1.9-2): Will attempt migration (Any information below is purely informational)
• rust-shared-library/armel (0.1.9-2 to 0.1.9-2)
  • Migration status for rust-shared-library/armel (0.1.9-2 to 0.1.9-2): Will attempt migration (Any information below is purely informational)
• rust-shared-library/mips64el (0.1.9-2 to 0.1.9-2)
  • Migration status for rust-shared-library/mips64el (0.1.9-2 to 0.1.9-2): Will attempt migration (Any information below is purely informational)
• rust-shell-escape/arm64 (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-shell-escape/arm64 (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-shell-escape/armel (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-shell-escape/armel (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-shell-escape/armhf (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-shell-escape/armhf (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-shell-escape/i386 (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-shell-escape/i386 (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-shell-escape/mips64el (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-shell-escape/mips64el (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-signal-hook-tokio/arm64 (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-signal-hook-tokio/arm64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-signal-hook-tokio/i386 (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-signal-hook-tokio/i386 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-signal-hook-tokio/mips64el (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-signal-hook-tokio/mips64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-signal-hook-tokio/ppc64el (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-signal-hook-tokio/ppc64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-signal-hook/amd64 (0.3.17-1 to 0.3.17-1)
  • Migration status for rust-signal-hook/amd64 (0.3.17-1 to 0.3.17-1): Will attempt migration (Any information below is purely informational)
• rust-signal-hook/ppc64el (0.3.17-1 to 0.3.17-1)
  • Migration status for rust-signal-hook/ppc64el (0.3.17-1 to 0.3.17-1): Will attempt migration (Any information below is purely informational)
• rust-simd-adler32/arm64 (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-simd-adler32/arm64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-simd-adler32/armhf (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-simd-adler32/armhf (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-simd-adler32/i386 (0.3.7-1 to 0.3.7-1)
  • Migration status for rust-simd-adler32/i386 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• rust-simd-helpers/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-simd-helpers/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-simd-helpers/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-simd-helpers/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-simplecss/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-simplecss/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-simplecss/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-simplecss/mips64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-simplecss/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-simplecss/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-sized-chunks/amd64 (0.6.5-2 to 0.6.5-2)
  • Migration status for rust-sized-chunks/amd64 (0.6.5-2 to 0.6.5-2): Will attempt migration (Any information below is purely informational)
• rust-sized-chunks/arm64 (0.6.5-2 to 0.6.5-2)
  • Migration status for rust-sized-chunks/arm64 (0.6.5-2 to 0.6.5-2): Will attempt migration (Any information below is purely informational)
• rust-sized-chunks/armhf (0.6.5-2 to 0.6.5-2)
  • Migration status for rust-sized-chunks/armhf (0.6.5-2 to 0.6.5-2): Will attempt migration (Any information below is purely informational)
• rust-sized-chunks/i386 (0.6.5-2 to 0.6.5-2)
  • Migration status for rust-sized-chunks/i386 (0.6.5-2 to 0.6.5-2): Will attempt migration (Any information below is purely informational)
• rust-sized-chunks/ppc64el (0.6.5-2 to 0.6.5-2)
  • Migration status for rust-sized-chunks/ppc64el (0.6.5-2 to 0.6.5-2): Will attempt migration (Any information below is purely informational)
• rust-smallbitvec/arm64 (2.5.1-1 to 2.5.1-1)
  • Migration status for rust-smallbitvec/arm64 (2.5.1-1 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-smallbitvec/armhf (2.5.1-1 to 2.5.1-1)
  • Migration status for rust-smallbitvec/armhf (2.5.1-1 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-smallbitvec/mips64el (2.5.1-1 to 2.5.1-1)
  • Migration status for rust-smallbitvec/mips64el (2.5.1-1 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-smartstring/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-smartstring/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-smartstring/armel (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-smartstring/armel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-smartstring/mips64el (1.0.1-1 to 1.0.1-1)
  • Migration status for rust-smartstring/mips64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-smithay-client-toolkit-0.16/armel (0.16.1-7 to 0.16.1-7)
  • Migration status for rust-smithay-client-toolkit-0.16/armel (0.16.1-7 to 0.16.1-7): Will attempt migration (Any information below is purely informational)
• rust-smithay-client-toolkit-0.16/i386 (0.16.1-7 to 0.16.1-7)
  • Migration status for rust-smithay-client-toolkit-0.16/i386 (0.16.1-7 to 0.16.1-7): Will attempt migration (Any information below is purely informational)
• rust-smithay-client-toolkit-0.16/mips64el (0.16.1-7 to 0.16.1-7)
  • Migration status for rust-smithay-client-toolkit-0.16/mips64el (0.16.1-7 to 0.16.1-7): Will attempt migration (Any information below is purely informational)
• rust-spinning/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-spinning/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-spinning/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-spinning/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-spinning/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-spinning/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-splitty/amd64 (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-splitty/amd64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-splitty/arm64 (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-splitty/arm64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-splitty/armel (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-splitty/armel (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-splitty/i386 (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-splitty/i386 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-splitty/mips64el (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-splitty/mips64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-splitty/ppc64el (1.0.2-1 to 1.0.2-1)
  • Migration status for rust-splitty/ppc64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format-error/amd64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ssh-format-error/amd64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format-error/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ssh-format-error/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format-error/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ssh-format-error/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format-error/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ssh-format-error/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format/amd64 (0.14.1-1 to 0.14.1-1)
  • Migration status for rust-ssh-format/amd64 (0.14.1-1 to 0.14.1-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format/arm64 (0.14.1-1 to 0.14.1-1)
  • Migration status for rust-ssh-format/arm64 (0.14.1-1 to 0.14.1-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format/armhf (0.14.1-1 to 0.14.1-1)
  • Migration status for rust-ssh-format/armhf (0.14.1-1 to 0.14.1-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format/i386 (0.14.1-1 to 0.14.1-1)
  • Migration status for rust-ssh-format/i386 (0.14.1-1 to 0.14.1-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format/mips64el (0.14.1-1 to 0.14.1-1)
  • Migration status for rust-ssh-format/mips64el (0.14.1-1 to 0.14.1-1): Will attempt migration (Any information below is purely informational)
• rust-ssh-format/ppc64el (0.14.1-1 to 0.14.1-1)
  • Migration status for rust-ssh-format/ppc64el (0.14.1-1 to 0.14.1-1): Will attempt migration (Any information below is purely informational)
• rust-ssri/armel (9.2.0-1 to 9.2.0-1)
  • Migration status for rust-ssri/armel (9.2.0-1 to 9.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-ssri/ppc64el (9.2.0-1 to 9.2.0-1)
  • Migration status for rust-ssri/ppc64el (9.2.0-1 to 9.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-stable-deref-trait/armel (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-stable-deref-trait/armel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-stable-deref-trait/armhf (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-stable-deref-trait/armhf (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-stackvector/amd64 (1.1.1-1 to 1.1.1-1)
  • Migration status for rust-stackvector/amd64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-static-alloc/mips64el (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-static-alloc/mips64el (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-static-alloc/ppc64el (0.2.5-1 to 0.2.5-1)
  • Migration status for rust-static-alloc/ppc64el (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• rust-statsd/armel (0.16.0-1 to 0.16.0-1)
  • Migration status for rust-statsd/armel (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-statsd/i386 (0.16.0-1 to 0.16.0-1)
  • Migration status for rust-statsd/i386 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-std-prelude/amd64 (0.2.12-1 to 0.2.12-1)
  • Migration status for rust-std-prelude/amd64 (0.2.12-1 to 0.2.12-1): Will attempt migration (Any information below is purely informational)
• rust-std-prelude/arm64 (0.2.12-1 to 0.2.12-1)
  • Migration status for rust-std-prelude/arm64 (0.2.12-1 to 0.2.12-1): Will attempt migration (Any information below is purely informational)
• rust-std-prelude/mips64el (0.2.12-1 to 0.2.12-1)
  • Migration status for rust-std-prelude/mips64el (0.2.12-1 to 0.2.12-1): Will attempt migration (Any information below is purely informational)
• rust-stderrlog/arm64 (0.5.4-1 to 0.5.4-1)
  • Migration status for rust-stderrlog/arm64 (0.5.4-1 to 0.5.4-1): Will attempt migration (Any information below is purely informational)
• rust-stderrlog/armel (0.5.4-1 to 0.5.4-1)
  • Migration status for rust-stderrlog/armel (0.5.4-1 to 0.5.4-1): Will attempt migration (Any information below is purely informational)
• rust-stderrlog/i386 (0.5.4-1 to 0.5.4-1)
  • Migration status for rust-stderrlog/i386 (0.5.4-1 to 0.5.4-1): Will attempt migration (Any information below is purely informational)
• rust-stderrlog/mips64el (0.5.4-1 to 0.5.4-1)
  • Migration status for rust-stderrlog/mips64el (0.5.4-1 to 0.5.4-1): Will attempt migration (Any information below is purely informational)
• rust-stdweb-derive/mips64el (0.5.3-1 to 0.5.3-1)
  • Migration status for rust-stdweb-derive/mips64el (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
• rust-stdweb-derive/ppc64el (0.5.3-1 to 0.5.3-1)
  • Migration status for rust-stdweb-derive/ppc64el (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
• rust-stfu8/amd64 (0.2.6-2 to 0.2.6-2)
  • Migration status for rust-stfu8/amd64 (0.2.6-2 to 0.2.6-2): Will attempt migration (Any information below is purely informational)
• rust-stfu8/armhf (0.2.6-2 to 0.2.6-2)
  • Migration status for rust-stfu8/armhf (0.2.6-2 to 0.2.6-2): Will attempt migration (Any information below is purely informational)
• rust-stfu8/mips64el (0.2.6-2 to 0.2.6-2)
  • Migration status for rust-stfu8/mips64el (0.2.6-2 to 0.2.6-2): Will attempt migration (Any information below is purely informational)
• rust-stfu8/ppc64el (0.2.6-2 to 0.2.6-2)
  • Migration status for rust-stfu8/ppc64el (0.2.6-2 to 0.2.6-2): Will attempt migration (Any information below is purely informational)
• rust-str-indices/arm64 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-str-indices/arm64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-str-indices/armel (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-str-indices/armel (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-str-indices/i386 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-str-indices/i386 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-str-indices/ppc64el (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-str-indices/ppc64el (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-str-stack/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-str-stack/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-str-stack/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-str-stack/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-str-stack/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-str-stack/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-str-stack/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-str-stack/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-streaming-stats/amd64 (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-streaming-stats/amd64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-streaming-stats/armhf (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-streaming-stats/armhf (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-streaming-stats/i386 (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-streaming-stats/i386 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-streaming-stats/mips64el (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-streaming-stats/mips64el (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-streebog/amd64 (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-streebog/amd64 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-streebog/arm64 (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-streebog/arm64 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-streebog/armhf (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-streebog/armhf (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-streebog/i386 (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-streebog/i386 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-streebog/ppc64el (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-streebog/ppc64el (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-strength-reduce/amd64 (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-strength-reduce/amd64 (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-strength-reduce/armel (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-strength-reduce/armel (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-strength-reduce/armhf (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-strength-reduce/armhf (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-strength-reduce/i386 (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-strength-reduce/i386 (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-strength-reduce/mips64el (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-strength-reduce/mips64el (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-string-cache/arm64 (0.8.7-1 to 0.8.7-1)
  • Migration status for rust-string-cache/arm64 (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
• rust-string-cache/armel (0.8.7-1 to 0.8.7-1)
  • Migration status for rust-string-cache/armel (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
• rust-string-cache/ppc64el (0.8.7-1 to 0.8.7-1)
  • Migration status for rust-string-cache/ppc64el (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
• rust-struct-patch-derive/arm64 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-struct-patch-derive/arm64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-struct-patch-derive/i386 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-struct-patch-derive/i386 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-struct-patch-derive/ppc64el (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-struct-patch-derive/ppc64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-struct-patch/amd64 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-struct-patch/amd64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-struct-patch/arm64 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-struct-patch/arm64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-struct-patch/armhf (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-struct-patch/armhf (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-struct-patch/mips64el (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-struct-patch/mips64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-struct-patch/ppc64el (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-struct-patch/ppc64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-structopt-derive/armhf (0.4.18-2 to 0.4.18-2)
  • Migration status for rust-structopt-derive/armhf (0.4.18-2 to 0.4.18-2): Will attempt migration (Any information below is purely informational)
• rust-substring/i386 (1.4.5-1 to 1.4.5-1)
  • Migration status for rust-substring/i386 (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• rust-substring/mips64el (1.4.5-1 to 1.4.5-1)
  • Migration status for rust-substring/mips64el (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• rust-substring/ppc64el (1.4.5-1 to 1.4.5-1)
  • Migration status for rust-substring/ppc64el (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• rust-suggest/amd64 (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-suggest/amd64 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-suggest/armel (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-suggest/armel (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-suggest/i386 (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-suggest/i386 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-suggest/mips64el (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-suggest/mips64el (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-suggest/ppc64el (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-suggest/ppc64el (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-supports-unicode/amd64 (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-supports-unicode/amd64 (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-supports-unicode/mips64el (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-supports-unicode/mips64el (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-supports-unicode/ppc64el (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-supports-unicode/ppc64el (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-sval-derive/amd64 (2.6.1-2 to 2.6.1-2)
  • Migration status for rust-sval-derive/amd64 (2.6.1-2 to 2.6.1-2): Will attempt migration (Any information below is purely informational)
• rust-sval-derive/mips64el (2.6.1-2 to 2.6.1-2)
  • Migration status for rust-sval-derive/mips64el (2.6.1-2 to 2.6.1-2): Will attempt migration (Any information below is purely informational)
• rust-sval-dynamic/amd64 (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-dynamic/amd64 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-dynamic/mips64el (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-dynamic/mips64el (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-dynamic/ppc64el (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-dynamic/ppc64el (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-fmt/amd64 (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-fmt/amd64 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-fmt/i386 (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-fmt/i386 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-fmt/mips64el (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-fmt/mips64el (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-ref/arm64 (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-ref/arm64 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-ref/armel (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-ref/armel (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-ref/armhf (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-ref/armhf (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-ref/i386 (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-ref/i386 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-sval-ref/mips64el (2.6.1-1 to 2.6.1-1)
  • Migration status for rust-sval-ref/mips64el (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-svg/arm64 (0.16.0-1 to 0.16.0-1)
  • Migration status for rust-svg/arm64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-svg/armel (0.16.0-1 to 0.16.0-1)
  • Migration status for rust-svg/armel (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-svg/i386 (0.16.0-1 to 0.16.0-1)
  • Migration status for rust-svg/i386 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-svg/mips64el (0.16.0-1 to 0.16.0-1)
  • Migration status for rust-svg/mips64el (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-svg/ppc64el (0.16.0-1 to 0.16.0-1)
  • Migration status for rust-svg/ppc64el (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-sw-composite/amd64 (0.7.2-2 to 0.7.2-2)
  • Migration status for rust-sw-composite/amd64 (0.7.2-2 to 0.7.2-2): Will attempt migration (Any information below is purely informational)
• rust-sw-composite/armel (0.7.2-2 to 0.7.2-2)
  • Migration status for rust-sw-composite/armel (0.7.2-2 to 0.7.2-2): Will attempt migration (Any information below is purely informational)
• rust-sw-composite/armhf (0.7.2-2 to 0.7.2-2)
  • Migration status for rust-sw-composite/armhf (0.7.2-2 to 0.7.2-2): Will attempt migration (Any information below is purely informational)
• rust-symbolic-common/armhf (12.8.0-1 to 12.8.0-1)
  • Migration status for rust-symbolic-common/armhf (12.8.0-1 to 12.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-symbolic-common/i386 (12.8.0-1 to 12.8.0-1)
  • Migration status for rust-symbolic-common/i386 (12.8.0-1 to 12.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-symbolic-common/mips64el (12.8.0-1 to 12.8.0-1)
  • Migration status for rust-symbolic-common/mips64el (12.8.0-1 to 12.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-symbolic-demangle/arm64 (12.4.0-1 to 12.4.0-1)
  • Migration status for rust-symbolic-demangle/arm64 (12.4.0-1 to 12.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-symbolic-demangle/i386 (12.4.0-1 to 12.4.0-1)
  • Migration status for rust-symbolic-demangle/i386 (12.4.0-1 to 12.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-symbolic-demangle/mips64el (12.4.0-1 to 12.4.0-1)
  • Migration status for rust-symbolic-demangle/mips64el (12.4.0-1 to 12.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-bundle-flac/armel (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-bundle-flac/armel (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-bundle-flac/mips64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-bundle-flac/mips64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-bundle-mp3/arm64 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-bundle-mp3/arm64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-bundle-mp3/mips64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-bundle-mp3/mips64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-bundle-mp3/ppc64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-bundle-mp3/ppc64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-codec-aac/amd64 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-codec-aac/amd64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-codec-aac/arm64 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-codec-aac/arm64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-codec-aac/mips64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-codec-aac/mips64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-codec-aac/ppc64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-codec-aac/ppc64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-codec-pcm/amd64 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-codec-pcm/amd64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-codec-pcm/armel (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-codec-pcm/armel (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-format-mkv/armhf (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-format-mkv/armhf (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-format-mkv/mips64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-format-mkv/mips64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-format-ogg/armhf (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-format-ogg/armhf (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-format-wav/armhf (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-format-wav/armhf (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-format-wav/i386 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-format-wav/i386 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-format-wav/mips64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-format-wav/mips64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-metadata/ppc64el (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-metadata/ppc64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-symphonia-utils-xiph/amd64 (0.5.2-1 to 0.5.2-1)
  • Migration status for rust-symphonia-utils-xiph/amd64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• rust-syn-mid/mips64el (0.5.0-2 to 0.5.0-2)
  • Migration status for rust-syn-mid/mips64el (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• rust-take-mut/mips64el (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-take-mut/mips64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-temporary/amd64 (0.6.4-2 to 0.6.4-2)
  • Migration status for rust-temporary/amd64 (0.6.4-2 to 0.6.4-2): Will attempt migration (Any information below is purely informational)
• rust-temporary/i386 (0.6.4-2 to 0.6.4-2)
  • Migration status for rust-temporary/i386 (0.6.4-2 to 0.6.4-2): Will attempt migration (Any information below is purely informational)
• rust-temporary/mips64el (0.6.4-2 to 0.6.4-2)
  • Migration status for rust-temporary/mips64el (0.6.4-2 to 0.6.4-2): Will attempt migration (Any information below is purely informational)
• rust-temptree/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-temptree/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-temptree/armel (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-temptree/armel (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-temptree/armhf (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-temptree/armhf (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-temptree/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-temptree/i386 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-temptree/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-temptree/mips64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-temptree/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-temptree/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-tendril/arm64 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-tendril/arm64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-tendril/armel (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-tendril/armel (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-tendril/armhf (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-tendril/armhf (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• rust-term-size/arm64 (0.3.1-2 to 0.3.1-2)
  • Migration status for rust-term-size/arm64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• rust-term-size/i386 (0.3.1-2 to 0.3.1-2)
  • Migration status for rust-term-size/i386 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• rust-term-size/ppc64el (0.3.1-2 to 0.3.1-2)
  • Migration status for rust-term-size/ppc64el (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• rust-termini/amd64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-termini/amd64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-termini/armhf (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-termini/armhf (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-termini/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-termini/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-termini/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-termini/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-termion/amd64 (1.5.6-1 to 1.5.6-1)
  • Migration status for rust-termion/amd64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-termion/arm64 (1.5.6-1 to 1.5.6-1)
  • Migration status for rust-termion/arm64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-termion/armel (1.5.6-1 to 1.5.6-1)
  • Migration status for rust-termion/armel (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-termion/i386 (1.5.6-1 to 1.5.6-1)
  • Migration status for rust-termion/i386 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-termion/mips64el (1.5.6-1 to 1.5.6-1)
  • Migration status for rust-termion/mips64el (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-termion/ppc64el (1.5.6-1 to 1.5.6-1)
  • Migration status for rust-termion/ppc64el (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-termios/amd64 (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-termios/amd64 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-termios/armel (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-termios/armel (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-termios/armhf (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-termios/armhf (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-termios/i386 (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-termios/i386 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-termios/mips64el (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-termios/mips64el (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• rust-termsize/armel (0.1.6-3 to 0.1.6-3)
  • Migration status for rust-termsize/armel (0.1.6-3 to 0.1.6-3): Will attempt migration (Any information below is purely informational)
• rust-termsize/i386 (0.1.6-3 to 0.1.6-3)
  • Migration status for rust-termsize/i386 (0.1.6-3 to 0.1.6-3): Will attempt migration (Any information below is purely informational)
• rust-termsize/mips64el (0.1.6-3 to 0.1.6-3)
  • Migration status for rust-termsize/mips64el (0.1.6-3 to 0.1.6-3): Will attempt migration (Any information below is purely informational)
• rust-test-casing-macro/amd64 (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-test-casing-macro/amd64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-test-casing-macro/arm64 (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-test-casing-macro/arm64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-test-casing-macro/armel (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-test-casing-macro/armel (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-test-casing-macro/armhf (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-test-casing-macro/armhf (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-test-casing-macro/i386 (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-test-casing-macro/i386 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-test-casing-macro/mips64el (0.1.3-1 to 0.1.3-1)
  • Migration status for rust-test-casing-macro/mips64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-test-log-macros/amd64 (0.2.14-1 to 0.2.14-1)
  • Migration status for rust-test-log-macros/amd64 (0.2.14-1 to 0.2.14-1): Will attempt migration (Any information below is purely informational)
• rust-test-log-macros/mips64el (0.2.14-1 to 0.2.14-1)
  • Migration status for rust-test-log-macros/mips64el (0.2.14-1 to 0.2.14-1): Will attempt migration (Any information below is purely informational)
• rust-thiserror-core/amd64 (1.0.38-2 to 1.0.38-2)
  • Migration status for rust-thiserror-core/amd64 (1.0.38-2 to 1.0.38-2): Will attempt migration (Any information below is purely informational)
• rust-thiserror-core/arm64 (1.0.38-2 to 1.0.38-2)
  • Migration status for rust-thiserror-core/arm64 (1.0.38-2 to 1.0.38-2): Will attempt migration (Any information below is purely informational)
• rust-thiserror-core/armel (1.0.38-2 to 1.0.38-2)
  • Migration status for rust-thiserror-core/armel (1.0.38-2 to 1.0.38-2): Will attempt migration (Any information below is purely informational)
• rust-thiserror-core/i386 (1.0.38-2 to 1.0.38-2)
  • Migration status for rust-thiserror-core/i386 (1.0.38-2 to 1.0.38-2): Will attempt migration (Any information below is purely informational)
• rust-thiserror-core/ppc64el (1.0.38-2 to 1.0.38-2)
  • Migration status for rust-thiserror-core/ppc64el (1.0.38-2 to 1.0.38-2): Will attempt migration (Any information below is purely informational)
• rust-thiserror-impl-no-std/arm64 (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-thiserror-impl-no-std/arm64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-thiserror-impl-no-std/i386 (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-thiserror-impl-no-std/i386 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-thiserror-no-std/arm64 (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-thiserror-no-std/arm64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-thiserror-no-std/armhf (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-thiserror-no-std/armhf (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-thread-local/armel (1.1.4-1 to 1.1.4-1)
  • Migration status for rust-thread-local/armel (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-thread-local/mips64el (1.1.4-1 to 1.1.4-1)
  • Migration status for rust-thread-local/mips64el (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-thread-priority/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-thread-priority/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-thread-priority/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-thread-priority/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiff/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-tiff/arm64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiff/armel (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-tiff/armel (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-timeago/amd64 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-timeago/amd64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-timeago/arm64 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-timeago/arm64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-timeago/armel (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-timeago/armel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-timeago/ppc64el (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-timeago/ppc64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-timsort/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-timsort/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-timsort/armel (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-timsort/armel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-timsort/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-timsort/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-bench/amd64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-tiny-bench/amd64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-bench/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-tiny-bench/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-bench/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-tiny-bench/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-bench/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-tiny-bench/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-bip39/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-tiny-bip39/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-bip39/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-tiny-bip39/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-bip39/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-tiny-bip39/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-http/amd64 (0.12.0-1 to 0.12.0-1)
  • Migration status for rust-tiny-http/amd64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-http/armel (0.12.0-1 to 0.12.0-1)
  • Migration status for rust-tiny-http/armel (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-http/i386 (0.12.0-1 to 0.12.0-1)
  • Migration status for rust-tiny-http/i386 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-http/mips64el (0.12.0-1 to 0.12.0-1)
  • Migration status for rust-tiny-http/mips64el (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-keccak/amd64 (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-tiny-keccak/amd64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-keccak/arm64 (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-tiny-keccak/arm64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-keccak/armel (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-tiny-keccak/armel (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-keccak/ppc64el (2.0.2-1 to 2.0.2-1)
  • Migration status for rust-tiny-keccak/ppc64el (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• rust-tinystr/armel (0.3.2-2 to 0.3.2-2)
  • Migration status for rust-tinystr/armel (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• rust-tinystr/i386 (0.3.2-2 to 0.3.2-2)
  • Migration status for rust-tinystr/i386 (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• rust-tinystr/ppc64el (0.3.2-2 to 0.3.2-2)
  • Migration status for rust-tinystr/ppc64el (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• rust-tinytemplate/arm64 (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-tinytemplate/arm64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-tinytemplate/armel (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-tinytemplate/armel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-tinytemplate/i386 (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-tinytemplate/i386 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-to-method/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-to-method/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-to-method/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-to-method/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-to-method/ppc64el (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-to-method/ppc64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-io-timeout/amd64 (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-tokio-io-timeout/amd64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-io-timeout/armel (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-tokio-io-timeout/armel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-io-timeout/mips64el (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-tokio-io-timeout/mips64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-io-utility/arm64 (0.7.6-1 to 0.7.6-1)
  • Migration status for rust-tokio-io-utility/arm64 (0.7.6-1 to 0.7.6-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-io-utility/i386 (0.7.6-1 to 0.7.6-1)
  • Migration status for rust-tokio-io-utility/i386 (0.7.6-1 to 0.7.6-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-pipe/armel (0.2.12-1 to 0.2.12-1)
  • Migration status for rust-tokio-pipe/armel (0.2.12-1 to 0.2.12-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-pipe/mips64el (0.2.12-1 to 0.2.12-1)
  • Migration status for rust-tokio-pipe/mips64el (0.2.12-1 to 0.2.12-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-serde/arm64 (0.8.0-2 to 0.8.0-2)
  • Migration status for rust-tokio-serde/arm64 (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• rust-tokio-serde/armel (0.8.0-2 to 0.8.0-2)
  • Migration status for rust-tokio-serde/armel (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• rust-tokio-serde/i386 (0.8.0-2 to 0.8.0-2)
  • Migration status for rust-tokio-serde/i386 (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• rust-tokio-serde/mips64el (0.8.0-2 to 0.8.0-2)
  • Migration status for rust-tokio-serde/mips64el (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• rust-toml-span/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-toml-span/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-toml-span/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-toml-span/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-tower-test/amd64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-tower-test/amd64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-tower-test/armel (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-tower-test/armel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-tower-test/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-tower-test/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-tower-test/ppc64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-tower-test/ppc64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-tr/i386 (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-tr/i386 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-tr/ppc64el (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-tr/ppc64el (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-tracing-appender/armel (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-tracing-appender/armel (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-tracing-appender/i386 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-tracing-appender/i386 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-tracing-appender/mips64el (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-tracing-appender/mips64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-tracing-appender/ppc64el (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-tracing-appender/ppc64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-tracing-chrome/i386 (0.7.2-1 to 0.7.2-1)
  • Migration status for rust-tracing-chrome/i386 (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• rust-tracing-futures/armel (0.2.5-2 to 0.2.5-2)
  • Migration status for rust-tracing-futures/armel (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
• rust-tracing-futures/armhf (0.2.5-2 to 0.2.5-2)
  • Migration status for rust-tracing-futures/armhf (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
• rust-tracing-futures/i386 (0.2.5-2 to 0.2.5-2)
  • Migration status for rust-tracing-futures/i386 (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
• rust-tracing-futures/mips64el (0.2.5-2 to 0.2.5-2)
  • Migration status for rust-tracing-futures/mips64el (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
• rust-tracing-futures/ppc64el (0.2.5-2 to 0.2.5-2)
  • Migration status for rust-tracing-futures/ppc64el (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
• rust-tracing-journald/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-tracing-journald/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-tracing-journald/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-tracing-journald/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-tracing-journald/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-tracing-journald/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable-derive/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-trackable-derive/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable-derive/armhf (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-trackable-derive/armhf (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable-derive/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-trackable-derive/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable-derive/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-trackable-derive/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable-derive/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-trackable-derive/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable/amd64 (1.3.0-1 to 1.3.0-1)
  • Migration status for rust-trackable/amd64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable/armel (1.3.0-1 to 1.3.0-1)
  • Migration status for rust-trackable/armel (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable/i386 (1.3.0-1 to 1.3.0-1)
  • Migration status for rust-trackable/i386 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable/mips64el (1.3.0-1 to 1.3.0-1)
  • Migration status for rust-trackable/mips64el (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-trackable/ppc64el (1.3.0-1 to 1.3.0-1)
  • Migration status for rust-trackable/ppc64el (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-trait-variant/amd64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-trait-variant/amd64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-trait-variant/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-trait-variant/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-trait-variant/ppc64el (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-trait-variant/ppc64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-traitobject/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-traitobject/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-traitobject/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-traitobject/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-traitobject/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-traitobject/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-traitobject/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-traitobject/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-trim-in-place/amd64 (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-trim-in-place/amd64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-trim-in-place/armel (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-trim-in-place/armel (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-trim-in-place/i386 (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-trim-in-place/i386 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-trim-in-place/mips64el (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-trim-in-place/mips64el (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-trim-in-place/ppc64el (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-trim-in-place/ppc64el (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-triple-accel/amd64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-triple-accel/amd64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-triple-accel/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-triple-accel/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-try-or/armhf (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-try-or/armhf (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-twofish/arm64 (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-twofish/arm64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-twofish/armel (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-twofish/armel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-twofish/i386 (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-twofish/i386 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-twofish/mips64el (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-twofish/mips64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-twofish/ppc64el (0.7.1-1 to 0.7.1-1)
  • Migration status for rust-twofish/ppc64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• rust-typemap/armel (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-typemap/armel (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-typemap/i386 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-typemap/i386 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-typemap/mips64el (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-typemap/mips64el (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-typemap/ppc64el (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-typemap/ppc64el (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• rust-typeshare-annotation/armel (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-typeshare-annotation/armel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-typeshare-annotation/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-typeshare-annotation/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-typeshare-annotation/ppc64el (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-typeshare-annotation/ppc64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-typetag-impl/amd64 (0.2.18-1 to 0.2.18-1)
  • Migration status for rust-typetag-impl/amd64 (0.2.18-1 to 0.2.18-1): Will attempt migration (Any information below is purely informational)
• rust-typetag-impl/i386 (0.2.18-1 to 0.2.18-1)
  • Migration status for rust-typetag-impl/i386 (0.2.18-1 to 0.2.18-1): Will attempt migration (Any information below is purely informational)
• rust-typetag-impl/mips64el (0.2.18-1 to 0.2.18-1)
  • Migration status for rust-typetag-impl/mips64el (0.2.18-1 to 0.2.18-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-trie/amd64 (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-ucd-trie/amd64 (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-trie/armel (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-ucd-trie/armel (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-trie/i386 (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-ucd-trie/i386 (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-trie/mips64el (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-ucd-trie/mips64el (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-trie/ppc64el (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-ucd-trie/ppc64el (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-util/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-ucd-util/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-util/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-ucd-util/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-util/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-ucd-util/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-util/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-ucd-util/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-util/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-ucd-util/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-ucd/amd64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-ucd/amd64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-ucd/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-ucd/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt-macros/amd64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-ufmt-macros/amd64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt-macros/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-ufmt-macros/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt-macros/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-ufmt-macros/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt-macros/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-ufmt-macros/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt-write/amd64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ufmt-write/amd64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt-write/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ufmt-write/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt-write/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-ufmt-write/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt/amd64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-ufmt/amd64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-ufmt/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-ufmt/mips64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-uluru/amd64 (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-uluru/amd64 (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-uluru/arm64 (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-uluru/arm64 (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-uluru/armel (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-uluru/armel (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-uluru/armhf (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-uluru/armhf (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-uluru/i386 (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-uluru/i386 (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-uluru/mips64el (3.0.0-1 to 3.0.0-1)
  • Migration status for rust-uluru/mips64el (3.0.0-1 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-umask/armel (2.1.0-1 to 2.1.0-1)
  • Migration status for rust-umask/armel (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unarray/armel (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-unarray/armel (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-unarray/i386 (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-unarray/i386 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-unarray/ppc64el (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-unarray/ppc64el (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-uncased/arm64 (0.9.6-2 to 0.9.6-2)
  • Migration status for rust-uncased/arm64 (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
• rust-uncased/armel (0.9.6-2 to 0.9.6-2)
  • Migration status for rust-uncased/armel (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
• rust-uncased/i386 (0.9.6-2 to 0.9.6-2)
  • Migration status for rust-uncased/i386 (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
• rust-unchecked-index/arm64 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-unchecked-index/arm64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-unchecked-index/armel (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-unchecked-index/armel (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-unchecked-index/i386 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-unchecked-index/i386 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-unescape/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unescape/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unescape/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unescape/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unescape/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unescape/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unescape/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unescape/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ungrammar/armel (1.16.1-1 to 1.16.1-1)
  • Migration status for rust-ungrammar/armel (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
• rust-ungrammar/armhf (1.16.1-1 to 1.16.1-1)
  • Migration status for rust-ungrammar/armhf (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
• rust-unic-char-property/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-char-property/arm64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-emoji-char/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-emoji-char/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-emoji-char/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-emoji-char/arm64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-emoji-char/armel (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-emoji-char/armel (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-emoji-char/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-emoji-char/i386 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-langid-impl/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-langid-impl/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-langid-impl/ppc64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-langid-impl/ppc64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-langid-macros/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-langid-macros/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-langid-macros/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-langid-macros/i386 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-langid/amd64 (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-unic-langid/amd64 (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-unic-langid/armel (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-unic-langid/armel (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-unic-langid/armhf (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-unic-langid/armhf (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-unic-langid/mips64el (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-unic-langid/mips64el (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-unic-segment/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-segment/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-segment/armel (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-segment/armel (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-segment/armhf (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-segment/armhf (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-segment/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-segment/i386 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-age/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-age/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-bidi/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-bidi/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-bidi/armhf (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-bidi/armhf (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-hangul/ppc64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-hangul/ppc64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-ident/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-ident/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-ident/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-ident/arm64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-ident/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-ident/i386 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-ident/ppc64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-ident/ppc64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-normal/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-normal/arm64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-normal/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-normal/i386 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unic-ucd-version/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-ucd-version/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-casing/amd64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-casing/amd64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-casing/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-casing/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-casing/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-casing/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-casing/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-casing/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-casing/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-casing/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-categories/armhf (0.1.1-2 to 0.1.1-2)
  • Migration status for rust-unicode-categories/armhf (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• rust-unicode-categories/ppc64el (0.1.1-2 to 0.1.1-2)
  • Migration status for rust-unicode-categories/ppc64el (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• rust-unicode-names2/amd64 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-unicode-names2/amd64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-names2/i386 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-unicode-names2/i386 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-names2/ppc64el (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-unicode-names2/ppc64el (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-properties/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-properties/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-properties/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-properties/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-properties/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-properties/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-properties/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-properties/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-properties/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unicode-properties/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unicode-script/armel (0.5.2-4 to 0.5.2-4)
  • Migration status for rust-unicode-script/armel (0.5.2-4 to 0.5.2-4): Will attempt migration (Any information below is purely informational)
• rust-unicode-script/i386 (0.5.2-4 to 0.5.2-4)
  • Migration status for rust-unicode-script/i386 (0.5.2-4 to 0.5.2-4): Will attempt migration (Any information below is purely informational)
• rust-unicode-script/ppc64el (0.5.2-4 to 0.5.2-4)
  • Migration status for rust-unicode-script/ppc64el (0.5.2-4 to 0.5.2-4): Will attempt migration (Any information below is purely informational)
• rust-unicode-vo/amd64 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-unicode-vo/amd64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-unicode-vo/arm64 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-unicode-vo/arm64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-unicode-vo/armel (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-unicode-vo/armel (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-unicode-vo/i386 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-unicode-vo/i386 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-unicode-vo/ppc64el (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-unicode-vo/ppc64el (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-unicode-xid/ppc64el (0.2.4-1 to 0.2.4-1)
  • Migration status for rust-unicode-xid/ppc64el (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• rust-universal-hash/i386 (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-universal-hash/i386 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-universal-hash/mips64el (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-universal-hash/mips64el (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-universal-hash/ppc64el (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-universal-hash/ppc64el (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-unreachable/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-unreachable/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-unsafe-any-ors/amd64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-unsafe-any-ors/amd64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-unsafe-any-ors/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-unsafe-any-ors/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-unsafe-any-ors/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-unsafe-any-ors/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-unsafe-any-ors/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-unsafe-any-ors/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-unsafe-any/armel (0.4.2-2 to 0.4.2-2)
  • Migration status for rust-unsafe-any/armel (0.4.2-2 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
• rust-unsafe-any/i386 (0.4.2-2 to 0.4.2-2)
  • Migration status for rust-unsafe-any/i386 (0.4.2-2 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
• rust-unsafe-any/ppc64el (0.4.2-2 to 0.4.2-2)
  • Migration status for rust-unsafe-any/ppc64el (0.4.2-2 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
• rust-unscanny/amd64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unscanny/amd64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unscanny/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unscanny/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unscanny/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unscanny/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-unsigned-varint/mips64el (0.8.0-1 to 0.8.0-1)
  • Migration status for rust-unsigned-varint/mips64el (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-unsigned-varint/ppc64el (0.8.0-1 to 0.8.0-1)
  • Migration status for rust-unsigned-varint/ppc64el (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-untrusted/armhf (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-untrusted/armhf (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-untrusted/i386 (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-untrusted/i386 (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-untrusted/ppc64el (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-untrusted/ppc64el (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-unwrap/amd64 (1.2.1-2 to 1.2.1-2)
  • Migration status for rust-unwrap/amd64 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-unwrap/arm64 (1.2.1-2 to 1.2.1-2)
  • Migration status for rust-unwrap/arm64 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-unwrap/armhf (1.2.1-2 to 1.2.1-2)
  • Migration status for rust-unwrap/armhf (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-unwrap/i386 (1.2.1-2 to 1.2.1-2)
  • Migration status for rust-unwrap/i386 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-uriparse/i386 (0.6.4-1 to 0.6.4-1)
  • Migration status for rust-uriparse/i386 (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• rust-urlencoding/amd64 (2.1.3-1 to 2.1.3-1)
  • Migration status for rust-urlencoding/amd64 (2.1.3-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-urlencoding/i386 (2.1.3-1 to 2.1.3-1)
  • Migration status for rust-urlencoding/i386 (2.1.3-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-urlencoding/ppc64el (2.1.3-1 to 2.1.3-1)
  • Migration status for rust-urlencoding/ppc64el (2.1.3-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
• rust-usb-disk-probe/armel (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-usb-disk-probe/armel (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-usb-disk-probe/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-usb-disk-probe/i386 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-usb-disk-probe/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-usb-disk-probe/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-utf-8/amd64 (0.7.6-2 to 0.7.6-2)
  • Migration status for rust-utf-8/amd64 (0.7.6-2 to 0.7.6-2): Will attempt migration (Any information below is purely informational)
• rust-utf-8/armel (0.7.6-2 to 0.7.6-2)
  • Migration status for rust-utf-8/armel (0.7.6-2 to 0.7.6-2): Will attempt migration (Any information below is purely informational)
• rust-utf-8/armhf (0.7.6-2 to 0.7.6-2)
  • Migration status for rust-utf-8/armhf (0.7.6-2 to 0.7.6-2): Will attempt migration (Any information below is purely informational)
• rust-utf-8/i386 (0.7.6-2 to 0.7.6-2)
  • Migration status for rust-utf-8/i386 (0.7.6-2 to 0.7.6-2): Will attempt migration (Any information below is purely informational)
• rust-utf8-ranges/armhf (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-utf8-ranges/armhf (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-utf8-ranges/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-utf8-ranges/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-utf8-ranges/ppc64el (1.0.4-1 to 1.0.4-1)
  • Migration status for rust-utf8-ranges/ppc64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-utf8parse/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-utf8parse/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-utf8parse/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-utf8parse/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-utf8parse/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-utf8parse/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-utf8parse/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-utf8parse/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-utf8parse/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-utf8parse/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-varint/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-varint/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-varint/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-varint/i386 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-varint/ppc64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-varint/ppc64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-vec-map/amd64 (0.8.1-2 to 0.8.1-2)
  • Migration status for rust-vec-map/amd64 (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
• rust-vec-map/armel (0.8.1-2 to 0.8.1-2)
  • Migration status for rust-vec-map/armel (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
• rust-vec-map/mips64el (0.8.1-2 to 0.8.1-2)
  • Migration status for rust-vec-map/mips64el (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
• rust-vec-map/ppc64el (0.8.1-2 to 0.8.1-2)
  • Migration status for rust-vec-map/ppc64el (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
• rust-version-compare/amd64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-version-compare/amd64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-version-compare/i386 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-version-compare/i386 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-versionize-derive/armel (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-versionize-derive/armel (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-versionize-derive/ppc64el (0.1.5-1 to 0.1.5-1)
  • Migration status for rust-versionize-derive/ppc64el (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• rust-volatile/amd64 (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-volatile/amd64 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-volatile/ppc64el (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-volatile/ppc64el (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-vsort/amd64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-vsort/amd64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-vsort/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-vsort/i386 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-vsort/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-vsort/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-vsprintf/armel (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-vsprintf/armel (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-vsprintf/armhf (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-vsprintf/armhf (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-vte-generate-state-changes/i386 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-vte-generate-state-changes/i386 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-wait-timeout/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-wait-timeout/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-wait-timeout/armel (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-wait-timeout/armel (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-wait-timeout/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-wait-timeout/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-waker-fn/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-waker-fn/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-waker-fn/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-waker-fn/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-want/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-want/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-want/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-want/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-want/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-want/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-want/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-want/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-wat/amd64 (1.217.0-1 to 1.217.0-1)
  • Migration status for rust-wat/amd64 (1.217.0-1 to 1.217.0-1): Will attempt migration (Any information below is purely informational)
• rust-wat/armel (1.217.0-1 to 1.217.0-1)
  • Migration status for rust-wat/armel (1.217.0-1 to 1.217.0-1): Will attempt migration (Any information below is purely informational)
• rust-wat/i386 (1.217.0-1 to 1.217.0-1)
  • Migration status for rust-wat/i386 (1.217.0-1 to 1.217.0-1): Will attempt migration (Any information below is purely informational)
• rust-wildmatch/armel (2.1.1-1 to 2.1.1-1)
  • Migration status for rust-wildmatch/armel (2.1.1-1 to 2.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-wildmatch/ppc64el (2.1.1-1 to 2.1.1-1)
  • Migration status for rust-wildmatch/ppc64el (2.1.1-1 to 2.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-winapi-build/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-winapi-build/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-winapi-build/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-winapi-build/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-winapi-x86-64-pc-windows-gnu/armel (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-winapi-x86-64-pc-windows-gnu/armel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-winapi-x86-64-pc-windows-gnu/ppc64el (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-winapi-x86-64-pc-windows-gnu/ppc64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-winreg/amd64 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-winreg/amd64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-winreg/i386 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-winreg/i386 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-winreg/mips64el (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-winreg/mips64el (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-winreg/ppc64el (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-winreg/ppc64el (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-wio/arm64 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-wio/arm64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-wio/i386 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-wio/i386 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-wrapcenum-derive/armhf (0.4.0-3 to 0.4.0-3)
  • Migration status for rust-wrapcenum-derive/armhf (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• rust-wrapcenum-derive/ppc64el (0.4.0-3 to 0.4.0-3)
  • Migration status for rust-wrapcenum-derive/ppc64el (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• rust-wu-diff/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-wu-diff/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-wu-diff/ppc64el (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-wu-diff/ppc64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-wyz/amd64 (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-wyz/amd64 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-wyz/armel (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-wyz/armel (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-wyz/ppc64el (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-wyz/ppc64el (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-x11-dl/arm64 (2.21.0-1 to 2.21.0-1)
  • Migration status for rust-x11-dl/arm64 (2.21.0-1 to 2.21.0-1): Will attempt migration (Any information below is purely informational)
• rust-x11-dl/armhf (2.21.0-1 to 2.21.0-1)
  • Migration status for rust-x11-dl/armhf (2.21.0-1 to 2.21.0-1): Will attempt migration (Any information below is purely informational)
• rust-x11-dl/ppc64el (2.21.0-1 to 2.21.0-1)
  • Migration status for rust-x11-dl/ppc64el (2.21.0-1 to 2.21.0-1): Will attempt migration (Any information below is purely informational)
• rust-x11/amd64 (2.19.1-1 to 2.19.1-1)
  • Migration status for rust-x11/amd64 (2.19.1-1 to 2.19.1-1): Will attempt migration (Any information below is purely informational)
• rust-x11/armhf (2.19.1-1 to 2.19.1-1)
  • Migration status for rust-x11/armhf (2.19.1-1 to 2.19.1-1): Will attempt migration (Any information below is purely informational)
• rust-x11/i386 (2.19.1-1 to 2.19.1-1)
  • Migration status for rust-x11/i386 (2.19.1-1 to 2.19.1-1): Will attempt migration (Any information below is purely informational)
• rust-xi-unicode/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-xi-unicode/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-xi-unicode/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-xi-unicode/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-xi-unicode/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-xi-unicode/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-xi-unicode/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-xi-unicode/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-xi-unicode/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-xi-unicode/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-xkb/arm64 (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-xkb/arm64 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-xkb/armhf (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-xkb/armhf (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-xkb/i386 (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-xkb/i386 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-xz/amd64 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-xz/amd64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-xz/arm64 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-xz/arm64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-xz/i386 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-xz/i386 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-xz/mips64el (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-xz/mips64el (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-xz2/armhf (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-xz2/armhf (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-yaml-rust/i386 (0.4.5-1 to 0.4.5-1)
  • Migration status for rust-yaml-rust/i386 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
• rust-yaml-rust/ppc64el (0.4.5-1 to 0.4.5-1)
  • Migration status for rust-yaml-rust/ppc64el (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
• rust-z85/arm64 (3.0.5-1 to 3.0.5-1)
  • Migration status for rust-z85/arm64 (3.0.5-1 to 3.0.5-1): Will attempt migration (Any information below is purely informational)
• rust-z85/i386 (3.0.5-1 to 3.0.5-1)
  • Migration status for rust-z85/i386 (3.0.5-1 to 3.0.5-1): Will attempt migration (Any information below is purely informational)
• rust-z85/ppc64el (3.0.5-1 to 3.0.5-1)
  • Migration status for rust-z85/ppc64el (3.0.5-1 to 3.0.5-1): Will attempt migration (Any information below is purely informational)
• rust-zbar-rust/arm64 (0.0.21-1 to 0.0.21-1)
  • Migration status for rust-zbar-rust/arm64 (0.0.21-1 to 0.0.21-1): Will attempt migration (Any information below is purely informational)
• rust-zbar-rust/armel (0.0.21-1 to 0.0.21-1)
  • Migration status for rust-zbar-rust/armel (0.0.21-1 to 0.0.21-1): Will attempt migration (Any information below is purely informational)
• rust-zbase32/amd64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-zbase32/amd64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-zbase32/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-zbase32/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-zbase32/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-zbase32/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-zmq-sys/arm64 (0.11.0-2 to 0.11.0-2)
  • Migration status for rust-zmq-sys/arm64 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-zmq-sys/i386 (0.11.0-2 to 0.11.0-2)
  • Migration status for rust-zmq-sys/i386 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-zopfli/amd64 (0.8.1-1 to 0.8.1-1)
  • Migration status for rust-zopfli/amd64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• rust-zopfli/ppc64el (0.8.1-1 to 0.8.1-1)
  • Migration status for rust-zopfli/ppc64el (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• salmon/arm64 (1.10.2+ds1-1 to 1.10.2+ds1-1)
  • Migration status for salmon/arm64 (1.10.2+ds1-1 to 1.10.2+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: salmon/arm64 onetbb (not considered)
    • Invalidated by dependency
• savi/arm64 (1.6.0-1 to 1.6.0-1)
  • Migration status for savi/arm64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• sbd/amd64 (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/amd64 (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/amd64 pacemaker (not considered)
    • Invalidated by dependency
• sbd/arm64 (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/arm64 (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/arm64 pacemaker (not considered)
    • Invalidated by dependency
• sbd/armel (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/armel (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/armel pacemaker (not considered)
    • Invalidated by dependency
• sbd/armhf (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/armhf (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/armhf pacemaker (not considered)
    • Invalidated by dependency
• sbd/i386 (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/i386 (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/i386 pacemaker (not considered)
    • Invalidated by dependency
• sbd/mips64el (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/mips64el (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/mips64el pacemaker (not considered)
    • Invalidated by dependency
• sbd/ppc64el (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/ppc64el (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/ppc64el pacemaker (not considered)
    • Invalidated by dependency
• sbd/riscv64 (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/riscv64 (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/riscv64 pacemaker (not considered)
    • Invalidated by dependency
• sbd/s390x (1.5.2-4 to 1.5.2-4)
  • Migration status for sbd/s390x (1.5.2-4 to 1.5.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbd/s390x pacemaker (not considered)
    • Invalidated by dependency
• scalpel/arm64 (1.60+git20240110.6960eb2-1 to 1.60+git20240110.6960eb2-1)
  • Migration status for scalpel/arm64 (1.60+git20240110.6960eb2-1 to 1.60+git20240110.6960eb2-1): Will attempt migration (Any information below is purely informational)
• sdop/arm64 (1.10-3 to 1.10-3)
  • Migration status for sdop/arm64 (1.10-3 to 1.10-3): Will attempt migration (Any information below is purely informational)
• sga/armhf (0.10.15-7 to 0.10.15-7)
  • Migration status for sga/armhf (0.10.15-7 to 0.10.15-7): Will attempt migration (Any information below is purely informational)
• sga/i386 (0.10.15-7 to 0.10.15-7)
  • Migration status for sga/i386 (0.10.15-7 to 0.10.15-7): Will attempt migration (Any information below is purely informational)
• sgf2dg/arm64 (4.252-1 to 4.252-1)
  • Migration status for sgf2dg/arm64 (4.252-1 to 4.252-1): Will attempt migration (Any information below is purely informational)
• sibelia/arm64 (3.0.7+dfsg-3 to 3.0.7+dfsg-3)
  • Migration status for sibelia/arm64 (3.0.7+dfsg-3 to 3.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• simka/arm64 (1.5.3-8 to 1.5.3-8)
  • Migration status for simka/arm64 (1.5.3-8 to 1.5.3-8): Will attempt migration (Any information below is purely informational)
• sinfo/arm64 (0.0.48-2.1 to 0.0.48-2.1)
  • Migration status for sinfo/arm64 (0.0.48-2.1 to 0.0.48-2.1): Will attempt migration (Any information below is purely informational)
• sinfo/armhf (0.0.48-2.1 to 0.0.48-2.1)
  • Migration status for sinfo/armhf (0.0.48-2.1 to 0.0.48-2.1): Will attempt migration (Any information below is purely informational)
• slirp/arm64 (1:1.0.17-11 to 1:1.0.17-11)
  • Migration status for slirp/arm64 (1:1.0.17-11 to 1:1.0.17-11): Will attempt migration (Any information below is purely informational)
• slxfig/amd64 (0.2.0~.138-1 to 0.2.0~.138-1)
  • Migration status for slxfig/amd64 (0.2.0~.138-1 to 0.2.0~.138-1): Will attempt migration (Any information below is purely informational)
• slxfig/arm64 (0.2.0~.138-1 to 0.2.0~.138-1)
  • Migration status for slxfig/arm64 (0.2.0~.138-1 to 0.2.0~.138-1): Will attempt migration (Any information below is purely informational)
• slxfig/armel (0.2.0~.138-1 to 0.2.0~.138-1)
  • Migration status for slxfig/armel (0.2.0~.138-1 to 0.2.0~.138-1): Will attempt migration (Any information below is purely informational)
• slxfig/armhf (0.2.0~.138-1 to 0.2.0~.138-1)
  • Migration status for slxfig/armhf (0.2.0~.138-1 to 0.2.0~.138-1): Will attempt migration (Any information below is purely informational)
• slxfig/mips64el (0.2.0~.138-1 to 0.2.0~.138-1)
  • Migration status for slxfig/mips64el (0.2.0~.138-1 to 0.2.0~.138-1): Will attempt migration (Any information below is purely informational)
• slxfig/s390x (0.2.0~.138-1 to 0.2.0~.138-1)
  • Migration status for slxfig/s390x (0.2.0~.138-1 to 0.2.0~.138-1): Will attempt migration (Any information below is purely informational)
• smstools/arm64 (3.1.21-4 to 3.1.21-4)
  • Migration status for smstools/arm64 (3.1.21-4 to 3.1.21-4): Will attempt migration (Any information below is purely informational)
• snap/arm64 (2013-11-29-11 to 2013-11-29-11)
  • Migration status for snap/arm64 (2013-11-29-11 to 2013-11-29-11): Will attempt migration (Any information below is purely informational)
• solid-pop3d/arm64 (0.15-31 to 0.15-31)
  • Migration status for solid-pop3d/arm64 (0.15-31 to 0.15-31): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• ssss/arm64 (0.5-5 to 0.5-5)
  • Migration status for ssss/arm64 (0.5-5 to 0.5-5): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• swish++/arm64 (6.1.5-6 to 6.1.5-6)
  • Migration status for swish++/arm64 (6.1.5-6 to 6.1.5-6): Will attempt migration (Any information below is purely informational)
• sxmo-utils/arm64 (1.12.0-7 to 1.12.0-7)
  • Migration status for sxmo-utils/arm64 (1.12.0-7 to 1.12.0-7): Will attempt migration (Any information below is purely informational)
• sxmo-utils/armhf (1.12.0-7 to 1.12.0-7)
  • Migration status for sxmo-utils/armhf (1.12.0-7 to 1.12.0-7): Will attempt migration (Any information below is purely informational)
• sysstat/arm64 (12.7.5-2 to 12.7.5-2)
  • Migration status for sysstat/arm64 (12.7.5-2 to 12.7.5-2): Will attempt migration (Any information below is purely informational)
• tang/arm64 (15-2 to 15-2)
  • Migration status for tang/arm64 (15-2 to 15-2): Will attempt migration (Any information below is purely informational)
• tcl-signal/arm64 (1.4.5-1 to 1.4.5-1)
  • Migration status for tcl-signal/arm64 (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• tcl-signal/armel (1.4.5-1 to 1.4.5-1)
  • Migration status for tcl-signal/armel (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• tcl-signal/armhf (1.4.5-1 to 1.4.5-1)
  • Migration status for tcl-signal/armhf (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• tcl-signal/mips64el (1.4.5-1 to 1.4.5-1)
  • Migration status for tcl-signal/mips64el (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• thunderbird_pu (1:128.9.0esr-1 to 1:128.9.0esr-1~deb12u1)
  • Migration status for thunderbird_pu (1:128.9.0esr-1 to 1:128.9.0esr-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: thunderbird is newer in the target suite (1:128.9.0esr-1 1:128.9.0esr-1~deb12u1)
• tilp2/arm64 (1.19~git20231112.5a2ea63-1 to 1.19~git20231112.5a2ea63-1)
  • Migration status for tilp2/arm64 (1.19~git20231112.5a2ea63-1 to 1.19~git20231112.5a2ea63-1): Will attempt migration (Any information below is purely informational)
• tomcat10_pu (10.1.35-1 to 10.1.34-0+deb12u2)
  • Migration status for tomcat10_pu (10.1.35-1 to 10.1.34-0+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: tomcat10 is newer in the target suite (10.1.35-1 10.1.34-0+deb12u2)
• treesheets/arm64 (1:1.0.2-1.1 to 1:1.0.2-1.1)
  • Migration status for treesheets/arm64 (1:1.0.2-1.1 to 1:1.0.2-1.1): Will attempt migration (Any information below is purely informational)
• trilinos/amd64 (13.2.0-6 to 13.2.0-6)
  • Migration status for trilinos/amd64 (13.2.0-6 to 13.2.0-6): Will attempt migration (Any information below is purely informational)
• trilinos/ppc64el (13.2.0-6 to 13.2.0-6)
  • Migration status for trilinos/ppc64el (13.2.0-6 to 13.2.0-6): Will attempt migration (Any information below is purely informational)
• trilinos/s390x (13.2.0-6 to 13.2.0-6)
  • Migration status for trilinos/s390x (13.2.0-6 to 13.2.0-6): Will attempt migration (Any information below is purely informational)
• trinculo/arm64 (0.96+dfsg-4 to 0.96+dfsg-4)
  • Migration status for trinculo/arm64 (0.96+dfsg-4 to 0.96+dfsg-4): Will attempt migration (Any information below is purely informational)
• trousers/arm64 (0.3.15-0.4 to 0.3.15-0.4)
  • Migration status for trousers/arm64 (0.3.15-0.4 to 0.3.15-0.4): Will attempt migration (Any information below is purely informational)
• tth/arm64 (4.16+ds-1 to 4.16+ds-1)
  • Migration status for tth/arm64 (4.16+ds-1 to 4.16+ds-1): Will attempt migration (Any information below is purely informational)
• twm/arm64 (1:1.0.10-1 to 1:1.0.10-1)
  • Migration status for twm/arm64 (1:1.0.10-1 to 1:1.0.10-1): Will attempt migration (Any information below is purely informational)
• tzdata_pu (2025b-1 to 2025b-0+deb12u1)
  • Migration status for tzdata_pu (2025b-1 to 2025b-0+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: tzdata is newer in the target suite (2025b-1 2025b-0+deb12u1)
• ucl/armhf (1.03+repack-6 to 1.03+repack-6)
  • Migration status for ucl/armhf (1.03+repack-6 to 1.03+repack-6): Will attempt migration (Any information below is purely informational)
• ucl/mips64el (1.03+repack-6 to 1.03+repack-6)
  • Migration status for ucl/mips64el (1.03+repack-6 to 1.03+repack-6): Will attempt migration (Any information below is purely informational)
• unadf/arm64 (0.7.11a-7 to 0.7.11a-7)
  • Migration status for unadf/arm64 (0.7.11a-7 to 0.7.11a-7): Will attempt migration (Any information below is purely informational)
• unpaper/arm64 (7.0.0-3 to 7.0.0-3)
  • Migration status for unpaper/arm64 (7.0.0-3 to 7.0.0-3): Will attempt migration (Any information below is purely informational)
• unpaper/armhf (7.0.0-3 to 7.0.0-3)
  • Migration status for unpaper/armhf (7.0.0-3 to 7.0.0-3): Will attempt migration (Any information below is purely informational)
• up-imapproxy/arm64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/arm64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
• usb-modeswitch/arm64 (2.6.1-4 to 2.6.1-4)
  • Migration status for usb-modeswitch/arm64 (2.6.1-4 to 2.6.1-4): Will attempt migration (Any information below is purely informational)
• usb-modeswitch/armhf (2.6.1-4 to 2.6.1-4)
  • Migration status for usb-modeswitch/armhf (2.6.1-4 to 2.6.1-4): Will attempt migration (Any information below is purely informational)
• valabind/arm64 (1.8.0-1 to 1.8.0-1)
  • Migration status for valabind/arm64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• veroroute/armhf (2.38-1 to 2.38-1)
  • Migration status for veroroute/armhf (2.38-1 to 2.38-1): Will attempt migration (Any information below is purely informational)
• vitetris/arm64 (0.59.1-3 to 0.59.1-3)
  • Migration status for vitetris/arm64 (0.59.1-3 to 0.59.1-3): Will attempt migration (Any information below is purely informational)
• vkeybd/armhf (1:0.1.18d-4 to 1:0.1.18d-4)
  • Migration status for vkeybd/armhf (1:0.1.18d-4 to 1:0.1.18d-4): Will attempt migration (Any information below is purely informational)
• vtprint/arm64 (2.0.2-15 to 2.0.2-15)
  • Migration status for vtprint/arm64 (2.0.2-15 to 2.0.2-15): Will attempt migration (Any information below is purely informational)
• wav2cdr/arm64 (2.3.4-5 to 2.3.4-5)
  • Migration status for wav2cdr/arm64 (2.3.4-5 to 2.3.4-5): Will attempt migration (Any information below is purely informational)
• webkit2gtk_pu (2.48.0-1 to 2.48.0-1~deb12u1)
  • Migration status for webkit2gtk_pu (2.48.0-1 to 2.48.0-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: webkit2gtk is newer in the target suite (2.48.0-1 2.48.0-1~deb12u1)
• wham-align/arm64 (0.1.5-8 to 0.1.5-8)
  • Migration status for wham-align/arm64 (0.1.5-8 to 0.1.5-8): Will attempt migration (Any information below is purely informational)
• wmf/arm64 (1.0.5-8.1 to 1.0.5-8.1)
  • Migration status for wmf/arm64 (1.0.5-8.1 to 1.0.5-8.1): Will attempt migration (Any information below is purely informational)
• wordplay/arm64 (8.0-1 to 8.0-1)
  • Migration status for wordplay/arm64 (8.0-1 to 8.0-1): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• xlax/arm64 (2.4-2 to 2.4-2)
  • Migration status for xlax/arm64 (2.4-2 to 2.4-2): Will attempt migration (Any information below is purely informational)
• xmacro/arm64 (0.3pre-20000911-10 to 0.3pre-20000911-10)
  • Migration status for xmacro/arm64 (0.3pre-20000911-10 to 0.3pre-20000911-10): Will attempt migration (Any information below is purely informational)
• xmedcon_pu (0.25.1-gtk3+dfsg-1 to 0.23.0-gtk3+dfsg-1+deb12u2)
  • Migration status for xmedcon_pu (0.25.1-gtk3+dfsg-1 to 0.23.0-gtk3+dfsg-1+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: xmedcon is newer in the target suite (0.25.1-gtk3+dfsg-1 0.23.0-gtk3+dfsg-1+deb12u2)
• xserver-xorg-input-keyboard/arm64 (1:1.9.0-1 to 1:1.9.0-1)
  • Migration status for xserver-xorg-input-keyboard/arm64 (1:1.9.0-1 to 1:1.9.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-input-mouse/arm64 (1:1.9.3-1 to 1:1.9.3-1)
  • Migration status for xserver-xorg-input-mouse/arm64 (1:1.9.3-1 to 1:1.9.3-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-amdgpu/arm64 (23.0.0-1 to 23.0.0-1)
  • Migration status for xserver-xorg-video-amdgpu/arm64 (23.0.0-1 to 23.0.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-ati/arm64 (1:22.0.0-1 to 1:22.0.0-1)
  • Migration status for xserver-xorg-video-ati/arm64 (1:22.0.0-1 to 1:22.0.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-fbdev/arm64 (1:0.5.0-2 to 1:0.5.0-2)
  • Migration status for xserver-xorg-video-fbdev/arm64 (1:0.5.0-2 to 1:0.5.0-2): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-mga/arm64 (1:2.0.0-1 to 1:2.0.0-1)
  • Migration status for xserver-xorg-video-mga/arm64 (1:2.0.0-1 to 1:2.0.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-mga/armhf (1:2.0.0-1 to 1:2.0.0-1)
  • Migration status for xserver-xorg-video-mga/armhf (1:2.0.0-1 to 1:2.0.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-neomagic/armhf (1:1.3.0-2 to 1:1.3.0-2)
  • Migration status for xserver-xorg-video-neomagic/armhf (1:1.3.0-2 to 1:1.3.0-2): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-savage/arm64 (1:2.3.9-5 to 1:2.3.9-5)
  • Migration status for xserver-xorg-video-savage/arm64 (1:2.3.9-5 to 1:2.3.9-5): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-siliconmotion/arm64 (1:1.7.9-4 to 1:1.7.9-4)
  • Migration status for xserver-xorg-video-siliconmotion/arm64 (1:1.7.9-4 to 1:1.7.9-4): Will attempt migration (Any information below is purely informational)
• xss-lock/arm64 (0.3.0+git20230128.0c562b-1 to 0.3.0+git20230128.0c562b-1)
  • Migration status for xss-lock/arm64 (0.3.0+git20230128.0c562b-1 to 0.3.0+git20230128.0c562b-1): Will attempt migration (Any information below is purely informational)
• xz-utils_pu (5.6.4-1 to 5.4.1-1)
  • Migration status for xz-utils_pu (5.6.4-1 to 5.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: xz-utils is newer in the target suite (5.6.4-1 5.4.1-1)
• yafc/arm64 (1.3.7-5 to 1.3.7-5)
  • Migration status for yafc/arm64 (1.3.7-5 to 1.3.7-5): Will attempt migration (Any information below is purely informational)
• yorick-hdf5/arm64 (0.8.0-9 to 0.8.0-9)
  • Migration status for yorick-hdf5/arm64 (0.8.0-9 to 0.8.0-9): Will attempt migration (Any information below is purely informational)
• yorick-hdf5/armhf (0.8.0-9 to 0.8.0-9)
  • Migration status for yorick-hdf5/armhf (0.8.0-9 to 0.8.0-9): Will attempt migration (Any information below is purely informational)
• yorick-hdf5/i386 (0.8.0-9 to 0.8.0-9)
  • Migration status for yorick-hdf5/i386 (0.8.0-9 to 0.8.0-9): Will attempt migration (Any information below is purely informational)
• zile/arm64 (2.6.2-2 to 2.6.2-2)
  • Migration status for zile/arm64 (2.6.2-2 to 2.6.2-2): Will attempt migration (Any information below is purely informational)
• ziproxy/arm64 (3.3.2-7 to 3.3.2-7)
  • Migration status for ziproxy/arm64 (3.3.2-7 to 3.3.2-7): Will attempt migration (Any information below is purely informational)
• alien-arena (- to 7.71.7+dfsg-1)
  • Migration status for alien-arena (- to 7.71.7+dfsg-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 mips64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• billiard (4.2.1-1 to 4.2.1-2)
  • Migration status for billiard (4.2.1-1 to 4.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for billiard/4.2.1-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating billiard will fix bugs in testing: #1101621, #1102286
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/billiard.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• blueman (2.4.3-1 to 2.4.4-1)
  • Migration status for blueman (2.4.3-1 to 2.4.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blueman.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• castle-game-engine (7.0~alpha.3+dfsg2-3 to 7.0~alpha.3+dfsg2-4)
  • Migration status for castle-game-engine (7.0~alpha.3+dfsg2-3 to 7.0~alpha.3+dfsg2-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/castle-game-engine.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cdbs (0.4.170 to 0.4.171)
  • Migration status for cdbs (0.4.170 to 0.4.171): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for lintian/2.122.0: amd64: Pass, arm64: Pass, armel: Pass, armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdbs.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cleware-traffic-light (- to 1.0.8~git20240522.f5e418d-1)
  • Migration status for cleware-traffic-light (- to 1.0.8~git20240522.f5e418d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cleware-traffic-light.html
    • autopkgtest for cleware-traffic-light/1.0.8~git20240522.f5e418d-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ddcutil (2.2.0-1 to 2.2.0-2)
  • Migration status for ddcutil (2.2.0-1 to 2.2.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddcutil.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• debugpy (1.8.8+ds-2 to 1.8.12+ds-1)
  • Migration status for debugpy (1.8.8+ds-2 to 1.8.12+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for debugpy/1.8.12+ds-1: amd64: Pass, armhf: Pass, i386: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debugpy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• django-fsm-2 (- to 4.0.0-1)
  • Migration status for django-fsm-2 (- to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sur5r@sur5r.net, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-fsm-2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dnscrypt-proxy (2.1.7+ds1-1 to 2.1.8+ds1-1)
  • Migration status for dnscrypt-proxy (2.1.7+ds1-1 to 2.1.8+ds1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for dnscrypt-proxy/2.1.8+ds1-1: amd64: Pass, i386: Pass, ppc64el: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnscrypt-proxy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dolphin-emu (2412+dfsg-1 to 2503+dfsg-1)
  • Migration status for dolphin-emu (2412+dfsg-1 to 2503+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolphin-emu.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fstl (0.10.0-2 to 0.11.0-1)
  • Migration status for fstl (0.10.0-2 to 0.11.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fstl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• glosstex (0.4.dfsg.1-5 to 0.4.dfsg.1-6)
  • Migration status for glosstex (0.4.dfsg.1-5 to 0.4.dfsg.1-6): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glosstex.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-browser-connector (42.1-5 to 42.1-6)
  • Migration status for gnome-browser-connector (42.1-5 to 42.1-6): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-browser-connector.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-mines (1:48~alpha.2-1 to 1:48.0-1)
  • Migration status for gnome-mines (1:48~alpha.2-1 to 1:48.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-mines.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-network-displays (0.94.0-1 to 0.96.0-1)
  • Migration status for gnome-network-displays (0.94.0-1 to 0.96.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-network-displays.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-shell-extension-manager (0.6.2-1 to 0.6.3-1)
  • Migration status for gnome-shell-extension-manager (0.6.2-1 to 0.6.3-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on armhf
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-manager.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-shell-extension-runcat (28-1 to 29-1)
  • Migration status for gnome-shell-extension-runcat (28-1 to 29-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-runcat.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-shell-extension-weather (139-2 to 139-3)
  • Migration status for gnome-shell-extension-weather (139-2 to 139-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-weather.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnss-sdr (0.0.19-2.1 to 0.0.20-1)
  • Migration status for gnss-sdr (0.0.19-2.1 to 0.0.20-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 gnss-sdr/0.0.20-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnss-sdr.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• graphicsmagick (1.4+really1.3.45+hg17692-1 to 1.4+really1.3.45+hg17696-1)
  • Migration status for graphicsmagick (1.4+really1.3.45+hg17692-1 to 1.4+really1.3.45+hg17696-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armhf
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graphicsmagick.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gridengine (- to 8.1.9+dfsg-13)
  • Migration status for gridengine (- to 8.1.9+dfsg-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gridengine-client/amd64 has unsatisfiable dependency
    • gridengine-exec/amd64 has unsatisfiable dependency
    • gridengine-qmon/amd64 has unsatisfiable dependency
    • gridengine-client/armel has unsatisfiable dependency
    • gridengine-exec/armel has unsatisfiable dependency
    • gridengine-qmon/armel has unsatisfiable dependency
    • gridengine-client/i386 has unsatisfiable dependency
    • gridengine-exec/i386 has unsatisfiable dependency
    • gridengine-qmon/i386 has unsatisfiable dependency
    • gridengine-client/mips64el has unsatisfiable dependency
    • gridengine-exec/mips64el has unsatisfiable dependency
    • gridengine-qmon/mips64el has unsatisfiable dependency
    • gridengine-client/ppc64el has unsatisfiable dependency
    • gridengine-exec/ppc64el has unsatisfiable dependency
    • gridengine-qmon/ppc64el has unsatisfiable dependency
    • missing build on arm64
    • missing build on armhf
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gridengine.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gtk4 (4.18.3+ds-1 to 4.18.4+ds-1)
  • Migration status for gtk4 (4.18.3+ds-1 to 4.18.4+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for game-data-packager/84: amd64: Failed (not a regression), arm64: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Pass, ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for gtk4/4.18.4+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for gtksourceview5/5.16.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • missing build on armel
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Depends: gtk4 glib2.0 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk4.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hedgewars (1.0.2-12 to 1.0.2-13)
  • Migration status for hedgewars (1.0.2-12 to 1.0.2-13): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hedgewars.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ibus-input-pad (1.4.99.20140916-3 to 1.5.0-1)
  • Migration status for ibus-input-pad (1.4.99.20140916-3 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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-input-pad.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• imap-tools (0.54.0+dfsg-1 to 1.10.0+dfsg-1)
  • Migration status for imap-tools (0.54.0+dfsg-1 to 1.10.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imap-tools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• khal (- to 1:0.11.3-6)
  • Migration status for khal (- to 1:0.11.3-6): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khal.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ldraw-parts (2303+ds-1 to 2502+ds-2)
  • Migration status for ldraw-parts (2303+ds-1 to 2502+ds-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• lemonldap-ng (2.20.2+ds-1 to 2.21.0+ds-2)
  • Migration status for lemonldap-ng (2.20.2+ds-1 to 2.21.0+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for lemonldap-ng/2.21.0+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lemonldap-ng.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libftdi1 (1.5-8 to 1.5-9)
  • Migration status for libftdi1 (1.5-8 to 1.5-9): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libftdi1.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libgepub (0.7.1-2 to 0.7.3-1)
  • Migration status for libgepub (0.7.1-2 to 0.7.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgepub.html
    • autopkgtest for libgepub/0.7.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libwiki-toolkit-plugin-diff-perl (0.12-4.1 to 0.12-5)
  • Migration status for libwiki-toolkit-plugin-diff-perl (0.12-4.1 to 0.12-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwiki-toolkit-plugin-diff-perl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• licenserecon (4.1 to 4.2)
  • Migration status for licenserecon (4.1 to 4.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/licenserecon.html
    • autopkgtest for licenserecon/4.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• lomiri-calendar-app (1.1.2-4 to 1.1.3-1)
  • Migration status for lomiri-calendar-app (1.1.2-4 to 1.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-calendar-app.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lua-zlib (1.2-4 to 1.3-1)
  • Migration status for lua-zlib (1.2-4 to 1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-zlib.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lutris (0.5.17-2 to 0.5.19-1)
  • Migration status for lutris (0.5.17-2 to 0.5.19-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• mastodon-el (1.1.12-1 to 2.0.0-1)
  • Migration status for mastodon-el (1.1.12-1 to 2.0.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mastodon-el.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mdbook (0.4.47+ds-1 to 0.4.48+ds-2)
  • Migration status for mdbook (0.4.47+ds-1 to 0.4.48+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mdbook unsatisfiable Build-Depends(-Arch) on arm64: librust-elasticlunr-rs-dev
    • mdbook unsatisfiable Build-Depends(-Arch) on armhf: librust-elasticlunr-rs-dev
    • mdbook unsatisfiable Build-Depends(-Arch) on mips64el: librust-elasticlunr-rs-dev
    • mdbook unsatisfiable Build-Depends(-Arch) on riscv64: librust-elasticlunr-rs-dev
    • mdbook unsatisfiable Build-Depends(-Arch) on s390x: librust-elasticlunr-rs-dev
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): mdbook rust-elasticlunr-rs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdbook.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• minio-client (0.0~20250312-2 to 0.0~20250403-2)
  • Migration status for minio-client (0.0~20250312-2 to 0.0~20250403-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for minio-client/0.0~20250403-2: armhf: Pass, i386: Pass, ppc64el: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minio-client.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mstflint (4.31.0+1-2 to 4.31.0+1-3)
  • Migration status for mstflint (4.31.0+1-2 to 4.31.0+1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by tzafrir
    • Not built on buildd: arch all binaries uploaded by tzafrir, a new source-only upload is needed to allow migration
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mstflint.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mtree-netbsd (20180822-8 to 20180822-9)
  • Migration status for mtree-netbsd (20180822-8 to 20180822-9): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on riscv64
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating mtree-netbsd will fix bugs in testing: #1034247
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mtree-netbsd.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mypy (1.15.0-4 to 1.15.0-5)
  • Migration status for mypy (1.15.0-4 to 1.15.0-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • missing build on i386
    • missing build on mips64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating mypy will fix bugs in testing: #1101856
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• netgen (6.2.2404+dfsg1-5 to 6.2.2501+dfsg1-4)
  • Migration status for netgen (6.2.2404+dfsg1-5 to 6.2.2501+dfsg1-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for netgen/6.2.2501+dfsg1-4: i386: Pass, ppc64el: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netgen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-d3-timer (1.0.10+~1.0.10-1 to 1.0.10+~1.0.10-2)
  • Migration status for node-d3-timer (1.0.10+~1.0.10-1 to 1.0.10+~1.0.10-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating node-d3-timer will fix bugs in testing: #1099251
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-d3-timer.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocaml-decimal (- to 1.0.2-1)
  • Migration status for ocaml-decimal (- to 1.0.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-decimal.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• onednn (3.7.1+ds-1 to 3.7.2+ds-1)
  • Migration status for onednn (3.7.1+ds-1 to 3.7.2+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 riscv64
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for onednn/3.7.2+ds-1: ppc64el: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onednn.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• orthanc (1.12.6+dfsg-1 to 1.12.7+dfsg-1)
  • Migration status for orthanc (1.12.6+dfsg-1 to 1.12.7+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orthanc/1.12.7+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for orthanc-python/5.0+ds-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for orthanc-wsi/3.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ospd-openvas (- to 22.8.2-1)
  • Migration status for ospd-openvas (- to 22.8.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
    • Depends: ospd-openvas openvas-scanner
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ospd-openvas.html
    • autopkgtest for ospd-openvas/22.8.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• patch (2.7.6-7 to 2.8-1)
  • Migration status for patch (2.7.6-7 to 2.8-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:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/patch.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pdns-recursor (5.2.0-5 to 5.2.1-1)
  • Migration status for pdns-recursor (5.2.0-5 to 5.2.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 pdns-recursor/5.2.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdns-recursor.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-crypt-gpg (1.6.9-5 to 1.6.10-1)
  • Migration status for php-crypt-gpg (1.6.9-5 to 1.6.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for php-crypt-gpg/1.6.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for roundcube/1.6.10+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-crypt-gpg.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• poppler (25.03.0-2 to 25.03.0-3)
  • Migration status for poppler (25.03.0-2 to 25.03.0-3): 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 poppler/25.03.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poppler.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• postgres-decoderbufs (3.1.0~cr1-1 to 3.1.0-1)
  • Migration status for postgres-decoderbufs (3.1.0~cr1-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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgres-decoderbufs.html
    • autopkgtest for postgres-decoderbufs/3.1.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• puppet-strings (- to 4.1.3-2)
  • Migration status for puppet-strings (- to 4.1.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for puppet-strings/4.1.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-strings.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pypaperless (- to 3.1.15-2)
  • Migration status for pypaperless (- to 3.1.15-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for pypaperless/3.1.15-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pypaperless.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pytest-unordered (- to 0.6.1-2)
  • Migration status for pytest-unordered (- to 0.6.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-unordered.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-advanced-alchemy (1.0.1-1 to 1.1.1-1)
  • Migration status for python-advanced-alchemy (1.0.1-1 to 1.1.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for python-advanced-alchemy/1.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-advanced-alchemy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-aiohasupervisor (- to 0.3.0-1)
  • Migration status for python-aiohasupervisor (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • autopkgtest for python-aiohasupervisor/0.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiohasupervisor.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-sdbus (0.13.0-1 to 0.14.0-1)
  • Migration status for python-sdbus (0.13.0-1 to 0.14.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for python-sdbus/0.14.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sdbus.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-securetar (- to 2025.2.1-2)
  • Migration status for python-securetar (- to 2025.2.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-securetar.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qemu (1:9.2.2+ds-1 to 1:10.0.0~rc2+ds-2)
  • Migration status for qemu (1:9.2.2+ds-1 to 1:10.0.0~rc2+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qemu would introduce bugs in testing: #1101599
    • autopkgtest for debusine/0.10.0: amd64: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for edk2/2025.02-5: amd64: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for ipxe/1.21.1+git20250317.42a29d56+dfsg-1: amd64: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for qemu/1:10.0.0~rc2+ds-2: amd64: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Pass
    • autopkgtest for systemd/257.5-1: amd64: Pass, s390x: Pass
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on riscv64
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qemu.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-cran-rtf (- to 0.4-14.1-2)
  • Migration status for r-cran-rtf (- to 0.4-14.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-rtf/0.4-14.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by plessy, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rtf.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rdkit (202409.6-2 to 202503.1-2)
  • Migration status for rdkit (202409.6-2 to 202503.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for coot/1.1.15+dfsg-1: amd64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • autopkgtest for rdkit/202503.1-2: amd64: Pass, ppc64el: Pass
    • missing build on arm64
    • missing build on mips64el
    • missing build on riscv64
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdkit.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-standalone (3.0~1 to 3.0~2)
  • Migration status for ruby-standalone (3.0~1 to 3.0~2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on s390x
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for ruby-standalone/3.0~2: amd64: Pass, arm64: Pass, armel: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-standalone.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-elasticlunr-rs (- to 3.0.2-1)
  • Migration status for rust-elasticlunr-rs (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by keyholding@ncts.me
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-elasticlunr-rs.html
    • autopkgtest for rust-elasticlunr-rs/3.0.2-1: amd64: Pass, armel: Pass, i386: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-escape-string (- to 0.1.2-1)
  • Migration status for rust-escape-string (- to 0.1.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch s390x binaries not found
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-escape-string.html
    • autopkgtest for rust-escape-string/0.1.2-1: amd64: Pass, armel: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-hstr (- to 0+20250327-1)
  • Migration status for rust-hstr (- to 0+20250327-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-hstr would introduce bugs in testing: #1102256
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hstr.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-microformats (- to 0.15.0-1)
  • Migration status for rust-microformats (- to 0.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-microformats has no binaries on any arch
    • Updating rust-microformats would introduce bugs in testing: #1050087
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-microformats rust-swc-core (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-swc-core (- to 21.0.1~ds-1)
  • Migration status for rust-swc-core (- to 21.0.1~ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-swc-core/21.0.1~ds-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-swc-core.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-tonic (0.12.3+dfsg-2 to 0.12.3+dfsg-3)
  • Migration status for rust-tonic (0.12.3+dfsg-2 to 0.12.3+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-tonic/0.12.3+dfsg-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Test in progress, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tonic.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sanlock (3.8.5-3 to 3.9.5-1)
  • Migration status for sanlock (3.8.5-3 to 3.9.5-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on i386
    • missing build on riscv64
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sanlock.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• snid (- to 0.3.0-1)
  • Migration status for snid (- 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 0 of 2 days old
    • Build-Depends(-Arch): snid golang-agwa-go-listener
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snid.html
    • autopkgtest for snid/0.3.0-1: amd64: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• spdlog (1:1.15.1+ds-1 to 1:1.15.2+ds-1)
  • Migration status for spdlog (1:1.15.1+ds-1 to 1:1.15.2+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • missing build on mips64el
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for bear/3.1.6-1: amd64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for cryfs/0.11.4-3: amd64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for dart/6.13.2+ds-3: amd64: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for dolfinx-mpc/0.9.1-1: amd64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for fenicsx-performance-tests/0.9.0-2: amd64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for gr-dab/0.5-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress
    • autopkgtest for gr-limesdr/3.0.1.10.69-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress
    • autopkgtest for j4-dmenu-desktop/3.2-1: amd64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for kodi/2:21.2+dfsg-4: amd64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for spdlog/1:1.15.2+ds-1: amd64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spdlog.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• spirv-llvm-translator-14 (- to 14.0.11-1)
  • Migration status for spirv-llvm-translator-14 (- to 14.0.11-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on mips64el
    • arch:amd64 not built yet, autopkgtest delayed there
    • autopkgtest for spirv-llvm-translator-14/14.0.11-1: arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): spirv-llvm-translator-14 llvm-toolchain-14 (not considered)
    • Depends: spirv-llvm-translator-14 llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-llvm-translator-14.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• splash (3.11.1-2 to 3.11.2-1)
  • Migration status for splash (3.11.1-2 to 3.11.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Depends: splash giza
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/splash.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• systemd (257.4-3 to 257.5-2)
  • Migration status for systemd (257.4-3 to 257.5-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating systemd will fix bugs in testing: #1101175
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/systemd.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• trac-tickettemplate (- to 1.0.1-2)
  • Migration status for trac-tickettemplate (- to 1.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trac-tickettemplate.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• vdo (8.3.0.71-2 to 8.3.1.1-1)
  • Migration status for vdo (8.3.0.71-2 to 8.3.1.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdo.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wtmpdb (0.72.0-1 to 0.72.0-2)
  • Migration status for wtmpdb (0.72.0-1 to 0.72.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for wtmpdb/0.72.0-2: amd64: Pass, arm64: Pass, armel: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wtmpdb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xsok (- to 1.02-23)
  • Migration status for xsok (- to 1.02-23): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xsok.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• youplot (- to 0.4.6-2)
  • Migration status for youplot (- to 0.4.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for youplot/0.4.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/youplot.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• adonthell (0.3.8-4 to 0.3.8-5)
  • Migration status for adonthell (0.3.8-4 to 0.3.8-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adonthell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• aiolimiter (- to 1.2.1-1.1)
  • Migration status for aiolimiter (- to 1.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiolimiter.html
    • autopkgtest for aiolimiter/1.2.1-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ansible-lint (25.1.3-1 to 25.2.1-1)
  • Migration status for ansible-lint (25.1.3-1 to 25.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): ansible-lint python-ansible-compat
    • Depends: ansible-lint python-ansible-compat
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ansible-lint.html
    • autopkgtest for ansible-lint/25.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• bbmap (39.18+dfsg-1 to 39.20+dfsg-2)
  • Migration status for bbmap (39.18+dfsg-1 to 39.20+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating bbmap will fix bugs in testing: #1102122
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bbmap.html
    • autopkgtest for bbmap/39.20+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• bisonc++ (6.09.00-1 to 6.09.01-1)
  • Migration status for bisonc++ (6.09.00-1 to 6.09.01-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bisonc++.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• blendsel (0.5 to 0.7)
  • Migration status for blendsel (0.5 to 0.7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blendsel.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• boost1.88 (- to 1.88.0~beta1-1)
  • Migration status for boost1.88 (- to 1.88.0~beta1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for boost1.88/1.88.0~beta1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boost1.88.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• calindori (24.12.1-1 to 24.12.3-1)
  • Migration status for calindori (24.12.1-1 to 24.12.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calindori.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cron (3.0pl1-195 to 3.0pl1-196)
  • Migration status for cron (3.0pl1-195 to 3.0pl1-196): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for bcron/0.11-23: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for cron/3.0pl1-196: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for inn2/2.7.3~rc1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for logcheck/1.4.3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for logrotate/3.22.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for mmdebstrap/1.5.6-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for octavia/16.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sbuild/0.88.5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sudo/1.9.16p2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for systemd-cron/2.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cron.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• crosshurd (1.7.61 to 1.7.62)
  • Migration status for crosshurd (1.7.61 to 1.7.62): Waiting for test 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/crosshurd.html
    • autopkgtest for crosshurd/1.7.62: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• crowdsec (- to 1.4.6-10)
  • Migration status for crowdsec (- to 1.4.6-10): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for crowdsec/1.4.6-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
    • Built-Using: crowdsec golang-github-mattn-go-sqlite3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• deal.ii (- to 9.6.2-3)
  • Migration status for deal.ii (- to 9.6.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Depends: deal.ii onetbb (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deal.ii.html
    • autopkgtest for deal.ii/9.6.2-3: amd64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• django-polymodels (1.8.0-1 to 1.8.1-1)
  • Migration status for django-polymodels (1.8.0-1 to 1.8.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-polymodels.html
    • autopkgtest for django-polymodels/1.8.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• dpb (0.0~git20241008+67f93e629 to 0.9~git20250406+4956e9080)
  • Migration status for dpb (0.0~git20241008+67f93e629 to 0.9~git20250406+4956e9080): Waiting for test 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/dpb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dput-ng (1.41 to 1.42)
  • Migration status for dput-ng (1.41 to 1.42): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for dgit/12.11: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for dput-ng/1.42: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for ubuntu-dev-tools/0.206: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating dput-ng will fix bugs in testing: #1078613
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dput-ng.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• egl-wayland (1:1.1.17-1 to 1:1.1.18-1)
  • Migration status for egl-wayland (1:1.1.17-1 to 1:1.1.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mutter/48.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/egl-wayland.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• falcosecurity-libs (- to 0.20.0-2)
  • Migration status for falcosecurity-libs (- to 0.20.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating falcosecurity-libs would introduce bugs in testing: #1100342
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for falcosecurity-libs/0.20.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • Too young, only 1 of 5 days old
    • Depends: falcosecurity-libs onetbb (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/falcosecurity-libs.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• far2l (2.6.4~beta+ds-2 to 2.6.5~beta+ds-1)
  • Migration status for far2l (2.6.4~beta+ds-2 to 2.6.5~beta+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/far2l.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• flask-sqlalchemy (3.1.1-3 to 3.1.1-4)
  • Migration status for flask-sqlalchemy (3.1.1-3 to 3.1.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating flask-sqlalchemy will fix bugs in testing: #1102177
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-sqlalchemy.html
    • autopkgtest for flask-sqlalchemy/3.1.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• flox (0.10.1-1 to 0.10.2-1)
  • Migration status for flox (0.10.1-1 to 0.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for flox/0.10.2-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flox.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fortunes-it (2.12-1 to 2.13-1)
  • Migration status for fortunes-it (2.12-1 to 2.13-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortunes-it.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• game-data-packager (84 to 85)
  • Migration status for game-data-packager (84 to 85): 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 game-data-packager will fix bugs in testing: #1102099
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for game-data-packager/85: i386: Pass
    • Required age reduced by 3 days because of autopkgtest
• gdal (3.10.2+dfsg-1 to 3.10.3+dfsg-1)
  • Migration status for gdal (3.10.2+dfsg-1 to 3.10.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdal.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gitlab (- to 17.6.5-1)
  • Migration status for gitlab (- to 17.6.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gitlab/amd64 has unsatisfiable dependency
    • gitlab/arm64 has unsatisfiable dependency
    • Updating gitlab would introduce bugs in testing: #1009942, #1102092, #983915
    • autopkgtest for gitlab/17.6.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): gitlab gitaly
    • Built-Using: gitlab gitaly
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-agwa-go-listener (- to 0.6.1-1.1)
  • Migration status for golang-agwa-go-listener (- to 0.6.1-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-agwa-go-listener.html
    • autopkgtest for golang-agwa-go-listener/0.6.1-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-mattn-go-sqlite3 (1.14.24~ds1-1 to 1.14.27~ds1-1)
  • Migration status for golang-github-mattn-go-sqlite3 (1.14.24~ds1-1 to 1.14.27~ds1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for golang-github-containers-image/5.34.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for golang-github-mattn-go-sqlite3/1.14.27~ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: 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/g/golang-github-mattn-go-sqlite3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-multiformats-go-varint (- to 0.0.7-2.1)
  • Migration status for golang-github-multiformats-go-varint (- to 0.0.7-2.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-multiformats-go-varint.html
    • autopkgtest for golang-github-multiformats-go-varint/0.0.7-2.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-k8s-sigs-randfill (- to 1.0.0-2)
  • Migration status for golang-k8s-sigs-randfill (- to 1.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-sigs-randfill.html
    • autopkgtest for golang-k8s-sigs-randfill/1.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-k8s-sigs-structured-merge-diff (4.6.0-2 to 4.6.0-3)
  • Migration status for golang-k8s-sigs-structured-merge-diff (4.6.0-2 to 4.6.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for golang-k8s-apimachinery/0.32.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for golang-k8s-client-go/0.32.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for golang-k8s-sigs-structured-merge-diff/4.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): golang-k8s-sigs-structured-merge-diff golang-k8s-sigs-randfill
    • Depends: golang-k8s-sigs-structured-merge-diff golang-k8s-sigs-randfill
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-sigs-structured-merge-diff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• grml-debootstrap (0.118 to 0.119)
  • Migration status for grml-debootstrap (0.118 to 0.119): Waiting for test 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/grml-debootstrap.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hw-detect (1.166 to 1.167)
  • Migration status for hw-detect (1.166 to 1.167): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for debian-edu-install/2.12.11: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ibus-typing-booster (2.27.29-1 to 2.27.30-1)
  • Migration status for ibus-typing-booster (2.27.29-1 to 2.27.30-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-typing-booster.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• iproute2 (6.14.0-1 to 6.14.0-2)
  • Migration status for iproute2 (6.14.0-1 to 6.14.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for autopkgtest/5.47: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for bash-completion/1:2.16.0-7: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for bettercap/2.33.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for bind9/1:9.20.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for charliecloud: riscv64: Test in progress
    • autopkgtest for chkrootkit/0.58b-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for dpdk/24.11.1-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for etcd/3.5.16-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for fai/6.3.1: amd64: Failed (not a regression), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for firejail/0.9.72-2.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for freedombox/25.6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for golang-github-containernetworking-plugins/1.1.1+ds1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for golang-github-containers-buildah/1.39.3+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for heartbeat/1:3.0.6-17: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for ifupdown/0.8.44: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for initramfs-tools/0.147: amd64: Pass, arm64: Failed (not a regression), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: Failed (not a regression), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for iproute2/6.14.0-2: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for isc-kea/2.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for kronosnet/1.30-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for netplan.io/1.1.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for nginx/1.26.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for openvswitch/3.5.0-1: amd64: Failed (not a regression), arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for podman/5.4.2+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-common/276: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-if-addrs/0.13.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for samba/2:4.22.0+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sos/4.9.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for strongswan/6.0.1-1: amd64: Failed (not a regression), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for systemd: riscv64: Test in progress
    • autopkgtest for systemd/257.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, s390x: Pass
    • autopkgtest for tang/15-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for unhide/20240510-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for vip-manager2/3.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for wireguard/1.0.20210914-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), 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/i/iproute2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jenkins-debian-glue (0.23.2 to 0.23.3)
  • Migration status for jenkins-debian-glue (0.23.2 to 0.23.3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jenkins-debian-glue.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jtreg7 (7.5.1+1+ds1-1 to 7.5.1+1+ds1-2)
  • Migration status for jtreg7 (7.5.1+1+ds1-1 to 7.5.1+1+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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jtreg7.html
    • autopkgtest for jtreg7/7.5.1+1+ds1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kalk (24.12.1-1 to 24.12.3-1)
  • Migration status for kalk (24.12.1-1 to 24.12.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kalk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kdiagram2 (2.8.0-3 to 2.8.0-4)
  • Migration status for kdiagram2 (2.8.0-3 to 2.8.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdiagram2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• koko (24.12.1-1 to 24.12.3-1)
  • Migration status for koko (24.12.1-1 to 24.12.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/koko.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kotlin (- to 1.3.31+ds1-3)
  • Migration status for kotlin (- to 1.3.31+ds1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): kotlin kotlinx-atomicfu
    • Build-Depends(-Arch): kotlin kotlinx-coroutines
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlin.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lavacli (- to 2.2.0-3)
  • Migration status for lavacli (- to 2.2.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for lavacli/2.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lavacli.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libconfig-model-itself-perl (2.023-1 to 2.025-1)
  • Migration status for libconfig-model-itself-perl (2.023-1 to 2.025-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating libconfig-model-itself-perl will fix bugs in testing: #1101994
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libconfig-model-itself-perl.html
    • autopkgtest for libconfig-model-itself-perl/2.025-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libimobiledevice (1.3.0+git20240701-4 to 1.3.0+git20250228-1)
  • Migration status for libimobiledevice (1.3.0+git20240701-4 to 1.3.0+git20250228-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for gvfs/1.57.2-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for kf6-solid/6.11.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libimobiledevice.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libsdl3-ttf (3.2.0+ds-1 to 3.2.2+ds-1)
  • Migration status for libsdl3-ttf (3.2.0+ds-1 to 3.2.2+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl3-ttf.html
    • autopkgtest for libsdl3-ttf/3.2.2+ds-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libsoftware-copyright-perl (0.014-1 to 0.015-1)
  • Migration status for libsoftware-copyright-perl (0.014-1 to 0.015-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/libs/libsoftware-copyright-perl.html
    • autopkgtest for libsoftware-copyright-perl/0.015-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libsolv (0.7.31-1 to 0.7.32-1)
  • Migration status for libsolv (0.7.31-1 to 0.7.32-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for libbssolv-perl/0.17-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsolv.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• litestar (- to 2.15.2-1)
  • Migration status for litestar (- to 2.15.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for litestar/2.15.2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻
    • Too young, only 1 of 5 days old
    • Build-Depends-Indep: litestar litestar-htmx (not considered)
    • Build-Depends-Indep: litestar python-polyfactory
    • Depends: litestar litestar-htmx (not considered)
    • Depends: litestar python-polyfactory
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/litestar.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mame (0.275+dfsg.1-3 to 0.276+dfsg.1-1)
  • Migration status for mame (0.275+dfsg.1-3 to 0.276+dfsg.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/m/mame.html
    • Reproducibility regression on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mlpack (4.5.1-1 to 4.6.0-1)
  • Migration status for mlpack (4.5.1-1 to 4.6.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlpack.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nano (8.3-1 to 8.4-1)
  • Migration status for nano (8.3-1 to 8.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nano.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nbc (1.2.1.r4+dfsg-13 to 1.2.1.r4+dfsg-14)
  • Migration status for nbc (1.2.1.r4+dfsg-13 to 1.2.1.r4+dfsg-14): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbc.html
    • autopkgtest for nbc/1.2.1.r4+dfsg-14: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• needrestart (3.9-1 to 3.10-1)
  • Migration status for needrestart (3.9-1 to 3.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/needrestart.html
    • autopkgtest for needrestart/3.10-1: amd64: Pass, arm64: Failed (not a regression), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• neutron-dynamic-routing (2:25.0.0-2 to 2:26.0.0-3)
  • Migration status for neutron-dynamic-routing (2:25.0.0-2 to 2:26.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for neutron-dynamic-routing/2:26.0.0-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends-Indep: neutron-dynamic-routing neutron
    • Depends: neutron-dynamic-routing neutron
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neutron-dynamic-routing.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-braces (3.0.3+~3.0.4-1 to 3.0.3+~3.0.5-1)
  • Migration status for node-braces (3.0.3+~3.0.4-1 to 3.0.3+~3.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-braces/3.0.3+~3.0.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for node-chokidar/3.6.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for node-micromatch/4.0.7+~4.0.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-braces.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-chokidar (3.6.0-2 to 3.6.0-3)
  • Migration status for node-chokidar (3.6.0-2 to 3.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 1 of 2 days old
  • Additional info:
    • Updating node-chokidar will fix bugs in testing: #1074735
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-chokidar.html
    • autopkgtest for node-chokidar/3.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• node-eslint-plugin-requirejs (- to 4.0.1-2)
  • Migration status for node-eslint-plugin-requirejs (- to 4.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-eslint-plugin-requirejs/4.0.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-eslint-plugin-requirejs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-http-server (- to 14.1.1+~cs3.16.36-1)
  • Migration status for node-http-server (- to 14.1.1+~cs3.16.36-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-http-server.html
    • autopkgtest for node-http-server/14.1.1+~cs3.16.36-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-immutable-tuple (0.4.10-11 to 0.4.10-13)
  • Migration status for node-immutable-tuple (0.4.10-11 to 0.4.10-13): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for node-immutable-tuple/0.4.10-13: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating node-immutable-tuple will fix bugs in testing: #1101242
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-immutable-tuple.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-kew (0.7.0-2 to 0.7.0-3)
  • Migration status for node-kew (0.7.0-2 to 0.7.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating node-kew will fix bugs in testing: #1082975
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-kew.html
    • autopkgtest for node-kew/0.7.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• node-node-rsa (- to 1.1.1-5)
  • Migration status for node-node-rsa (- to 1.1.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-rsa.html
    • autopkgtest for node-node-rsa/1.1.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• node-nunjucks (3.2.3+dfsg+~cs1.0.1-3 to 3.2.4+~cs4.2.7-1)
  • Migration status for node-nunjucks (3.2.3+dfsg+~cs1.0.1-3 to 3.2.4+~cs4.2.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-nunjucks.html
    • autopkgtest for node-nunjucks/3.2.4+~cs4.2.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• node-send (1.1.0+~cs1.19.4-2 to 1.2.0+~cs1.19.4-1)
  • Migration status for node-send (1.1.0+~cs1.19.4-2 to 1.2.0+~cs1.19.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for node-body-parser/1.20.3+~1.19.5-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for node-send/1.2.0+~cs1.19.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for node-serve-static/2.1.0+~1.15.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-send.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-serialize-javascript (6.0.1-1 to 6.0.2-1)
  • Migration status for node-serialize-javascript (6.0.1-1 to 6.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-compression-webpack-plugin/10.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for node-serialize-javascript/6.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for node-webpack/5.97.1+dfsg1+~cs11.18.27-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-serialize-javascript.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• opkssh (- to 0.4.0-1)
  • Migration status for opkssh (- to 0.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opkssh.html
    • autopkgtest for opkssh/0.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• os-autoinst (4.6.1731418769.97d9a7fd-3 to 4.6.1731418769.97d9a7fd-4)
  • Migration status for os-autoinst (4.6.1731418769.97d9a7fd-3 to 4.6.1731418769.97d9a7fd-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating os-autoinst will fix bugs in testing: #1101603
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/os-autoinst.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• oscs (- to 0.0.2)
  • Migration status for oscs (- to 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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oscs.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pg-auto-failover (2.2-1 to 2.2-2)
  • Migration status for pg-auto-failover (2.2-1 to 2.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for pg-auto-failover/2.2-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-auto-failover.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pglast (7.5-1 to 7.7-1)
  • Migration status for pglast (7.5-1 to 7.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/pglast.html
    • autopkgtest for pglast/7.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pineapple-pictures (0.9.1-1 to 0.9.2-1)
  • Migration status for pineapple-pictures (0.9.1-1 to 0.9.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pineapple-pictures.html
    • autopkgtest for pineapple-pictures/0.9.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-mobile (6.3.2-1 to 6.3.4-1)
  • Migration status for plasma-mobile (6.3.2-1 to 6.3.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-mobile kwin
    • Depends: plasma-mobile kwin
  • Additional info:
    • Updating plasma-mobile will fix bugs in testing: #1100380
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-mobile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-settings (25.02.0-1 to 25.02.0-2)
  • Migration status for plasma-settings (25.02.0-1 to 25.02.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-settings.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• policyd-rate-limit (1.0.1.1-2.2 to 1.2.0-1.1)
  • Migration status for policyd-rate-limit (1.0.1.1-2.2 to 1.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 1 of 5 days old
  • Additional info:
    • Updating policyd-rate-limit will fix bugs in testing: #1022034
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/policyd-rate-limit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• postgresql-17 (17.4-1 to 17.4-2)
  • Migration status for postgresql-17 (17.4-1 to 17.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cyrus-imapd/3.10.1-2: amd64: Pass, arm64: Test in progress (will not be considered a regression), ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for dbconfig-common/2.0.24: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for libreoffice/4:25.2.2-1: amd64: Pass, arm64: Pass, armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress, s390x: Pass
    • autopkgtest for mobilitydb/1.2.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for pdns/4.9.4-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pg-checksums/1.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pg-fact-loader/2.0.1-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for pg-failover-slots/1.1.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pg-squeeze/1.8.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pg-statviz/0.7-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgfincore/1.3.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgl-ddl-deploy/2.2.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pglogical/2.4.5-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pglogical-ticker/1.4.1-8: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgmemcache/2.3.0-14: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgnodemx/1.7-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgpcre/0.20190509-8: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgpointcloud/1.2.5-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgpool2/4.6.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgq/3.5-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgq-node/3.5-7: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgrouting/3.7.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgsphere/1.5.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgsql-asn1oid/1.6-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgsql-http/1.6.3-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for pgsql-ogr-fdw/1.1.6-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgstat/1.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgtap/1.3.3-3: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgtt/4.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pgvector/0.8.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php8.4/8.4.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pldebugger/1:1.8-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for plpgsql-check/2.8.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for plprofiler/4.2.5-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for plr/1:8.4.7-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postfix/3.10.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgis/3.5.2+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgres-decoderbufs/3.1.0~cr1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-16-age/1.5.0~rc0-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-17/17.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-common/276: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-debversion/1.2.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-hll/2.18-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for postgresql-mysql-fdw/2.9.2-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for postgresql-numeral/1.3-7: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-periods/1.2.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-pgmp/1.0.5-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-pllua/1:2.0.12-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-plproxy/2.11.0-12: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-plsh/1.20220917-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-prioritize/1.0.4-12: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-q3c/2.0.1-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-rum/1.3.14-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-semver/0.40.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-set-user/4.1.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postgresql-unit/7.10-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for powa-archivist/5.0.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for prefix/1.2.10-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for preprepare/0.9-9: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for proftpd-dfsg/1.3.8.c+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pspg/5.8.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for psqlodbc/1:17.00.0004-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for psycopg2/2.9.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for psycopg3/3.2.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pygresql/1:6.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for r-cran-rpostgresql/0.7-7+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rdkit/202409.6-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for redmine/6.0.4+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for repmgr/5.5.0+debpgdg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for request-tracker4/4.4.7+dfsg-4: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for request-tracker5/5.0.7+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for roundcube/1.6.10+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rsyslog/8.2502.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for ruby-pg/1.5.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for ruby-sequel-pg/1.14.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for rust-pq-sys/0.4.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for slony1-2/2.2.11-6: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for soci/4.0.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sqitch/1.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sqlsmith/1.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sysbench/1.0.20+ds-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for tablelog/0.6.4-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for tdigest/1.4.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for tds-fdw/2.0.4-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for timescaledb/2.19.1+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for tntdb/1.4-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for toastinfo/1.5-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for uwsgi/2.0.28-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for vtk9/9.3.0+dfsg1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for w1retap/1.5.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for wal2json/2.6-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgresql-17.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• primecount (7.15+ds-1 to 7.16+ds-1)
  • Migration status for primecount (7.15+ds-1 to 7.16+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/primecount.html
    • autopkgtest for primecount/7.16+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• propaganda-debian (13.5.10+nmu1 to 13.5.11)
  • Migration status for propaganda-debian (13.5.10+nmu1 to 13.5.11): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/propaganda-debian.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• puppet-module-neutron (25.0.0-4 to 25.0.0-5)
  • Migration status for puppet-module-neutron (25.0.0-4 to 25.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-neutron.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pydantic (2.10.6-1 to 2.10.6-2)
  • Migration status for pydantic (2.10.6-1 to 2.10.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for aiopurpleair/2023.12.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for debusine/0.10.0: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for deepdiff/8.1.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for fastapi/0.115.11-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for flask-openapi3/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for geojson-pydantic/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for monty/2025.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pydantic/2.10.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pydantic-settings/2.8.1-1: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for python-aioopenexchangerates/0.4.14-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-confection/0.1.5-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-datamodel-code-generator/0.26.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-gcal-sync/7.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-ical/9.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-lazy-model/0.2.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-maggma/0.70.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-maison/2.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-odmantic/1.0.2-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-openai/1.69.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-sigstore-protobuf-specs/0.3.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-sigstore-rekor-types/0.0.18-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-youtubeaio/1.1.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for qcelemental/0.29.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for scalene/1.5.51-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for stravalib/2.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for zwave-js-server-python/0.62.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): pydantic pydantic-core (not considered)
  • Additional info:
    • Updating pydantic will fix bugs in testing: #1102283
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydantic.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pyepr (1.1.5-2 to 1.2.0-1)
  • Migration status for pyepr (1.1.5-2 to 1.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyepr.html
    • autopkgtest for pyepr/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pygnuplot (0.11.16-5 to 0.12.3-1)
  • Migration status for pygnuplot (0.11.16-5 to 0.12.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pygnuplot.html
    • autopkgtest for pygnuplot/0.12.3-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pysolfc (3.1.0-2 to 3.2.0-1)
  • Migration status for pysolfc (3.1.0-2 to 3.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc.html
    • autopkgtest for pysolfc/3.2.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-ansible-compat (25.1.4-1 to 25.1.5-1)
  • Migration status for python-ansible-compat (25.1.4-1 to 25.1.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ansible-compat.html
    • autopkgtest for python-ansible-compat/25.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-gflanguages (0.7.2-2 to 0.7.2-3)
  • Migration status for python-gflanguages (0.7.2-2 to 0.7.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gflanguages.html
    • autopkgtest for python-gflanguages/0.7.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-glyphsets (1.0.0-2 to 1.0.0-3)
  • Migration status for python-glyphsets (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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-glyphsets.html
    • autopkgtest for python-glyphsets/1.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-griffe-typingdoc (- to 0.2.8-2)
  • Migration status for python-griffe-typingdoc (- to 0.2.8-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-griffe-typingdoc.html
    • autopkgtest for python-griffe-typingdoc/0.2.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-mne (1.9.0-1 to 1.9.0-2)
  • Migration status for python-mne (1.9.0-1 to 1.9.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating python-mne will fix bugs in testing: #1100273
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mne.html
    • autopkgtest for python-mne/1.9.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-pyo (- to 1.0.6-1)
  • Migration status for python-pyo (- to 1.0.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for python-pyo/1.0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyo.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-typing-extensions (4.13.0-1 to 4.13.1-1)
  • Migration status for python-typing-extensions (4.13.0-1 to 4.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for app-model/0.3.0-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for automat/24.8.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for beets/2.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for bleak/0.22.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for bpython/0.25-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for django-countries/7.6.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for domdf-python-tools/3.10.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for fastapi/0.115.11-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for flake8-noqa/1.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for hypercorn/0.17.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for ipython/8.30.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for magicgui/0.9.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for mkdocstrings-python-handlers/1.16.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for nibabel/5.3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for plastex/3.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pydantic/2.10.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pydantic-core/2.27.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pydantic-extra-types/2.10.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pylint/3.3.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pypdf/4.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pyscard/2.2.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pytest-check/2.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-advanced-alchemy/1.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-aiosqlite/0.21.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-anyio/4.8.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-async-lru/2.0.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-asyncssh/2.20.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-bioblend/1.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-cloup/3.0.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-coincidence/0.6.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-cyclopts/3.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-django-solo/2.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-emmet-core/0.84.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-globus-sdk/3.54.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-hatch-fancy-pypi-readme/24.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-inline-snapshot/0.20.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-keystoneauth1/5.10.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-marshmallow-sqlalchemy/1.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-memray/1.17.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-odmantic/1.0.2-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-openai/1.69.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-parsl/2025.01.13+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-pint/0.24.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-pynvim/0.5.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-pytest-subtests/0.13.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-pyvista/0.44.1-11: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-returns/0.25.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-ring-doorbell/0.9.13-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-rx/4.0.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-shippinglabel/2.1.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-signedjson/1.1.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-sphinx-autodoc2/0.5.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-transmission-rpc/7.0.11-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-treq/24.9.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-twomemo/1.1.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-typing-extensions/4.13.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-utils/3.9.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-uvicorn/0.32.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-x3dh/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pyvisa-py/0.7.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for pyvisa-sim/0.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rstcheck/6.2.4+~1.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for scikit-rf/1.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for slixmpp-omemo/1.2.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sphinx-theme-builder/0.2.0b2-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sqlmodel/0.0.24-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for starlette/0.46.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for tox/4.25.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for tox-uv/1.25.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for yt/4.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-typing-extensions.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pytroll-schedule (0.7.2-2 to 0.7.2-3)
  • Migration status for pytroll-schedule (0.7.2-2 to 0.7.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating pytroll-schedule will fix bugs in testing: #1101594
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytroll-schedule.html
    • autopkgtest for pytroll-schedule/0.7.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qpdf (12.0.0-2 to 12.1.0-1)
  • Migration status for qpdf (12.0.0-2 to 12.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpdf.html
    • autopkgtest for qpdf/12.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• r-bioc-ihw (1.34.0+dfsg-2 to 1.34.0+dfsg-3)
  • Migration status for r-bioc-ihw (1.34.0+dfsg-2 to 1.34.0+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for r-bioc-ihw/1.34.0+dfsg-3: amd64: Failed (not a regression), arm64: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Reference test in progress, but real test failed already ♻, s390x: Failed (not a regression)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): r-bioc-ihw r-bioc-lpsymphony
  • Additional info:
    • Updating r-bioc-ihw will fix bugs in testing: #1101711
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ihw.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-bioc-lpsymphony (1.34.0+dfsg-2 to 1.34.0+dfsg-3)
  • Migration status for r-bioc-lpsymphony (1.34.0+dfsg-2 to 1.34.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 1 of 2 days old
  • Additional info:
    • Updating r-bioc-lpsymphony will fix bugs in testing: #1101251
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-lpsymphony.html
    • autopkgtest for r-bioc-lpsymphony/1.34.0+dfsg-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• r-cran-quantmod (0.4.26-1 to 0.4.27-1)
  • Migration status for r-cran-quantmod (0.4.26-1 to 0.4.27-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-quantmod.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-cran-seurat (5.2.1-4 to 5.2.1-5)
  • Migration status for r-cran-seurat (5.2.1-4 to 5.2.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-seurat.html
    • autopkgtest for r-cran-seurat/5.2.1-5: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-cran-writexl (1.5.2-1 to 1.5.3-1)
  • Migration status for r-cran-writexl (1.5.2-1 to 1.5.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-writexl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• recode (3.7.14-3 to 3.7.15-1)
  • Migration status for recode (3.7.14-3 to 3.7.15-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/recode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• reqwest (- to 2.0.5+dfsg-2)
  • Migration status for reqwest (- to 2.0.5+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reqwest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• retroarch-assets (1.19.0+dfsg-1 to 1.20.0+dfsg-1)
  • Migration status for retroarch-assets (1.19.0+dfsg-1 to 1.20.0+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/retroarch-assets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rheolef (- to 7.2-4)
  • Migration status for rheolef (- to 7.2-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rheolef.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ruby-graphql (2.2.5-3 to 2.2.17-1)
  • Migration status for ruby-graphql (2.2.5-3 to 2.2.17-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating ruby-graphql will fix bugs in testing: #1100442
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-graphql.html
    • autopkgtest for ruby-graphql/2.2.17-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruptime (1.8-3 to 1.8-4)
  • Migration status for ruptime (1.8-3 to 1.8-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruptime.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-eza (0.20.24-1 to 0.21.0-1)
  • Migration status for rust-eza (0.20.24-1 to 0.21.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-eza.html
    • autopkgtest for rust-eza/0.21.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-findutils (0.7.0-3 to 0.8.0-1)
  • Migration status for rust-findutils (0.7.0-3 to 0.8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-findutils rust-uucore (not considered)
    • Depends: rust-findutils rust-uucore (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-findutils.html
    • autopkgtest for rust-findutils/0.8.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-gstreamer-audio (0.23.0-2 to 0.23.5-3)
  • Migration status for rust-gstreamer-audio (0.23.0-2 to 0.23.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gstreamer-audio/0.23.5-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gstreamer-audio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-libseat-sys (- to 0.1.9-2)
  • Migration status for rust-libseat-sys (- to 0.1.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-libseat-sys-dev/amd64 has unsatisfiable dependency
    • librust-libseat-sys-dev/arm64 has unsatisfiable dependency
    • librust-libseat-sys-dev/armel has unsatisfiable dependency
    • librust-libseat-sys-dev/armhf has unsatisfiable dependency
    • librust-libseat-sys-dev/i386 has unsatisfiable dependency
    • librust-libseat-sys-dev/mips64el has unsatisfiable dependency
    • librust-libseat-sys-dev/ppc64el has unsatisfiable dependency
    • librust-libseat-sys-dev/riscv64 has unsatisfiable dependency
    • librust-libseat-sys-dev/s390x has unsatisfiable dependency
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-libseat-sys.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-numbat-cli (1.11.0-2 to 1.11.0-3)
  • Migration status for rust-numbat-cli (1.11.0-2 to 1.11.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating rust-numbat-cli will fix bugs in testing: #1101585
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-numbat-cli.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-quote (1.0.37-1 to 1.0.40-1)
  • Migration status for rust-quote (1.0.37-1 to 1.0.40-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-axum/0.7.9-13: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-ntest-timeout/0.9.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for rust-postgres-derive/0.4.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-quote/1.0.40-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-rinja-derive/0.3.5-2: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for rust-shrinkwraprs/0.3.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-signature/2.2.0+ds-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-test-with/0.12.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-thiserror-impl-no-std/2.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-tokio-macros/2.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-tracing-attributes/0.1.27-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-trait-variant/0.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-typed-builder-macro/0.20.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-upstream-ontologist/0.2.1-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for rust-urid-derive/0.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-usb-ids/1.2025.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-valuable-derive/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-versionize-derive/0.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-vte-generate-state-changes/0.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-wasm-bindgen-backend/0.2.99-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-wasm-bindgen-macro-support/0.2.99-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-wezterm-dynamic-derive/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-zbus-macros-1/1.9.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-zerofrom-derive/0.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-zvariant-utils/3.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-quote.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-syn (2.0.96-2 to 2.0.98-1)
  • Migration status for rust-syn (2.0.96-2 to 2.0.98-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-alacritty-config-derive/0.2.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-asn1-derive/0.20.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-asn1-rs/0.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-asn1-rs-impl/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-automod/1.0.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-axum/0.7.9-13: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-bindgen/0.71.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-blanket/0.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-build-time/0.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-bytemuck-derive/1.5.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-cbindgen/0.27.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-clap-derive/4.5.18-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-color-print-proc-macro/0.3.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-cpp-build/0.5.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-cpp-macros/0.5.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-curve25519-dalek/4.1.3+20240618+dfsg-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-cxx-gen/0.7.141-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-cxxbridge-macro/1.0.141-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-darling-core/0.20.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-databake-derive/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-deb822-derive/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-defmt-macros/0.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-deluxe-core/0.5.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-deluxe-macros/0.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-derive-arbitrary/1.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-derive-builder-core/0.20.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-derive-builder-macro/0.20.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-derive-deftly/1.0.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-derive-destructure2/0.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-derive-more-0.99/0.99.18-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-derive-more-impl/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-derive-where/1.2.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-diesel-derives/2.2.3-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for rust-dir-test-macros/0.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-displaydoc/0.2.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-dyn-clonable-impl/0.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-enum-iterator-derive/1.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-enum-map-derive/0.17.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-enum-ordinalize/3.1.13-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-enumflags2-derive/0.7.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-futures-macro/0.3.31-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-git-testament-derive/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-gix-macros/0.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-glib-macros/0.20.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-glib-macros-0.18/0.18.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-gtk3-macros-0.18/0.18.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-gtk4-macros/0.9.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-html5ever/0.27.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-i18n-embed-fl/0.9.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-interpolate-name/0.2.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-jj-lib-proc-macros/0.22.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-juniper-codegen/0.16.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-lazy-regex/3.4.1+20241227-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-lofty-attr/0.11.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-macrotest/1.0.13-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-magnus-macros/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-miette-derive/7.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-mockall-derive/0.13.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-munge-macro/0.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-nalgebra-macros/0.2.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for rust-no-panic/0.1.32-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for rust-openssl-macros/0.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-palette-derive/0.7.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-pest-generator/2.7.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-pin-project-internal/1.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-pmutil/0.6.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-powerfmt-macros/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-prettyplease/0.2.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-profiling-procmacros/1.0.16-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-prost-build/0.12.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-ptr-meta-derive/0.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-pyo3-async-runtimes-macros/0.22.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-pyo3-macros/0.22.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-pyo3-macros-backend/0.22.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-railway-api-derive/0.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-random-number-macro-impl/0.1.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-ref-cast-impl/1.0.23-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-rkyv-derive/0.8.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-rust-embed-impl/8.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-sailfish-compiler/0.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-schemars-derive/0.8.21-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-serde-derive/1.0.217-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-serde-derive-internals/0.29.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-serial-test-derive/2.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-smart-default/0.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-sqlx-macros-core/0.8.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-stability/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-strum-macros/0.26.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-sval-derive/2.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-syn/2.0.98-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-syn-derive/0.1.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-tabled-derive/0.10.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-test-casing-macro/0.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-test-log-macros/0.2.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-test-with/0.12.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-thiserror-impl/2.0.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-tokio-macros/2.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-tonic/0.12.3+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-trait-variant/0.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-version-sync/0.9.5-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-wasm-bindgen-backend/0.2.99-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-wasm-bindgen-macro-support/0.2.99-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-wrapcenum-derive/0.4.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-zbus-macros/5.3.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-zerocopy-derive/0.7.34-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-zerofrom-derive/0.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-zerovec-derive/0.11.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-zvariant-utils/3.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-syn.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-uucore (0.0.23-3.1 to 0.0.30-1)
  • Migration status for rust-uucore (0.0.23-3.1 to 0.0.30-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-uucore/0.0.30-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-uucore rust-uucore-procs
    • Depends: rust-uucore rust-utmp-classic (not considered)
    • Depends: rust-uucore rust-uucore-procs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-uucore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-uucore-procs (0.0.23-1 to 0.0.30-1)
  • Migration status for rust-uucore-procs (0.0.23-1 to 0.0.30-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-uucore-procs rust-uuhelp-parser
    • Depends: rust-uucore-procs rust-uuhelp-parser
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-uucore-procs.html
    • autopkgtest for rust-uucore-procs/0.0.30-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-uuhelp-parser (0.0.23-1 to 0.0.30-1)
  • Migration status for rust-uuhelp-parser (0.0.23-1 to 0.0.30-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
    • Implicit dependency: rust-uuhelp-parser rust-uucore-procs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-uuhelp-parser.html
    • autopkgtest for rust-uuhelp-parser/0.0.30-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ruy (0.0.0~git20230215.21a85fe-1 to 0.0.0~git20230215.21a85fe-2)
  • Migration status for ruy (0.0.0~git20230215.21a85fe-1 to 0.0.0~git20230215.21a85fe-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/r/ruy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sail (0.9.7-1 to 0.9.8-1)
  • Migration status for sail (0.9.7-1 to 0.9.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• satdump (- to 1.2.2-1)
  • Migration status for satdump (- 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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/satdump.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• scriv (1.5.1-2 to 1.6.2-1)
  • Migration status for scriv (1.5.1-2 to 1.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scriv.html
    • autopkgtest for scriv/1.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• sdkmanager (0.6.11-1 to 0.6.11-2)
  • Migration status for sdkmanager (0.6.11-1 to 0.6.11-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdkmanager.html
    • autopkgtest for sdkmanager/0.6.11-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• selint (1.5.1-1 to 1.5.1-2)
  • Migration status for selint (1.5.1-1 to 1.5.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for selint/1.5.1-2: amd64: Pass, arm64: Pass, armel: 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/s/selint.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• selinux-basics (0.5.9 to 0.6.0)
  • Migration status for selinux-basics (0.5.9 to 0.6.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/s/selinux-basics.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• skopeo (1.17.0+ds1-1 to 1.18.0+ds1-1)
  • Migration status for skopeo (1.17.0+ds1-1 to 1.18.0+ds1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for skopeo/1.18.0+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
    • Built-Using: skopeo golang-github-mattn-go-sqlite3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skopeo.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• slidge (0.2.8-1 to 0.2.9-1)
  • Migration status for slidge (0.2.8-1 to 0.2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for slidge/0.2.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for slidge-matridge/0.2.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slidge.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• slidge-matridge (0.2.0-2 to 0.2.2-1)
  • Migration status for slidge-matridge (0.2.0-2 to 0.2.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slidge-matridge.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• spacebar (1:6.2.4-2 to 1:6.3.4-1)
  • Migration status for spacebar (1:6.2.4-2 to 1:6.3.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spacebar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• speech-dispatcher (0.12.0-2 to 0.12.0-3)
  • Migration status for speech-dispatcher (0.12.0-2 to 0.12.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for calibre/8.2.1+ds-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for speech-dispatcher/0.12.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/speech-dispatcher.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sphinx-external-toc (- to 1.0.1-1)
  • Migration status for sphinx-external-toc (- to 1.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): sphinx-external-toc sphinx-book-theme
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-external-toc.html
    • autopkgtest for sphinx-external-toc/1.0.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• stalin (0.11-7 to 0.11-10)
  • Migration status for stalin (0.11-7 to 0.11-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
  • Additional info:
    • Updating stalin will fix bugs in testing: #1101384
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stalin.html
    • autopkgtest for stalin/0.11-10: amd64: Pass, arm64: Pass, i386: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• strawberry (1.2.7-2 to 1.2.8-1)
  • Migration status for strawberry (1.2.7-2 to 1.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/s/strawberry.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• streamlink (7.1.3-1 to 7.2.0-1)
  • Migration status for streamlink (7.1.3-1 to 7.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/streamlink.html
    • autopkgtest for streamlink/7.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• subversion (1.14.5-2 to 1.14.5-3)
  • Migration status for subversion (1.14.5-2 to 1.14.5-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/subversion.html
    • autopkgtest for subversion/1.14.5-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• synaptic (0.91.6 to 0.91.7)
  • Migration status for synaptic (0.91.6 to 0.91.7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating synaptic will fix bugs in testing: #1062190
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synaptic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sysdig (- to 0.40.0+repack-2)
  • Migration status for sysdig (- to 0.40.0+repack-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sysdig would introduce bugs in testing: #1066959
    • missing build on ppc64el
    • missing build on s390x
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): sysdig falcosecurity-libs (not considered)
    • Depends: sysdig falcosecurity-libs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysdig.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• systemd-boot-efi-amd64-signed (257.4+3 to 257.5+1)
  • Migration status for systemd-boot-efi-amd64-signed (257.4+3 to 257.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
    • Build-Depends(-Arch): systemd-boot-efi-amd64-signed systemd (not considered)
    • Built-Using: systemd-boot-efi-amd64-signed systemd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/systemd-boot-efi-amd64-signed.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• systemd-boot-efi-arm64-signed (257.4+3 to 257.5+1)
  • Migration status for systemd-boot-efi-arm64-signed (257.4+3 to 257.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
    • Build-Depends(-Arch): systemd-boot-efi-arm64-signed systemd (not considered)
    • Built-Using: systemd-boot-efi-arm64-signed systemd (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• t2n (0.7-1 to 0.7-2)
  • Migration status for t2n (0.7-1 to 0.7-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/t2n.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tox-current-env (0.0.14-1 to 0.0.16-1)
  • Migration status for tox-current-env (0.0.14-1 to 0.0.16-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for tox-current-env/0.0.16-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tox-current-env.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ufolib2 (0.17.0+dfsg1-1 to 0.17.1+dfsg1-1)
  • Migration status for ufolib2 (0.17.0+dfsg1-1 to 0.17.1+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for fonttools/4.55.3-2: riscv64: Pass
    • autopkgtest for glyphslib/6.9.5+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for ufolib2/0.17.1+dfsg1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ufolib2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ufoprocessor (1.13.2-1 to 1.13.3-1)
  • Migration status for ufoprocessor (1.13.2-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/u/ufoprocessor.html
    • autopkgtest for ufoprocessor/1.13.3-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ukui-sidebar (3.1.2-2 to 3.1.3-1)
  • Migration status for ukui-sidebar (3.1.2-2 to 3.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-sidebar.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• uml-utilities (- to 20070815.4-2)
  • Migration status for uml-utilities (- to 20070815.4-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uml-utilities.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• veryfasttree (4.0.4+dfsg-1 to 4.0.4+dfsg-2)
  • Migration status for veryfasttree (4.0.4+dfsg-1 to 4.0.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/veryfasttree.html
    • autopkgtest for veryfasttree/4.0.4+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• wine (9.0~repack-7 to 10.0~repack-3)
  • Migration status for wine (9.0~repack-7 to 10.0~repack-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for matomo/5.2.2+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating wine will fix bugs in testing: #1094858, #1100695
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wp2latex (4.14~ds-1 to 4.15~ds-1)
  • Migration status for wp2latex (4.14~ds-1 to 4.15~ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wp2latex.html
    • autopkgtest for wp2latex/4.15~ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• xarray-sentinel (0.9.5+ds-3 to 0.9.5+ds-4)
  • Migration status for xarray-sentinel (0.9.5+ds-3 to 0.9.5+ds-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating xarray-sentinel will fix bugs in testing: #1101633
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xarray-sentinel.html
    • autopkgtest for xarray-sentinel/0.9.5+ds-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• yquake2 (8.41+dfsg-1 to 8.50+dfsg-1)
  • Migration status for yquake2 (8.41+dfsg-1 to 8.50+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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• yt-dlp (2025.03.27-1 to 2025.03.31-1)
  • Migration status for yt-dlp (2025.03.27-1 to 2025.03.31-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for gallery-dl/1.29.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for yt-dlp/2025.03.31-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: 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/y/yt-dlp.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• zc.buildout (4.0-1 to 4.1.6-1)
  • Migration status for zc.buildout (4.0-1 to 4.1.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zc.buildout.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• zycore-c (1.5.1-1 to 1.5.2-1)
  • Migration status for zycore-c (1.5.1-1 to 1.5.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zycore-c.html
    • autopkgtest for zycore-c/1.5.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• zydis (4.1.0-3 to 4.1.1-1)
  • Migration status for zydis (4.1.0-3 to 4.1.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zydis.html
    • autopkgtest for zydis/4.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• afflib (3.7.20-2 to 3.7.21-1)
  • Migration status for afflib (3.7.20-2 to 3.7.21-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/afflib.html
    • autopkgtest for afflib/3.7.21-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• amphetamine-data (0.8.7-18 to 0.8.7-19)
  • Migration status for amphetamine-data (0.8.7-18 to 0.8.7-19): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amphetamine-data.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• blender-doc (3.6-3 to 4.3-1)
  • Migration status for blender-doc (3.6-3 to 4.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blender-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• blobandconquer (1.11-dfsg+20-3 to 1.11-dfsg+20-5)
  • Migration status for blobandconquer (1.11-dfsg+20-3 to 1.11-dfsg+20-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating blobandconquer will fix bugs in testing: #1037045
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blobandconquer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• blockdomains (- to 0.1-1)
  • Migration status for blockdomains (- to 0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blockdomains.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bootstrap-flask (2.4.1+ds-1 to 2.4.2+ds-1)
  • Migration status for bootstrap-flask (2.4.1+ds-1 to 2.4.2+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bootstrap-flask.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bootstrap-html (5.3.3+dfsg-5 to 5.3.5+dfsg-1)
  • Migration status for bootstrap-html (5.3.3+dfsg-5 to 5.3.5+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for freedombox/25.6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for hyperkitty/1.3.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for libminion-perl/10.31+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-mne/1.9.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-taskflow/5.12.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bootstrap-html.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• caddy (- to 2.6.2-10)
  • Migration status for caddy (- to 2.6.2-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): caddy golang-github-smallstep-certificates (not considered)
    • Built-Using: caddy golang-github-smallstep-certificates (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caddy.html
    • autopkgtest for caddy/2.6.2-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• changelog-chug (- to 0.0.3-1.1)
  • Migration status for changelog-chug (- to 0.0.3-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/changelog-chug.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• charliecloud (0.38-2 to 0.38-3)
  • Migration status for charliecloud (0.38-2 to 0.38-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/charliecloud.html
    • autopkgtest for charliecloud/0.38-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• composer (2.8.6-1 to 2.8.8-1)
  • Migration status for composer (2.8.6-1 to 2.8.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: composer php-json-schema (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/composer.html
    • autopkgtest for composer/2.8.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• cyclonedx-python-lib (- to 9.1.0-1)
  • Migration status for cyclonedx-python-lib (- to 9.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by santiago, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cyclonedx-python-lib.html
    • autopkgtest for cyclonedx-python-lib/9.1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dar (2.7.16-1 to 2.7.17-1)
  • Migration status for dar (2.7.16-1 to 2.7.17-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ddnet (- to 19.1-1)
  • Migration status for ddnet (- to 19.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddnet.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• debian-edu (2.12.16 to 2.12.17)
  • Migration status for debian-edu (2.12.16 to 2.12.17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debian-edu/2.12.17: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress (will not be considered a regression), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-edu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• debian-ports-archive-keyring (2025.02.01 to 2025.04.05)
  • Migration status for debian-ports-archive-keyring (2025.02.01 to 2025.04.05): Waiting for test 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-ports-archive-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• deepin-movie-reborn (5.15.10-1 to 5.15.10-3)
  • Migration status for deepin-movie-reborn (5.15.10-1 to 5.15.10-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-movie-reborn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• devicexlib (0.8.5-2 to 0.8.6-1)
  • Migration status for devicexlib (0.8.5-2 to 0.8.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devicexlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• devscripts (2.25.7 to 2.25.8)
  • Migration status for devscripts (2.25.7 to 2.25.8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debusine/0.10.0: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for devscripts/2.25.8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devscripts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• djangorestframework-api-key (3.0.0-1 to 3.1.0-1)
  • Migration status for djangorestframework-api-key (3.0.0-1 to 3.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djangorestframework-api-key.html
    • autopkgtest for djangorestframework-api-key/3.1.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• drf-yasg-nonfree (1.21.9-1 to 1.21.10-1)
  • Migration status for drf-yasg-nonfree (1.21.9-1 to 1.21.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• edlio (0.2.1-1 to 0.2.1-2)
  • Migration status for edlio (0.2.1-1 to 0.2.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/edlio.html
    • autopkgtest for edlio/0.2.1-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• endless-sky (- to 0.10.10-1)
  • Migration status for endless-sky (- to 0.10.10-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/endless-sky.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• erlang (1:27.3.1+dfsg-1 to 1:27.3.2+dfsg-1)
  • Migration status for erlang (1:27.3.1+dfsg-1 to 1:27.3.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• erofs-utils (1.8.5-1 to 1.8.6-1)
  • Migration status for erofs-utils (1.8.5-1 to 1.8.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erofs-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• etherdfs-server (0~20180203-2 to 0~20180203-3)
  • Migration status for etherdfs-server (0~20180203-2 to 0~20180203-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/e/etherdfs-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ez-vcard (0.11.2+dfsg-2 to 0.12.1+dfsg-1)
  • Migration status for ez-vcard (0.11.2+dfsg-2 to 0.12.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ez-vcard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fastdoubleparser (- to 2.0.1-1.1)
  • Migration status for fastdoubleparser (- to 2.0.1-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fastdoubleparser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gcc-h8300-hms (1:3.4.6+dfsg2-5 to 1:3.4.6+dfsg2-6)
  • Migration status for gcc-h8300-hms (1:3.4.6+dfsg2-5 to 1:3.4.6+dfsg2-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-h8300-hms.html
    • autopkgtest for gcc-h8300-hms/1:3.4.6+dfsg2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• gensio (2.8.6-1 to 2.8.13-7)
  • Migration status for gensio (2.8.6-1 to 2.8.13-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gensio.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ghostess (20210101-1 to 20210101-2)
  • Migration status for ghostess (20210101-1 to 20210101-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 ghostess will fix bugs in testing: #1074995
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghostess.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• git-delta (0.18.2-3 to 0.18.2-4)
  • Migration status for git-delta (0.18.2-3 to 0.18.2-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating git-delta will fix bugs in testing: #1101624
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-delta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• giza (1.4.4-2 to 1.5.0-2)
  • Migration status for giza (1.4.4-2 to 1.5.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating giza will fix bugs in testing: #1101626
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/giza.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• glulxe (0.5.4-1.1 to 0.6.1-1)
  • Migration status for glulxe (0.5.4-1.1 to 0.6.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glulxe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-d5-tengo (- to 2.17.0-1)
  • Migration status for golang-github-d5-tengo (- to 2.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by maytha8thedev@gmail.com, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by maytha8thedev@gmail.com
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-d5-tengo.html
    • autopkgtest for golang-github-d5-tengo/2.17.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 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:
    • 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-jesseduffield-generics (- to 0.0~git20220320.727e535-1)
  • Migration status for golang-github-jesseduffield-generics (- to 0.0~git20220320.727e535-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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-jesseduffield-generics.html
    • autopkgtest for golang-github-jesseduffield-generics/0.0~git20220320.727e535-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-jesseduffield-kill (- to 0.0~git20250101.e216ddb-1)
  • Migration status for golang-github-jesseduffield-kill (- to 0.0~git20250101.e216ddb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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-jesseduffield-kill.html
    • autopkgtest for golang-github-jesseduffield-kill/0.0~git20250101.e216ddb-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-jesseduffield-minimal (- to 0.0~git20211018.9cde264-1)
  • Migration status for golang-github-jesseduffield-minimal (- to 0.0~git20211018.9cde264-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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-jesseduffield-minimal.html
    • autopkgtest for golang-github-jesseduffield-minimal/0.0~git20211018.9cde264-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-mvo5-goconfigparser (0.2.2-1 to 0.2.2-1.1)
  • Migration status for golang-github-mvo5-goconfigparser (0.2.2-1 to 0.2.2-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating golang-github-mvo5-goconfigparser will fix bugs in testing: #1076048
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-mvo5-goconfigparser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-smallstep-certificates (- to 0.20.0-1)
  • Migration status for golang-github-smallstep-certificates (- to 0.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-smallstep-certificates/0.20.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-smallstep-certificates.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• greaseweazle (1.21-1 to 1.22+dfsg-1)
  • Migration status for greaseweazle (1.21-1 to 1.22+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/g/greaseweazle.html
    • autopkgtest for greaseweazle/1.22+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• guava-mini (0.1.4-1 to 0.1.7-1)
  • Migration status for guava-mini (0.1.4-1 to 0.1.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guava-mini.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• horae (071~svn537+ds1-1 to 071~svn537+ds1-2)
  • Migration status for horae (071~svn537+ds1-1 to 071~svn537+ds1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• infinipath-psm (3.3+20.604758e7-6.3 to 3.3+20.604758e7-6.4)
  • Migration status for infinipath-psm (3.3+20.604758e7-6.3 to 3.3+20.604758e7-6.4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating infinipath-psm will fix bugs in testing: #1071316
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/infinipath-psm.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• itinerary (- to 24.12.3-1)
  • Migration status for itinerary (- to 24.12.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/itinerary.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ldraw-parts-free (2502+dfsg-1 to 2502+dfsg-2)
  • Migration status for ldraw-parts-free (2502+dfsg-1 to 2502+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for ldraw-parts-free/2502+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldraw-parts-free.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libmongocrypt (1.13.0-1 to 1.13.1-1)
  • Migration status for libmongocrypt (1.13.0-1 to 1.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/libm/libmongocrypt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libqapt (3.0.5-3 to 3.0.5-4)
  • Migration status for libqapt (3.0.5-3 to 3.0.5-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libq/libqapt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• make-dfsg (4.4.1-1 to 4.4.1-2)
  • Migration status for make-dfsg (4.4.1-1 to 4.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for abyss/2.3.10-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for bgw-replstatus/1.0.7-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for breathe/4.35.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for cccl/2.2.0-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for dahdi-linux/1:3.1.0+git20230717~dfsg-10: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for deheader/1.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for dh-make-perl/0.128: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for dkms/3.1.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for dpkg/1.22.18: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for fennel/1.5.3+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: Pass
    • autopkgtest for first-last-agg/0.1.4-4-gd63ea3b-8: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for freeradius/3.2.7+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for gcc-13/13.3.0-13: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for gcc-14/14.2.0-19: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for givaro/4.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for google-android-installers/1743526702-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for hunspell-dict-ko/0.7.94-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for latexml/0.8.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for make-dfsg/4.4.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for perlbrew/1.01-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for spirv-llvm-translator-17/17.0.10-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for spirv-llvm-translator-18/18.1.10-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/make-dfsg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• markdown-mode (2.6-2 to 2.7-1)
  • Migration status for markdown-mode (2.6-2 to 2.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for markdown-mode/2.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mdanalysis (2.8.0-4 to 2.9.0-1)
  • Migration status for mdanalysis (2.8.0-4 to 2.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdanalysis.html
    • autopkgtest for mdanalysis/2.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mgmt (- to 0.0.26.git.2024.10.25.85e1d6c0e8-3)
  • Migration status for mgmt (- to 0.0.26.git.2024.10.25.85e1d6c0e8-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/mgmt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• neovim-gruvbox (- to 2.0.0-2)
  • Migration status for neovim-gruvbox (- to 2.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neovim-gruvbox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• neovim-lualine (- to 0.0.6+git20250404-1)
  • Migration status for neovim-lualine (- to 0.0.6+git20250404-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neovim-lualine.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• netatalk (4.1.2~ds-4 to 4.2.0~ds-1)
  • Migration status for netatalk (4.1.2~ds-4 to 4.2.0~ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for netatalk/4.2.0~ds-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch armel binaries not found
    • Not built on buildd: upload info for arch armhf binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netatalk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• networking-l2gw (1:20.0.0-3 to 1:21.0.0-1)
  • Migration status for networking-l2gw (1:20.0.0-3 to 1:21.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends-Indep: networking-l2gw neutron
    • Depends: networking-l2gw neutron
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-l2gw.html
    • autopkgtest for networking-l2gw/1:21.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Failed (not a regression), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nextcloud-desktop (3.16.0-1 to 3.16.2-1)
  • Migration status for nextcloud-desktop (3.16.0-1 to 3.16.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nextcloud-desktop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-enquirer (2.3.6~ds-4 to 2.3.6~ds-5)
  • Migration status for node-enquirer (2.3.6~ds-4 to 2.3.6~ds-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-enquirer.html
    • autopkgtest for node-enquirer/2.3.6~ds-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-shiny-server (1.5.20.1002-3 to 1.5.20.1002-4)
  • Migration status for node-shiny-server (1.5.20.1002-3 to 1.5.20.1002-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/n/node-shiny-server.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• notification-position-reloaded (- to 0.0~git20250402.42cb38e-1)
  • Migration status for notification-position-reloaded (- to 0.0~git20250402.42cb38e-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notification-position-reloaded.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nvme-stas (2.4-3 to 2.4.1-1)
  • Migration status for nvme-stas (2.4-3 to 2.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvme-stas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• objcryst-fox (2022.1-1 to 2022.1-2)
  • Migration status for objcryst-fox (2022.1-1 to 2022.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/objcryst-fox.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• obs-scene-as-transition (1.1.1-1 to 1.1.1-2)
  • Migration status for obs-scene-as-transition (1.1.1-1 to 1.1.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-scene-as-transition.html
    • autopkgtest for obs-scene-as-transition/1.1.1-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocl-icd (2.3.2-1 to 2.3.3-1)
  • Migration status for ocl-icd (2.3.2-1 to 2.3.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocl-icd.html
    • autopkgtest for mesa/25.0.2-1: riscv64: No tests, superficial or marked flaky
    • autopkgtest for ocl-icd/2.3.3-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• openrct2 (0.4.20+ds-1 to 0.4.21+ds-1)
  • Migration status for openrct2 (0.4.20+ds-1 to 0.4.21+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: openrct2 openrct2-objects
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• openrct2-objects (1.5.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for openrct2-objects (1.5.1+dfsg-1 to 1.6.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• patchelf (0.18.0-1.1 to 0.18.0-1.2)
  • Migration status for patchelf (0.18.0-1.1 to 0.18.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating patchelf would introduce bugs in testing: #1102299
    • missing build on mips64el
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating patchelf will fix bugs in testing: #1091236
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/patchelf.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-json-schema (5.3.0-2 to 6.4.1-1)
  • Migration status for php-json-schema (5.3.0-2 to 6.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Implicit dependency: php-json-schema composer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-json-schema.html
    • autopkgtest for php-json-schema/6.4.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• polib (1.2.0-1 to 1.2.0-2)
  • Migration status for polib (1.2.0-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:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating polib will fix bugs in testing: #1074675
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polib.html
    • autopkgtest for polib/1.2.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pydantic-core (2.27.2-1 to 2.27.2-2)
  • Migration status for pydantic-core (2.27.2-1 to 2.27.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pydantic/2.10.6-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pydantic-core/2.27.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): pydantic-core rust-idna (not considered)
    • Build-Depends(-Arch): pydantic-core rust-url (not considered)
  • Additional info:
    • Updating pydantic-core will fix bugs in testing: #1101417
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydantic-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pydantic-settings (2.8.1-1 to 2.8.1-2)
  • Migration status for pydantic-settings (2.8.1-1 to 2.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pydantic-settings/2.8.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-maggma/0.70.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating pydantic-settings will fix bugs in testing: #1101859
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydantic-settings.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-drf-spectacular-sidecar-nonfree (2025.3.1-1 to 2025.4.1-1)
  • Migration status for python-drf-spectacular-sidecar-nonfree (2025.3.1-1 to 2025.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-flickrapi (- to 2.4-0.2)
  • Migration status for python-flickrapi (- to 2.4-0.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flickrapi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-openqa-client (4.2.3-1 to 4.3.0-1)
  • Migration status for python-openqa-client (4.2.3-1 to 4.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-openqa-client.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-polyfactory (- to 2.20.0-2)
  • Migration status for python-polyfactory (- to 2.20.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends-Indep: python-polyfactory python-auto-pytabs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-polyfactory.html
    • autopkgtest for python-polyfactory/2.20.0-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-tz (2025.1-3 to 2025.2-1)
  • Migration status for python-tz (2025.1-3 to 2025.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pandas/2.2.3+dfsg-8: riscv64: Pass
    • autopkgtest for python-tz/2025.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for stravalib/2.2-1: riscv64: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-virtualenv (20.29.3+ds-1 to 20.30.0+ds-1)
  • Migration status for python-virtualenv (20.29.3+ds-1 to 20.30.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for poetry/2.1.1+dfsg-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-virtualenv/20.30.0+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-virtualenv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-yolink-api (0.4.8-1 to 0.5.1-1)
  • Migration status for python-yolink-api (0.4.8-1 to 0.5.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-yolink-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ros2-colcon-core (0.18.4-1 to 0.19.0-1)
  • Migration status for ros2-colcon-core (0.18.4-1 to 0.19.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-colcon-core.html
    • autopkgtest for ros2-colcon-core/0.19.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ruby-dry-logger (- to 1.0.4-1.1)
  • Migration status for ruby-dry-logger (- to 1.0.4-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dry-logger.html
    • autopkgtest for ruby-dry-logger/1.0.4-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-redis-clustering (- to 5.3.0-1.1)
  • Migration status for ruby-redis-clustering (- to 5.3.0-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-clustering.html
    • autopkgtest for ruby-redis-clustering/5.3.0-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-ab-glyph (0.2.28-1 to 0.2.29-1)
  • Migration status for rust-ab-glyph (0.2.28-1 to 0.2.29-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ab-glyph rust-owned-ttf-parser (not considered)
    • Depends: rust-ab-glyph rust-owned-ttf-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ab-glyph.html
    • autopkgtest for rust-ab-glyph/0.2.29-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-plotters/0.3.7-2: riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-cargo-outdated (0.16.0-2 to 0.17.0-1)
  • Migration status for rust-cargo-outdated (0.16.0-2 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 2 of 5 days old
  • Additional info:
    • Updating rust-cargo-outdated will fix bugs in testing: #1102186
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-outdated.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-fontdb (0.22.0-2 to 0.22.0-3)
  • Migration status for rust-fontdb (0.22.0-2 to 0.22.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-fontdb rust-ttf-parser (not considered)
    • Depends: rust-fontdb rust-ttf-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fontdb.html
    • autopkgtest for rust-fontdb/0.22.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-gbm (- to 0.18.0-1)
  • Migration status for rust-gbm (- to 0.18.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-gbm rust-gbm-sys (not considered)
    • Depends: rust-gbm rust-gbm-sys (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gbm.html
    • autopkgtest for rust-gbm/0.18.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-idna (0.4.0-1 to 1.0.3-2)
  • Migration status for rust-idna (0.4.0-1 to 1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-idna/1.0.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-sequoia-openpgp/2.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 2 of 5 days old
    • Implicit dependency: rust-idna rust-url (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-idna.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-libseccomp (0.3.0-10 to 0.3.0-11)
  • Migration status for rust-libseccomp (0.3.0-10 to 0.3.0-11): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-glycin-utils/3.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-libseccomp/0.3.0-11: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating rust-libseccomp will fix bugs in testing: #1102199
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libseccomp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-libxml (- to 0.3.3-1)
  • Migration status for rust-libxml (- to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-libxml would introduce bugs in testing: #1102187
    • autopkgtest for rust-libxml/0.3.3-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libxml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-lsd (1.1.5-4 to 1.1.5-5)
  • Migration status for rust-lsd (1.1.5-4 to 1.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 2 of 5 days old
  • Additional info:
    • Updating rust-lsd will fix bugs in testing: #1102121
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lsd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-owned-ttf-parser (0.24.0-1 to 0.25.0-2)
  • Migration status for rust-owned-ttf-parser (0.24.0-1 to 0.25.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-owned-ttf-parser rust-ttf-parser (not considered)
    • Depends: rust-owned-ttf-parser rust-ttf-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Implicit dependency: rust-owned-ttf-parser rust-ab-glyph
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-owned-ttf-parser.html
    • autopkgtest for rust-owned-ttf-parser/0.25.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-potential-utf (- to 0.1.2-1)
  • Migration status for rust-potential-utf (- to 0.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 2 of 5 days old
  • 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-procs (0.14.9-2 to 0.14.10-1)
  • Migration status for rust-procs (0.14.9-2 to 0.14.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-procs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-rustybuzz (0.18.0-1 to 0.18.0-2)
  • Migration status for rust-rustybuzz (0.18.0-1 to 0.18.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-rustybuzz rust-ttf-parser (not considered)
    • Depends: rust-rustybuzz rust-ttf-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustybuzz.html
    • autopkgtest for rust-rustybuzz/0.18.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-url (2.5.2-1 to 2.5.4-2)
  • Migration status for rust-url (2.5.2-1 to 2.5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-dockworker/0.5.1-3: riscv64: Pass
    • autopkgtest for rust-git2/0.19.0-2: riscv64: Pass
    • autopkgtest for rust-reqwest/0.12.12-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-sequoia-cert-store/0.6.2-1: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-sequoia-net/0.29.0-1: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-url/2.5.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-url rust-idna (not considered)
    • Depends: rust-url rust-idna (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-url.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sccache (0.10.0-1 to 0.10.0-4)
  • Migration status for sccache (0.10.0-1 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 2 of 5 days old
    • Build-Depends(-Arch): sccache rust-zip (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sccache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• seadrive-gui (- to 3.0.13+ds1-1)
  • Migration status for seadrive-gui (- to 3.0.13+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • seadrive-gui/amd64 has unsatisfiable dependency
    • seadrive-gui/arm64 has unsatisfiable dependency
    • seadrive-gui/armhf has unsatisfiable dependency
    • seadrive-gui/i386 has unsatisfiable dependency
    • seadrive-gui/mips64el has unsatisfiable dependency
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/seadrive-gui.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• socat (1.8.0.2-1 to 1.8.0.3-1)
  • Migration status for socat (1.8.0.2-1 to 1.8.0.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating socat will fix bugs in testing: #1091603, #1100875
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socat.html
    • autopkgtest for podman/5.4.1+ds1-3: riscv64: Pass
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• solaar (1.1.14-2 to 1.1.14-3)
  • Migration status for solaar (1.1.14-2 to 1.1.14-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/s/solaar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sphinx-book-theme (0.1.7-3 to 1.1.4-2)
  • Migration status for sphinx-book-theme (0.1.7-3 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating sphinx-book-theme will fix bugs in testing: #1085947
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-book-theme.html
    • autopkgtest for sphinx-book-theme/1.1.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• sqlglot (26.12.0-1 to 26.12.1-1)
  • Migration status for sqlglot (26.12.0-1 to 26.12.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlglot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sqlmap (1.9.3-1 to 1.9.4-1)
  • Migration status for sqlmap (1.9.3-1 to 1.9.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/s/sqlmap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• starvoyager (0.4.4-11 to 0.4.4-13)
  • Migration status for starvoyager (0.4.4-11 to 0.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/s/starvoyager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• strophejs (1.2.14+dfsg-8 to 3.1.0-2)
  • Migration status for strophejs (1.2.14+dfsg-8 to 3.1.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/strophejs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• swiftlang (5.10.1-2 to 6.0.3-1)
  • Migration status for swiftlang (5.10.1-2 to 6.0.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swiftlang.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch 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 ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tclthread3 (- to 3.0.1-2)
  • Migration status for tclthread3 (- to 3.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tclthread3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tcpdf (6.8.2+dfsg-1 to 6.9.1+dfsg-1)
  • Migration status for tcpdf (6.8.2+dfsg-1 to 6.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcpdf.html
    • autopkgtest for tcpdf/6.9.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• u-boot-efi-dtb (2 to 3)
  • Migration status for u-boot-efi-dtb (2 to 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/u/u-boot-efi-dtb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wacomtablet (6.3.2-1 to 6.3.4-2)
  • Migration status for wacomtablet (6.3.2-1 to 6.3.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating wacomtablet will fix bugs in testing: #1102124
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wacomtablet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xgks (2.6.1+dfsg.2-16 to 2.6.1+dfsg.2-17)
  • Migration status for xgks (2.6.1+dfsg.2-16 to 2.6.1+dfsg.2-17): Waiting for test 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 xgks will fix bugs in testing: #1084078
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xgks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xmoto (0.6.2+repack-3 to 0.6.3+repack-1)
  • Migration status for xmoto (0.6.2+repack-3 to 0.6.3+repack-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmoto.html
    • autopkgtest for xmoto/0.6.3+repack-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xpuzzles (8.8.7+ds-1 to 8.8.7+ds-2)
  • Migration status for xpuzzles (8.8.7+ds-1 to 8.8.7+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating xpuzzles will fix bugs in testing: #1098419
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xpuzzles.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• zpaqfranz (60.10-1 to 62.2-1)
  • Migration status for zpaqfranz (60.10-1 to 62.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • zpaqfranz/armel has unsatisfiable dependency
    • zpaqfranz/armhf has unsatisfiable dependency
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zpaqfranz.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• abseil (20240722.0-1.5 to 20240722.0-3)
  • Migration status for abseil (20240722.0-1.5 to 20240722.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for abseil/20240722.0-3: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for bazel-bootstrap/4.2.3+ds-11: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for grpc/1.51.1-6: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for libreoffice/4:25.2.2-1: amd64: Pass, arm64: Pass, armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abseil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• aiorpcx (0.23.1-1 to 0.24-1)
  • Migration status for aiorpcx (0.23.1-1 to 0.24-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiorpcx.html
    • autopkgtest for aiorpcx/0.24-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• alsa-ucm-conf-asahi (8-1 to 8-2)
  • Migration status for alsa-ucm-conf-asahi (8-1 to 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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alsa-ucm-conf-asahi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• appstream-glib (0.8.2-1.1 to 0.8.3-1)
  • Migration status for appstream-glib (0.8.2-1.1 to 0.8.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appstream-glib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• apt (2.9.35 to 3.0.0)
  • Migration status for apt (2.9.35 to 3.0.0): Waiting for test results or 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/apt.html
    • autopkgtest for apt/3.0.0: amd64: Pass, arm64: Failed (not a regression), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• arpack (3.9.1-4 to 3.9.1-6)
  • Migration status for arpack (3.9.1-4 to 3.9.1-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/a/arpack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• asahi-audio (3.2-1 to 3.2-2)
  • Migration status for asahi-audio (3.2-1 to 3.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• asahi-fwextract (0.7.8-1 to 0.7.8-2)
  • Migration status for asahi-fwextract (0.7.8-1 to 0.7.8-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asahi-fwextract.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• bleak-retry-connector (3.9.0-1 to 3.10.0-1)
  • Migration status for bleak-retry-connector (3.9.0-1 to 3.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for airthings-ble/1.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for bleak-retry-connector/3.10.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for inkbird-ble/0.9.0-1: riscv64: Pass
    • autopkgtest for ld2410-ble/0.2.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for led-ble/1.1.6-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pyswitchbot/0.59.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for yalexs-ble/2.5.7-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bleak-retry-connector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• bmap-tools (3.8.0-1 to 3.9.0-2)
  • Migration status for bmap-tools (3.8.0-1 to 3.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by josch, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bmap-tools.html
    • autopkgtest for bmap-tools/3.9.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• boost-ext-ut (- to 2.3.1-1)
  • Migration status for boost-ext-ut (- to 2.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boost-ext-ut.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• bornagain (- to 22~git20250325170646.93042f5+ds3-3)
  • Migration status for bornagain (- to 22~git20250325170646.93042f5+ds3-3): 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 bornagain/22~git20250325170646.93042f5+ds3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bornagain.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• cacti-spine (1.2.27-1 to 1.2.30-1)
  • Migration status for cacti-spine (1.2.27-1 to 1.2.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/c/cacti-spine.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ccfits (2.6+dfsg-1 to 2.7+dfsg-1)
  • Migration status for ccfits (2.6+dfsg-1 to 2.7+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccfits.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cjs (6.4.0-1 to 128.0-1)
  • Migration status for cjs (6.4.0-1 to 128.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cjs unsatisfiable Build-Depends(-Arch) on armel: libmozjs-128-dev
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for cjs/128.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating cjs will fix bugs in testing: #1100204
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cjs.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ckermit (414~beta11-3 to 416~beta12-1)
  • Migration status for ckermit (414~beta11-3 to 416~beta12-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ckermit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• condor (23.6.2+dfsg-2 to 23.9.6+dfsg-2)
  • Migration status for condor (23.6.2+dfsg-2 to 23.9.6+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 condor will fix bugs in testing: #1101498
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/condor.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• coreutils (9.5-1 to 9.6-2)
  • Migration status for coreutils (9.5-1 to 9.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coreutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cp2k (- to 2025.1-1)
  • Migration status for cp2k (- to 2025.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cp2k/2025.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cp2k.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ctemplate (2.4-3.1 to 2.4-4)
  • Migration status for ctemplate (2.4-3.1 to 2.4-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctemplate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dkms (3.1.5-2 to 3.1.7-2)
  • Migration status for dkms (3.1.5-2 to 3.1.7-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Implicit dependency: dkms dahdi-linux
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dkms.html
    • autopkgtest for dkms/3.1.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• doom-wad-shareware (1.9.fixed-4 to 1.9.fixed-5)
  • Migration status for doom-wad-shareware (1.9.fixed-4 to 1.9.fixed-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• ezquake (- to 3.6.6-1)
  • Migration status for ezquake (- to 3.6.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ezquake.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• feenox (- to 1.1-1)
  • Migration status for feenox (- to 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
    • Depends: feenox petsc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/feenox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• foliate (4.~really3.2.1-1 to 4.~really3.3.0-1)
  • Migration status for foliate (4.~really3.2.1-1 to 4.~really3.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foliate.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• fonts-recommended (1 to 2)
  • Migration status for fonts-recommended (1 to 2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-recommended.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• forecast-solar (4.0.0-2 to 4.1.0-1)
  • Migration status for forecast-solar (4.0.0-2 to 4.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forecast-solar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gammaray (3.1.0+ds-2 to 3.1.0+ds-3)
  • Migration status for gammaray (3.1.0+ds-2 to 3.1.0+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gammaray.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gdb-doc (- to 16.2-2)
  • Migration status for gdb-doc (- to 16.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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gitaly-installer (- to 17.3.6+debian2)
  • Migration status for gitaly-installer (- to 17.3.6+debian2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Depends: gitaly-installer gitlab-shell
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• glib2.0 (2.84.0-2 to 2.84.1-1)
  • Migration status for glib2.0 (2.84.0-2 to 2.84.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/glib2.0.html
    • autopkgtest for glib2.0/2.84.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for libvirt/11.1.0-1: riscv64: Pass
    • autopkgtest for openjdk-25/25~16ea-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-swtchr/0.1.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for tinysparql/3.8.2-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• glycin (1.2.0+ds-2 to 1.2.0+ds-5)
  • Migration status for glycin (1.2.0+ds-2 to 1.2.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glycin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnubg (1.08.003-2 to 1.08.003-3)
  • Migration status for gnubg (1.08.003-2 to 1.08.003-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnubg.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• grantlee5 (5.3.1-3 to 5.3.1-4)
  • Migration status for grantlee5 (5.3.1-3 to 5.3.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grantlee5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• hunspell-br (0.12-2.1 to 0.14-1)
  • Migration status for hunspell-br (0.12-2.1 to 0.14-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hunspell-br.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• icingadb (1.2.1-1 to 1.3.0-1)
  • Migration status for icingadb (1.2.1-1 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingadb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kernelshark (2.3.2-1 to 2.4.0-1)
  • Migration status for kernelshark (2.3.2-1 to 2.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kernelshark.html
    • autopkgtest for kernelshark/2.4.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• keyman (18.0.199-2 to 18.0.227-1)
  • Migration status for keyman (18.0.199-2 to 18.0.227-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/keyman.html
    • autopkgtest for keyman/18.0.227-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kicad (9.0.0+dfsg-1 to 9.0.1+dfsg-1)
  • Migration status for kicad (9.0.0+dfsg-1 to 9.0.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad.html
    • autopkgtest for kicad/9.0.1+dfsg-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kicad-footprints (9.0.0-1 to 9.0.1-1)
  • Migration status for kicad-footprints (9.0.0-1 to 9.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/k/kicad-footprints.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kicad-packages3d (9.0.0-1 to 9.0.1-1)
  • Migration status for kicad-packages3d (9.0.0-1 to 9.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/k/kicad-packages3d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kicad-symbols (9.0.0-1 to 9.0.1-1)
  • Migration status for kicad-symbols (9.0.0-1 to 9.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/k/kicad-symbols.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kwin (4:6.3.2.1-2 to 4:6.3.4-2)
  • Migration status for kwin (4:6.3.2.1-2 to 4:6.3.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libfreemarker-java (2.3.32-2 to 2.3.32-2.1)
  • Migration status for libfreemarker-java (2.3.32-2 to 2.3.32-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/libf/libfreemarker-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libmegapixels (0.2.0-1 to 0.2.1-1)
  • Migration status for libmegapixels (0.2.0-1 to 0.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmegapixels.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libunibreak (6.1-2 to 6.1-3)
  • Migration status for libunibreak (6.1-2 to 6.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libunibreak.html
    • autopkgtest for libunibreak/6.1-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-dekko-app (0.4.1+dfsg-4 to 0.4.1+dfsg-6)
  • Migration status for lomiri-dekko-app (0.4.1+dfsg-4 to 0.4.1+dfsg-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 lomiri-dekko-app will fix bugs in testing: #1102100
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-dekko-app.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lomiri-docviewer-app (3.1.0+dfsg-1 to 3.1.1+dfsg-3)
  • Migration status for lomiri-docviewer-app (3.1.0+dfsg-1 to 3.1.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lomiri-docviewer-app unsatisfiable Build-Depends(-Arch) on mips64el: libreoffice
    • missing build on mips64el
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating lomiri-docviewer-app will fix bugs in testing: #1102111
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-docviewer-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mapnik (4.0.6+ds-1 to 4.0.7+ds-1)
  • Migration status for mapnik (4.0.6+ds-1 to 4.0.7+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mapnik.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• martchus-cpp-utilities (5.27.3-1 to 5.28.0-1)
  • Migration status for martchus-cpp-utilities (5.27.3-1 to 5.28.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/martchus-cpp-utilities.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• martchus-qtforkawesome (0.3.1-1 to 0.3.1-2)
  • Migration status for martchus-qtforkawesome (0.3.1-1 to 0.3.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): martchus-qtforkawesome martchus-cpp-utilities
    • Build-Depends(-Arch): martchus-qtforkawesome martchus-qtutilities
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/martchus-qtforkawesome.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• martchus-qtutilities (6.14.6-1 to 6.15.0-1)
  • Migration status for martchus-qtutilities (6.14.6-1 to 6.15.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): martchus-qtutilities martchus-cpp-utilities
    • Depends: martchus-qtutilities martchus-cpp-utilities
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/martchus-qtutilities.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mpv (0.40.0-2 to 0.40.0-3)
  • Migration status for mpv (0.40.0-2 to 0.40.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating mpv will fix bugs in testing: #1101854, #1101869
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nagvis (1:1.9.45-1 to 1:1.9.46-1)
  • Migration status for nagvis (1:1.9.45-1 to 1:1.9.46-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/nagvis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• neomutt (20250113+dfsg-1 to 20250404+dfsg-1)
  • Migration status for neomutt (20250113+dfsg-1 to 20250404+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neomutt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• numdiff (5.9.0-1 to 5.9.0-2)
  • Migration status for numdiff (5.9.0-1 to 5.9.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numdiff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nvidia-modprobe (550.144.03-1 to 570.133.07-1)
  • Migration status for nvidia-modprobe (550.144.03-1 to 570.133.07-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• obs-advanced-masks (- to 1.1.0-3)
  • Migration status for obs-advanced-masks (- to 1.1.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-advanced-masks.html
    • autopkgtest for obs-advanced-masks/1.1.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• obs-retro-effects (- to 1.0.0-2)
  • Migration status for obs-retro-effects (- to 1.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-retro-effects.html
    • autopkgtest for obs-retro-effects/1.0.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• obs-stroke-glow-shadow (- to 1.5.2-3)
  • Migration status for obs-stroke-glow-shadow (- to 1.5.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-stroke-glow-shadow.html
    • autopkgtest for obs-stroke-glow-shadow/1.5.2-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• okteta (5:0.26.20-1 to 5:0.26.21-1)
  • Migration status for okteta (5:0.26.20-1 to 5:0.26.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/okteta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ompl (- to 1.6.0+ds1-2)
  • Migration status for ompl (- to 1.6.0+ds1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ompl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• openjdk-25 (25~16ea-1 to 25~17ea-1)
  • Migration status for openjdk-25 (25~16ea-1 to 25~17ea-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 openjdk-25/25~17ea-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-25.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• org-mode (9.7.25+dfsg-1 to 9.7.27+dfsg-1)
  • Migration status for org-mode (9.7.25+dfsg-1 to 9.7.27+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/org-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• org-mode-doc (9.7.25-1 to 9.7.27-1)
  • Migration status for org-mode-doc (9.7.25-1 to 9.7.27-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)
• passwordsafe (1.17.0+dfsg-1 to 1.21.0+dfsg-1)
  • Migration status for passwordsafe (1.17.0+dfsg-1 to 1.21.0+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/passwordsafe.html
    • autopkgtest for passwordsafe/1.21.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-nesbot-carbon (2.72.6-2 to 2.73.0-1)
  • Migration status for php-nesbot-carbon (2.72.6-2 to 2.73.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/php-nesbot-carbon.html
    • autopkgtest for php-nesbot-carbon/2.73.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• pwntools (4.14.0-1 to 4.14.1-1)
  • Migration status for pwntools (4.14.0-1 to 4.14.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pwntools.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pygopherd (3.0.1-1.1 to 3.0.1-2)
  • Migration status for pygopherd (3.0.1-1.1 to 3.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pygopherd.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• python-decorator (5.1.1-5 to 5.2.1-1)
  • Migration status for python-decorator (5.1.1-5 to 5.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ipyparallel/8.8.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for python-decorator/5.2.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-openstacksdk/4.4.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-decorator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-gnuplotlib (0.43-1 to 0.45-1)
  • Migration status for python-gnuplotlib (0.43-1 to 0.45-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-gnuplotlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-hypothesis (6.127.4-1 to 6.130.5-1)
  • Migration status for python-hypothesis (6.127.4-1 to 6.130.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mdanalysis/2.8.0-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for pandas/2.2.3+dfsg-8: riscv64: Pass
    • autopkgtest for python-hypothesis/6.130.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Too young, only 3 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-nxtomomill (- to 1.1.0-4)
  • Migration status for python-nxtomomill (- to 1.1.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nxtomomill.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-pycudwt (- to 1.0.2-5)
  • Migration status for python-pycudwt (- to 1.0.2-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for python-pycudwt/1.0.2-5: amd64: No tests, superficial or marked flaky ♻
• python-websockets (14.1-1 to 15.0.1-1)
  • Migration status for python-websockets (14.1-1 to 15.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/p/python-websockets.html
    • autopkgtest for python-websockets/15.0.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qemu-web-desktop (25.02.28+ds1-2 to 25.04.05+ds1-1)
  • Migration status for qemu-web-desktop (25.02.28+ds1-2 to 25.04.05+ds1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qemu-web-desktop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• r-cran-nloptr (2.2.1-1 to 2.2.1-2)
  • Migration status for r-cran-nloptr (2.2.1-1 to 2.2.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-nloptr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-rms (7.0-0-1 to 8.0-0-1)
  • Migration status for r-cran-rms (7.0-0-1 to 8.0-0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rms.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ragel (6.10-4 to 6.10-5)
  • Migration status for ragel (6.10-4 to 6.10-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/ragel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• raysession (0.14.4-1 to 0.14.4-2)
  • Migration status for raysession (0.14.4-1 to 0.14.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raysession.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• referencing (0.35.1-2 to 0.36.2-1)
  • Migration status for referencing (0.35.1-2 to 0.36.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/referencing.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• renpy (8.3.4+dfsg-1 to 8.3.4+dfsg-2)
  • Migration status for renpy (8.3.4+dfsg-1 to 8.3.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/renpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ruby-faraday-middleware-aws-sigv4 (0.3.0-2 to 1.0.1-2)
  • Migration status for ruby-faraday-middleware-aws-sigv4 (0.3.0-2 to 1.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-faraday-middleware-aws-sigv4.html
    • autopkgtest for ruby-faraday-middleware-aws-sigv4/1.0.1-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ruby-semver-dialects (2.0.2-2 to 3.4.0-2)
  • Migration status for ruby-semver-dialects (2.0.2-2 to 3.4.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-semver-dialects.html
    • autopkgtest for ruby-semver-dialects/3.4.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-coreutils (0.0.27-3 to 0.0.30-1)
  • Migration status for rust-coreutils (0.0.27-3 to 0.0.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:
    • Updating rust-coreutils will fix bugs in testing: #1101590
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-coreutils.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-railway-provider-search-ch (0.1.0-4 to 0.1.1-1)
  • Migration status for rust-railway-provider-search-ch (0.1.0-4 to 0.1.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-railway-provider-search-ch.html
    • autopkgtest for rust-railway-provider-search-ch/0.1.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-ripasso-cursive (0.7.0-1 to 0.8.0-1)
  • Migration status for rust-ripasso-cursive (0.7.0-1 to 0.8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ripasso-cursive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-ttf-parser (0.24.1-1 to 0.25.1-1)
  • Migration status for rust-ttf-parser (0.24.1-1 to 0.25.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
    • Implicit dependency: rust-ttf-parser rust-fontdb
    • Implicit dependency: rust-ttf-parser rust-owned-ttf-parser
    • Implicit dependency: rust-ttf-parser rust-rustybuzz
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ttf-parser.html
    • autopkgtest for rust-plotters/0.3.7-2: riscv64: Pass
    • autopkgtest for rust-ttf-parser/0.25.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• scite (5.5.5-1 to 5.5.6-1)
  • Migration status for scite (5.5.5-1 to 5.5.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ser2net (4.6.2-1 to 4.6.4-1)
  • Migration status for ser2net (4.6.2-1 to 4.6.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): ser2net gensio
    • Depends: ser2net gensio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ser2net.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• shadow (1:4.17.3-3 to 1:4.17.4-1)
  • Migration status for shadow (1:4.17.3-3 to 1:4.17.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shadow.html
    • autopkgtest for podman/5.4.1+ds1-3: riscv64: Pass
    • autopkgtest for shadow/1:4.17.4-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for util-linux/2.40.4-5: riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• simplemonitor (1.14.0a-1 to 1.14.0a-2)
  • Migration status for simplemonitor (1.14.0a-1 to 1.14.0a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simplemonitor would introduce bugs in testing: #1102320
    • Not built on buildd: arch all binaries uploaded by cpina, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplemonitor.html
    • autopkgtest for simplemonitor/1.14.0a-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• smifb2 (2.4.0-2.1 to 2.4.1-1)
  • Migration status for smifb2 (2.4.0-2.1 to 2.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smifb2.html
    • autopkgtest for smifb2/2.4.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• snimpy (1.0.3-1 to 1.0.3-2)
  • Migration status for snimpy (1.0.3-1 to 1.0.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating snimpy will fix bugs in testing: #1101298, #1101601
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snimpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• syncthingtray (1.5.4-1 to 1.7.5-1)
  • Migration status for syncthingtray (1.5.4-1 to 1.7.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
    • Build-Depends(-Arch): syncthingtray martchus-cpp-utilities
    • Build-Depends(-Arch): syncthingtray martchus-qtforkawesome
    • Build-Depends(-Arch): syncthingtray martchus-qtutilities
    • Depends: syncthingtray martchus-cpp-utilities
    • Depends: syncthingtray martchus-qtutilities
  • Additional info:
    • Updating syncthingtray will fix bugs in testing: #1100350, #1101377
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syncthingtray.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tiff (4.7.0-2 to 4.7.0-3)
  • Migration status for tiff (4.7.0-2 to 4.7.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating tiff will fix bugs in testing: #1102073
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• treemacs (3.1-2 to 3.2-1)
  • Migration status for treemacs (3.1-2 to 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/t/treemacs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tuxpaint-stamps (2024.10.25-1 to 2025.03.31-1)
  • Migration status for tuxpaint-stamps (2024.10.25-1 to 2025.03.31-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tuxpaint-stamps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• virt-manager (1:5.0.0-4 to 1:5.0.0-5)
  • Migration status for virt-manager (1:5.0.0-4 to 1:5.0.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virt-manager.html
    • autopkgtest for virt-manager/1:5.0.0-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• virtuoso-opensource (7.2.12+dfsg-1 to 7.2.12+dfsg-2)
  • Migration status for virtuoso-opensource (7.2.12+dfsg-1 to 7.2.12+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtuoso-opensource.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• webkit2gtk (2.48.0-1 to 2.48.1-2)
  • Migration status for webkit2gtk (2.48.0-1 to 2.48.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for astroidmail/0.16+20240629-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for balsa/2.6.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for devhelp/43.0-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for evolution-data-server/3.56.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for formiko/1.4.3-2.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for geary/46.0-6: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress
    • autopkgtest for glade/3.40.0-6: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnome-feeds/2.2.0-4: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for juce/8.0.6+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for keyman/18.0.199-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libgepub/0.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for libgtk3-webkit2-perl/0.06-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for liferea/1.15.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-pywebview/5.0.5+dfsg-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for ruby-gnome/4.2.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for wxwidgets3.2/3.2.6+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for yelp/42.2-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webkit2gtk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 3 days old (needed 2 days)
• webtest (3.0.2-1 to 3.0.4-1)
  • Migration status for webtest (3.0.2-1 to 3.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webtest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• wiredpanda (4.1.12-1 to 4.2.1-1)
  • Migration status for wiredpanda (4.1.12-1 to 4.2.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wiredpanda.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xsd (4.0.0-9 to 4.0.0-10)
  • Migration status for xsd (4.0.0-9 to 4.0.0-10): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch armhf binaries not found
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating xsd will fix bugs in testing: #1069553
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xsd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xserver-xorg-video-glide (1.2.2-1 to 1.2.2-2)
  • Migration status for xserver-xorg-video-glide (1.2.2-1 to 1.2.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-glide.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• blazar-dashboard (- to 13.0.0-2)
  • Migration status for blazar-dashboard (- to 13.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blazar-dashboard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• bluefish (2.2.16-1 to 2.2.17-1)
  • Migration status for bluefish (2.2.16-1 to 2.2.17-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bluefish.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• c3p0 (0.9.1.2-10 to 0.9.1.2-10.1)
  • Migration status for c3p0 (0.9.1.2-10 to 0.9.1.2-10.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating c3p0 will fix bugs in testing: #927936
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/c3p0.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• clipit (1.4.5+git20210313-3 to 1.4.5+git20241103-1)
  • Migration status for clipit (1.4.5+git20210313-3 to 1.4.5+git20241103-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/clipit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• copyq (9.1.0-2 to 10.0.0-1)
  • Migration status for copyq (9.1.0-2 to 10.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/copyq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dahdi-linux (1:3.1.0+git20230717~dfsg-10 to 1:3.1.0+git20230717~dfsg-10.1)
  • Migration status for dahdi-linux (1:3.1.0+git20230717~dfsg-10 to 1:3.1.0+git20230717~dfsg-10.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating dahdi-linux will fix bugs in testing: #1101409
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dahdi-linux.html
    • autopkgtest for dahdi-linux/1:3.1.0+git20230717~dfsg-10.1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• debian-security-support (1:13+2025.01.30 to 1:13+2025.04.04)
  • Migration status for debian-security-support (1:13+2025.01.30 to 1:13+2025.04.04): Waiting for test results or another package, or too young (no action required now - 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/debian-security-support.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• enter-tex (3.47.0-4 to 3.47.0-6)
  • Migration status for enter-tex (3.47.0-4 to 3.47.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Depends: enter-tex libgedit-tepl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enter-tex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• eprosima-idl-parser (4.0.3+dfsg-1 to 4.0.4+dfsg-1)
  • Migration status for eprosima-idl-parser (4.0.3+dfsg-1 to 4.0.4+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eprosima-idl-parser.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
• falkon (24.12.2-1 to 25.03.90-1)
  • Migration status for falkon (24.12.2-1 to 25.03.90-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/falkon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• fonts-roboto (2:0~20170802-3 to 2:0~20170802-4)
  • Migration status for fonts-roboto (2:0~20170802-3 to 2:0~20170802-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
    • Implicit dependency: fonts-roboto raysession
    • Implicit dependency: fonts-roboto renpy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-roboto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gcc-snapshot (- to 1:20250404-1)
  • Migration status for gcc-snapshot (- to 1:20250404-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:20250404-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻
    • missing build on mips64el
    • missing build on riscv64
    • missing build on s390x
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-snapshot.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gedit (48.1-2 to 48.1-3)
  • Migration status for gedit (48.1-2 to 48.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
    • Depends: gedit libgedit-tepl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gedit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gedit-plugins (48.1-1 to 48.1-2)
  • Migration status for gedit-plugins (48.1-1 to 48.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Depends: gedit-plugins libgedit-tepl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gedit-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• geomet (1.1.0-2 to 1.1.0-3)
  • Migration status for geomet (1.1.0-2 to 1.1.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geomet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gitaly (- to 16.11.6+ds1-4)
  • Migration status for gitaly (- to 16.11.6+ds1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): gitaly gitlab-shell
    • Depends: gitaly gitlab-shell
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitaly.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• glab (1.49.0-1 to 1.53.0-1)
  • Migration status for glab (1.49.0-1 to 1.53.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): glab golang-gitlab-gitlab-org-api-client-go (not considered)
    • Built-Using: glab golang-gitlab-gitlab-org-api-client-go (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glab.html
    • autopkgtest for glab/1.53.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• gp-saml-gui (0.0~git20240904-2 to 0.0~git20241120-1)
  • Migration status for gp-saml-gui (0.0~git20240904-2 to 0.0~git20241120-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/gp-saml-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• hwdata (0.393-3 to 0.394-1)
  • Migration status for hwdata (0.393-3 to 0.394-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/hwdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• i2c-tools (4.4-1 to 4.4-2)
  • Migration status for i2c-tools (4.4-1 to 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i2c-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• idjc (- to 0.9.9-1)
  • Migration status for idjc (- to 0.9.9-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idjc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ikos (- to 3.5-2)
  • Migration status for ikos (- to 3.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): ikos llvm-toolchain-14 (not considered)
    • Depends: ikos llvm-toolchain-14 (not considered)
    • Depends: ikos onetbb (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• jackson-dataformat-cbor (2.7.8-5 to 2.7.8-5.1)
  • Migration status for jackson-dataformat-cbor (2.7.8-5 to 2.7.8-5.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating jackson-dataformat-cbor will fix bugs in testing: #983664
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jackson-dataformat-cbor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kclock (24.12.1-1 to 25.03.90-1)
  • Migration status for kclock (24.12.1-1 to 25.03.90-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kclock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• keysmith (- to 25.03.90-1)
  • Migration status for keysmith (- to 25.03.90-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keysmith.html
    • Waiting for reproducibility test results on armhf - info ♻
• keyutils (1.6.3-4 to 1.6.3-5)
  • Migration status for keyutils (1.6.3-4 to 1.6.3-5): 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 keyutils/1.6.3-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keyutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libapache-mod-evasive (1.10.1-7 to 2.4.0-1)
  • Migration status for libapache-mod-evasive (1.10.1-7 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/liba/libapache-mod-evasive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libbeam-java (1.3.8-1 to 1.3.9-1)
  • Migration status for libbeam-java (1.3.8-1 to 1.3.9-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbeam-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libgedit-tepl (- to 6.13.0-2)
  • Migration status for libgedit-tepl (- to 6.13.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgedit-tepl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• liblscp (1.0.0-1 to 1.0.1-1)
  • Migration status for liblscp (1.0.0-1 to 1.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libl/liblscp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libpisp (- to 1.2.0-2)
  • Migration status for libpisp (- 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/libp/libpisp.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
• libslf4j2-java (- to 2.0.16-1.1)
  • Migration status for libslf4j2-java (- to 2.0.16-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libslf4j2-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libsmb2 (6.2+dfsg-1 to 6.2+dfsg-2)
  • Migration status for libsmb2 (6.2+dfsg-1 to 6.2+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsmb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libzypp (17.36.5-1 to 17.36.6-1)
  • Migration status for libzypp (17.36.5-1 to 17.36.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/libz/libzypp.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• live-tasks (13.0.2.1 to 13.0.3)
  • Migration status for live-tasks (13.0.2.1 to 13.0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating live-tasks would introduce bugs in testing: #1094950
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/live-tasks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-download-manager (0.1.3-5 to 0.2.1-1)
  • Migration status for lomiri-download-manager (0.1.3-5 to 0.2.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-download-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxc-ci (0.0~git20250113.158dfe2-1 to 0.0~git20250401.1736f36-1)
  • Migration status for lxc-ci (0.0~git20250113.158dfe2-1 to 0.0~git20250401.1736f36-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxc-ci.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxcfs (6.0.3-2 to 6.0.4-1)
  • Migration status for lxcfs (6.0.3-2 to 6.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxcfs.html
    • autopkgtest for lxcfs/6.0.4-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxpanel (0.10.1-4 to 0.11.0-1)
  • Migration status for lxpanel (0.10.1-4 to 0.11.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating lxpanel will fix bugs in testing: #1052376, #1075243, #855521
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxpanel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• magit-annex (1.8.1-2 to 1.9.0-1)
  • Migration status for magit-annex (1.8.1-2 to 1.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magit-annex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mathgl (- to 8.0.3-1)
  • Migration status for mathgl (- to 8.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mathgl/8.0.3-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathgl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• meta-kde (5:160 to 5:161)
  • Migration status for meta-kde (5:160 to 5:161): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Depends: meta-kde plasma-desktop
    • Depends: meta-kde plasma-workspace
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meta-kde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mgcv (1.9-1-1 to 1.9-3-1)
  • Migration status for mgcv (1.9-1-1 to 1.9-3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for r-cran-dharma/0.4.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mgcv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mono (6.12.0.199+dfsg-3 to 6.12.0.199+dfsg-6)
  • Migration status for mono (6.12.0.199+dfsg-3 to 6.12.0.199+dfsg-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating mono will fix bugs in testing: #1098958
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mono.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility reference results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-reinterval (1.1.0-3 to 1.1.0-4)
  • Migration status for node-reinterval (1.1.0-3 to 1.1.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-reinterval.html
    • autopkgtest for node-reinterval/1.1.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nodejs (20.19.0+dfsg-1 to 20.19.0+dfsg-2)
  • Migration status for nodejs (20.19.0+dfsg-1 to 20.19.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for coffeescript/2.7.0+dfsg1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for node-marked/4.2.3+ds+~4.0.7-3: riscv64: Pass
    • autopkgtest for node-stylus/0.59.0+~0.48.38-2: riscv64: Pass
    • autopkgtest for node-tape/5.6.1+~cs8.20.19-2: riscv64: Pass
    • autopkgtest for nodejs/20.19.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nodejs.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nordugrid-arc (6.21.1-3 to 7.0.0-1)
  • Migration status for nordugrid-arc (6.21.1-3 to 7.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by ellert
    • Not built on buildd: arch all binaries uploaded by ellert, a new source-only upload is needed to allow migration
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nordugrid-arc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• obs-draw-dock (- to 0.2.0-2)
  • Migration status for obs-draw-dock (- to 0.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-draw-dock.html
    • autopkgtest for obs-draw-dock/0.2.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• obs-move-transition (3.1.1-1 to 3.1.2-1)
  • Migration status for obs-move-transition (3.1.1-1 to 3.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-move-transition.html
    • autopkgtest for obs-move-transition/3.1.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• packmol (1:20.16.0-1 to 1:21.0.1-1)
  • Migration status for packmol (1:20.16.0-1 to 1:21.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/packmol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• partclone (0.3.34+repack-2 to 0.3.36+repack-1)
  • Migration status for partclone (0.3.34+repack-2 to 0.3.36+repack-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/partclone.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• plasma-discover (6.3.2-1 to 6.3.4-3)
  • Migration status for plasma-discover (6.3.2-1 to 6.3.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-discover.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• plasma-wayland-protocols (1.16.0-3 to 1.17.0-1)
  • Migration status for plasma-wayland-protocols (1.16.0-3 to 1.17.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-wayland-protocols.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pocket-reform-handbook (- to 2025-03-16+dfsg-2)
  • Migration status for pocket-reform-handbook (- to 2025-03-16+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pocket-reform-handbook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• poetry (2.1.1+dfsg-3 to 2.1.2+dfsg-1)
  • Migration status for poetry (2.1.1+dfsg-3 to 2.1.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poetry.html
    • autopkgtest for poetry/2.1.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• prosody (13.0.0-1 to 13.0.1-1)
  • Migration status for prosody (13.0.0-1 to 13.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/prosody.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• prosody-modules (0.0~hg20250316.a1a33f0f6f6e+dfsg-1 to 0.0~hg20250402.f315edc39f3d+dfsg-1)
  • Migration status for prosody-modules (0.0~hg20250316.a1a33f0f6f6e+dfsg-1 to 0.0~hg20250402.f315edc39f3d+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/p/prosody-modules.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pry (0.14.2-1 to 0.15.2-1)
  • Migration status for pry (0.14.2-1 to 0.15.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating pry/0.15.2-1/amd64 to testing makes ruby-pry-byebug/3.10.1-1/amd64 uninstallable
    • migrating pry/0.15.2-1/arm64 to testing makes ruby-pry-byebug/3.10.1-1/arm64 uninstallable
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pry.html
    • autopkgtest for pry/0.15.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• python-miltertest (- to 1.0.0-2)
  • Migration status for python-miltertest (- to 1.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-miltertest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-py-vapid (- to 1.9.2-2)
  • Migration status for python-py-vapid (- to 1.9.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-py-vapid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-xiaomi-ble (0.30.2-3 to 0.36.0-1)
  • Migration status for python-xiaomi-ble (0.30.2-3 to 0.36.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-xiaomi-ble/0.36.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xiaomi-ble.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qcoro (0.11.0-1 to 0.12.0-1)
  • Migration status for qcoro (0.11.0-1 to 0.12.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qcoro.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qjackctl (1.0.3-1 to 1.0.4-1)
  • Migration status for qjackctl (1.0.3-1 to 1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qjackctl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rifiuti2 (0.7.0-5 to 0.8.1-1)
  • Migration status for rifiuti2 (0.7.0-5 to 0.8.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for rifiuti2/0.8.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rifiuti2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ruby-ox (2.14.17-1 to 2.14.22-1)
  • Migration status for ruby-ox (2.14.17-1 to 2.14.22-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ox.html
    • autopkgtest for ruby-ox/2.14.22-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-sudo-rs (0.2.4-1 to 0.2.5-1)
  • Migration status for rust-sudo-rs (0.2.4-1 to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-sudo-rs would introduce bugs in testing: #1102251
    • autopkgtest for rust-sudo-rs/0.2.5-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sudo-rs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sqlalchemy (2.0.32+ds1-1 to 2.0.40+ds1-1)
  • Migration status for sqlalchemy (2.0.32+ds1-1 to 2.0.40+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for blazar/15.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Reference test in progress, but real test failed already ♻, s390x: Pass
    • autopkgtest for mistral/20.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for pandas/2.2.3+dfsg-8: riscv64: Pass
    • autopkgtest for sqlalchemy/2.0.40+ds1-1: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress (will not be considered a regression), s390x: Failed (not a regression)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating sqlalchemy will fix bugs in testing: #1086031, #1101868
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlalchemy.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• stylish-haskell (0.14.5.0-2 to 0.14.5.0-3)
  • Migration status for stylish-haskell (0.14.5.0-2 to 0.14.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stylish-haskell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• swift (2.34.0-5 to 2.35.0-2)
  • Migration status for swift (2.34.0-5 to 2.35.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/s/swift.html
    • autopkgtest for swift/2.35.0-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Test in progress (will not be considered a regression)
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tailspin (4.0.0+dfsg-4 to 5.1.0~dfsg-1)
  • Migration status for tailspin (4.0.0+dfsg-4 to 5.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tailspin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tomcat10 (10.1.35-1 to 10.1.40-1)
  • Migration status for tomcat10 (10.1.35-1 to 10.1.40-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomcat10.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• tomcat11 (11.0.5-1 to 11.0.6-1)
  • Migration status for tomcat11 (11.0.5-1 to 11.0.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomcat11.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility reference results on i386 - info ♻
• trapperkeeper-clojure (4.0.0-1 to 4.0.2-1)
  • Migration status for trapperkeeper-clojure (4.0.0-1 to 4.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for jruby-utils-clojure/5.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for trapperkeeper-clojure/4.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trapperkeeper-clojure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• tryton-sao (7.0.26+ds1-1 to 7.0.27+ds1-1)
  • Migration status for tryton-sao (7.0.26+ds1-1 to 7.0.27+ds1-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/tryton-sao.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tupi (- to 0.2+git08-6)
  • Migration status for tupi (- to 0.2+git08-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tupi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• usbutils (1:018-1 to 1:018-2)
  • Migration status for usbutils (1:018-1 to 1:018-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/usbutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• virtnbdbackup (2.24-1 to 2.26-1)
  • Migration status for virtnbdbackup (2.24-1 to 2.26-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtnbdbackup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• workrave (1.10.53-1 to 1.10.53-2)
  • Migration status for workrave (1.10.53-1 to 1.10.53-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 workrave will fix bugs in testing: #1101970
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/workrave.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xz-utils (5.6.4-1 to 5.8.1-1)
  • Migration status for xz-utils (5.6.4-1 to 5.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lintian/2.122.0: amd64: Pass, arm64: Pass, armel: Pass, armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for xz-utils/5.8.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xz-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• yuma123 (2.13-2.1 to 2.14-1)
  • Migration status for yuma123 (2.13-2.1 to 2.14-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yuma123.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dxvk (- to 2.6+ds-1)
  • Migration status for dxvk (- to 2.6+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dxvk/2.6+ds-1: amd64: Pass, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dxvk.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• emacs-helm-ag (- to 0.59-4)
  • Migration status for emacs-helm-ag (- to 0.59-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-helm-ag would introduce bugs in testing: #1057557
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-helm-ag.html
    • autopkgtest for emacs-helm-ag/0.59-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• jube (2.7.1-2 to 2.7.1-3)
  • Migration status for jube (2.7.1-2 to 2.7.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jube.html
    • autopkgtest for jube/2.7.1-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-cloudsync-app (- to 0.8.1+dfsg-1)
  • Migration status for lomiri-cloudsync-app (- to 0.8.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-cloudsync-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• mimalloc (3.0.1+ds-2.1 to 3.0.3+ds-1)
  • Migration status for mimalloc (3.0.1+ds-2.1 to 3.0.3+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mimalloc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• nginx-snippets (- to 1.0)
  • Migration status for nginx-snippets (- to 1.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tsimonq2@ubuntu.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nginx-snippets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• onetbb (2022.0.0-2 to 2022.1.0-1)
  • Migration status for onetbb (2022.0.0-2 to 2022.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libtbb12/2022.1.0-1/amd64 to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b2/amd64 uninstallable
    • migrating libtbb12/2022.1.0-1/arm64 to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b3/arm64 uninstallable
    • migrating libtbb12/2022.1.0-1/armel to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b2/armel uninstallable
    • migrating libtbb12/2022.1.0-1/armhf to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b2/armhf uninstallable
    • migrating libtbb12/2022.1.0-1/i386 to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b2/i386 uninstallable
    • migrating libtbb12/2022.1.0-1/mips64el to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b2/mips64el uninstallable
    • migrating libtbb12/2022.1.0-1/ppc64el to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b2/ppc64el uninstallable
    • migrating libtbb12/2022.1.0-1/riscv64 to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b2/riscv64 uninstallable
    • migrating libtbb12/2022.1.0-1/s390x to testing makes r-cran-rcppparallel/5.1.7+dfsg-5+b2/s390x uninstallable
    • autopkgtest for onetbb/2022.1.0-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for r-bioc-dada2/1.34.0+dfsg-2: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-lamw/2.2.4-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-markovchain/0.10.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-openmx/2.21.13+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-prophet/1.0+dfsg-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-rcppparallel/5.1.7+dfsg-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-rstan/2.32.7-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onetbb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• pcsc-lite (2.3.1-1 to 2.3.3-1)
  • Migration status for pcsc-lite (2.3.1-1 to 2.3.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for openjdk-25/25~16ea-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcsc-lite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• plasma-browser-integration (6.3.2-3 to 6.3.4-1)
  • Migration status for plasma-browser-integration (6.3.2-3 to 6.3.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): plasma-browser-integration plasma-workspace (not considered)
    • Depends: plasma-browser-integration plasma-workspace (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-browser-integration.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• plasma-desktop (4:6.3.2-3 to 4:6.3.4-1)
  • Migration status for plasma-desktop (4:6.3.2-3 to 4:6.3.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): plasma-desktop kwin (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): plasma-desktop plasma-workspace
    • Depends: plasma-desktop plasma-workspace
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-desktop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• plasma-workspace (4:6.3.2-2 to 4:6.3.4-1)
  • Migration status for plasma-workspace (4:6.3.2-2 to 4:6.3.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): plasma-workspace kwin (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-workspace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• powerdevil (4:6.3.2-2 to 4:6.3.4-1)
  • Migration status for powerdevil (4:6.3.2-2 to 4:6.3.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): powerdevil plasma-workspace (not considered)
    • Depends: powerdevil plasma-workspace (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/powerdevil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• pypdf (4.3.1-1 to 5.4.0-1)
  • Migration status for pypdf (4.3.1-1 to 5.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 5 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pypdf.html
    • autopkgtest for pypdf/5.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pytorch-geometric (- to 2.6.1-6)
  • Migration status for pytorch-geometric (- to 2.6.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytorch-geometric/2.6.1-6: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-geometric.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• sddm-kcm (- to 4:6.3.4-1)
  • Migration status for sddm-kcm (- to 4:6.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sddm-kcm would introduce bugs in testing: #1090041
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sddm-kcm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• tasksel (3.79 to 3.80)
  • Migration status for tasksel (3.79 to 3.80): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debian-edu/2.12.16: amd64: Pass, arm64: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress (will not be considered a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tasksel.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• arctica-greeter (0.99.8.4-2 to 0.99.8.8-1)
  • Migration status for arctica-greeter (0.99.8.4-2 to 0.99.8.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by mike.gabriel@das-netzwerkteam.de
    • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arctica-greeter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• django-picklefield (3.2.0-1 to 3.3.0-1)
  • Migration status for django-picklefield (3.2.0-1 to 3.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 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-picklefield.html
    • autopkgtest for django-picklefield/3.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• firefox (- to 137.0-1)
  • Migration status for firefox (- to 137.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firefox would introduce bugs in testing: #1017919, #817954, #992263, #993659
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• ironic-python-agent (9.14.0-5 to 10.2.0-3)
  • Migration status for ironic-python-agent (9.14.0-5 to 10.2.0-3): Will attempt migration (Any information below is purely informational)
    • Build-Depends-Indep: ironic-python-agent python-oslo.utils
    • Depends: ironic-python-agent python-oslo.utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ironic-python-agent.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for ironic-python-agent/10.2.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• networking-bgpvpn (21.0.0-3 to 22.0.0-1)
  • Migration status for networking-bgpvpn (21.0.0-3 to 22.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for networking-bagpipe/22.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for networking-bgpvpn/22.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Build-Depends-Indep: networking-bgpvpn neutron
    • Depends: networking-bgpvpn neutron
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-bgpvpn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 6 days old (needed 5 days)
• networking-sfc (19.0.0-2 to 20.0.0-1)
  • Migration status for networking-sfc (19.0.0-2 to 20.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for networking-bagpipe/22.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for networking-sfc/20.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Build-Depends-Indep: networking-sfc neutron
    • Depends: networking-sfc neutron
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-sfc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 6 days old (needed 5 days)
• neutron (2:25.1.0-1 to 2:26.0.0-1)
  • Migration status for neutron (2:25.1.0-1 to 2:26.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: neutron python-psutil (not considered)
    • Depends: neutron python-psutil (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neutron.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • 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
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 6 days old (needed 5 days)
• neutron-taas (12.0.0+git.2024.10.07.749ac4557c-2 to 15.0.0-1)
  • Migration status for neutron-taas (12.0.0+git.2024.10.07.749ac4557c-2 to 15.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: neutron-taas neutron (not considered)
    • Depends: neutron-taas neutron (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neutron-taas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 6 days old (needed 5 days)
• neutron-vpnaas (2:25.0.0-2 to 2:26.0.0-1)
  • Migration status for neutron-vpnaas (2:25.0.0-2 to 2:26.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for neutron-vpnaas/2:26.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Build-Depends-Indep: neutron-vpnaas neutron
    • Depends: neutron-vpnaas neutron
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neutron-vpnaas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 6 days old (needed 5 days)
• nova (2:30.0.0-7 to 2:31.0.0-1)
  • Migration status for nova (2:30.0.0-7 to 2:31.0.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends-Indep: nova python-oslo.utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nova.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 6 days old (needed 5 days)
• nss (2:3.109-1 to 2:3.110-1)
  • Migration status for nss (2:3.109-1 to 2:3.110-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for openjdk-25/25~16ea-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nss.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 6 days old (needed 5 days)
• pytest (8.3.5-1 to 8.3.5-2)
  • Migration status for pytest (8.3.5-1 to 8.3.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adios4dolfinx/0.9.3-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for apprise/1.9.2-1: riscv64: Pass
    • autopkgtest for billiard/4.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for crmsh/4.6.0-4: riscv64: Pass
    • autopkgtest for fonttools/4.55.3-2: riscv64: Pass
    • autopkgtest for ipyparallel/8.8.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for pandas/2.2.3+dfsg-8: riscv64: Pass
    • autopkgtest for pytest/8.3.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-authlib/1.5.1-1: riscv64: Pass
    • autopkgtest for python-bumps/1.0.0a13-1: riscv64: Pass
    • autopkgtest for radicale/3.5.0-1: riscv64: Pass
    • autopkgtest for superqt/0.7.2-1: riscv64: Pass
  • Additional info:
    • Updating pytest will fix bugs in testing: #1101860
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• python-django-braces (1.16.0-1 to 1.17.0-1)
  • Migration status for python-django-braces (1.16.0-1 to 1.17.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-braces.html
    • autopkgtest for python-django-braces/1.17.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-django-channels (4.2.0-1 to 4.2.2-1)
  • Migration status for python-django-channels (4.2.0-1 to 4.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 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-channels.html
    • autopkgtest for python-django-channels/4.2.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-django-storages (1.14.4-2 to 1.14.5-1)
  • Migration status for python-django-storages (1.14.4-2 to 1.14.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-storages.html
    • autopkgtest for python-django-storages/1.14.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-django-timezone-field (7.0-1 to 7.1-1)
  • Migration status for python-django-timezone-field (7.0-1 to 7.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-timezone-field.html
    • autopkgtest for python-django-timezone-field/7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-djangorestframework-simplejwt (5.4.0-1 to 5.5.0-1)
  • Migration status for python-djangorestframework-simplejwt (5.4.0-1 to 5.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-djangorestframework-simplejwt.html
    • autopkgtest for python-djangorestframework-simplejwt/5.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-djangosaml2 (1.9.3-1 to 1.10.1-1)
  • Migration status for python-djangosaml2 (1.9.3-1 to 1.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-djangosaml2.html
    • autopkgtest for python-djangosaml2/1.10.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-duo-client (5.4.0-1 to 5.5.0-1)
  • Migration status for python-duo-client (5.4.0-1 to 5.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-duo-client.html
    • autopkgtest for python-duo-client/5.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-exchangelib (5.5.0-1 to 5.5.1-1)
  • Migration status for python-exchangelib (5.5.0-1 to 5.5.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-exchangelib.html
    • autopkgtest for python-exchangelib/5.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• vitrage (- to 14.0.0-1)
  • Migration status for vitrage (- to 14.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for vitrage/14.0.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/v/vitrage.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• cdebconf (0.277 to 0.278)
  • Migration status for cdebconf (0.277 to 0.278): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for aide/0.18.8-3: riscv64: Pass
    • autopkgtest for blazar/15.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for cacti/1.2.28+ds1-4: riscv64: Pass
    • autopkgtest for ceilometer/1:24.0.0~rc1-2: riscv64: No tests, superficial or marked flaky
    • autopkgtest for designate/1:19.0.0-4: riscv64: Pass
    • autopkgtest for heat/1:23.0.0-5: riscv64: Pass
    • autopkgtest for libvirt/11.1.0-1: riscv64: Pass
    • autopkgtest for mistral/19.0.0-2: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for nncp/8.11.0-3: riscv64: Pass
    • autopkgtest for util-linux/2.40.4-5: riscv64: Pass
    • autopkgtest for yggdrasil/0.5.12-1: riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdebconf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• choose-mirror (2.129 to 2.130)
  • Migration status for choose-mirror (2.129 to 2.130): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: choose-mirror cdebconf (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• cmake (3.31.6-1 to 3.31.6-2)
  • Migration status for cmake (3.31.6-1 to 3.31.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for chemps2/1.8.12-4: amd64: Test in progress (will not be considered a regression), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for cmake/3.31.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Pass, s390x: Pass
    • autopkgtest for mbedtls/3.6.2-3: riscv64: Pass
  • Additional info:
    • Updating cmake will fix bugs in testing: #1101604
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmake.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• lua-wsapi (1.6.1-2 to 1.6.1-3)
  • Migration status for lua-wsapi (1.6.1-2 to 1.6.1-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-wsapi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• main-menu (1.68 to 1.69)
  • Migration status for main-menu (1.68 to 1.69): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: main-menu cdebconf (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• mistune (3.0.2-2 to 3.1.3-1)
  • Migration status for mistune (3.0.2-2 to 3.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for hyperkitty/1.3.12-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mistune/3.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-schema-salad/8.8.20241206093842-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mistune.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• mmdebstrap (1.5.6-4 to 1.5.6-5)
  • Migration status for mmdebstrap (1.5.6-4 to 1.5.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debomatic/0.40-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for mmdebstrap/1.5.6-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mmdebstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• netcfg (1.194 to 1.195)
  • Migration status for netcfg (1.194 to 1.195): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: netcfg cdebconf (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• nvidia-graphics-drivers-tesla (- to 525.147.05-14)
  • Migration status for nvidia-graphics-drivers-tesla (- to 525.147.05-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla would introduce bugs in testing: #1085244
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-tesla/525.147.05-14: 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 ♻
    • 7 days old (needed 5 days)
• pdfsam (4.3.4-1 to 4.3.4-2)
  • Migration status for pdfsam (4.3.4-1 to 4.3.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pdfsam bouncycastle (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating pdfsam will fix bugs in testing: #1095365
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfsam.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• promod3 (- to 3.4.2+ds-1)
  • Migration status for promod3 (- to 3.4.2+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • promod3/arm64 has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/promod3.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• rust-astral-tokio-tar (0.5.1-1 to 0.5.2-1)
  • Migration status for rust-astral-tokio-tar (0.5.1-1 to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-astral-tokio-tar/0.5.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-astral-tokio-tar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• 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:
    • autopkgtest for whizzytex/1.5.0-0.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whizzytex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• wireguard (1.0.20210914-1.1 to 1.0.20210914-2)
  • Migration status for wireguard (1.0.20210914-1.1 to 1.0.20210914-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wireguard would introduce bugs in testing: #1102292
    • autopkgtest for netplan.io/1.1.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for wireguard/1.0.20210914-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wireguard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• xsystem35 (2.13.0-0.1 to 2.14.2-1)
  • Migration status for xsystem35 (2.13.0-0.1 to 2.14.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
    • Too young, only 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xsystem35.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• imagemagick (8:7.1.1.43+dfsg1-1 to 8:7.1.1.46+dfsg1-1)
  • Migration status for imagemagick (8:7.1.1.43+dfsg1-1 to 8:7.1.1.46+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for imagemagick/8:7.1.1.46+dfsg1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for xplanet/1.3.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imagemagick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• linux86 (0.16.17-3.10 to 0.16.21-1)
  • Migration status for linux86 (0.16.17-3.10 to 0.16.21-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux86.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 8 days old (needed 5 days)
• lloconv (6.1.1-1 to 6.1.2-1)
  • Migration status for lloconv (6.1.1-1 to 6.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lloconv/mips64el has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lloconv.html
    • autopkgtest for lloconv/6.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• lomiri-ui-extras (0.6.3-2 to 0.7.0-2)
  • Migration status for lomiri-ui-extras (0.6.3-2 to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • qml6-module-lomiri-components-extras/amd64 has unsatisfiable dependency
    • qml6-module-lomiri-components-extras/arm64 has unsatisfiable dependency
    • qml6-module-lomiri-components-extras/armel has unsatisfiable dependency
    • qml6-module-lomiri-components-extras/armhf has unsatisfiable dependency
    • qml6-module-lomiri-components-extras/i386 has unsatisfiable dependency
    • qml6-module-lomiri-components-extras/mips64el has unsatisfiable dependency
    • qml6-module-lomiri-components-extras/ppc64el has unsatisfiable dependency
    • qml6-module-lomiri-components-extras/riscv64 has unsatisfiable dependency
    • qml6-module-lomiri-components-extras/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lomiri-ui-extras.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• mpich (4.2.1-5 to 4.3.0-4)
  • Migration status for mpich (4.2.1-5 to 4.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mpich would introduce bugs in testing: #1089694, #1101686
    • autopkgtest for armci-mpi/0.4-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for bagel/1.2.2-8: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Failed (not a regression)
    • autopkgtest for eztrace/2.1.1-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mpi-defaults/1.18: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for mpich/4.3.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for nwchem/7.2.3-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Test in progress (will not be considered a regression), armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • autopkgtest for scifem/0.3.1-1: riscv64: Pass
    • Depends: mpich libfabric (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpich.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 8 days old (needed 5 days)
• petsc (3.22.3+dfsg1-1 to 3.22.5+dfsg1-1)
  • Migration status for petsc (3.22.3+dfsg1-1 to 3.22.5+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-6: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for fenicsx-performance-tests/0.9.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for petsc/3.22.5+dfsg1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for slepc/3.22.2+dfsg1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for sundials/7.1.1+dfsg1-8: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/petsc.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 8 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 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• python-openleadr-python (- to 0.5.34+dfsg.1-2)
  • Migration status for python-openleadr-python (- to 0.5.34+dfsg.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-openleadr-python.html
    • autopkgtest for python-openleadr-python/0.5.34+dfsg.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-cap-async-std (- to 3.4.1-1)
  • Migration status for rust-cap-async-std (- to 3.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cap-async-std-dev/amd64 has unsatisfiable dependency
    • librust-cap-async-std-dev/arm64 has unsatisfiable dependency
    • librust-cap-async-std-dev/armel has unsatisfiable dependency
    • librust-cap-async-std-dev/armhf has unsatisfiable dependency
    • librust-cap-async-std-dev/i386 has unsatisfiable dependency
    • librust-cap-async-std-dev/mips64el has unsatisfiable dependency
    • librust-cap-async-std-dev/ppc64el has unsatisfiable dependency
    • librust-cap-async-std-dev/riscv64 has unsatisfiable dependency
    • librust-cap-async-std-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cap-async-std.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-cap-fs-ext (- to 3.4.1-1)
  • Migration status for rust-cap-fs-ext (- to 3.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cap-fs-ext-dev/amd64 has unsatisfiable dependency
    • Not built on buildd: arch amd64 binaries uploaded by weepingclown@disroot.org
    • Build-Depends(-Arch): rust-cap-fs-ext rust-cap-std (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cap-fs-ext.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-cap-net-ext (- to 3.4.1-1)
  • Migration status for rust-cap-net-ext (- to 3.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by weepingclown@disroot.org
    • Build-Depends(-Arch): rust-cap-net-ext rust-cap-std (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cap-net-ext.html
    • autopkgtest for rust-cap-net-ext/3.4.1-1: amd64: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-cap-std (- to 3.4.1-1)
  • Migration status for rust-cap-std (- to 3.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cap-std-dev/amd64 has unsatisfiable dependency
    • librust-cap-std-dev/arm64 has unsatisfiable dependency
    • librust-cap-std-dev/armel has unsatisfiable dependency
    • librust-cap-std-dev/armhf has unsatisfiable dependency
    • librust-cap-std-dev/i386 has unsatisfiable dependency
    • librust-cap-std-dev/mips64el has unsatisfiable dependency
    • librust-cap-std-dev/ppc64el has unsatisfiable dependency
    • librust-cap-std-dev/riscv64 has unsatisfiable dependency
    • librust-cap-std-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cap-std.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-cap-tempfile (- to 3.4.1-1)
  • Migration status for rust-cap-tempfile (- to 3.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by weepingclown@disroot.org
    • Build-Depends(-Arch): rust-cap-tempfile rust-cap-std (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cap-tempfile.html
    • autopkgtest for rust-cap-tempfile/3.4.1-1: amd64: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-cap-time-ext (- to 3.4.1-1)
  • Migration status for rust-cap-time-ext (- to 3.4.1-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-cap-time-ext.html
    • autopkgtest for rust-cap-time-ext/3.4.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-sequoia-chameleon-gnupg (0.12.1-1 to 0.13.1-2)
  • Migration status for rust-sequoia-chameleon-gnupg (0.12.1-1 to 0.13.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lintian/2.122.0: amd64: Pass, arm64: Pass, armel: Pass, armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-chameleon-gnupg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• btas (- to 1.0.0-1)
  • Migration status for btas (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating btas would introduce bugs in testing: #1028634
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• fenics-dolfinx (1:0.9.0-6 to 1:0.9.0-7)
  • Migration status for fenics-dolfinx (1:0.9.0-6 to 1:0.9.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fenics-dolfinx/1:0.9.0-7: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for fenicsx-performance-tests/0.9.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for scifem/0.3.1-1: riscv64: Pass
    • Depends: fenics-dolfinx petsc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenics-dolfinx.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 9 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
    • 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 armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• haskell-ogma-cli (- to 1.7.0-1)
  • Migration status for haskell-ogma-cli (- to 1.7.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-ogma-cli haskell-ogma-core (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 9 days old (needed 5 days)
• haskell-ogma-core (- to 1.7.0-1)
  • Migration status for haskell-ogma-core (- to 1.7.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-ogma-core haskell-ogma-language-xlsx (not considered)
    • Build-Depends-Indep: haskell-ogma-core haskell-ogma-language-xlsx (not considered)
    • Depends: haskell-ogma-core haskell-ogma-language-xlsx (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): haskell-ogma-core haskell-ogma-language-csv
    • Build-Depends(-Arch): haskell-ogma-core haskell-ogma-language-lustre
    • Build-Depends-Indep: haskell-ogma-core haskell-ogma-language-csv
    • Build-Depends-Indep: haskell-ogma-core haskell-ogma-language-lustre
    • Depends: haskell-ogma-core haskell-ogma-language-csv
    • Depends: haskell-ogma-core haskell-ogma-language-lustre
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 9 days old (needed 5 days)
• haskell-ogma-language-csv (- to 1.7.0-1)
  • Migration status for haskell-ogma-language-csv (- to 1.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 9 of 10 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• haskell-ogma-language-lustre (- to 1.7.0-1)
  • Migration status for haskell-ogma-language-lustre (- to 1.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 9 of 10 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• haskell-ogma-language-xlsx (- to 1.7.0-1)
  • Migration status for haskell-ogma-language-xlsx (- to 1.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 9 of 10 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libpath-tiny-perl (0.146-1 to 0.148-1)
  • Migration status for libpath-tiny-perl (0.146-1 to 0.148-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libconfig-model-itself-perl/2.023-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for libpath-tiny-perl/0.148-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpath-tiny-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-450 (- to 450.248.02-10)
  • Migration status for nvidia-graphics-drivers-tesla-450 (- to 450.248.02-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-450 would introduce bugs in testing: #1014304
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-tesla-450/450.248.02-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 ♻
    • 9 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-460 (- to 460.106.00-20)
  • Migration status for nvidia-graphics-drivers-tesla-460 (- to 460.106.00-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-460 would introduce bugs in testing: #1027704
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-tesla-460/460.106.00-20: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • 9 days old (needed 5 days)
• python-xarray (2025.01.2-1 to 2025.03.0-2)
  • Migration status for python-xarray (2025.01.2-1 to 2025.03.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pandas/2.2.3+dfsg-8: riscv64: Pass
    • autopkgtest for python-xarray/2025.03.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for xarray-sentinel/0.9.5+ds-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating python-xarray will fix bugs in testing: #1100293
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xarray.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 9 days old (needed 5 days)
• python-ytmusicapi (- to 1.10.2-1)
  • Migration status for python-ytmusicapi (- to 1.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ytmusicapi would introduce bugs in testing: #1101671
    • Not built on buildd: arch all binaries uploaded by tiposchi@tiscali.it, a new source-only upload is needed to allow migration
    • Too young, only 9 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ytmusicapi.html
• rust-gbm-sys (- to 0.4.0-2)
  • Migration status for rust-gbm-sys (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gbm-sys/0.4.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gbm-sys.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• rust-vergen (8.3.2-4 to 8.3.2-6)
  • Migration status for rust-vergen (8.3.2-4 to 8.3.2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-vergen rust-cargo-metadata (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-vergen.html
    • autopkgtest for rust-sequoia-git/0.1.0-1: riscv64: Pass
    • autopkgtest for rust-vergen/8.3.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• adduser (3.149 to 3.150)
  • Migration status for adduser (3.149 to 3.150): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adduser/3.150: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for ceilometer/1:24.0.0~rc1-2: riscv64: No tests, superficial or marked flaky
    • autopkgtest for chrony/4.6.1-2: amd64: Failed (not a regression), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for designate/1:19.0.0-4: riscv64: Pass
    • autopkgtest for heat/1:23.0.0-5: riscv64: Pass
    • autopkgtest for mistral/20.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for nncp/8.11.0-3: riscv64: Pass
    • autopkgtest for radicale/3.5.0-1: riscv64: Pass
    • autopkgtest for util-linux/2.40.4-5: riscv64: Pass
    • autopkgtest for yggdrasil/0.5.12-1: riscv64: Pass
  • Additional info:
    • Updating adduser will fix bugs in testing: #1101454
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adduser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• debian-edu-router (2.12.8 to 2.13.0~beta3)
  • Migration status for debian-edu-router (2.12.8 to 2.13.0~beta3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/debian-edu-router.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• file (1:5.45-3 to 1:5.46-4)
  • Migration status for file (1:5.45-3 to 1:5.46-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for file/1:5.46-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for gnumed-client/1.8.19+dfsg-1: riscv64: No tests, superficial or marked flaky
    • autopkgtest for lintian/2.121.1+nmu1: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for munin/2.0.76-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for podman/5.4.1+ds1-3: riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/file.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 2 days)
• freerdp3 (3.14.0+dfsg-1 to 3.14.1+dfsg-2)
  • Migration status for freerdp3 (3.14.0+dfsg-1 to 3.14.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freerdp3 would introduce bugs in testing: #1101910
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freerdp3.html
    • autopkgtest for freerdp3/3.14.1+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• ironic (1:26.1.1-4 to 1:29.0.0-2)
  • Migration status for ironic (1:26.1.1-4 to 1:29.0.0-2): Will attempt migration (Any information below is purely informational)
    • Build-Depends-Indep: ironic python-oslo.utils
    • Depends: ironic python-oslo.utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ironic.html
    • autopkgtest for ironic/1:29.0.0-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • No reference result, but not reproducibility on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 10 days old (needed 5 days)
• kiwi (- to 10.2.16-1)
  • Migration status for kiwi (- to 10.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency
  • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-390xx (- to 390.157-12)
  • Migration status for nvidia-graphics-drivers-legacy-390xx (- to 390.157-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-390xx would introduce bugs in testing: #1006719, #1033776, #1039680, #1055138, #1064985, #1072794, #1085970, #1093910
    • Depends: nvidia-graphics-drivers-legacy-390xx nvidia-graphics-drivers-tesla-418 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-legacy-390xx/390.157-12: amd64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 10 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-418 (- to 418.226.00-18)
  • Migration status for nvidia-graphics-drivers-tesla-418 (- to 418.226.00-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xserver-xorg-video-nvidia-tesla-418/amd64 has unsatisfiable dependency
    • xserver-xorg-video-nvidia-tesla-418/ppc64el has unsatisfiable dependency
    • Updating nvidia-graphics-drivers-tesla-418 would introduce bugs in testing: #1005930, #1006718, #1011143, #1016617, #1025282, #1033777, #1039681, #1055139, #1064986, #1072795, #1081648, #1085971, #1093911
    • autopkgtest for nvidia-graphics-drivers-tesla-418/418.226.00-18: 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
    • 10 days old (needed 5 days)
• orange-spectroscopy (- to 0.8.1+git20250328-2)
  • Migration status for orange-spectroscopy (- to 0.8.1+git20250328-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orange-spectroscopy/0.8.1+git20250328-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange-spectroscopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• pgpainless (1.6.8-1 to 1.6.9-1)
  • Migration status for pgpainless (1.6.8-1 to 1.6.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pgpainless bouncycastle (not considered)
    • Depends: pgpainless bouncycastle (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating pgpainless will fix bugs in testing: #1100250, #1101420
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgpainless.html
    • autopkgtest for pgpainless/1.6.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• rust-pyo3-async-runtimes (- to 0.22.0-2)
  • Migration status for rust-pyo3-async-runtimes (- to 0.22.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-pyo3-async-runtimes/0.22.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pyo3-async-runtimes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• asterisk (- to 1:22.3.0~dfsg+~cs6.15.60671435-1)
  • Migration status for asterisk (- to 1:22.3.0~dfsg+~cs6.15.60671435-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asterisk would introduce bugs in testing: #1031046
    • Build-Depends(-Arch): asterisk uw-imap (not considered)
    • Depends: asterisk uw-imap (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk.html
    • autopkgtest for asterisk/1:22.3.0~dfsg+~cs6.15.60671435-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 11 days old (needed 5 days)
• pyserial-asyncio-fast (0.14-2 to 0.16-1)
  • Migration status for pyserial-asyncio-fast (0.14-2 to 0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pyserial-asyncio-fast unsatisfiable Build-Depends(-Arch) on amd64: python3-setuptools (>= 77)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyserial-asyncio-fast.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• python-oslo.utils (7.3.0-5 to 8.2.0-4)
  • Migration status for python-oslo.utils (7.3.0-5 to 8.2.0-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-oslo.utils.html
    • autopkgtest for python-oslo.utils/8.2.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 days)
• python-oslo.versionedobjects (3.4.0-3 to 3.6.0-3)
  • Migration status for python-oslo.versionedobjects (3.4.0-3 to 3.6.0-3): Will attempt migration (Any information below is purely informational)
    • Build-Depends-Indep: python-oslo.versionedobjects python-oslo.utils
    • Depends: python-oslo.versionedobjects python-oslo.utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-oslo.versionedobjects.html
    • autopkgtest for designate/1:19.0.0-4: riscv64: Pass
    • autopkgtest for python-oslo.versionedobjects/3.6.0-3: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Failed (not a regression), s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• rust-shadow-rs (0.37.0-2 to 1.1.1-2)
  • Migration status for rust-shadow-rs (0.37.0-2 to 1.1.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-shadow-rs rust-cargo-metadata (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-shadow-rs.html
    • autopkgtest for rust-shadow-rs/1.1.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 days)
• gnome-authenticator (4.5.0-4 to 4.6.2-1)
  • Migration status for gnome-authenticator (4.5.0-4 to 4.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnome-authenticator rust-zip (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-authenticator.html
    • autopkgtest for gnome-authenticator/4.6.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 12 days old (needed 5 days)
• rust-bacon (- to 3.12.0-1)
  • Migration status for rust-bacon (- to 3.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-bacon would introduce bugs in testing: #1099838
    • Build-Depends(-Arch): rust-bacon rust-cargo-metadata (not considered)
    • Depends: rust-bacon rust-cargo-metadata (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bacon.html
    • autopkgtest for rust-bacon/3.12.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• rust-cargo-auditable (0.6.1-3 to 0.6.6-1)
  • Migration status for rust-cargo-auditable (0.6.1-3 to 0.6.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-cargo-auditable rust-cargo-metadata (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-auditable.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-cargo-binutils (0.3.6-1 to 0.3.6-2)
  • Migration status for rust-cargo-binutils (0.3.6-1 to 0.3.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-cargo-binutils rust-cargo-metadata (not considered)
    • Depends: rust-cargo-binutils rust-cargo-metadata (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-binutils.html
    • autopkgtest for rust-cargo-binutils/0.3.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• rust-cargo-debstatus (0.6.3-1 to 0.6.3-2)
  • Migration status for rust-cargo-debstatus (0.6.3-1 to 0.6.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-cargo-debstatus rust-cargo-metadata (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-debstatus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-cargo-lichking (0.9.0-4 to 0.9.0-5)
  • Migration status for rust-cargo-lichking (0.9.0-4 to 0.9.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-cargo-lichking rust-cargo-metadata (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-lichking.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-cargo-metadata (0.15.4-3 to 0.19.2-1)
  • Migration status for rust-cargo-metadata (0.15.4-3 to 0.19.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-cargo-metadata-dev/0.19.2-1/amd64 to testing makes librust-skeptic-dev/0.13.7-4/amd64 uninstallable
    • migrating librust-cargo-metadata-dev/0.19.2-1/arm64 to testing makes librust-skeptic-dev/0.13.7-4/arm64 uninstallable
    • migrating librust-cargo-metadata-dev/0.19.2-1/armel to testing makes librust-skeptic-dev/0.13.7-4/armel uninstallable
    • migrating librust-cargo-metadata-dev/0.19.2-1/armhf to testing makes librust-skeptic-dev/0.13.7-4/armhf uninstallable
    • migrating librust-cargo-metadata-dev/0.19.2-1/i386 to testing makes librust-skeptic-dev/0.13.7-4/i386 uninstallable
    • migrating librust-cargo-metadata-dev/0.19.2-1/mips64el to testing makes librust-skeptic-dev/0.13.7-4/mips64el uninstallable
    • migrating librust-cargo-metadata-dev/0.19.2-1/ppc64el to testing makes librust-skeptic-dev/0.13.7-4/ppc64el uninstallable
    • migrating librust-cargo-metadata-dev/0.19.2-1/riscv64 to testing makes librust-skeptic-dev/0.13.7-4/riscv64 uninstallable
    • migrating librust-cargo-metadata-dev/0.19.2-1/s390x to testing makes librust-skeptic-dev/0.13.7-4/s390x uninstallable
    • Implicit dependency: rust-cargo-metadata rust-cargo-binutils
    • Implicit dependency: rust-cargo-metadata rust-libbpf-cargo
    • Implicit dependency: rust-cargo-metadata rust-shadow-rs
    • Implicit dependency: rust-cargo-metadata rust-vergen
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-metadata.html
    • autopkgtest for rust-cargo-metadata/0.19.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• rust-cargo-mutants (23.10.0-1 to 25.0.0-1)
  • Migration status for rust-cargo-mutants (23.10.0-1 to 25.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): rust-cargo-mutants rust-cargo-metadata (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-mutants.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-cfb (0.7.3-1 to 0.10.0-1)
  • Migration status for rust-cfb (0.7.3-1 to 0.10.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-cfb rust-infer (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cfb.html
    • autopkgtest for rust-cfb/0.10.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• rust-gix-archive (0.18.0-1 to 0.18.0-2)
  • Migration status for rust-gix-archive (0.18.0-1 to 0.18.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-gix-archive rust-zip (not considered)
    • Depends: rust-gix-archive rust-zip (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix-archive.html
    • autopkgtest for rust-gix-archive/0.18.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• rust-gping (1.19.0-2 to 1.19.0-3)
  • Migration status for rust-gping (1.19.0-2 to 1.19.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-gping rust-shadow-rs (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gping.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-grcov (0.8.20-1 to 0.8.22-1)
  • Migration status for rust-grcov (0.8.20-1 to 0.8.22-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-grcov rust-zip (not considered)
    • Depends: rust-grcov rust-zip (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-grcov rust-infer
    • Depends: rust-grcov rust-infer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-grcov.html
    • autopkgtest for rust-grcov/0.8.22-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• rust-http-types (2.12.0-2 to 2.12.0-3)
  • Migration status for rust-http-types (2.12.0-2 to 2.12.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-http-types rust-infer (not considered)
    • Depends: rust-http-types rust-infer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-http-types.html
    • autopkgtest for rust-http-types/2.12.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• rust-infer (0.16.0-1 to 0.19.0-1)
  • Migration status for rust-infer (0.16.0-1 to 0.19.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-infer rust-grcov (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-infer rust-cfb
    • Depends: rust-infer rust-cfb
    • Implicit dependency: rust-infer rust-http-types
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-infer.html
    • autopkgtest for rust-infer/0.19.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• rust-libbpf-cargo (0.25.0~beta.1-1 to 0.25.0~beta.1-2)
  • Migration status for rust-libbpf-cargo (0.25.0~beta.1-1 to 0.25.0~beta.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-libbpf-cargo rust-cargo-metadata (not considered)
    • Depends: rust-libbpf-cargo rust-cargo-metadata (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libbpf-cargo.html
    • autopkgtest for rust-libbpf-cargo/0.25.0~beta.1-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-tealdeer (1.7.0-2 to 1.7.2-1)
  • Migration status for rust-tealdeer (1.7.0-2 to 1.7.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-tealdeer rust-zip (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tealdeer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-zip (0.6.6-5 to 2.5.0-1)
  • Migration status for rust-zip (0.6.6-5 to 2.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-zip-dev/2.5.0-1/amd64 to testing makes librust-unzip-dev/0.1.0-1+b1/amd64 uninstallable
    • migrating librust-zip-dev/2.5.0-1/arm64 to testing makes librust-unzip-dev/0.1.0-1+b1/arm64 uninstallable
    • migrating librust-zip-dev/2.5.0-1/armel to testing makes librust-unzip-dev/0.1.0-1+b1/armel uninstallable
    • migrating librust-zip-dev/2.5.0-1/armhf to testing makes librust-unzip-dev/0.1.0-1+b1/armhf uninstallable
    • migrating librust-zip-dev/2.5.0-1/i386 to testing makes librust-unzip-dev/0.1.0-1+b1/i386 uninstallable
    • migrating librust-zip-dev/2.5.0-1/mips64el to testing makes librust-unzip-dev/0.1.0-1+b1/mips64el uninstallable
    • migrating librust-zip-dev/2.5.0-1/ppc64el to testing makes librust-unzip-dev/0.1.0-1+b1/ppc64el uninstallable
    • migrating librust-zip-dev/2.5.0-1/riscv64 to testing makes librust-unzip-dev/0.1.0-1+b1/riscv64 uninstallable
    • migrating librust-zip-dev/2.5.0-1/s390x to testing makes librust-unzip-dev/0.1.0-1+b1/s390x uninstallable
    • Implicit dependency: rust-zip rust-gix-archive
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zip.html
    • autopkgtest for rust-zip/2.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• golang-gitlab-gitlab-org-api-client-go (- to 0.123.0-1)
  • Migration status for golang-gitlab-gitlab-org-api-client-go (- to 0.123.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-gitlab-gitlab-org-api-client-go would introduce bugs in testing: #1101345
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gitlab-gitlab-org-api-client-go.html
    • autopkgtest for golang-gitlab-gitlab-org-api-client-go/0.123.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• gsad (- to 24.2.3-1)
  • Migration status for gsad (- to 24.2.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gsad gvmd (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gsad gvm-libs (not considered)
    • Depends: gsad gvm-libs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• gvmd (- to 25.1.3-1)
  • Migration status for gvmd (- to 25.1.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvmd ospd-openvas (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gvmd gvm-libs (not considered)
    • Depends: gvmd gvm-libs (not considered)
    • Depends: gvmd pg-gvm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvmd.html
    • autopkgtest for gvmd/25.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• hurd (- to 1:0.9.git20250304-3)
  • Migration status for hurd (- to 1:0.9.git20250304-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hurd would introduce bugs in testing: #838244
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libc0.3-dev (>= 2.33-2~1)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-disk-dev (>= 0~20211031-2)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-usb-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libacpica-dev
    • Not touching package due to block request by freeze (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hurd.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 13 days old (needed 5 days)
• matplotlib (3.8.3-7 to 3.10.1+dfsg1-2)
  • Migration status for matplotlib (3.8.3-7 to 3.10.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for matplotlib/3.10.1+dfsg1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for pandas/2.2.3+dfsg-8: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-bumps/1.0.0a13-1: riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matplotlib.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 13 days old (needed 5 days)
• openvas-scanner (- to 23.16.1-1)
  • Migration status for openvas-scanner (- to 23.16.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openvas-scanner gvm-libs (not considered)
    • Depends: openvas-scanner gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvas-scanner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• pg-gvm (- to 22.6.8-1)
  • Migration status for pg-gvm (- to 22.6.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• python-djvulibre (0.9.0-7 to 0.9.1-1)
  • Migration status for python-djvulibre (0.9.0-7 to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-djvulibre/0.9.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-djvulibre.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• faust (2.77.3+ds-2 to 2.79.3+ds-1)
  • Migration status for faust (2.77.3+ds-2 to 2.79.3+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/faust.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• octave-image (2.14.0-5 to 2.16.0-1)
  • Migration status for octave-image (2.14.0-5 to 2.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for octave-image/2.16.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-image.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• fuse3 (3.17.1~rc1-3 to 3.17.1-1)
  • Migration status for fuse3 (3.17.1~rc1-3 to 3.17.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fuse3 would introduce bugs in testing: #1101305
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fuse3.html
    • autopkgtest for libvirt/11.1.0-1: riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• gvm-libs (- to 22.18.1-1)
  • Migration status for gvm-libs (- to 22.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gvm-libs would introduce bugs in testing: #986529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• mystic (- to 0.4.3-3)
  • Migration status for mystic (- to 0.4.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mystic/0.4.3-3: amd64: Pass, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mystic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• python-mastodon (2.0.0-2 to 2.0.1-1)
  • Migration status for python-mastodon (2.0.0-2 to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-mastodon/2.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mastodon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 15 days old (needed 5 days)
• requests (2.32.3+dfsg-4 to 2.32.3+dfsg-5)
  • Migration status for requests (2.32.3+dfsg-4 to 2.32.3+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for apprise/1.9.2-1: riscv64: Pass
    • autopkgtest for designate/1:19.0.0-4: riscv64: Pass
    • autopkgtest for graphite-web/1.1.10-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for heat/1:24.0.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for mistral/20.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for proxmoxer/2.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for pyfritzhome/0.6.14-1: riscv64: Pass
    • autopkgtest for python-authlib/1.5.1-1: riscv64: Pass
    • autopkgtest for python-tado/0.19.1-1: riscv64: Pass
    • autopkgtest for requests/2.32.3+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for stravalib/2.2-1: riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/requests.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• 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, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whitakers-words.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• dirb (2.22+dfsg-5 to 2.22+dfsg-6)
  • Migration status for dirb (2.22+dfsg-5 to 2.22+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dirb/2.22+dfsg-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dirb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• gnome-calls (47.0-2 to 48.0-1)
  • Migration status for gnome-calls (47.0-2 to 48.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Updating gnome-calls will fix bugs in testing: #1101387
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-calls.html
    • autopkgtest for gnome-calls/48.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• systraq (20201231-1 to 20201231-3)
  • Migration status for systraq (20201231-1 to 20201231-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/systraq.html
  • Additional info:
    • Updating systraq will fix bugs in testing: #1101052
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• ukui-power-manager (- to 4.0.0.2-1)
  • Migration status for ukui-power-manager (- to 4.0.0.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ukui-power-manager ukui-control-center (not considered)
    • Depends: ukui-power-manager ukui-control-center (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-power-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• ccache (4.10.2-1 to 4.11.2-1)
  • Migration status for ccache (4.10.2-1 to 4.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ccache/4.11.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• lptools (- to 0.3.0-2)
  • Migration status for lptools (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lptools would introduce bugs in testing: #1063447
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lptools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• toil (- to 8.0.0-4)
  • Migration status for toil (- to 8.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating toil would introduce bugs in testing: #1101085
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toil.html
    • autopkgtest for toil/8.0.0-4: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• axc (0.3.7-1.1 to 0.3.7-2)
  • Migration status for axc (0.3.7-1.1 to 0.3.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating axc would introduce bugs in testing: #1101090
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/axc.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• breezy-debian (2.8.79 to 2.8.80)
  • Migration status for breezy-debian (2.8.79 to 2.8.80): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breezy-debian.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 18 days old (needed 5 days)
• dcmtk (3.6.9-4 to 3.6.9-5)
  • Migration status for dcmtk (3.6.9-4 to 3.6.9-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for biosig/2.6.1-1: riscv64: No tests, superficial or marked flaky
    • autopkgtest for dcmtk/3.6.9-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for orthanc/1.12.6+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for orthanc-wsi/3.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dcmtk.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
    • 18 days old (needed 5 days)
• intel-compute-runtime (- to 25.05.32567.18-1)
  • Migration status for intel-compute-runtime (- to 25.05.32567.18-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.05.32567.18-1: amd64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 18 days old (needed 5 days)
• intel-graphics-compiler2 (- to 2.9.2-1)
  • Migration status for intel-graphics-compiler2 (- to 2.9.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): intel-graphics-compiler2 spirv-llvm-translator-14 (not considered)
    • Depends: intel-graphics-compiler2 spirv-llvm-translator-14 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • 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
    • Depends: intel-graphics-compiler2 llvm-toolchain-14 (not considered)
    • Depends: intel-graphics-compiler2 opencl-clang-14
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-graphics-compiler2.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 18 days old (needed 5 days)
• intel-vc-intrinsics (- to 0.22.1-1)
  • Migration status for intel-vc-intrinsics (- to 0.22.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• snac2 (2.73-1 to 2.74-1)
  • Migration status for snac2 (2.73-1 to 2.74-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for snac2/2.74-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snac2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• forgejo-api (- to 0.7.0-2)
  • Migration status for forgejo-api (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for forgejo-api/0.7.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forgejo-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• harlequin (- to 2.1.1-1)
  • Migration status for harlequin (- to 2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating harlequin would introduce bugs in testing: #1099499
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harlequin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• harlequin-odbc (0.3.0-1 to 0.3.1-1)
  • Migration status for harlequin-odbc (0.3.0-1 to 0.3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: harlequin-odbc harlequin (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harlequin-odbc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• 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
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/p/pynpoint.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• r-cran-cards (- to 0.5.1-1)
  • Migration status for r-cran-cards (- to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-cards/0.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cards.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• r-cran-spatstat.geom (3.2-9-2 to 3.3-6-1)
  • Migration status for r-cran-spatstat.geom (3.2-9-2 to 3.3-6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-seurat/5.2.1-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-spatstat.geom/3.3-6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating r-cran-spatstat.geom will fix bugs in testing: #1099924
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.geom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• r-cran-spatstat.random (3.2-3-1 to 3.3-3-1)
  • Migration status for r-cran-spatstat.random (3.2-3-1 to 3.3-3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-spatstat.random r-cran-spatstat.geom (not considered)
    • Depends: r-cran-spatstat.random r-cran-spatstat.geom (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating r-cran-spatstat.random will fix bugs in testing: #1099922
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.random.html
    • autopkgtest for r-cran-spatstat.random/3.3-3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• rsplib (3.4.4-1.1 to 3.5.1-1.1)
  • Migration status for rsplib (3.4.4-1.1 to 3.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rsplib would introduce bugs in testing: #1100891
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsplib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• urjtag (2021.03-2 to 2021.03-3)
  • Migration status for urjtag (2021.03-2 to 2021.03-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating urjtag would introduce bugs in testing: #1100873
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating urjtag will fix bugs in testing: #1100328
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urjtag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• pymupdf (- to 1.25.4+ds1-1)
  • Migration status for pymupdf (- to 1.25.4+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pymupdf would introduce bugs in testing: #1100748
    • autopkgtest for pymupdf/1.25.4+ds1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymupdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• djbdns (- to 1:1.05-20)
  • Migration status for djbdns (- to 1:1.05-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for djbdns/1:1.05-20: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djbdns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• orthanc-wsi (3.0+dfsg-1 to 3.1+dfsg-1)
  • Migration status for orthanc-wsi (3.0+dfsg-1 to 3.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orthanc-wsi/3.1+dfsg-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-wsi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• 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, #953053
    • autopkgtest for psychopy/2023.2.4+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psychopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• sch-rnd (1.0.7-1 to 1.0.8-2)
  • Migration status for sch-rnd (1.0.7-1 to 1.0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sch-rnd-core/armel has unsatisfiable dependency
    • sch-rnd-core/armhf has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sch-rnd.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 21 days old (needed 5 days)
• gabedit (- to 2.5.1+ds-2)
  • Migration status for gabedit (- to 2.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): gabedit gtkglext (not considered)
    • Depends: gabedit gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gabedit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
• gdis (- to 1.00-1)
  • Migration status for gdis (- to 1.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gdis gtkglext (not considered)
    • Depends: gdis gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdis.html
    • autopkgtest for gdis/1.00-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
• gittuf (- to 0.9.0-1)
  • Migration status for gittuf (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gittuf would introduce bugs in testing: #1101704
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gittuf.html
    • 22 days old (needed 5 days)
• hvcc (- to 0.13.3-1)
  • Migration status for hvcc (- to 0.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for hvcc/0.13.3-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hvcc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
• intel-compute-runtime-legacy (- to 24.35.30872.32-2)
  • Migration status for intel-compute-runtime-legacy (- to 24.35.30872.32-2): 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-legacy intel-graphics-compiler (not considered)
    • Depends: intel-compute-runtime-legacy intel-graphics-compiler (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-compute-runtime-legacy.html
    • autopkgtest for intel-compute-runtime-legacy/24.35.30872.32-2: amd64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 22 days old (needed 5 days)
• jakarta-standard-taglib (- to 3.0.2-2)
  • Migration status for jakarta-standard-taglib (- to 3.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • jakarta-standard-taglib unsatisfiable Build-Depends(-Arch) on amd64: libjakarta-jsp-api-java
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jakarta-standard-taglib.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 22 days old (needed 5 days)
• kitty (0.39.1-1 to 0.40.0-1)
  • Migration status for kitty (0.39.1-1 to 0.40.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kitty.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 22 days old (needed 5 days)
• mysql-connector-python (- to 9.2.0-1)
  • Migration status for mysql-connector-python (- to 9.2.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 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:
    • autopkgtest for psi4/1:1.3.2+dfsg-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psi4.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 22 days old (needed 5 days)
• python-aiohttp-security (- to 0.5.0-2)
  • Migration status for python-aiohttp-security (- to 0.5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-aiohttp-security aioredis (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiohttp-security.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
• 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 days old (needed 2 days)
• r-bioc-mofa2 (- to 1.16.0+ds-4)
  • Migration status for r-bioc-mofa2 (- to 1.16.0+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-mofa2/1.16.0+ds-4: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-mofa2.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 22 days old (needed 5 days)
• r-cran-performance (- to 0.13.0-2)
  • Migration status for r-cran-performance (- to 0.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-performance would introduce bugs in testing: #1071104
    • autopkgtest for r-cran-performance/0.13.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-performance.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
• r-cran-waveslim (1.8.4-1 to 1.8.5-1)
  • Migration status for r-cran-waveslim (1.8.4-1 to 1.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-waveslim would introduce bugs in testing: #1101591
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on amd64: r-cran-multitaper
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on arm64: r-cran-multitaper
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on armel: r-cran-multitaper
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on armhf: r-cran-multitaper
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on i386: r-cran-multitaper
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-multitaper
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-multitaper
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-multitaper
    • r-cran-waveslim unsatisfiable Build-Depends(-Arch) on s390x: r-cran-multitaper
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-waveslim.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 22 days old (needed 5 days)
• git (1:2.47.2-0.1 to 1:2.49.0-1)
  • Migration status for git (1:2.47.2-0.1 to 1:2.49.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating git would introduce bugs in testing: #1102106
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for magit/4.3.1-2: riscv64: Pass
    • autopkgtest for podman/5.4.1+ds1-3: riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 10 days)
• libfabric (1.17.0-3.1 to 2.0.0-4)
  • Migration status for libfabric (1.17.0-3.1 to 2.0.0-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfabric.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 23 days old (needed 5 days)
• libimage-exiftool-perl (13.10+dfsg-1 to 13.25+dfsg-1)
  • Migration status for libimage-exiftool-perl (13.10+dfsg-1 to 13.25+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libimage-exiftool-perl/13.25+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for mat2/0.13.5-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libimage-exiftool-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• linuxcnc (- to 1:2.9.4-1)
  • Migration status for linuxcnc (- to 1:2.9.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • linuxcnc-uspace/armel has unsatisfiable dependency
    • linuxcnc-uspace/ppc64el has unsatisfiable dependency
    • linuxcnc-uspace/riscv64 has unsatisfiable dependency
    • linuxcnc-uspace/s390x has unsatisfiable dependency
    • Updating linuxcnc would introduce bugs in testing: #1100882, #1101346
    • autopkgtest for linuxcnc/1:2.9.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linuxcnc.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 23 days old (needed 5 days)
• napari (- to 0.5.6-2)
  • Migration status for napari (- to 0.5.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for napari/0.5.6-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): napari napari-console (not considered)
    • Build-Depends(-Arch): napari napari-plugin-manager (not considered)
    • Build-Depends(-Arch): napari napari-svg
    • Depends: napari napari-console (not considered)
    • Depends: napari napari-svg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 23 days old (needed 5 days)
• napari-plugin-manager (- to 0.1.4-3)
  • Migration status for napari-plugin-manager (- to 0.1.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for napari-plugin-manager/0.1.4-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): napari-plugin-manager napari (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-plugin-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• php-jolicode-php-os-helper (- to 0.2.0-1)
  • Migration status for php-jolicode-php-os-helper (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-jolicode-php-os-helper would introduce bugs in testing: #1100631
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-jolicode-php-os-helper.html
    • autopkgtest for php-jolicode-php-os-helper/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• python-psutil (5.9.8-2 to 7.0.0-1)
  • Migration status for python-psutil (5.9.8-2 to 7.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-psutil would introduce bugs in testing: #1101865
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for python-psutil/7.0.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 ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-psutil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 23 days old (needed 5 days)
• napari-svg (- to 0.2.1-1)
  • Migration status for napari-svg (- to 0.2.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): napari-svg napari (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-svg.html
    • autopkgtest for napari-svg/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 24 days old (needed 2 days)
• openjdk-11 (- to 11.0.27~4ea-1)
  • Migration status for openjdk-11 (- to 11.0.27~4ea-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-11 would introduce bugs in testing: #1023237, #1071118
    • missing build on armel
    • missing build on armhf
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for openjdk-11/11.0.27~4ea-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 24 days old (needed 5 days)
• pacemaker (2.1.8-1 to 3.0.0-2)
  • Migration status for pacemaker (2.1.8-1 to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for crmsh/4.6.0-4: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for pacemaker/3.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pacemaker.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 24 days old (needed 5 days)
• r-cran-units (0.8-5+dfsg-1 to 0.8-7+dfsg-1)
  • Migration status for r-cran-units (0.8-5+dfsg-1 to 0.8-7+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-units/0.8-7+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: upload info for arch arm64 binaries not found
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-units.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• slurm-wlm (24.11.0-2 to 24.11.3-2)
  • Migration status for slurm-wlm (24.11.0-2 to 24.11.3-2): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: slurm-wlm slurm-wlm-contrib
  • Additional info:
    • Updating slurm-wlm will fix bugs in testing: #1099903
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slurm-wlm.html
    • autopkgtest for slurm-wlm/24.11.3-2: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• slurm-wlm-contrib (24.11.0-2 to 24.11.3-2)
  • Migration status for slurm-wlm-contrib (24.11.0-2 to 24.11.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: slurm-wlm-contrib slurm-wlm
  • Additional info:
    • Updating slurm-wlm-contrib will fix bugs in testing: #1099902
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 25 days old (needed 5 days)
• biglybt (3.7.0.0-1 to 3.8.0.0-2)
  • Migration status for biglybt (3.7.0.0-1 to 3.8.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: biglybt bouncycastle (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating biglybt will fix bugs in testing: #1102084
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biglybt.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 26 days old (needed 5 days)
• slic3r-prusa (- to 2.9.1+dfsg-1)
  • Migration status for slic3r-prusa (- to 2.9.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for slic3r-prusa/2.9.1+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r-prusa.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• sundials (7.1.1+dfsg1-8 to 7.1.1+dfsg1-10)
  • Migration status for sundials (7.1.1+dfsg1-8 to 7.1.1+dfsg1-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials petsc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sundials.html
    • autopkgtest for sundials/7.1.1+dfsg1-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 26 days old (needed 2 days)
• frr (10.2.1-6 to 10.3-1)
  • Migration status for frr (10.2.1-6 to 10.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 frr/10.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• gitlabracadabra (2.5.1 to 2.7.0)
  • Migration status for gitlabracadabra (2.5.1 to 2.7.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gitlabracadabra/2.7.0: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlabracadabra.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• harlequin-mysql (- to 1.1.0-3)
  • Migration status for harlequin-mysql (- to 1.1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: harlequin-mysql mysql-connector-python (not considered)
    • Invalidated by dependency
    • Depends: harlequin-mysql harlequin (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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• harlequin-postgres (1.2.0-1 to 1.2.0-2)
  • Migration status for harlequin-postgres (1.2.0-1 to 1.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: harlequin-postgres harlequin (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harlequin-postgres.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• petsc4py (3.22.3-1 to 3.22.4-1)
  • Migration status for petsc4py (3.22.3-1 to 3.22.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: petsc4py petsc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/petsc4py.html
    • autopkgtest for petsc4py/3.22.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• fonts-jetbrains-mono (2.304+ds-4 to 2.304+ds-5)
  • Migration status for fonts-jetbrains-mono (2.304+ds-4 to 2.304+ds-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): fonts-jetbrains-mono kotlin (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-jetbrains-mono.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• golang-github-apptainer-container-library-client (1.2.2-2 to 1.4.10-1)
  • Migration status for golang-github-apptainer-container-library-client (1.2.2-2 to 1.4.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-apptainer-container-library-client would introduce bugs in testing: #1101623
    • golang-github-apptainer-container-library-client unsatisfiable Build-Depends(-Arch) on amd64: golang-github-apptainer-sif-dev
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-apptainer-container-library-client.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 5 days)
• chuck (- to 1.5.5.0-1)
  • Migration status for chuck (- to 1.5.5.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chuck.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• litestar-htmx (- to 0.4.1-2)
  • Migration status for litestar-htmx (- to 0.4.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for litestar-htmx/0.4.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 29 days old (needed 5 days)
• lsp-plugins (1.2.16-1 to 1.2.21-1)
  • Migration status for lsp-plugins (1.2.16-1 to 1.2.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lsp-plugins/1.2.21-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsp-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 29 days old (needed 5 days)
• r-cran-broom.helpers (1.14.0-3 to 1.20.0-1)
  • Migration status for r-cran-broom.helpers (1.14.0-3 to 1.20.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-broom.helpers r-cran-cards (not considered)
    • Depends: r-cran-broom.helpers r-cran-cards (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-broom.helpers.html
    • autopkgtest for r-cran-broom.helpers/1.20.0-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• r-cran-fansi (1.0.5-1 to 1.0.6-1)
  • Migration status for r-cran-fansi (1.0.5-1 to 1.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-fansi/1.0.6-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fansi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• r-cran-sjplot (- to 2.8.17+dfsg-1)
  • Migration status for r-cran-sjplot (- to 2.8.17+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-sjplot r-cran-performance (not considered)
    • Depends: r-cran-sjplot r-cran-performance (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-sjplot r-cran-sjstats
    • Depends: r-cran-sjplot r-cran-sjstats
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sjplot.html
    • autopkgtest for r-cran-sjplot/2.8.17+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• rust-hurl (- to 6.0.0-1)
  • Migration status for rust-hurl (- to 6.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-hurl rust-libxml (not considered)
    • Depends: rust-hurl rust-libxml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-hurl rust-hurl-core
    • Depends: rust-hurl rust-hurl-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hurl.html
    • autopkgtest for rust-hurl/6.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• rust-hurl-core (- to 6.0.0-1)
  • Migration status for rust-hurl-core (- to 6.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-hurl-core rust-libxml (not considered)
    • Depends: rust-hurl-core rust-libxml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hurl-core.html
    • autopkgtest for rust-hurl-core/6.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• rust-zoxide (0.9.6-1 to 0.9.7-1)
  • Migration status for rust-zoxide (0.9.6-1 to 0.9.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-zoxide would introduce bugs in testing: #1095528
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zoxide.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• cl-asdf (2:3.3.7.2-1 to 2:3.3.7.3-1)
  • Migration status for cl-asdf (2:3.3.7.2-1 to 2:3.3.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by pvaneynd, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating cl-asdf will fix bugs in testing: #1102349
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-asdf.html
    • autopkgtest for cl-asdf/2:3.3.7.3-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), 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: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• cl-closer-mop (2:20241031.git875f4b7-1 to 2:20250303.git53221de-1)
  • Migration status for cl-closer-mop (2:20241031.git875f4b7-1 to 2:20250303.git53221de-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by pvaneynd, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating cl-closer-mop will fix bugs in testing: #1102348
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-closer-mop.html
    • autopkgtest for cl-closer-mop/2:20250303.git53221de-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), 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: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• cl-nibbles (20240607.gitc054c32-2 to 20250305.gitc1ecd02-1)
  • Migration status for cl-nibbles (20240607.gitc054c32-2 to 20250305.gitc1ecd02-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by pvaneynd, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating cl-nibbles will fix bugs in testing: #1102347
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-nibbles.html
    • autopkgtest for cl-nibbles/20250305.gitc1ecd02-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• python-daemon (3.1.2-1 to 3.1.2-2)
  • Migration status for python-daemon (3.1.2-1 to 3.1.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends-Indep: python-daemon changelog-chug (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-daemon.html
    • autopkgtest for python-daemon/3.1.2-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• rust-wl-nl80211 (- to 0.2.0-1)
  • Migration status for rust-wl-nl80211 (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-wl-nl80211/0.2.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-wl-nl80211.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• 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/armel has unsatisfiable dependency
    • librust-zerovec-dev/armhf has unsatisfiable dependency
    • librust-zerovec-dev/i386 has unsatisfiable dependency
    • librust-zerovec-dev/mips64el has unsatisfiable dependency
    • librust-zerovec-dev/ppc64el has unsatisfiable dependency
    • librust-zerovec-dev/riscv64 has unsatisfiable dependency
    • librust-zerovec-dev/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): rust-zerovec rust-zerofrom (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-zerovec.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• trivial-features (20230607.gitd249a62-1 to 20250129.git18a5cfa-1)
  • Migration status for trivial-features (20230607.gitd249a62-1 to 20250129.git18a5cfa-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by pvaneynd, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating trivial-features will fix bugs in testing: #1102346
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trivial-features.html
    • autopkgtest for trivial-features/20250129.git18a5cfa-1: amd64: Pass, arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Failed (not a regression), s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• oss4 (- to 4.2-build2020-4)
  • Migration status for oss4 (- to 4.2-build2020-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oss4 would introduce bugs in testing: #1064301, #796636
    • autopkgtest for oss4/4.2-build2020-4: amd64: No tests, superficial or marked flaky ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oss4.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• r-cran-survminer (0.4.9+dfsg-1 to 0.5.0+dfsg-1)
  • Migration status for r-cran-survminer (0.4.9+dfsg-1 to 0.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-survminer/0.5.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r-cran-survminer will fix bugs in testing: #1102345
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-survminer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 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/armel has unsatisfiable dependency
    • librust-yoke-dev/armhf has unsatisfiable dependency
    • librust-yoke-dev/i386 has unsatisfiable dependency
    • librust-yoke-dev/mips64el has unsatisfiable dependency
    • librust-yoke-dev/ppc64el has unsatisfiable dependency
    • librust-yoke-dev/riscv64 has unsatisfiable dependency
    • librust-yoke-dev/s390x has unsatisfiable dependency
    • Updating rust-yoke would introduce bugs in testing: #1073151
    • Build-Depends(-Arch): rust-yoke rust-zerofrom (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-yoke.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• r-cran-argparser (0.7.1-1 to 0.7.2-1)
  • Migration status for r-cran-argparser (0.7.1-1 to 0.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-argparser/0.7.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r-cran-argparser will fix bugs in testing: #1102189
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-argparser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• rust-sha256 (- to 1.6.0-1)
  • Migration status for rust-sha256 (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sha256/1.6.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha256.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• bouncycastle (1.77-1 to 1.80-2)
  • Migration status for bouncycastle (1.77-1 to 1.80-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bouncycastle would introduce bugs in testing: #1100227
  • Additional info:
    • Updating bouncycastle will fix bugs in testing: #1102110
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bouncycastle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• calamares-extensions (- to 3.3.12-1.1)
  • Migration status for calamares-extensions (- to 3.3.12-1.1): 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• tboot (- to 1.10.5-4.1)
  • Migration status for tboot (- to 1.10.5-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tboot/1.10.5-4.1: amd64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tboot.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 35 days old (needed 5 days)
• python-django-timescaledb (- to 0.2.13-4)
  • Migration status for python-django-timescaledb (- to 0.2.13-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-django-timescaledb/0.2.13-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-timescaledb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 36 days old (needed 5 days)
• r-cran-bit64 (4.0.5-1 to 4.6.0-1-1)
  • Migration status for r-cran-bit64 (4.0.5-1 to 4.6.0-1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-bit64/4.6.0-1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r-cran-bit64 will fix bugs in testing: #1102109
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bit64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 36 days old (needed 5 days)
• rust-xshell-macros (0.2.5-1 to 0.3.0~pre.2-1)
  • Migration status for rust-xshell-macros (0.2.5-1 to 0.3.0~pre.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-xshell-macros would introduce bugs in testing: #1099527
    • autopkgtest for rust-xshell-macros/0.3.0~pre.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating rust-xshell-macros will fix bugs in testing: #1101870
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xshell-macros.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• mysql-workbench (- to 8.0.41+dfsg-1)
  • Migration status for mysql-workbench (- to 8.0.41+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-workbench would introduce bugs in testing: #1000093, #1084634
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Depends: mysql-workbench mysql-connector-python (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-workbench.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 38 days old (needed 5 days)
• ntpsec (1.2.3+dfsg1-3 to 1.2.3+dfsg1-4)
  • Migration status for ntpsec (1.2.3+dfsg1-3 to 1.2.3+dfsg1-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating ntpsec will fix bugs in testing: #1101872
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntpsec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 38 days old (needed 5 days)
• pocl (6.0-4 to 6.0-5)
  • Migration status for pocl (6.0-4 to 6.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pocl/6.0-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for pyopencl/2024.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻)
    • Not built on buildd: arch amd64 binaries uploaded by debian@abeckmann.de
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating pocl will fix bugs in testing: #1097326, #1101871
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pocl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 38 days old (needed 5 days)
• debmutate (0.71 to 0.72)
  • Migration status for debmutate (0.71 to 0.72): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debmutate/0.72: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating debmutate will fix bugs in testing: #1101771
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debmutate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 39 days old (needed 5 days)
• janus (- to 1.1.2-1.2)
  • Migration status for janus (- to 1.1.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for janus/1.1.2-1.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/janus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 39 days old (needed 5 days)
• 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
    • singularity-container/mips64el has unsatisfiable Built-Using on golang-1.21 1.21.6-1
    • singularity-container/mips64el has unsatisfiable Built-Using on golang-github-container-orchestrated-devices-container-device-interface 0.6.1-2
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singularity-container.html
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 39 days old (needed 5 days)
• r-cran-bslib (0.8.0+dfsg-1 to 0.9.0+dfsg-1)
  • Migration status for r-cran-bslib (0.8.0+dfsg-1 to 0.9.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-bslib/0.9.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r-cran-bslib will fix bugs in testing: #1101679
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bslib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 40 days old (needed 5 days)
• rust-apt-swarm (- to 0.5.0-1)
  • Migration status for rust-apt-swarm (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-apt-swarm-dev/amd64 has unsatisfiable dependency
    • librust-apt-swarm-dev/arm64 has unsatisfiable dependency
    • librust-apt-swarm-dev/armel has unsatisfiable dependency
    • librust-apt-swarm-dev/armhf has unsatisfiable dependency
    • librust-apt-swarm-dev/i386 has unsatisfiable dependency
    • librust-apt-swarm-dev/mips64el has unsatisfiable dependency
    • librust-apt-swarm-dev/ppc64el has unsatisfiable dependency
    • librust-apt-swarm-dev/riscv64 has unsatisfiable dependency
    • librust-apt-swarm-dev/s390x has unsatisfiable dependency
    • Updating rust-apt-swarm would introduce bugs in testing: #1101874
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on amd64: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on arm64: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on armel: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on armhf: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on i386: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on mips64el: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on ppc64el: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on riscv64: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
    • rust-apt-swarm unsatisfiable Build-Depends(-Arch) on s390x: librust-sequoia-openpgp-1+default-dev (>= 1.21-~~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-apt-swarm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 40 days old (needed 5 days)
• rust-aya (- to 0.13.1-2)
  • Migration status for rust-aya (- to 0.13.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-aya/0.13.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-aya.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 40 days old (needed 5 days)
• fossil (1:2.24-6 to 1:2.25-1)
  • Migration status for fossil (1:2.24-6 to 1:2.25-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 fossil/1:2.25-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating fossil will fix bugs in testing: #1101646
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fossil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 41 days old (needed 5 days)
• r-cran-spatstat (3.0-8-1 to 3.3-1-1)
  • Migration status for r-cran-spatstat (3.0-8-1 to 3.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): r-cran-spatstat r-cran-spatstat.geom (not considered)
    • Depends: r-cran-spatstat r-cran-spatstat.geom (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-spatstat r-cran-spatstat.explore
    • Build-Depends(-Arch): r-cran-spatstat r-cran-spatstat.linnet
    • Build-Depends(-Arch): r-cran-spatstat r-cran-spatstat.model
    • Build-Depends(-Arch): r-cran-spatstat r-cran-spatstat.random
    • Depends: r-cran-spatstat r-cran-spatstat.explore
    • Depends: r-cran-spatstat r-cran-spatstat.linnet
    • Depends: r-cran-spatstat r-cran-spatstat.model
    • Depends: r-cran-spatstat r-cran-spatstat.random
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.html
    • autopkgtest for r-cran-spatstat/3.3-1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 42 days old (needed 2 days)
• r-cran-spatstat.linnet (3.1-5-1 to 3.2-5-1)
  • Migration status for r-cran-spatstat.linnet (3.1-5-1 to 3.2-5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-spatstat.linnet r-cran-spatstat.geom (not considered)
    • Depends: r-cran-spatstat.linnet r-cran-spatstat.geom (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-spatstat.linnet r-cran-spatstat.explore
    • Build-Depends(-Arch): r-cran-spatstat.linnet r-cran-spatstat.model
    • Build-Depends(-Arch): r-cran-spatstat.linnet r-cran-spatstat.random
    • Depends: r-cran-spatstat.linnet r-cran-spatstat.explore
    • Depends: r-cran-spatstat.linnet r-cran-spatstat.model
    • Depends: r-cran-spatstat.linnet r-cran-spatstat.random
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.linnet.html
    • autopkgtest for r-cran-spatstat.linnet/3.2-5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 42 days old (needed 2 days)
• libkryo2-java (- to 2.20-9)
  • Migration status for libkryo2-java (- to 2.20-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkryo2-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• urdfdom-headers (1.0.5-3 to 1.1.2-1)
  • Migration status for urdfdom-headers (1.0.5-3 to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for urdfdom/4.0.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating urdfdom-headers will fix bugs in testing: #1101441
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urdfdom-headers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 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: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: lava djangorestframework-filters (not considered)
    • Depends: lava lavacli
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lava.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• java-data-clojure (- to 1.2.107-1)
  • Migration status for java-data-clojure (- to 1.2.107-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by lavamind, a new source-only upload is needed to allow migration
    • autopkgtest for java-data-clojure/1.2.107-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/java-data-clojure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 45 days old (needed 5 days)
• jnettop (- to 0.13.0-3)
  • Migration status for jnettop (- to 0.13.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jnettop would introduce bugs in testing: #1075103
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jnettop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 45 days old (needed 5 days)
• mysql-8.0 (- to 8.0.41-3)
  • Migration status for mysql-8.0 (- to 8.0.41-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-8.0 would introduce bugs in testing: #1078629
    • autopkgtest for mediawiki-extension-codemirror/6.0.0~git20250325.399da27-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for mediawiki-extension-youtube/1.9.4~git20241126.01673ce-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for mediawiki-skin-greystuff/1.2.5~git20250311.35884cb-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for mysql-8.0/8.0.41-3: amd64: Regression or new test ♻, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not touching package due to block request by pochu (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-8.0.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • 45 days old (needed 5 days)
• alicevision (- to 3.2.0+repack-2)
  • Migration status for alicevision (- to 3.2.0+repack-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): alicevision geogram (not considered)
    • Depends: alicevision geogram (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 46 days old (needed 5 days)
• json-tricks (3.11.0-4 to 3.17.3-1)
  • Migration status for json-tricks (3.11.0-4 to 3.17.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for json-tricks/3.17.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating json-tricks will fix bugs in testing: #1101381
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/json-tricks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 46 days old (needed 5 days)
• g10k (0.9.9-1 to 0.9.10-1)
  • Migration status for g10k (0.9.9-1 to 0.9.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating g10k would introduce bugs in testing: #1095672
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for g10k/0.9.10-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating g10k will fix bugs in testing: #1100514
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/g10k.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 47 days old (needed 5 days)
• power-profiles-daemon (0.23-1 to 0.30-1)
  • Migration status for power-profiles-daemon (0.23-1 to 0.30-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating power-profiles-daemon would introduce bugs in testing: #1098432
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating power-profiles-daemon will fix bugs in testing: #1100965
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/power-profiles-daemon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• python-discord (- to 2.5.0+dfsg-1)
  • Migration status for python-discord (- to 2.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-discord would introduce bugs in testing: #1057608
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-discord.html
    • autopkgtest for python-discord/2.5.0+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• 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:
    • autopkgtest for python-gassist-text/0.0.11-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• tomwer (- to 1.4.8-1)
  • Migration status for tomwer (- to 1.4.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): tomwer python-nxtomomill (not considered)
    • Depends: tomwer python-nxtomomill (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomwer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• tworld (1.3.2-5 to 2.3.0-1)
  • Migration status for tworld (1.3.2-5 to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tworld would introduce bugs in testing: #1098466
  • Additional info:
    • Updating tworld will fix bugs in testing: #1101054
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tworld.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• x2gobroker (- to 0.0.4.3-4.2)
  • Migration status for x2gobroker (- to 0.0.4.3-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • x2gobroker/amd64 has unsatisfiable dependency
    • x2gobroker/arm64 has unsatisfiable dependency
    • Updating x2gobroker would introduce bugs in testing: #1087443
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/x2gobroker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• bcbio (- to 1.2.9-3)
  • Migration status for bcbio (- to 1.2.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bcbio would introduce bugs in testing: #928076
    • Build-Depends(-Arch): bcbio mosdepth
    • Build-Depends(-Arch): bcbio r-bioc-degreport
    • 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-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • 49 days old (needed 5 days)
• pynn (- to 0.10.1-4)
  • Migration status for pynn (- to 0.10.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pynn would introduce bugs in testing: #1071337
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynn.html
    • autopkgtest for pynn/0.10.1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 49 days old (needed 5 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 armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for circlator/1.5.6-13: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 50 days old (needed 2 days)
• libbio-procedural-perl (- to 1.7.4-4)
  • Migration status for libbio-procedural-perl (- to 1.7.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libbio-procedural-perl would introduce bugs in testing: #1098343
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbio-procedural-perl.html
    • autopkgtest for libbio-procedural-perl/1.7.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 50 days old (needed 2 days)
• plakativ (- to 0.5.3-1)
  • Migration status for plakativ (- to 0.5.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): plakativ pymupdf (not considered)
    • Depends: plakativ pymupdf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plakativ.html
    • autopkgtest for plakativ/0.5.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 50 days old (needed 2 days)
• node-svgdotjs-svg.draggable.js (- to 3.0.6-1)
  • Migration status for node-svgdotjs-svg.draggable.js (- to 3.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-svgdotjs-svg.draggable.js/3.0.6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-svgdotjs-svg.draggable.js.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 51 days old (needed 5 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 51 days old (needed 5 days)
• spades (3.15.5+dfsg-8 to 4.0.0+dfsg1-2)
  • Migration status for spades (3.15.5+dfsg-8 to 4.0.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for shovill/1.1.0-9: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for spades/4.0.0+dfsg1-2: amd64: Pass
    • autopkgtest for unicycler/0.5.1+dfsg-3: amd64: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating spades will fix bugs in testing: #1100877
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spades.html
    • Reproducible on amd64 - info ♻
    • 51 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 52 days old (needed 5 days)
• rust-keyring (- to 3.2.1-3)
  • Migration status for rust-keyring (- to 3.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-keyring/3.2.1-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: rust-keyring rust-dbus-secret-service (not considered)
    • Depends: rust-keyring rust-secret-service (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 days old (needed 5 days)
• rust-secret-service (- to 4.0.0-4)
  • Migration status for rust-secret-service (- to 4.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-secret-service would introduce bugs in testing: #1083230, #1102276
    • autopkgtest for rust-secret-service/4.0.0-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-secret-service.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• openjdk-8 (- to 8u442-ga-2)
  • Migration status for openjdk-8 (- to 8u442-ga-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-8 would introduce bugs in testing: #1095932, #989736
  • 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 openjdk-8: amd64: Test in progress (will not be considered a regression), arm64: Test in progress (will not be considered a regression), armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression), s390x: Test in progress (will not be considered a regression)
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 55 days old (needed 5 days)
• forgejo-cli (- to 0.2.0-2)
  • Migration status for forgejo-cli (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-git2-0.19+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on arm64: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on arm64: librust-git2-0.19+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on armel: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on armel: librust-git2-0.19+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on armhf: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on armhf: librust-git2-0.19+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on i386: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on i386: librust-git2-0.19+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on mips64el: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on mips64el: librust-git2-0.19+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on ppc64el: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on ppc64el: librust-git2-0.19+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on riscv64: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on riscv64: librust-git2-0.19+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on s390x: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on s390x: librust-git2-0.19+default-dev
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): forgejo-cli rust-sha256 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forgejo-cli.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 56 days old (needed 5 days)
• python-datapoint (- to 0.9.9-2)
  • Migration status for python-datapoint (- to 0.9.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-datapoint would introduce bugs in testing: #1095915
    • Build-Depends-Indep: python-datapoint appdirs (not considered)
    • Depends: python-datapoint appdirs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-datapoint.html
    • autopkgtest for python-datapoint/0.9.9-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 56 days old (needed 2 days)
• jaraco.stream (- to 3.0.4-1)
  • Migration status for jaraco.stream (- to 3.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for jaraco.stream/3.0.4-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by ben@benfinney.id.au, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jaraco.stream.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 days)
• rust-litemap (- to 0.7.4-1)
  • Migration status for rust-litemap (- to 0.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-litemap-dev/amd64 has unsatisfiable dependency
    • librust-litemap-dev/arm64 has unsatisfiable dependency
    • librust-litemap-dev/armel has unsatisfiable dependency
    • librust-litemap-dev/armhf has unsatisfiable dependency
    • librust-litemap-dev/i386 has unsatisfiable dependency
    • librust-litemap-dev/mips64el has unsatisfiable dependency
    • librust-litemap-dev/ppc64el has unsatisfiable dependency
    • librust-litemap-dev/riscv64 has unsatisfiable dependency
    • librust-litemap-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-litemap.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 days)
• rust-ryu-js (- to 1.0.1-1)
  • Migration status for rust-ryu-js (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ryu-js/1.0.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ryu-js.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 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:
    • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 57 days old (needed 5 days)
• wlroots-0.17 (- to 0.17.4-2)
  • Migration status for wlroots-0.17 (- to 0.17.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wlroots-0.17 would introduce bugs in testing: #1095751
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wlroots-0.17.html
    • autopkgtest for wlroots-0.17/0.17.4-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 days)
• rust-launchpadlib (- to 0.2.0-3)
  • Migration status for rust-launchpadlib (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-launchpadlib/0.2.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Depends: rust-launchpadlib rust-keyring (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-launchpadlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 58 days old (needed 5 days)
• rust-safe-arch (0.7.2-2 to 0.7.4-2)
  • Migration status for rust-safe-arch (0.7.2-2 to 0.7.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-safe-arch would introduce bugs in testing: #1092391
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating rust-safe-arch will fix bugs in testing: #1093789
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-safe-arch.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 59 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bdebstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 60 days old (needed 5 days)
• check-all-the-things (- to 2025.02.06)
  • Migration status for check-all-the-things (- to 2025.02.06): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating check-all-the-things would introduce bugs in testing: #862378
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-all-the-things.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 60 days old (needed 5 days)
• libjpeg9 (- to 1:9f-2)
  • Migration status for libjpeg9 (- to 1:9f-2): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 60 days old (needed 5 days)
• libstdc++-riscv64-unknown-elf (- to 4)
  • Migration status for libstdc++-riscv64-unknown-elf (- to 4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libs/libstdc++-riscv64-unknown-elf.html
  • Additional info:
    • autopkgtest for libstdc++-riscv64-unknown-elf/4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 60 days old (needed 2 days)
• pyfftw (- to 0.15.0-1)
  • Migration status for pyfftw (- to 0.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pyfftw/0.15.0-1: amd64: Pass, arm64: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfftw.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 60 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vpb-driver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 61 days old (needed 5 days)
• python-aioraven (- to 0.7.0-1)
  • Migration status for python-aioraven (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-aioraven/amd64 has unsatisfiable dependency
    • python3-aioraven/arm64 has unsatisfiable dependency
    • python-aioraven unsatisfiable Build-Depends-Indep on amd64: python3-iso4217
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-aioraven.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 62 days old (needed 5 days)
• python3.12 (- to 3.12.9-1)
  • Migration status for python3.12 (- to 3.12.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3.12-full/amd64 has unsatisfiable dependency
    • python3.12-full/arm64 has unsatisfiable dependency
    • python3.12-full/armel has unsatisfiable dependency
    • python3.12-full/armhf has unsatisfiable dependency
    • python3.12-full/i386 has unsatisfiable dependency
    • python3.12-full/mips64el has unsatisfiable dependency
    • python3.12-full/ppc64el has unsatisfiable dependency
    • python3.12-full/riscv64 has unsatisfiable dependency
    • python3.12-full/s390x has unsatisfiable dependency
    • Updating python3.12 would introduce bugs in testing: #1099668
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3.12.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• r-cran-sparr (2.3-10-1 to 2.3-15-1)
  • Migration status for r-cran-sparr (2.3-10-1 to 2.3-15-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating r-cran-sparr will fix bugs in testing: #1099929
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sparr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• scrcpy (- to 1.25-1.1)
  • Migration status for scrcpy (- to 1.25-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for scrcpy/1.25-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends-Indep: scrcpy android-framework-23 (not considered)
    • Build-Depends-Indep: scrcpy android-platform-dalvik
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrcpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• moarvm (2024.09+dfsg-3 to 2024.09+dfsg-4)
  • Migration status for moarvm (2024.09+dfsg-3 to 2024.09+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • removing moarvm/2024.09+dfsg-3/arm64 from testing makes nqp/2024.09+dfsg-2.1/arm64 uninstallable
    • removing moarvm/2024.09+dfsg-3/arm64 from testing makes nqp-data/2024.09+dfsg-2.1/arm64 uninstallable
    • removing moarvm/2024.09+dfsg-3/arm64 from testing makes rakudo/2024.09-2/arm64 uninstallable
    • removing moarvm/2024.09+dfsg-3/armel from testing makes nqp/2024.09+dfsg-2.1/armel uninstallable
    • removing moarvm/2024.09+dfsg-3/armel from testing makes rakudo/2024.09-2/armel uninstallable
    • removing moarvm/2024.09+dfsg-3/armhf from testing makes nqp/2024.09+dfsg-2.1/armhf uninstallable
    • removing moarvm/2024.09+dfsg-3/armhf from testing makes rakudo/2024.09-2/armhf uninstallable
  • Additional info:
    • Updating moarvm will fix bugs in testing: #1099928
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moarvm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 63 days old (needed 5 days)
• r-cran-testthat (3.2.1.1-1 to 3.2.3-1)
  • Migration status for r-cran-testthat (3.2.1.1-1 to 3.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-dharma/0.4.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for r-cran-hdf5r/1.3.12+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • autopkgtest for r-cran-s2/1.1.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for r-cran-sparsevctrs/0.2.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-testthat/3.2.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating r-cran-testthat will fix bugs in testing: #1099927
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-testthat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 64 days old (needed 5 days)
• r-cran-vegan (2.6-8+dfsg-1 to 2.6-10+dfsg-1)
  • Migration status for r-cran-vegan (2.6-8+dfsg-1 to 2.6-10+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-vegan/2.6-10+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r-cran-vegan will fix bugs in testing: #1099926
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vegan.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 64 days old (needed 5 days)
• virtualbox (- to 7.0.20-dfsg-1.2)
  • Migration status for virtualbox (- to 7.0.20-dfsg-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualbox would introduce bugs in testing: #1080878, #1085440, #1093879, #1098998, #1101182, #794466
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for virtualbox/7.0.20-dfsg-1.2: amd64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 65 days old (needed 5 days)
• dante (- to 1.4.3+dfsg-3)
  • Migration status for dante (- to 1.4.3+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dante would introduce bugs in testing: #1067709
    • autopkgtest for dante/1.4.3+dfsg-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dante.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 66 days old (needed 5 days)
• ariba (- to 2.14.7+ds-7)
  • Migration status for ariba (- to 2.14.7+ds-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ariba would introduce bugs in testing: #1098530
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ariba.html
    • autopkgtest for ariba/2.14.7+ds-7: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 67 days old (needed 2 days)
• r-cran-effectsize (- to 1.0.0+dfsg-1)
  • Migration status for r-cran-effectsize (- to 1.0.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-effectsize/1.0.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): r-cran-effectsize r-cran-performance (not considered)
    • Depends: r-cran-effectsize r-cran-performance (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-effectsize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 67 days old (needed 5 days)
• r-cran-spatstat.explore (3.2-7-1 to 3.3-4-1)
  • Migration status for r-cran-spatstat.explore (3.2-7-1 to 3.3-4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-spatstat.explore r-cran-spatstat.geom (not considered)
    • Depends: r-cran-spatstat.explore r-cran-spatstat.geom (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-spatstat.explore r-cran-spatstat.random
    • Depends: r-cran-spatstat.explore r-cran-spatstat.random
  • Additional info:
    • Updating r-cran-spatstat.explore will fix bugs in testing: #1099925
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.explore.html
    • autopkgtest for r-cran-spatstat.explore/3.3-4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 67 days old (needed 2 days)
• r-cran-spatstat.model (3.2-11-1 to 3.3-4-1)
  • Migration status for r-cran-spatstat.model (3.2-11-1 to 3.3-4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-spatstat.model r-cran-spatstat.geom (not considered)
    • Depends: r-cran-spatstat.model r-cran-spatstat.geom (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-spatstat.model r-cran-spatstat.explore
    • Build-Depends(-Arch): r-cran-spatstat.model r-cran-spatstat.random
    • Depends: r-cran-spatstat.model r-cran-spatstat.explore
    • Depends: r-cran-spatstat.model r-cran-spatstat.random
  • Additional info:
    • Updating r-cran-spatstat.model will fix bugs in testing: #1099923
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.model.html
    • autopkgtest for r-cran-spatstat.model/3.3-4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 67 days old (needed 2 days)
• 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 68 days old (needed 5 days)
• notcurses (- to 3.0.13+dfsg-2)
  • Migration status for notcurses (- to 3.0.13+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating notcurses would introduce bugs in testing: #1001661, #1015747
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notcurses.html
    • autopkgtest for notcurses/3.0.13+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 68 days old (needed 2 days)
• python-molotov (- to 2.7-2)
  • Migration status for python-molotov (- to 2.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-molotov/2.7-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-molotov.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 68 days old (needed 5 days)
• gocryptfs (2.4.0-1 to 2.5.1-1)
  • Migration status for gocryptfs (2.4.0-1 to 2.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gocryptfs would introduce bugs in testing: #1097131
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for gocryptfs/2.5.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating gocryptfs will fix bugs in testing: #1099900
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gocryptfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 69 days old (needed 5 days)
• r-cran-bios2cor (- to 2.2.2-1)
  • Migration status for r-cran-bios2cor (- to 2.2.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-bios2cor r-cran-bigmemory (not considered)
    • Depends: r-cran-bios2cor r-cran-bigmemory (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bios2cor.html
    • autopkgtest for r-cran-bios2cor/2.2.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 69 days old (needed 2 days)
• r-cran-patrick (- to 0.3.0-1)
  • Migration status for r-cran-patrick (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-patrick/0.3.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-patrick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 69 days old (needed 5 days)
• ruby-memory-profiler (- to 1.1.0-2)
  • Migration status for ruby-memory-profiler (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-memory-profiler would introduce bugs in testing: #1094048
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-memory-profiler.html
    • autopkgtest for ruby-memory-profiler/1.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 69 days old (needed 2 days)
• php-zstd (- to 0.14.0-1)
  • Migration status for php-zstd (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ondrej, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by ondrej
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-zstd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 70 days old (needed 5 days)
• rainbows (- to 5.2.1-2)
  • Migration status for rainbows (- to 5.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rainbows would introduce bugs in testing: #1094473
    • autopkgtest for rainbows/5.2.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Impossible Depends: rainbows -> ruby-rack/2.2.13-1~deb12u1/amd64
    • Impossible Depends: rainbows -> ruby-rack/2.2.13-1~deb12u1/arm64
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rainbows.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 70 days old (needed 5 days)
• golang-github-awslabs-soci-snapshotter (- to 0.4.1-4)
  • Migration status for golang-github-awslabs-soci-snapshotter (- to 0.4.1-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for golang-github-awslabs-soci-snapshotter/0.4.1-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-awslabs-soci-snapshotter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 71 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-340xx (- to 340.108-24)
  • Migration status for nvidia-graphics-drivers-legacy-340xx (- to 340.108-24): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-340xx would introduce bugs in testing: #1004848, #1011141, #1016615, #1025280, #1033775, #1039679, #1055137, #1064984, #1072793, #1085969, #1093909, #973599, #979671, #987217, #991352
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-legacy-340xx/340.108-24: amd64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 72 days old (needed 5 days)
• xperia-flashtool (- to 0.9.34+ds-2)
  • Migration status for xperia-flashtool (- to 0.9.34+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xperia-flashtool jarchivelib (not considered)
    • Depends: xperia-flashtool jarchivelib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xperia-flashtool.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 72 days old (needed 5 days)
• r-cran-dendextend (- to 1.19.0+dfsg-1)
  • Migration status for r-cran-dendextend (- to 1.19.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-dendextend/1.19.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dendextend.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• rust-pdb2 (- to 0.9.1-1)
  • Migration status for rust-pdb2 (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-pdb2/0.9.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pdb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• rust-proc-macro2-diagnostics (- to 0.10.1-1)
  • Migration status for rust-proc-macro2-diagnostics (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-proc-macro2-diagnostics/0.10.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-macro2-diagnostics.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• libgovirt (- to 0.3.9-4)
  • Migration status for libgovirt (- to 0.3.9-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgovirt would introduce bugs in testing: #1030904
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgovirt.html
    • 76 days old (needed 5 days)
• danmaq (- to 0.2.3.2-3)
  • Migration status for danmaq (- to 0.2.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating danmaq would introduce bugs in testing: #1091543
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/danmaq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 77 days old (needed 5 days)
• libpsml (- to 2.0.1-2)
  • Migration status for libpsml (- to 2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpsml would introduce bugs in testing: #1071043
    • libpsml unsatisfiable Build-Depends(-Arch) on amd64: libxmlf90-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libp/libpsml.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 78 days old (needed 5 days)
• mu-editor (- to 1.2.0+dfsg-2)
  • Migration status for mu-editor (- to 1.2.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mu-editor python-uflash (not considered)
    • Depends: mu-editor python-uflash (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mu-editor.html
    • autopkgtest for mu-editor/1.2.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 78 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/armel has unsatisfiable dependency
    • watchman/armhf has unsatisfiable dependency
    • watchman/i386 has unsatisfiable dependency
    • watchman/mips64el has unsatisfiable dependency
    • watchman/ppc64el has unsatisfiable dependency
    • watchman/riscv64 has unsatisfiable dependency
    • Updating watchman would introduce bugs in testing: #999930
    • watchman unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watchman.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 78 days old (needed 5 days)
• rust-symphonia-format-riff (- to 0.5.4-1)
  • Migration status for rust-symphonia-format-riff (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-symphonia-format-riff-dev/amd64 has unsatisfiable dependency
    • rust-symphonia-format-riff unsatisfiable Build-Depends(-Arch) on amd64: librust-symphonia-core-0.5+default-dev (>= 0.5.4-~~)
    • rust-symphonia-format-riff unsatisfiable Build-Depends(-Arch) on amd64: librust-symphonia-metadata-0.5+default-dev (>= 0.5.4-~~)
    • Not built on buildd: arch amd64 binaries uploaded by alexander.kjall@gmail.com
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-symphonia-format-riff.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 79 days old (needed 5 days)
• bfh-metapackages (- to 20211009-32)
  • Migration status for bfh-metapackages (- to 20211009-32): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bfh-container-server/amd64 has unsatisfiable dependency
    • bfh-container-server/arm64 has unsatisfiable dependency
    • bfh-base-system/armel has unsatisfiable dependency
    • bfh-base-system/armhf has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bfh-metapackages.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 82 days old (needed 5 days)
• progress-linux-metapackages (- to 20221002-21)
  • Migration status for progress-linux-metapackages (- to 20221002-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • progress-linux-container-server/amd64 has unsatisfiable dependency
    • progress-linux-container-server/arm64 has unsatisfiable dependency
    • progress-linux-base-system/armel has unsatisfiable dependency
    • progress-linux-base-system/armhf has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/progress-linux-metapackages.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 82 days old (needed 5 days)
• rally-openstack (- to 3.0.0-3)
  • Migration status for rally-openstack (- to 3.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-rally-openstack/amd64 has unsatisfiable dependency
    • python3-rally-openstack/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rally-openstack.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 82 days old (needed 5 days)
• geophar (- to 18.10+dfsg1-6)
  • Migration status for geophar (- to 18.10+dfsg1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geophar would introduce bugs in testing: #1078365
    • autopkgtest for geophar/18.10+dfsg1-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geophar.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 83 days old (needed 5 days)
• amgcl (- to 1.4.4-1)
  • Migration status for amgcl (- to 1.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • amgcl unsatisfiable Build-Depends(-Arch) on i386: libopenmpi-dev
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): amgcl parmetis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 84 days old (needed 5 days)
• geogram (- to 1.9.2-1)
  • Migration status for geogram (- to 1.9.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): geogram amgcl (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 84 days old (needed 5 days)
• r-bioc-degnorm (- to 1.16.0+ds-2)
  • Migration status for r-bioc-degnorm (- to 1.16.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): r-bioc-degnorm r-cran-heatmaply (not considered)
    • Depends: r-bioc-degnorm r-cran-heatmaply (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-degnorm.html
    • autopkgtest for r-bioc-degnorm/1.16.0+ds-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 84 days old (needed 2 days)
• r-bioc-demixt (- to 1.22.0-2)
  • Migration status for r-bioc-demixt (- to 1.22.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-demixt r-cran-dendextend (not considered)
    • Depends: r-bioc-demixt r-cran-dendextend (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-demixt.html
    • autopkgtest for r-bioc-demixt/1.22.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 84 days old (needed 2 days)
• ruby3.1 (- to 3.1.2-8.5)
  • Migration status for ruby3.1 (- to 3.1.2-8.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby3.1 would introduce bugs in testing: #1020580, #1055352, #1069966, #1078642
    • autopkgtest for ruby3.1/3.1.2-8.5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby3.1.html
    • 84 days old (needed 5 days)
• r-bioc-degreport (- to 1.42.0+dfsg-2)
  • Migration status for r-bioc-degreport (- to 1.42.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-degreport r-cran-dendextend (not considered)
    • Depends: r-bioc-degreport r-cran-dendextend (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-degreport.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for r-bioc-degreport/1.42.0+dfsg-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 85 days old (needed 2 days)
• django-pipeline (- to 4.0.0-3)
  • Migration status for django-pipeline (- to 4.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for django-pipeline/4.0.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-pipeline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 86 days old (needed 5 days)
• rust-opendal (- to 0.51.0-1)
  • Migration status for rust-opendal (- to 0.51.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-opendal-dev/amd64 has unsatisfiable dependency
    • librust-opendal-dev/arm64 has unsatisfiable dependency
    • librust-opendal-dev/armhf has unsatisfiable dependency
    • librust-opendal-dev/i386 has unsatisfiable dependency
    • librust-opendal-dev/mips64el has unsatisfiable dependency
    • librust-opendal-dev/ppc64el has unsatisfiable dependency
    • librust-opendal-dev/riscv64 has unsatisfiable dependency
    • librust-opendal-dev/s390x has unsatisfiable dependency
    • Updating rust-opendal would introduce bugs in testing: #1069715
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-opendal.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 87 days old (needed 5 days)
• simplesamlphp (- to 1.19.7-1+deb12u1)
  • Migration status for simplesamlphp (- to 1.19.7-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simplesamlphp would introduce bugs in testing: #1088816, #1100595
    • Not built on buildd: arch all binaries uploaded by thijs, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplesamlphp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 87 days old (needed 5 days)
• mailsync (- to 5.2.7-3.3)
  • Migration status for mailsync (- to 5.2.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): mailsync uw-imap (not considered)
    • Depends: mailsync uw-imap (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailsync.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 89 days old (needed 5 days)
• qtwebkit-opensource-src (- to 5.212.0~alpha4-42)
  • Migration status for qtwebkit-opensource-src (- to 5.212.0~alpha4-42): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qtwebkit-opensource-src would introduce bugs in testing: #1069574
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtwebkit-opensource-src.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 89 days old (needed 5 days)
• routine-update (- to 0.2.3)
  • Migration status for routine-update (- to 0.2.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: routine-update lintian-brush (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/routine-update.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 89 days old (needed 5 days)
• rust-utmp-classic (- to 0.1.6-1)
  • Migration status for rust-utmp-classic (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-utmp-classic/0.1.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-utmp-classic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 89 days old (needed 5 days)
• 389-ds-base (- to 3.1.1+dfsg1-3)
  • Migration status for 389-ds-base (- to 3.1.1+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating 389-ds-base would introduce bugs in testing: #1095537
    • Build-Depends(-Arch): 389-ds-base rust-ahash-0.7 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/3/389-ds-base.html
    • autopkgtest for 389-ds-base/3.1.1+dfsg1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 90 days old (needed 2 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:
    • Updating homer-api would introduce bugs in testing: #1095931
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/homer-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• rust-append-only-vec (- to 0.1.7-1)
  • Migration status for rust-append-only-vec (- to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-append-only-vec/0.1.7-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-append-only-vec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• rust-clap-complete-nushell (- to 4.5.4-1)
  • Migration status for rust-clap-complete-nushell (- to 4.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-clap-complete-nushell-dev/amd64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/arm64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/armel has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/armhf has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/i386 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/mips64el has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/ppc64el has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/riscv64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/s390x has unsatisfiable dependency
    • Updating rust-clap-complete-nushell would introduce bugs in testing: #1092486
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-clap-complete-nushell.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• mlterm (- to 3.9.3-3)
  • Migration status for mlterm (- to 3.9.3-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for spectrwm/3.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Build-Depends(-Arch): mlterm freewnn (not considered)
    • Depends: mlterm freewnn (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 91 days old (needed 5 days)
• rust-concurrent-arena (- to 0.1.10-2)
  • Migration status for rust-concurrent-arena (- to 0.1.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-concurrent-arena/0.1.10-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-concurrent-arena.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 91 days old (needed 5 days)
• cppgir (- to 2.0+git20240928.c8bb1c6-1)
  • Migration status for cppgir (- to 2.0+git20240928.c8bb1c6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cppgir would introduce bugs in testing: #1097127
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cppgir.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 94 days old (needed 5 days)
• deepboof (- to 0.5.1+ds-2)
  • Migration status for deepboof (- to 0.5.1+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): deepboof jarchivelib (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepboof.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 days old (needed 5 days)
• gcc-11 (- to 11.5.0-2)
  • Migration status for gcc-11 (- to 11.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11 would introduce bugs in testing: #1023690
    • autopkgtest for gcc-11/11.5.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
    • autopkgtest for mpich/4.2.1-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for rustc/1.85.0+dfsg1-1: riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 95 days old (needed 5 days)
• gcc-11-cross (- to 22)
  • Migration status for gcc-11-cross (- to 22): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-11-cross gcc-11 (not considered)
    • Built-Using: gcc-11-cross gcc-11 (not considered)
    • Depends: gcc-11-cross gcc-11 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • 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 i386 - info ♻
    • 95 days old (needed 5 days)
• gcc-11-cross-ports (- to 19)
  • Migration status for gcc-11-cross-ports (- to 19): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-11-cross-ports gcc-11 (not considered)
    • Built-Using: gcc-11-cross-ports gcc-11 (not considered)
    • Depends: gcc-11-cross-ports gcc-11 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross-ports.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 95 days old (needed 5 days)
• pmbootstrap (- to 3.1.0-1)
  • Migration status for pmbootstrap (- to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pmbootstrap/3.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmbootstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 96 days old (needed 5 days)
• tt-rss (- to 21~git20210204.b4cbc79+dfsg-2)
  • Migration status for tt-rss (- to 21~git20210204.b4cbc79+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tt-rss would introduce bugs in testing: #1021656, #1054608
    • Depends: tt-rss php-gettext (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tt-rss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 96 days old (needed 5 days)
• napari-console (- to 0.1.3-1)
  • Migration status for napari-console (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for napari-console/0.1.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): napari-console napari (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-console.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 97 days old (needed 5 days)
• php-dompdf (- to 3.0.2+dfsg-1)
  • Migration status for php-dompdf (- to 3.0.2+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-dompdf php-dompdf-svg-lib (not considered)
    • Depends: php-dompdf php-dompdf-svg-lib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-dompdf.html
    • autopkgtest for php-dompdf/3.0.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 97 days old (needed 2 days)
• rust-netlink-packet-wireguard (- to 0.2.3-2)
  • Migration status for rust-netlink-packet-wireguard (- to 0.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-netlink-packet-wireguard/0.2.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-netlink-packet-wireguard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 97 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uw-imap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 98 days old (needed 5 days)
• ruby-build (- to 20241225.2-1)
  • Migration status for ruby-build (- to 20241225.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-build would introduce bugs in testing: #1095653
    • autopkgtest for ruby-build/20241225.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-build.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 100 days old (needed 5 days)
• bioxtasraw (- to 2.3.0-2)
  • Migration status for bioxtasraw (- to 2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-bioxtasraw/riscv64 has unsatisfiable dependency
    • autopkgtest for bioxtasraw/2.3.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/b/bioxtasraw.html
  • Additional info:
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 103 days old (needed 5 days)
• libphp-swiftmailer (- to 6.3.0-7)
  • Migration status for libphp-swiftmailer (- to 6.3.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libphp-swiftmailer would introduce bugs in testing: #1039752, #1085113
    • autopkgtest for libphp-swiftmailer/6.3.0-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libphp-swiftmailer.html
    • Reproducible on armhf - info ♻
    • 104 days old (needed 5 days)
• rust-ruma-state-res (- to 0.8.0-5)
  • Migration status for rust-ruma-state-res (- to 0.8.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ruma-state-res/0.8.0-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ruma-state-res.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 104 days old (needed 5 days)
• bidentd (- to 1.1.4-1.4)
  • Migration status for bidentd (- to 1.1.4-1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bidentd would introduce bugs in testing: #763430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bidentd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 105 days old (needed 5 days)
• php-codesniffer (- to 3.11.2-2)
  • Migration status for php-codesniffer (- to 3.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-codesniffer would introduce bugs in testing: #1092009
    • autopkgtest for php-codesniffer/3.11.2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-codesniffer.html
    • Reproducible on armhf - info ♻
    • 105 days old (needed 5 days)
• apt-clone (- to 0.4.3+nmu3)
  • Migration status for apt-clone (- to 0.4.3+nmu3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-clone would introduce bugs in testing: #1074515
    • autopkgtest for apt-clone/0.4.3+nmu3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-clone.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• ukui-panel (- to 4.0.0.5-1)
  • Migration status for ukui-panel (- to 4.0.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ukui-panel/amd64 has unsatisfiable dependency
    • ukui-panel/arm64 has unsatisfiable dependency
    • ukui-panel/armel has unsatisfiable dependency
    • ukui-panel/armhf has unsatisfiable dependency
    • ukui-panel/i386 has unsatisfiable dependency
    • ukui-panel/mips64el has unsatisfiable dependency
    • ukui-panel/ppc64el has unsatisfiable dependency
    • ukui-panel/riscv64 has unsatisfiable dependency
    • ukui-panel/s390x has unsatisfiable dependency
    • Updating ukui-panel would introduce bugs in testing: #1079813
    • ukui-panel unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-dev
    • Build-Depends(-Arch): ukui-panel ukui-control-center (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-panel.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 106 days old (needed 5 days)
• ruby-chef-config (- to 16.12.3-3)
  • Migration status for ruby-chef-config (- to 16.12.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-chef-config would introduce bugs in testing: #1091657
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-chef-config.html
    • autopkgtest for ruby-chef-config/16.12.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 107 days old (needed 2 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrr.html
    • Reproducible on armhf - info ♻
    • 108 days old (needed 5 days)
• tycho (- to 2.7.5-1.1)
  • Migration status for tycho (- to 2.7.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tycho would introduce bugs in testing: #1086322
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tycho.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 108 days old (needed 5 days)
• lintian-brush (- to 0.160)
  • Migration status for lintian-brush (- to 0.160): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lintian-brush/0.160: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on armel
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lintian-brush.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 109 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dtcwt.html
    • 109 days old (needed 5 days)
• ruby-vips (2.1.4-1.1 to 2.2.2-1)
  • Migration status for ruby-vips (2.1.4-1.1 to 2.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-vips would introduce bugs in testing: #1088648, #1098623, #1102179
    • autopkgtest for ruby-image-processing/1.14.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-vips/2.2.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Updating ruby-vips will fix bugs in testing: #1093786
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-vips.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 109 days old (needed 5 days)
• rust-symphonia-format-caf (- to 0.5.4-1)
  • Migration status for rust-symphonia-format-caf (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-symphonia-format-caf-dev/amd64 has unsatisfiable dependency
    • rust-symphonia-format-caf unsatisfiable Build-Depends(-Arch) on amd64: librust-symphonia-core-0.5+default-dev (>= 0.5.4-~~)
    • rust-symphonia-format-caf unsatisfiable Build-Depends(-Arch) on amd64: librust-symphonia-metadata-0.5+default-dev (>= 0.5.4-~~)
    • Not built on buildd: arch amd64 binaries uploaded by alexander.kjall@gmail.com
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-symphonia-format-caf.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 109 days old (needed 5 days)
• libjpeg6b (- to 1:6b2-4)
  • Migration status for libjpeg6b (- to 1:6b2-4): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg6b.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 110 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: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanook.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 110 days old (needed 5 days)
• camping (- to 2.3-2)
  • Migration status for camping (- to 2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating camping would introduce bugs in testing: #1094532
    • autopkgtest for camping/2.3-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camping.html
    • Reproducible on armhf - info ♻
    • 112 days old (needed 5 days)
• opencl-clang-14 (- to 14.0.1-1)
  • Migration status for opencl-clang-14 (- to 14.0.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): opencl-clang-14 spirv-llvm-translator-14 (not considered)
    • Depends: opencl-clang-14 spirv-llvm-translator-14 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): opencl-clang-14 llvm-toolchain-14 (not considered)
    • Depends: opencl-clang-14 llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencl-clang-14.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 112 days old (needed 5 days)
• ruby-clockwork (- to 3.0.1-2)
  • Migration status for ruby-clockwork (- to 3.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-clockwork would introduce bugs in testing: #1066730
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-clockwork.html
    • autopkgtest for ruby-clockwork/3.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 112 days old (needed 2 days)
• git-ubuntu (- to 1.1-2)
  • Migration status for git-ubuntu (- to 1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for git-ubuntu/1.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-ubuntu.html
    • 113 days old (needed 5 days)
• iitii (- to 0.0+git20191030.85209e0-3)
  • Migration status for iitii (- to 0.0+git20191030.85209e0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): iitii libmmap-allocator (not considered)
    • Depends: iitii libmmap-allocator (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iitii.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 114 days old (needed 5 days)
• rust-termwiz (- to 0.22.0-2)
  • Migration status for rust-termwiz (- to 0.22.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-termwiz unsatisfiable Build-Depends(-Arch) on amd64: librust-finl-unicode-1+default-dev (>= 1.2-~~)
    • rust-termwiz unsatisfiable Build-Depends(-Arch) on amd64: librust-siphasher-0.3+default-dev
    • rust-termwiz unsatisfiable Build-Depends(-Arch) on amd64: librust-terminfo-0.8+default-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-termwiz.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 114 days old (needed 5 days)
• mosdepth (- to 0.3.10+ds-1)
  • Migration status for mosdepth (- to 0.3.10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mosdepth nim (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): mosdepth nim-docopt (not considered)
    • Build-Depends(-Arch): mosdepth nim-hts (not considered)
    • Build-Depends(-Arch): mosdepth nim-regex
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mosdepth.html
    • autopkgtest for mosdepth/0.3.10+ds-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 115 days old (needed 5 days)
• gpa (- to 0.11.0-1)
  • Migration status for gpa (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpa would introduce bugs in testing: #1089914
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 117 days old (needed 5 days)
• lomiri-sync-monitor (- to 0.6.0-4)
  • Migration status for lomiri-sync-monitor (- to 0.6.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-sync-monitor syncevolution (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-sync-monitor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 117 days old (needed 5 days)
• sia (- to 1.3.0-4)
  • Migration status for sia (- to 1.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sia would introduce bugs in testing: #1089970
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sia.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 117 days old (needed 5 days)
• umis (- to 1.0.9-2)
  • Migration status for umis (- to 1.0.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umis would introduce bugs in testing: #1089115
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umis.html
    • autopkgtest for umis/1.0.9-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 117 days old (needed 2 days)
• readucks (- to 0.0.3-6)
  • Migration status for readucks (- to 0.0.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for readucks/0.0.3-6: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/readucks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 118 days old (needed 5 days)
• pbsuite (- to 15.8.24+dfsg-8)
  • Migration status for pbsuite (- to 15.8.24+dfsg-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pbsuite would introduce bugs in testing: #1091721
    • autopkgtest for pbsuite/15.8.24+dfsg-8: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pbsuite.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 119 days old (needed 5 days)
• wapiti (- to 3.2.2+dfsg-1)
  • Migration status for wapiti (- to 3.2.2+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wapiti mitmproxy (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wapiti.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 119 days old (needed 5 days)
• resteasy (- to 3.6.2-3)
  • Migration status for resteasy (- to 3.6.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating resteasy would introduce bugs in testing: #879469
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resteasy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 120 days old (needed 5 days)
• python-aiobotocore (- to 2.13.1-1.1)
  • Migration status for python-aiobotocore (- to 2.13.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiobotocore would introduce bugs in testing: #1091485
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiobotocore.html
    • 121 days old (needed 5 days)
• open-adventure (- to 1.20-1)
  • Migration status for open-adventure (- to 1.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating open-adventure would introduce bugs in testing: #1091064
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-adventure.html
    • Reproducible on armhf - info ♻
    • 122 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)
    • 122 days old (needed 5 days)
• rust-libyml (- to 0.0.5-2)
  • Migration status for rust-libyml (- to 0.0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-libyml would introduce bugs in testing: #1094422
    • autopkgtest for rust-libyml/0.0.5-2: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libyml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 122 days old (needed 5 days)
• rust-serde-yml (- to 0.0.12-2)
  • Migration status for rust-serde-yml (- to 0.0.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-serde-yml would introduce bugs in testing: #1094419
    • Build-Depends(-Arch): rust-serde-yml rust-libyml (not considered)
    • Depends: rust-serde-yml rust-libyml (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde-yml.html
    • autopkgtest for rust-serde-yml/0.0.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 122 days old (needed 2 days)
• tgl (- to 2.0.1+git20160323.ffb04cac-4)
  • Migration status for tgl (- to 2.0.1+git20160323.ffb04cac-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tgl would introduce bugs in testing: #1087142
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tgl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 123 days old (needed 5 days)
• rust-cargo-test-support (- to 0.3.0-1)
  • Migration status for rust-cargo-test-support (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cargo-test-support-dev/amd64 has unsatisfiable dependency
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-git2-0.19+default-dev
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+default-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+paserk-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+serde-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+std-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+v3-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+default-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+diff-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+dir-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+json-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+regex-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+term-svg-dev (>= 0.6.9-~~)
    • Not built on buildd: arch amd64 binaries uploaded by debian@fabian.gruenbichler.email
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cargo-test-support.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 124 days old (needed 5 days)
• pushpin (- to 1.39.1-3)
  • Migration status for pushpin (- to 1.39.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pushpin would introduce bugs in testing: #1084517
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pushpin.html
    • Reproducible on armhf - info ♻
    • 125 days old (needed 5 days)
• intel-graphics-compiler (- to 1.0.17791.18-1)
  • Migration status for intel-graphics-compiler (- to 1.0.17791.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-graphics-compiler would introduce bugs in testing: #1061213
    • Build-Depends(-Arch): intel-graphics-compiler intel-vc-intrinsics (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler llvm-toolchain-14 (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler opencl-clang-14
    • Build-Depends(-Arch): intel-graphics-compiler spirv-llvm-translator-14 (not considered)
    • Depends: intel-graphics-compiler llvm-toolchain-14 (not considered)
    • Depends: intel-graphics-compiler opencl-clang-14
    • Depends: intel-graphics-compiler spirv-llvm-translator-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-graphics-compiler.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 126 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:
    • autopkgtest for nim-hts/0.3.25+ds-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): 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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 126 days old (needed 5 days)
• php-imap (- to 3:1.0.3-1)
  • Migration status for php-imap (- to 3:1.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-imap uw-imap (not considered)
    • Depends: php-imap uw-imap (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-imap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 126 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 126 days old (needed 2 days)
• gfpoken (- to 1-5)
  • Migration status for gfpoken (- to 1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gfpoken would introduce bugs in testing: #1090226
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfpoken.html
    • 127 days old (needed 5 days)
• hts-nim-tools (- to 0.2.1-2)
  • Migration status for hts-nim-tools (- to 0.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for hts-nim-tools/0.2.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): hts-nim-tools nim (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-docopt (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-hts (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-kexpr (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-lapper (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-regex
    • Build-Depends(-Arch): hts-nim-tools nim-unicodedb
    • Build-Depends(-Arch): hts-nim-tools nim-unicodeplus
    • Depends: hts-nim-tools nim-hts (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hts-nim-tools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 127 days old (needed 5 days)
• hiera-eyaml (- to 4.2.0-1.1)
  • Migration status for hiera-eyaml (- to 4.2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hiera-eyaml would introduce bugs in testing: #1094446
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hiera-eyaml.html
    • autopkgtest for hiera-eyaml/4.2.0-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 128 days old (needed 2 days)
• python-aiovlc (- to 0.4.2-4)
  • Migration status for python-aiovlc (- to 0.4.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiovlc would introduce bugs in testing: #1098591
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiovlc.html
    • autopkgtest for python-aiovlc/0.4.2-4: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 128 days old (needed 5 days)
• eye (- to 1:10.30.11~ds-1)
  • Migration status for eye (- to 1:10.30.11~ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eye would introduce bugs in testing: #1088839
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eye.html
    • autopkgtest for eye/1:10.30.11~ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 129 days old (needed 2 days)
• partman-hfs (- to 14)
  • Migration status for partman-hfs (- to 14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • partman-hfs/amd64 has unsatisfiable dependency
    • partman-hfs/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 129 days old (needed 5 days)
• gvm (- to 24.11.1)
  • Migration status for gvm (- to 24.11.1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvm ospd-openvas (not considered)
    • Invalidated by dependency
    • Depends: gvm gsad
    • Depends: gvm gvmd
    • Depends: gvm openvas-scanner
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 130 days old (needed 5 days)
• sctk (- to 2.4.12+dfsg-1)
  • Migration status for sctk (- to 2.4.12+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sctk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 131 days old (needed 5 days)
• tinydyndns (- to 0.4.2.debian1-4)
  • Migration status for tinydyndns (- to 0.4.2.debian1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tinydyndns would introduce bugs in testing: #1090038
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinydyndns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 131 days old (needed 5 days)
• pybdsf (- to 1.12.0-1)
  • Migration status for pybdsf (- to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-bdsf/amd64 has unsatisfiable dependency
    • python3-bdsf/arm64 has unsatisfiable dependency
    • python3-bdsf/armel has unsatisfiable dependency
    • python3-bdsf/armhf has unsatisfiable dependency
    • python3-bdsf/i386 has unsatisfiable dependency
    • python3-bdsf/mips64el has unsatisfiable dependency
    • python3-bdsf/ppc64el has unsatisfiable dependency
    • python3-bdsf/riscv64 has unsatisfiable dependency
    • python3-bdsf/s390x has unsatisfiable dependency
    • Updating pybdsf would introduce bugs in testing: #1094757, #1095216
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pybdsf.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • New but not reproducible on armhf - info ♻
    • 133 days old (needed 5 days)
• python-meshplex (- to 0.17.1-4)
  • Migration status for python-meshplex (- to 0.17.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-meshplex would introduce bugs in testing: #1094984
    • autopkgtest for python-meshplex/0.17.1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-meshplex.html
    • Reproducible on armhf - info ♻
    • 133 days old (needed 5 days)
• dadadodo (- to 1.04-10)
  • Migration status for dadadodo (- to 1.04-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dadadodo/1.04-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dadadodo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 135 days old (needed 5 days)
• puppetdb (- to 8.4.1-3)
  • Migration status for puppetdb (- to 8.4.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating puppetdb would introduce bugs in testing: #1091504
    • autopkgtest for puppetdb/8.4.1-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppetdb.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 135 days old (needed 5 days)
• python-mypermobil (- to 0.1.8-1.1)
  • Migration status for python-mypermobil (- to 0.1.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-mypermobil would introduce bugs in testing: #1090280
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mypermobil.html
    • 135 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: Regression or new test ♻, arm64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vg.html
    • 135 days old (needed 5 days)
• gosa-plugins-rolemanagement (- to 2.8~git20211022.90f50d1-1.1)
  • Migration status for gosa-plugins-rolemanagement (- to 2.8~git20211022.90f50d1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-rolemanagement gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-rolemanagement.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 136 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 136 days old (needed 2 days)
• gosa (- to 2.8~git20230203.10abe45+dfsg-18)
  • Migration status for gosa (- to 2.8~git20230203.10abe45+dfsg-18): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa php-imap (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 137 days old (needed 5 days)
• lastpass-cli (- to 1.6.1-1)
  • Migration status for lastpass-cli (- to 1.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lastpass-cli would introduce bugs in testing: #1092429
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lastpass-cli.html
    • autopkgtest for lastpass-cli/1.6.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 137 days old (needed 2 days)
• trocla (- to 0.5.1-4)
  • Migration status for trocla (- to 0.5.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • trocla-puppetserver/amd64 has unsatisfiable dependency
    • trocla-puppetserver/arm64 has unsatisfiable dependency
    • trocla-puppetserver/armel has unsatisfiable dependency
    • trocla-puppetserver/armhf has unsatisfiable dependency
    • trocla-puppetserver/i386 has unsatisfiable dependency
    • trocla-puppetserver/mips64el has unsatisfiable dependency
    • trocla-puppetserver/ppc64el has unsatisfiable dependency
    • trocla-puppetserver/riscv64 has unsatisfiable dependency
    • trocla-puppetserver/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/trocla.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 137 days old (needed 5 days)
• slic3r (- to 1.3.0+dfsg1-5.1)
  • Migration status for slic3r (- to 1.3.0+dfsg1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slic3r would introduce bugs in testing: #1034848
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 138 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 139 days old (needed 2 days)
• mayavi2 (- to 4.8.2-4)
  • Migration status for mayavi2 (- to 4.8.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mayavi2/amd64 has unsatisfiable dependency
    • mayavi2/arm64 has unsatisfiable dependency
    • mayavi2/mips64el has unsatisfiable dependency
    • mayavi2/ppc64el has unsatisfiable dependency
    • mayavi2/riscv64 has unsatisfiable dependency
    • mayavi2/s390x has unsatisfiable dependency
    • Updating mayavi2 would introduce bugs in testing: #1092083
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mayavi2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 140 days old (needed 5 days)
• qt5-ukui-platformtheme (- to 1.0.8-5)
  • Migration status for qt5-ukui-platformtheme (- to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qt5-ukui-platformtheme would introduce bugs in testing: #1091097
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt5-ukui-platformtheme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 140 days old (needed 5 days)
• ruby-proc-to-ast (- to 0.2.0-1)
  • Migration status for ruby-proc-to-ast (- to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-proc-to-ast ruby-unparser (not considered)
    • Depends: ruby-proc-to-ast ruby-unparser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-proc-to-ast.html
    • autopkgtest for ruby-proc-to-ast/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 141 days old (needed 2 days)
• pct-scanner-scripts (- to 0.0.4-5)
  • Migration status for pct-scanner-scripts (- to 0.0.4-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pct-scanner-scripts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 142 days old (needed 5 days)
• prewikka (- to 5.2.0-2.3)
  • Migration status for prewikka (- to 5.2.0-2.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: prewikka libpreludedb (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prewikka.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 142 days old (needed 5 days)
• ruby-unparser (- to 0.6.13-1)
  • Migration status for ruby-unparser (- to 0.6.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-unparser/0.6.13-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-unparser.html
    • 142 days old (needed 5 days)
• nwall (- to 1.32+debian-10)
  • Migration status for nwall (- to 1.32+debian-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nwall would introduce bugs in testing: #1089824
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nwall.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 144 days old (needed 5 days)
• dials (- to 3.22.1+dfsg3-1)
  • Migration status for dials (- to 3.22.1+dfsg3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dials would introduce bugs in testing: #1089231
    • autopkgtest for dials/3.22.1+dfsg3-1: amd64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dials.html
    • Reproducible on amd64 - info ♻
    • 146 days old (needed 5 days)
• rust-dbus-secret-service (- to 4.0.3-2)
  • Migration status for rust-dbus-secret-service (- to 4.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-dbus-secret-service would introduce bugs in testing: #1081520
    • autopkgtest for rust-dbus-secret-service/4.0.3-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-dbus-secret-service.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 146 days old (needed 5 days)
• gensim (- to 4.3.3+dfsg-2)
  • Migration status for gensim (- to 4.3.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gensim/amd64 has unsatisfiable dependency
    • python3-gensim/arm64 has unsatisfiable dependency
    • python3-gensim/armel has unsatisfiable dependency
    • python3-gensim/armhf has unsatisfiable dependency
    • python3-gensim/i386 has unsatisfiable dependency
    • python3-gensim/mips64el has unsatisfiable dependency
    • python3-gensim/ppc64el has unsatisfiable dependency
    • python3-gensim/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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 148 days old (needed 5 days)
• valentina (- to 0.7.53~dfsg-2)
  • Migration status for valentina (- to 0.7.53~dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating valentina would introduce bugs in testing: #1087710
    • autopkgtest for valentina/0.7.53~dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valentina.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 149 days old (needed 5 days)
• netdata (- to 1.47.5-1)
  • Migration status for netdata (- to 1.47.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netdata would introduce bugs in testing: #1042533, #1045145
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 150 days old (needed 5 days)
• golang-github-vulcand-oxy (- to 2.0.0-3)
  • Migration status for golang-github-vulcand-oxy (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-vulcand-oxy/2.0.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-vulcand-oxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 151 days old (needed 5 days)
• postgresql-filedump (- to 17.1-1)
  • Migration status for postgresql-filedump (- to 17.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for postgresql-filedump/17.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgresql-filedump.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 151 days old (needed 5 days)
• python-sparse (- to 0.16.0a9-1)
  • Migration status for python-sparse (- to 0.16.0a9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-sparse would introduce bugs in testing: #1055847
    • autopkgtest for python-sparse/0.16.0a9-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/p/python-sparse.html
    • Build-Depends(-Arch): python-sparse numba (not considered)
  • Additional info:
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 152 days old (needed 5 days)
• priv-wrapper (- to 1.0.1-4)
  • Migration status for priv-wrapper (- to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for priv-wrapper/1.0.1-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/priv-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 153 days old (needed 5 days)
• sdml (- to 0.3.1+20241024-1)
  • Migration status for sdml (- to 0.3.1+20241024-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sdml would introduce bugs in testing: #1086384
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-tree-sitter-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-tree-sitter-highlight-0.20+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-tree-sitter-sdml-0.3+default-dev
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdml.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 153 days old (needed 5 days)
• rust-num-prime (- to 0.4.4-2)
  • Migration status for rust-num-prime (- to 0.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-num-prime/0.4.4-2: amd64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-prime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 156 days old (needed 5 days)
• ruby-rspec-parameterized-table-syntax (- to 1.0.1-1.1)
  • Migration status for ruby-rspec-parameterized-table-syntax (- to 1.0.1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core (not considered)
    • Depends: ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-table-syntax.html
    • autopkgtest for ruby-rspec-parameterized-table-syntax/1.0.1-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 158 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
    • Depends: cecilia python-pyo
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cecilia.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 166 days old (needed 5 days)
• kel-agent (- to 0.4.6-2.1)
  • Migration status for kel-agent (- to 0.4.6-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kel-agent would introduce bugs in testing: #1033710
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kel-agent.html
    • autopkgtest for kel-agent/0.4.6-2.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 169 days old (needed 2 days)
• haskell-lambdabot-novelty-plugins (- to 5.3.1.2-1)
  • Migration status for haskell-lambdabot-novelty-plugins (- to 5.3.1.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-lambdabot-novelty-plugins haskell-misfortune (not considered)
    • Build-Depends-Indep: haskell-lambdabot-novelty-plugins haskell-misfortune (not considered)
    • Depends: haskell-lambdabot-novelty-plugins haskell-misfortune (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-lambdabot-novelty-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 170 days old (needed 5 days)
• haskell-misfortune (- to 0.1.2.1-4)
  • Migration status for haskell-misfortune (- to 0.1.2.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • haskell-misfortune/amd64 has unsatisfiable dependency
    • haskell-misfortune/arm64 has unsatisfiable dependency
    • haskell-misfortune/armel has unsatisfiable dependency
    • haskell-misfortune/armhf has unsatisfiable dependency
    • haskell-misfortune/i386 has unsatisfiable dependency
    • haskell-misfortune/mips64el has unsatisfiable dependency
    • haskell-misfortune/ppc64el has unsatisfiable dependency
    • haskell-misfortune/riscv64 has unsatisfiable dependency
    • haskell-misfortune/s390x has unsatisfiable dependency
    • Updating haskell-misfortune would introduce bugs in testing: #1061618
    • 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 armel: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on armel: 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 mips64el: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on mips64el: 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 170 days old (needed 5 days)
• lambdabot (- to 5.3.1.2-1)
  • Migration status for lambdabot (- to 5.3.1.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lambdabot haskell-lambdabot-novelty-plugins (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lambdabot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 170 days old (needed 5 days)
• gitit (- to 0.15.1.2+dfsg-1)
  • Migration status for gitit (- to 0.15.1.2+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gitit haskell-hoauth2 (not considered)
    • Build-Depends-Indep: gitit haskell-hoauth2 (not considered)
    • Depends: gitit haskell-hoauth2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 174 days old (needed 5 days)
• rust-tree-sitter-cli (- to 0.20.8-6)
  • Migration status for rust-tree-sitter-cli (- to 0.20.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-tree-sitter-cli has no binaries on any arch
    • rust-tree-sitter-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.20+default-dev (>= 0.20.10-~~)
    • rust-tree-sitter-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-config-0.19+default-dev
    • rust-tree-sitter-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-highlight-0.20+default-dev
    • rust-tree-sitter-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-loader-0.20+default-dev
    • rust-tree-sitter-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-tags-0.20+default-dev
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 176 days old (needed 5 days)
• haskell-hledger-web (- to 1.32.3-1)
  • Migration status for haskell-hledger-web (- to 1.32.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-hledger-web haskell-base64 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hledger-web.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 177 days old (needed 5 days)
• python-uiprotect (- to 6.1.0-2)
  • Migration status for python-uiprotect (- to 6.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-uiprotect would introduce bugs in testing: #1098614
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-uiprotect.html
    • autopkgtest for python-uiprotect/6.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 177 days old (needed 2 days)
• haskell-hoauth2 (- to 2.10.0-1)
  • Migration status for haskell-hoauth2 (- to 2.10.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-hoauth2 haskell-base64 (not considered)
    • Build-Depends-Indep: haskell-hoauth2 haskell-base64 (not considered)
    • Depends: haskell-hoauth2 haskell-base64 (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hoauth2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 178 days old (needed 5 days)
• ruby-omniauth-saml (- to 2.2.1-1)
  • Migration status for ruby-omniauth-saml (- to 2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-saml would introduce bugs in testing: #1094543
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-saml.html
    • autopkgtest for ruby-omniauth-saml/2.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 178 days old (needed 2 days)
• phploc (- to 7.0.2-4)
  • Migration status for phploc (- to 7.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phploc/amd64 has unsatisfiable dependency
    • phploc/arm64 has unsatisfiable dependency
    • Updating phploc would introduce bugs in testing: #1092879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phploc.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 179 days old (needed 5 days)
• gvm-tools (- to 24.8.0-1)
  • Migration status for gvm-tools (- to 24.8.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): gvm-tools python-gvm (not considered)
    • Depends: gvm-tools python-gvm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm-tools.html
    • autopkgtest for gvm-tools/24.8.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 180 days old (needed 5 days)
• python-gvm (- to 24.8.0-1)
  • Migration status for python-gvm (- to 24.8.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: python-gvm gvmd (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gvm.html
    • autopkgtest for python-gvm/24.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 180 days old (needed 2 days)
• haskell-github (- to 0.29-1)
  • Migration status for haskell-github (- to 0.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-github would introduce bugs in testing: #1085141
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-github.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 181 days old (needed 5 days)
• eclipse-wtp (- to 3.35-1)
  • Migration status for eclipse-wtp (- to 3.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for eclipse-wtp/3.35-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-wtp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 182 days old (needed 5 days)
• geotranz (- to 3.7-4)
  • Migration status for geotranz (- to 3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geotranz would introduce bugs in testing: #1092415
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geotranz.html
    • Reproducible on armhf - info ♻
    • 182 days old (needed 5 days)
• python-homematicip (- to 1.1.2-1)
  • Migration status for python-homematicip (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-homematicip would introduce bugs in testing: #1084768
    • autopkgtest for python-homematicip/1.1.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-homematicip.html
    • 182 days old (needed 5 days)
• eclipse-collections (- to 11.1.0-1)
  • Migration status for eclipse-collections (- to 11.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): eclipse-collections tycho (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-collections.html
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 183 days old (needed 5 days)
• projectreactor (- to 2.0.8-2)
  • Migration status for projectreactor (- to 2.0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating projectreactor would introduce bugs in testing: #1091946
    • Build-Depends(-Arch): projectreactor eclipse-collections
    • Depends: projectreactor eclipse-collections
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/projectreactor.html
    • Reproducible on armhf - info ♻
    • 184 days old (needed 5 days)
• vala-panel-appmenu (- to 0.7.6+dfsg1-7)
  • Migration status for vala-panel-appmenu (- to 0.7.6+dfsg1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vala-panel-appmenu would introduce bugs in testing: #1091049, #1095102
    • Depends: vala-panel-appmenu appmenu-registrar (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vala-panel-appmenu.html
    • Reproducible on armhf - info ♻
    • 185 days old (needed 5 days)
• xfce4-sntray-plugin (- to 0.4.13.1-5)
  • Migration status for xfce4-sntray-plugin (- to 0.4.13.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfce4-sntray-plugin would introduce bugs in testing: #1086771, #1091960
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-sntray-plugin.html
    • Reproducible on armhf - info ♻
    • 185 days old (needed 5 days)
• haskell-base64 (- to 0.4.2.4-4)
  • Migration status for haskell-base64 (- to 0.4.2.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-base64 would introduce bugs in testing: #1057652
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-base64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 186 days old (needed 5 days)
• r-cran-gbm (- to 2.2.2-1)
  • Migration status for r-cran-gbm (- to 2.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-gbm would introduce bugs in testing: #1064922
    • autopkgtest for r-cran-gbm/2.2.2-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gbm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 186 days old (needed 5 days)
• jsurf-alggeo (- to 0.4.1+ds-5)
  • Migration status for jsurf-alggeo (- to 0.4.1+ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for jsurf-alggeo/0.4.1+ds-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsurf-alggeo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 187 days old (needed 5 days)
• r-cran-rpact (- to 4.1.0-1)
  • Migration status for r-cran-rpact (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-rpact/4.1.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rpact.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 187 days old (needed 5 days)
• kraft (- to 1.2.2-1)
  • Migration status for kraft (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kraft/amd64 has unsatisfiable dependency
    • kraft/arm64 has unsatisfiable dependency
    • kraft/armel has unsatisfiable dependency
    • kraft/armhf has unsatisfiable dependency
    • kraft/i386 has unsatisfiable dependency
    • kraft/mips64el has unsatisfiable dependency
    • kraft/ppc64el has unsatisfiable dependency
    • kraft/riscv64 has unsatisfiable dependency
    • kraft/s390x has unsatisfiable dependency
    • Updating kraft would introduce bugs in testing: #1029734, #1088983
    • kraft unsatisfiable Build-Depends(-Arch) on amd64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on amd64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on arm64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on arm64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armel: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armel: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armhf: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armhf: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on i386: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on i386: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on mips64el: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on mips64el: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on riscv64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on riscv64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on s390x: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on s390x: libkf5akonadicontact-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kraft.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 188 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 188 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 189 days old (needed 2 days)
• gitlab-shell (- to 14.35.0+ds1-2)
  • Migration status for gitlab-shell (- to 14.35.0+ds1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): gitlab-shell gitaly (not considered)
    • Built-Using: gitlab-shell gitaly (not considered)
    • Depends: gitlab-shell gitaly (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-shell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 days old (needed 5 days)
• apt-transport-in-toto (- to 0.1.1-5)
  • Migration status for apt-transport-in-toto (- to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-transport-in-toto would introduce bugs in testing: #1090090
    • Build-Depends(-Arch): apt-transport-in-toto in-toto (not considered)
    • Depends: apt-transport-in-toto in-toto (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-transport-in-toto.html
    • Reproducible on armhf - info ♻
    • 194 days old (needed 5 days)
• ruby-premailer (- to 1.27.0-1)
  • Migration status for ruby-premailer (- to 1.27.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-premailer would introduce bugs in testing: #1073370
    • autopkgtest for ruby-premailer/1.27.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-premailer.html
    • 194 days old (needed 5 days)
• php-horde-db (- to 2.4.1-8.1)
  • Migration status for php-horde-db (- to 2.4.1-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-db would introduce bugs in testing: #1089726
    • autopkgtest for php-horde-db/2.4.1-8.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 195 days old (needed 5 days)
• python-calendra (- to 7.9.1-1)
  • Migration status for python-calendra (- to 7.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-calendra would introduce bugs in testing: #1078636, #1092399
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calendra.html
    • Reproducible on armhf - info ♻
    • 195 days old (needed 5 days)
• haskell-cryptohash-cryptoapi (- to 0.1.4-9)
  • Migration status for haskell-cryptohash-cryptoapi (- to 0.1.4-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-cryptohash-cryptoapi would introduce bugs in testing: #1082561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cryptohash-cryptoapi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 197 days old (needed 5 days)
• nvchecker (- to 2.15.1-0.1)
  • Migration status for nvchecker (- to 2.15.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvchecker would introduce bugs in testing: #1082628
    • autopkgtest for nvchecker/2.15.1-0.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvchecker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 197 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 197 days old (needed 5 days)
• python-cobra (- to 0.29.1-1)
  • Migration status for python-cobra (- to 0.29.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-cobra would introduce bugs in testing: #1092791
    • autopkgtest for python-cobra/0.29.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cobra.html
    • Reproducible on armhf - info ♻
    • 197 days old (needed 5 days)
• haskell-options (- to 1.2.1.2-1)
  • Migration status for haskell-options (- to 1.2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-options would introduce bugs in testing: #1082184
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-options.html
    • 199 days old (needed 5 days)
• haskell-set-extra (- to 1.4.2-1)
  • Migration status for haskell-set-extra (- to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-set-extra would introduce bugs in testing: #1081387
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-set-extra.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
• unknown-horizons (- to 2019.1-8)
  • Migration status for unknown-horizons (- to 2019.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unknown-horizons would introduce bugs in testing: #1089495
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unknown-horizons.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
• rust-openpgp-card-state (- to 0.3.1-1)
  • Migration status for rust-openpgp-card-state (- 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-openpgp-card-state rust-keyring (not considered)
    • Depends: rust-openpgp-card-state rust-keyring (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-openpgp-card-state.html
    • autopkgtest for rust-openpgp-card-state/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 200 days old (needed 2 days)
• coremltools (- to 8.0-1)
  • Migration status for coremltools (- to 8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating coremltools would introduce bugs in testing: #1077292
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coremltools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 201 days old (needed 5 days)
• freesas (- to 2024.9.0-1)
  • Migration status for freesas (- to 2024.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-freesas/amd64 has unsatisfiable dependency
    • python3-freesas/arm64 has unsatisfiable dependency
    • python3-freesas/armel has unsatisfiable dependency
    • python3-freesas/armhf has unsatisfiable dependency
    • python3-freesas/i386 has unsatisfiable dependency
    • python3-freesas/mips64el has unsatisfiable dependency
    • python3-freesas/ppc64el has unsatisfiable dependency
    • python3-freesas/riscv64 has unsatisfiable dependency
    • Updating freesas would introduce bugs in testing: #1088040, #1092054
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freesas.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • 201 days old (needed 5 days)
• haskell-presburger (- to 1.3.1-11)
  • Migration status for haskell-presburger (- to 1.3.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-presburger would introduce bugs in testing: #1085437
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-presburger.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 201 days old (needed 5 days)
• gxr-openvr (- to 0.15.1-2.2)
  • Migration status for gxr-openvr (- to 0.15.1-2.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gxr-openvr openvr (not considered)
    • Depends: gxr-openvr openvr (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 204 days old (needed 5 days)
• haskell-hcwiid (- to 0.0.6.1-7)
  • Migration status for haskell-hcwiid (- to 0.0.6.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-hcwiid would introduce bugs in testing: #1093530
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hcwiid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 205 days old (needed 5 days)
• memkind (- to 1.14.0-3.1)
  • Migration status for memkind (- to 1.14.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating memkind would introduce bugs in testing: #1089267
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/memkind.html
    • autopkgtest for memkind/1.14.0-3.1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 206 days old (needed 2 days)
• nrpe-ng (- to 0.2.0-1.3)
  • Migration status for nrpe-ng (- to 0.2.0-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nrpe-ng would introduce bugs in testing: #1087622
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nrpe-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 206 days old (needed 5 days)
• pass-audit (- to 1.2-1.2)
  • Migration status for pass-audit (- to 1.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pass-audit/1.2-1.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pass-audit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 206 days old (needed 5 days)
• resampy (- to 0.4.3+ds-4)
  • Migration status for resampy (- to 0.4.3+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for resampy/0.4.3+ds-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): resampy numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resampy.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 206 days old (needed 5 days)
• epoptes (- to 23.08-2)
  • Migration status for epoptes (- to 23.08-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epoptes would introduce bugs in testing: #1084716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epoptes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 210 days old (needed 5 days)
• node-microsoft-fast (- to 0~20240320+ds1-1)
  • Migration status for node-microsoft-fast (- to 0~20240320+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-microsoft-fast would introduce bugs in testing: #1081223
    • Not built on buildd: arch all binaries uploaded by x.guimard@free.fr, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-microsoft-fast.html
    • autopkgtest for node-microsoft-fast/0~20240320+ds1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 211 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bellows.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 211 days old (needed 5 days)
• python-foobot-async (- to 1.0.1-2)
  • Migration status for python-foobot-async (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-foobot-async would introduce bugs in testing: #1090274
    • autopkgtest for python-foobot-async/1.0.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-foobot-async.html
    • Reproducible on armhf - info ♻
    • 211 days old (needed 5 days)
• pocketsphinx-python (- to 1:0.1.15-7)
  • Migration status for pocketsphinx-python (- to 1:0.1.15-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pocketsphinx-python would introduce bugs in testing: #1088764
    • autopkgtest for pocketsphinx-python/1:0.1.15-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pocketsphinx-python.html
    • Reproducible on armhf - info ♻
    • 212 days old (needed 5 days)
• python-aiowebostv (- to 0.4.2-2)
  • Migration status for python-aiowebostv (- to 0.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-aiowebostv/amd64 has unsatisfiable dependency
    • python3-aiowebostv/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-aiowebostv.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 212 days old (needed 5 days)
• python-aiowithings (- to 3.0.3-2)
  • Migration status for python-aiowithings (- to 3.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiowithings would introduce bugs in testing: #1084327
    • autopkgtest for python-aiowithings/3.0.3-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiowithings.html
    • 212 days old (needed 5 days)
• rust-openssh-sftp-client (- to 0.15.0-1)
  • Migration status for rust-openssh-sftp-client (- to 0.15.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-openssh-sftp-client rust-openssh-sftp-client-lowlevel (not considered)
    • Depends: rust-openssh-sftp-client rust-openssh-sftp-client-lowlevel (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-openssh-sftp-client.html
    • autopkgtest for rust-openssh-sftp-client/0.15.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 212 days old (needed 5 days)
• rust-openssh-sftp-client-lowlevel (- to 0.7.0-1)
  • Migration status for rust-openssh-sftp-client-lowlevel (- to 0.7.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-openssh-sftp-client-lowlevel rust-concurrent-arena (not considered)
    • Depends: rust-openssh-sftp-client-lowlevel rust-concurrent-arena (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-openssh-sftp-client-lowlevel.html
    • autopkgtest for rust-openssh-sftp-client-lowlevel/0.7.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 212 days old (needed 5 days)
• mindthegap (- to 2.3.0-4)
  • Migration status for mindthegap (- to 2.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mindthegap/2.3.0-4: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mindthegap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 213 days old (needed 5 days)
• onevpl (- to 1:2.13.0-1)
  • Migration status for onevpl (- to 1:2.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • onevpl has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • 213 days old (needed 5 days)
• r-cran-filehash (- to 2.4-6-1)
  • Migration status for r-cran-filehash (- to 2.4-6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-filehash/2.4-6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-filehash.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 214 days old (needed 5 days)
• python-auto-pytabs (- to 0.4.0-2)
  • Migration status for python-auto-pytabs (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-auto-pytabs/0.4.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-auto-pytabs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 216 days old (needed 5 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 217 days old (needed 5 days)
• weakforced (- to 2.10.2-1)
  • Migration status for weakforced (- to 2.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating weakforced would introduce bugs in testing: #1088172
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/w/weakforced.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 217 days old (needed 5 days)
• golang-github-traefik-paerser (- to 0.2.0-1)
  • Migration status for golang-github-traefik-paerser (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-traefik-paerser/0.2.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by alois@micard.lu, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-traefik-paerser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 221 days old (needed 5 days)
• telegram-desktop (- to 4.14.9+ds-1.1)
  • Migration status for telegram-desktop (- to 4.14.9+ds-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telegram-desktop would introduce bugs in testing: #1091237, #1092377
    • Build-Depends(-Arch): telegram-desktop cppgir (not considered)
    • Built-Using: telegram-desktop cppgir (not considered)
    • Depends: telegram-desktop abseil
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-desktop.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 225 days old (needed 5 days)
• ruby-active-model-serializers (- to 0.10.14-1)
  • Migration status for ruby-active-model-serializers (- to 0.10.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-active-model-serializers would introduce bugs in testing: #1095377
    • autopkgtest for ruby-active-model-serializers/0.10.14-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-active-model-serializers ruby-grape (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-active-model-serializers.html
    • Reproducible on armhf - info ♻
    • 227 days old (needed 5 days)
• trafficserver (- to 9.2.5+ds-1)
  • Migration status for trafficserver (- to 9.2.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • trafficserver/amd64 has unsatisfiable dependency
    • trafficserver/arm64 has unsatisfiable dependency
    • Updating trafficserver would introduce bugs in testing: #1087531, #1099691, #1101996, #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 ♻
    • 227 days old (needed 5 days)
• ukui-media (- to 3.1.1.2-2)
  • Migration status for ukui-media (- to 3.1.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ukui-media ukui-control-center (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-media.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 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/armel has unsatisfiable dependency
    • python3-libzfs/armhf has unsatisfiable dependency
    • python3-libzfs/i386 has unsatisfiable dependency
    • python3-libzfs/mips64el has unsatisfiable dependency
    • python3-libzfs/ppc64el has unsatisfiable dependency
    • python3-libzfs/riscv64 has unsatisfiable dependency
    • python3-libzfs/s390x has unsatisfiable dependency
    • Updating py-libzfs would introduce bugs in testing: #1082340, #1093171
    • Build-Depends(-Arch): py-libzfs cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 228 days old (needed 5 days)
• clblas (- to 2.12-6)
  • Migration status for clblas (- to 2.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clblas would introduce bugs in testing: #949767
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clblas.html
    • autopkgtest for clblas/2.12-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 229 days old (needed 2 days)
• pympler (- to 1.1+dfsg1-1)
  • Migration status for pympler (- to 1.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pympler would introduce bugs in testing: #1082154
    • autopkgtest for pympler/1.1+dfsg1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pympler.html
    • Reproducible on armhf - info ♻
    • 229 days old (needed 5 days)
• csaps (- to 1.2.0-4)
  • Migration status for csaps (- to 1.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating csaps would introduce bugs in testing: #1094071
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/csaps.html
    • autopkgtest for csaps/1.2.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • 230 days old (needed 5 days)
• christianriesen-otp (- to 1.4.3-5)
  • Migration status for christianriesen-otp (- to 1.4.3-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): christianriesen-otp christianriesen-base32 (not considered)
    • Depends: christianriesen-otp christianriesen-base32 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/christianriesen-otp.html
    • autopkgtest for christianriesen-otp/1.4.3-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 236 days old (needed 2 days)
• gosa-plugins-ldapmanager (- to 2.8~git20240614.c540e17-1)
  • Migration status for gosa-plugins-ldapmanager (- to 2.8~git20240614.c540e17-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-ldapmanager gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-ldapmanager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 236 days old (needed 5 days)
• matthiasmullie-minify (- to 1.3.73-1)
  • Migration status for matthiasmullie-minify (- to 1.3.73-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matthiasmullie-minify would introduce bugs in testing: #1099938
    • Build-Depends(-Arch): matthiasmullie-minify matthiasmullie-path-converter (not considered)
    • Depends: matthiasmullie-minify matthiasmullie-path-converter (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matthiasmullie-minify.html
    • autopkgtest for matthiasmullie-minify/1.3.73-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 236 days old (needed 2 days)
• python-aiomodernforms (- to 0.1.8-2)
  • Migration status for python-aiomodernforms (- to 0.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiomodernforms would introduce bugs in testing: #1084326
    • autopkgtest for python-aiomodernforms/0.1.8-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiomodernforms.html
    • Reproducible on armhf - info ♻
    • 236 days old (needed 5 days)
• christianriesen-base32 (- to 1.6.0-4)
  • Migration status for christianriesen-base32 (- to 1.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating christianriesen-base32 would introduce bugs in testing: #1092005
    • autopkgtest for christianriesen-base32/1.6.0-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/christianriesen-base32.html
    • Reproducible on armhf - info ♻
    • 237 days old (needed 5 days)
• eluceo-ical (- to 0.16.1-3)
  • Migration status for eluceo-ical (- to 0.16.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eluceo-ical would introduce bugs in testing: #1099658
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eluceo-ical.html
    • autopkgtest for eluceo-ical/0.16.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 237 days old (needed 2 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-traefik-yaegi.html
    • Reproducible on armhf - info ♻
    • 237 days old (needed 5 days)
• matthiasmullie-path-converter (- to 1.1.3-3)
  • Migration status for matthiasmullie-path-converter (- to 1.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matthiasmullie-path-converter would introduce bugs in testing: #1092008
    • autopkgtest for matthiasmullie-path-converter/1.1.3-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matthiasmullie-path-converter.html
    • Reproducible on armhf - info ♻
    • 237 days old (needed 5 days)
• looking-glass (- to 0+b6+ds1-1)
  • Migration status for looking-glass (- to 0+b6+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating looking-glass would introduce bugs in testing: #1094308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/looking-glass.html
    • Reproducible on amd64 - info ♻
    • 239 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 ♻
    • 239 days old (needed 5 days)
• rust-tree-sitter-loader (- to 0.20.0-4)
  • Migration status for rust-tree-sitter-loader (- to 0.20.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-tree-sitter-loader has no binaries on any arch
    • rust-tree-sitter-loader unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.20+default-dev
    • rust-tree-sitter-loader unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-highlight-0.20+default-dev
    • rust-tree-sitter-loader unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-tags-0.20+default-dev
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 240 days old (needed 5 days)
• spectrum2 (- to 2.2.1+dfsg-2)
  • Migration status for spectrum2 (- to 2.2.1+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): spectrum2 swift-im (not considered)
    • Depends: spectrum2 swift-im (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spectrum2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 240 days old (needed 5 days)
• gimp-plugin-registry (- to 9.20240808)
  • Migration status for gimp-plugin-registry (- to 9.20240808): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gimp-plugin-registry/amd64 has unsatisfiable dependency
    • gimp-plugin-registry/arm64 has unsatisfiable dependency
    • gimp-plugin-registry/armel has unsatisfiable dependency
    • gimp-plugin-registry/armhf has unsatisfiable dependency
    • gimp-plugin-registry/i386 has unsatisfiable dependency
    • gimp-plugin-registry/mips64el has unsatisfiable dependency
    • gimp-plugin-registry/ppc64el has unsatisfiable dependency
    • gimp-plugin-registry/riscv64 has unsatisfiable dependency
    • Updating gimp-plugin-registry would introduce bugs in testing: #1043232
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on amd64: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on arm64: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on armel: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on armhf: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on i386: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on mips64el: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on ppc64el: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on riscv64: libgimp2.0-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gimp-plugin-registry.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 242 days old (needed 5 days)
• google-guest-agent (- to 20211116.00-6.2)
  • Migration status for google-guest-agent (- to 20211116.00-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating google-guest-agent would introduce bugs in testing: #1070319
    • google-guest-agent/amd64 has unsatisfiable Built-Using on golang-1.22 1.22.6-1
    • google-guest-agent/arm64 has unsatisfiable Built-Using on golang-1.22 1.22.6-1
    • google-guest-agent/armel has unsatisfiable Built-Using on golang-1.22 1.22.6-1
    • google-guest-agent/armhf has unsatisfiable Built-Using on golang-1.22 1.22.6-1
    • google-guest-agent/i386 has unsatisfiable Built-Using on golang-1.22 1.22.6-1
    • google-guest-agent/mips64el has unsatisfiable Built-Using on golang-1.22 1.22.6-1
    • google-guest-agent/ppc64el has unsatisfiable Built-Using on golang-1.22 1.22.6-1
    • google-guest-agent/riscv64 has unsatisfiable Built-Using on golang-1.22 1.22.6-1
    • google-guest-agent/s390x has unsatisfiable Built-Using on golang-1.22 1.22.6-1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/google-guest-agent.html
    • autopkgtest for google-guest-agent/20211116.00-6.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 242 days old (needed 2 days)
• libprelude (- to 5.2.0-5.6)
  • Migration status for libprelude (- to 5.2.0-5.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-prelude/amd64 has unsatisfiable dependency
    • ruby-libprelude/amd64 has unsatisfiable dependency
    • python3-prelude/arm64 has unsatisfiable dependency
    • ruby-libprelude/arm64 has unsatisfiable dependency
    • python3-prelude/armel has unsatisfiable dependency
    • ruby-libprelude/armel has unsatisfiable dependency
    • python3-prelude/armhf has unsatisfiable dependency
    • ruby-libprelude/armhf has unsatisfiable dependency
    • python3-prelude/i386 has unsatisfiable dependency
    • ruby-libprelude/i386 has unsatisfiable dependency
    • python3-prelude/mips64el has unsatisfiable dependency
    • ruby-libprelude/mips64el has unsatisfiable dependency
    • python3-prelude/ppc64el has unsatisfiable dependency
    • ruby-libprelude/ppc64el has unsatisfiable dependency
    • python3-prelude/riscv64 has unsatisfiable dependency
    • ruby-libprelude/riscv64 has unsatisfiable dependency
    • python3-prelude/s390x has unsatisfiable dependency
    • ruby-libprelude/s390x has unsatisfiable dependency
    • Updating libprelude would introduce bugs in testing: #1080647, #1081473
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libprelude.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 242 days old (needed 5 days)
• r-cran-psychtools (- to 2.4.3-1)
  • Migration status for r-cran-psychtools (- to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-psychtools would introduce bugs in testing: #1078401
    • autopkgtest for r-cran-afex/1.4-1-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for r-cran-psychtools/2.4.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Build-Depends(-Arch): r-cran-psychtools r-cran-rtf (not considered)
    • Depends: r-cran-psychtools r-cran-rtf (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-psychtools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 243 days old (needed 5 days)
• python-adb-shell (- to 0.4.4-2)
  • Migration status for python-adb-shell (- to 0.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-adb-shell would introduce bugs in testing: #1082192, #1086887
    • python-adb-shell unsatisfiable Build-Depends-Indep on amd64: python3-libusb1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-adb-shell.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 244 days old (needed 5 days)
• safeeyes (- to 2.1.9-1.1)
  • Migration status for safeeyes (- to 2.1.9-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating safeeyes would introduce bugs in testing: #1077629
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/safeeyes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 244 days old (needed 5 days)
• prospector (- to 1.10.3-1)
  • Migration status for prospector (- to 1.10.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): prospector pyroma (not considered)
    • Depends: prospector pyroma (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prospector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• haskell-libxml-sax (- to 0.7.5-15)
  • Migration status for haskell-libxml-sax (- to 0.7.5-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-libxml-sax-doc/amd64 has unsatisfiable dependency
    • libghc-libxml-sax-doc/arm64 has unsatisfiable dependency
    • Updating haskell-libxml-sax would introduce bugs in testing: #1081369
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-libxml-sax.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 247 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-open-meteo.html
    • 248 days old (needed 5 days)
• swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-4)
  • Migration status for swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swift-im would introduce bugs in testing: #1088140, #1093866
    • Build-Depends(-Arch): swift-im qtwebkit-opensource-src (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swift-im.html
    • Reproducible on armhf - info ♻
    • 248 days old (needed 5 days)
• python-thinc (- to 9.0.0-2)
  • Migration status for python-thinc (- to 9.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-thinc/amd64 has unsatisfiable dependency
    • python3-thinc/arm64 has unsatisfiable dependency
    • python3-thinc/armhf has unsatisfiable dependency
    • python3-thinc/i386 has unsatisfiable dependency
    • python3-thinc/mips64el has unsatisfiable dependency
    • python3-thinc/riscv64 has unsatisfiable dependency
    • python3-thinc/s390x has unsatisfiable dependency
    • Updating python-thinc would introduce bugs in testing: #1082128, #1089717
    • Build-Depends(-Arch): python-thinc cython-legacy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-thinc.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 249 days old (needed 5 days)
• pychopper (- to 2.7.10-1)
  • Migration status for pychopper (- to 2.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pychopper would introduce bugs in testing: #1082368
    • autopkgtest for pychopper/2.7.10-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pychopper.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 251 days old (needed 5 days)
• pyroma (- to 4.2-2)
  • Migration status for pyroma (- to 4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyroma would introduce bugs in testing: #1077701
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyroma.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 253 days old (needed 5 days)
• cadabra2 (- to 2.4.3.2-2)
  • Migration status for cadabra2 (- to 2.4.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cadabra2 would introduce bugs in testing: #1061319, #1080566
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cadabra2.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 254 days old (needed 5 days)
• markdown-toc-el (- to 0.1.5-4)
  • Migration status for markdown-toc-el (- to 0.1.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating markdown-toc-el would introduce bugs in testing: #1036359
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-toc-el.html
    • autopkgtest for markdown-toc-el/0.1.5-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 256 days old (needed 2 days)
• minetest (- to 5.8.0+dfsg+~1.9.0mt13-2)
  • Migration status for minetest (- to 5.8.0+dfsg+~1.9.0mt13-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • minetest has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 256 days old (needed 5 days)
• cycle-quotes (- to 0.1-6)
  • Migration status for cycle-quotes (- to 0.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cycle-quotes would introduce bugs in testing: #1020192
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cycle-quotes.html
    • 257 days old (needed 5 days)
• ruby-carrierwave (- to 3.0.7-1)
  • Migration status for ruby-carrierwave (- to 3.0.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-carrierwave ruby-fog-rackspace (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-carrierwave.html
    • autopkgtest for ruby-carrierwave/3.0.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 257 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/armel has unsatisfiable dependency
    • libsynfig0t64/armhf has unsatisfiable dependency
    • libsynfig0t64/i386 has unsatisfiable dependency
    • libsynfig0t64/mips64el has unsatisfiable dependency
    • libsynfig0t64/ppc64el has unsatisfiable dependency
    • libsynfig0t64/riscv64 has unsatisfiable dependency
    • libsynfig0t64/s390x has unsatisfiable dependency
    • Updating synfig would introduce bugs in testing: #1079335, #1086935
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synfig.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 257 days old (needed 5 days)
• numba (- to 0.59.1+dfsg-3)
  • Migration status for numba (- to 0.59.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-numba/amd64 has unsatisfiable dependency
    • python3-numba/ppc64el has unsatisfiable dependency
    • Updating numba would introduce bugs in testing: #1033907, #1077047, #1086090, #1090292
    • numba unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • numba unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • numba unsatisfiable Build-Depends(-Arch) on i386: architecture-is-64-bit
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): numba llvmlite (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numba.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 258 days old (needed 5 days)
• php-dompdf-svg-lib (- to 1.0.0-1)
  • Migration status for php-dompdf-svg-lib (- to 1.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 258 days old (needed 2 days)
• python-pymzml (- to 2.5.10+repack1-1)
  • Migration status for python-pymzml (- to 2.5.10+repack1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pymzml would introduce bugs in testing: #1092544
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pymzml.html
    • New but not reproducible on armhf - info ♻
    • 258 days old (needed 5 days)
• ruby-omniauth-multipassword (- to 2.0.1-1)
  • Migration status for ruby-omniauth-multipassword (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-multipassword would introduce bugs in testing: #1094531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-multipassword.html
    • autopkgtest for ruby-omniauth-multipassword/2.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 258 days old (needed 2 days)
• hyprpaper (- to 0.7.0-1)
  • Migration status for hyprpaper (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyprpaper would introduce bugs in testing: #1092436
    • Build-Depends(-Arch): hyprpaper wlroots-0.17 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyprpaper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 262 days old (needed 5 days)
• pydrive2 (- to 1.20.0-1)
  • Migration status for pydrive2 (- to 1.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pydrive2 would introduce bugs in testing: #1083031
    • Build-Depends(-Arch): pydrive2 python-oauth2client (not considered)
    • Depends: pydrive2 python-oauth2client (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydrive2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 263 days old (needed 5 days)
• tulip (- to 5.4.0+dfsg-3.1)
  • Migration status for tulip (- to 5.4.0+dfsg-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tulip would introduce bugs in testing: #1092993, #1101128
    • Build-Depends(-Arch): tulip qtwebkit-opensource-src (not considered)
    • Build-Depends(-Arch): tulip sip4 (not considered)
    • Depends: tulip python3.12 (not considered)
    • Depends: tulip qtwebkit-opensource-src (not considered)
    • Depends: tulip sip4 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tulip.html
    • 264 days old (needed 5 days)
• ffcv (- to 1.0.0+git20240202+ds-2)
  • Migration status for ffcv (- to 1.0.0+git20240202+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-ffcv/riscv64 has unsatisfiable dependency
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/f/ffcv.html
  • Additional info:
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 265 days old (needed 5 days)
• virtualbox-ext-pack (- to 7.0.20-1)
  • Migration status for virtualbox-ext-pack (- to 7.0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • virtualbox-ext-pack/arm64 has unsatisfiable dependency
    • Depends: virtualbox-ext-pack virtualbox (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 266 days old (needed 5 days)
• sks (- to 1.1.6+git20210302.c3ba6d5a-4.1)
  • Migration status for sks (- to 1.1.6+git20210302.c3ba6d5a-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sks/armel has unsatisfiable dependency
    • sks/mips64el has unsatisfiable dependency
    • Updating sks would introduce bugs in testing: #1073911, #1093110
    • autopkgtest for sks/1.1.6+git20210302.c3ba6d5a-4.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sks.html
    • uninstallable on arch armel, not running autopkgtest there
    • 267 days old (needed 5 days)
• crowdsec-custom-bouncer (- to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer (- to 0.0.15-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): crowdsec-custom-bouncer crowdsec (not considered)
    • Built-Using: crowdsec-custom-bouncer crowdsec (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Build-Depends(-Arch): crowdsec-custom-bouncer golang-github-crowdsecurity-go-cs-bouncer
    • Built-Using: crowdsec-custom-bouncer golang-github-crowdsecurity-go-cs-bouncer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec-custom-bouncer.html
    • autopkgtest for crowdsec-custom-bouncer/0.0.15-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 268 days old (needed 2 days)
• crowdsec-firewall-bouncer (- to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer (- to 0.0.25-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): crowdsec-firewall-bouncer crowdsec (not considered)
    • Built-Using: crowdsec-firewall-bouncer crowdsec (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Build-Depends(-Arch): crowdsec-firewall-bouncer golang-github-crowdsecurity-go-cs-bouncer
    • Built-Using: crowdsec-firewall-bouncer golang-github-crowdsecurity-go-cs-bouncer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec-firewall-bouncer.html
    • autopkgtest for crowdsec-firewall-bouncer/0.0.25-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 268 days old (needed 2 days)
• mes (- to 0.27-1)
  • Migration status for mes (- to 0.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mes would introduce bugs in testing: #1067952
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mes.html
    • 269 days old (needed 5 days)
• appmenu-registrar (- to 24.05-1)
  • Migration status for appmenu-registrar (- to 24.05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating appmenu-registrar would introduce bugs in testing: #1095103
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appmenu-registrar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 271 days old (needed 5 days)
• mailfront (- to 2.12-3)
  • Migration status for mailfront (- to 2.12-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mailfront cvm (not considered)
    • Depends: mailfront cvm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailfront.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 273 days old (needed 5 days)
• purple-lurch (- to 0.7.0-2.1)
  • Migration status for purple-lurch (- to 0.7.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • purple-lurch/armel has unsatisfiable dependency
    • purple-lurch/armhf has unsatisfiable dependency
    • Updating purple-lurch would introduce bugs in testing: #1098589
    • autopkgtest for purple-lurch/0.7.0-2.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purple-lurch.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 273 days old (needed 5 days)
• spopt (- to 0.6.1-2)
  • Migration status for spopt (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for spopt/0.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spopt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 273 days old (needed 5 days)
• socklog (- to 2.1.0+repack-5.1)
  • Migration status for socklog (- to 2.1.0+repack-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating socklog would introduce bugs in testing: #1075523
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socklog.html
    • 274 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
    • python3-cogent3/mips64el has unsatisfiable dependency
    • python3-cogent3/ppc64el has unsatisfiable dependency
    • Updating python-cogent would introduce bugs in testing: #1090269
    • python-cogent unsatisfiable Build-Depends(-Arch) on s390x: architecture-is-little-endian
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): python-cogent numba (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-cogent.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 276 days old (needed 5 days)
• klystrack (- to 0.20171212-7)
  • Migration status for klystrack (- to 0.20171212-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating klystrack would introduce bugs in testing: #1075115
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/klystrack.html
    • 277 days old (needed 5 days)
• ruby-jira (- to 2.3.0-1)
  • Migration status for ruby-jira (- to 2.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jira ruby-atlassian-jwt (not considered)
    • Depends: ruby-jira ruby-atlassian-jwt (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jira.html
    • autopkgtest for ruby-jira/2.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 277 days old (needed 2 days)
• yaramod (- to 3.21.0-1.1)
  • Migration status for yaramod (- to 3.21.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for yaramod/3.21.0-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yaramod.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 278 days old (needed 5 days)
• cub (- to 2.1.1-1)
  • Migration status for cub (- to 2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cub has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 280 days old (needed 5 days)
• libcudacxx (- to 2.1.1-1)
  • Migration status for libcudacxx (- to 2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libcudacxx has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 280 days old (needed 5 days)
• libthrust (- to 2.1.1-1)
  • Migration status for libthrust (- to 2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libthrust has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 280 days old (needed 5 days)
• krop (- to 0.6.0-3)
  • Migration status for krop (- to 0.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating krop would introduce bugs in testing: #1029735
    • Build-Depends(-Arch): krop pypdf2 (not considered)
    • Depends: krop pypdf2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/krop.html
    • autopkgtest for krop/0.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 281 days old (needed 2 days)
• symfit (- to 0.5.6-3)
  • Migration status for symfit (- to 0.5.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating symfit would introduce bugs in testing: #1078417, #1079756
    • autopkgtest for symfit/0.5.6-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/symfit.html
    • 281 days old (needed 5 days)
• q2-diversity-lib (- to 2024.5.0-1)
  • Migration status for q2-diversity-lib (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-diversity-lib/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-diversity-lib qiime (not considered)
    • Depends: q2-diversity-lib q2-emperor
    • Depends: q2-diversity-lib q2-feature-table (not considered)
    • Depends: q2-diversity-lib qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-diversity-lib.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 282 days old (needed 5 days)
• q2-emperor (- to 2024.5.0-2)
  • Migration status for q2-emperor (- to 2024.5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): q2-emperor qiime (not considered)
    • Depends: q2-emperor qiime (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): q2-emperor q2-types (not considered)
    • Depends: q2-emperor q2-types (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-emperor.html
    • autopkgtest for q2-emperor/2024.5.0-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 282 days old (needed 5 days)
• q2-sample-classifier (- to 2024.5.0-2)
  • Migration status for q2-sample-classifier (- to 2024.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-sample-classifier/2024.5.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): q2-sample-classifier qiime (not considered)
    • Depends: q2-sample-classifier q2-feature-table (not considered)
    • Depends: q2-sample-classifier q2-types (not considered)
    • Depends: q2-sample-classifier qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-sample-classifier.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 282 days old (needed 5 days)
• sagenb-export (- to 3.4-1)
  • Migration status for sagenb-export (- to 3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sagenb-export would introduce bugs in testing: #1091611
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagenb-export.html
    • autopkgtest for sagenb-export/3.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 282 days old (needed 5 days)
• gpscorrelate (- to 2.1-2)
  • Migration status for gpscorrelate (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpscorrelate would introduce bugs in testing: #1076775
    • autopkgtest for gpscorrelate/2.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpscorrelate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 284 days old (needed 5 days)
• caml-crush (- to 1.0.12-1.2)
  • Migration status for caml-crush (- to 1.0.12-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating caml-crush would introduce bugs in testing: #1074545, #1076869
    • caml-crush unsatisfiable Build-Depends(-Arch) on armhf: ocaml-native-compilers
    • caml-crush unsatisfiable Build-Depends(-Arch) on i386: ocaml-native-compilers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caml-crush.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 285 days old (needed 5 days)
• q2-dada2 (- to 2024.5.0-1)
  • Migration status for q2-dada2 (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-dada2/2024.5.0-1: amd64: Regression or new test ♻
    • Build-Depends(-Arch): q2-dada2 qiime (not considered)
    • Depends: q2-dada2 q2-types (not considered)
    • Depends: q2-dada2 qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-dada2.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 285 days old (needed 5 days)
• q2cli (- to 2024.5.0-2)
  • Migration status for q2cli (- to 2024.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • q2cli/amd64 has unsatisfiable dependency
    • q2cli/arm64 has unsatisfiable dependency
    • Updating q2cli would introduce bugs in testing: #1076080
    • Build-Depends(-Arch): q2cli qiime (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/q/q2cli.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 285 days old (needed 5 days)
• slapi-nis (- to 0.60.0-1.1)
  • Migration status for slapi-nis (- to 0.60.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): slapi-nis 389-ds-base (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slapi-nis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 285 days old (needed 5 days)
• q2-alignment (- to 2024.5.0-1)
  • Migration status for q2-alignment (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-alignment would introduce bugs in testing: #1076318
    • autopkgtest for q2-alignment/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-alignment q2-types (not considered)
    • Build-Depends(-Arch): q2-alignment qiime (not considered)
    • Depends: q2-alignment q2-types (not considered)
    • Depends: q2-alignment qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-alignment.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 286 days old (needed 5 days)
• q2-demux (- to 2024.5.0+dfsg-1)
  • Migration status for q2-demux (- to 2024.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-demux would introduce bugs in testing: #1076315
    • autopkgtest for q2-demux/2024.5.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-demux q2-types (not considered)
    • Build-Depends(-Arch): q2-demux qiime (not considered)
    • Depends: q2-demux q2-types (not considered)
    • Depends: q2-demux qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-demux.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 286 days old (needed 5 days)
• q2-metadata (- to 2024.5.0+dfsg-1)
  • Migration status for q2-metadata (- to 2024.5.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): q2-metadata qiime (not considered)
    • Depends: q2-metadata qiime (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): q2-metadata q2-quality-filter (not considered)
    • Build-Depends(-Arch): q2-metadata q2-types (not considered)
    • Depends: q2-metadata q2-quality-filter (not considered)
    • Depends: q2-metadata q2-types (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-metadata.html
    • autopkgtest for q2-metadata/2024.5.0+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 286 days old (needed 2 days)
• q2-phylogeny (- to 2024.5.0-1)
  • Migration status for q2-phylogeny (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-phylogeny would introduce bugs in testing: #1076317
    • autopkgtest for q2-phylogeny/2024.5.0-1: amd64: Regression or new test ♻
    • Depends: q2-phylogeny q2-alignment (not considered)
    • Depends: q2-phylogeny q2-types (not considered)
    • Depends: q2-phylogeny qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-phylogeny.html
    • Reproducible on amd64 - info ♻
    • 286 days old (needed 5 days)
• q2-quality-control (- to 2024.5.0-1)
  • Migration status for q2-quality-control (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-quality-control would introduce bugs in testing: #1076914
    • autopkgtest for q2-quality-control/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress
    • Build-Depends(-Arch): q2-quality-control q2-feature-table (not considered)
    • Build-Depends(-Arch): q2-quality-control q2-taxa
    • Build-Depends(-Arch): q2-quality-control qiime (not considered)
    • Depends: q2-quality-control q2-taxa
    • Depends: q2-quality-control qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-quality-control.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 286 days old (needed 5 days)
• q2-taxa (- to 2024.5.0+dfsg-1)
  • Migration status for q2-taxa (- to 2024.5.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): q2-taxa qiime (not considered)
    • Depends: q2-taxa qiime (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): q2-taxa q2-types (not considered)
    • Depends: q2-taxa q2-types (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-taxa.html
    • autopkgtest for q2-taxa/2024.5.0+dfsg-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 286 days old (needed 5 days)
• q2-cutadapt (- to 2024.5.0-1)
  • Migration status for q2-cutadapt (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-cutadapt/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-cutadapt q2-types (not considered)
    • Build-Depends(-Arch): q2-cutadapt qiime (not considered)
    • Depends: q2-cutadapt q2-types (not considered)
    • Depends: q2-cutadapt qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-cutadapt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 287 days old (needed 5 days)
• q2-feature-table (- to 2024.5.0+dfsg-1)
  • Migration status for q2-feature-table (- to 2024.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-feature-table/2024.5.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-feature-table q2-types (not considered)
    • Build-Depends(-Arch): q2-feature-table qiime (not considered)
    • Depends: q2-feature-table q2-types (not considered)
    • Depends: q2-feature-table qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-feature-table.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 287 days old (needed 5 days)
• q2-fragment-insertion (- to 2024.5.0-1)
  • Migration status for q2-fragment-insertion (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-fragment-insertion/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-fragment-insertion qiime (not considered)
    • Depends: q2-fragment-insertion q2-types (not considered)
    • Depends: q2-fragment-insertion qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-fragment-insertion.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 287 days old (needed 5 days)
• q2-quality-filter (- to 2024.5.0-1)
  • Migration status for q2-quality-filter (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-quality-filter/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): q2-quality-filter q2-types (not considered)
    • Build-Depends(-Arch): q2-quality-filter qiime (not considered)
    • Depends: q2-quality-filter q2-types (not considered)
    • Depends: q2-quality-filter qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-quality-filter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 287 days old (needed 5 days)
• q2-types (- to 2024.5.0-1)
  • Migration status for q2-types (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-types would introduce bugs in testing: #1076316
    • autopkgtest for q2-types/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-types qiime (not considered)
    • Depends: q2-types qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-types.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 287 days old (needed 5 days)
• qiime (- to 2024.5.0-1)
  • Migration status for qiime (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiime would introduce bugs in testing: #1076314, #1084668
    • autopkgtest for qiime/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 287 days old (needed 5 days)
• sdpa (- to 7.3.18-1)
  • Migration status for sdpa (- to 7.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sdpa/amd64 has unsatisfiable dependency
    • sdpa/arm64 has unsatisfiable dependency
    • sdpa/armhf has unsatisfiable dependency
    • sdpa/i386 has unsatisfiable dependency
    • sdpa/mips64el has unsatisfiable dependency
    • sdpa/ppc64el has unsatisfiable dependency
    • sdpa/riscv64 has unsatisfiable dependency
    • sdpa/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sdpa.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 287 days old (needed 5 days)
• fonts-arapey (- to 0+git20200408-3)
  • Migration status for fonts-arapey (- to 0+git20200408-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-arapey would introduce bugs in testing: #1087299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-arapey.html
    • 289 days old (needed 5 days)
• libhdr-histogram (- to 0.11.8-4)
  • Migration status for libhdr-histogram (- to 0.11.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libhdr-histogram/0.11.8-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhdr-histogram.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 289 days old (needed 5 days)
• libcypher-parser (- to 0.6.2-0.2)
  • Migration status for libcypher-parser (- to 0.6.2-0.2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcypher-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 291 days old (needed 5 days)
• phnxdeco (- to 0.33-3.2)
  • Migration status for phnxdeco (- to 0.33-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phnxdeco would introduce bugs in testing: #1075385
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phnxdeco.html
    • 292 days old (needed 5 days)
• r-cran-sjstats (- to 0.19.0-1)
  • Migration status for r-cran-sjstats (- to 0.19.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-sjstats r-cran-performance (not considered)
    • Depends: r-cran-sjstats r-cran-performance (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-sjstats r-cran-effectsize (not considered)
    • 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 294 days old (needed 2 days)
• ruby-omniauth-shibboleth-redux (- to 2.0.0-2)
  • Migration status for ruby-omniauth-shibboleth-redux (- to 2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-shibboleth-redux would introduce bugs in testing: #1094549
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-shibboleth-redux.html
    • autopkgtest for ruby-omniauth-shibboleth-redux/2.0.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 294 days old (needed 5 days)
• ntopng (- to 5.2.1+dfsg1-2)
  • Migration status for ntopng (- to 5.2.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ntopng would introduce bugs in testing: #1038842, #1090110
    • Build-Depends(-Arch): ntopng ndpi (not considered)
    • Depends: ntopng ndpi (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntopng.html
    • New but not reproducible on armhf - info ♻
    • 295 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
    • 297 days old (needed 5 days)
• hilive (- to 2.0a-4)
  • Migration status for hilive (- to 2.0a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hilive would introduce bugs in testing: #1053499
    • autopkgtest for hilive/2.0a-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hilive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 298 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
    • 298 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 299 days old (needed 5 days)
• rcconf (- to 3.2+nmu2)
  • Migration status for rcconf (- to 3.2+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rcconf would introduce bugs in testing: #570404
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rcconf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 300 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
    • 301 days old (needed 5 days)
• src2tex (- to 2.12h-9.1)
  • Migration status for src2tex (- to 2.12h-9.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating src2tex would introduce bugs in testing: #1075535
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/src2tex.html
    • 301 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
    • 302 days old (needed 5 days)
• python-awkward (- to 2.6.5-1)
  • Migration status for python-awkward (- to 2.6.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-awkward/2.6.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-awkward.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 305 days old (needed 5 days)
• harden-doc (- to 3.19+nmu3)
  • Migration status for harden-doc (- to 3.19+nmu3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating harden-doc would introduce bugs in testing: #1053602
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harden-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 310 days old (needed 5 days)
• netctl (- to 1.29-1)
  • Migration status for netctl (- to 1.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/n/netctl.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 310 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
    • autopkgtest for odin/2.0.5-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eterm.html
    • 311 days old (needed 5 days)
• gfxreconstruct (- to 1.0.4+dfsg-1)
  • Migration status for gfxreconstruct (- to 1.0.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gfxreconstruct would introduce bugs in testing: #1081863
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfxreconstruct.html
    • 311 days old (needed 5 days)
• python-pynndescent (- to 0.5.11-1)
  • Migration status for python-pynndescent (- to 0.5.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pynndescent would introduce bugs in testing: #1090284
    • autopkgtest for python-pynndescent/0.5.11-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻
    • Build-Depends(-Arch): python-pynndescent llvmlite (not considered)
    • Build-Depends(-Arch): python-pynndescent numba (not considered)
    • Depends: python-pynndescent llvmlite (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pynndescent.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 311 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pytray.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 312 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
    • 313 days old (needed 5 days)
• prelude-correlator (- to 5.2.0-1.2)
  • Migration status for prelude-correlator (- to 5.2.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): prelude-correlator libprelude (not considered)
    • Depends: prelude-correlator libprelude (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-correlator.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 316 days old (needed 5 days)
• libmmap-allocator (- to 0.4.0+git20200122.adbfbe1-2)
  • Migration status for libmmap-allocator (- to 0.4.0+git20200122.adbfbe1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmmap-allocator.html
    • autopkgtest for libmmap-allocator/0.4.0+git20200122.adbfbe1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 317 days old (needed 2 days)
• dbab (- to 1.5.8-1.1)
  • Migration status for dbab (- to 1.5.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dbab would introduce bugs in testing: #1100058
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for dbab/1.5.8-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 318 days old (needed 5 days)
• ledgersmb (- to 1.6.33+ds-2.2)
  • Migration status for ledgersmb (- to 1.6.33+ds-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ledgersmb would introduce bugs in testing: #1027472
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ledgersmb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 318 days old (needed 5 days)
• tomoyo-tools (- to 2.6.1-20210910-1.1)
  • Migration status for tomoyo-tools (- to 2.6.1-20210910-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomoyo-tools would introduce bugs in testing: #1088729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomoyo-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 318 days old (needed 5 days)
• unicrypto (- to 0.0.10-2)
  • Migration status for unicrypto (- to 0.0.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unicrypto would introduce bugs in testing: #1090176
    • autopkgtest for unicrypto/0.0.10-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): unicrypto python-mbedtls (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unicrypto.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 318 days old (needed 5 days)
• vanguards (- to 0.3.1-2.4)
  • Migration status for vanguards (- to 0.3.1-2.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vanguards would introduce bugs in testing: #1074750
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vanguards.html
    • 318 days old (needed 5 days)
• pplacer (- to 1.1~alpha19-8)
  • Migration status for pplacer (- to 1.1~alpha19-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pplacer would introduce bugs in testing: #1074546, #1093109
    • autopkgtest for pplacer/1.1~alpha19-8: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplacer.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 319 days old (needed 5 days)
• ukui-screensaver (- to 3.0.3.3-2)
  • Migration status for ukui-screensaver (- to 3.0.3.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ukui-screensaver ukui-session-manager (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-screensaver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 319 days old (needed 5 days)
• mercurial-evolve (- to 11.1.3-1)
  • Migration status for mercurial-evolve (- to 11.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mercurial-evolve would introduce bugs in testing: #1076081, #1076895
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mercurial-evolve.html
    • 320 days old (needed 5 days)
• tla (- to 1.3.5+dfsg2-1)
  • Migration status for tla (- to 1.3.5+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tla would introduce bugs in testing: #1075579
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tla.html
    • 320 days old (needed 5 days)
• quickml (- to 0.8-2)
  • Migration status for quickml (- to 0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quickml would introduce bugs in testing: #1073471
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickml.html
    • 321 days old (needed 5 days)
• photopc (- to 3.07-4)
  • Migration status for photopc (- to 3.07-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating photopc would introduce bugs in testing: #1091307
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/photopc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 324 days old (needed 5 days)
• olive-editor (- to 20230614+ds-2)
  • Migration status for olive-editor (- to 20230614+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • olive-editor/amd64 has unsatisfiable dependency
    • olive-editor/arm64 has unsatisfiable dependency
    • olive-editor/mips64el has unsatisfiable dependency
    • olive-editor/ppc64el has unsatisfiable dependency
    • olive-editor/riscv64 has unsatisfiable dependency
    • olive-editor/s390x has unsatisfiable dependency
    • Updating olive-editor would introduce bugs in testing: #1072441
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/olive-editor.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 326 days old (needed 5 days)
• rust-ahash-0.7 (- to 0.7.8-2)
  • Migration status for rust-ahash-0.7 (- to 0.7.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ahash-0.7 would introduce bugs in testing: #1077617
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ahash-0.7.html
    • autopkgtest for rust-ahash-0.7/0.7.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 326 days old (needed 2 days)
• 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kde-config-systemd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 328 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 329 days old (needed 5 days)
• liblopsub (- to 1.0.5-1)
  • Migration status for liblopsub (- to 1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liblopsub would introduce bugs in testing: #1086623, #1089365
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libl/liblopsub.html
    • Reproducible on armhf - info ♻
    • 331 days old (needed 5 days)
• software-properties (- to 0.99.30-4.1)
  • Migration status for software-properties (- to 0.99.30-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating software-properties would introduce bugs in testing: #1038747, #1088285, #1089720
    • autopkgtest for software-properties/0.99.30-4.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/software-properties.html
    • 331 days old (needed 5 days)
• tfortune (- to 1.0.2-1)
  • Migration status for tfortune (- to 1.0.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tfortune liblopsub (not considered)
    • Depends: tfortune liblopsub (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tfortune.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 331 days old (needed 5 days)
• python-mbedtls (- to 2.10.1-1)
  • Migration status for python-mbedtls (- to 2.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mbedtls/amd64 has unsatisfiable dependency
    • python3-mbedtls/arm64 has unsatisfiable dependency
    • python3-mbedtls/armel has unsatisfiable dependency
    • python3-mbedtls/armhf has unsatisfiable dependency
    • python3-mbedtls/i386 has unsatisfiable dependency
    • python3-mbedtls/mips64el has unsatisfiable dependency
    • python3-mbedtls/ppc64el has unsatisfiable dependency
    • python3-mbedtls/riscv64 has unsatisfiable dependency
    • python3-mbedtls/s390x has unsatisfiable dependency
    • Updating python-mbedtls would introduce bugs in testing: #1075872
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mbedtls.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 332 days old (needed 5 days)
• coz-profiler (- to 0.2.2-3)
  • Migration status for coz-profiler (- to 0.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating coz-profiler would introduce bugs in testing: #1066941
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for coz-profiler/0.2.2-3: ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coz-profiler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 334 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
    • 334 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
    • 335 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
    • 339 days old (needed 5 days)
• llvm-toolchain-14 (- to 1:14.0.6-20)
  • Migration status for llvm-toolchain-14 (- to 1:14.0.6-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liblldb-14t64/amd64 has unsatisfiable dependency
    • liblldb-14t64/arm64 has unsatisfiable dependency
    • liblldb-14t64/armel has unsatisfiable dependency
    • liblldb-14t64/armhf has unsatisfiable dependency
    • liblldb-14t64/i386 has unsatisfiable dependency
    • liblldb-14t64/ppc64el has unsatisfiable dependency
    • liblldb-14t64/s390x has unsatisfiable dependency
    • Updating llvm-toolchain-14 would introduce bugs in testing: #1036596, #1058822, #1068840, #1076412, #1084564, #1100374
    • autopkgtest for llvm-toolchain-14/1:14.0.6-20: riscv64: Regression or new test ♻
    • autopkgtest for rustc/1.85.0+dfsg1-1: riscv64: Pass
    • missing build on mips64el
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
    • Depends: llvm-toolchain-14 abseil
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/llvm-toolchain-14.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 339 days old (needed 5 days)
• rust-zerofrom (- to 0.1.3-1)
  • Migration status for rust-zerofrom (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-zerofrom would introduce bugs in testing: #1073146
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zerofrom.html
    • autopkgtest for rust-zerofrom/0.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 346 days old (needed 2 days)
• nim (- to 1.6.14-3)
  • Migration status for nim (- to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • nim/amd64 has unsatisfiable dependency
    • nim/arm64 has unsatisfiable dependency
    • nim/armel has unsatisfiable dependency
    • nim/armhf has unsatisfiable dependency
    • nim/i386 has unsatisfiable dependency
    • nim/mips64el has unsatisfiable dependency
    • nim/ppc64el has unsatisfiable dependency
    • nim/riscv64 has unsatisfiable dependency
    • Updating nim would introduce bugs in testing: #1071691
    • nim unsatisfiable Build-Depends(-Arch) on amd64: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on arm64: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on armel: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on armhf: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on i386: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 347 days old (needed 5 days)
• ganglia (- to 3.7.2-7)
  • Migration status for ganglia (- to 3.7.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ganglia would introduce bugs in testing: #1074977
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia.html
    • autopkgtest for ganglia/3.7.2-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 348 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 348 days old (needed 5 days)
• sniffit (- to 0.6-1)
  • Migration status for sniffit (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sniffit would introduce bugs in testing: #1075521
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sniffit.html
    • autopkgtest for sniffit/0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 349 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/armel has unsatisfiable dependency
    • libt3window0/armel 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/mips64el has unsatisfiable dependency
    • libt3window0/mips64el 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
    • 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 armel: 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 mips64el: 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 350 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
    • 350 days old (needed 5 days)
• ukui-control-center (- to 3.22.1.28-1)
  • Migration status for ukui-control-center (- to 3.22.1.28-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ukui-control-center/amd64 has unsatisfiable dependency
    • ukui-control-center/arm64 has unsatisfiable dependency
    • ukui-control-center/armel has unsatisfiable dependency
    • ukui-control-center/armhf has unsatisfiable dependency
    • ukui-control-center/i386 has unsatisfiable dependency
    • ukui-control-center/mips64el has unsatisfiable dependency
    • ukui-control-center/ppc64el has unsatisfiable dependency
    • ukui-control-center/riscv64 has unsatisfiable dependency
    • ukui-control-center/s390x has unsatisfiable dependency
    • Updating ukui-control-center would introduce bugs in testing: #1079811
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-control-center.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 351 days old (needed 5 days)
• network-manager-fortisslvpn (- to 1.4.0-1.1)
  • Migration status for network-manager-fortisslvpn (- to 1.4.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating network-manager-fortisslvpn would introduce bugs in testing: #1069693
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/network-manager-fortisslvpn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 352 days old (needed 5 days)
• tss2 (- to 1045-3)
  • Migration status for tss2 (- to 1045-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tss2 would introduce bugs in testing: #971758
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tss2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 352 days old (needed 5 days)
• cegui-mk2 (- to 0.8.7+git20220615-6)
  • Migration status for cegui-mk2 (- to 0.8.7+git20220615-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-libcegui-mk2-0.8.7/amd64 has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/arm64 has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/armel has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/armhf has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/i386 has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/mips64el has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/ppc64el has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/riscv64 has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/cegui-mk2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 353 days old (needed 5 days)
• pplatex (- to 1.0~beta2023.12.01.repack-1)
  • Migration status for pplatex (- to 1.0~beta2023.12.01.repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pplatex/amd64 has unsatisfiable dependency
    • pplatex/arm64 has unsatisfiable dependency
    • pplatex/armel has unsatisfiable dependency
    • pplatex/armhf has unsatisfiable dependency
    • pplatex/i386 has unsatisfiable dependency
    • pplatex/mips64el has unsatisfiable dependency
    • pplatex/ppc64el has unsatisfiable dependency
    • pplatex/riscv64 has unsatisfiable dependency
    • pplatex/s390x has unsatisfiable dependency
    • Updating pplatex would introduce bugs in testing: #1070288
    • pplatex unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplatex.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 353 days old (needed 5 days)
• syncevolution (- to 2.0.0-3.1)
  • Migration status for syncevolution (- to 2.0.0-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): syncevolution libsynthesis (not considered)
    • Depends: syncevolution libsynthesis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/syncevolution.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 353 days old (needed 5 days)
• pyzbar (- to 0.1.9-2)
  • Migration status for pyzbar (- to 0.1.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyzbar would introduce bugs in testing: #1080136
    • autopkgtest for pyzbar/0.1.9-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyzbar.html
    • 354 days old (needed 5 days)
• gnome-paint (- to 0.4.0-10)
  • Migration status for gnome-paint (- to 0.4.0-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-paint would introduce bugs in testing: #1075026
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-paint.html
    • 356 days old (needed 5 days)
• librem5-flash-image (- to 0.0.4-2)
  • Migration status for librem5-flash-image (- to 0.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating librem5-flash-image would introduce bugs in testing: #1085089
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 356 days old (needed 5 days)
• sambamba (- to 1.0.1+dfsg-2)
  • Migration status for sambamba (- to 1.0.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: sambamba -> libphobos2-ldc-shared106/1:1.36.0-2.1/amd64
    • Impossible Depends: sambamba -> libphobos2-ldc-shared106/1:1.36.0-2.1/arm64
    • Impossible Depends: sambamba -> libphobos2-ldc-shared106/1:1.36.0-2.1/riscv64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sambamba.html
    • autopkgtest for sambamba/1.0.1+dfsg-2: amd64: Pass, arm64: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 356 days old (needed 2 days)
• tcpxtract (- to 1.0.1-18)
  • Migration status for tcpxtract (- to 1.0.1-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tcpxtract would introduce bugs in testing: #1075557
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcpxtract.html
    • autopkgtest for tcpxtract/1.0.1-18: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 356 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
    • 359 days old (needed 5 days)
• kcemu (- to 0.5.2+dfsg-2)
  • Migration status for kcemu (- to 0.5.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kcemu would introduce bugs in testing: #1078231
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 360 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-moderngl-window pyrr (not considered)
    • Depends: python-moderngl-window pyrr (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 362 days old (needed 2 days)
• r-cran-rstanarm (- to 2.32.1-2)
  • Migration status for r-cran-rstanarm (- to 2.32.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-rstanarm would introduce bugs in testing: #1091239
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rstanarm.html
    • autopkgtest for r-cran-rstanarm/2.32.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 362 days old (needed 2 days)
• form (- to 4.3.1+git20240409+ds-2)
  • Migration status for form (- to 4.3.1+git20240409+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating form would introduce bugs in testing: #1091275
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/form.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 364 days old (needed 5 days)
• cython-legacy (- to 0.29.37-2)
  • Migration status for cython-legacy (- to 0.29.37-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cython3-legacy/amd64 has unsatisfiable dependency
    • cython3-legacy/arm64 has unsatisfiable dependency
    • cython3-legacy/armel has unsatisfiable dependency
    • cython3-legacy/armhf has unsatisfiable dependency
    • cython3-legacy/i386 has unsatisfiable dependency
    • cython3-legacy/mips64el has unsatisfiable dependency
    • cython3-legacy/ppc64el has unsatisfiable dependency
    • cython3-legacy/riscv64 has unsatisfiable dependency
    • cython3-legacy/s390x has unsatisfiable dependency
    • Updating cython-legacy would introduce bugs in testing: #1078460
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cython-legacy.html
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 365 days old (needed 5 days)
• ttyd (- to 1.7.7-2)
  • Migration status for ttyd (- to 1.7.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ttyd would introduce bugs in testing: #996042
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/ttyd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 365 days old (needed 5 days)
• python-xsdata (- to 24.1-1)
  • Migration status for python-xsdata (- to 24.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-xsdata/24.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xsdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 370 days old (needed 5 days)
• python-anndata (- to 0.10.6-1)
  • Migration status for python-anndata (- to 0.10.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-anndata would introduce bugs in testing: #1100261
    • autopkgtest for python-anndata/0.10.6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-anndata.html
    • Reproducible on amd64 - info ♻
    • 375 days old (needed 5 days)
• aplus-fsf (- to 4.22.1-13)
  • Migration status for aplus-fsf (- to 4.22.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aplus-fsf would introduce bugs in testing: #1067921, #1088380
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aplus-fsf.html
    • 376 days old (needed 5 days)
• oclgrind (- to 21.10-4)
  • Migration status for oclgrind (- to 21.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oclgrind would introduce bugs in testing: #1061215
    • Build-Depends(-Arch): oclgrind llvm-toolchain-14 (not considered)
    • Depends: oclgrind llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oclgrind.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 381 days old (needed 5 days)
• python-uflash (- to 1.2.4+dfsg-11)
  • Migration status for python-uflash (- to 1.2.4+dfsg-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-uflash firmware-microbit-micropython (not considered)
    • Depends: python-uflash firmware-microbit-micropython (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-uflash.html
    • autopkgtest for python-uflash/1.2.4+dfsg-11: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 382 days old (needed 2 days)
• glib-d (- to 2.4.3-2)
  • Migration status for glib-d (- to 2.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glib-d would introduce bugs in testing: #1101383
    • Impossible Depends: glib-d -> libphobos2-ldc-shared106/1:1.36.0-2.1/amd64
    • Impossible Depends: glib-d -> libphobos2-ldc-shared106/1:1.36.0-2.1/arm64
    • Impossible Depends: glib-d -> libphobos2-ldc-shared106/1:1.36.0-2.1/i386
    • Impossible Depends: glib-d -> libphobos2-ldc-shared106/1:1.36.0-2.1/riscv64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glib-d.html
    • New but not reproducible on armhf - info ♻
    • 384 days old (needed 5 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)
    • 386 days old (needed 5 days)
• calculix-ccx (- to 2.21-1)
  • Migration status for calculix-ccx (- to 2.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for calculix-ccx/2.21-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): calculix-ccx spooles (not considered)
    • Depends: calculix-ccx spooles (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calculix-ccx.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 388 days old (needed 5 days)
• sane-frontends (- to 1.0.14-18)
  • Migration status for sane-frontends (- to 1.0.14-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sane/amd64 has unsatisfiable dependency
    • sane/arm64 has unsatisfiable dependency
    • sane/armel has unsatisfiable dependency
    • sane/armhf has unsatisfiable dependency
    • sane/i386 has unsatisfiable dependency
    • sane/mips64el has unsatisfiable dependency
    • sane/ppc64el has unsatisfiable dependency
    • sane/riscv64 has unsatisfiable dependency
    • sane/s390x has unsatisfiable dependency
    • Updating sane-frontends would introduce bugs in testing: #1088081
    • sane-frontends unsatisfiable Build-Depends(-Arch) on amd64: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on arm64: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on armel: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on armhf: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on i386: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on mips64el: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on ppc64el: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on riscv64: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on s390x: libgimp2.0-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sane-frontends.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 389 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
    • 394 days old (needed 5 days)
• clippoly (- to 0.11-11)
  • Migration status for clippoly (- to 0.11-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clippoly would introduce bugs in testing: #976540
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clippoly.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• libapache2-mod-python (- to 3.5.0.1-3)
  • Migration status for libapache2-mod-python (- to 3.5.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libapache2-mod-python/amd64 has unsatisfiable dependency
    • libapache2-mod-python/arm64 has unsatisfiable dependency
    • libapache2-mod-python/armel has unsatisfiable dependency
    • libapache2-mod-python/armhf has unsatisfiable dependency
    • libapache2-mod-python/i386 has unsatisfiable dependency
    • libapache2-mod-python/mips64el has unsatisfiable dependency
    • libapache2-mod-python/ppc64el has unsatisfiable dependency
    • libapache2-mod-python/riscv64 has unsatisfiable dependency
    • libapache2-mod-python/s390x has unsatisfiable dependency
    • Updating libapache2-mod-python would introduce bugs in testing: #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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 396 days old (needed 5 days)
• ohai (- to 18.1.3-2.1)
  • Migration status for ohai (- to 18.1.3-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ohai ruby-chef-config (not considered)
    • Depends: ohai ruby-chef-config (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ohai.html
    • autopkgtest for ohai/18.1.3-2.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 396 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 397 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdepend.html
    • Reproducible on armhf - info ♻
    • 397 days old (needed 5 days)
• phpcpd (- to 6.0.3-3)
  • Migration status for phpcpd (- to 6.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phpcpd/amd64 has unsatisfiable dependency
    • phpcpd/arm64 has unsatisfiable dependency
    • Updating phpcpd would introduce bugs in testing: #1070618
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpcpd.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 397 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): phpmd pdepend (not considered)
    • Depends: phpmd pdepend (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpmd.html
    • Reproducible on armhf - info ♻
    • 397 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 ♻
    • 403 days old (needed 5 days)
• ldapjdk (- to 5.5.0+dfsg1-1)
  • Migration status for ldapjdk (- to 5.5.0+dfsg1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: ldapjdk jss (not considered)
    • Depends: ldapjdk jss (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldapjdk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 403 days old (needed 5 days)
• openvr (- to 1.23.7~ds1-2.1)
  • Migration status for openvr (- to 1.23.7~ds1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openvr would introduce bugs in testing: #1067724
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 403 days old (needed 5 days)
• palabos (- to 1.5~r1+repack1-5.1)
  • Migration status for palabos (- to 1.5~r1+repack1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for palabos/1.5~r1+repack1-5.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/palabos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 403 days old (needed 5 days)
• s2geometry (- to 0.10.0-6.1)
  • Migration status for s2geometry (- to 0.10.0-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libs2-0t64/amd64 has unsatisfiable dependency
    • python3-pywraps2/amd64 has unsatisfiable dependency
    • libs2-0t64/arm64 has unsatisfiable dependency
    • python3-pywraps2/arm64 has unsatisfiable dependency
    • libs2-0t64/armel has unsatisfiable dependency
    • python3-pywraps2/armel has unsatisfiable dependency
    • libs2-0t64/armhf has unsatisfiable dependency
    • python3-pywraps2/armhf has unsatisfiable dependency
    • libs2-0t64/i386 has unsatisfiable dependency
    • python3-pywraps2/i386 has unsatisfiable dependency
    • libs2-0t64/mips64el has unsatisfiable dependency
    • python3-pywraps2/mips64el has unsatisfiable dependency
    • libs2-0t64/ppc64el has unsatisfiable dependency
    • python3-pywraps2/ppc64el has unsatisfiable dependency
    • libs2-0t64/riscv64 has unsatisfiable dependency
    • python3-pywraps2/riscv64 has unsatisfiable dependency
    • libs2-0t64/s390x has unsatisfiable dependency
    • python3-pywraps2/s390x has unsatisfiable dependency
    • Updating s2geometry would introduce bugs in testing: #1059228
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/s2geometry.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 403 days old (needed 5 days)
• shapetools (- to 1.4pl6-16.1)
  • Migration status for shapetools (- to 1.4pl6-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shapetools would introduce bugs in testing: #1075506
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shapetools.html
    • 403 days old (needed 5 days)
• sphde (- to 1.4.0-5.1)
  • Migration status for sphde (- to 1.4.0-5.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphde.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 403 days old (needed 5 days)
• spooles (- to 2.2-14.1)
  • Migration status for spooles (- to 2.2-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libspooles2.2t64/amd64 has unsatisfiable dependency
    • libspooles2.2t64/arm64 has unsatisfiable dependency
    • libspooles2.2t64/mips64el has unsatisfiable dependency
    • libspooles2.2t64/ppc64el has unsatisfiable dependency
    • libspooles2.2t64/riscv64 has unsatisfiable dependency
    • libspooles2.2t64/s390x has unsatisfiable dependency
    • Updating spooles would introduce bugs in testing: #1075534
    • autopkgtest for spooles/2.2-14.1: armel: Pass, armhf: Pass, i386: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spooles.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 403 days old (needed 5 days)
• termrec (- to 0.19-2.1)
  • Migration status for termrec (- to 0.19-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating termrec would introduce bugs in testing: #1065906
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termrec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 403 days old (needed 5 days)
• android-platform-frameworks-native (- to 1:10.0.0+r36-1.2)
  • Migration status for android-platform-frameworks-native (- to 1:10.0.0+r36-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-frameworks-native would introduce bugs in testing: #1062267
    • autopkgtest for android-platform-frameworks-native/1:10.0.0+r36-1.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-frameworks-native.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 404 days old (needed 5 days)
• grok (- to 1.20110708.1-7.1)
  • Migration status for grok (- to 1.20110708.1-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • grok/amd64 has unsatisfiable dependency
    • libgrok1t64/amd64 has unsatisfiable dependency
    • grok/arm64 has unsatisfiable dependency
    • libgrok1t64/arm64 has unsatisfiable dependency
    • grok/i386 has unsatisfiable dependency
    • libgrok1t64/i386 has unsatisfiable dependency
    • grok/mips64el has unsatisfiable dependency
    • libgrok1t64/mips64el has unsatisfiable dependency
    • grok/ppc64el has unsatisfiable dependency
    • libgrok1t64/ppc64el has unsatisfiable dependency
    • grok/riscv64 has unsatisfiable dependency
    • libgrok1t64/riscv64 has unsatisfiable dependency
    • grok/s390x has unsatisfiable dependency
    • libgrok1t64/s390x has unsatisfiable dependency
    • Updating grok would introduce bugs in testing: #1000065, #1065556
    • grok unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grok.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 404 days old (needed 5 days)
• libapr-memcache (- to 0.7.0-3.1)
  • Migration status for libapr-memcache (- to 0.7.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapr-memcache would introduce bugs in testing: #1075144
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapr-memcache.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 404 days old (needed 5 days)
• libkqueue (- to 2.3.1-1.1)
  • Migration status for libkqueue (- to 2.3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libkqueue would introduce bugs in testing: #955260
    • autopkgtest for libkqueue/2.3.1-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkqueue.html
    • Reproducible on arm64 - info ♻
    • 404 days old (needed 5 days)
• libonvif (- to 1.4.4-1.1)
  • Migration status for libonvif (- to 1.4.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libonvif1t64/amd64 has unsatisfiable dependency
    • libonvif1t64/arm64 has unsatisfiable dependency
    • libonvif1t64/armel has unsatisfiable dependency
    • libonvif1t64/armhf has unsatisfiable dependency
    • libonvif1t64/i386 has unsatisfiable dependency
    • libonvif1t64/mips64el has unsatisfiable dependency
    • libonvif1t64/ppc64el has unsatisfiable dependency
    • libonvif1t64/riscv64 has unsatisfiable dependency
    • libonvif1t64/s390x has unsatisfiable dependency
    • Updating libonvif would introduce bugs in testing: #1072430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libonvif.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 404 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
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 404 days old (needed 5 days)
• libpwiz (- to 3.0.18342-4.1)
  • Migration status for libpwiz (- to 3.0.18342-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpwiz would introduce bugs in testing: #1075199
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpwiz.html
    • 404 days old (needed 5 days)
• libsnl (- to 0.2.1.svn.18-1.2)
  • Migration status for libsnl (- to 0.2.1.svn.18-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsnl would introduce bugs in testing: #1074861
    • autopkgtest for libsnl/0.2.1.svn.18-1.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsnl.html
    • 404 days old (needed 5 days)
• libsynthesis (- to 3.4.0.47.5+syncevolution-1.5.3-1.2)
  • Migration status for libsynthesis (- to 3.4.0.47.5+syncevolution-1.5.3-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsynthesis0t64/amd64 has unsatisfiable dependency
    • libsynthesis0t64/arm64 has unsatisfiable dependency
    • libsynthesis0t64/armel has unsatisfiable dependency
    • libsynthesis0t64/armhf has unsatisfiable dependency
    • libsynthesis0t64/i386 has unsatisfiable dependency
    • libsynthesis0t64/mips64el has unsatisfiable dependency
    • libsynthesis0t64/ppc64el has unsatisfiable dependency
    • libsynthesis0t64/riscv64 has unsatisfiable dependency
    • libsynthesis0t64/s390x has unsatisfiable dependency
    • Updating libsynthesis would introduce bugs in testing: #1000047
    • libsynthesis unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsynthesis.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 404 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/armel has unsatisfiable dependency
    • libt3widget2t64/armel 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/mips64el has unsatisfiable dependency
    • libt3widget2t64/mips64el 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
    • 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 armel: 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 mips64el: 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 404 days old (needed 5 days)
• llvmlite (- to 0.42.0-1)
  • Migration status for llvmlite (- to 0.42.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating llvmlite would introduce bugs in testing: #1061214
    • Build-Depends(-Arch): llvmlite llvm-toolchain-14 (not considered)
    • Depends: llvmlite llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvmlite.html
    • autopkgtest for llvmlite/0.42.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 404 days old (needed 2 days)
• mongo-cxx-driver-legacy (- to 1.1.3-3.3)
  • Migration status for mongo-cxx-driver-legacy (- to 1.1.3-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mongo-cxx-driver-legacy would introduce bugs in testing: #1065905
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on arm64: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on armel: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on armhf: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on i386: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on mips64el: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on ppc64el: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on riscv64: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on s390x: python3-distutils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongo-cxx-driver-legacy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 404 days old (needed 5 days)
• mrtdreader (- to 0.1.6-3.1)
  • Migration status for mrtdreader (- to 0.1.6-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mrtdreader would introduce bugs in testing: #1066260
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for mrtdreader/0.1.6-3.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrtdreader.html
    • 404 days old (needed 5 days)
• ndpi (- to 4.2-2.1)
  • Migration status for ndpi (- to 4.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ndpi would introduce bugs in testing: #1082040
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ndpi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 404 days old (needed 5 days)
• ogre-1.9 (- to 1.9.0+dfsg1-14.1)
  • Migration status for ogre-1.9 (- to 1.9.0+dfsg1-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ogre-1.9 would introduce bugs in testing: #1024182
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogre-1.9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 404 days old (needed 5 days)
• opendht (- to 3.0.1-1.1)
  • Migration status for opendht (- to 3.0.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opendht would introduce bugs in testing: #1087610
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opendht.html
    • autopkgtest for opendht/3.0.1-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 404 days old (needed 2 days)
• xbase64 (- to 3.1.2-14.1)
  • Migration status for xbase64 (- to 3.1.2-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libxbase64-bin/armel has unsatisfiable dependency
    • libxbase64-bin/armhf has unsatisfiable dependency
    • Updating xbase64 would introduce bugs in testing: #1069340
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xbase64.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 404 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
    • autopkgtest for ygl/4.2e-6.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ygl.html
    • 404 days old (needed 5 days)
• armnn (- to 23.08-4.1)
  • Migration status for armnn (- to 23.08-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pyarmnn/amd64 has unsatisfiable dependency
    • python3-pyarmnn/arm64 has unsatisfiable dependency
    • python3-pyarmnn/armhf has unsatisfiable dependency
    • python3-pyarmnn/i386 has unsatisfiable dependency
    • python3-pyarmnn/mips64el has unsatisfiable dependency
    • python3-pyarmnn/ppc64el has unsatisfiable dependency
    • Updating armnn would introduce bugs in testing: #1074820
    • Impossible Depends: armnn -> libarm-compute32t64/23.08+dfsg-3.1/arm64
    • Impossible Depends: armnn -> libarm-compute32t64/23.08+dfsg-3.1/armhf
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/armnn.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 405 days old (needed 5 days)
• brial (- to 1.2.12-1.1)
  • Migration status for brial (- to 1.2.12-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-brial/riscv64 has unsatisfiable dependency
    • Updating brial would introduce bugs in testing: #1080888, #1093321
    • autopkgtest for brial/1.2.12-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/brial.html
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 405 days old (needed 5 days)
• cvm (- to 0.97-3.1)
  • Migration status for cvm (- to 0.97-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cvm would introduce bugs in testing: #1074896
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvm.html
    • 405 days old (needed 5 days)
• daq (- to 2.0.7-5.1)
  • Migration status for daq (- to 2.0.7-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating daq would introduce bugs in testing: #1074902
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/daq.html
    • 405 days old (needed 5 days)
• dyssol (- to 1.1.1+ds1-2.1)
  • Migration status for dyssol (- to 1.1.1+ds1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dyssol/amd64 has unsatisfiable dependency
    • dyssol-gui/amd64 has unsatisfiable dependency
    • libdyssol1.0t64/amd64 has unsatisfiable dependency
    • dyssol/arm64 has unsatisfiable dependency
    • dyssol-gui/arm64 has unsatisfiable dependency
    • libdyssol1.0t64/arm64 has unsatisfiable dependency
    • dyssol/armel has unsatisfiable dependency
    • dyssol-gui/armel has unsatisfiable dependency
    • libdyssol1.0t64/armel has unsatisfiable dependency
    • dyssol/armhf has unsatisfiable dependency
    • dyssol-gui/armhf has unsatisfiable dependency
    • libdyssol1.0t64/armhf has unsatisfiable dependency
    • dyssol/i386 has unsatisfiable dependency
    • dyssol-gui/i386 has unsatisfiable dependency
    • libdyssol1.0t64/i386 has unsatisfiable dependency
    • dyssol/mips64el has unsatisfiable dependency
    • dyssol-gui/mips64el has unsatisfiable dependency
    • libdyssol1.0t64/mips64el has unsatisfiable dependency
    • dyssol/ppc64el has unsatisfiable dependency
    • dyssol-gui/ppc64el has unsatisfiable dependency
    • libdyssol1.0t64/ppc64el has unsatisfiable dependency
    • dyssol/riscv64 has unsatisfiable dependency
    • dyssol-gui/riscv64 has unsatisfiable dependency
    • libdyssol1.0t64/riscv64 has unsatisfiable dependency
    • dyssol/s390x has unsatisfiable dependency
    • dyssol-gui/s390x has unsatisfiable dependency
    • libdyssol1.0t64/s390x has unsatisfiable dependency
    • Updating dyssol would introduce bugs in testing: #1082562
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dyssol.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 405 days old (needed 5 days)
• forge (- to 1.0.1-3.1)
  • Migration status for forge (- to 1.0.1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libforge1t64/amd64 has unsatisfiable dependency
    • libforge1t64/arm64 has unsatisfiable dependency
    • libforge1t64/armel has unsatisfiable dependency
    • libforge1t64/armhf has unsatisfiable dependency
    • libforge1t64/i386 has unsatisfiable dependency
    • libforge1t64/mips64el has unsatisfiable dependency
    • libforge1t64/ppc64el has unsatisfiable dependency
    • libforge1t64/riscv64 has unsatisfiable dependency
    • libforge1t64/s390x has unsatisfiable dependency
    • Updating forge would introduce bugs in testing: #1090222
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forge.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 405 days old (needed 5 days)
• hepmc3 (- to 3.1.2-2.1)
  • Migration status for hepmc3 (- to 3.1.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hepmc3 would introduce bugs in testing: #1064556
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hepmc3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 405 days old (needed 5 days)
• libghemical (- to 3.0.0-4.4)
  • Migration status for libghemical (- to 3.0.0-4.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghemical5t64/amd64 has unsatisfiable dependency
    • libghemical5t64/arm64 has unsatisfiable dependency
    • libghemical5t64/i386 has unsatisfiable dependency
    • libghemical5t64/mips64el has unsatisfiable dependency
    • libghemical5t64/ppc64el has unsatisfiable dependency
    • libghemical5t64/riscv64 has unsatisfiable dependency
    • libghemical5t64/s390x has unsatisfiable dependency
    • Updating libghemical would introduce bugs in testing: #1086282
    • Build-Depends(-Arch): libghemical mpqc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libghemical.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 405 days old (needed 5 days)
• tlog (- to 14-1)
  • Migration status for tlog (- to 14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libtlog0/armel has unsatisfiable dependency
    • libtlog0/armhf has unsatisfiable dependency
    • Updating tlog would introduce bugs in testing: #1067828
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tlog.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 405 days old (needed 5 days)
• ukui-session-manager (- to 4.0.0.1-1)
  • Migration status for ukui-session-manager (- to 4.0.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ukui-session-manager would introduce bugs in testing: #1089800
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-session-manager.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 406 days old (needed 5 days)
• ruby-riddle (- to 2.4.3-1)
  • Migration status for ruby-riddle (- to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-riddle would introduce bugs in testing: #1033369
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-riddle.html
    • autopkgtest for ruby-riddle/2.4.3-1: amd64: Pass, arm64: Pass, armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 410 days old (needed 5 days)
• ruby-grape (- to 2.0.0-3)
  • Migration status for ruby-grape (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-grape would introduce bugs in testing: #1091659
    • autopkgtest for ruby-grape/2.0.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-grape.html
    • Reproducible on armhf - info ♻
    • 411 days old (needed 5 days)
• mir-core (- to 1.7.0-1)
  • Migration status for mir-core (- to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: mir-core -> libphobos2-ldc-shared106/1:1.36.0-2.1/amd64
    • Impossible Depends: mir-core -> libphobos2-ldc-shared106/1:1.36.0-2.1/arm64
    • Impossible Depends: mir-core -> libphobos2-ldc-shared106/1:1.36.0-2.1/i386
    • Impossible Depends: mir-core -> libphobos2-ldc-shared106/1:1.36.0-2.1/riscv64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mir-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• siconos (- to 4.4.0+dfsg-4)
  • Migration status for siconos (- to 4.4.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsiconos-numerics7/amd64 has unsatisfiable dependency
    • python3-siconos/amd64 has unsatisfiable dependency
    • libsiconos-numerics7/arm64 has unsatisfiable dependency
    • python3-siconos/arm64 has unsatisfiable dependency
    • libsiconos-numerics7/ppc64el has unsatisfiable dependency
    • python3-siconos/ppc64el has unsatisfiable dependency
    • libsiconos-numerics7/riscv64 has unsatisfiable dependency
    • python3-siconos/riscv64 has unsatisfiable dependency
    • Updating siconos would introduce bugs in testing: #1066316
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/siconos.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 412 days old (needed 5 days)
• q2-feature-classifier (- to 2024.2.0-1)
  • Migration status for q2-feature-classifier (- to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-feature-classifier would introduce bugs in testing: #1071882
    • autopkgtest for q2-feature-classifier/2024.2.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-feature-classifier q2-feature-table (not considered)
    • Build-Depends(-Arch): q2-feature-classifier q2-quality-control (not considered)
    • Build-Depends(-Arch): q2-feature-classifier q2-taxa
    • Build-Depends(-Arch): q2-feature-classifier q2-types (not considered)
    • Build-Depends(-Arch): q2-feature-classifier qiime (not considered)
    • Depends: q2-feature-classifier q2-feature-table (not considered)
    • Depends: q2-feature-classifier q2-quality-control (not considered)
    • Depends: q2-feature-classifier q2-taxa
    • Depends: q2-feature-classifier q2-types (not considered)
    • Depends: q2-feature-classifier qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-feature-classifier.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 414 days old (needed 5 days)
• ruby-grape-path-helpers (- to 2.0.1-2)
  • Migration status for ruby-grape-path-helpers (- to 2.0.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-grape-path-helpers ruby-grape (not considered)
    • Depends: ruby-grape-path-helpers ruby-grape (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-grape-path-helpers.html
    • autopkgtest for ruby-grape-path-helpers/2.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 414 days old (needed 2 days)
• triton (- to 2.0.0.post1-4)
  • Migration status for triton (- to 2.0.0.post1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating triton would introduce bugs in testing: #1061219, #1067839
    • Build-Depends(-Arch): triton llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/triton.html
    • autopkgtest for triton/2.0.0.post1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 415 days old (needed 2 days)
• python-certbot-dns-dnsimple (- to 2.9.0-1)
  • Migration status for python-certbot-dns-dnsimple (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-dnsimple lexicon (not considered)
    • Depends: python-certbot-dns-dnsimple lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-dnsimple.html
    • autopkgtest for python-certbot-dns-dnsimple/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 416 days old (needed 5 days)
• python-certbot-dns-gehirn (- to 2.9.0-1)
  • Migration status for python-certbot-dns-gehirn (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-gehirn lexicon (not considered)
    • Depends: python-certbot-dns-gehirn lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-gehirn.html
    • autopkgtest for python-certbot-dns-gehirn/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 416 days old (needed 5 days)
• python-certbot-dns-linode (- to 2.9.0-1)
  • Migration status for python-certbot-dns-linode (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-linode lexicon (not considered)
    • Depends: python-certbot-dns-linode lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-linode.html
    • autopkgtest for python-certbot-dns-linode/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 416 days old (needed 5 days)
• python-certbot-dns-ovh (- to 2.9.0-1)
  • Migration status for python-certbot-dns-ovh (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-ovh lexicon (not considered)
    • Depends: python-certbot-dns-ovh lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-ovh.html
    • autopkgtest for python-certbot-dns-ovh/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 416 days old (needed 5 days)
• python-certbot-dns-sakuracloud (- to 2.9.0-1)
  • Migration status for python-certbot-dns-sakuracloud (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-sakuracloud lexicon (not considered)
    • Depends: python-certbot-dns-sakuracloud lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-sakuracloud.html
    • autopkgtest for python-certbot-dns-sakuracloud/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 416 days old (needed 5 days)
• lexicon (- to 3.17.0-1)
  • Migration status for lexicon (- to 3.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lexicon would introduce bugs in testing: #1076826
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lexicon.html
    • autopkgtest for lexicon/3.17.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 418 days old (needed 5 days)
• octave-arduino (- to 0.12.1-2)
  • Migration status for octave-arduino (- to 0.12.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: octave-arduino arduino (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-arduino.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for octave-arduino/0.12.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 419 days old (needed 5 days)
• prody (- to 2.4.1+dfsg-2)
  • Migration status for prody (- to 2.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-prody/amd64 has unsatisfiable dependency
    • python3-prody/arm64 has unsatisfiable dependency
    • python3-prody/armel has unsatisfiable dependency
    • python3-prody/armhf has unsatisfiable dependency
    • python3-prody/mips64el has unsatisfiable dependency
    • python3-prody/ppc64el has unsatisfiable dependency
    • python3-prody/riscv64 has unsatisfiable dependency
    • Updating prody would introduce bugs in testing: #1058454, #1071807
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/prody.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • 420 days old (needed 5 days)
• ruby-rails-assets-markdown-it-diaspora-mention (- to 1.2.0-3)
  • Migration status for ruby-rails-assets-markdown-it-diaspora-mention (- to 1.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-markdown-it-diaspora-mention would introduce bugs in testing: #1092700
    • autopkgtest for ruby-rails-assets-markdown-it-diaspora-mention/1.2.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-markdown-it-diaspora-mention.html
    • Reproducible on armhf - info ♻
    • 423 days old (needed 5 days)
• ruby-rails-assets-underscore (- to 1.8.3+dfsg-5)
  • Migration status for ruby-rails-assets-underscore (- to 1.8.3+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-underscore would introduce bugs in testing: #1091737, #1092701
    • autopkgtest for ruby-rails-assets-underscore/1.8.3+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-underscore.html
    • Reproducible on armhf - info ♻
    • 423 days old (needed 5 days)
• python-feather-format (- to 0.3.1+dfsg1-8)
  • Migration status for python-feather-format (- to 0.3.1+dfsg1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-feather-format/amd64 has unsatisfiable dependency
    • python3-feather-format/arm64 has unsatisfiable dependency
    • python3-feather-format/armel has unsatisfiable dependency
    • python3-feather-format/armhf has unsatisfiable dependency
    • python3-feather-format/i386 has unsatisfiable dependency
    • python3-feather-format/mips64el has unsatisfiable dependency
    • python3-feather-format/ppc64el has unsatisfiable dependency
    • python3-feather-format/riscv64 has unsatisfiable dependency
    • python3-feather-format/s390x has unsatisfiable dependency
    • Updating python-feather-format would introduce bugs in testing: #1090271, #1092784
    • Build-Depends(-Arch): python-feather-format cython-legacy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-feather-format.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 424 days old (needed 5 days)
• ruby-mmap2 (- to 2.2.9-1)
  • Migration status for ruby-mmap2 (- to 2.2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-mmap2 would introduce bugs in testing: #1075466
    • autopkgtest for ruby-mmap2/2.2.9-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: ruby-mmap2 ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-mmap2.html
    • 426 days old (needed 5 days)
• ruby-redis-actionpack (- to 5.4.0-1)
  • Migration status for ruby-redis-actionpack (- to 5.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-actionpack would introduce bugs in testing: #1095384
    • autopkgtest for ruby-redis-actionpack/5.4.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-redis-actionpack ruby-redis-rack (not considered)
    • Depends: ruby-redis-actionpack ruby-redis-rack (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-actionpack.html
    • Reproducible on armhf - info ♻
    • 426 days old (needed 5 days)
• django-simple-redis-admin (- to 1.4.0-4)
  • Migration status for django-simple-redis-admin (- to 1.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-simple-redis-admin would introduce bugs in testing: #1072858
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-simple-redis-admin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 427 days old (needed 5 days)
• abinit (- to 9.10.4-3)
  • Migration status for abinit (- to 9.10.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating abinit would introduce bugs in testing: #1076027, #1089281
    • autopkgtest for abinit/9.10.4-3: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abinit.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 428 days old (needed 5 days)
• giada (- to 0.22.0-4)
  • Migration status for giada (- to 0.22.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • giada/amd64 has unsatisfiable dependency
    • giada/arm64 has unsatisfiable dependency
    • giada/armhf has unsatisfiable dependency
    • giada/i386 has unsatisfiable dependency
    • giada/mips64el has unsatisfiable dependency
    • giada/ppc64el has unsatisfiable dependency
    • giada/riscv64 has unsatisfiable dependency
    • giada/s390x has unsatisfiable dependency
    • Updating giada would introduce bugs in testing: #1073997
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/giada.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 428 days old (needed 5 days)
• rss-glx (- to 0.9.1-6.5)
  • Migration status for rss-glx (- to 0.9.1-6.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rss-glx/amd64 has unsatisfiable dependency
    • rss-glx/arm64 has unsatisfiable dependency
    • rss-glx/armel has unsatisfiable dependency
    • rss-glx/armhf has unsatisfiable dependency
    • rss-glx/i386 has unsatisfiable dependency
    • rss-glx/mips64el has unsatisfiable dependency
    • rss-glx/ppc64el has unsatisfiable dependency
    • rss-glx/riscv64 has unsatisfiable dependency
    • rss-glx/s390x has unsatisfiable dependency
    • Updating rss-glx would introduce bugs in testing: #1079338
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rss-glx.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 429 days old (needed 5 days)
• python-lsp-ruff (- to 1.5.3-2)
  • Migration status for python-lsp-ruff (- to 1.5.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-lsp-ruff/1.5.3-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lsp-ruff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 430 days old (needed 5 days)
• dt-schema (- to 2023.11-3)
  • Migration status for dt-schema (- to 2023.11-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dt-schema would introduce bugs in testing: #1063562
    • autopkgtest for dt-schema/2023.11-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dt-schema.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 435 days old (needed 5 days)
• asterisk-espeak (- to 5.0~1-4)
  • Migration status for asterisk-espeak (- to 5.0~1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for asterisk-espeak/5.0~1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): asterisk-espeak asterisk (not considered)
    • Depends: asterisk-espeak asterisk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-espeak.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 437 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 437 days old (needed 5 days)
• wine-development (- to 8.21~repack-1)
  • Migration status for wine-development (- to 8.21~repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wine-development would introduce bugs in testing: #1069318, #988246
    • wine-development unsatisfiable Build-Depends(-Arch) on amd64: unicode-idna (<< 16)
    • wine-development unsatisfiable Build-Depends(-Arch) on arm64: unicode-idna (<< 16)
    • wine-development unsatisfiable Build-Depends(-Arch) on armel: unicode-idna (<< 16)
    • wine-development unsatisfiable Build-Depends(-Arch) on armhf: unicode-idna (<< 16)
    • wine-development unsatisfiable Build-Depends(-Arch) on i386: unicode-idna (<< 16)
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine-development.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 437 days old (needed 5 days)
• pmacct (- to 1.7.8-2)
  • Migration status for pmacct (- to 1.7.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pmacct ndpi (not considered)
    • Depends: pmacct ndpi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmacct.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 438 days old (needed 5 days)
• calculix-cgx (- to 2.21+dfsg-1)
  • Migration status for calculix-cgx (- to 2.21+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating calculix-cgx would introduce bugs in testing: #1077425
    • Build-Depends(-Arch): calculix-cgx libsnl (not considered)
    • Depends: calculix-cgx libsnl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calculix-cgx.html
    • autopkgtest for calculix-cgx/2.21+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 442 days old (needed 2 days)
• mlpy (- to 3.5.0+ds-3)
  • Migration status for mlpy (- to 3.5.0+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mlpy-lib/amd64 has unsatisfiable dependency
    • python3-mlpy-lib/arm64 has unsatisfiable dependency
    • python3-mlpy-lib/armel has unsatisfiable dependency
    • python3-mlpy-lib/armhf has unsatisfiable dependency
    • python3-mlpy-lib/i386 has unsatisfiable dependency
    • python3-mlpy-lib/mips64el has unsatisfiable dependency
    • python3-mlpy-lib/ppc64el has unsatisfiable dependency
    • python3-mlpy-lib/riscv64 has unsatisfiable dependency
    • python3-mlpy-lib/s390x has unsatisfiable dependency
    • Updating mlpy would introduce bugs in testing: #1075279, #1092779
    • Build-Depends(-Arch): mlpy cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mlpy.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 442 days old (needed 5 days)
• pybj (- to 0.2.6-2)
  • Migration status for pybj (- to 0.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-bjdata/amd64 has unsatisfiable dependency
    • python3-bjdata/arm64 has unsatisfiable dependency
    • python3-bjdata/armel has unsatisfiable dependency
    • python3-bjdata/armhf has unsatisfiable dependency
    • python3-bjdata/i386 has unsatisfiable dependency
    • python3-bjdata/mips64el 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 442 days old (needed 5 days)
• python-refurb (- to 1.27.0-1)
  • Migration status for python-refurb (- to 1.27.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-refurb would introduce bugs in testing: #1077460
    • autopkgtest for python-refurb/1.27.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-refurb.html
    • 442 days old (needed 5 days)
• elvis-tiny (- to 1.4-24.2)
  • Migration status for elvis-tiny (- to 1.4-24.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating elvis-tiny would introduce bugs in testing: #1074934
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elvis-tiny.html
    • 444 days old (needed 5 days)
• pypdf2 (- to 2.12.1-4)
  • Migration status for pypdf2 (- to 2.12.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pypdf2 would introduce bugs in testing: #1061162, #1066762
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pypdf2.html
    • 444 days old (needed 5 days)
• cypari2 (- to 2.1.4-1)
  • Migration status for cypari2 (- to 2.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-cypari2/amd64 has unsatisfiable dependency
    • python3-cypari2/arm64 has unsatisfiable dependency
    • python3-cypari2/armel has unsatisfiable dependency
    • python3-cypari2/armhf has unsatisfiable dependency
    • python3-cypari2/i386 has unsatisfiable dependency
    • python3-cypari2/mips64el has unsatisfiable dependency
    • python3-cypari2/ppc64el has unsatisfiable dependency
    • python3-cypari2/riscv64 has unsatisfiable dependency
    • python3-cypari2/s390x has unsatisfiable dependency
    • Updating cypari2 would introduce bugs in testing: #1081687
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cypari2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • 445 days old (needed 5 days)
• r-cran-bigmemory (- to 4.6.4-1)
  • Migration status for r-cran-bigmemory (- to 4.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-bigmemory would introduce bugs in testing: #1064135
    • autopkgtest for r-cran-bigmemory/4.6.4-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bigmemory.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 447 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
    • 450 days old (needed 5 days)
• awesfx (- to 0.5.2-1.1)
  • Migration status for awesfx (- to 0.5.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating awesfx would introduce bugs in testing: #1074831
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/awesfx.html
    • 451 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
    • 451 days old (needed 5 days)
• sfwbar (- to 1.0~beta13-1)
  • Migration status for sfwbar (- to 1.0~beta13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sfwbar would introduce bugs in testing: #1091451
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfwbar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 451 days old (needed 5 days)
• pybik (- to 3.0-6)
  • Migration status for pybik (- to 3.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pybik-bin/amd64 has unsatisfiable dependency
    • pybik-bin/arm64 has unsatisfiable dependency
    • pybik-bin/armel has unsatisfiable dependency
    • pybik-bin/armhf has unsatisfiable dependency
    • pybik-bin/i386 has unsatisfiable dependency
    • pybik-bin/mips64el has unsatisfiable dependency
    • pybik-bin/ppc64el has unsatisfiable dependency
    • pybik-bin/riscv64 has unsatisfiable dependency
    • pybik-bin/s390x has unsatisfiable dependency
    • Updating pybik would introduce bugs in testing: #1080864, #1087643, #1092780
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pybik.html
    • Build-Depends(-Arch): pybik cython-legacy (not considered)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 453 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-alreadyloggedin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 454 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
    • 454 days old (needed 5 days)
• r-cran-tikzdevice (- to 0.12.6-1)
  • Migration status for r-cran-tikzdevice (- to 0.12.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-tikzdevice r-cran-filehash (not considered)
    • Depends: r-cran-tikzdevice r-cran-filehash (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tikzdevice.html
    • autopkgtest for r-cran-tikzdevice/0.12.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 455 days old (needed 2 days)
• pysph (- to 1.0~b1-8)
  • Migration status for pysph (- to 1.0~b1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pysph/amd64 has unsatisfiable dependency
    • python3-pysph/arm64 has unsatisfiable dependency
    • Updating pysph would introduce bugs in testing: #1084148
    • Build-Depends(-Arch): pysph mayavi2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysph.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 456 days old (needed 5 days)
• python-loompy (- to 3.0.7+dfsg-3)
  • Migration status for python-loompy (- to 3.0.7+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-loompy would introduce bugs in testing: #1090279
    • autopkgtest for python-loompy/3.0.7+dfsg-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-loompy numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-loompy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 457 days old (needed 5 days)
• apt-verify (- to 2.0-1)
  • Migration status for apt-verify (- to 2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-verify would introduce bugs in testing: #1061185
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/apt-verify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 458 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/civicrm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 459 days old (needed 5 days)
• codraft (- to 2.2.1-3)
  • Migration status for codraft (- to 2.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating codraft would introduce bugs in testing: #1064714
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/codraft.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for codraft/2.2.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 459 days old (needed 2 days)
• intake (- to 0.6.6-3)
  • Migration status for intake (- to 0.6.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intake would introduce bugs in testing: #1063953, #1064752
    • autopkgtest for intake/0.6.6-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): intake appdirs (not considered)
    • Depends: intake appdirs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intake.html
    • 459 days old (needed 5 days)
• ruby-devise (- to 4.9.3-1)
  • Migration status for ruby-devise (- to 4.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-devise would introduce bugs in testing: #1095881
    • autopkgtest for ruby-devise/4.9.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-devise ruby-responders (not considered)
    • Build-Depends(-Arch): ruby-devise ruby-warden (not considered)
    • Depends: ruby-devise ruby-responders (not considered)
    • Depends: ruby-devise ruby-warden (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-devise.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 461 days old (needed 5 days)
• einsteinpy (- to 0.4.0-3)
  • Migration status for einsteinpy (- to 0.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating einsteinpy would introduce bugs in testing: #1063527
    • autopkgtest for einsteinpy/0.4.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/einsteinpy.html
    • 462 days old (needed 5 days)
• concurrent-log-handler (- to 0.9.25-1)
  • Migration status for concurrent-log-handler (- to 0.9.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating concurrent-log-handler would introduce bugs in testing: #1071301
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/concurrent-log-handler.html
    • 464 days old (needed 5 days)
• yash (- to 2.55-2)
  • Migration status for yash (- to 2.55-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yash would introduce bugs in testing: #1086620
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yash.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 466 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
  • 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
    • 469 days old (needed 5 days)
• mate-hud (- to 22.10.3-2)
  • Migration status for mate-hud (- to 22.10.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mate-hud vala-panel-appmenu (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-hud.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 469 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
    • Build-Depends(-Arch): aseba qtwebkit-opensource-src (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aseba.html
    • 473 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
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 474 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)
    • 476 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
    • 476 days old (needed 5 days)
• apper (- to 1.0.0-5)
  • Migration status for apper (- to 1.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • apper/amd64 has unsatisfiable dependency
    • apper/arm64 has unsatisfiable dependency
    • apper/armel has unsatisfiable dependency
    • apper/armhf has unsatisfiable dependency
    • apper/i386 has unsatisfiable dependency
    • apper/mips64el has unsatisfiable dependency
    • apper/ppc64el has unsatisfiable dependency
    • apper/riscv64 has unsatisfiable dependency
    • apper/s390x has unsatisfiable dependency
    • Updating apper would introduce bugs in testing: #1090089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apper.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 477 days old (needed 5 days)
• appstream-generator (- to 0.9.1-1)
  • Migration status for appstream-generator (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: appstream-generator -> libphobos2-ldc-shared106/1:1.36.0-2.1/amd64
    • Impossible Depends: appstream-generator -> libphobos2-ldc-shared106/1:1.36.0-2.1/arm64
    • Impossible Depends: appstream-generator -> libphobos2-ldc-shared106/1:1.36.0-2.1/i386
    • Impossible Depends: appstream-generator -> libphobos2-ldc-shared106/1:1.36.0-2.1/riscv64
    • Build-Depends(-Arch): appstream-generator glib-d (not considered)
    • Depends: appstream-generator glib-d (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appstream-generator.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 478 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
    • autopkgtest for pysurfer/0.11.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): pysurfer mayavi2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysurfer.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 479 days old (needed 5 days)
• 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 480 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
    • Reproducible on armhf - info ♻
    • 482 days old (needed 5 days)
• pandoc-sidenote (- to 0.23.0-1)
  • Migration status for pandoc-sidenote (- to 0.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-pandoc-sidenote-doc/amd64 has unsatisfiable dependency
    • pandoc-sidenote/amd64 has unsatisfiable dependency
    • libghc-pandoc-sidenote-doc/arm64 has unsatisfiable dependency
    • pandoc-sidenote/arm64 has unsatisfiable dependency
    • pandoc-sidenote/ppc64el has unsatisfiable dependency
    • pandoc-sidenote/s390x has unsatisfiable dependency
    • Updating pandoc-sidenote would introduce bugs in testing: #1055980
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pandoc-sidenote.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 484 days old (needed 5 days)
• node-har-validator (- to 5.1.5-4)
  • Migration status for node-har-validator (- to 5.1.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-har-validator would introduce bugs in testing: #1024575
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-har-validator.html
    • autopkgtest for node-har-validator/5.1.5-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 488 days old (needed 5 days)
• kmscon (- to 9.0.0-5)
  • Migration status for kmscon (- to 9.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kmscon would introduce bugs in testing: #1061686
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmscon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 490 days old (needed 5 days)
• slashtime (- to 0.5.13-3)
  • Migration status for slashtime (- to 0.5.13-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): slashtime java-gnome (not considered)
    • Depends: slashtime java-gnome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slashtime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 491 days old (needed 5 days)
• comskip (- to 0.82.009+git20230112.d0cc422+ds.1-2.1)
  • Migration status for comskip (- to 0.82.009+git20230112.d0cc422+ds.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • comskip/amd64 has unsatisfiable dependency
    • comskip-gui/amd64 has unsatisfiable dependency
    • comskip/arm64 has unsatisfiable dependency
    • comskip-gui/arm64 has unsatisfiable dependency
    • comskip/armel has unsatisfiable dependency
    • comskip-gui/armel has unsatisfiable dependency
    • comskip/armhf has unsatisfiable dependency
    • comskip-gui/armhf has unsatisfiable dependency
    • comskip/i386 has unsatisfiable dependency
    • comskip-gui/i386 has unsatisfiable dependency
    • comskip/mips64el has unsatisfiable dependency
    • comskip-gui/mips64el has unsatisfiable dependency
    • comskip/ppc64el has unsatisfiable dependency
    • comskip-gui/ppc64el has unsatisfiable dependency
    • comskip/riscv64 has unsatisfiable dependency
    • comskip-gui/riscv64 has unsatisfiable dependency
    • comskip/s390x has unsatisfiable dependency
    • comskip-gui/s390x has unsatisfiable dependency
    • Updating comskip would introduce bugs in testing: #1072406
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/comskip.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 492 days old (needed 5 days)
• ruby-factory-bot-rails (- to 6.4.2-1)
  • Migration status for ruby-factory-bot-rails (- to 6.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-factory-bot-rails would introduce bugs in testing: #1094536, #1095882
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-factory-bot-rails.html
    • autopkgtest for ruby-factory-bot-rails/6.4.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 496 days old (needed 2 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 497 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 499 days old (needed 2 days)
• pygccjit (- to 0.4-13)
  • Migration status for pygccjit (- to 0.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gccjit/amd64 has unsatisfiable dependency
    • python3-gccjit/arm64 has unsatisfiable dependency
    • python3-gccjit/armel has unsatisfiable dependency
    • python3-gccjit/armhf has unsatisfiable dependency
    • python3-gccjit/i386 has unsatisfiable dependency
    • python3-gccjit/mips64el has unsatisfiable dependency
    • python3-gccjit/ppc64el has unsatisfiable dependency
    • python3-gccjit/riscv64 has unsatisfiable dependency
    • python3-gccjit/s390x has unsatisfiable dependency
    • Updating pygccjit would introduce bugs in testing: #1082097, #1092782
    • Build-Depends(-Arch): pygccjit cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pygccjit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 499 days old (needed 5 days)
• recutils (- to 1.9-3)
  • Migration status for recutils (- to 1.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librec1/armel has unsatisfiable dependency
    • recutils/armel has unsatisfiable dependency
    • librec1/armhf has unsatisfiable dependency
    • recutils/armhf has unsatisfiable dependency
    • Updating recutils would introduce bugs in testing: #1066370
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/recutils.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 499 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
    • 500 days old (needed 5 days)
• xemacs21-packages (- to 2009.02.17.dfsg.3-3)
  • Migration status for xemacs21-packages (- to 2009.02.17.dfsg.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: xemacs21-packages xemacs21 (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xemacs21-packages.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 501 days old (needed 5 days)
• node-wikibase-cli (- to 15.15.4-5)
  • Migration status for node-wikibase-cli (- to 15.15.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-wikibase-cli would introduce bugs in testing: #1056699, #1056708
    • autopkgtest for node-wikibase-cli/15.15.4-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-wikibase-cli.html
    • 502 days old (needed 5 days)
• gnome-split (- to 1.2-5)
  • Migration status for gnome-split (- to 1.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnome-split java-gnome (not considered)
    • Depends: gnome-split java-gnome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-split.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 504 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
    • 504 days old (needed 5 days)
• cryptojs (- to 3.1.2+dfsg-4)
  • Migration status for cryptojs (- to 3.1.2+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cryptojs would introduce bugs in testing: #1056014
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cryptojs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 508 days old (needed 5 days)
• ruby-voight-kampff (- to 2.0.0-1)
  • Migration status for ruby-voight-kampff (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-voight-kampff would introduce bugs in testing: #1094529
    • autopkgtest for ruby-voight-kampff/2.0.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • ruby-voight-kampff unsatisfiable Build-Depends(-Arch) on amd64: ruby-rack (<< 3.0)
    • Impossible Depends: ruby-voight-kampff -> ruby-rack/2.2.13-1~deb12u1/amd64
    • Impossible Depends: ruby-voight-kampff -> ruby-rack/2.2.13-1~deb12u1/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-voight-kampff.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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 508 days old (needed 5 days)
• jupyter-ydoc (- to 1.0.2-2)
  • Migration status for jupyter-ydoc (- to 1.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-jupyter-ydoc/arm64 has unsatisfiable dependency
    • Updating jupyter-ydoc would introduce bugs in testing: #1071771
    • autopkgtest for jupyter-ydoc/1.0.2-2: amd64: Regression or new test ♻
    • Build-Depends(-Arch): jupyter-ydoc ypy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/j/jupyter-ydoc.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 509 days old (needed 5 days)
• ypy (- to 0.7.0~a1-2)
  • Migration status for ypy (- to 0.7.0~a1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ypy would introduce bugs in testing: #1071899
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-lib0-dev
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-yrs-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/y/ypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 509 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
    • 510 days old (needed 5 days)
• python-diagrams (- to 0.23.4-1)
  • Migration status for python-diagrams (- to 0.23.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-diagrams/amd64 has unsatisfiable dependency
    • python3-diagrams/arm64 has unsatisfiable dependency
    • Updating python-diagrams would introduce bugs in testing: #1057174
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-diagrams.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 511 days old (needed 5 days)
• kiwi-boxed-plugin (- to 0.2.31-1)
  • Migration status for kiwi-boxed-plugin (- to 0.2.31-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kiwi-boxed-plugin kiwi (not considered)
    • Depends: kiwi-boxed-plugin kiwi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kiwi-boxed-plugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 513 days old (needed 5 days)
• umap-learn (- to 0.5.4+dfsg-1)
  • Migration status for umap-learn (- to 0.5.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umap-learn would introduce bugs in testing: #1071816
    • autopkgtest for umap-learn/0.5.4+dfsg-1: amd64: Regression or new test ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): umap-learn numba (not considered)
    • Build-Depends(-Arch): umap-learn python-pynndescent (not considered)
    • Depends: umap-learn python-pynndescent (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umap-learn.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 516 days old (needed 5 days)
• ruby-timeliness (- to 0.4.5-1)
  • Migration status for ruby-timeliness (- to 0.4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-timeliness would introduce bugs in testing: #1086314
    • autopkgtest for ruby-timeliness/0.4.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-timeliness.html
    • 519 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
    • 520 days old (needed 5 days)
• robot-testing-framework (- to 2.0.1+ds1-3)
  • Migration status for robot-testing-framework (- to 2.0.1+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating robot-testing-framework would introduce bugs in testing: #1075449
    • Depends: robot-testing-framework ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/robot-testing-framework.html
    • 521 days old (needed 5 days)
• ruby-distribution (- to 0.8.0+dfsg-1)
  • Migration status for ruby-distribution (- to 0.8.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-distribution/0.8.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-distribution.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 523 days old (needed 5 days)
• parcellite (- to 1.2.1-8)
  • Migration status for parcellite (- to 1.2.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parcellite would introduce bugs in testing: #1075362
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parcellite.html
    • autopkgtest for parcellite/1.2.1-8: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 530 days old (needed 5 days)
• python-certbot-dns-gandi (- to 1.4.3-2)
  • Migration status for python-certbot-dns-gandi (- to 1.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-certbot-dns-gandi would introduce bugs in testing: #1038920
    • autopkgtest for python-certbot-dns-gandi/1.4.3-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-gandi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 530 days old (needed 5 days)
• haskell-soap-tls (- to 0.1.1.4-6)
  • Migration status for haskell-soap-tls (- to 0.1.1.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-soap-tls-dev/amd64 has unsatisfiable dependency
    • libghc-soap-tls-doc/amd64 has unsatisfiable dependency
    • libghc-soap-tls-prof/amd64 has unsatisfiable dependency
    • libghc-soap-tls-dev/arm64 has unsatisfiable dependency
    • libghc-soap-tls-doc/arm64 has unsatisfiable dependency
    • libghc-soap-tls-prof/arm64 has unsatisfiable dependency
    • libghc-soap-tls-dev/armel has unsatisfiable dependency
    • libghc-soap-tls-prof/armel has unsatisfiable dependency
    • libghc-soap-tls-dev/armhf has unsatisfiable dependency
    • libghc-soap-tls-prof/armhf has unsatisfiable dependency
    • libghc-soap-tls-dev/i386 has unsatisfiable dependency
    • libghc-soap-tls-prof/i386 has unsatisfiable dependency
    • libghc-soap-tls-dev/mips64el has unsatisfiable dependency
    • libghc-soap-tls-prof/mips64el has unsatisfiable dependency
    • libghc-soap-tls-dev/ppc64el has unsatisfiable dependency
    • libghc-soap-tls-prof/ppc64el has unsatisfiable dependency
    • libghc-soap-tls-dev/riscv64 has unsatisfiable dependency
    • libghc-soap-tls-prof/riscv64 has unsatisfiable dependency
    • libghc-soap-tls-dev/s390x has unsatisfiable dependency
    • libghc-soap-tls-prof/s390x has unsatisfiable dependency
    • Updating haskell-soap-tls would introduce bugs in testing: #1082423
    • Build-Depends(-Arch): haskell-soap-tls haskell-connection (not considered)
    • Build-Depends-Indep: haskell-soap-tls haskell-connection (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-soap-tls.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 531 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
    • 532 days old (needed 5 days)
• haskell-cryptol (- to 3.0.0-1)
  • Migration status for haskell-cryptol (- to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-cryptol-dev/amd64 has unsatisfiable dependency
    • libghc-cryptol-doc/amd64 has unsatisfiable dependency
    • libghc-cryptol-prof/amd64 has unsatisfiable dependency
    • libghc-cryptol-dev/arm64 has unsatisfiable dependency
    • libghc-cryptol-doc/arm64 has unsatisfiable dependency
    • libghc-cryptol-prof/arm64 has unsatisfiable dependency
    • libghc-cryptol-dev/mips64el has unsatisfiable dependency
    • libghc-cryptol-prof/mips64el has unsatisfiable dependency
    • libghc-cryptol-dev/ppc64el has unsatisfiable dependency
    • libghc-cryptol-prof/ppc64el has unsatisfiable dependency
    • libghc-cryptol-dev/riscv64 has unsatisfiable dependency
    • libghc-cryptol-prof/riscv64 has unsatisfiable dependency
    • Updating haskell-cryptol would introduce bugs in testing: #1081937
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on amd64: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on arm64: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on mips64el: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on riscv64: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-base-compat-dev (<< 0.13)
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-cryptol.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 532 days old (needed 5 days)
• haskell-smtp-mail (- to 0.3.0.0-3)
  • Migration status for haskell-smtp-mail (- to 0.3.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-smtp-mail-dev/amd64 has unsatisfiable dependency
    • libghc-smtp-mail-doc/amd64 has unsatisfiable dependency
    • libghc-smtp-mail-prof/amd64 has unsatisfiable dependency
    • libghc-smtp-mail-dev/arm64 has unsatisfiable dependency
    • libghc-smtp-mail-doc/arm64 has unsatisfiable dependency
    • libghc-smtp-mail-prof/arm64 has unsatisfiable dependency
    • libghc-smtp-mail-dev/armel has unsatisfiable dependency
    • libghc-smtp-mail-prof/armel has unsatisfiable dependency
    • libghc-smtp-mail-dev/armhf has unsatisfiable dependency
    • libghc-smtp-mail-prof/armhf has unsatisfiable dependency
    • libghc-smtp-mail-dev/i386 has unsatisfiable dependency
    • libghc-smtp-mail-prof/i386 has unsatisfiable dependency
    • libghc-smtp-mail-dev/mips64el has unsatisfiable dependency
    • libghc-smtp-mail-prof/mips64el has unsatisfiable dependency
    • libghc-smtp-mail-dev/ppc64el has unsatisfiable dependency
    • libghc-smtp-mail-prof/ppc64el has unsatisfiable dependency
    • libghc-smtp-mail-dev/riscv64 has unsatisfiable dependency
    • libghc-smtp-mail-prof/riscv64 has unsatisfiable dependency
    • libghc-smtp-mail-dev/s390x has unsatisfiable dependency
    • libghc-smtp-mail-prof/s390x has unsatisfiable dependency
    • Updating haskell-smtp-mail would introduce bugs in testing: #1082420
    • Build-Depends(-Arch): haskell-smtp-mail haskell-connection (not considered)
    • Build-Depends-Indep: haskell-smtp-mail haskell-connection (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-smtp-mail.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 532 days old (needed 5 days)
• haskell-connection (- to 0.3.1-4)
  • Migration status for haskell-connection (- to 0.3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-connection-dev/amd64 has unsatisfiable dependency
    • libghc-connection-doc/amd64 has unsatisfiable dependency
    • libghc-connection-prof/amd64 has unsatisfiable dependency
    • libghc-connection-dev/arm64 has unsatisfiable dependency
    • libghc-connection-doc/arm64 has unsatisfiable dependency
    • libghc-connection-prof/arm64 has unsatisfiable dependency
    • libghc-connection-dev/armel has unsatisfiable dependency
    • libghc-connection-prof/armel has unsatisfiable dependency
    • libghc-connection-dev/armhf has unsatisfiable dependency
    • libghc-connection-prof/armhf has unsatisfiable dependency
    • libghc-connection-dev/i386 has unsatisfiable dependency
    • libghc-connection-prof/i386 has unsatisfiable dependency
    • libghc-connection-dev/mips64el has unsatisfiable dependency
    • libghc-connection-prof/mips64el has unsatisfiable dependency
    • libghc-connection-dev/ppc64el has unsatisfiable dependency
    • libghc-connection-prof/ppc64el has unsatisfiable dependency
    • libghc-connection-dev/riscv64 has unsatisfiable dependency
    • libghc-connection-prof/riscv64 has unsatisfiable dependency
    • libghc-connection-dev/s390x has unsatisfiable dependency
    • libghc-connection-prof/s390x has unsatisfiable dependency
    • Updating haskell-connection would introduce bugs in testing: #1084124, #1085013
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-connection.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 533 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
    • 533 days old (needed 5 days)
• rust-xflags-macros (- to 0.3.1-1)
  • Migration status for rust-xflags-macros (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-xflags-macros/0.3.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags-macros.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 533 days old (needed 5 days)
• haskell-cryptohash-conduit (- to 0.1.1-13)
  • Migration status for haskell-cryptohash-conduit (- to 0.1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-cryptohash-conduit-doc/amd64 has unsatisfiable dependency
    • libghc-cryptohash-conduit-doc/arm64 has unsatisfiable dependency
    • Updating haskell-cryptohash-conduit would introduce bugs in testing: #1082560
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-cryptohash-conduit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 534 days old (needed 5 days)
• canu (- to 2.2+dfsg-5)
  • Migration status for canu (- to 2.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for canu/2.2+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress (will not be considered a regression), s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/canu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 535 days old (needed 5 days)
• gnome-chemistry-utils (- to 0.14.17-6.2)
  • Migration status for gnome-chemistry-utils (- to 0.14.17-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-chemistry-utils would introduce bugs in testing: #1078386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-chemistry-utils.html
    • autopkgtest for gnome-chemistry-utils/0.14.17-6.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 535 days old (needed 2 days)
• haskell-crypto-random (- to 0.0.9-11)
  • Migration status for haskell-crypto-random (- to 0.0.9-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-crypto-random-dev/amd64 has unsatisfiable dependency
    • libghc-crypto-random-doc/amd64 has unsatisfiable dependency
    • libghc-crypto-random-prof/amd64 has unsatisfiable dependency
    • libghc-crypto-random-dev/arm64 has unsatisfiable dependency
    • libghc-crypto-random-doc/arm64 has unsatisfiable dependency
    • libghc-crypto-random-prof/arm64 has unsatisfiable dependency
    • libghc-crypto-random-dev/armel has unsatisfiable dependency
    • libghc-crypto-random-prof/armel has unsatisfiable dependency
    • libghc-crypto-random-dev/armhf has unsatisfiable dependency
    • libghc-crypto-random-prof/armhf has unsatisfiable dependency
    • libghc-crypto-random-dev/i386 has unsatisfiable dependency
    • libghc-crypto-random-prof/i386 has unsatisfiable dependency
    • libghc-crypto-random-dev/mips64el has unsatisfiable dependency
    • libghc-crypto-random-prof/mips64el has unsatisfiable dependency
    • libghc-crypto-random-dev/ppc64el has unsatisfiable dependency
    • libghc-crypto-random-prof/ppc64el has unsatisfiable dependency
    • libghc-crypto-random-dev/riscv64 has unsatisfiable dependency
    • libghc-crypto-random-prof/riscv64 has unsatisfiable dependency
    • libghc-crypto-random-dev/s390x has unsatisfiable dependency
    • libghc-crypto-random-prof/s390x has unsatisfiable dependency
    • Updating haskell-crypto-random would introduce bugs in testing: #1082405
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-crypto-random.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 535 days old (needed 5 days)
• ruby-hipchat (- to 1.6.0-1)
  • Migration status for ruby-hipchat (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-hipchat would introduce bugs in testing: #1093921
    • autopkgtest for ruby-hipchat/1.6.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-hipchat.html
    • 539 days old (needed 5 days)
• rust-xflags (- to 0.3.1-1)
  • Migration status for rust-xflags (- to 0.3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-xflags rust-xflags-macros (not considered)
    • Depends: rust-xflags rust-xflags-macros (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags.html
    • autopkgtest for rust-xflags/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 539 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
    • 542 days old (needed 5 days)
• r-cran-heatmaply (- to 1.5.0+dfsg-1)
  • Migration status for r-cran-heatmaply (- to 1.5.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-heatmaply r-cran-dendextend (not considered)
    • Depends: r-cran-heatmaply r-cran-dendextend (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-heatmaply.html
    • autopkgtest for r-cran-heatmaply/1.5.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 543 days old (needed 2 days)
• gnome-packagekit (- to 43.0-2)
  • Migration status for gnome-packagekit (- to 43.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-packagekit would introduce bugs in testing: #1074666
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-packagekit.html
    • 546 days old (needed 5 days)
• mrb (- to 0.3+nmu3)
  • Migration status for mrb (- to 0.3+nmu3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mrb would introduce bugs in testing: #1092435
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrb.html
    • 546 days old (needed 5 days)
• haskell-web-routes-boomerang (- to 0.28.4.4-1)
  • Migration status for haskell-web-routes-boomerang (- to 0.28.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-boomerang-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/armel has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/armel has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes-boomerang would introduce bugs in testing: #1084755
    • Build-Depends(-Arch): haskell-web-routes-boomerang haskell-web-routes (not considered)
    • Build-Depends-Indep: haskell-web-routes-boomerang haskell-web-routes (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes-boomerang.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 547 days old (needed 5 days)
• haskell-web-routes-happstack (- to 0.23.12.3-1)
  • Migration status for haskell-web-routes-happstack (- to 0.23.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-happstack-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-happstack-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-happstack-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/armel has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/armel has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes-happstack would introduce bugs in testing: #1084756
    • Build-Depends(-Arch): haskell-web-routes-happstack haskell-web-routes (not considered)
    • Build-Depends-Indep: haskell-web-routes-happstack haskell-web-routes (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes-happstack.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 547 days old (needed 5 days)
• haskell-web-routes-th (- to 0.22.8.1-1)
  • Migration status for haskell-web-routes-th (- to 0.22.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-th-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-th-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-th-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-th-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-th-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-th-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-th-dev/armel has unsatisfiable dependency
    • libghc-web-routes-th-prof/armel has unsatisfiable dependency
    • libghc-web-routes-th-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-th-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-th-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-th-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-th-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-th-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-th-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-th-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-th-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-th-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-th-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-th-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes-th would introduce bugs in testing: #1084757
    • Build-Depends(-Arch): haskell-web-routes-th haskell-web-routes (not considered)
    • Build-Depends-Indep: haskell-web-routes-th haskell-web-routes (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes-th.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 547 days old (needed 5 days)
• rust-extprim (- to 1.7.1-2)
  • Migration status for rust-extprim (- to 1.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-extprim would introduce bugs in testing: #1053625
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-extprim.html
    • autopkgtest for rust-extprim/1.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 548 days old (needed 2 days)
• haskell-csv-conduit (- to 0.7.3.0-2)
  • Migration status for haskell-csv-conduit (- to 0.7.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-csv-conduit-dev/amd64 has unsatisfiable dependency
    • libghc-csv-conduit-doc/amd64 has unsatisfiable dependency
    • libghc-csv-conduit-prof/amd64 has unsatisfiable dependency
    • libghc-csv-conduit-dev/arm64 has unsatisfiable dependency
    • libghc-csv-conduit-doc/arm64 has unsatisfiable dependency
    • libghc-csv-conduit-prof/arm64 has unsatisfiable dependency
    • libghc-csv-conduit-dev/armel has unsatisfiable dependency
    • libghc-csv-conduit-prof/armel has unsatisfiable dependency
    • libghc-csv-conduit-dev/armhf has unsatisfiable dependency
    • libghc-csv-conduit-prof/armhf has unsatisfiable dependency
    • libghc-csv-conduit-dev/i386 has unsatisfiable dependency
    • libghc-csv-conduit-prof/i386 has unsatisfiable dependency
    • libghc-csv-conduit-dev/mips64el has unsatisfiable dependency
    • libghc-csv-conduit-prof/mips64el has unsatisfiable dependency
    • libghc-csv-conduit-dev/ppc64el has unsatisfiable dependency
    • libghc-csv-conduit-prof/ppc64el has unsatisfiable dependency
    • libghc-csv-conduit-dev/riscv64 has unsatisfiable dependency
    • libghc-csv-conduit-prof/riscv64 has unsatisfiable dependency
    • libghc-csv-conduit-dev/s390x has unsatisfiable dependency
    • libghc-csv-conduit-prof/s390x has unsatisfiable dependency
    • Updating haskell-csv-conduit would introduce bugs in testing: #1082408
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-csv-conduit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 549 days old (needed 5 days)
• haskell-hsx-jmacro (- to 7.3.8.2-2)
  • Migration status for haskell-hsx-jmacro (- to 7.3.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsx-jmacro-dev/amd64 has unsatisfiable dependency
    • libghc-hsx-jmacro-doc/amd64 has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/amd64 has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/arm64 has unsatisfiable dependency
    • libghc-hsx-jmacro-doc/arm64 has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/arm64 has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/armel has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/armel has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/armhf has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/armhf has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/i386 has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/i386 has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/mips64el has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/mips64el has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/ppc64el has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/ppc64el has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/riscv64 has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/riscv64 has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/s390x has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsx-jmacro would introduce bugs in testing: #1082355
    • Build-Depends(-Arch): haskell-hsx-jmacro haskell-hsp (not considered)
    • Build-Depends-Indep: haskell-hsx-jmacro haskell-hsp (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsx-jmacro.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 549 days old (needed 5 days)
• haskell-publicsuffixlist (- to 0.1-15)
  • Migration status for haskell-publicsuffixlist (- to 0.1-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-publicsuffixlist-dev/amd64 has unsatisfiable dependency
    • libghc-publicsuffixlist-doc/amd64 has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/amd64 has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/arm64 has unsatisfiable dependency
    • libghc-publicsuffixlist-doc/arm64 has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/arm64 has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/armel has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/armel has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/armhf has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/armhf has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/i386 has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/i386 has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/mips64el has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/mips64el has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/ppc64el has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/ppc64el has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/riscv64 has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/riscv64 has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/s390x has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/s390x has unsatisfiable dependency
    • Updating haskell-publicsuffixlist would introduce bugs in testing: #1082006
    • Build-Depends(-Arch): haskell-publicsuffixlist haskell-idna (not considered)
    • Build-Depends-Indep: haskell-publicsuffixlist haskell-idna (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-publicsuffixlist.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 549 days old (needed 5 days)
• haskell-web-routes-hsp (- to 0.24.6.2-2)
  • Migration status for haskell-web-routes-hsp (- to 0.24.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/armel has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/armel has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes-hsp would introduce bugs in testing: #1082356
    • Build-Depends(-Arch): haskell-web-routes-hsp haskell-hsp (not considered)
    • Build-Depends(-Arch): haskell-web-routes-hsp haskell-web-routes (not considered)
    • Build-Depends-Indep: haskell-web-routes-hsp haskell-hsp (not considered)
    • Build-Depends-Indep: haskell-web-routes-hsp haskell-web-routes (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 549 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
    • 550 days old (needed 5 days)
• haskell-web-routes (- to 0.27.15-1)
  • Migration status for haskell-web-routes (- to 0.27.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-dev/armel has unsatisfiable dependency
    • libghc-web-routes-prof/armel has unsatisfiable dependency
    • libghc-web-routes-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes would introduce bugs in testing: #1084129, #1084758
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 550 days old (needed 5 days)
• transgui (- to 5.18.0+dfsg-3.1)
  • Migration status for transgui (- to 5.18.0+dfsg-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating transgui would introduce bugs in testing: #1094088
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/transgui.html
    • Reproducible on armhf - info ♻
    • 556 days old (needed 5 days)
• yosys-plugin-ghdl (- to 0.0~git20230419.5b64ccf-1)
  • Migration status for yosys-plugin-ghdl (- to 0.0~git20230419.5b64ccf-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yosys-plugin-ghdl/amd64 has unsatisfiable dependency
    • yosys-plugin-ghdl/i386 has unsatisfiable dependency
    • Updating yosys-plugin-ghdl would introduce bugs in testing: #1067465
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on arm64: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on armel: yosys-dev
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on armel: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on i386: yosys-dev
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on i386: libghdl-dev (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on i386: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on mips64el: libghdl-dev (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on mips64el: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on ppc64el: ghdl-mcode (>= 3.0.0)
    • missing build on arm64
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/y/yosys-plugin-ghdl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 556 days old (needed 5 days)
• bonnie++ (- to 2.00a+nmu2)
  • Migration status for bonnie++ (- to 2.00a+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bonnie++/2.00a+nmu2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bonnie++.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 557 days old (needed 5 days)
• jh7100-bootloader-recovery (- to 0~2021.07.14~git2b268a1c-3)
  • Migration status for jh7100-bootloader-recovery (- to 0~2021.07.14~git2b268a1c-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jh7100-bootloader-recovery would introduce bugs in testing: #1066679
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jh7100-bootloader-recovery.html
    • 558 days old (needed 5 days)
• fbb (- to 7.011-3)
  • Migration status for fbb (- to 7.011-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fbb would introduce bugs in testing: #1091298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fbb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 559 days old (needed 5 days)
• rust-test-strategy (- to 0.3.1-1)
  • Migration status for rust-test-strategy (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-test-strategy/0.3.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-test-strategy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 563 days old (needed 5 days)
• gosa-plugins-systems (- to 2.8~git20211027.5741b8f-9)
  • Migration status for gosa-plugins-systems (- to 2.8~git20211027.5741b8f-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-systems gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-systems.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 567 days old (needed 5 days)
• jack-capture (- to 0.9.73-4)
  • Migration status for jack-capture (- to 0.9.73-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jack-capture would introduce bugs in testing: #1071318
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jack-capture.html
    • 567 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
    • 567 days old (needed 5 days)
• materia-kde (- to 20220823-2)
  • Migration status for materia-kde (- to 20220823-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating materia-kde would introduce bugs in testing: #1091373
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/materia-kde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 568 days old (needed 5 days)
• haskell-reform-happstack (- to 0.2.5.6-1)
  • Migration status for haskell-reform-happstack (- to 0.2.5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-reform-happstack-dev/amd64 has unsatisfiable dependency
    • libghc-reform-happstack-doc/amd64 has unsatisfiable dependency
    • libghc-reform-happstack-prof/amd64 has unsatisfiable dependency
    • libghc-reform-happstack-dev/arm64 has unsatisfiable dependency
    • libghc-reform-happstack-doc/arm64 has unsatisfiable dependency
    • libghc-reform-happstack-prof/arm64 has unsatisfiable dependency
    • libghc-reform-happstack-dev/armel has unsatisfiable dependency
    • libghc-reform-happstack-prof/armel has unsatisfiable dependency
    • libghc-reform-happstack-dev/armhf has unsatisfiable dependency
    • libghc-reform-happstack-prof/armhf has unsatisfiable dependency
    • libghc-reform-happstack-dev/i386 has unsatisfiable dependency
    • libghc-reform-happstack-prof/i386 has unsatisfiable dependency
    • libghc-reform-happstack-dev/mips64el has unsatisfiable dependency
    • libghc-reform-happstack-prof/mips64el has unsatisfiable dependency
    • libghc-reform-happstack-dev/ppc64el has unsatisfiable dependency
    • libghc-reform-happstack-prof/ppc64el has unsatisfiable dependency
    • libghc-reform-happstack-dev/riscv64 has unsatisfiable dependency
    • libghc-reform-happstack-prof/riscv64 has unsatisfiable dependency
    • libghc-reform-happstack-dev/s390x has unsatisfiable dependency
    • libghc-reform-happstack-prof/s390x has unsatisfiable dependency
    • Updating haskell-reform-happstack would introduce bugs in testing: #1082414
    • Build-Depends(-Arch): haskell-reform-happstack haskell-reform (not considered)
    • Build-Depends-Indep: haskell-reform-happstack haskell-reform (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-reform-happstack.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 569 days old (needed 5 days)
• haskell-happstack-hsp (- to 7.3.7.7-1)
  • Migration status for haskell-happstack-hsp (- to 7.3.7.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-happstack-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-happstack-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-happstack-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-happstack-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-happstack-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-happstack-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-happstack-hsp-dev/armel has unsatisfiable dependency
    • libghc-happstack-hsp-prof/armel has unsatisfiable dependency
    • libghc-happstack-hsp-dev/armhf has unsatisfiable dependency
    • libghc-happstack-hsp-prof/armhf has unsatisfiable dependency
    • libghc-happstack-hsp-dev/i386 has unsatisfiable dependency
    • libghc-happstack-hsp-prof/i386 has unsatisfiable dependency
    • libghc-happstack-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-happstack-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-happstack-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-happstack-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-happstack-hsp-dev/riscv64 has unsatisfiable dependency
    • libghc-happstack-hsp-prof/riscv64 has unsatisfiable dependency
    • libghc-happstack-hsp-dev/s390x has unsatisfiable dependency
    • libghc-happstack-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-happstack-hsp would introduce bugs in testing: #1082351
    • Build-Depends(-Arch): haskell-happstack-hsp haskell-harp (not considered)
    • Build-Depends(-Arch): haskell-happstack-hsp haskell-hsp (not considered)
    • Build-Depends(-Arch): haskell-happstack-hsp haskell-hsx2hs (not considered)
    • Build-Depends-Indep: haskell-happstack-hsp haskell-harp (not considered)
    • Build-Depends-Indep: haskell-happstack-hsp haskell-hsp (not considered)
    • Build-Depends-Indep: haskell-happstack-hsp haskell-hsx2hs (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-happstack-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 570 days old (needed 5 days)
• xpra (- to 3.1.5+dfsg1-0.2)
  • Migration status for xpra (- to 3.1.5+dfsg1-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xpra/amd64 has unsatisfiable dependency
    • xpra/arm64 has unsatisfiable dependency
    • xpra/armel has unsatisfiable dependency
    • xpra/armhf has unsatisfiable dependency
    • xpra/i386 has unsatisfiable dependency
    • xpra/mips64el has unsatisfiable dependency
    • xpra/ppc64el has unsatisfiable dependency
    • xpra/riscv64 has unsatisfiable dependency
    • xpra/s390x has unsatisfiable dependency
    • Updating xpra would introduce bugs in testing: #1067627, #1072463, #1086122, #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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 571 days old (needed 5 days)
• haskell-reform (- to 0.2.7.5-2)
  • Migration status for haskell-reform (- to 0.2.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-reform-dev/amd64 has unsatisfiable dependency
    • libghc-reform-doc/amd64 has unsatisfiable dependency
    • libghc-reform-prof/amd64 has unsatisfiable dependency
    • libghc-reform-dev/arm64 has unsatisfiable dependency
    • libghc-reform-doc/arm64 has unsatisfiable dependency
    • libghc-reform-prof/arm64 has unsatisfiable dependency
    • libghc-reform-dev/armel has unsatisfiable dependency
    • libghc-reform-prof/armel has unsatisfiable dependency
    • libghc-reform-dev/armhf has unsatisfiable dependency
    • libghc-reform-prof/armhf has unsatisfiable dependency
    • libghc-reform-dev/i386 has unsatisfiable dependency
    • libghc-reform-prof/i386 has unsatisfiable dependency
    • libghc-reform-dev/mips64el has unsatisfiable dependency
    • libghc-reform-prof/mips64el has unsatisfiable dependency
    • libghc-reform-dev/ppc64el has unsatisfiable dependency
    • libghc-reform-prof/ppc64el has unsatisfiable dependency
    • libghc-reform-dev/riscv64 has unsatisfiable dependency
    • libghc-reform-prof/riscv64 has unsatisfiable dependency
    • libghc-reform-dev/s390x has unsatisfiable dependency
    • libghc-reform-prof/s390x has unsatisfiable dependency
    • Updating haskell-reform would introduce bugs in testing: #1082413
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-reform.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 573 days old (needed 5 days)
• soundgrain (- to 6.0.1-5)
  • Migration status for soundgrain (- to 6.0.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: soundgrain python-pyo (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soundgrain.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 573 days old (needed 5 days)
• frama-c (- to 20220511-manganese-5)
  • Migration status for frama-c (- to 20220511-manganese-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • frama-c-base/amd64 has unsatisfiable dependency
    • frama-c-base/arm64 has unsatisfiable dependency
    • frama-c-base/armel has unsatisfiable dependency
    • frama-c-base/armhf has unsatisfiable dependency
    • frama-c-base/i386 has unsatisfiable dependency
    • frama-c-base/mips64el has unsatisfiable dependency
    • frama-c-base/ppc64el has unsatisfiable dependency
    • frama-c-base/riscv64 has unsatisfiable dependency
    • frama-c-base/s390x has unsatisfiable dependency
    • Updating frama-c would introduce bugs in testing: #1093102
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frama-c.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 577 days old (needed 5 days)
• haskell-idna (- to 0.3.0-13)
  • Migration status for haskell-idna (- to 0.3.0-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-idna-dev/amd64 has unsatisfiable dependency
    • libghc-idna-doc/amd64 has unsatisfiable dependency
    • libghc-idna-prof/amd64 has unsatisfiable dependency
    • libghc-idna-dev/arm64 has unsatisfiable dependency
    • libghc-idna-doc/arm64 has unsatisfiable dependency
    • libghc-idna-prof/arm64 has unsatisfiable dependency
    • libghc-idna-dev/armel has unsatisfiable dependency
    • libghc-idna-prof/armel has unsatisfiable dependency
    • libghc-idna-dev/armhf has unsatisfiable dependency
    • libghc-idna-prof/armhf has unsatisfiable dependency
    • libghc-idna-dev/i386 has unsatisfiable dependency
    • libghc-idna-prof/i386 has unsatisfiable dependency
    • libghc-idna-dev/mips64el has unsatisfiable dependency
    • libghc-idna-prof/mips64el has unsatisfiable dependency
    • libghc-idna-dev/ppc64el has unsatisfiable dependency
    • libghc-idna-prof/ppc64el has unsatisfiable dependency
    • libghc-idna-dev/riscv64 has unsatisfiable dependency
    • libghc-idna-prof/riscv64 has unsatisfiable dependency
    • libghc-idna-dev/s390x has unsatisfiable dependency
    • libghc-idna-prof/s390x has unsatisfiable dependency
    • Updating haskell-idna would introduce bugs in testing: #1082007
    • Build-Depends(-Arch): haskell-idna haskell-punycode (not considered)
    • Build-Depends-Indep: haskell-idna haskell-punycode (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-idna.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 577 days old (needed 5 days)
• haskell-regex-applicative-text (- to 0.1.0.1-10)
  • Migration status for haskell-regex-applicative-text (- to 0.1.0.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-regex-applicative-text-doc/amd64 has unsatisfiable dependency
    • libghc-regex-applicative-text-doc/arm64 has unsatisfiable dependency
    • Updating haskell-regex-applicative-text would introduce bugs in testing: #1082416
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-regex-applicative-text.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 577 days old (needed 5 days)
• haskell-file-location (- to 0.4.9.1-5)
  • Migration status for haskell-file-location (- to 0.4.9.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-file-location-dev/amd64 has unsatisfiable dependency
    • libghc-file-location-doc/amd64 has unsatisfiable dependency
    • libghc-file-location-prof/amd64 has unsatisfiable dependency
    • libghc-file-location-dev/arm64 has unsatisfiable dependency
    • libghc-file-location-doc/arm64 has unsatisfiable dependency
    • libghc-file-location-prof/arm64 has unsatisfiable dependency
    • libghc-file-location-dev/armel has unsatisfiable dependency
    • libghc-file-location-prof/armel has unsatisfiable dependency
    • libghc-file-location-dev/armhf has unsatisfiable dependency
    • libghc-file-location-prof/armhf has unsatisfiable dependency
    • libghc-file-location-dev/i386 has unsatisfiable dependency
    • libghc-file-location-prof/i386 has unsatisfiable dependency
    • libghc-file-location-dev/mips64el has unsatisfiable dependency
    • libghc-file-location-prof/mips64el has unsatisfiable dependency
    • libghc-file-location-dev/ppc64el has unsatisfiable dependency
    • libghc-file-location-prof/ppc64el has unsatisfiable dependency
    • libghc-file-location-dev/riscv64 has unsatisfiable dependency
    • libghc-file-location-prof/riscv64 has unsatisfiable dependency
    • libghc-file-location-dev/s390x has unsatisfiable dependency
    • libghc-file-location-prof/s390x has unsatisfiable dependency
    • Updating haskell-file-location would introduce bugs in testing: #1082409
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-file-location.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 578 days old (needed 5 days)
• vuls (- to 0.6.1-5)
  • Migration status for vuls (- to 0.6.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vuls would introduce bugs in testing: #1085477
    • Build-Depends(-Arch): vuls go-cve-dictionary (not considered)
    • Build-Depends(-Arch): vuls go-exploitdb (not considered)
    • Build-Depends(-Arch): vuls gost (not considered)
    • Build-Depends(-Arch): vuls goval-dictionary (not considered)
    • Built-Using: vuls go-cve-dictionary (not considered)
    • Built-Using: vuls go-exploitdb (not considered)
    • Built-Using: vuls golang-github-go-redis-redis (not considered)
    • Built-Using: vuls gost (not considered)
    • Built-Using: vuls goval-dictionary (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vuls.html
    • autopkgtest for vuls/0.6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 579 days old (needed 2 days)
• haskell-argon2 (- to 1.3.0.1-10)
  • Migration status for haskell-argon2 (- to 1.3.0.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-argon2-dev/amd64 has unsatisfiable dependency
    • libghc-argon2-doc/amd64 has unsatisfiable dependency
    • libghc-argon2-prof/amd64 has unsatisfiable dependency
    • libghc-argon2-dev/arm64 has unsatisfiable dependency
    • libghc-argon2-doc/arm64 has unsatisfiable dependency
    • libghc-argon2-prof/arm64 has unsatisfiable dependency
    • libghc-argon2-dev/armel has unsatisfiable dependency
    • libghc-argon2-prof/armel has unsatisfiable dependency
    • libghc-argon2-dev/armhf has unsatisfiable dependency
    • libghc-argon2-prof/armhf has unsatisfiable dependency
    • libghc-argon2-dev/i386 has unsatisfiable dependency
    • libghc-argon2-prof/i386 has unsatisfiable dependency
    • libghc-argon2-dev/mips64el has unsatisfiable dependency
    • libghc-argon2-prof/mips64el has unsatisfiable dependency
    • libghc-argon2-dev/ppc64el has unsatisfiable dependency
    • libghc-argon2-prof/ppc64el has unsatisfiable dependency
    • libghc-argon2-dev/riscv64 has unsatisfiable dependency
    • libghc-argon2-prof/riscv64 has unsatisfiable dependency
    • libghc-argon2-dev/s390x has unsatisfiable dependency
    • libghc-argon2-prof/s390x has unsatisfiable dependency
    • Updating haskell-argon2 would introduce bugs in testing: #1081373
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-argon2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 580 days old (needed 5 days)
• haskell-hsx2hs (- to 0.14.1.11-1)
  • Migration status for haskell-hsx2hs (- to 0.14.1.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsx2hs-dev/amd64 has unsatisfiable dependency
    • libghc-hsx2hs-doc/amd64 has unsatisfiable dependency
    • libghc-hsx2hs-prof/amd64 has unsatisfiable dependency
    • libghc-hsx2hs-dev/arm64 has unsatisfiable dependency
    • libghc-hsx2hs-doc/arm64 has unsatisfiable dependency
    • libghc-hsx2hs-prof/arm64 has unsatisfiable dependency
    • libghc-hsx2hs-dev/armel has unsatisfiable dependency
    • libghc-hsx2hs-prof/armel has unsatisfiable dependency
    • libghc-hsx2hs-dev/armhf has unsatisfiable dependency
    • libghc-hsx2hs-prof/armhf has unsatisfiable dependency
    • libghc-hsx2hs-dev/i386 has unsatisfiable dependency
    • libghc-hsx2hs-prof/i386 has unsatisfiable dependency
    • libghc-hsx2hs-dev/mips64el has unsatisfiable dependency
    • libghc-hsx2hs-prof/mips64el has unsatisfiable dependency
    • libghc-hsx2hs-dev/ppc64el has unsatisfiable dependency
    • libghc-hsx2hs-prof/ppc64el has unsatisfiable dependency
    • libghc-hsx2hs-dev/riscv64 has unsatisfiable dependency
    • libghc-hsx2hs-prof/riscv64 has unsatisfiable dependency
    • libghc-hsx2hs-dev/s390x has unsatisfiable dependency
    • libghc-hsx2hs-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsx2hs would introduce bugs in testing: #1082352
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsx2hs.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 580 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
    • 582 days old (needed 5 days)
• haskell-configfile (- to 1.1.4-11)
  • Migration status for haskell-configfile (- to 1.1.4-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-configfile-dev/amd64 has unsatisfiable dependency
    • libghc-configfile-doc/amd64 has unsatisfiable dependency
    • libghc-configfile-prof/amd64 has unsatisfiable dependency
    • libghc-configfile-dev/arm64 has unsatisfiable dependency
    • libghc-configfile-doc/arm64 has unsatisfiable dependency
    • libghc-configfile-prof/arm64 has unsatisfiable dependency
    • libghc-configfile-dev/armel has unsatisfiable dependency
    • libghc-configfile-prof/armel has unsatisfiable dependency
    • libghc-configfile-dev/armhf has unsatisfiable dependency
    • libghc-configfile-prof/armhf has unsatisfiable dependency
    • libghc-configfile-dev/i386 has unsatisfiable dependency
    • libghc-configfile-prof/i386 has unsatisfiable dependency
    • libghc-configfile-dev/mips64el has unsatisfiable dependency
    • libghc-configfile-prof/mips64el has unsatisfiable dependency
    • libghc-configfile-dev/ppc64el has unsatisfiable dependency
    • libghc-configfile-prof/ppc64el has unsatisfiable dependency
    • libghc-configfile-dev/riscv64 has unsatisfiable dependency
    • libghc-configfile-prof/riscv64 has unsatisfiable dependency
    • libghc-configfile-dev/s390x has unsatisfiable dependency
    • libghc-configfile-prof/s390x has unsatisfiable dependency
    • Updating haskell-configfile would introduce bugs in testing: #1081936
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-configfile.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 582 days old (needed 5 days)
• haskell-prettyprinter-convert-ansi-wl-pprint (- to 1.1.2-2)
  • Migration status for haskell-prettyprinter-convert-ansi-wl-pprint (- to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/amd64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-doc/amd64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/amd64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/arm64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-doc/arm64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/arm64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/armel has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/armel has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/armhf has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/armhf has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/i386 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/i386 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/mips64el has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/mips64el has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/ppc64el has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/ppc64el has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/riscv64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/riscv64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/s390x has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/s390x has unsatisfiable dependency
    • Updating haskell-prettyprinter-convert-ansi-wl-pprint would introduce bugs in testing: #1083255
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-prettyprinter-convert-ansi-wl-pprint.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 582 days old (needed 5 days)
• w3cam (- to 0.7.2-6.4)
  • Migration status for w3cam (- to 0.7.2-6.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating w3cam would introduce bugs in testing: #1091279
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/w3cam.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 582 days old (needed 5 days)
• haskell-lucid-svg (- to 0.7.1.1-1)
  • Migration status for haskell-lucid-svg (- to 0.7.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-lucid-svg-dev/amd64 has unsatisfiable dependency
    • libghc-lucid-svg-doc/amd64 has unsatisfiable dependency
    • libghc-lucid-svg-prof/amd64 has unsatisfiable dependency
    • libghc-lucid-svg-dev/arm64 has unsatisfiable dependency
    • libghc-lucid-svg-doc/arm64 has unsatisfiable dependency
    • libghc-lucid-svg-prof/arm64 has unsatisfiable dependency
    • libghc-lucid-svg-dev/armel has unsatisfiable dependency
    • libghc-lucid-svg-prof/armel has unsatisfiable dependency
    • libghc-lucid-svg-dev/armhf has unsatisfiable dependency
    • libghc-lucid-svg-prof/armhf has unsatisfiable dependency
    • libghc-lucid-svg-dev/i386 has unsatisfiable dependency
    • libghc-lucid-svg-prof/i386 has unsatisfiable dependency
    • libghc-lucid-svg-dev/mips64el has unsatisfiable dependency
    • libghc-lucid-svg-prof/mips64el has unsatisfiable dependency
    • libghc-lucid-svg-dev/ppc64el has unsatisfiable dependency
    • libghc-lucid-svg-prof/ppc64el has unsatisfiable dependency
    • libghc-lucid-svg-dev/riscv64 has unsatisfiable dependency
    • libghc-lucid-svg-prof/riscv64 has unsatisfiable dependency
    • libghc-lucid-svg-dev/s390x has unsatisfiable dependency
    • libghc-lucid-svg-prof/s390x has unsatisfiable dependency
    • Updating haskell-lucid-svg would introduce bugs in testing: #1082410
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-lucid-svg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 583 days old (needed 5 days)
• haskell-monad-journal (- to 0.8.1-6)
  • Migration status for haskell-monad-journal (- to 0.8.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-monad-journal-dev/amd64 has unsatisfiable dependency
    • libghc-monad-journal-doc/amd64 has unsatisfiable dependency
    • libghc-monad-journal-prof/amd64 has unsatisfiable dependency
    • libghc-monad-journal-dev/arm64 has unsatisfiable dependency
    • libghc-monad-journal-doc/arm64 has unsatisfiable dependency
    • libghc-monad-journal-prof/arm64 has unsatisfiable dependency
    • libghc-monad-journal-dev/armel has unsatisfiable dependency
    • libghc-monad-journal-prof/armel has unsatisfiable dependency
    • libghc-monad-journal-dev/armhf has unsatisfiable dependency
    • libghc-monad-journal-prof/armhf has unsatisfiable dependency
    • libghc-monad-journal-dev/i386 has unsatisfiable dependency
    • libghc-monad-journal-prof/i386 has unsatisfiable dependency
    • libghc-monad-journal-dev/mips64el has unsatisfiable dependency
    • libghc-monad-journal-prof/mips64el has unsatisfiable dependency
    • libghc-monad-journal-dev/ppc64el has unsatisfiable dependency
    • libghc-monad-journal-prof/ppc64el has unsatisfiable dependency
    • libghc-monad-journal-dev/riscv64 has unsatisfiable dependency
    • libghc-monad-journal-prof/riscv64 has unsatisfiable dependency
    • libghc-monad-journal-dev/s390x has unsatisfiable dependency
    • libghc-monad-journal-prof/s390x has unsatisfiable dependency
    • Updating haskell-monad-journal would introduce bugs in testing: #1082411
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-monad-journal.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 583 days old (needed 5 days)
• haskell-hosc (- to 0.20-1)
  • Migration status for haskell-hosc (- to 0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hosc-doc/amd64 has unsatisfiable dependency
    • libghc-hosc-doc/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hosc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 584 days old (needed 5 days)
• haskell-gsasl (- to 0.3.7-3)
  • Migration status for haskell-gsasl (- to 0.3.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gsasl-doc/amd64 has unsatisfiable dependency
    • libghc-gsasl-doc/arm64 has unsatisfiable dependency
    • Updating haskell-gsasl would introduce bugs in testing: #1081386
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-gsasl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 585 days old (needed 5 days)
• haskell-regexpr (- to 0.5.4-17)
  • Migration status for haskell-regexpr (- to 0.5.4-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-regexpr-dev/amd64 has unsatisfiable dependency
    • libghc-regexpr-doc/amd64 has unsatisfiable dependency
    • libghc-regexpr-prof/amd64 has unsatisfiable dependency
    • libghc-regexpr-dev/arm64 has unsatisfiable dependency
    • libghc-regexpr-doc/arm64 has unsatisfiable dependency
    • libghc-regexpr-prof/arm64 has unsatisfiable dependency
    • libghc-regexpr-dev/armel has unsatisfiable dependency
    • libghc-regexpr-prof/armel has unsatisfiable dependency
    • libghc-regexpr-dev/armhf has unsatisfiable dependency
    • libghc-regexpr-prof/armhf has unsatisfiable dependency
    • libghc-regexpr-dev/i386 has unsatisfiable dependency
    • libghc-regexpr-prof/i386 has unsatisfiable dependency
    • libghc-regexpr-dev/mips64el has unsatisfiable dependency
    • libghc-regexpr-prof/mips64el has unsatisfiable dependency
    • libghc-regexpr-dev/ppc64el has unsatisfiable dependency
    • libghc-regexpr-prof/ppc64el has unsatisfiable dependency
    • libghc-regexpr-dev/riscv64 has unsatisfiable dependency
    • libghc-regexpr-prof/riscv64 has unsatisfiable dependency
    • libghc-regexpr-dev/s390x has unsatisfiable dependency
    • libghc-regexpr-prof/s390x has unsatisfiable dependency
    • Updating haskell-regexpr would introduce bugs in testing: #1082536
    • Build-Depends(-Arch): haskell-regexpr haskell-mtlparse (not considered)
    • Build-Depends-Indep: haskell-regexpr haskell-mtlparse (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-regexpr.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 585 days old (needed 5 days)
• ldap-haskell (- to 0.6.11-7)
  • Migration status for ldap-haskell (- to 0.6.11-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-ldap-doc/amd64 has unsatisfiable dependency
    • libghc-ldap-doc/arm64 has unsatisfiable dependency
    • Updating ldap-haskell would introduce bugs in testing: #1082566
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/ldap-haskell.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 585 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
    • 585 days old (needed 5 days)
• ormar (- to 0.12.2-1)
  • Migration status for ormar (- to 0.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ormar would introduce bugs in testing: #1066769
    • autopkgtest for ormar/0.12.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ormar.html
    • 585 days old (needed 5 days)
• haskell-crypto-random-api (- to 0.2.0-13)
  • Migration status for haskell-crypto-random-api (- to 0.2.0-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-crypto-random-api-doc/amd64 has unsatisfiable dependency
    • libghc-crypto-random-api-doc/arm64 has unsatisfiable dependency
    • Updating haskell-crypto-random-api would introduce bugs in testing: #1082407
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-crypto-random-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 588 days old (needed 5 days)
• haskell-djinn-lib (- to 0.0.1.4-2)
  • Migration status for haskell-djinn-lib (- to 0.0.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-djinn-lib-doc/amd64 has unsatisfiable dependency
    • libghc-djinn-lib-doc/arm64 has unsatisfiable dependency
    • Updating haskell-djinn-lib would introduce bugs in testing: #1082344
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-djinn-lib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 588 days old (needed 5 days)
• haskell-punycode (- to 2.0-14)
  • Migration status for haskell-punycode (- to 2.0-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-punycode-dev/amd64 has unsatisfiable dependency
    • libghc-punycode-doc/amd64 has unsatisfiable dependency
    • libghc-punycode-prof/amd64 has unsatisfiable dependency
    • libghc-punycode-dev/arm64 has unsatisfiable dependency
    • libghc-punycode-doc/arm64 has unsatisfiable dependency
    • libghc-punycode-prof/arm64 has unsatisfiable dependency
    • libghc-punycode-dev/armel has unsatisfiable dependency
    • libghc-punycode-prof/armel has unsatisfiable dependency
    • libghc-punycode-dev/armhf has unsatisfiable dependency
    • libghc-punycode-prof/armhf has unsatisfiable dependency
    • libghc-punycode-dev/i386 has unsatisfiable dependency
    • libghc-punycode-prof/i386 has unsatisfiable dependency
    • libghc-punycode-dev/mips64el has unsatisfiable dependency
    • libghc-punycode-prof/mips64el has unsatisfiable dependency
    • libghc-punycode-dev/ppc64el has unsatisfiable dependency
    • libghc-punycode-prof/ppc64el has unsatisfiable dependency
    • libghc-punycode-dev/riscv64 has unsatisfiable dependency
    • libghc-punycode-prof/riscv64 has unsatisfiable dependency
    • libghc-punycode-dev/s390x has unsatisfiable dependency
    • libghc-punycode-prof/s390x has unsatisfiable dependency
    • Updating haskell-punycode would introduce bugs in testing: #1082009
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-punycode.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 588 days old (needed 5 days)
• mia (- to 2.4.7-13)
  • Migration status for mia (- to 2.4.7-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libmia-2.4-4/amd64 has unsatisfiable dependency
    • mia-tools/amd64 has unsatisfiable dependency
    • libmia-2.4-4/arm64 has unsatisfiable dependency
    • mia-tools/arm64 has unsatisfiable dependency
    • libmia-2.4-4/armel has unsatisfiable dependency
    • mia-tools/armel has unsatisfiable dependency
    • libmia-2.4-4/armhf has unsatisfiable dependency
    • mia-tools/armhf has unsatisfiable dependency
    • libmia-2.4-4/i386 has unsatisfiable dependency
    • mia-tools/i386 has unsatisfiable dependency
    • libmia-2.4-4/mips64el has unsatisfiable dependency
    • mia-tools/mips64el has unsatisfiable dependency
    • libmia-2.4-4/ppc64el has unsatisfiable dependency
    • mia-tools/ppc64el has unsatisfiable dependency
    • libmia-2.4-4/riscv64 has unsatisfiable dependency
    • mia-tools/riscv64 has unsatisfiable dependency
    • libmia-2.4-4/s390x has unsatisfiable dependency
    • mia-tools/s390x has unsatisfiable dependency
    • Updating mia would introduce bugs in testing: #1075270
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mia.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 588 days old (needed 5 days)
• haskell-generic-trie (- to 0.3.2-1)
  • Migration status for haskell-generic-trie (- to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-generic-trie-dev/amd64 has unsatisfiable dependency
    • libghc-generic-trie-doc/amd64 has unsatisfiable dependency
    • libghc-generic-trie-prof/amd64 has unsatisfiable dependency
    • libghc-generic-trie-dev/arm64 has unsatisfiable dependency
    • libghc-generic-trie-doc/arm64 has unsatisfiable dependency
    • libghc-generic-trie-prof/arm64 has unsatisfiable dependency
    • libghc-generic-trie-dev/armel has unsatisfiable dependency
    • libghc-generic-trie-prof/armel has unsatisfiable dependency
    • libghc-generic-trie-dev/armhf has unsatisfiable dependency
    • libghc-generic-trie-prof/armhf has unsatisfiable dependency
    • libghc-generic-trie-dev/i386 has unsatisfiable dependency
    • libghc-generic-trie-prof/i386 has unsatisfiable dependency
    • libghc-generic-trie-dev/mips64el has unsatisfiable dependency
    • libghc-generic-trie-prof/mips64el has unsatisfiable dependency
    • libghc-generic-trie-dev/ppc64el has unsatisfiable dependency
    • libghc-generic-trie-prof/ppc64el has unsatisfiable dependency
    • libghc-generic-trie-dev/riscv64 has unsatisfiable dependency
    • libghc-generic-trie-prof/riscv64 has unsatisfiable dependency
    • libghc-generic-trie-dev/s390x has unsatisfiable dependency
    • libghc-generic-trie-prof/s390x has unsatisfiable dependency
    • Updating haskell-generic-trie would introduce bugs in testing: #1082348
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-generic-trie.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 589 days old (needed 5 days)
• haskell-geniplate-mirror (- to 0.7.9-1)
  • Migration status for haskell-geniplate-mirror (- to 0.7.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-geniplate-mirror-dev/amd64 has unsatisfiable dependency
    • libghc-geniplate-mirror-doc/amd64 has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/amd64 has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/arm64 has unsatisfiable dependency
    • libghc-geniplate-mirror-doc/arm64 has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/arm64 has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/armel has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/armel has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/armhf has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/armhf has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/i386 has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/i386 has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/mips64el has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/mips64el has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/ppc64el has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/ppc64el has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/riscv64 has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/riscv64 has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/s390x has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/s390x has unsatisfiable dependency
    • Updating haskell-geniplate-mirror would introduce bugs in testing: #1082349
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-geniplate-mirror.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 589 days old (needed 5 days)
• haskell-harp (- to 0.4.3.6-1)
  • Migration status for haskell-harp (- to 0.4.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-harp-dev/amd64 has unsatisfiable dependency
    • libghc-harp-doc/amd64 has unsatisfiable dependency
    • libghc-harp-prof/amd64 has unsatisfiable dependency
    • libghc-harp-dev/arm64 has unsatisfiable dependency
    • libghc-harp-doc/arm64 has unsatisfiable dependency
    • libghc-harp-prof/arm64 has unsatisfiable dependency
    • libghc-harp-dev/armel has unsatisfiable dependency
    • libghc-harp-prof/armel has unsatisfiable dependency
    • libghc-harp-dev/armhf has unsatisfiable dependency
    • libghc-harp-prof/armhf has unsatisfiable dependency
    • libghc-harp-dev/i386 has unsatisfiable dependency
    • libghc-harp-prof/i386 has unsatisfiable dependency
    • libghc-harp-dev/mips64el has unsatisfiable dependency
    • libghc-harp-prof/mips64el has unsatisfiable dependency
    • libghc-harp-dev/ppc64el has unsatisfiable dependency
    • libghc-harp-prof/ppc64el has unsatisfiable dependency
    • libghc-harp-dev/riscv64 has unsatisfiable dependency
    • libghc-harp-prof/riscv64 has unsatisfiable dependency
    • libghc-harp-dev/s390x has unsatisfiable dependency
    • libghc-harp-prof/s390x has unsatisfiable dependency
    • Updating haskell-harp would introduce bugs in testing: #1082350
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-harp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 589 days old (needed 5 days)
• haskell-bool-extras (- to 0.4.0-11)
  • Migration status for haskell-bool-extras (- to 0.4.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-bool-extras-doc/amd64 has unsatisfiable dependency
    • libghc-bool-extras-doc/arm64 has unsatisfiable dependency
    • Updating haskell-bool-extras would introduce bugs in testing: #1082343
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-bool-extras.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 590 days old (needed 5 days)
• haskell-failure (- to 0.2.0.3-12)
  • Migration status for haskell-failure (- to 0.2.0.3-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-failure-dev/amd64 has unsatisfiable dependency
    • libghc-failure-doc/amd64 has unsatisfiable dependency
    • libghc-failure-prof/amd64 has unsatisfiable dependency
    • libghc-failure-dev/arm64 has unsatisfiable dependency
    • libghc-failure-doc/arm64 has unsatisfiable dependency
    • libghc-failure-prof/arm64 has unsatisfiable dependency
    • libghc-failure-dev/armel has unsatisfiable dependency
    • libghc-failure-prof/armel has unsatisfiable dependency
    • libghc-failure-dev/armhf has unsatisfiable dependency
    • libghc-failure-prof/armhf has unsatisfiable dependency
    • libghc-failure-dev/i386 has unsatisfiable dependency
    • libghc-failure-prof/i386 has unsatisfiable dependency
    • libghc-failure-dev/mips64el has unsatisfiable dependency
    • libghc-failure-prof/mips64el has unsatisfiable dependency
    • libghc-failure-dev/ppc64el has unsatisfiable dependency
    • libghc-failure-prof/ppc64el has unsatisfiable dependency
    • libghc-failure-dev/riscv64 has unsatisfiable dependency
    • libghc-failure-prof/riscv64 has unsatisfiable dependency
    • libghc-failure-dev/s390x has unsatisfiable dependency
    • libghc-failure-prof/s390x has unsatisfiable dependency
    • Updating haskell-failure would introduce bugs in testing: #1082347
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-failure.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 590 days old (needed 5 days)
• haskell-hsp (- to 0.10.0-11)
  • Migration status for haskell-hsp (- to 0.10.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-hsp-dev/armel has unsatisfiable dependency
    • libghc-hsp-prof/armel has unsatisfiable dependency
    • libghc-hsp-dev/armhf has unsatisfiable dependency
    • libghc-hsp-prof/armhf has unsatisfiable dependency
    • libghc-hsp-dev/i386 has unsatisfiable dependency
    • libghc-hsp-prof/i386 has unsatisfiable dependency
    • libghc-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-hsp-dev/riscv64 has unsatisfiable dependency
    • libghc-hsp-prof/riscv64 has unsatisfiable dependency
    • libghc-hsp-dev/s390x has unsatisfiable dependency
    • libghc-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsp would introduce bugs in testing: #1082353
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 590 days old (needed 5 days)
• haskell-mime (- to 0.4.0.2-10)
  • Migration status for haskell-mime (- to 0.4.0.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-mime-doc/amd64 has unsatisfiable dependency
    • libghc-mime-doc/arm64 has unsatisfiable dependency
    • Updating haskell-mime would introduce bugs in testing: #1082534
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-mime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 590 days old (needed 5 days)
• haskell-mtlparse (- to 0.1.4.0-12)
  • Migration status for haskell-mtlparse (- to 0.1.4.0-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-mtlparse-doc/amd64 has unsatisfiable dependency
    • libghc-mtlparse-doc/arm64 has unsatisfiable dependency
    • Updating haskell-mtlparse would introduce bugs in testing: #1082535
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-mtlparse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 590 days old (needed 5 days)
• haskell-qrencode (- to 1.0.4-13)
  • Migration status for haskell-qrencode (- to 1.0.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-qrencode-doc/amd64 has unsatisfiable dependency
    • libghc-qrencode-doc/arm64 has unsatisfiable dependency
    • Updating haskell-qrencode would introduce bugs in testing: #1082563
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-qrencode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 590 days old (needed 5 days)
• haskell-readline (- to 1.0.3.0-13)
  • Migration status for haskell-readline (- to 1.0.3.0-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-readline-doc/amd64 has unsatisfiable dependency
    • libghc-readline-doc/arm64 has unsatisfiable dependency
    • Updating haskell-readline would introduce bugs in testing: #1082564
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-readline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 590 days old (needed 5 days)
• haskell-tagshare (- to 0.0-7)
  • Migration status for haskell-tagshare (- to 0.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-tagshare-dev/amd64 has unsatisfiable dependency
    • libghc-tagshare-doc/amd64 has unsatisfiable dependency
    • libghc-tagshare-prof/amd64 has unsatisfiable dependency
    • libghc-tagshare-dev/arm64 has unsatisfiable dependency
    • libghc-tagshare-doc/arm64 has unsatisfiable dependency
    • libghc-tagshare-prof/arm64 has unsatisfiable dependency
    • libghc-tagshare-dev/armel has unsatisfiable dependency
    • libghc-tagshare-prof/armel has unsatisfiable dependency
    • libghc-tagshare-dev/armhf has unsatisfiable dependency
    • libghc-tagshare-prof/armhf has unsatisfiable dependency
    • libghc-tagshare-dev/i386 has unsatisfiable dependency
    • libghc-tagshare-prof/i386 has unsatisfiable dependency
    • libghc-tagshare-dev/mips64el has unsatisfiable dependency
    • libghc-tagshare-prof/mips64el has unsatisfiable dependency
    • libghc-tagshare-dev/ppc64el has unsatisfiable dependency
    • libghc-tagshare-prof/ppc64el has unsatisfiable dependency
    • libghc-tagshare-dev/riscv64 has unsatisfiable dependency
    • libghc-tagshare-prof/riscv64 has unsatisfiable dependency
    • libghc-tagshare-dev/s390x has unsatisfiable dependency
    • libghc-tagshare-prof/s390x has unsatisfiable dependency
    • Updating haskell-tagshare would introduce bugs in testing: #1082565
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-tagshare.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 590 days old (needed 5 days)
• bind-dyndb-ldap (- to 11.10-6)
  • Migration status for bind-dyndb-ldap (- to 11.10-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bind9-dyndb-ldap/amd64 has unsatisfiable dependency
    • bind9-dyndb-ldap/arm64 has unsatisfiable dependency
    • bind9-dyndb-ldap/armel has unsatisfiable dependency
    • bind9-dyndb-ldap/armhf has unsatisfiable dependency
    • bind9-dyndb-ldap/i386 has unsatisfiable dependency
    • bind9-dyndb-ldap/mips64el has unsatisfiable dependency
    • bind9-dyndb-ldap/ppc64el has unsatisfiable dependency
    • bind9-dyndb-ldap/riscv64 has unsatisfiable dependency
    • bind9-dyndb-ldap/s390x has unsatisfiable dependency
    • Updating bind-dyndb-ldap would introduce bugs in testing: #1064294
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bind-dyndb-ldap.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 593 days old (needed 5 days)
• gosa-plugins-sudo (- to 2.8~git20211022.7ff3ed2-3)
  • Migration status for gosa-plugins-sudo (- to 2.8~git20211022.7ff3ed2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-sudo gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-sudo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 593 days old (needed 5 days)
• shapetools-tutorial (- to 1.3-6)
  • Migration status for shapetools-tutorial (- to 1.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: shapetools-tutorial shapetools (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 593 days old (needed 5 days)
• python-oauth2client (- to 4.1.3-5)
  • Migration status for python-oauth2client (- to 4.1.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-oauth2client would introduce bugs in testing: #1058392, #1066132
    • autopkgtest for python-oauth2client/4.1.3-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • 599 days old (needed 5 days)
• go-cve-dictionary (- to 0.3.1-5)
  • Migration status for go-cve-dictionary (- to 0.3.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating go-cve-dictionary would introduce bugs in testing: #1085476
    • Build-Depends(-Arch): go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Depends: go-cve-dictionary golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-cve-dictionary.html
    • autopkgtest for go-cve-dictionary/0.3.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 600 days old (needed 2 days)
• gost (- to 0.1.2-2)
  • Migration status for gost (- to 0.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gost would introduce bugs in testing: #1085479
    • Build-Depends(-Arch): gost golang-github-go-redis-redis (not considered)
    • Built-Using: gost golang-github-go-redis-redis (not considered)
    • Depends: gost golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gost.html
    • autopkgtest for gost/0.1.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 600 days old (needed 2 days)
• goval-dictionary (- to 0.2.0-6)
  • Migration status for goval-dictionary (- to 0.2.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating goval-dictionary would introduce bugs in testing: #1085471
    • Build-Depends(-Arch): goval-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: goval-dictionary golang-github-go-redis-redis (not considered)
    • Depends: goval-dictionary golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goval-dictionary.html
    • autopkgtest for goval-dictionary/0.2.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 600 days old (needed 2 days)
• go-exploitdb (- to 0.0~git20181130.7c961e7-3)
  • Migration status for go-exploitdb (- to 0.0~git20181130.7c961e7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating go-exploitdb would introduce bugs in testing: #1085478
    • Build-Depends(-Arch): go-exploitdb golang-github-go-redis-redis (not considered)
    • Built-Using: go-exploitdb golang-github-go-redis-redis (not considered)
    • Depends: go-exploitdb golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-exploitdb.html
    • autopkgtest for go-exploitdb/0.0~git20181130.7c961e7-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 601 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/armel has unsatisfiable dependency
    • libengine-gost-openssl/armel has unsatisfiable dependency
    • gostsum/armhf has unsatisfiable dependency
    • libengine-gost-openssl/armhf has unsatisfiable dependency
    • Updating libengine-gost-openssl would introduce bugs in testing: #1054922
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libengine-gost-openssl.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 602 days old (needed 5 days)
• xemacs21 (- to 21.4.24-12)
  • Migration status for xemacs21 (- to 21.4.24-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xemacs21 would introduce bugs in testing: #1075659, #1095538
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/armel
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/armhf
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/mips64el
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/riscv64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/s390x
    • autopkgtest for libwwwbrowser-perl/2.23-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • 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
    • 602 days old (needed 5 days)
• pseudo (- to 1.9.0+git20230301+ec6151a2b057-1)
  • Migration status for pseudo (- to 1.9.0+git20230301+ec6151a2b057-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pseudo would introduce bugs in testing: #1069487
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pseudo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 603 days old (needed 5 days)
• searx (- to 1.1.0+dfsg1-2)
  • Migration status for searx (- to 1.1.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating searx would introduce bugs in testing: #1051510
    • autopkgtest for searx/1.1.0+dfsg1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/searx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 603 days old (needed 5 days)
• arduino (- to 2:1.8.19+dfsg1-2)
  • Migration status for arduino (- to 2:1.8.19+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating arduino would introduce bugs in testing: #1099511
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 605 days old (needed 5 days)
• tomcatjss (- to 8.4.0-2)
  • Migration status for tomcatjss (- to 8.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomcatjss would introduce bugs in testing: #1031816
    • Build-Depends(-Arch): tomcatjss jss (not considered)
    • Depends: tomcatjss jss (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomcatjss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 606 days old (needed 5 days)
• chkservice (- to 0.3-1.1)
  • Migration status for chkservice (- to 0.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chkservice would introduce bugs in testing: #988094
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chkservice.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 612 days old (needed 5 days)
• linphone-desktop (- to 5.0.2-4)
  • Migration status for linphone-desktop (- to 5.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • linphone-desktop/amd64 has unsatisfiable dependency
    • linphone-desktop/arm64 has unsatisfiable dependency
    • linphone-desktop/armel has unsatisfiable dependency
    • linphone-desktop/armhf has unsatisfiable dependency
    • linphone-desktop/i386 has unsatisfiable dependency
    • linphone-desktop/mips64el has unsatisfiable dependency
    • linphone-desktop/ppc64el has unsatisfiable dependency
    • linphone-desktop/riscv64 has unsatisfiable dependency
    • linphone-desktop/s390x has unsatisfiable dependency
    • Updating linphone-desktop would introduce bugs in testing: #1100237
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linphone-desktop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 618 days old (needed 5 days)
• rust-tree-sitter-config (- to 0.19.0-3)
  • Migration status for rust-tree-sitter-config (- to 0.19.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-tree-sitter-config has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 621 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 ♻
    • 621 days old (needed 5 days)
• openmw (- to 0.48.0-1)
  • Migration status for openmw (- to 0.48.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openmw/amd64 has unsatisfiable dependency
    • openmw/arm64 has unsatisfiable dependency
    • openmw/armel has unsatisfiable dependency
    • openmw/armhf has unsatisfiable dependency
    • openmw/i386 has unsatisfiable dependency
    • openmw/mips64el has unsatisfiable dependency
    • openmw/s390x has unsatisfiable dependency
    • Updating openmw would introduce bugs in testing: #1072443, #1075344
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmw.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 626 days old (needed 5 days)
• openjdk-20 (- to 20.0.2+9-1)
  • Migration status for openjdk-20 (- to 20.0.2+9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openjdk-20-jre/armel has unsatisfiable dependency
    • openjdk-20-jre-headless/armel has unsatisfiable dependency
    • openjdk-20-jre/armhf has unsatisfiable dependency
    • openjdk-20-jre-headless/armhf has unsatisfiable dependency
    • Updating openjdk-20 would introduce bugs in testing: #1031889, #1069315
    • openjdk-20 unsatisfiable Build-Depends(-Arch) on armel: libgtk2.0-0 | libgtk-3-0
    • openjdk-20 unsatisfiable Build-Depends(-Arch) on armhf: libgtk2.0-0 | libgtk-3-0
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
    • autopkgtest for openjdk-20/20.0.2+9-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-20.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 627 days old (needed 5 days)
• python-tinyrpc (- to 0.6-5)
  • Migration status for python-tinyrpc (- to 0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-tinyrpc would introduce bugs in testing: #1084578, #1090165
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tinyrpc.html
    • autopkgtest for python-tinyrpc/0.6-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 627 days old (needed 5 days)
• debian-parl (- to 1.9.31+nmu1)
  • Migration status for debian-parl (- to 1.9.31+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debian-parl would introduce bugs in testing: #1081075
    • debian-parl unsatisfiable Build-Depends(-Arch) on amd64: boxer-data (<< 10.10)
    • Depends: debian-parl parcimonie (not considered)
    • Depends: debian-parl syncevolution
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-parl.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 629 days old (needed 5 days)
• iem-plugin-suite (- to 1.14.1-1)
  • Migration status for iem-plugin-suite (- to 1.14.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iem-plugin-suite would introduce bugs in testing: #1078519
    • iem-plugin-suite unsatisfiable Build-Depends(-Arch) on mips64el: juce-modules-source (>= 7.0.2~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iem-plugin-suite.html
    • 630 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
    • 633 days old (needed 5 days)
• rust-packed-simd (- to 0.3.8-1)
  • Migration status for rust-packed-simd (- to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-packed-simd would introduce bugs in testing: #1077952
    • autopkgtest for rust-packed-simd/0.3.8-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-packed-simd.html
    • 633 days old (needed 5 days)
• barrier (- to 2.4.0+dfsg-4)
  • Migration status for barrier (- to 2.4.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating barrier would introduce bugs in testing: #1057544
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/barrier.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 634 days old (needed 5 days)
• ruby-appraiser-rubocop (- to 1.0.1-2)
  • Migration status for ruby-appraiser-rubocop (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-appraiser-rubocop/amd64 has unsatisfiable dependency
    • ruby-appraiser-rubocop/arm64 has unsatisfiable dependency
    • Updating ruby-appraiser-rubocop would introduce bugs in testing: #1054166
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-appraiser-rubocop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 634 days old (needed 5 days)
• appdirs (- to 1.4.4-4)
  • Migration status for appdirs (- to 1.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating appdirs would introduce bugs in testing: #1060427
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appdirs.html
    • autopkgtest for appdirs/1.4.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 635 days old (needed 2 days)
• ruby-prometheus-client-mmap (- to 0.23.1-3)
  • Migration status for ruby-prometheus-client-mmap (- to 0.23.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-prometheus-client-mmap would introduce bugs in testing: #1075473
    • autopkgtest for ruby-prometheus-client-mmap/0.23.1-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: ruby-prometheus-client-mmap ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-prometheus-client-mmap.html
    • 635 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
    • autopkgtest for libsendmail-milter-perl/0.18-10: amd64: Regression or new test ♻, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsendmail-milter-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 638 days old (needed 5 days)
• ruby-benchmark-memory (- to 0.2.0-2)
  • Migration status for ruby-benchmark-memory (- to 0.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-benchmark-memory ruby-memory-profiler (not considered)
    • Depends: ruby-benchmark-memory ruby-memory-profiler (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-benchmark-memory.html
    • autopkgtest for ruby-benchmark-memory/0.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 640 days old (needed 2 days)
• ruby-rails-assets-jquery (- to 3.5.1+dfsg-2)
  • Migration status for ruby-rails-assets-jquery (- to 3.5.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-jquery would introduce bugs in testing: #1094741
    • autopkgtest for ruby-rails-assets-jquery/3.5.1+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-jquery.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 640 days old (needed 5 days)
• ruby-browser (- to 5.3.1-3)
  • Migration status for ruby-browser (- to 5.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-browser would introduce bugs in testing: #1094527
    • autopkgtest for ruby-browser/5.3.1-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-browser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 641 days old (needed 5 days)
• rust-tree-sitter (- to 0.20.10-1)
  • Migration status for rust-tree-sitter (- to 0.20.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-tree-sitter has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 641 days old (needed 5 days)
• php-gettext (- to 1.0.12-6)
  • Migration status for php-gettext (- to 1.0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-gettext would introduce bugs in testing: #1092095
    • autopkgtest for php-gettext/1.0.12-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-gettext.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 644 days old (needed 5 days)
• printrun (- to 2.0.1-1)
  • Migration status for printrun (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating printrun would introduce bugs in testing: #1050157, #1067982
    • Depends: printrun appdirs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/printrun.html
    • autopkgtest for printrun/2.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 645 days old (needed 2 days)
• fdm (- to 1.9+git20181219-1.1)
  • Migration status for fdm (- to 1.9+git20181219-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fdm would introduce bugs in testing: #1074950
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdm.html
    • 646 days old (needed 5 days)
• foxtrotgps (- to 1.2.2+bzr332-1)
  • Migration status for foxtrotgps (- to 1.2.2+bzr332-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating foxtrotgps would introduce bugs in testing: #967861
    • Build-Depends(-Arch): foxtrotgps libglade2 (not considered)
    • Depends: foxtrotgps libglade2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foxtrotgps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 654 days old (needed 5 days)
• golang-github-form3tech-oss-jwt-go (- to 3.2.3-2)
  • Migration status for golang-github-form3tech-oss-jwt-go (- to 3.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-form3tech-oss-jwt-go would introduce bugs in testing: #1038793, #1042736
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-form3tech-oss-jwt-go.html
    • autopkgtest for golang-github-form3tech-oss-jwt-go/3.2.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 657 days old (needed 2 days)
• gosa-plugins-netgroups (- to 2.8~git20211022.3b6449d-5)
  • Migration status for gosa-plugins-netgroups (- to 2.8~git20211022.3b6449d-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-netgroups gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-netgroups.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 658 days old (needed 5 days)
• python-django-ical (- to 1.9.2-1)
  • Migration status for python-django-ical (- to 1.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-ical would introduce bugs in testing: #1052796
    • autopkgtest for python-django-ical/1.9.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ical.html
    • 658 days old (needed 5 days)
• liboqs (- to 0.8.0-1)
  • Migration status for liboqs (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liboqs3/armel has unsatisfiable dependency
    • liboqs3/armhf has unsatisfiable dependency
    • Updating liboqs would introduce bugs in testing: #1000303, #1065802, #1073250, #1089185
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liboqs.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 662 days old (needed 5 days)
• ruby-fog-aliyun (- to 0.4.0-2)
  • Migration status for ruby-fog-aliyun (- 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(-Arch): ruby-fog-aliyun ruby-memory-profiler (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-fog-aliyun.html
    • autopkgtest for ruby-fog-aliyun/0.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 663 days old (needed 2 days)
• hijra (- to 1.0-4)
  • Migration status for hijra (- to 1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hijra would introduce bugs in testing: #1080610
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 665 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 ♻
    • 665 days old (needed 5 days)
• othman (- to 1.0.0-2)
  • Migration status for othman (- to 1.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating othman would introduce bugs in testing: #1080701
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 673 days old (needed 5 days)
• wmdate (- to 0.7-4.2)
  • Migration status for wmdate (- to 0.7-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wmdate would introduce bugs in testing: #1075642
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmdate.html
    • 691 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)
    • 692 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 692 days old (needed 5 days)
• wmmatrix (- to 0.2-12.2)
  • Migration status for wmmatrix (- to 0.2-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wmmatrix would introduce bugs in testing: #1066282
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmmatrix.html
    • 693 days old (needed 5 days)
• mate-equake-applet (- to 1.3.8.2-1.1)
  • Migration status for mate-equake-applet (- to 1.3.8.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mate-equake-applet/armel has unsatisfiable dependency
    • mate-equake-applet/armhf has unsatisfiable dependency
    • Updating mate-equake-applet would introduce bugs in testing: #1066183
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-equake-applet.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 700 days old (needed 5 days)
• regina-normal (- to 7.3-2)
  • Migration status for regina-normal (- to 7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • regina-normal/amd64 has unsatisfiable dependency
    • regina-normal/arm64 has unsatisfiable dependency
    • regina-normal/armel has unsatisfiable dependency
    • regina-normal/armhf has unsatisfiable dependency
    • regina-normal/i386 has unsatisfiable dependency
    • regina-normal/mips64el has unsatisfiable dependency
    • regina-normal/ppc64el has unsatisfiable dependency
    • regina-normal/s390x has unsatisfiable dependency
    • Updating regina-normal would introduce bugs in testing: #1037840
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/regina-normal.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 704 days old (needed 5 days)
• terminus (- to 2.3.1-1)
  • Migration status for terminus (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating terminus would introduce bugs in testing: #1075562
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/terminus.html
    • 710 days old (needed 5 days)
• ponyorm (- to 0.7.16+ds-3)
  • Migration status for ponyorm (- to 0.7.16+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ponyorm would introduce bugs in testing: #1056435
    • autopkgtest for ponyorm/0.7.16+ds-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ponyorm.html
    • 731 days old (needed 5 days)
• ocrfeeder (- to 0.8.5-1)
  • Migration status for ocrfeeder (- to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocrfeeder would introduce bugs in testing: #1074646, #1084529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocrfeeder.html
    • 744 days old (needed 5 days)
• gitlab-ci-multi-runner (- to 14.10.1-1)
  • Migration status for gitlab-ci-multi-runner (- to 14.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-ci-multi-runner would introduce bugs in testing: #1080062, #1086672
    • gitlab-runner/amd64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/arm64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/mips64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/ppc64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/s390x has unsatisfiable Built-Using on golang-1.19 1.19.6-2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
    • 747 days old (needed 5 days)
• ruby-omniauth-auth0 (- to 3.1.0-2)
  • Migration status for ruby-omniauth-auth0 (- to 3.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-auth0 would introduce bugs in testing: #1095381
    • autopkgtest for ruby-omniauth-auth0/3.1.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-auth0.html
    • Reproducible on armhf - info ♻
    • 748 days old (needed 5 days)
• lsh-utils (- to 2.1-14)
  • Migration status for lsh-utils (- to 2.1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lsh-client/armel has unsatisfiable dependency
    • lsh-server/armel has unsatisfiable dependency
    • lsh-utils/armel has unsatisfiable dependency
    • lsh-client/armhf has unsatisfiable dependency
    • lsh-server/armhf has unsatisfiable dependency
    • lsh-utils/armhf has unsatisfiable dependency
    • Updating lsh-utils would introduce bugs in testing: #1067313
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsh-utils.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 757 days old (needed 5 days)
• php-horde-kolab-storage (- to 2.2.4-5)
  • Migration status for php-horde-kolab-storage (- to 2.2.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-kolab-storage/2.2.4-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 757 days old (needed 5 days)
• searx-admin (- to 0.0~git20170823.95fe63b+ds-3)
  • Migration status for searx-admin (- to 0.0~git20170823.95fe63b+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for searx-admin/0.0~git20170823.95fe63b+ds-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: searx-admin searx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/searx-admin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 759 days old (needed 5 days)
• debian-pan (- to 0.4)
  • Migration status for debian-pan (- to 0.4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: debian-pan mathgl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-pan.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 764 days old (needed 5 days)
• mitmproxy (- to 8.1.1-2)
  • Migration status for mitmproxy (- to 8.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mitmproxy would introduce bugs in testing: #1071640
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mitmproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 767 days old (needed 5 days)
• debian-timeline (- to 46)
  • Migration status for debian-timeline (- to 46): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debian-timeline would introduce bugs in testing: #655664
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-timeline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 769 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
    • 774 days old (needed 5 days)
• vertx-docgen (- to 0.9.4-2)
  • Migration status for vertx-docgen (- to 0.9.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vertx-docgen would introduce bugs in testing: #1081475
    • Build-Depends(-Arch): vertx-docgen openjdk-11 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vertx-docgen.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 774 days old (needed 5 days)
• fava (- to 1.23.1+dfsg-1)
  • Migration status for fava (- to 1.23.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-fava/amd64 has unsatisfiable dependency
    • python3-fava/arm64 has unsatisfiable dependency
    • Updating fava would introduce bugs in testing: #1031724, #1071795
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/fava.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 776 days old (needed 5 days)
• python-lua (- to 0.6-1)
  • Migration status for python-lua (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-lua/0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lua.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 777 days old (needed 5 days)
• oregano (- to 0.84.41+dfsg.1-1.1)
  • Migration status for oregano (- to 0.84.41+dfsg.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oregano would introduce bugs in testing: #1051281, #1081089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oregano.html
    • 779 days old (needed 5 days)
• xserver-xorg-video-trident (- to 1:1.4.0-1)
  • Migration status for xserver-xorg-video-trident (- to 1:1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-trident would introduce bugs in testing: #1087037
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-trident.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 779 days old (needed 5 days)
• golang-github-crowdsecurity-go-cs-bouncer (- to 0.0.2-2)
  • Migration status for golang-github-crowdsecurity-go-cs-bouncer (- to 0.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-crowdsecurity-go-cs-bouncer crowdsec (not considered)
    • Depends: golang-github-crowdsecurity-go-cs-bouncer crowdsec (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-crowdsecurity-go-cs-bouncer.html
    • autopkgtest for golang-github-crowdsecurity-go-cs-bouncer/0.0.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 780 days old (needed 2 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 782 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 782 days old (needed 5 days)
• php-horde-kolab-session (- to 2.0.3-10)
  • Migration status for php-horde-kolab-session (- to 2.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kolab-session would introduce bugs in testing: #1089775
    • autopkgtest for php-horde-kolab-session/2.0.3-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 782 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 785 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 786 days old (needed 5 days)
• libgrokj2k (- to 10.0.5-1)
  • Migration status for libgrokj2k (- to 10.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libgrokj2k1/armhf has unsatisfiable dependency
    • Updating libgrokj2k would introduce bugs in testing: #1085165
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgrokj2k.html
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 788 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 788 days old (needed 5 days)
• samizdat (- to 0.7.1-3)
  • Migration status for samizdat (- to 0.7.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating samizdat would introduce bugs in testing: #1038848, #1093940
    • Build-Depends(-Arch): samizdat ruby-whitewash (not considered)
    • Depends: samizdat ruby-whitewash (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/samizdat.html
    • 788 days old (needed 5 days)
• adv-17v35x (- to 5.0.7.0-1)
  • Migration status for adv-17v35x (- to 5.0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating adv-17v35x would introduce bugs in testing: #1077217
    • autopkgtest for adv-17v35x/5.0.7.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adv-17v35x.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 789 days old (needed 5 days)
• ruby-rails-assets-jquery.slimscroll (- to 1.3.6+dfsg-4)
  • Migration status for ruby-rails-assets-jquery.slimscroll (- to 1.3.6+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-jquery.slimscroll would introduce bugs in testing: #1094450
    • autopkgtest for ruby-rails-assets-jquery.slimscroll/1.3.6+dfsg-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: ruby-rails-assets-jquery.slimscroll ruby-rails-assets-jquery (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-jquery.slimscroll.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 789 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 790 days old (needed 2 days)
• haskell-raaz (- to 0.2.1-2.1)
  • Migration status for haskell-raaz (- to 0.2.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-raaz-dev/amd64 has unsatisfiable dependency
    • libghc-raaz-doc/amd64 has unsatisfiable dependency
    • libghc-raaz-prof/amd64 has unsatisfiable dependency
    • libghc-raaz-dev/arm64 has unsatisfiable dependency
    • libghc-raaz-doc/arm64 has unsatisfiable dependency
    • libghc-raaz-prof/arm64 has unsatisfiable dependency
    • libghc-raaz-dev/armel has unsatisfiable dependency
    • libghc-raaz-prof/armel has unsatisfiable dependency
    • libghc-raaz-dev/armhf has unsatisfiable dependency
    • libghc-raaz-prof/armhf has unsatisfiable dependency
    • libghc-raaz-dev/i386 has unsatisfiable dependency
    • libghc-raaz-prof/i386 has unsatisfiable dependency
    • libghc-raaz-dev/mips64el has unsatisfiable dependency
    • libghc-raaz-prof/mips64el has unsatisfiable dependency
    • libghc-raaz-dev/ppc64el has unsatisfiable dependency
    • libghc-raaz-prof/ppc64el has unsatisfiable dependency
    • libghc-raaz-dev/riscv64 has unsatisfiable dependency
    • libghc-raaz-prof/riscv64 has unsatisfiable dependency
    • libghc-raaz-dev/s390x has unsatisfiable dependency
    • libghc-raaz-prof/s390x has unsatisfiable dependency
    • Updating haskell-raaz would introduce bugs in testing: #1053980, #1054978
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on riscv64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-raaz.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 790 days old (needed 5 days)
• ruby-arbre (- to 1.5.0-1)
  • Migration status for ruby-arbre (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-arbre would introduce bugs in testing: #1095379
    • autopkgtest for ruby-arbre/1.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • ruby-arbre unsatisfiable Build-Depends(-Arch) on amd64: ruby-activesupport (<< 2:7.1)
    • Impossible Depends: ruby-arbre -> ruby-activesupport/2:6.1.7.10+dfsg-1~deb12u1/amd64
    • Impossible Depends: ruby-arbre -> ruby-activesupport/2:6.1.7.10+dfsg-1~deb12u1/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-arbre.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 ♻
    • Reproducible on i386 - info ♻
    • 790 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 armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 790 days old (needed 5 days)
• segyio (- to 1.8.3-1.2)
  • Migration status for segyio (- to 1.8.3-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-segyio/amd64 has unsatisfiable dependency
    • python3-segyio/arm64 has unsatisfiable dependency
    • python3-segyio/armel has unsatisfiable dependency
    • python3-segyio/armhf has unsatisfiable dependency
    • python3-segyio/i386 has unsatisfiable dependency
    • python3-segyio/mips64el has unsatisfiable dependency
    • python3-segyio/ppc64el has unsatisfiable dependency
    • python3-segyio/riscv64 has unsatisfiable dependency
    • python3-segyio/s390x has unsatisfiable dependency
    • Updating segyio would introduce bugs in testing: #1055728
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/segyio.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 790 days old (needed 5 days)
• hyperspy (- to 1.7.3-1)
  • Migration status for hyperspy (- to 1.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyperspy would introduce bugs in testing: #1040332, #1041803
    • hyperspy unsatisfiable Build-Depends(-Arch) on amd64: python3-ptable
    • hyperspy unsatisfiable Build-Depends(-Arch) on ppc64el: python3-ptable
    • Build-Depends(-Arch): hyperspy numba (not considered)
    • Build-Depends(-Arch): hyperspy python-sparse (not considered)
    • Depends: hyperspy python-sparse (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyperspy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 791 days old (needed 5 days)
• ruby-gruff (- to 0.6.0-2)
  • Migration status for ruby-gruff (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gruff would introduce bugs in testing: #1054733
    • autopkgtest for ruby-gruff/0.6.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gruff.html
    • 791 days old (needed 5 days)
• drmaa (- to 0.7.9-3)
  • Migration status for drmaa (- to 0.7.9-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: drmaa gridengine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drmaa.html
    • autopkgtest for drmaa/0.7.9-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 792 days old (needed 5 days)
• phing (- to 2.17.4-1)
  • Migration status for phing (- to 2.17.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phing would introduce bugs in testing: #1091520
    • Build-Depends(-Arch): phing pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phing.html
    • autopkgtest for phing/2.17.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 792 days old (needed 5 days)
• pyemd (- to 0.5.1.54.g802fa86-2)
  • Migration status for pyemd (- to 0.5.1.54.g802fa86-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pyemd/amd64 has unsatisfiable dependency
    • python3-pyemd/arm64 has unsatisfiable dependency
    • python3-pyemd/armel has unsatisfiable dependency
    • python3-pyemd/armhf has unsatisfiable dependency
    • python3-pyemd/i386 has unsatisfiable dependency
    • python3-pyemd/mips64el has unsatisfiable dependency
    • python3-pyemd/ppc64el has unsatisfiable dependency
    • python3-pyemd/riscv64 has unsatisfiable dependency
    • python3-pyemd/s390x has unsatisfiable dependency
    • Updating pyemd would introduce bugs in testing: #1080277
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pyemd.html
    • 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 armel: 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 mips64el: 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 792 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
    • 792 days old (needed 5 days)
• r-cran-mockr (- to 0.2.1-1)
  • Migration status for r-cran-mockr (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-mockr would introduce bugs in testing: #1072631
    • autopkgtest for r-cran-mockr/0.2.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mockr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 792 days old (needed 5 days)
• xen-tools (- to 4.9.2-1)
  • Migration status for xen-tools (- to 4.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xen-tools would introduce bugs in testing: #1092454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xen-tools.html
    • autopkgtest for xen-tools/4.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 792 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
    • 793 days old (needed 5 days)
• xrdesktop (- to 0.15.1-5.1)
  • Migration status for xrdesktop (- to 0.15.1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xrdesktop would introduce bugs in testing: #1075679
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrdesktop.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 793 days old (needed 5 days)
• malai (- to 2.0+ds1-3)
  • Migration status for malai (- to 2.0+ds1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): malai jinput (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/malai.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 794 days old (needed 5 days)
• kotlinx-atomicfu (- to 0.11.12-2)
  • Migration status for kotlinx-atomicfu (- to 0.11.12-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): kotlinx-atomicfu kotlin (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlinx-atomicfu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 795 days old (needed 5 days)
• kotlinx-coroutines (- to 1.0.1-2)
  • Migration status for kotlinx-coroutines (- to 1.0.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): kotlinx-coroutines kotlin (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): kotlinx-coroutines kotlinx-atomicfu
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlinx-coroutines.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 795 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: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polyml.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 795 days old (needed 5 days)
• stumpwm (- to 2:22.11-3)
  • Migration status for stumpwm (- to 2:22.11-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stumpwm would introduce bugs in testing: #1090308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stumpwm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 796 days old (needed 5 days)
• gradle-kotlin-dsl (- to 0.13.2-5)
  • Migration status for gradle-kotlin-dsl (- to 0.13.2-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): gradle-kotlin-dsl kotlin (not considered)
    • Depends: gradle-kotlin-dsl kotlin (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gradle-kotlin-dsl.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 797 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
    • 797 days old (needed 5 days)
• gosa-plugins-pwreset (- to 2.8~git20211021.d93b138-4)
  • Migration status for gosa-plugins-pwreset (- to 2.8~git20211021.d93b138-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-pwreset gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-pwreset.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 798 days old (needed 5 days)
• 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 798 days old (needed 5 days)
• mvdsv (- to 0.35-6)
  • Migration status for mvdsv (- to 0.35-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mvdsv/amd64 has unsatisfiable dependency
    • mvdsv/arm64 has unsatisfiable dependency
    • mvdsv/armel has unsatisfiable dependency
    • mvdsv/armhf has unsatisfiable dependency
    • mvdsv/i386 has unsatisfiable dependency
    • mvdsv/mips64el has unsatisfiable dependency
    • mvdsv/ppc64el has unsatisfiable dependency
    • mvdsv/riscv64 has unsatisfiable dependency
    • mvdsv/s390x has unsatisfiable dependency
    • Updating mvdsv would introduce bugs in testing: #1050187
    • mvdsv unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mvdsv.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 800 days old (needed 5 days)
• ruby-whitewash (- to 2.1-2)
  • Migration status for ruby-whitewash (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-whitewash would introduce bugs in testing: #1091663
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-whitewash.html
    • Reproducible on armhf - info ♻
    • 800 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
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 days old (needed 5 days)
• php-horde-kolab-server (- to 2.0.5-10)
  • Migration status for php-horde-kolab-server (- to 2.0.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kolab-server would introduce bugs in testing: #1089774
    • autopkgtest for php-horde-kolab-server/2.0.5-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 days old (needed 5 days)
• gosa-plugins-mailaddress (- to 2.8~git20211027.08b10a2-2)
  • Migration status for gosa-plugins-mailaddress (- to 2.8~git20211027.08b10a2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-mailaddress gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-mailaddress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 days old (needed 5 days)
• ktx (- to 1.42+dfsg-3)
  • Migration status for ktx (- to 1.42+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ktx would introduce bugs in testing: #1071772
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktx.html
    • 802 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 days old (needed 5 days)
• php-horde-crypt (- to 2.7.12-9)
  • Migration status for php-horde-crypt (- to 2.7.12-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-crypt would introduce bugs in testing: #1089770
    • autopkgtest for php-horde-crypt/2.7.12-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 days old (needed 5 days)
• php-horde-rdo (- to 2.1.0-10)
  • Migration status for php-horde-rdo (- to 2.1.0-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-rdo/2.1.0-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 days old (needed 5 days)
• ruby-dataobjects-mysql (- to 0.10.17-4)
  • Migration status for ruby-dataobjects-mysql (- to 0.10.17-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-dataobjects-mysql/0.10.17-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-dataobjects-mysql ruby-dataobjects (not considered)
    • Depends: ruby-dataobjects-mysql ruby-dataobjects (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dataobjects-mysql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 802 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 days old (needed 5 days)
• php-horde-injector (- to 2.0.5-12)
  • Migration status for php-horde-injector (- to 2.0.5-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-injector would introduce bugs in testing: #1089773
    • autopkgtest for php-horde-injector/2.0.5-12: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 days old (needed 5 days)
• php-horde-itip (- to 2.1.2-9)
  • Migration status for php-horde-itip (- to 2.1.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-itip/2.1.2-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 days old (needed 5 days)
• php-horde-log (- to 2.3.0-9)
  • Migration status for php-horde-log (- to 2.3.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-log would introduce bugs in testing: #1089776
    • autopkgtest for php-horde-log/2.3.0-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 days old (needed 5 days)
• php-horde-mapi (- to 1.0.10-5)
  • Migration status for php-horde-mapi (- to 1.0.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mapi would introduce bugs in testing: #1089727
    • autopkgtest for php-horde-mapi/1.0.10-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 days old (needed 5 days)
• php-horde-mime (- to 2.11.2-2)
  • Migration status for php-horde-mime (- to 2.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mime would introduce bugs in testing: #1089777
    • autopkgtest for php-horde-mime/2.11.2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 days old (needed 5 days)
• php-horde-passwd (- to 5.0.7-9)
  • Migration status for php-horde-passwd (- to 5.0.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-passwd/5.0.7-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 days old (needed 5 days)
• php-horde-token (- to 2.0.9-9)
  • Migration status for php-horde-token (- to 2.0.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-token would introduce bugs in testing: #1089779
    • autopkgtest for php-horde-token/2.0.9-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 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
    • 804 days old (needed 5 days)
• php-horde-auth (- to 2.2.2-10)
  • Migration status for php-horde-auth (- to 2.2.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-auth would introduce bugs in testing: #1089768
    • autopkgtest for php-horde-auth/2.2.2-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 804 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 804 days old (needed 5 days)
• php-horde-compress (- to 2.2.4-3)
  • Migration status for php-horde-compress (- to 2.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-compress/2.2.4-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 804 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 804 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 804 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 804 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:
    • autopkgtest for php-horde-util/2.5.12-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 804 days old (needed 5 days)
• aribas (- to 1.65-1)
  • Migration status for aribas (- to 1.65-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aribas would introduce bugs in testing: #1074818
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aribas.html
    • autopkgtest for aribas/1.65-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 805 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 805 days old (needed 5 days)
• libembperl-perl (- to 2.5.0-17)
  • Migration status for libembperl-perl (- to 2.5.0-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libembperl-perl/amd64 has unsatisfiable dependency
    • libembperl-perl/arm64 has unsatisfiable dependency
    • libembperl-perl/armel has unsatisfiable dependency
    • libembperl-perl/armhf has unsatisfiable dependency
    • libembperl-perl/i386 has unsatisfiable dependency
    • libembperl-perl/mips64el has unsatisfiable dependency
    • libembperl-perl/ppc64el has unsatisfiable dependency
    • libembperl-perl/s390x has unsatisfiable dependency
    • Updating libembperl-perl would introduce bugs in testing: #1042845
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libe/libembperl-perl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 806 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 806 days old (needed 2 days)
• sfepy (- to 2021.4-4)
  • Migration status for sfepy (- to 2021.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-sfepy/amd64 has unsatisfiable dependency
    • python3-sfepy/arm64 has unsatisfiable dependency
    • python3-sfepy/mips64el has unsatisfiable dependency
    • python3-sfepy/ppc64el has unsatisfiable dependency
    • python3-sfepy/s390x has unsatisfiable dependency
    • Updating sfepy would introduce bugs in testing: #1056887, #1086578
    • Build-Depends(-Arch): sfepy mayavi2 (not considered)
    • Build-Depends(-Arch): sfepy python-sparse (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfepy.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 806 days old (needed 5 days)
• bustle (- to 0.8.0-2)
  • Migration status for bustle (- to 0.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bustle would introduce bugs in testing: #1084243, #1084512
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bustle.html
    • 807 days old (needed 5 days)
• php-horde-imap-client (- to 2.30.6-3)
  • Migration status for php-horde-imap-client (- to 2.30.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-imap-client/2.30.6-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 808 days old (needed 5 days)
• relion-cuda (- to 3.1.3-2)
  • Migration status for relion-cuda (- to 3.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • relion-cuda/amd64 has unsatisfiable dependency
    • relion-gui-cuda/amd64 has unsatisfiable dependency
    • Updating relion-cuda would introduce bugs in testing: #1036681, #1040128
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 810 days old (needed 5 days)
• latexdraw (- to 3.3.8+ds1-2)
  • Migration status for latexdraw (- to 3.3.8+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: latexdraw malai (not considered)
    • Depends: latexdraw malai (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latexdraw.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 811 days old (needed 5 days)
• vim-ultisnips (- to 3.2-2)
  • Migration status for vim-ultisnips (- to 3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vim-ultisnips would introduce bugs in testing: #1033510
    • autopkgtest for vim-ultisnips/3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-ultisnips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 812 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
    • Reproducible on armhf - info ♻
    • 816 days old (needed 5 days)
• ytcc (- to 2.6.1-1)
  • Migration status for ytcc (- to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ytcc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 816 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)
    • 819 days old (needed 5 days)
• organize (- to 2.4.0-1)
  • Migration status for organize (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating organize would introduce bugs in testing: #1080883, #1082579
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/organize.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 819 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)
    • 821 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 821 days old (needed 5 days)
• astunparse (- to 1.6.3-2)
  • Migration status for astunparse (- to 1.6.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating astunparse would introduce bugs in testing: #1082046
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astunparse.html
    • autopkgtest for astunparse/1.6.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 822 days old (needed 2 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)
    • 823 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)
    • 823 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)
    • 823 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)
    • 823 days old (needed 5 days)
• php-horde-activesync (- to 2.41.9-1)
  • Migration status for php-horde-activesync (- to 2.41.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-activesync/2.41.9-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 823 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 823 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)
    • 824 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 824 days old (needed 5 days)
• php-horde-turba (- to 4.2.29-2)
  • Migration status for php-horde-turba (- to 4.2.29-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-turba would introduce bugs in testing: #1064392
    • autopkgtest for php-horde-turba/4.2.29-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 824 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 825 days old (needed 5 days)
• ruby-influxdb (- to 0.8.1-2)
  • Migration status for ruby-influxdb (- to 0.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-influxdb would introduce bugs in testing: #1076919
    • autopkgtest for ruby-influxdb/0.8.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-influxdb.html
    • 825 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 826 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 826 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 828 days old (needed 5 days)
• php-horde-share (- to 2.2.0-9)
  • Migration status for php-horde-share (- to 2.2.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-share/2.2.0-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 828 days old (needed 5 days)
• 3depict (- to 0.0.23-2)
  • Migration status for 3depict (- to 0.0.23-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 3depict mathgl (not considered)
    • Depends: 3depict mathgl (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/3/3depict.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 829 days old (needed 5 days)
• php-sabre-vobject (- to 2.1.7-6.1)
  • Migration status for php-sabre-vobject (- to 2.1.7-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-vobject would introduce bugs in testing: #1052792
    • autopkgtest for php-sabre-vobject/2.1.7-6.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-vobject.html
    • 830 days old (needed 5 days)
• kbtin (- to 2.1-2)
  • Migration status for kbtin (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kbtin/armhf has unsatisfiable dependency
    • Updating kbtin would introduce bugs in testing: #1061076
    • autopkgtest for kbtin/2.1-2: amd64: Pass, arm64: Pass, armel: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kbtin.html
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 832 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 833 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 834 days old (needed 5 days)
• php-horde-prefs (- to 2.9.0-9)
  • Migration status for php-horde-prefs (- to 2.9.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-prefs/2.9.0-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 834 days old (needed 5 days)
• speedcrunch (- to 0.12.0-6)
  • Migration status for speedcrunch (- to 0.12.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): speedcrunch quark-sphinx-theme (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/speedcrunch.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 836 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 837 days old (needed 5 days)
• php-horde-history (- to 2.3.6-11)
  • Migration status for php-horde-history (- to 2.3.6-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-history/2.3.6-11: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 837 days old (needed 5 days)
• ball (- to 1.5.0+git20180813.37fc53c-11)
  • Migration status for ball (- to 1.5.0+git20180813.37fc53c-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ball sip4 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/ball.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 838 days old (needed 5 days)
• alsa-oss (- to 1.1.8-2)
  • Migration status for alsa-oss (- to 1.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • alsa-oss/armel has unsatisfiable dependency
    • alsa-oss/armhf has unsatisfiable dependency
    • Updating alsa-oss would introduce bugs in testing: #1066825
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alsa-oss.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 839 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 840 days old (needed 5 days)
• jamin (- to 0.98.9~git20170111~199091~repack1-2)
  • Migration status for jamin (- to 0.98.9~git20170111~199091~repack1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jamin would introduce bugs in testing: #1075099
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jamin.html
    • 840 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
    • 840 days old (needed 5 days)
• ruby-omniauth-openid (- to 2.0.1-2)
  • Migration status for ruby-omniauth-openid (- to 2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-openid would introduce bugs in testing: #1094566
    • autopkgtest for ruby-omniauth-openid/2.0.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-openid.html
    • Reproducible on armhf - info ♻
    • 845 days old (needed 5 days)
• atitvout (- to 0.4-13.2)
  • Migration status for atitvout (- to 0.4-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating atitvout would introduce bugs in testing: #1063644, #1099831
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 850 days old (needed 5 days)
• python-mockupdb (- to 1.8.0-4)
  • Migration status for python-mockupdb (- to 1.8.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-mockupdb would introduce bugs in testing: #1058189
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mockupdb.html
    • autopkgtest for python-mockupdb/1.8.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 852 days old (needed 5 days)
• sooperlooper (- to 1.7.8~dfsg0-2)
  • Migration status for sooperlooper (- to 1.7.8~dfsg0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sooperlooper would introduce bugs in testing: #1071364
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sooperlooper.html
    • 853 days old (needed 5 days)
• trimage (- to 1.0.6-2)
  • Migration status for trimage (- to 1.0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trimage would introduce bugs in testing: #1080828
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trimage.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 853 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
    • 856 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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 857 days old (needed 5 days)
• mpqc (- to 2.3.1-22)
  • Migration status for mpqc (- to 2.3.1-22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsc-dev/amd64 has unsatisfiable dependency
    • libsc7v5/amd64 has unsatisfiable dependency
    • mpqc/amd64 has unsatisfiable dependency
    • libsc-dev/arm64 has unsatisfiable dependency
    • libsc7v5/arm64 has unsatisfiable dependency
    • mpqc/arm64 has unsatisfiable dependency
    • libsc-dev/mips64el has unsatisfiable dependency
    • libsc7v5/mips64el has unsatisfiable dependency
    • mpqc/mips64el has unsatisfiable dependency
    • libsc-dev/ppc64el has unsatisfiable dependency
    • libsc7v5/ppc64el has unsatisfiable dependency
    • mpqc/ppc64el has unsatisfiable dependency
    • libsc-dev/riscv64 has unsatisfiable dependency
    • libsc7v5/riscv64 has unsatisfiable dependency
    • mpqc/riscv64 has unsatisfiable dependency
    • libsc-dev/s390x has unsatisfiable dependency
    • libsc7v5/s390x has unsatisfiable dependency
    • mpqc/s390x has unsatisfiable dependency
    • Updating mpqc would introduce bugs in testing: #1075293, #1077120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpqc.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 857 days old (needed 5 days)
• telepathy-haze (- to 0.8.1-0.1)
  • Migration status for telepathy-haze (- to 0.8.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telepathy-haze would introduce bugs in testing: #1075560
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telepathy-haze.html
    • 859 days old (needed 5 days)
• libapache-db-perl (- to 0.18-2)
  • Migration status for libapache-db-perl (- to 0.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libapache-db-perl/amd64 has unsatisfiable dependency
    • libapache-db-perl/arm64 has unsatisfiable dependency
    • libapache-db-perl/armel has unsatisfiable dependency
    • libapache-db-perl/armhf has unsatisfiable dependency
    • libapache-db-perl/i386 has unsatisfiable dependency
    • libapache-db-perl/mips64el has unsatisfiable dependency
    • libapache-db-perl/ppc64el has unsatisfiable dependency
    • libapache-db-perl/riscv64 has unsatisfiable dependency
    • libapache-db-perl/s390x has unsatisfiable dependency
    • Updating libapache-db-perl would introduce bugs in testing: #1040396
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/liba/libapache-db-perl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 860 days old (needed 5 days)
• djangorestframework-filters (- to 1.0.0.dev2-2)
  • Migration status for djangorestframework-filters (- to 1.0.0.dev2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating djangorestframework-filters would introduce bugs in testing: #1052818
    • autopkgtest for djangorestframework-filters/1.0.0.dev2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djangorestframework-filters.html
    • 862 days old (needed 5 days)
• octocatalog-diff (- to 2.1.0-1)
  • Migration status for octocatalog-diff (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octocatalog-diff would introduce bugs in testing: #1025300
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octocatalog-diff.html
    • autopkgtest for octocatalog-diff/2.1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 862 days old (needed 5 days)
• funguloids (- to 1.06-15)
  • Migration status for funguloids (- to 1.06-15): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): funguloids ogre-1.9 (not considered)
    • Depends: funguloids ogre-1.9 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/funguloids.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 863 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 864 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
    • 864 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsinventory-server php-imap (not considered)
    • Invalidated by dependency
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 865 days old (needed 5 days)
• python-certbot-dns-digitalocean (- to 2.0.0-1)
  • Migration status for python-certbot-dns-digitalocean (- to 2.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-digitalocean python-digitalocean (not considered)
    • Depends: python-certbot-dns-digitalocean python-digitalocean (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-digitalocean.html
    • autopkgtest for python-certbot-dns-digitalocean/2.0.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 866 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 ♻
    • 868 days old (needed 5 days)
• golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2)
  • Migration status for golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-leanovate-gopter/0.2.9+git20210201.bbbf00e-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-leanovate-gopter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 868 days old (needed 5 days)
• shush (- to 1.2.3-5.1)
  • Migration status for shush (- to 1.2.3-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • shush/amd64 has unsatisfiable dependency
    • shush/arm64 has unsatisfiable dependency
    • shush/armel has unsatisfiable dependency
    • shush/armhf has unsatisfiable dependency
    • shush/i386 has unsatisfiable dependency
    • shush/mips64el has unsatisfiable dependency
    • shush/ppc64el has unsatisfiable dependency
    • shush/riscv64 has unsatisfiable dependency
    • shush/s390x has unsatisfiable dependency
    • Updating shush would introduce bugs in testing: #999964
    • shush unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shush.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 869 days old (needed 5 days)
• osdsh (- to 0.7.0-11)
  • Migration status for osdsh (- to 0.7.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating osdsh would introduce bugs in testing: #1091062
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/osdsh.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 871 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: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 872 days old (needed 5 days)
• tipp (- to 1.0+dfsg-3)
  • Migration status for tipp (- to 1.0+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tipp sepp (not considered)
    • Depends: tipp sepp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tipp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 873 days old (needed 5 days)
• sip4 (- to 4.19.25+dfsg-5)
  • Migration status for sip4 (- to 4.19.25+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sip4 would introduce bugs in testing: #1059648, #1080800
    • autopkgtest for sip4/4.19.25+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sip4.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 876 days old (needed 5 days)
• between (- to 6+dfsg1-4)
  • Migration status for between (- to 6+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating between would introduce bugs in testing: #1072834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/between.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 881 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-rails-csrf-protection.html
    • Reproducible on armhf - info ♻
    • 881 days old (needed 5 days)
• py-rnp (- to 0.1.0+git20221014.01b7129-4)
  • Migration status for py-rnp (- to 0.1.0+git20221014.01b7129-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating py-rnp would introduce bugs in testing: #1058436
    • autopkgtest for py-rnp/0.1.0+git20221014.01b7129-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-rnp.html
    • 884 days old (needed 5 days)
• gamgi (- to 0.17.5-1)
  • Migration status for gamgi (- to 0.17.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gamgi gtkglext (not considered)
    • Depends: gamgi gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gamgi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 885 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
    • 885 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
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 885 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)
    • 886 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)
    • 886 days old (needed 5 days)
• xautolock (- to 1:2.2-8)
  • Migration status for xautolock (- to 1:2.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xautolock would introduce bugs in testing: #1070663
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xautolock.html
    • autopkgtest for xautolock/1:2.2-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 891 days old (needed 2 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
    • 903 days old (needed 5 days)
• dradio (- to 3.8-2.1)
  • Migration status for dradio (- to 3.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dradio/armel has unsatisfiable dependency
    • dradio/armhf has unsatisfiable dependency
    • Updating dradio would introduce bugs in testing: #1057554
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dradio.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 904 days old (needed 5 days)
• libextutils-cbuilder-perl (- to 0.280236-2)
  • Migration status for libextutils-cbuilder-perl (- to 0.280236-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libextutils-cbuilder-perl would introduce bugs in testing: #1060712
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libe/libextutils-cbuilder-perl.html
    • autopkgtest for libextutils-cbuilder-perl/0.280236-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 905 days old (needed 5 days)
• libbio-tools-run-alignment-tcoffee-perl (- to 1.7.4-3)
  • Migration status for libbio-tools-run-alignment-tcoffee-perl (- to 1.7.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libbio-tools-run-alignment-tcoffee-perl/1.7.4-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbio-tools-run-alignment-tcoffee-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 906 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
    • 907 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
    • 908 days old (needed 5 days)
• phabricator (- to 0~git20220903-2)
  • Migration status for phabricator (- to 0~git20220903-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phabricator would introduce bugs in testing: #1038843
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phabricator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 911 days old (needed 5 days)
• ruby-elasticsearch-model (- to 7.2.1-1)
  • Migration status for ruby-elasticsearch-model (- to 7.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-elasticsearch-model would introduce bugs in testing: #1064751
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-elasticsearch-model.html
    • autopkgtest for ruby-elasticsearch-model/7.2.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 914 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
    • 917 days old (needed 5 days)
• dvi2ps (- to 5.1j-1.5)
  • Migration status for dvi2ps (- to 5.1j-1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dvi2ps would introduce bugs in testing: #1066362
    • Build-Depends(-Arch): dvi2ps vflib3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvi2ps.html
    • 918 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
    • 918 days old (needed 5 days)
• vflib3 (- to 3.7.2+dfsg-0.1)
  • Migration status for vflib3 (- to 3.7.2+dfsg-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vflib3 would introduce bugs in testing: #1075620
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vflib3.html
    • 920 days old (needed 5 days)
• ruby-fog-rackspace (- to 0.1.6-4)
  • Migration status for ruby-fog-rackspace (- to 0.1.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-fog-rackspace would introduce bugs in testing: #1094116
    • autopkgtest for ruby-fog-rackspace/0.1.6-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-fog-rackspace.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 922 days old (needed 5 days)
• jzmq (- to 3.1.0-16)
  • Migration status for jzmq (- to 3.1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jzmq would introduce bugs in testing: #1053044
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jzmq.html
    • 923 days old (needed 5 days)
• netris (- to 0.52-11)
  • Migration status for netris (- to 0.52-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netris would introduce bugs in testing: #1075313
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netris.html
    • 925 days old (needed 5 days)
• php-fdomdocument (- to 1.6.7-2)
  • Migration status for php-fdomdocument (- to 1.6.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fdomdocument would introduce bugs in testing: #1082448, #813866
    • autopkgtest for php-fdomdocument/1.6.7-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-fdomdocument pdepend (not considered)
    • Build-Depends(-Arch): php-fdomdocument php-codesniffer (not considered)
    • Build-Depends(-Arch): php-fdomdocument phpcpd (not considered)
    • Build-Depends(-Arch): php-fdomdocument phploc (not considered)
    • Build-Depends(-Arch): php-fdomdocument phpmd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fdomdocument.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 931 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 armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 931 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 933 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/armel has unsatisfiable dependency
    • eclipse-titan/armhf has unsatisfiable dependency
    • eclipse-titan/i386 has unsatisfiable dependency
    • eclipse-titan/mips64el has unsatisfiable dependency
    • eclipse-titan/ppc64el has unsatisfiable dependency
    • eclipse-titan/riscv64 has unsatisfiable dependency
    • eclipse-titan/s390x has unsatisfiable dependency
    • Updating eclipse-titan would introduce bugs in testing: #1071679, #1089251
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-titan.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • New but not reproducible on armhf - info ♻
    • 935 days old (needed 5 days)
• qreator (- to 16.06.1-7.1)
  • Migration status for qreator (- to 16.06.1-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qreator would introduce bugs in testing: #1058246
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qreator.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 935 days old (needed 5 days)
• xserver-xorg-video-tdfx (- to 1:1.5.0-5)
  • Migration status for xserver-xorg-video-tdfx (- to 1:1.5.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-tdfx would introduce bugs in testing: #1087036
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-tdfx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 935 days old (needed 5 days)
• bing (- to 1.3.5-5)
  • Migration status for bing (- to 1.3.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bing would introduce bugs in testing: #1054398, #1071791
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bing.html
    • 936 days old (needed 5 days)
• xserver-xorg-input-aiptek (- to 1:1.4.1-4)
  • Migration status for xserver-xorg-input-aiptek (- to 1:1.4.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-input-aiptek would introduce bugs in testing: #1075678
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-input-aiptek.html
    • 936 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
    • 936 days old (needed 5 days)
• sagetex (- to 3.6.1+ds-1)
  • Migration status for sagetex (- to 3.6.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sagetex/3.6.1+ds-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): sagetex sagemath (not considered)
    • Depends: sagetex sagemath (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sagetex.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 940 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-easyrdf.html
    • 946 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: Regression or new test ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-lxc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 952 days old (needed 5 days)
• gnome-subtitles (- to 1.8-1)
  • Migration status for gnome-subtitles (- to 1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-subtitles would introduce bugs in testing: #1053529, #1067191, #1069308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-subtitles.html
    • 957 days old (needed 5 days)
• xstow (- to 1.1.0-1)
  • Migration status for xstow (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xstow would introduce bugs in testing: #1075685
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xstow.html
    • 963 days old (needed 5 days)
• ruby-omniauth-ldap (- to 2.2.0-1)
  • Migration status for ruby-omniauth-ldap (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-ldap would introduce bugs in testing: #1094518
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-ldap.html
    • autopkgtest for ruby-omniauth-ldap/2.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 965 days old (needed 2 days)
• ruby-grape-logging (- to 1.8.4-1)
  • Migration status for ruby-grape-logging (- to 1.8.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-grape-logging ruby-grape (not considered)
    • Depends: ruby-grape-logging ruby-grape (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-grape-logging.html
    • autopkgtest for ruby-grape-logging/1.8.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 967 days old (needed 2 days)
• node-mock-fs (- to 5.1.4-1)
  • Migration status for node-mock-fs (- to 5.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mock-fs would introduce bugs in testing: #1072601
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mock-fs.html
    • autopkgtest for node-mock-fs/5.1.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 968 days old (needed 5 days)
• diet-ng (- to 1.8.1-3)
  • Migration status for diet-ng (- to 1.8.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: diet-ng -> libphobos2-ldc-shared106/1:1.36.0-2.1/amd64
    • Impossible Depends: diet-ng -> libphobos2-ldc-shared106/1:1.36.0-2.1/arm64
    • Impossible Depends: diet-ng -> libphobos2-ldc-shared106/1:1.36.0-2.1/i386
    • Impossible Depends: diet-ng -> libphobos2-ldc-shared106/1:1.36.0-2.1/riscv64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diet-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 969 days old (needed 5 days)
• debian-design (- to 3.0.27)
  • Migration status for debian-design (- to 3.0.27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • design-desktop-graphics/amd64 has unsatisfiable dependency
    • design-desktop-graphics/arm64 has unsatisfiable dependency
    • Updating debian-design would introduce bugs in testing: #1081074, #1088060
    • debian-design unsatisfiable Build-Depends(-Arch) on amd64: boxer-data (<< 10.10)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-design.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 970 days old (needed 5 days)
• medialibrary (- to 0.12.3-1)
  • Migration status for medialibrary (- to 0.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating medialibrary would introduce bugs in testing: #1042710, #949532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/medialibrary.html
    • 972 days old (needed 5 days)
• haskell-hindent (- to 5.3.4-1)
  • Migration status for haskell-hindent (- to 5.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hindent-dev/amd64 has unsatisfiable dependency
    • libghc-hindent-doc/amd64 has unsatisfiable dependency
    • libghc-hindent-prof/amd64 has unsatisfiable dependency
    • libghc-hindent-dev/arm64 has unsatisfiable dependency
    • libghc-hindent-doc/arm64 has unsatisfiable dependency
    • libghc-hindent-prof/arm64 has unsatisfiable dependency
    • libghc-hindent-dev/armel has unsatisfiable dependency
    • libghc-hindent-prof/armel has unsatisfiable dependency
    • libghc-hindent-dev/armhf has unsatisfiable dependency
    • libghc-hindent-prof/armhf has unsatisfiable dependency
    • libghc-hindent-dev/i386 has unsatisfiable dependency
    • libghc-hindent-prof/i386 has unsatisfiable dependency
    • libghc-hindent-dev/mips64el has unsatisfiable dependency
    • libghc-hindent-prof/mips64el has unsatisfiable dependency
    • libghc-hindent-dev/ppc64el has unsatisfiable dependency
    • libghc-hindent-prof/ppc64el has unsatisfiable dependency
    • libghc-hindent-dev/riscv64 has unsatisfiable dependency
    • libghc-hindent-prof/riscv64 has unsatisfiable dependency
    • libghc-hindent-dev/s390x has unsatisfiable dependency
    • libghc-hindent-prof/s390x has unsatisfiable dependency
    • Updating haskell-hindent would introduce bugs in testing: #1053982
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hindent.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 982 days old (needed 5 days)
• haskell-x509-util (- to 1.6.6-1)
  • Migration status for haskell-x509-util (- to 1.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-x509-util would introduce bugs in testing: #1082922
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-x509-util.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 986 days old (needed 5 days)
• gcc-11-doc (- to 11.3.0-1)
  • Migration status for gcc-11-doc (- to 11.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11-doc would introduce bugs in testing: #1057560
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 994 days old (needed 5 days)
• parmetis (- to 4.0.3-7)
  • Migration status for parmetis (- to 4.0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parmetis would introduce bugs in testing: #1080199
    • autopkgtest for parmetis/4.0.3-7: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 995 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 999 days old (needed 5 days)
• php-horde-data (- to 2.1.5-3)
  • Migration status for php-horde-data (- to 2.1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-data would introduce bugs in testing: #1089772
    • autopkgtest for php-horde-data/2.1.5-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1001 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1001 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1001 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1001 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1005 days old (needed 5 days)
• ruby-eb (- to 2.6-4)
  • Migration status for ruby-eb (- to 2.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-eb would introduce bugs in testing: #1075457
    • Depends: ruby-eb ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-eb.html
    • 1012 days old (needed 5 days)
• dvbcut (- to 0.7.4-1)
  • Migration status for dvbcut (- to 0.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dvbcut/amd64 has unsatisfiable dependency
    • dvbcut/arm64 has unsatisfiable dependency
    • dvbcut/armel has unsatisfiable dependency
    • dvbcut/armhf has unsatisfiable dependency
    • dvbcut/i386 has unsatisfiable dependency
    • dvbcut/mips64el has unsatisfiable dependency
    • dvbcut/ppc64el has unsatisfiable dependency
    • dvbcut/riscv64 has unsatisfiable dependency
    • dvbcut/s390x has unsatisfiable dependency
    • Updating dvbcut would introduce bugs in testing: #1072411
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvbcut.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1016 days old (needed 5 days)
• ippsample (- to 0.0~git20220607.72f89b3-1)
  • Migration status for ippsample (- to 0.0~git20220607.72f89b3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ippsample/armel has unsatisfiable dependency
    • ippsample/armhf has unsatisfiable dependency
    • Updating ippsample would introduce bugs in testing: #1042570, #1069333
    • ippsample unsatisfiable Build-Depends(-Arch) on mips64el: libmupdf-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippsample.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 1022 days old (needed 5 days)
• quark-sphinx-theme (- to 0.5.1-3)
  • Migration status for quark-sphinx-theme (- to 0.5.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quark-sphinx-theme would introduce bugs in testing: #1042679
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quark-sphinx-theme.html
    • 1022 days old (needed 5 days)
• php-sql-formatter (- to 1.2.17+dct1.1.3-1)
  • Migration status for php-sql-formatter (- to 1.2.17+dct1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sql-formatter would introduce bugs in testing: #1064641, #1073571
    • autopkgtest for php-sql-formatter/1.2.17+dct1.1.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sql-formatter.html
    • 1023 days old (needed 5 days)
• gamehub (- to 0.16.3-2-master+ds-1)
  • Migration status for gamehub (- to 0.16.3-2-master+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gamehub/riscv64 has unsatisfiable dependency
    • Updating gamehub would introduce bugs in testing: #1063232
    • gamehub unsatisfiable Build-Depends(-Arch) on amd64: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on arm64: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on armel: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on armhf: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on i386: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on mips64el: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on ppc64el: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on riscv64: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on s390x: libwebkit2gtk-4.0-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gamehub.html
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1027 days old (needed 5 days)
• howdoi (- to 1.1.9-1.1)
  • Migration status for howdoi (- to 1.1.9-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating howdoi would introduce bugs in testing: #1051370
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/howdoi.html
    • autopkgtest for howdoi/1.1.9-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1029 days old (needed 2 days)
• lice5 (- to 1:5.3.0-1.1)
  • Migration status for lice5 (- to 1:5.3.0-1.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lice5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• php-letodms-core (- to 3.4.2-1.1)
  • Migration status for php-letodms-core (- to 3.4.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-letodms-core would introduce bugs in testing: #1065716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-letodms-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• php-mdb2 (- to 2.5.0b5-2.1)
  • Migration status for php-mdb2 (- to 2.5.0b5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-mdb2 would introduce bugs in testing: #1065705
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mdb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• php-mdb2-driver-mysql (- to 1.5.0b4-2.1)
  • Migration status for php-mdb2-driver-mysql (- to 1.5.0b4-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-mdb2-driver-mysql php-mdb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mdb2-driver-mysql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• php-mdb2-driver-pgsql (- to 1.5.0b4-2.1)
  • Migration status for php-mdb2-driver-pgsql (- to 1.5.0b4-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-mdb2-driver-pgsql php-mdb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mdb2-driver-pgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• php-net-dime (- to 1.0.2-3.1)
  • Migration status for php-net-dime (- to 1.0.2-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-dime would introduce bugs in testing: #1065719
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-dime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• php-net-publicsuffix (- to 0.2-1.1)
  • Migration status for php-net-publicsuffix (- to 0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-publicsuffix would introduce bugs in testing: #1090260
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-publicsuffix.html
    • 1029 days old (needed 5 days)
• php-net-url (- to 1.0.15-4.1)
  • Migration status for php-net-url (- to 1.0.15-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-url would introduce bugs in testing: #1093492
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-url.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• ruby-devise-token-authenticatable (- to 0.5.2-1.1)
  • Migration status for ruby-devise-token-authenticatable (- to 0.5.2-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-devise-token-authenticatable ruby-devise (not considered)
    • Depends: ruby-devise-token-authenticatable ruby-devise (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-devise-token-authenticatable.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• python-pyepsg (- to 0.4.0-1)
  • Migration status for python-pyepsg (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyepsg would introduce bugs in testing: #1033851
    • autopkgtest for python-pyepsg/0.4.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyepsg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1032 days old (needed 5 days)
• ruby-backbone-on-rails (- to 1.4.1+dfsg-1)
  • Migration status for ruby-backbone-on-rails (- to 1.4.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-backbone-on-rails/1.4.1+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-backbone-on-rails ruby-rails-assets-underscore (not considered)
    • Depends: ruby-backbone-on-rails ruby-rails-assets-underscore (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-backbone-on-rails.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1040 days old (needed 5 days)
• ruby-entypo-rails (- to 3.0.0-4)
  • Migration status for ruby-entypo-rails (- to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-entypo-rails would introduce bugs in testing: #1094819, #1100304
    • autopkgtest for ruby-entypo-rails/3.0.0-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Impossible Depends: ruby-entypo-rails -> ruby-railties/2:6.1.7.10+dfsg-1~deb12u1/amd64
    • Impossible Depends: ruby-entypo-rails -> ruby-railties/2:6.1.7.10+dfsg-1~deb12u1/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-entypo-rails.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1040 days old (needed 5 days)
• ruby-rails-assets-markdown-it (- to 8.4.2-6)
  • Migration status for ruby-rails-assets-markdown-it (- to 8.4.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-markdown-it would introduce bugs in testing: #1095463
    • autopkgtest for ruby-rails-assets-markdown-it/8.4.2-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-markdown-it.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1040 days old (needed 5 days)
• rust-ioctl-sys (- to 0.8.0-1)
  • Migration status for rust-ioctl-sys (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ioctl-sys/0.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ioctl-sys.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1041 days old (needed 5 days)
• pfqueue (- to 0.5.6-9.2)
  • Migration status for pfqueue (- to 0.5.6-9.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pfqueue would introduce bugs in testing: #1066631
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pfqueue.html
    • 1048 days old (needed 5 days)
• lwjgl (- to 2.9.3+dfsg-6)
  • Migration status for lwjgl (- to 2.9.3+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lwjgl jinput (not considered)
    • Depends: lwjgl jinput (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lwjgl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1051 days old (needed 5 days)
• python-cx-oracle (- to 8.3.0-3)
  • Migration status for python-cx-oracle (- to 8.3.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-cx-oracle odpic (not considered)
    • Depends: python-cx-oracle odpic (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for python-cx-oracle/8.3.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1053 days old (needed 5 days)
• rust-tree-sitter-tags (- to 0.20.2-1)
  • Migration status for rust-tree-sitter-tags (- to 0.20.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-tree-sitter-tags has no binaries on any arch
    • rust-tree-sitter-tags unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.20+default-dev
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1059 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
    • 1062 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
    • 1062 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
    • 1062 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
    • 1064 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
    • 1064 days old (needed 5 days)
• openjdk-11-jre-dcevm (- to 11.0.15+1-1)
  • Migration status for openjdk-11-jre-dcevm (- to 11.0.15+1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for openjdk-11-jre-dcevm/11.0.15+1-1: amd64: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): openjdk-11-jre-dcevm openjdk-11 (not considered)
    • Depends: openjdk-11-jre-dcevm openjdk-11 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11-jre-dcevm.html
    • New but not reproducible on amd64 - info ♻
    • 1070 days old (needed 5 days)
• r-cran-zelig (- to 5.1.7-3)
  • Migration status for r-cran-zelig (- to 5.1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-zelig/5.1.7-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-zelig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1073 days old (needed 5 days)
• unburden-home-dir (- to 0.4.2)
  • Migration status for unburden-home-dir (- to 0.4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unburden-home-dir would introduce bugs in testing: #1073114
    • autopkgtest for unburden-home-dir/0.4.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1077 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)
    • 1081 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)
    • 1081 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 armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for coyote/2022.04.12-1: amd64: Pass, arm64: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1090 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1092 days old (needed 5 days)
• synfigstudio (- to 1.5.1-1)
  • Migration status for synfigstudio (- to 1.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): synfigstudio synfig (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synfigstudio.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1093 days old (needed 5 days)
• android-platform-dalvik (- to 10.0.0+r36-4)
  • Migration status for android-platform-dalvik (- to 10.0.0+r36-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: android-platform-dalvik android-framework-23 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-dalvik.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1096 days old (needed 5 days)
• ruby-fakeredis (- to 0.8.0-7)
  • Migration status for ruby-fakeredis (- to 0.8.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-fakeredis would introduce bugs in testing: #1084361
    • autopkgtest for ruby-fakeredis/0.8.0-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-fakeredis.html
    • 1099 days old (needed 5 days)
• gtk-vector-screenshot (- to 0.3.3-2)
  • Migration status for gtk-vector-screenshot (- to 0.3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtk-vector-screenshot would introduce bugs in testing: #1075051
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-vector-screenshot.html
    • 1101 days old (needed 5 days)
• ruby-devise-two-factor (- to 4.0.2-1)
  • Migration status for ruby-devise-two-factor (- to 4.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-devise-two-factor would introduce bugs in testing: #1082382, #1084360
    • autopkgtest for ruby-devise-two-factor/4.0.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-devise-two-factor ruby-devise (not considered)
    • Depends: ruby-devise-two-factor ruby-devise (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-devise-two-factor.html
    • 1102 days old (needed 5 days)
• hackage-tracker (- to 0.1.1)
  • Migration status for hackage-tracker (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hackage-tracker would introduce bugs in testing: #1091077
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hackage-tracker.html
    • 1104 days old (needed 5 days)
• prelude-lml (- to 5.2.0-3)
  • Migration status for prelude-lml (- to 5.2.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): prelude-lml libprelude (not considered)
    • Depends: prelude-lml libprelude (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-lml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1121 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1126 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1126 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1126 days old (needed 5 days)
• python-dmsh (- to 0.2.19-1)
  • Migration status for python-dmsh (- to 0.2.19-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-dmsh python-meshplex (not considered)
    • Depends: python-dmsh python-meshplex (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dmsh.html
    • autopkgtest for python-dmsh/0.2.19-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1132 days old (needed 2 days)
• kickoff (- to 0.1.1)
  • Migration status for kickoff (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kickoff would introduce bugs in testing: #1091059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kickoff.html
    • Reproducible on armhf - info ♻
    • 1135 days old (needed 5 days)
• emacs-lintian (- to 0.1.1)
  • Migration status for emacs-lintian (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-lintian would introduce bugs in testing: #1077105
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-lintian.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1140 days old (needed 5 days)
• freeart (- to 3.3.0+ds1-3)
  • Migration status for freeart (- to 3.3.0+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-freeart/amd64 has unsatisfiable dependency
    • python3-freeart/arm64 has unsatisfiable dependency
    • python3-freeart/armel has unsatisfiable dependency
    • python3-freeart/armhf has unsatisfiable dependency
    • python3-freeart/i386 has unsatisfiable dependency
    • python3-freeart/mips64el has unsatisfiable dependency
    • python3-freeart/ppc64el has unsatisfiable dependency
    • Updating freeart would introduce bugs in testing: #1013606, #1056801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/freeart.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 1146 days old (needed 5 days)
• node-functional.js (- to 0.8.0-1)
  • Migration status for node-functional.js (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-functional.js would introduce bugs in testing: #1014605
    • Not built on buildd: arch all binaries uploaded by stephanlachnit@protonmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-functional.js.html
    • autopkgtest for node-functional.js/0.8.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1150 days old (needed 5 days)
• node-grunt-timer (- to 0.6.0-1)
  • Migration status for node-grunt-timer (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by stephanlachnit@protonmail.com, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): node-grunt-timer node-functional.js (not considered)
    • Depends: node-grunt-timer node-functional.js (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-grunt-timer.html
    • autopkgtest for node-grunt-timer/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1150 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
    • 1154 days old (needed 5 days)
• asterisk-flite (- to 3.0-4)
  • Migration status for asterisk-flite (- to 3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): asterisk-flite asterisk (not considered)
    • Depends: asterisk-flite asterisk (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-flite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1157 days old (needed 5 days)
• tomogui (- to 0.3.1-2)
  • Migration status for tomogui (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomogui would introduce bugs in testing: #1069226
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tomogui.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1161 days old (needed 5 days)
• dumpasn1 (- to 20210212-3)
  • Migration status for dumpasn1 (- to 20210212-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dumpasn1 would introduce bugs in testing: #1060766
    • autopkgtest for dumpasn1/20210212-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dumpasn1.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1166 days old (needed 5 days)
• rust-proc-quote (- to 0.4.0-1)
  • Migration status for rust-proc-quote (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-proc-quote/0.4.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-quote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1166 days old (needed 5 days)
• ruby-redis-activesupport (- to 5.3.0-1)
  • Migration status for ruby-redis-activesupport (- to 5.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-activesupport would introduce bugs in testing: #1084364
    • autopkgtest for ruby-redis-activesupport/5.3.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-activesupport.html
    • 1172 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
    • 1175 days old (needed 5 days)
• nim-lapper (- to 0.1.7-5)
  • Migration status for nim-lapper (- to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nim-lapper/0.1.7-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): nim-lapper nim (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-lapper.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1176 days old (needed 5 days)
• idseq-bench (- to 0.0~git20210602.27fb6dc-1)
  • Migration status for idseq-bench (- to 0.0~git20210602.27fb6dc-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for idseq-bench/0.0~git20210602.27fb6dc-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idseq-bench.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1177 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)
    • 1181 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
    • Reproducible on armhf - info ♻
    • 1181 days old (needed 5 days)
• growlight (- to 1.2.38-5)
  • Migration status for growlight (- to 1.2.38-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): growlight notcurses (not considered)
    • Depends: growlight notcurses (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/growlight.html
    • autopkgtest for growlight/1.2.38-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1182 days old (needed 2 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 in progress (will not be considered a regression), arm64: Test in progress (will not be considered a regression), armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress (will not be considered a regression), s390x: Test in progress (will not be considered a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1186 days old (needed 5 days)
• mlton (- to 20210117+dfsg-3)
  • Migration status for mlton (- to 20210117+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlton would introduce bugs in testing: #917644, #998156
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch arm64 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch armel binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch armhf binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch i386 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch mips64el binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch s390x binaries uploaded by ryanakca@kubuntu.org
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlton.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1188 days old (needed 5 days)
• tf (- to 1:4.0s1-21.1)
  • Migration status for tf (- to 1:4.0s1-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tf would introduce bugs in testing: #1066561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tf.html
    • 1189 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-charmbracelet-wish.html
    • autopkgtest for golang-github-charmbracelet-wish/0.1.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1191 days old (needed 2 days)
• mhddfs (- to 0.1.39+nmu2)
  • Migration status for mhddfs (- to 0.1.39+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mhddfs would introduce bugs in testing: #953919
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mhddfs.html
    • 1191 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: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-duckpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1191 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 armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): tiledarray btas (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledarray.html
    • 1191 days old (needed 5 days)
• php-fxsl (- to 1.1.1-6)
  • Migration status for php-fxsl (- to 1.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fxsl would introduce bugs in testing: #813865
    • autopkgtest for php-fxsl/1.1.1-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-fxsl pdepend (not considered)
    • Build-Depends(-Arch): php-fxsl php-codesniffer (not considered)
    • Build-Depends(-Arch): php-fxsl phpcpd (not considered)
    • Build-Depends(-Arch): php-fxsl phploc (not considered)
    • Build-Depends(-Arch): php-fxsl phpmd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fxsl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1193 days old (needed 5 days)
• rust-tree-sitter-highlight (- to 0.20.1-1)
  • Migration status for rust-tree-sitter-highlight (- to 0.20.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-tree-sitter-highlight has no binaries on any arch
    • rust-tree-sitter-highlight unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.20+default-dev
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1196 days old (needed 5 days)
• ssed (- to 3.62-8)
  • Migration status for ssed (- to 3.62-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ssed would introduce bugs in testing: #1066373
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssed.html
    • autopkgtest for ssed/3.62-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1197 days old (needed 2 days)
• ippl (- to 1.4.14-13)
  • Migration status for ippl (- to 1.4.14-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ippl would introduce bugs in testing: #1066218
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippl.html
    • 1201 days old (needed 5 days)
• magic (- to 8.3.105+ds.1-1.1)
  • Migration status for magic (- to 8.3.105+ds.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating magic would introduce bugs in testing: #1075249
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magic.html
    • 1204 days old (needed 5 days)
• kore (- to 4.1.0-6)
  • Migration status for kore (- to 4.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kore would introduce bugs in testing: #1033711, #1081081
    • autopkgtest for kore/4.1.0-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kore.html
    • 1206 days old (needed 5 days)
• morla (- to 0.16.1-2)
  • Migration status for morla (- to 0.16.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating morla would introduce bugs in testing: #1075286
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morla.html
    • 1207 days old (needed 5 days)
• pixmap (- to 2.6.6-1)
  • Migration status for pixmap (- to 2.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pixmap/armel has unsatisfiable dependency
    • pixmap/armhf has unsatisfiable dependency
    • Updating pixmap would introduce bugs in testing: #1054698
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pixmap.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1208 days old (needed 5 days)
• erlang-poolboy (- to 1.5.2+dfsg-2)
  • Migration status for erlang-poolboy (- to 1.5.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for erlang-poolboy/1.5.2+dfsg-2: amd64: Pass, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-poolboy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1214 days old (needed 5 days)
• ruby-atlassian-jwt (- to 0.2.1-1)
  • Migration status for ruby-atlassian-jwt (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-atlassian-jwt would introduce bugs in testing: #1078646
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-atlassian-jwt.html
    • autopkgtest for ruby-atlassian-jwt/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1218 days old (needed 2 days)
• ruby-puma-worker-killer (- to 0.3.1-3)
  • Migration status for ruby-puma-worker-killer (- to 0.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-puma-worker-killer would introduce bugs in testing: #1093924
    • autopkgtest for ruby-puma-worker-killer/0.3.1-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-puma-worker-killer.html
    • 1224 days old (needed 5 days)
• ruby-rails-controller-testing (- to 1.0.5-2)
  • Migration status for ruby-rails-controller-testing (- to 1.0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-controller-testing would introduce bugs in testing: #1094552
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-controller-testing.html
    • autopkgtest for ruby-rails-controller-testing/1.0.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1225 days old (needed 2 days)
• ruby-inherited-resources (- to 1.13.0-1)
  • Migration status for ruby-inherited-resources (- to 1.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-inherited-resources would introduce bugs in testing: #1094550
    • autopkgtest for ruby-inherited-resources/1.13.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • ruby-inherited-resources unsatisfiable Build-Depends(-Arch) on amd64: ruby-actionpack (<< 2:6.2)
    • ruby-inherited-resources unsatisfiable Build-Depends(-Arch) on amd64: ruby-activemodel (<< 2:6.2)
    • ruby-inherited-resources unsatisfiable Build-Depends(-Arch) on amd64: ruby-railties (<< 2:6.2)
    • Impossible Depends: ruby-inherited-resources -> ruby-actionpack/2:6.1.7.10+dfsg-1~deb12u1/amd64
    • Impossible Depends: ruby-inherited-resources -> ruby-actionpack/2:6.1.7.10+dfsg-1~deb12u1/arm64
    • Impossible Depends: ruby-inherited-resources -> ruby-railties/2:6.1.7.10+dfsg-1~deb12u1/amd64
    • Impossible Depends: ruby-inherited-resources -> ruby-railties/2:6.1.7.10+dfsg-1~deb12u1/arm64
    • Build-Depends(-Arch): ruby-inherited-resources ruby-rails-controller-testing (not considered)
    • Build-Depends(-Arch): ruby-inherited-resources ruby-responders (not considered)
    • Depends: ruby-inherited-resources ruby-responders (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-inherited-resources.html
    • 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 ♻
    • Reproducible on armhf - info ♻
    • 1226 days old (needed 5 days)
• ruby-joiner (- to 0.6.0-1)
  • Migration status for ruby-joiner (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-joiner would introduce bugs in testing: #1093923
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-joiner.html
    • autopkgtest for ruby-joiner/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1226 days old (needed 2 days)
• php-sabredav (- to 1.8.12-10)
  • Migration status for php-sabredav (- to 1.8.12-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabredav would introduce bugs in testing: #1070597
    • autopkgtest for php-sabredav/1.8.12-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-sabredav php-sabre-vobject (not considered)
    • Depends: php-sabredav php-sabre-vobject (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabredav.html
    • Reproducible on armhf - info ♻
    • 1229 days old (needed 5 days)
• ruby-i18n-inflector-rails (- to 1.0.7-5)
  • Migration status for ruby-i18n-inflector-rails (- to 1.0.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-i18n-inflector-rails would introduce bugs in testing: #1094535
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-i18n-inflector-rails.html
    • autopkgtest for ruby-i18n-inflector-rails/1.0.7-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1229 days old (needed 2 days)
• node-mongodb (- to 3.6.4+~cs11.13.19-2)
  • Migration status for node-mongodb (- to 3.6.4+~cs11.13.19-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mongodb would introduce bugs in testing: #1033817
    • autopkgtest for node-mongodb/3.6.4+~cs11.13.19-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mongodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1234 days old (needed 5 days)
• ruby-api-pagination (- to 4.8.2-2)
  • Migration status for ruby-api-pagination (- to 4.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-api-pagination would introduce bugs in testing: #1092690
    • autopkgtest for ruby-api-pagination/4.8.2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-api-pagination ruby-grape (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-api-pagination.html
    • Reproducible on armhf - info ♻
    • 1234 days old (needed 5 days)
• materialize (- to 1.1.0~alpha+ds-1)
  • Migration status for materialize (- to 1.1.0~alpha+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating materialize would introduce bugs in testing: #1012320
    • materialize unsatisfiable Build-Depends(-Arch) on amd64: libjs-anime
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/materialize.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1235 days old (needed 5 days)
• ruby-responders (- to 3.0.1-2)
  • Migration status for ruby-responders (- to 3.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-responders would introduce bugs in testing: #1095385, #1095456
    • autopkgtest for ruby-responders/3.0.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-responders ruby-rails-controller-testing (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-responders.html
    • Reproducible on armhf - info ♻
    • 1235 days old (needed 5 days)
• node-solid-keychain (- to 0.1.3-3.1)
  • Migration status for node-solid-keychain (- to 0.1.3-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-solid-keychain would introduce bugs in testing: #1071803
    • autopkgtest for node-solid-keychain/0.1.3-3.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): node-solid-keychain node-trust-webcrypto (not considered)
    • Depends: node-solid-keychain node-trust-webcrypto (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-solid-keychain.html
    • 1239 days old (needed 5 days)
• ruby-roxml (- to 4.2.0-1)
  • Migration status for ruby-roxml (- to 4.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-roxml would introduce bugs in testing: #1050580
    • autopkgtest for ruby-roxml/4.2.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-roxml.html
    • 1243 days old (needed 5 days)
• jarchivelib (- to 1.2.0-2)
  • Migration status for jarchivelib (- to 1.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jarchivelib would introduce bugs in testing: #1086277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jarchivelib.html
    • Reproducible on armhf - info ♻
    • 1246 days old (needed 5 days)
• golang-github-intel-go-cpuid (- to 0.0~git20210602.5747e5c-2)
  • Migration status for golang-github-intel-go-cpuid (- to 0.0~git20210602.5747e5c-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-intel-go-cpuid/0.0~git20210602.5747e5c-2: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-intel-go-cpuid.html
    • Reproducible on amd64 - info ♻
    • 1249 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
    • autopkgtest for ruby-file-validators/3.0.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-file-validators.html
    • Reproducible on armhf - info ♻
    • 1254 days old (needed 5 days)
• ruby-gd (- to 0.8.0-8)
  • Migration status for ruby-gd (- to 0.8.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gd would introduce bugs in testing: #1075461
    • Depends: ruby-gd ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gd.html
    • 1254 days old (needed 5 days)
• ruby-serialport (- to 1.3.2-1)
  • Migration status for ruby-serialport (- to 1.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-serialport would introduce bugs in testing: #1075476
    • Depends: ruby-serialport ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-serialport.html
    • 1258 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): nim-kexpr nim (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-kexpr.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1264 days old (needed 5 days)
• libdfp (- to 1.0.16-1)
  • Migration status for libdfp (- to 1.0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdfp would introduce bugs in testing: #1077413
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdfp.html
    • Reproducible on i386 - info ♻
    • 1266 days old (needed 5 days)
• idm-console-framework (- to 2.0.0-1)
  • Migration status for idm-console-framework (- to 2.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): idm-console-framework jss (not considered)
    • Depends: idm-console-framework jss (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): idm-console-framework ldapjdk
    • Depends: idm-console-framework ldapjdk
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idm-console-framework.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1267 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
    • 1270 days old (needed 5 days)
• prads (- to 0.3.3-7)
  • Migration status for prads (- to 0.3.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • prads/amd64 has unsatisfiable dependency
    • prads/arm64 has unsatisfiable dependency
    • prads/armel has unsatisfiable dependency
    • prads/armhf has unsatisfiable dependency
    • prads/i386 has unsatisfiable dependency
    • prads/mips64el has unsatisfiable dependency
    • prads/ppc64el has unsatisfiable dependency
    • prads/s390x has unsatisfiable dependency
    • Updating prads would introduce bugs in testing: #1069335, #1081091, #999984
    • prads unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prads.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 1271 days old (needed 5 days)
• epic5 (- to 2.1.6-1)
  • Migration status for epic5 (- to 2.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • epic5/amd64 has unsatisfiable dependency
    • epic5/arm64 has unsatisfiable dependency
    • epic5/armel has unsatisfiable dependency
    • epic5/armhf has unsatisfiable dependency
    • epic5/i386 has unsatisfiable dependency
    • epic5/mips64el has unsatisfiable dependency
    • epic5/ppc64el has unsatisfiable dependency
    • epic5/riscv64 has unsatisfiable dependency
    • epic5/s390x has unsatisfiable dependency
    • Updating epic5 would introduce bugs in testing: #1066505
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epic5.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1277 days old (needed 5 days)
• anfo (- to 0.98-9)
  • Migration status for anfo (- to 0.98-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • anfo/amd64 has unsatisfiable dependency
    • libanfo0/amd64 has unsatisfiable dependency
    • anfo/arm64 has unsatisfiable dependency
    • libanfo0/arm64 has unsatisfiable dependency
    • anfo/armel has unsatisfiable dependency
    • libanfo0/armel has unsatisfiable dependency
    • anfo/armhf has unsatisfiable dependency
    • libanfo0/armhf has unsatisfiable dependency
    • anfo/i386 has unsatisfiable dependency
    • libanfo0/i386 has unsatisfiable dependency
    • anfo/mips64el has unsatisfiable dependency
    • libanfo0/mips64el has unsatisfiable dependency
    • anfo/ppc64el has unsatisfiable dependency
    • libanfo0/ppc64el has unsatisfiable dependency
    • anfo/s390x has unsatisfiable dependency
    • libanfo0/s390x has unsatisfiable dependency
    • Updating anfo would introduce bugs in testing: #1012893, #1061888
    • anfo unsatisfiable Build-Depends(-Arch) on armel: libelk0
    • anfo unsatisfiable Build-Depends(-Arch) on armhf: libelk0
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/anfo.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1280 days old (needed 5 days)
• gwc (- to 0.22.05-1)
  • Migration status for gwc (- to 0.22.05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gwc/armel has unsatisfiable dependency
    • gwc/armhf has unsatisfiable dependency
    • Updating gwc would introduce bugs in testing: #1066364
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gwc.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1282 days old (needed 5 days)
• async-http-client (- to 2.12.3-1)
  • Migration status for async-http-client (- to 2.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating async-http-client would introduce bugs in testing: #1089228
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/async-http-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1298 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
    • 1299 days old (needed 5 days)
• clues-emacs (- to 1.0.1-3.1)
  • Migration status for clues-emacs (- to 1.0.1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clues-emacs would introduce bugs in testing: #1077097
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clues-emacs.html
    • autopkgtest for clues-emacs/1.0.1-3.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1304 days old (needed 2 days)
• libglade2 (- to 1:2.6.4-2.4)
  • Migration status for libglade2 (- to 1:2.6.4-2.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libglade2 would introduce bugs in testing: #1099823, #895517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libglade2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1323 days old (needed 5 days)
• libjs-jsxc (- to 3.4.4+dfsg-2)
  • Migration status for libjs-jsxc (- to 3.4.4+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: libjs-jsxc ruby-rails-assets-jquery.slimscroll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjs-jsxc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1324 days old (needed 5 days)
• ganglia-modules-linux (- to 1.3.6-5)
  • Migration status for ganglia-modules-linux (- to 1.3.6-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ganglia-modules-linux ganglia (not considered)
    • Depends: ganglia-modules-linux ganglia (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia-modules-linux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1360 days old (needed 5 days)
• redisearch (- to 1:1.2.2-4)
  • Migration status for redisearch (- to 1:1.2.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redisearch would introduce bugs in testing: #1091247
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redisearch.html
    • autopkgtest for redisearch/1:1.2.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1405 days old (needed 2 days)
• mialmpick (- to 0.2.15-2)
  • Migration status for mialmpick (- to 0.2.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mialmpick would introduce bugs in testing: #967880
    • Build-Depends(-Arch): mialmpick gtkglext (not considered)
    • Build-Depends(-Arch): mialmpick libglade2 (not considered)
    • Depends: mialmpick gtkglext (not considered)
    • Depends: mialmpick libglade2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mialmpick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1406 days old (needed 5 days)
• scrollz (- to 2.2.3-2)
  • Migration status for scrollz (- to 2.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • scrollz/armel has unsatisfiable dependency
    • scrollz/armhf has unsatisfiable dependency
    • Updating scrollz would introduce bugs in testing: #1066483
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrollz.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1413 days old (needed 5 days)
• dstat (- to 0.7.4-6.1)
  • Migration status for dstat (- to 0.7.4-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dstat would introduce bugs in testing: #1034856
    • autopkgtest for dstat/0.7.4-6.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1461 days old (needed 5 days)
• gtkglext (- to 1.2.0-11)
  • Migration status for gtkglext (- to 1.2.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtkglext would introduce bugs in testing: #1054392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkglext.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1479 days old (needed 5 days)
• gkrellshoot (- to 0.4.4-3)
  • Migration status for gkrellshoot (- to 0.4.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gkrellshoot would introduce bugs in testing: #1075008
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gkrellshoot.html
    • 1498 days old (needed 5 days)
• hotspot (- to 1.3.0-2)
  • Migration status for hotspot (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • hotspot/amd64 has unsatisfiable dependency
    • hotspot/arm64 has unsatisfiable dependency
    • hotspot/armel has unsatisfiable dependency
    • hotspot/armhf has unsatisfiable dependency
    • hotspot/i386 has unsatisfiable dependency
    • hotspot/mips64el has unsatisfiable dependency
    • hotspot/ppc64el has unsatisfiable dependency
    • hotspot/riscv64 has unsatisfiable dependency
    • Updating hotspot would introduce bugs in testing: #1025573, #1033848
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/hotspot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1507 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1509 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1509 days old (needed 5 days)
• utox (- to 0.18.1-1)
  • Migration status for utox (- to 0.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for utox/0.18.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1509 days old (needed 5 days)
• qrouter (- to 1.4.71-2)
  • Migration status for qrouter (- to 1.4.71-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qrouter would introduce bugs in testing: #1066488
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qrouter.html
    • autopkgtest for qrouter/1.4.71-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1512 days old (needed 5 days)
• mydumper (- to 0.10.1-1)
  • Migration status for mydumper (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mydumper/amd64 has unsatisfiable dependency
    • mydumper/arm64 has unsatisfiable dependency
    • mydumper/armel has unsatisfiable dependency
    • mydumper/armhf has unsatisfiable dependency
    • mydumper/i386 has unsatisfiable dependency
    • mydumper/mips64el has unsatisfiable dependency
    • mydumper/ppc64el has unsatisfiable dependency
    • mydumper/riscv64 has unsatisfiable dependency
    • mydumper/s390x has unsatisfiable dependency
    • Updating mydumper would introduce bugs in testing: #1000014
    • mydumper unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mydumper.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1518 days old (needed 5 days)
• nattable (- to 2.0.0+dfsg-1)
  • Migration status for nattable (- to 2.0.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nattable eclipse-collections (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nattable.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1519 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1519 days old (needed 5 days)
• arduino-mk (- to 1.5.2-2.1)
  • Migration status for arduino-mk (- to 1.5.2-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: arduino-mk arduino (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino-mk.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1520 days old (needed 5 days)
• btrfs-compsize (- to 1.5-1)
  • Migration status for btrfs-compsize (- to 1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating btrfs-compsize would introduce bugs in testing: #1091561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btrfs-compsize.html
    • Reproducible on armhf - info ♻
    • 1520 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
    • 1520 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
    • 1520 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
    • 1520 days old (needed 5 days)
• performous-composer (- to 2.0+20181009-gitbeeea23-2.1)
  • Migration status for performous-composer (- to 2.0+20181009-gitbeeea23-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • performous-composer/amd64 has unsatisfiable dependency
    • performous-composer/arm64 has unsatisfiable dependency
    • performous-composer/armel has unsatisfiable dependency
    • performous-composer/armhf has unsatisfiable dependency
    • performous-composer/i386 has unsatisfiable dependency
    • performous-composer/mips64el has unsatisfiable dependency
    • performous-composer/ppc64el has unsatisfiable dependency
    • performous-composer/s390x has unsatisfiable dependency
    • Updating performous-composer would introduce bugs in testing: #1004816
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/performous-composer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1521 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
    • 1525 days old (needed 5 days)
• sugar-etoys-activity (- to 116-10)
  • Migration status for sugar-etoys-activity (- to 116-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sugar-etoys-activity etoys (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1525 days old (needed 5 days)
• arduino-mighty-1284p (- to 1-5)
  • Migration status for arduino-mighty-1284p (- to 1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: arduino-mighty-1284p arduino (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino-mighty-1284p.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1526 days old (needed 5 days)
• pantomime-clojure (- to 2.1.0+dfsg-2)
  • Migration status for pantomime-clojure (- to 2.1.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pantomime-clojure tika (not considered)
    • Depends: pantomime-clojure tika (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantomime-clojure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1526 days old (needed 5 days)
• tika (- to 1.22-2)
  • Migration status for tika (- to 1.22-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tika would introduce bugs in testing: #1011492
    • Build-Depends(-Arch): tika vorbis-java
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tika.html
    • 1526 days old (needed 5 days)
• libscout (- to 2.3.2-3)
  • Migration status for libscout (- to 2.3.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libscout android-framework-23 (not considered)
    • Depends: libscout android-framework-23 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libscout.html
    • autopkgtest for libscout/2.3.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1531 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
    • 1541 days old (needed 5 days)
• keynav (- to 0.20180421~git6505bd0d-3)
  • Migration status for keynav (- to 0.20180421~git6505bd0d-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating keynav would introduce bugs in testing: #1065949
    • Depends: keynav glib2.0 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keynav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1541 days old (needed 5 days)
• python-aioopenssl (- to 0.6.0-1)
  • Migration status for python-aioopenssl (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioopenssl would introduce bugs in testing: #1090130
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioopenssl.html
    • Reproducible on armhf - info ♻
    • 1541 days old (needed 5 days)
• sptk (- to 3.9-3)
  • Migration status for sptk (- to 3.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sptk would introduce bugs in testing: #1091296
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sptk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1541 days old (needed 5 days)
• ruby-rack-google-analytics (- to 1.2.0-2.1)
  • Migration status for ruby-rack-google-analytics (- to 1.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rack-google-analytics would introduce bugs in testing: #1094516, #1094846
    • autopkgtest for ruby-rack-google-analytics/1.2.0-2.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rack-google-analytics.html
    • Reproducible on i386 - info ♻
    • 1549 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
    • 1550 days old (needed 5 days)
• dlang-libevent (- to 2.0.16.1~really2.0.2-0.2)
  • Migration status for dlang-libevent (- to 2.0.16.1~really2.0.2-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dlang-libevent would introduce bugs in testing: #1091010
    • Depends: dlang-libevent dlang-openssl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dlang-libevent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1550 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
    • 1550 days old (needed 5 days)
• ruby-cleanroom (- to 1.0.0-1.1)
  • Migration status for ruby-cleanroom (- to 1.0.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-cleanroom would introduce bugs in testing: #1092691, #1101902
    • autopkgtest for ruby-cleanroom/1.0.0-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-cleanroom.html
    • 1550 days old (needed 5 days)
• ruby-rack-piwik (- to 0.3.0-2.1)
  • Migration status for ruby-rack-piwik (- to 0.3.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rack-piwik would introduce bugs in testing: #1094558
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rack-piwik.html
    • 1550 days old (needed 5 days)
• dlang-openssl (- to 2.0.0+1.1.0h-0.2)
  • Migration status for dlang-openssl (- to 2.0.0+1.1.0h-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dlang-openssl would introduce bugs in testing: #1091022
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dlang-openssl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1552 days old (needed 5 days)
• graypy (- to 2.1.0-1)
  • Migration status for graypy (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graypy would introduce bugs in testing: #1082050
    • autopkgtest for graypy/2.1.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • graypy unsatisfiable Build-Depends(-Arch) on amd64: python3-amqplib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1552 days old (needed 5 days)
• makepp (- to 2.0.98.5-2.1)
  • Migration status for makepp (- to 2.0.98.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating makepp would introduce bugs in testing: #1087904, #1100005
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/makepp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1552 days old (needed 5 days)
• jsjac (- to 1.3.4+dfsg-3)
  • Migration status for jsjac (- to 1.3.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsjac would introduce bugs in testing: #1091600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsjac.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1554 days old (needed 5 days)
• ruby-omniauth-kerberos (- to 0.3.0-3.1)
  • Migration status for ruby-omniauth-kerberos (- to 0.3.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-kerberos would introduce bugs in testing: #1094542
    • Build-Depends(-Arch): ruby-omniauth-kerberos ruby-omniauth-multipassword (not considered)
    • Depends: ruby-omniauth-kerberos ruby-omniauth-multipassword (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-kerberos.html
    • autopkgtest for ruby-omniauth-kerberos/0.3.0-3.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1554 days old (needed 2 days)
• android-framework-23 (- to 6.0.1+r72-6)
  • Migration status for android-framework-23 (- to 6.0.1+r72-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-framework-23 would introduce bugs in testing: #1011567, #1038833
    • Build-Depends(-Arch): android-framework-23 android-platform-external-doclava (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-framework-23.html
    • autopkgtest for android-framework-23/6.0.1+r72-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1556 days old (needed 2 days)
• php-net-ftp (- to 1:1.4.0-2.1)
  • Migration status for php-net-ftp (- to 1:1.4.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-ftp would introduce bugs in testing: #1041477
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-ftp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1556 days old (needed 5 days)
• scratch (- to 1.4.0.6~dfsg1-6.1)
  • Migration status for scratch (- to 1.4.0.6~dfsg1-6.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: scratch squeak-vm (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scratch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1557 days old (needed 5 days)
• libphp-snoopy (- to 2.0.0-3)
  • Migration status for libphp-snoopy (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libphp-snoopy would introduce bugs in testing: #1065707
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libphp-snoopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1563 days old (needed 5 days)
• broker (- to 1.4.0+ds1-1)
  • Migration status for broker (- to 1.4.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-broker/amd64 has unsatisfiable dependency
    • python3-broker/arm64 has unsatisfiable dependency
    • libbroker2/armel has unsatisfiable dependency
    • python3-broker/armel has unsatisfiable dependency
    • libbroker2/armhf has unsatisfiable dependency
    • python3-broker/armhf has unsatisfiable dependency
    • python3-broker/i386 has unsatisfiable dependency
    • python3-broker/mips64el has unsatisfiable dependency
    • python3-broker/ppc64el has unsatisfiable dependency
    • python3-broker/s390x has unsatisfiable dependency
    • Updating broker would introduce bugs in testing: #1037597, #1062029
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/broker.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1564 days old (needed 5 days)
• ydotool (- to 0.1.8-3)
  • Migration status for ydotool (- to 0.1.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ydotool would introduce bugs in testing: #1069485
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ydotool.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1567 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-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
    • Reproducible on i386 - info ♻
    • 1568 days old (needed 5 days)
• adabrowse (- to 4.0.3-14)
  • Migration status for adabrowse (- to 4.0.3-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • adabrowse/amd64 has unsatisfiable dependency
    • adabrowse/arm64 has unsatisfiable dependency
    • adabrowse/armel has unsatisfiable dependency
    • adabrowse/armhf has unsatisfiable dependency
    • adabrowse/i386 has unsatisfiable dependency
    • adabrowse/mips64el has unsatisfiable dependency
    • adabrowse/ppc64el has unsatisfiable dependency
    • adabrowse/s390x has unsatisfiable dependency
    • Updating adabrowse would introduce bugs in testing: #1008980
    • Build-Depends(-Arch): adabrowse asis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adabrowse.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1570 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
    • 1570 days old (needed 5 days)
• asis (- to 2019-5)
  • Migration status for asis (- to 2019-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • asis-programs/amd64 has unsatisfiable dependency
    • libasis2019.1/amd64 has unsatisfiable dependency
    • libasis2019.1-dev/amd64 has unsatisfiable dependency
    • asis-programs/arm64 has unsatisfiable dependency
    • libasis2019.1/arm64 has unsatisfiable dependency
    • libasis2019.1-dev/arm64 has unsatisfiable dependency
    • asis-programs/armel has unsatisfiable dependency
    • libasis2019.1/armel has unsatisfiable dependency
    • libasis2019.1-dev/armel has unsatisfiable dependency
    • asis-programs/armhf has unsatisfiable dependency
    • libasis2019.1/armhf has unsatisfiable dependency
    • libasis2019.1-dev/armhf has unsatisfiable dependency
    • asis-programs/i386 has unsatisfiable dependency
    • libasis2019.1/i386 has unsatisfiable dependency
    • libasis2019.1-dev/i386 has unsatisfiable dependency
    • asis-programs/mips64el has unsatisfiable dependency
    • libasis2019.1/mips64el has unsatisfiable dependency
    • libasis2019.1-dev/mips64el has unsatisfiable dependency
    • asis-programs/ppc64el has unsatisfiable dependency
    • libasis2019.1/ppc64el has unsatisfiable dependency
    • libasis2019.1-dev/ppc64el has unsatisfiable dependency
    • asis-programs/s390x has unsatisfiable dependency
    • libasis2019.1/s390x has unsatisfiable dependency
    • libasis2019.1-dev/s390x has unsatisfiable dependency
    • Updating asis would introduce bugs in testing: #1008979
    • asis unsatisfiable Build-Depends(-Arch) on amd64: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on arm64: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armel: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on armel: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armhf: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on i386: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on i386: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on s390x: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlezout8-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/asis.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1576 days old (needed 5 days)
• autoconf2.13 (- to 2.13-69)
  • Migration status for autoconf2.13 (- to 2.13-69): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autoconf2.13 would introduce bugs in testing: #1081532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autoconf2.13.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1576 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1584 days old (needed 5 days)
• nanostat (- to 1.4.0-3)
  • Migration status for nanostat (- to 1.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nanostat/1.4.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanostat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1588 days old (needed 5 days)
• shoogle (- to 0.1.4-10)
  • Migration status for shoogle (- to 0.1.4-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shoogle would introduce bugs in testing: #1083030
    • Depends: shoogle python-oauth2client (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shoogle.html
    • autopkgtest for shoogle/0.1.4-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1589 days old (needed 2 days)
• yagv (- to 0.4~20171211.r234ef16+dfsg-2)
  • Migration status for yagv (- to 0.4~20171211.r234ef16+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yagv would introduce bugs in testing: #1064598
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yagv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1592 days old (needed 5 days)
• prelude-manager (- to 5.2.0-2)
  • Migration status for prelude-manager (- to 5.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): prelude-manager libpreludedb (not considered)
    • Depends: prelude-manager libpreludedb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): prelude-manager libprelude (not considered)
    • Depends: prelude-manager libprelude (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1593 days old (needed 5 days)
• php-horde-javascriptminify (- to 1.1.5-7)
  • Migration status for php-horde-javascriptminify (- to 1.1.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-javascriptminify/1.1.5-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1596 days old (needed 5 days)
• desproxy (- to 0.1.0~pre3-10.1)
  • Migration status for desproxy (- to 0.1.0~pre3-10.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating desproxy would introduce bugs in testing: #1074907
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/desproxy.html
    • 1600 days old (needed 5 days)
• nim-docopt (- to 0.6.8-3)
  • Migration status for nim-docopt (- to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nim-docopt would introduce bugs in testing: #1081085
    • autopkgtest for nim-docopt/0.6.8-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): nim-docopt nim (not considered)
    • Build-Depends(-Arch): nim-docopt nim-regex
    • Build-Depends(-Arch): nim-docopt nim-unicodedb
    • Build-Depends(-Arch): nim-docopt nim-unicodeplus
    • Depends: nim-docopt nim-regex
    • Depends: nim-docopt nim-unicodedb
    • Depends: nim-docopt nim-unicodeplus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-docopt.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1604 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)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-d3.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1606 days old (needed 5 days)
• tpp (- to 1.3.1-8)
  • Migration status for tpp (- to 1.3.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tpp would introduce bugs in testing: #1077125
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1610 days old (needed 5 days)
• shc (- to 4.0.3-1)
  • Migration status for shc (- to 4.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shc would introduce bugs in testing: #1072469
    • shc unsatisfiable Build-Depends(-Arch) on amd64: ash
    • shc unsatisfiable Build-Depends(-Arch) on arm64: ash
    • shc unsatisfiable Build-Depends(-Arch) on armel: ash
    • shc unsatisfiable Build-Depends(-Arch) on armhf: ash
    • shc unsatisfiable Build-Depends(-Arch) on i386: ash
    • shc unsatisfiable Build-Depends(-Arch) on mips64el: ash
    • shc unsatisfiable Build-Depends(-Arch) on ppc64el: ash
    • shc unsatisfiable Build-Depends(-Arch) on riscv64: ash
    • shc unsatisfiable Build-Depends(-Arch) on s390x: ash
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shc.html
    • autopkgtest for shc/4.0.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1611 days old (needed 2 days)
• holes (- to 0.1-5)
  • Migration status for holes (- to 0.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating holes would introduce bugs in testing: #1069466
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/holes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1618 days old (needed 5 days)
• nim-regex (- to 0.17.0+ds-2)
  • Migration status for nim-regex (- to 0.17.0+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-regex nim (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): nim-regex nim-unicodedb
    • Build-Depends(-Arch): nim-regex nim-unicodeplus
    • Depends: nim-regex nim-unicodedb
    • Depends: nim-regex nim-unicodeplus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-regex.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1619 days old (needed 5 days)
• php-horde-mail-autoconfig (- to 1.0.3-10)
  • Migration status for php-horde-mail-autoconfig (- to 1.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-mail-autoconfig/1.0.3-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1629 days old (needed 5 days)
• php-horde-mnemo (- to 4.2.14-10)
  • Migration status for php-horde-mnemo (- to 4.2.14-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-mnemo/4.2.14-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1629 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-dns2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1631 days old (needed 5 days)
• r-cran-factoextra (- to 1.0.7-2)
  • Migration status for r-cran-factoextra (- to 1.0.7-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-factoextra r-cran-dendextend (not considered)
    • Depends: r-cran-factoextra r-cran-dendextend (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-factoextra.html
    • autopkgtest for r-cran-factoextra/1.0.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1632 days old (needed 2 days)
• pyqwt3d (- to 0.1.8-6)
  • Migration status for pyqwt3d (- to 0.1.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyqwt3d sip4 (not considered)
    • Depends: pyqwt3d sip4 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyqwt3d.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1634 days old (needed 5 days)
• php-horde-nag (- to 4.2.19-6)
  • Migration status for php-horde-nag (- to 4.2.19-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-nag would introduce bugs in testing: #1064389
    • autopkgtest for php-horde-nag/4.2.19-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1647 days old (needed 5 days)
• ruby-rollout (- to 2.5.0-1)
  • Migration status for ruby-rollout (- to 2.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rollout would introduce bugs in testing: #1084366
    • autopkgtest for ruby-rollout/2.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-rollout ruby-fakeredis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rollout.html
    • 1648 days old (needed 5 days)
• php-horde-content (- to 2.0.6-7)
  • Migration status for php-horde-content (- to 2.0.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-content/2.0.6-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1652 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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)
    • 1657 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1657 days old (needed 5 days)
• php-horde-javascriptminify-jsmin (- to 1.0.2-9)
  • Migration status for php-horde-javascriptminify-jsmin (- to 1.0.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-javascriptminify-jsmin/1.0.2-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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)
    • 1661 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1663 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1663 days old (needed 5 days)
• ruby-rails-assets-fine-uploader (- to 5.13.0-2)
  • Migration status for ruby-rails-assets-fine-uploader (- to 5.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-fine-uploader would introduce bugs in testing: #1034027
    • autopkgtest for ruby-rails-assets-fine-uploader/5.13.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-fine-uploader.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1663 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1664 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1666 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1666 days old (needed 5 days)
• php-horde-timezone (- to 1.1.0-7)
  • Migration status for php-horde-timezone (- to 1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-timezone would introduce bugs in testing: #1089778
    • autopkgtest for php-horde-timezone/1.1.0-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1666 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1667 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1667 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
    • 1676 days old (needed 5 days)
• ruby-rails-assets-blueimp-gallery (- to 2.33.0-2)
  • Migration status for ruby-rails-assets-blueimp-gallery (- to 2.33.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-blueimp-gallery would introduce bugs in testing: #1033914
    • autopkgtest for ruby-rails-assets-blueimp-gallery/2.33.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-blueimp-gallery.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1687 days old (needed 5 days)
• fvwm1 (- to 1.24r-57)
  • Migration status for fvwm1 (- to 1.24r-57): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fvwm1 would introduce bugs in testing: #1066565
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fvwm1.html
    • 1693 days old (needed 5 days)
• mlv-smile (- to 1.47-8)
  • Migration status for mlv-smile (- to 1.47-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlv-smile would introduce bugs in testing: #1066525
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlv-smile.html
    • autopkgtest for mlv-smile/1.47-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1695 days old (needed 2 days)
• gmanedit (- to 0.4.2-8)
  • Migration status for gmanedit (- to 0.4.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gmanedit would introduce bugs in testing: #1075015
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmanedit.html
    • 1698 days old (needed 5 days)
• nim-unicodedb (- to 0.9.0-2)
  • Migration status for nim-unicodedb (- to 0.9.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-unicodedb nim (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-unicodedb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1699 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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1699 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
    • 1700 days old (needed 5 days)
• tree-style-tab (- to 3.5.20-1)
  • Migration status for tree-style-tab (- to 3.5.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tree-style-tab would introduce bugs in testing: #1071896
    • tree-style-tab unsatisfiable Build-Depends(-Arch) on amd64: mozilla-devscripts (>= 0.50~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tree-style-tab.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1703 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)
    • 1705 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)
    • 1705 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: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyjdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1706 days old (needed 5 days)
• nastran (- to 0.1.95-2)
  • Migration status for nastran (- to 0.1.95-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nastran would introduce bugs in testing: #1054241
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1709 days old (needed 5 days)
• gnucap-python (- to 0.0.2-1.2)
  • Migration status for gnucap-python (- to 0.0.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gnucap/amd64 has unsatisfiable dependency
    • python3-gnucap/arm64 has unsatisfiable dependency
    • python3-gnucap/armel has unsatisfiable dependency
    • python3-gnucap/armhf has unsatisfiable dependency
    • python3-gnucap/i386 has unsatisfiable dependency
    • python3-gnucap/mips64el has unsatisfiable dependency
    • python3-gnucap/ppc64el has unsatisfiable dependency
    • python3-gnucap/riscv64 has unsatisfiable dependency
    • python3-gnucap/s390x has unsatisfiable dependency
    • Updating gnucap-python would introduce bugs in testing: #1067335
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnucap-python.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1713 days old (needed 5 days)
• 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1715 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1716 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1716 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
    • 1718 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/armel has unsatisfiable dependency
    • mongrel2-core/armhf has unsatisfiable dependency
    • mongrel2-core/i386 has unsatisfiable dependency
    • mongrel2-core/mips64el 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1720 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1721 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1721 days old (needed 5 days)
• php-horde-controller (- to 2.0.5-5)
  • Migration status for php-horde-controller (- to 2.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-controller/2.0.5-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1721 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
    • autopkgtest for php-horde-css-parser/1.0.11-8: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1721 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1721 days old (needed 5 days)
• yeahconsole (- to 0.3.4-6)
  • Migration status for yeahconsole (- to 0.3.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yeahconsole would introduce bugs in testing: #1075696
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yeahconsole.html
    • 1724 days old (needed 5 days)
• fonts-kacst (- to 2.01+mry-15)
  • Migration status for fonts-kacst (- to 2.01+mry-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-kacst would introduce bugs in testing: #1041017
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-kacst.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1725 days old (needed 5 days)
• eclipse-remote (- to 2.1.0-2)
  • Migration status for eclipse-remote (- to 2.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): eclipse-remote eclipse-cdt (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-remote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1726 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1726 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1738 days old (needed 5 days)
• php-horde-gollem (- to 3.0.13-5)
  • Migration status for php-horde-gollem (- to 3.0.13-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-gollem php-horde (not considered)
    • Invalidated by dependency
    • 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-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1739 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1739 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1741 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1741 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1741 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1741 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1741 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 days old (needed 5 days)
• php-horde-groupware (- to 5.2.22-6)
  • Migration status for php-horde-groupware (- to 5.2.22-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-groupware php-horde (not considered)
    • Invalidated by dependency
    • 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-content (not considered)
    • Depends: php-horde-groupware php-horde-gollem
    • Depends: php-horde-groupware php-horde-kronolith (not considered)
    • Depends: php-horde-groupware php-horde-mnemo (not considered)
    • Depends: php-horde-groupware php-horde-nag (not considered)
    • Depends: php-horde-groupware php-horde-timeobjects
    • Depends: php-horde-groupware php-horde-trean
    • Depends: php-horde-groupware php-horde-turba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-groupware.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 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
    • 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
    • Depends: php-horde-webmail php-horde-imp (not considered)
    • Depends: php-horde-webmail php-horde-ingo (not considered)
    • Depends: php-horde-webmail php-horde-kronolith (not considered)
    • Depends: php-horde-webmail php-horde-mnemo (not considered)
    • Depends: php-horde-webmail php-horde-nag (not considered)
    • Depends: php-horde-webmail php-horde-timeobjects
    • Depends: php-horde-webmail php-horde-trean
    • Depends: php-horde-webmail php-horde-turba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-webmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1742 days old (needed 5 days)
• dpaste (- to 0.4.0-1)
  • Migration status for dpaste (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dpaste would introduce bugs in testing: #1082991
    • Build-Depends(-Arch): dpaste opendht (not considered)
    • Depends: dpaste opendht (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dpaste.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 1748 days old (needed 5 days)
• lhs2tex (- to 1.24-1)
  • Migration status for lhs2tex (- to 1.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lhs2tex would introduce bugs in testing: #1082301
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lhs2tex.html
    • 1756 days old (needed 5 days)
• jinput (- to 20100502+dfsg-11)
  • Migration status for jinput (- to 20100502+dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jinput would introduce bugs in testing: #1069434
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jinput.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1766 days old (needed 5 days)
• runescape (- to 0.8-2)
  • Migration status for runescape (- to 0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating runescape would introduce bugs in testing: #1061393
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for runescape/0.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1774 days old (needed 2 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/armel has unsatisfiable dependency
    • tilde/armhf has unsatisfiable dependency
    • tilde/i386 has unsatisfiable dependency
    • tilde/mips64el 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 armel: 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 mips64el: 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1778 days old (needed 5 days)
• id-utils (- to 4.6.28-20200521ss15dab)
  • Migration status for id-utils (- to 4.6.28-20200521ss15dab): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating id-utils would introduce bugs in testing: #1089346, #1091243
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/id-utils.html
    • 1779 days old (needed 5 days)
• r-cran-fitcoach (- to 1.0-4)
  • Migration status for r-cran-fitcoach (- to 1.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-fitcoach r-cran-gbm (not considered)
    • Depends: r-cran-fitcoach r-cran-gbm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fitcoach.html
    • autopkgtest for r-cran-fitcoach/1.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1784 days old (needed 2 days)
• quiterss (- to 0.19.4+dfsg-1)
  • Migration status for quiterss (- to 0.19.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quiterss would introduce bugs in testing: #1093725
    • Build-Depends(-Arch): quiterss qtwebkit-opensource-src (not considered)
    • Depends: quiterss qtwebkit-opensource-src (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quiterss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1801 days old (needed 5 days)
• parcimonie (- to 0.12.0-2)
  • Migration status for parcimonie (- to 0.12.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parcimonie would introduce bugs in testing: #1091033
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parcimonie.html
    • autopkgtest for parcimonie/0.12.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1809 days old (needed 2 days)
• syrthes (- to 4.3.5+20200129-dfsg1-1)
  • Migration status for syrthes (- to 4.3.5+20200129-dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • syrthes-tools/armel has unsatisfiable dependency
    • syrthes-tools/armhf has unsatisfiable dependency
    • Updating syrthes would introduce bugs in testing: #1066258
    • Build-Depends(-Arch): syrthes code-saturne (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syrthes.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1813 days old (needed 5 days)
• code-saturne (- to 6.0.2-2)
  • Migration status for code-saturne (- to 6.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • code-saturne-bin/amd64 has unsatisfiable dependency
    • code-saturne-bin/arm64 has unsatisfiable dependency
    • code-saturne-bin/armel has unsatisfiable dependency
    • code-saturne-bin/armhf has unsatisfiable dependency
    • code-saturne-bin/i386 has unsatisfiable dependency
    • code-saturne-bin/mips64el has unsatisfiable dependency
    • code-saturne-bin/ppc64el has unsatisfiable dependency
    • code-saturne-bin/riscv64 has unsatisfiable dependency
    • code-saturne-bin/s390x has unsatisfiable dependency
    • Updating code-saturne would introduce bugs in testing: #1066231, #1068318
    • code-saturne unsatisfiable Build-Depends(-Arch) on armel: libopenmpi-dev
    • code-saturne unsatisfiable Build-Depends(-Arch) on armhf: libopenmpi-dev
    • code-saturne unsatisfiable Build-Depends(-Arch) on i386: libopenmpi-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/code-saturne.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1814 days old (needed 5 days)
• ruby-feature (- to 1.4.0-2)
  • Migration status for ruby-feature (- to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-feature would introduce bugs in testing: #1084362
    • autopkgtest for ruby-feature/1.4.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-feature ruby-fakeredis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-feature.html
    • 1817 days old (needed 5 days)
• cclib-data (- to 1.6.2-2)
  • Migration status for cclib-data (- to 1.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cclib-data would introduce bugs in testing: #1057547
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1822 days old (needed 5 days)
• ruby-redis-rack (- to 2.1.2-4)
  • Migration status for ruby-redis-rack (- to 2.1.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-rack would introduce bugs in testing: #1084365
    • autopkgtest for ruby-redis-rack/2.1.2-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-rack.html
    • 1824 days old (needed 5 days)
• ecb (- to 2.50+git20170628-1)
  • Migration status for ecb (- to 2.50+git20170628-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ecb would introduce bugs in testing: #1020168
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecb.html
    • 1825 days old (needed 5 days)
• clips (- to 6.30-4.1)
  • Migration status for clips (- to 6.30-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clips would introduce bugs in testing: #1061729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1834 days old (needed 5 days)
• ruby-warden (- to 1.2.8-1)
  • Migration status for ruby-warden (- to 1.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-warden would introduce bugs in testing: #1094553
    • autopkgtest for ruby-warden/1.2.8-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-warden.html
    • Reproducible on armhf - info ♻
    • 1835 days old (needed 5 days)
• tmperamental (- to 1.4)
  • Migration status for tmperamental (- to 1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tmperamental would introduce bugs in testing: #1069505
    • autopkgtest for tmperamental/1.4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tmperamental.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1856 days old (needed 5 days)
• aboot (- to 1.0~pre20200212-1)
  • Migration status for aboot (- to 1.0~pre20200212-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aboot-cross/amd64 has unsatisfiable dependency
    • aboot-cross/arm64 has unsatisfiable dependency
    • aboot-cross/armel has unsatisfiable dependency
    • aboot-cross/armhf has unsatisfiable dependency
    • aboot-cross/i386 has unsatisfiable dependency
    • aboot-cross/mips64el has unsatisfiable dependency
    • aboot-cross/ppc64el has unsatisfiable dependency
    • aboot-cross/riscv64 has unsatisfiable dependency
    • aboot-cross/s390x has unsatisfiable dependency
    • Updating aboot would introduce bugs in testing: #805988
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/aboot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1858 days old (needed 5 days)
• mustache-d (- to 0.1.4-1)
  • Migration status for mustache-d (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: mustache-d -> libphobos2-ldc-shared106/1:1.36.0-2.1/amd64
    • Impossible Depends: mustache-d -> libphobos2-ldc-shared106/1:1.36.0-2.1/arm64
    • Impossible Depends: mustache-d -> libphobos2-ldc-shared106/1:1.36.0-2.1/i386
    • Impossible Depends: mustache-d -> libphobos2-ldc-shared106/1:1.36.0-2.1/riscv64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mustache-d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1873 days old (needed 5 days)
• cafeobj (- to 1.6.0-2)
  • Migration status for cafeobj (- to 1.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cafeobj would introduce bugs in testing: #1085008, #1093322
    • cafeobj unsatisfiable Build-Depends(-Arch) on armel: sbcl
    • cafeobj unsatisfiable Build-Depends(-Arch) on armhf: sbcl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cafeobj.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 1875 days old (needed 5 days)
• ruby-dataobjects (- to 0.10.17-2)
  • Migration status for ruby-dataobjects (- to 0.10.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-dataobjects would introduce bugs in testing: #1092694
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dataobjects.html
    • Reproducible on armhf - info ♻
    • 1889 days old (needed 5 days)
• ruby-dataobjects-postgres (- to 0.10.17-1)
  • Migration status for ruby-dataobjects-postgres (- to 0.10.17-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-dataobjects-postgres ruby-dataobjects (not considered)
    • Depends: ruby-dataobjects-postgres ruby-dataobjects (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dataobjects-postgres.html
    • autopkgtest for ruby-dataobjects-postgres/0.10.17-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1889 days old (needed 5 days)
• ruby-dataobjects-sqlite3 (- to 0.10.17-1)
  • Migration status for ruby-dataobjects-sqlite3 (- to 0.10.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-dataobjects-sqlite3/arm64 has unsatisfiable dependency
    • Updating ruby-dataobjects-sqlite3 would introduce bugs in testing: #1092692
    • Build-Depends(-Arch): ruby-dataobjects-sqlite3 ruby-dataobjects (not considered)
    • Depends: ruby-dataobjects-sqlite3 ruby-dataobjects (not considered)
    • Depends: ruby-dataobjects-sqlite3 ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dataobjects-sqlite3.html
    • uninstallable on arch arm64, not running autopkgtest there
    • 1889 days old (needed 5 days)
• acpi-override (- to 0.1+nmu1)
  • Migration status for acpi-override (- to 0.1+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating acpi-override would introduce bugs in testing: #968604
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acpi-override.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1898 days old (needed 5 days)
• ghemical (- to 3.0.0-5)
  • Migration status for ghemical (- to 3.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ghemical/armel has unsatisfiable dependency
    • ghemical/armhf has unsatisfiable dependency
    • Updating ghemical would introduce bugs in testing: #1066986, #967865
    • Build-Depends(-Arch): ghemical gtkglext (not considered)
    • Build-Depends(-Arch): ghemical libghemical (not considered)
    • Build-Depends(-Arch): ghemical libglade2 (not considered)
    • Build-Depends(-Arch): ghemical mpqc (not considered)
    • Depends: ghemical gtkglext (not considered)
    • Depends: ghemical libglade2 (not considered)
    • Depends: ghemical mpqc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghemical.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1902 days old (needed 5 days)
• form-history-control (- to 2.5.1.0-1)
  • Migration status for form-history-control (- to 2.5.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating form-history-control would introduce bugs in testing: #1085455
    • webext-form-history-control/amd64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/arm64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/armel has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/armhf has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/i386 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/mips64el has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/ppc64el has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/riscv64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/s390x has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/form-history-control.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1912 days old (needed 5 days)
• golang-github-hashicorp-go-getter (- to 1.4.1-1)
  • Migration status for golang-github-hashicorp-go-getter (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-hashicorp-go-getter would introduce bugs in testing: #1083184
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-go-getter.html
    • autopkgtest for golang-github-hashicorp-go-getter/1.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1915 days old (needed 2 days)
• pyhoca-gui (- to 0.6.1.1-1)
  • Migration status for pyhoca-gui (- to 0.6.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyhoca-gui would introduce bugs in testing: #1054832
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyhoca-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1923 days old (needed 5 days)
• fortunes-mario (- to 0.21-1.1)
  • Migration status for fortunes-mario (- to 0.21-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fortunes-mario would introduce bugs in testing: #1073475
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortunes-mario.html
    • 1924 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
    • 1924 days old (needed 5 days)
• golang-github-throttled-throttled (- to 2.2.4-1)
  • Migration status for golang-github-throttled-throttled (- to 2.2.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-throttled-throttled golang-github-go-redis-redis (not considered)
    • Depends: golang-github-throttled-throttled golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-throttled-throttled.html
    • autopkgtest for golang-github-throttled-throttled/2.2.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1936 days old (needed 2 days)
• golang-github-ulule-limiter (- to 3.3.3-1)
  • Migration status for golang-github-ulule-limiter (- to 3.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Depends: golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ulule-limiter.html
    • autopkgtest for golang-github-ulule-limiter/3.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1954 days old (needed 2 days)
• android-platform-external-nist-sip (- to 9.0.0+r35-1.1)
  • Migration status for android-platform-external-nist-sip (- to 9.0.0+r35-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-external-nist-sip would introduce bugs in testing: #1065522
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-nist-sip.html
    • 1989 days old (needed 5 days)
• gphoto2-cffi (- to 0.4.3~a1-1.1)
  • Migration status for gphoto2-cffi (- to 0.4.3~a1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gphoto2-cffi would introduce bugs in testing: #1091277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gphoto2-cffi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1992 days old (needed 5 days)
• pymia (- to 0.1.9-2.1)
  • Migration status for pymia (- to 0.1.9-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mia/amd64 has unsatisfiable dependency
    • python3-mia/arm64 has unsatisfiable dependency
    • python3-mia/armel has unsatisfiable dependency
    • python3-mia/armhf has unsatisfiable dependency
    • python3-mia/i386 has unsatisfiable dependency
    • python3-mia/mips64el has unsatisfiable dependency
    • python3-mia/ppc64el has unsatisfiable dependency
    • python3-mia/riscv64 has unsatisfiable dependency
    • python3-mia/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): pymia mia (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pymia.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1993 days old (needed 5 days)
• python-pyramid-zcml (- to 1.0.0-1.2)
  • Migration status for python-pyramid-zcml (- to 1.0.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyramid-zcml would introduce bugs in testing: #997353
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-zcml.html
    • 2020 days old (needed 5 days)
• ca-cacert (- to 2019.0411-2)
  • Migration status for ca-cacert (- to 2019.0411-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ca-cacert would introduce bugs in testing: #988512, #990409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ca-cacert.html
    • 2038 days old (needed 5 days)
• hydroffice.bag (- to 0.2.15-3)
  • Migration status for hydroffice.bag (- to 0.2.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hydroffice.bag would introduce bugs in testing: #1079963, #993003
    • autopkgtest for hydroffice.bag/0.2.15-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hydroffice.bag.html
    • 2051 days old (needed 5 days)
• 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2057 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2058 days old (needed 5 days)
• gertty (- to 1.6.0-1)
  • Migration status for gertty (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gertty would introduce bugs in testing: #1054007, #1069052
    • autopkgtest for gertty/1.6.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gertty.html
    • 2065 days old (needed 5 days)
• pytest-salt (- to 2019.6.13-1)
  • Migration status for pytest-salt (- to 2019.6.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-salt would introduce bugs in testing: #1074682
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-salt.html
    • autopkgtest for pytest-salt/2019.6.13-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 2099 days old (needed 5 days)
• averell (- to 1.2.5-1.1)
  • Migration status for averell (- to 1.2.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating averell would introduce bugs in testing: #1090191
    • Build-Depends(-Arch): averell erlang-cowboy (not considered)
    • Depends: averell erlang-cowboy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/averell.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • New but not reproducible on armhf - info ♻
    • 2147 days old (needed 5 days)
• libretro-beetle-pce-fast (- to 0.9.38.7+git20160609-2)
  • Migration status for libretro-beetle-pce-fast (- to 0.9.38.7+git20160609-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libretro-beetle-pce-fast would introduce bugs in testing: #1070021
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-beetle-pce-fast.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2228 days old (needed 5 days)
• libretro-beetle-psx (- to 0.9.38.6+git20151019-3)
  • Migration status for libretro-beetle-psx (- to 0.9.38.6+git20151019-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libretro-beetle-psx would introduce bugs in testing: #1070022
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-beetle-psx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2228 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
    • Reproducible on armhf - info ♻
    • 2229 days old (needed 5 days)
• whitedune (- to 0.30.10-2.2)
  • Migration status for whitedune (- to 0.30.10-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • whitedune/armel has unsatisfiable dependency
    • whitedune/armhf has unsatisfiable dependency
    • Updating whitedune would introduce bugs in testing: #1036881, #1067618
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whitedune.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 2246 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
    • 2248 days old (needed 5 days)
• node-trust-webcrypto (- to 0.9.2-1)
  • Migration status for node-trust-webcrypto (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-trust-webcrypto would introduce bugs in testing: #1002262
    • autopkgtest for node-trust-webcrypto/0.9.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): node-trust-webcrypto node-node-rsa
    • Depends: node-trust-webcrypto node-node-rsa
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-trust-webcrypto.html
    • 2252 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
    • Waiting for reproducibility test results on armhf - info ♻
    • 2262 days old (needed 5 days)
• pgcharts (- to 1.0+2017-09-16-1)
  • Migration status for pgcharts (- to 1.0+2017-09-16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pgcharts would introduce bugs in testing: #1024642
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2277 days old (needed 5 days)
• vorbis-java (- to 0.8-3)
  • Migration status for vorbis-java (- to 0.8-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vorbis-java tika (not considered)
    • Depends: vorbis-java tika (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vorbis-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2283 days old (needed 5 days)
• gforth (- to 0.7.3+dfsg-9)
  • Migration status for gforth (- to 0.7.3+dfsg-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gforth would introduce bugs in testing: #1067376
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gforth.html
    • autopkgtest for gforth/0.7.3+dfsg-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2286 days old (needed 2 days)
• ruby-webpack-rails (- to 0.9.11+git-1)
  • Migration status for ruby-webpack-rails (- to 0.9.11+git-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-webpack-rails would introduce bugs in testing: #1094511
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-webpack-rails.html
    • autopkgtest for ruby-webpack-rails/0.9.11+git-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2328 days old (needed 2 days)
• xcircuit (- to 3.9.73+dfsg.1-1)
  • Migration status for xcircuit (- to 3.9.73+dfsg.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcircuit would introduce bugs in testing: #1066600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcircuit.html
    • 2341 days old (needed 5 days)
• sn (- to 0.3.8-12)
  • Migration status for sn (- to 0.3.8-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sn would introduce bugs in testing: #1075519
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sn.html
    • 2353 days old (needed 5 days)
• djinn (- to 2014.9.7-9)
  • Migration status for djinn (- to 2014.9.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating djinn would introduce bugs in testing: #1083254
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djinn.html
    • 2377 days old (needed 5 days)
• only (- to 0.0.6.0-2)
  • Migration status for only (- to 0.0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating only would introduce bugs in testing: #1085428
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/only.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2378 days old (needed 5 days)
• chessx (- to 1.4.6-2)
  • Migration status for chessx (- to 1.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chessx would introduce bugs in testing: #1074880
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chessx.html
    • 2406 days old (needed 5 days)
• globjects (- to 1.1.0-3)
  • Migration status for globjects (- to 1.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libglobjects1/amd64 has unsatisfiable dependency
    • libglobjects1/arm64 has unsatisfiable dependency
    • libglobjects1/armel has unsatisfiable dependency
    • libglobjects1/armhf has unsatisfiable dependency
    • libglobjects1/i386 has unsatisfiable dependency
    • libglobjects1/mips64el has unsatisfiable dependency
    • libglobjects1/ppc64el has unsatisfiable dependency
    • libglobjects1/riscv64 has unsatisfiable dependency
    • libglobjects1/s390x has unsatisfiable dependency
    • Updating globjects would introduce bugs in testing: #1090229
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globjects.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2470 days old (needed 5 days)
• erlang-cowboy (- to 2.0.0~pre.1+dfsg1-4)
  • Migration status for erlang-cowboy (- to 2.0.0~pre.1+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by iwamatsu
    • Not built on buildd: arch all binaries uploaded by iwamatsu, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): erlang-cowboy erlang-ranch (not considered)
    • Depends: erlang-cowboy erlang-ranch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-cowboy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2497 days old (needed 5 days)
• ruby-rjb (- to 1.5.5-3)
  • Migration status for ruby-rjb (- to 1.5.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rjb would introduce bugs in testing: #1075477
    • autopkgtest for ruby-rjb/1.5.5-3: amd64: Regression or new test ♻, i386: Regression or new test ♻
    • Depends: ruby-rjb ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rjb.html
    • 2527 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 ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • 2549 days old (needed 5 days)
• dita-ot (- to 1.5.3+dfsg-1)
  • Migration status for dita-ot (- to 1.5.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dita-ot would introduce bugs in testing: #1092375
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dita-ot.html
    • 2550 days old (needed 5 days)
• whowatch (- to 1.8.6-1)
  • Migration status for whowatch (- to 1.8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating whowatch would introduce bugs in testing: #1091295
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whowatch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 2554 days old (needed 5 days)
• ruby-gitlab-flowdock-git-hook (- to 1.0.1-4)
  • Migration status for ruby-gitlab-flowdock-git-hook (- to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-flowdock-git-hook would introduce bugs in testing: #1092695
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-flowdock-git-hook.html
    • autopkgtest for ruby-gitlab-flowdock-git-hook/1.0.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2575 days old (needed 2 days)
• ruby-redis-rails (- to 5.0.2-3)
  • Migration status for ruby-redis-rails (- to 5.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-rails would introduce bugs in testing: #1095383
    • autopkgtest for ruby-redis-rails/5.0.2-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-actionpack (not considered)
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-activesupport (not considered)
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-rack (not considered)
    • Depends: ruby-redis-rails ruby-redis-actionpack (not considered)
    • Depends: ruby-redis-rails ruby-redis-activesupport (not considered)
    • Depends: ruby-redis-rails ruby-redis-rack (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-rails.html
    • Reproducible on armhf - info ♻
    • 2599 days old (needed 5 days)
• metis-edf (- to 4.1-2-4)
  • Migration status for metis-edf (- to 4.1-2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating metis-edf would introduce bugs in testing: #1066955
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2629 days old (needed 5 days)
• similarity-tester (- to 3.0.2-1)
  • Migration status for similarity-tester (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating similarity-tester would introduce bugs in testing: #1066293
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/similarity-tester.html
    • 2649 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
    • 2651 days old (needed 5 days)
• debtags (- to 2.1.5)
  • Migration status for debtags (- to 2.1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debtags would introduce bugs in testing: #1058262, #1094655
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debtags.html
    • 2651 days old (needed 5 days)
• tz-converter (- to 1.0.1-1)
  • Migration status for tz-converter (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tz-converter would introduce bugs in testing: #1038851
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tz-converter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2653 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
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2701 days old (needed 5 days)
• monajat (- to 4.1-2)
  • Migration status for monajat (- to 4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating monajat would introduce bugs in testing: #1080671
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monajat.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2720 days old (needed 5 days)
• urweb (- to 20170720+dfsg-2)
  • Migration status for urweb (- to 20170720+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liburweb0/armel has unsatisfiable dependency
    • liburweb0/armhf has unsatisfiable dependency
    • liburweb0/ppc64el has unsatisfiable dependency
    • Updating urweb would introduce bugs in testing: #1060107
    • Build-Depends(-Arch): urweb mlton (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urweb.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 2759 days old (needed 5 days)
• endless-sky-high-dpi (- to 0.9.8-1)
  • Migration status for endless-sky-high-dpi (- to 0.9.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: endless-sky-high-dpi endless-sky (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/endless-sky-high-dpi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2789 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)
    • 2802 days old (needed 5 days)
• ruby-omniauth-twitter (- to 1.4.0-1)
  • Migration status for ruby-omniauth-twitter (- to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-twitter would introduce bugs in testing: #1094563
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-twitter.html
    • autopkgtest for ruby-omniauth-twitter/1.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2819 days old (needed 2 days)
• verilog-mode (- to 20161124.fd230e6-2)
  • Migration status for verilog-mode (- to 20161124.fd230e6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating verilog-mode would introduce bugs in testing: #934977
    • verilog-mode unsatisfiable Build-Depends(-Arch) on amd64: emacs25
    • Not built on buildd: arch all binaries uploaded by spwhitton@spwhitton.name, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): verilog-mode xemacs21 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilog-mode.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 3016 days old (needed 5 days)
• simpleproxy (- to 3.5-1)
  • Migration status for simpleproxy (- to 3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simpleproxy would introduce bugs in testing: #1075512
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simpleproxy.html
    • 3069 days old (needed 5 days)
• ccd2iso (- to 0.3-7)
  • Migration status for ccd2iso (- to 0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ccd2iso would introduce bugs in testing: #1066265
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccd2iso.html
    • 3107 days old (needed 5 days)
• i2util (- to 1.6-1)
  • Migration status for i2util (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating i2util would introduce bugs in testing: #1075076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i2util.html
    • 3121 days old (needed 5 days)
• netsed (- to 1.2-3)
  • Migration status for netsed (- to 1.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netsed would introduce bugs in testing: #1094091
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netsed.html
    • 3139 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)
    • 3143 days old (needed 5 days)
• ecere-sdk (- to 0.44.15-1)
  • Migration status for ecere-sdk (- to 0.44.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libedasqlite0/amd64 has unsatisfiable dependency
    • libedasqlite0/arm64 has unsatisfiable dependency
    • libecere0/armel has unsatisfiable dependency
    • libecereaudio0/armel has unsatisfiable dependency
    • libedasqlite0/armel has unsatisfiable dependency
    • libecere0/armhf has unsatisfiable dependency
    • libecereaudio0/armhf has unsatisfiable dependency
    • libedasqlite0/armhf has unsatisfiable dependency
    • libecere0/i386 has unsatisfiable dependency
    • libedasqlite0/i386 has unsatisfiable dependency
    • libedasqlite0/mips64el has unsatisfiable dependency
    • libedasqlite0/ppc64el has unsatisfiable dependency
    • libedasqlite0/s390x has unsatisfiable dependency
    • Updating ecere-sdk would introduce bugs in testing: #898832, #995050
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on amd64: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on arm64: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on armel: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on armhf: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on i386: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on mips64el: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on ppc64el: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on s390x: libgl1-mesa-glx
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/ecere-sdk.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 3167 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
    • 3269 days old (needed 5 days)
• subtle (- to 0.11.3224-xi-2.2)
  • Migration status for subtle (- to 0.11.3224-xi-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating subtle would introduce bugs in testing: #1075542
    • Depends: subtle ruby3.1 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/subtle.html
    • 3322 days old (needed 5 days)
• libr3 (- to 1.3.4-1)
  • Migration status for libr3 (- to 1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libr3-0/amd64 has unsatisfiable dependency
    • libr3-dev/amd64 has unsatisfiable dependency
    • libr3-0/arm64 has unsatisfiable dependency
    • libr3-dev/arm64 has unsatisfiable dependency
    • libr3-0/armel has unsatisfiable dependency
    • libr3-dev/armel has unsatisfiable dependency
    • libr3-0/armhf has unsatisfiable dependency
    • libr3-dev/armhf has unsatisfiable dependency
    • libr3-0/i386 has unsatisfiable dependency
    • libr3-dev/i386 has unsatisfiable dependency
    • libr3-0/mips64el has unsatisfiable dependency
    • libr3-dev/mips64el has unsatisfiable dependency
    • libr3-0/ppc64el has unsatisfiable dependency
    • libr3-dev/ppc64el has unsatisfiable dependency
    • libr3-0/riscv64 has unsatisfiable dependency
    • libr3-dev/riscv64 has unsatisfiable dependency
    • libr3-0/s390x has unsatisfiable dependency
    • libr3-dev/s390x has unsatisfiable dependency
    • Updating libr3 would introduce bugs in testing: #1000058
    • libr3 unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libr3.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 3347 days old (needed 5 days)
• woff-tools (- to 0:2009.10.04-2)
  • Migration status for woff-tools (- to 0:2009.10.04-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • woff-tools has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3470 days old (needed 5 days)
• psicode (- to 3.4.0-6)
  • Migration status for psicode (- to 3.4.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psicode would introduce bugs in testing: #1075399
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psicode.html
    • 3492 days old (needed 5 days)
• etoys (- to 5.0.2408-1)
  • Migration status for etoys (- to 5.0.2408-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoys squeak-vm (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3574 days old (needed 5 days)
• tvoe (- to 0.1-1)
  • Migration status for tvoe (- to 0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tvoe would introduce bugs in testing: #1075592
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tvoe.html
    • 3819 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)
    • 4214 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)
    • 4247 days old (needed 5 days)
• xfishtank (- to 2.5-1)
  • Migration status for xfishtank (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfishtank would introduce bugs in testing: #1075662
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfishtank.html
    • 4248 days old (needed 5 days)
• i810switch (- to 0.6.5-7.1)
  • Migration status for i810switch (- to 0.6.5-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating i810switch would introduce bugs in testing: #1075078, #1092161
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i810switch.html
    • 4350 days old (needed 5 days)