Generated: 2024.02.23 00:05:14 +0000

• aardvark-dns/s390x (1.4.0-5 to 1.4.0-5)
  • Migration status for aardvark-dns/s390x (1.4.0-5 to 1.4.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aardvark-dns/s390x has unsatisfiable dependency
• architecture-properties/amd64 (0.1.1 to 0.1.1)
  • Migration status for architecture-properties/amd64 (0.1.1 to 0.1.1): Will attempt migration (Any information below is purely informational)
• architecture-properties/armhf (0.1.1 to 0.1.1)
  • Migration status for architecture-properties/armhf (0.1.1 to 0.1.1): Will attempt migration (Any information below is purely informational)
• architecture-properties/i386 (0.1.1 to 0.1.1)
  • Migration status for architecture-properties/i386 (0.1.1 to 0.1.1): Will attempt migration (Any information below is purely informational)
• architecture-properties/mips64el (0.1.1 to 0.1.1)
  • Migration status for architecture-properties/mips64el (0.1.1 to 0.1.1): Will attempt migration (Any information below is purely informational)
• architecture-properties/s390x (0.1.1 to 0.1.1)
  • Migration status for architecture-properties/s390x (0.1.1 to 0.1.1): Will attempt migration (Any information below is purely informational)
• archlinux-keyring_pu (0~20231222-1 to 0~20231113-1~deb12u1)
  • Migration status for archlinux-keyring_pu (0~20231222-1 to 0~20231113-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: archlinux-keyring is newer in the target suite (0~20231222-1 0~20231113-1~deb12u1)
• ben/armel (0.10.3 to 0.10.3)
  • Migration status for ben/armel (0.10.3 to 0.10.3): Will attempt migration (Any information below is purely informational)
    • Depends: ben/armel lwt/armel
• ben/mips64el (0.10.3 to 0.10.3)
  • Migration status for ben/mips64el (0.10.3 to 0.10.3): Will attempt migration (Any information below is purely informational)
    • Depends: ben/mips64el lwt/mips64el
• bind9_pu (1:9.19.21-1 to 1:9.18.24-1)
  • Migration status for bind9_pu (1:9.19.21-1 to 1:9.18.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: bind9 is newer in the target suite (1:9.19.21-1 1:9.18.24-1)
• boost-defaults/amd64 (1.83.0.2 to 1.83.0.2)
  • Migration status for boost-defaults/amd64 (1.83.0.2 to 1.83.0.2): Will attempt migration (Any information below is purely informational)
• boost-defaults/armhf (1.83.0.2 to 1.83.0.2)
  • Migration status for boost-defaults/armhf (1.83.0.2 to 1.83.0.2): Will attempt migration (Any information below is purely informational)
• boost-defaults/i386 (1.83.0.2 to 1.83.0.2)
  • Migration status for boost-defaults/i386 (1.83.0.2 to 1.83.0.2): Will attempt migration (Any information below is purely informational)
• boost-defaults/mips64el (1.83.0.2 to 1.83.0.2)
  • Migration status for boost-defaults/mips64el (1.83.0.2 to 1.83.0.2): Will attempt migration (Any information below is purely informational)
• boost-defaults/s390x (1.83.0.2 to 1.83.0.2)
  • Migration status for boost-defaults/s390x (1.83.0.2 to 1.83.0.2): Will attempt migration (Any information below is purely informational)
• cairo-5c/amd64 (1.21 to 1.21)
  • Migration status for cairo-5c/amd64 (1.21 to 1.21): Will attempt migration (Any information below is purely informational)
• cairo-5c/armhf (1.21 to 1.21)
  • Migration status for cairo-5c/armhf (1.21 to 1.21): Will attempt migration (Any information below is purely informational)
• cairo-5c/i386 (1.21 to 1.21)
  • Migration status for cairo-5c/i386 (1.21 to 1.21): Will attempt migration (Any information below is purely informational)
• cairo-5c/mips64el (1.21 to 1.21)
  • Migration status for cairo-5c/mips64el (1.21 to 1.21): Will attempt migration (Any information below is purely informational)
• cairo-5c/s390x (1.21 to 1.21)
  • Migration status for cairo-5c/s390x (1.21 to 1.21): Will attempt migration (Any information below is purely informational)
• camlp5-buildscripts/amd64 (0.03-1 to 0.03-1)
  • Migration status for camlp5-buildscripts/amd64 (0.03-1 to 0.03-1): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5-buildscripts/amd64 ocaml-logs/amd64
• camlp5-buildscripts/arm64 (0.03-1 to 0.03-1)
  • Migration status for camlp5-buildscripts/arm64 (0.03-1 to 0.03-1): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5-buildscripts/arm64 ocaml-logs/arm64
• camlp5-buildscripts/armhf (0.03-1 to 0.03-1)
  • Migration status for camlp5-buildscripts/armhf (0.03-1 to 0.03-1): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5-buildscripts/armhf ocaml-logs/armhf
• camlp5-buildscripts/i386 (0.03-1 to 0.03-1)
  • Migration status for camlp5-buildscripts/i386 (0.03-1 to 0.03-1): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5-buildscripts/i386 ocaml-logs/i386
• camlp5-buildscripts/ppc64el (0.03-1 to 0.03-1)
  • Migration status for camlp5-buildscripts/ppc64el (0.03-1 to 0.03-1): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5-buildscripts/ppc64el ocaml-logs/ppc64el
• camlp5-buildscripts/s390x (0.03-1 to 0.03-1)
  • Migration status for camlp5-buildscripts/s390x (0.03-1 to 0.03-1): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5-buildscripts/s390x ocaml-logs/s390x
• camlp5/amd64 (8.02.01-2 to 8.02.01-2)
  • Migration status for camlp5/amd64 (8.02.01-2 to 8.02.01-2): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5/amd64 ocaml-logs/amd64
• camlp5/arm64 (8.02.01-2 to 8.02.01-2)
  • Migration status for camlp5/arm64 (8.02.01-2 to 8.02.01-2): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5/arm64 ocaml-logs/arm64
• camlp5/armhf (8.02.01-2 to 8.02.01-2)
  • Migration status for camlp5/armhf (8.02.01-2 to 8.02.01-2): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5/armhf ocaml-logs/armhf
• camlp5/i386 (8.02.01-2 to 8.02.01-2)
  • Migration status for camlp5/i386 (8.02.01-2 to 8.02.01-2): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5/i386 ocaml-logs/i386
• camlp5/ppc64el (8.02.01-2 to 8.02.01-2)
  • Migration status for camlp5/ppc64el (8.02.01-2 to 8.02.01-2): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5/ppc64el ocaml-logs/ppc64el
• camlp5/s390x (8.02.01-2 to 8.02.01-2)
  • Migration status for camlp5/s390x (8.02.01-2 to 8.02.01-2): Will attempt migration (Any information below is purely informational)
    • Depends: camlp5/s390x ocaml-logs/s390x
• camomile/amd64 (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/amd64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: camomile/amd64 ocaml-dune
• camomile/arm64 (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/arm64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: camomile/arm64 ocaml-dune
• camomile/armel (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/armel (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: camomile/armel ocaml-dune
• camomile/armhf (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/armhf (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: camomile/armhf ocaml-dune
• camomile/i386 (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/i386 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: camomile/i386 ocaml-dune
• camomile/mips64el (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/mips64el (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: camomile/mips64el ocaml-dune
• camomile/ppc64el (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/ppc64el (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: camomile/ppc64el ocaml-dune
• camomile/s390x (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/s390x (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: camomile/s390x ocaml-dune
• cdebconf/amd64 (0.271 to 0.271)
  • Migration status for cdebconf/amd64 (0.271 to 0.271): Will attempt migration (Any information below is purely informational)
• cdebconf/armhf (0.271 to 0.271)
  • Migration status for cdebconf/armhf (0.271 to 0.271): Will attempt migration (Any information below is purely informational)
• cdebconf/i386 (0.271 to 0.271)
  • Migration status for cdebconf/i386 (0.271 to 0.271): Will attempt migration (Any information below is purely informational)
• cdebconf/mips64el (0.271 to 0.271)
  • Migration status for cdebconf/mips64el (0.271 to 0.271): Will attempt migration (Any information below is purely informational)
• cdebconf/s390x (0.271 to 0.271)
  • Migration status for cdebconf/s390x (0.271 to 0.271): Will attempt migration (Any information below is purely informational)
• cdo_pu (2.3.0-3 to 2.1.1-1+deb12u1)
  • Migration status for cdo_pu (2.3.0-3 to 2.1.1-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: cdo is newer in the target suite (2.3.0-3 2.1.1-1+deb12u1)
• chiark-tcl/amd64 (1.3.5 to 1.3.5)
  • Migration status for chiark-tcl/amd64 (1.3.5 to 1.3.5): Will attempt migration (Any information below is purely informational)
• chiark-tcl/armhf (1.3.5 to 1.3.5)
  • Migration status for chiark-tcl/armhf (1.3.5 to 1.3.5): Will attempt migration (Any information below is purely informational)
• chiark-tcl/i386 (1.3.5 to 1.3.5)
  • Migration status for chiark-tcl/i386 (1.3.5 to 1.3.5): Will attempt migration (Any information below is purely informational)
• chiark-tcl/mips64el (1.3.5 to 1.3.5)
  • Migration status for chiark-tcl/mips64el (1.3.5 to 1.3.5): Will attempt migration (Any information below is purely informational)
• chiark-tcl/s390x (1.3.5 to 1.3.5)
  • Migration status for chiark-tcl/s390x (1.3.5 to 1.3.5): Will attempt migration (Any information below is purely informational)
• chromium_pu (121.0.6167.160-1 to 121.0.6167.160-1~deb12u1)
  • Migration status for chromium_pu (121.0.6167.160-1 to 121.0.6167.160-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: chromium is newer in the target suite (121.0.6167.160-1 121.0.6167.160-1~deb12u1)
• coq-deriving/amd64 (0.2.0-1 to 0.2.0-1)
  • Migration status for coq-deriving/amd64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-deriving/amd64 ssreflect/amd64
    • Implicit dependency: coq-deriving/amd64 coq-extructures/amd64
• coq-deriving/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for coq-deriving/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-deriving/arm64 ssreflect/arm64
    • Implicit dependency: coq-deriving/arm64 coq-extructures/arm64
• coq-deriving/armhf (0.2.0-1 to 0.2.0-1)
  • Migration status for coq-deriving/armhf (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-deriving/armhf ssreflect/armhf
    • Implicit dependency: coq-deriving/armhf coq-extructures/armhf
• coq-deriving/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for coq-deriving/i386 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-deriving/i386 ssreflect/i386
    • Implicit dependency: coq-deriving/i386 coq-extructures/i386
• coq-deriving/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for coq-deriving/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-deriving/ppc64el ssreflect/ppc64el
    • Implicit dependency: coq-deriving/ppc64el coq-extructures/ppc64el
• coq-deriving/s390x (0.2.0-1 to 0.2.0-1)
  • Migration status for coq-deriving/s390x (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-deriving/s390x ssreflect/s390x
    • Implicit dependency: coq-deriving/s390x coq-extructures/s390x
• coq-elpi/amd64 (1.19.3-2 to 1.19.3-2)
  • Migration status for coq-elpi/amd64 (1.19.3-2 to 1.19.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-elpi/amd64 elpi/amd64
    • Implicit dependency: coq-elpi/amd64 coq-hierarchy-builder/amd64
    • Implicit dependency: coq-elpi/amd64 mathcomp-algebra-tactics/amd64
    • Implicit dependency: coq-elpi/amd64 mathcomp-analysis/amd64
• coq-elpi/arm64 (1.19.3-2 to 1.19.3-2)
  • Migration status for coq-elpi/arm64 (1.19.3-2 to 1.19.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-elpi/arm64 elpi/arm64
    • Implicit dependency: coq-elpi/arm64 coq-hierarchy-builder/arm64
    • Implicit dependency: coq-elpi/arm64 mathcomp-algebra-tactics/arm64
    • Implicit dependency: coq-elpi/arm64 mathcomp-analysis/arm64
• coq-elpi/armhf (1.19.3-2 to 1.19.3-2)
  • Migration status for coq-elpi/armhf (1.19.3-2 to 1.19.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-elpi/armhf elpi/armhf
    • Implicit dependency: coq-elpi/armhf coq-hierarchy-builder/armhf
    • Implicit dependency: coq-elpi/armhf mathcomp-algebra-tactics/armhf
    • Implicit dependency: coq-elpi/armhf mathcomp-analysis/armhf
• coq-elpi/i386 (1.19.3-2 to 1.19.3-2)
  • Migration status for coq-elpi/i386 (1.19.3-2 to 1.19.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-elpi/i386 elpi/i386
    • Implicit dependency: coq-elpi/i386 coq-hierarchy-builder/i386
    • Implicit dependency: coq-elpi/i386 mathcomp-algebra-tactics/i386
    • Implicit dependency: coq-elpi/i386 mathcomp-analysis/i386
• coq-elpi/ppc64el (1.19.3-2 to 1.19.3-2)
  • Migration status for coq-elpi/ppc64el (1.19.3-2 to 1.19.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-elpi/ppc64el elpi/ppc64el
    • Implicit dependency: coq-elpi/ppc64el coq-hierarchy-builder/ppc64el
    • Implicit dependency: coq-elpi/ppc64el mathcomp-algebra-tactics/ppc64el
    • Implicit dependency: coq-elpi/ppc64el mathcomp-analysis/ppc64el
• coq-elpi/s390x (1.19.3-2 to 1.19.3-2)
  • Migration status for coq-elpi/s390x (1.19.3-2 to 1.19.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-elpi/s390x elpi/s390x
    • Implicit dependency: coq-elpi/s390x coq-hierarchy-builder/s390x
    • Implicit dependency: coq-elpi/s390x mathcomp-algebra-tactics/s390x
    • Implicit dependency: coq-elpi/s390x mathcomp-analysis/s390x
• coq-extructures/amd64 (0.4.0-1 to 0.4.0-1)
  • Migration status for coq-extructures/amd64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-extructures/amd64 coq-deriving/amd64
    • Depends: coq-extructures/amd64 ssreflect/amd64
• coq-extructures/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for coq-extructures/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-extructures/arm64 coq-deriving/arm64
    • Depends: coq-extructures/arm64 ssreflect/arm64
• coq-extructures/armhf (0.4.0-1 to 0.4.0-1)
  • Migration status for coq-extructures/armhf (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-extructures/armhf coq-deriving/armhf
    • Depends: coq-extructures/armhf ssreflect/armhf
• coq-extructures/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for coq-extructures/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-extructures/i386 coq-deriving/i386
    • Depends: coq-extructures/i386 ssreflect/i386
• coq-extructures/ppc64el (0.4.0-1 to 0.4.0-1)
  • Migration status for coq-extructures/ppc64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-extructures/ppc64el coq-deriving/ppc64el
    • Depends: coq-extructures/ppc64el ssreflect/ppc64el
• coq-extructures/s390x (0.4.0-1 to 0.4.0-1)
  • Migration status for coq-extructures/s390x (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-extructures/s390x coq-deriving/s390x
    • Depends: coq-extructures/s390x ssreflect/s390x
• coq-hierarchy-builder/amd64 (1.6.0-1 to 1.6.0-1)
  • Migration status for coq-hierarchy-builder/amd64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-hierarchy-builder/amd64 coq-elpi/amd64
    • Implicit dependency: coq-hierarchy-builder/amd64 mathcomp-analysis/amd64
    • Implicit dependency: coq-hierarchy-builder/amd64 ssreflect/amd64
• coq-hierarchy-builder/arm64 (1.6.0-1 to 1.6.0-1)
  • Migration status for coq-hierarchy-builder/arm64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-hierarchy-builder/arm64 coq-elpi/arm64
    • Implicit dependency: coq-hierarchy-builder/arm64 mathcomp-analysis/arm64
    • Implicit dependency: coq-hierarchy-builder/arm64 ssreflect/arm64
• coq-hierarchy-builder/armhf (1.6.0-1 to 1.6.0-1)
  • Migration status for coq-hierarchy-builder/armhf (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-hierarchy-builder/armhf coq-elpi/armhf
    • Implicit dependency: coq-hierarchy-builder/armhf mathcomp-analysis/armhf
    • Implicit dependency: coq-hierarchy-builder/armhf ssreflect/armhf
• coq-hierarchy-builder/i386 (1.6.0-1 to 1.6.0-1)
  • Migration status for coq-hierarchy-builder/i386 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-hierarchy-builder/i386 coq-elpi/i386
    • Implicit dependency: coq-hierarchy-builder/i386 mathcomp-analysis/i386
    • Implicit dependency: coq-hierarchy-builder/i386 ssreflect/i386
• coq-hierarchy-builder/ppc64el (1.6.0-1 to 1.6.0-1)
  • Migration status for coq-hierarchy-builder/ppc64el (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-hierarchy-builder/ppc64el coq-elpi/ppc64el
    • Implicit dependency: coq-hierarchy-builder/ppc64el mathcomp-analysis/ppc64el
    • Implicit dependency: coq-hierarchy-builder/ppc64el ssreflect/ppc64el
• coq-hierarchy-builder/s390x (1.6.0-1 to 1.6.0-1)
  • Migration status for coq-hierarchy-builder/s390x (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-hierarchy-builder/s390x coq-elpi/s390x
    • Implicit dependency: coq-hierarchy-builder/s390x mathcomp-analysis/s390x
    • Implicit dependency: coq-hierarchy-builder/s390x ssreflect/s390x
• coq-interval/amd64 (4.9.0-1 to 4.9.0-1)
  • Migration status for coq-interval/amd64 (4.9.0-1 to 4.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-interval/amd64 coquelicot/amd64
    • Depends: coq-interval/amd64 ssreflect/amd64
• coq-interval/arm64 (4.9.0-1 to 4.9.0-1)
  • Migration status for coq-interval/arm64 (4.9.0-1 to 4.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-interval/arm64 coquelicot/arm64
    • Depends: coq-interval/arm64 ssreflect/arm64
• coq-interval/armhf (4.9.0-1 to 4.9.0-1)
  • Migration status for coq-interval/armhf (4.9.0-1 to 4.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-interval/armhf coquelicot/armhf
    • Depends: coq-interval/armhf ssreflect/armhf
• coq-interval/i386 (4.9.0-1 to 4.9.0-1)
  • Migration status for coq-interval/i386 (4.9.0-1 to 4.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-interval/i386 coquelicot/i386
    • Depends: coq-interval/i386 ssreflect/i386
• coq-interval/ppc64el (4.9.0-1 to 4.9.0-1)
  • Migration status for coq-interval/ppc64el (4.9.0-1 to 4.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-interval/ppc64el coquelicot/ppc64el
    • Depends: coq-interval/ppc64el ssreflect/ppc64el
• coq-interval/s390x (4.9.0-1 to 4.9.0-1)
  • Migration status for coq-interval/s390x (4.9.0-1 to 4.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-interval/s390x coquelicot/s390x
    • Depends: coq-interval/s390x ssreflect/s390x
• coq-quickchick/amd64 (2.0.2-1 to 2.0.2-1)
  • Migration status for coq-quickchick/amd64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-quickchick/amd64 ssreflect/amd64
• coq-quickchick/arm64 (2.0.2-1 to 2.0.2-1)
  • Migration status for coq-quickchick/arm64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-quickchick/arm64 ssreflect/arm64
• coq-quickchick/armhf (2.0.2-1 to 2.0.2-1)
  • Migration status for coq-quickchick/armhf (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-quickchick/armhf ssreflect/armhf
• coq-quickchick/i386 (2.0.2-1 to 2.0.2-1)
  • Migration status for coq-quickchick/i386 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-quickchick/i386 ssreflect/i386
• coq-quickchick/ppc64el (2.0.2-1 to 2.0.2-1)
  • Migration status for coq-quickchick/ppc64el (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-quickchick/ppc64el ssreflect/ppc64el
• coq-quickchick/s390x (2.0.2-1 to 2.0.2-1)
  • Migration status for coq-quickchick/s390x (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-quickchick/s390x ssreflect/s390x
• coq-reglang/amd64 (1.2.1-1 to 1.2.1-1)
  • Migration status for coq-reglang/amd64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-reglang/amd64 ssreflect/amd64
• coq-reglang/arm64 (1.2.1-1 to 1.2.1-1)
  • Migration status for coq-reglang/arm64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-reglang/arm64 ssreflect/arm64
• coq-reglang/armhf (1.2.1-1 to 1.2.1-1)
  • Migration status for coq-reglang/armhf (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-reglang/armhf ssreflect/armhf
• coq-reglang/i386 (1.2.1-1 to 1.2.1-1)
  • Migration status for coq-reglang/i386 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-reglang/i386 ssreflect/i386
• coq-reglang/ppc64el (1.2.1-1 to 1.2.1-1)
  • Migration status for coq-reglang/ppc64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-reglang/ppc64el ssreflect/ppc64el
• coq-reglang/s390x (1.2.1-1 to 1.2.1-1)
  • Migration status for coq-reglang/s390x (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coq-reglang/s390x ssreflect/s390x
• coq-relation-algebra/amd64 (1.7.9-2 to 1.7.9-2)
  • Migration status for coq-relation-algebra/amd64 (1.7.9-2 to 1.7.9-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-relation-algebra/amd64 ssreflect/amd64
• coq-relation-algebra/arm64 (1.7.9-2 to 1.7.9-2)
  • Migration status for coq-relation-algebra/arm64 (1.7.9-2 to 1.7.9-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-relation-algebra/arm64 ssreflect/arm64
• coq-relation-algebra/armhf (1.7.9-2 to 1.7.9-2)
  • Migration status for coq-relation-algebra/armhf (1.7.9-2 to 1.7.9-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-relation-algebra/armhf ssreflect/armhf
• coq-relation-algebra/i386 (1.7.9-2 to 1.7.9-2)
  • Migration status for coq-relation-algebra/i386 (1.7.9-2 to 1.7.9-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-relation-algebra/i386 ssreflect/i386
• coq-relation-algebra/ppc64el (1.7.9-2 to 1.7.9-2)
  • Migration status for coq-relation-algebra/ppc64el (1.7.9-2 to 1.7.9-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-relation-algebra/ppc64el ssreflect/ppc64el
• coq-relation-algebra/s390x (1.7.9-2 to 1.7.9-2)
  • Migration status for coq-relation-algebra/s390x (1.7.9-2 to 1.7.9-2): Will attempt migration (Any information below is purely informational)
    • Depends: coq-relation-algebra/s390x ssreflect/s390x
• coqeal/amd64 (2.0.1-1 to 2.0.1-1)
  • Migration status for coqeal/amd64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coqeal/amd64 mathcomp-real-closed/amd64
    • Depends: coqeal/amd64 ssreflect/amd64
• coqeal/arm64 (2.0.1-1 to 2.0.1-1)
  • Migration status for coqeal/arm64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coqeal/arm64 mathcomp-real-closed/arm64
    • Depends: coqeal/arm64 ssreflect/arm64
• coqeal/armhf (2.0.1-1 to 2.0.1-1)
  • Migration status for coqeal/armhf (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coqeal/armhf mathcomp-real-closed/armhf
    • Depends: coqeal/armhf ssreflect/armhf
• coqeal/i386 (2.0.1-1 to 2.0.1-1)
  • Migration status for coqeal/i386 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coqeal/i386 mathcomp-real-closed/i386
    • Depends: coqeal/i386 ssreflect/i386
• coqeal/ppc64el (2.0.1-1 to 2.0.1-1)
  • Migration status for coqeal/ppc64el (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coqeal/ppc64el mathcomp-real-closed/ppc64el
    • Depends: coqeal/ppc64el ssreflect/ppc64el
• coqeal/s390x (2.0.1-1 to 2.0.1-1)
  • Migration status for coqeal/s390x (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coqeal/s390x mathcomp-real-closed/s390x
    • Depends: coqeal/s390x ssreflect/s390x
• coquelicot/amd64 (3.4.1-1 to 3.4.1-1)
  • Migration status for coquelicot/amd64 (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coquelicot/amd64 ssreflect/amd64
    • Implicit dependency: coquelicot/amd64 coq-interval/amd64
• coquelicot/arm64 (3.4.1-1 to 3.4.1-1)
  • Migration status for coquelicot/arm64 (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coquelicot/arm64 ssreflect/arm64
    • Implicit dependency: coquelicot/arm64 coq-interval/arm64
• coquelicot/armhf (3.4.1-1 to 3.4.1-1)
  • Migration status for coquelicot/armhf (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coquelicot/armhf ssreflect/armhf
    • Implicit dependency: coquelicot/armhf coq-interval/armhf
• coquelicot/i386 (3.4.1-1 to 3.4.1-1)
  • Migration status for coquelicot/i386 (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coquelicot/i386 ssreflect/i386
    • Implicit dependency: coquelicot/i386 coq-interval/i386
• coquelicot/ppc64el (3.4.1-1 to 3.4.1-1)
  • Migration status for coquelicot/ppc64el (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coquelicot/ppc64el ssreflect/ppc64el
    • Implicit dependency: coquelicot/ppc64el coq-interval/ppc64el
• coquelicot/s390x (3.4.1-1 to 3.4.1-1)
  • Migration status for coquelicot/s390x (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: coquelicot/s390x ssreflect/s390x
    • Implicit dependency: coquelicot/s390x coq-interval/s390x
• crmsh_pu (4.6.0-1 to 4.4.1-1+deb12u1)
  • Migration status for crmsh_pu (4.6.0-1 to 4.4.1-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: crmsh is newer in the target suite (4.6.0-1 4.4.1-1+deb12u1)
• db-defaults/amd64 (5.3.3 to 5.3.3)
  • Migration status for db-defaults/amd64 (5.3.3 to 5.3.3): Will attempt migration (Any information below is purely informational)
• db-defaults/armel (5.3.3 to 5.3.3)
  • Migration status for db-defaults/armel (5.3.3 to 5.3.3): Will attempt migration (Any information below is purely informational)
• db-defaults/armhf (5.3.3 to 5.3.3)
  • Migration status for db-defaults/armhf (5.3.3 to 5.3.3): Will attempt migration (Any information below is purely informational)
• db-defaults/i386 (5.3.3 to 5.3.3)
  • Migration status for db-defaults/i386 (5.3.3 to 5.3.3): Will attempt migration (Any information below is purely informational)
• db-defaults/mips64el (5.3.3 to 5.3.3)
  • Migration status for db-defaults/mips64el (5.3.3 to 5.3.3): Will attempt migration (Any information below is purely informational)
• db-defaults/s390x (5.3.3 to 5.3.3)
  • Migration status for db-defaults/s390x (5.3.3 to 5.3.3): Will attempt migration (Any information below is purely informational)
• debian-edu/amd64 (2.12.15 to 2.12.15)
  • Migration status for debian-edu/amd64 (2.12.15 to 2.12.15): Will attempt migration (Any information below is purely informational)
• debian-edu/armel (2.12.15 to 2.12.15)
  • Migration status for debian-edu/armel (2.12.15 to 2.12.15): Will attempt migration (Any information below is purely informational)
• debian-edu/armhf (2.12.15 to 2.12.15)
  • Migration status for debian-edu/armhf (2.12.15 to 2.12.15): Will attempt migration (Any information below is purely informational)
• debian-edu/i386 (2.12.15 to 2.12.15)
  • Migration status for debian-edu/i386 (2.12.15 to 2.12.15): Will attempt migration (Any information below is purely informational)
• debian-edu/mips64el (2.12.15 to 2.12.15)
  • Migration status for debian-edu/mips64el (2.12.15 to 2.12.15): Will attempt migration (Any information below is purely informational)
• debian-edu/s390x (2.12.15 to 2.12.15)
  • Migration status for debian-edu/s390x (2.12.15 to 2.12.15): Will attempt migration (Any information below is purely informational)
• diet-ng/amd64 (1.8.1-3 to 1.8.1-3)
  • Migration status for diet-ng/amd64 (1.8.1-3 to 1.8.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: diet-ng/amd64 ldc (not considered)
    • Invalidated by dependency
• diet-ng/arm64 (1.8.1-3 to 1.8.1-3)
  • Migration status for diet-ng/arm64 (1.8.1-3 to 1.8.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: diet-ng/arm64 ldc (not considered)
    • Invalidated by dependency
• diet-ng/i386 (1.8.1-3 to 1.8.1-3)
  • Migration status for diet-ng/i386 (1.8.1-3 to 1.8.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: diet-ng/i386 ldc (not considered)
    • Invalidated by dependency
• ebook-speaker_pu (6.2.0-5 to 6.2.0-4+deb12u1)
  • Migration status for ebook-speaker_pu (6.2.0-5 to 6.2.0-4+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ebook-speaker is newer in the target suite (6.2.0-5 6.2.0-4+deb12u1)
• edk2_pu (2023.11-6 to 2022.11-6+deb12u1)
  • Migration status for edk2_pu (2023.11-6 to 2022.11-6+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: edk2 is newer in the target suite (2023.11-6 2022.11-6+deb12u1)
• elpi/amd64 (1.17.4-3 to 1.17.4-3)
  • Migration status for elpi/amd64 (1.17.4-3 to 1.17.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: elpi/amd64 menhir
    • Depends: elpi/amd64 ppx-deriving/amd64
    • Depends: elpi/amd64 ppxlib
    • Implicit dependency: elpi/amd64 coq-elpi/amd64
• elpi/arm64 (1.17.4-3 to 1.17.4-3)
  • Migration status for elpi/arm64 (1.17.4-3 to 1.17.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: elpi/arm64 menhir
    • Depends: elpi/arm64 ppx-deriving/arm64
    • Depends: elpi/arm64 ppxlib
    • Implicit dependency: elpi/arm64 coq-elpi/arm64
• elpi/armhf (1.17.4-3 to 1.17.4-3)
  • Migration status for elpi/armhf (1.17.4-3 to 1.17.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: elpi/armhf menhir
    • Depends: elpi/armhf ppx-deriving/armhf
    • Depends: elpi/armhf ppxlib
    • Implicit dependency: elpi/armhf coq-elpi/armhf
• elpi/i386 (1.17.4-3 to 1.17.4-3)
  • Migration status for elpi/i386 (1.17.4-3 to 1.17.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: elpi/i386 menhir
    • Depends: elpi/i386 ppx-deriving/i386
    • Depends: elpi/i386 ppxlib
    • Implicit dependency: elpi/i386 coq-elpi/i386
• elpi/ppc64el (1.17.4-3 to 1.17.4-3)
  • Migration status for elpi/ppc64el (1.17.4-3 to 1.17.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: elpi/ppc64el menhir
    • Depends: elpi/ppc64el ppx-deriving/ppc64el
    • Depends: elpi/ppc64el ppxlib
    • Implicit dependency: elpi/ppc64el coq-elpi/ppc64el
• elpi/s390x (1.17.4-3 to 1.17.4-3)
  • Migration status for elpi/s390x (1.17.4-3 to 1.17.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: elpi/s390x menhir
    • Depends: elpi/s390x ppx-deriving/s390x
    • Depends: elpi/s390x ppxlib
    • Implicit dependency: elpi/s390x coq-elpi/s390x
• engrampa_pu (1.26.2-3 to 1.26.0-1+deb12u2)
  • Migration status for engrampa_pu (1.26.2-3 to 1.26.0-1+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: engrampa is newer in the target suite (1.26.2-3 1.26.0-1+deb12u2)
• fenics/amd64 (2:0.7.0.1 to 2:0.7.0.1)
  • Migration status for fenics/amd64 (2:0.7.0.1 to 2:0.7.0.1): Will attempt migration (Any information below is purely informational)
• fenics/armel (2:0.7.0.1 to 2:0.7.0.1)
  • Migration status for fenics/armel (2:0.7.0.1 to 2:0.7.0.1): Will attempt migration (Any information below is purely informational)
• fenics/armhf (2:0.7.0.1 to 2:0.7.0.1)
  • Migration status for fenics/armhf (2:0.7.0.1 to 2:0.7.0.1): Will attempt migration (Any information below is purely informational)
• fenics/i386 (2:0.7.0.1 to 2:0.7.0.1)
  • Migration status for fenics/i386 (2:0.7.0.1 to 2:0.7.0.1): Will attempt migration (Any information below is purely informational)
• fenics/mips64el (2:0.7.0.1 to 2:0.7.0.1)
  • Migration status for fenics/mips64el (2:0.7.0.1 to 2:0.7.0.1): Will attempt migration (Any information below is purely informational)
• fenics/s390x (2:0.7.0.1 to 2:0.7.0.1)
  • Migration status for fenics/s390x (2:0.7.0.1 to 2:0.7.0.1): Will attempt migration (Any information below is purely informational)
• frama-c/amd64 (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/amd64 (20220511-manganese-5 to 20220511-manganese-5): Will attempt migration (Any information below is purely informational)
    • Depends: frama-c/amd64 lablgtk3
    • Depends: frama-c/amd64 ppx-deriving/amd64
• frama-c/arm64 (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/arm64 (20220511-manganese-5 to 20220511-manganese-5): Will attempt migration (Any information below is purely informational)
    • Depends: frama-c/arm64 lablgtk3
    • Depends: frama-c/arm64 ppx-deriving/arm64
• frama-c/armel (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/armel (20220511-manganese-5 to 20220511-manganese-5): Will attempt migration (Any information below is purely informational)
    • Depends: frama-c/armel lablgtk3
    • Depends: frama-c/armel ppx-deriving/armel
• frama-c/armhf (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/armhf (20220511-manganese-5 to 20220511-manganese-5): Will attempt migration (Any information below is purely informational)
    • Depends: frama-c/armhf lablgtk3
    • Depends: frama-c/armhf ppx-deriving/armhf
• frama-c/i386 (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/i386 (20220511-manganese-5 to 20220511-manganese-5): Will attempt migration (Any information below is purely informational)
    • Depends: frama-c/i386 lablgtk3
    • Depends: frama-c/i386 ppx-deriving/i386
• frama-c/mips64el (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/mips64el (20220511-manganese-5 to 20220511-manganese-5): Will attempt migration (Any information below is purely informational)
    • Depends: frama-c/mips64el lablgtk3
    • Depends: frama-c/mips64el ppx-deriving/mips64el
• frama-c/ppc64el (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/ppc64el (20220511-manganese-5 to 20220511-manganese-5): Will attempt migration (Any information below is purely informational)
    • Depends: frama-c/ppc64el lablgtk3
    • Depends: frama-c/ppc64el ppx-deriving/ppc64el
• frama-c/s390x (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/s390x (20220511-manganese-5 to 20220511-manganese-5): Will attempt migration (Any information below is purely informational)
    • Depends: frama-c/s390x lablgtk3
    • Depends: frama-c/s390x ppx-deriving/s390x
• freetype_pu (2.13.2+dfsg-1 to 2.12.1+dfsg-5+deb12u2)
  • Migration status for freetype_pu (2.13.2+dfsg-1 to 2.12.1+dfsg-5+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: freetype is newer in the target suite (2.13.2+dfsg-1 2.12.1+dfsg-5+deb12u2)
• govarnam/amd64 (1.9.0-2 to 1.9.0-2)
  • Migration status for govarnam/amd64 (1.9.0-2 to 1.9.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: govarnam/amd64 golang-1.21
• govarnam/arm64 (1.9.0-2 to 1.9.0-2)
  • Migration status for govarnam/arm64 (1.9.0-2 to 1.9.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: govarnam/arm64 golang-1.21
• govarnam/armel (1.9.0-2 to 1.9.0-2)
  • Migration status for govarnam/armel (1.9.0-2 to 1.9.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: govarnam/armel golang-1.21
• govarnam/armhf (1.9.0-2 to 1.9.0-2)
  • Migration status for govarnam/armhf (1.9.0-2 to 1.9.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: govarnam/armhf golang-1.21
• govarnam/i386 (1.9.0-2 to 1.9.0-2)
  • Migration status for govarnam/i386 (1.9.0-2 to 1.9.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: govarnam/i386 golang-1.21
• govarnam/ppc64el (1.9.0-2 to 1.9.0-2)
  • Migration status for govarnam/ppc64el (1.9.0-2 to 1.9.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: govarnam/ppc64el golang-1.21
• govarnam/s390x (1.9.0-2 to 1.9.0-2)
  • Migration status for govarnam/s390x (1.9.0-2 to 1.9.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: govarnam/s390x golang-1.21
• gtk-d/amd64 (3.10.0-2 to 3.10.0-2)
  • Migration status for gtk-d/amd64 (3.10.0-2 to 3.10.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gtk-d/amd64 ldc (not considered)
    • Invalidated by dependency
• gtk-d/arm64 (3.10.0-2 to 3.10.0-2)
  • Migration status for gtk-d/arm64 (3.10.0-2 to 3.10.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gtk-d/arm64 ldc (not considered)
    • Invalidated by dependency
• gtk-d/i386 (3.10.0-2 to 3.10.0-2)
  • Migration status for gtk-d/i386 (3.10.0-2 to 3.10.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gtk-d/i386 ldc (not considered)
    • Invalidated by dependency
• gtk-d/s390x (3.10.0-2 to 3.10.0-2)
  • Migration status for gtk-d/s390x (3.10.0-2 to 3.10.0-2): Will attempt migration (Any information below is purely informational)
• harp/amd64 (1.20.2-1 to 1.20.2-1)
  • Migration status for harp/amd64 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
• harp/arm64 (1.20.2-1 to 1.20.2-1)
  • Migration status for harp/arm64 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
• harp/armel (1.20.2-1 to 1.20.2-1)
  • Migration status for harp/armel (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
• harp/armhf (1.20.2-1 to 1.20.2-1)
  • Migration status for harp/armhf (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
• harp/i386 (1.20.2-1 to 1.20.2-1)
  • Migration status for harp/i386 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
• harp/mips64el (1.20.2-1 to 1.20.2-1)
  • Migration status for harp/mips64el (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
• harp/ppc64el (1.20.2-1 to 1.20.2-1)
  • Migration status for harp/ppc64el (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
• harp/s390x (1.20.2-1 to 1.20.2-1)
  • Migration status for harp/s390x (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
• js-of-ocaml-ocamlbuild/amd64 (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/amd64 (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml-ocamlbuild/amd64 ocamlbuild
    • Implicit dependency: js-of-ocaml-ocamlbuild/amd64 eliom
• js-of-ocaml-ocamlbuild/arm64 (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/arm64 (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml-ocamlbuild/arm64 ocamlbuild
    • Implicit dependency: js-of-ocaml-ocamlbuild/arm64 eliom
• js-of-ocaml-ocamlbuild/armel (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/armel (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml-ocamlbuild/armel ocamlbuild
• js-of-ocaml-ocamlbuild/armhf (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/armhf (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml-ocamlbuild/armhf ocamlbuild
    • Implicit dependency: js-of-ocaml-ocamlbuild/armhf eliom
• js-of-ocaml-ocamlbuild/i386 (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/i386 (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml-ocamlbuild/i386 ocamlbuild
    • Implicit dependency: js-of-ocaml-ocamlbuild/i386 eliom
• js-of-ocaml-ocamlbuild/mips64el (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/mips64el (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml-ocamlbuild/mips64el ocamlbuild
• js-of-ocaml-ocamlbuild/ppc64el (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/ppc64el (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml-ocamlbuild/ppc64el ocamlbuild
    • Implicit dependency: js-of-ocaml-ocamlbuild/ppc64el eliom
• js-of-ocaml-ocamlbuild/s390x (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/s390x (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml-ocamlbuild/s390x ocamlbuild
    • Implicit dependency: js-of-ocaml-ocamlbuild/s390x eliom
• laby/armel (0.7.0-2 to 0.7.0-2)
  • Migration status for laby/armel (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: laby/armel lablgtk3
• laby/mips64el (0.7.0-2 to 0.7.0-2)
  • Migration status for laby/mips64el (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: laby/mips64el lablgtk3
• lambda-term/amd64 (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/amd64 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: lambda-term/amd64 lwt/amd64
    • Depends: lambda-term/amd64 ocaml-logs/amd64
• lambda-term/arm64 (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/arm64 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: lambda-term/arm64 lwt/arm64
    • Depends: lambda-term/arm64 ocaml-logs/arm64
• lambda-term/armel (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/armel (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: lambda-term/armel lwt/armel
• lambda-term/armhf (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/armhf (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: lambda-term/armhf lwt/armhf
    • Depends: lambda-term/armhf ocaml-logs/armhf
• lambda-term/i386 (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/i386 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: lambda-term/i386 lwt/i386
    • Depends: lambda-term/i386 ocaml-logs/i386
• lambda-term/mips64el (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/mips64el (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: lambda-term/mips64el lwt/mips64el
• lambda-term/ppc64el (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/ppc64el (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: lambda-term/ppc64el lwt/ppc64el
    • Depends: lambda-term/ppc64el ocaml-logs/ppc64el
• lambda-term/s390x (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/s390x (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: lambda-term/s390x lwt/s390x
    • Depends: lambda-term/s390x ocaml-logs/s390x
• libgit2_pu (1.7.2+ds-1 to 1.5.1+ds-1+deb12u1)
  • Migration status for libgit2_pu (1.7.2+ds-1 to 1.5.1+ds-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libgit2 is newer in the target suite (1.7.2+ds-1 1.5.1+ds-1+deb12u1)
• lwt-log/amd64 (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/amd64 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-log/amd64 lwt/amd64
• lwt-log/arm64 (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/arm64 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-log/arm64 lwt/arm64
• lwt-log/armel (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/armel (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-log/armel lwt/armel
• lwt-log/armhf (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/armhf (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-log/armhf lwt/armhf
• lwt-log/i386 (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/i386 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-log/i386 lwt/i386
• lwt-log/mips64el (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/mips64el (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-log/mips64el lwt/mips64el
• lwt-log/ppc64el (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/ppc64el (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-log/ppc64el lwt/ppc64el
• lwt-log/s390x (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/s390x (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-log/s390x lwt/s390x
• lwt-ssl/amd64 (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/amd64 (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-ssl/amd64 lwt/amd64
• lwt-ssl/arm64 (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/arm64 (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-ssl/arm64 lwt/arm64
• lwt-ssl/armel (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/armel (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-ssl/armel lwt/armel
• lwt-ssl/armhf (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/armhf (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-ssl/armhf lwt/armhf
• lwt-ssl/i386 (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/i386 (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-ssl/i386 lwt/i386
• lwt-ssl/mips64el (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/mips64el (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-ssl/mips64el lwt/mips64el
• lwt-ssl/ppc64el (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/ppc64el (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-ssl/ppc64el lwt/ppc64el
• lwt-ssl/s390x (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/s390x (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: lwt-ssl/s390x lwt/s390x
• lwt/amd64 (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/amd64 (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lwt/amd64 ppxlib
    • Implicit dependency: lwt/amd64 eliom
    • Implicit dependency: lwt/amd64 js-of-ocaml
    • Implicit dependency: lwt/amd64 lambda-term/amd64
    • Implicit dependency: lwt/amd64 lwt-log/amd64
    • Implicit dependency: lwt/amd64 lwt-ssl/amd64
    • Implicit dependency: lwt/amd64 nproc/amd64
    • Implicit dependency: lwt/amd64 nurpawiki/amd64
    • Implicit dependency: lwt/amd64 obus/amd64
    • Implicit dependency: lwt/amd64 ocaml-cohttp/amd64
    • Implicit dependency: lwt/amd64 ocaml-conduit
    • Implicit dependency: lwt/amd64 ocaml-cstruct/amd64
    • Implicit dependency: lwt/amd64 ocaml-inotify
    • Implicit dependency: lwt/amd64 ocaml-logs/amd64
    • Implicit dependency: lwt/amd64 ocaml-usb/amd64
    • Implicit dependency: lwt/amd64 ocsigenserver/amd64
    • Implicit dependency: lwt/amd64 ocsipersist/amd64
    • Implicit dependency: lwt/amd64 ocurl/amd64
    • Implicit dependency: lwt/amd64 utop/amd64
• lwt/arm64 (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/arm64 (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lwt/arm64 ppxlib
    • Implicit dependency: lwt/arm64 eliom
    • Implicit dependency: lwt/arm64 js-of-ocaml
    • Implicit dependency: lwt/arm64 lambda-term/arm64
    • Implicit dependency: lwt/arm64 lwt-log/arm64
    • Implicit dependency: lwt/arm64 lwt-ssl/arm64
    • Implicit dependency: lwt/arm64 nproc/arm64
    • Implicit dependency: lwt/arm64 nurpawiki/arm64
    • Implicit dependency: lwt/arm64 obus/arm64
    • Implicit dependency: lwt/arm64 ocaml-cohttp/arm64
    • Implicit dependency: lwt/arm64 ocaml-conduit
    • Implicit dependency: lwt/arm64 ocaml-cstruct/arm64
    • Implicit dependency: lwt/arm64 ocaml-inotify
    • Implicit dependency: lwt/arm64 ocaml-logs/arm64
    • Implicit dependency: lwt/arm64 ocaml-usb/arm64
    • Implicit dependency: lwt/arm64 ocsigenserver/arm64
    • Implicit dependency: lwt/arm64 ocsipersist/arm64
    • Implicit dependency: lwt/arm64 ocurl/arm64
    • Implicit dependency: lwt/arm64 utop/arm64
• lwt/armel (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/armel (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lwt/armel ppxlib
    • Implicit dependency: lwt/armel ben/armel
    • Implicit dependency: lwt/armel eliom
    • Implicit dependency: lwt/armel js-of-ocaml
    • Implicit dependency: lwt/armel lambda-term/armel
    • Implicit dependency: lwt/armel lwt-log/armel
    • Implicit dependency: lwt/armel lwt-ssl/armel
    • Implicit dependency: lwt/armel nproc/armel
    • Implicit dependency: lwt/armel nurpawiki/armel
    • Implicit dependency: lwt/armel obus/armel
    • Implicit dependency: lwt/armel ocaml-cohttp/armel
    • Implicit dependency: lwt/armel ocaml-conduit
    • Implicit dependency: lwt/armel ocaml-cstruct/armel
    • Implicit dependency: lwt/armel ocaml-inotify
    • Implicit dependency: lwt/armel ocaml-logs/armel
    • Implicit dependency: lwt/armel ocaml-usb/armel
    • Implicit dependency: lwt/armel ocsigenserver/armel
    • Implicit dependency: lwt/armel ocsipersist/armel
    • Implicit dependency: lwt/armel ocurl/armel
    • Implicit dependency: lwt/armel utop/armel
• lwt/armhf (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/armhf (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lwt/armhf ppxlib
    • Implicit dependency: lwt/armhf eliom
    • Implicit dependency: lwt/armhf js-of-ocaml
    • Implicit dependency: lwt/armhf lambda-term/armhf
    • Implicit dependency: lwt/armhf lwt-log/armhf
    • Implicit dependency: lwt/armhf lwt-ssl/armhf
    • Implicit dependency: lwt/armhf nproc/armhf
    • Implicit dependency: lwt/armhf nurpawiki/armhf
    • Implicit dependency: lwt/armhf obus/armhf
    • Implicit dependency: lwt/armhf ocaml-cohttp/armhf
    • Implicit dependency: lwt/armhf ocaml-conduit
    • Implicit dependency: lwt/armhf ocaml-cstruct/armhf
    • Implicit dependency: lwt/armhf ocaml-inotify
    • Implicit dependency: lwt/armhf ocaml-logs/armhf
    • Implicit dependency: lwt/armhf ocaml-usb/armhf
    • Implicit dependency: lwt/armhf ocsigenserver/armhf
    • Implicit dependency: lwt/armhf ocsipersist/armhf
    • Implicit dependency: lwt/armhf ocurl/armhf
    • Implicit dependency: lwt/armhf utop/armhf
• lwt/i386 (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/i386 (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lwt/i386 ppxlib
    • Implicit dependency: lwt/i386 eliom
    • Implicit dependency: lwt/i386 js-of-ocaml
    • Implicit dependency: lwt/i386 lambda-term/i386
    • Implicit dependency: lwt/i386 lwt-log/i386
    • Implicit dependency: lwt/i386 lwt-ssl/i386
    • Implicit dependency: lwt/i386 nproc/i386
    • Implicit dependency: lwt/i386 nurpawiki/i386
    • Implicit dependency: lwt/i386 obus/i386
    • Implicit dependency: lwt/i386 ocaml-cohttp/i386
    • Implicit dependency: lwt/i386 ocaml-conduit
    • Implicit dependency: lwt/i386 ocaml-cstruct/i386
    • Implicit dependency: lwt/i386 ocaml-inotify
    • Implicit dependency: lwt/i386 ocaml-logs/i386
    • Implicit dependency: lwt/i386 ocaml-usb/i386
    • Implicit dependency: lwt/i386 ocsigenserver/i386
    • Implicit dependency: lwt/i386 ocsipersist/i386
    • Implicit dependency: lwt/i386 ocurl/i386
    • Implicit dependency: lwt/i386 utop/i386
• lwt/mips64el (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/mips64el (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lwt/mips64el ppxlib
    • Implicit dependency: lwt/mips64el ben/mips64el
    • Implicit dependency: lwt/mips64el eliom
    • Implicit dependency: lwt/mips64el js-of-ocaml
    • Implicit dependency: lwt/mips64el lambda-term/mips64el
    • Implicit dependency: lwt/mips64el lwt-log/mips64el
    • Implicit dependency: lwt/mips64el lwt-ssl/mips64el
    • Implicit dependency: lwt/mips64el nproc/mips64el
    • Implicit dependency: lwt/mips64el nurpawiki/mips64el
    • Implicit dependency: lwt/mips64el obus/mips64el
    • Implicit dependency: lwt/mips64el ocaml-cohttp/mips64el
    • Implicit dependency: lwt/mips64el ocaml-conduit
    • Implicit dependency: lwt/mips64el ocaml-cstruct/mips64el
    • Implicit dependency: lwt/mips64el ocaml-inotify
    • Implicit dependency: lwt/mips64el ocaml-logs/mips64el
    • Implicit dependency: lwt/mips64el ocaml-usb/mips64el
    • Implicit dependency: lwt/mips64el ocsigenserver/mips64el
    • Implicit dependency: lwt/mips64el ocsipersist/mips64el
    • Implicit dependency: lwt/mips64el ocurl/mips64el
    • Implicit dependency: lwt/mips64el utop/mips64el
• lwt/ppc64el (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/ppc64el (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lwt/ppc64el ppxlib
    • Implicit dependency: lwt/ppc64el eliom
    • Implicit dependency: lwt/ppc64el js-of-ocaml
    • Implicit dependency: lwt/ppc64el lambda-term/ppc64el
    • Implicit dependency: lwt/ppc64el lwt-log/ppc64el
    • Implicit dependency: lwt/ppc64el lwt-ssl/ppc64el
    • Implicit dependency: lwt/ppc64el nproc/ppc64el
    • Implicit dependency: lwt/ppc64el nurpawiki/ppc64el
    • Implicit dependency: lwt/ppc64el obus/ppc64el
    • Implicit dependency: lwt/ppc64el ocaml-cohttp/ppc64el
    • Implicit dependency: lwt/ppc64el ocaml-conduit
    • Implicit dependency: lwt/ppc64el ocaml-cstruct/ppc64el
    • Implicit dependency: lwt/ppc64el ocaml-inotify
    • Implicit dependency: lwt/ppc64el ocaml-logs/ppc64el
    • Implicit dependency: lwt/ppc64el ocaml-usb/ppc64el
    • Implicit dependency: lwt/ppc64el ocsigenserver/ppc64el
    • Implicit dependency: lwt/ppc64el ocsipersist/ppc64el
    • Implicit dependency: lwt/ppc64el ocurl/ppc64el
    • Implicit dependency: lwt/ppc64el utop/ppc64el
• lwt/s390x (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/s390x (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lwt/s390x ppxlib
    • Implicit dependency: lwt/s390x eliom
    • Implicit dependency: lwt/s390x js-of-ocaml
    • Implicit dependency: lwt/s390x lambda-term/s390x
    • Implicit dependency: lwt/s390x lwt-log/s390x
    • Implicit dependency: lwt/s390x lwt-ssl/s390x
    • Implicit dependency: lwt/s390x nproc/s390x
    • Implicit dependency: lwt/s390x nurpawiki/s390x
    • Implicit dependency: lwt/s390x obus/s390x
    • Implicit dependency: lwt/s390x ocaml-cohttp/s390x
    • Implicit dependency: lwt/s390x ocaml-conduit
    • Implicit dependency: lwt/s390x ocaml-cstruct/s390x
    • Implicit dependency: lwt/s390x ocaml-inotify
    • Implicit dependency: lwt/s390x ocaml-logs/s390x
    • Implicit dependency: lwt/s390x ocaml-usb/s390x
    • Implicit dependency: lwt/s390x ocsigenserver/s390x
    • Implicit dependency: lwt/s390x ocsipersist/s390x
    • Implicit dependency: lwt/s390x ocurl/s390x
    • Implicit dependency: lwt/s390x utop/s390x
• lxqt-metapackages/amd64 (32 to 32)
  • Migration status for lxqt-metapackages/amd64 (32 to 32): Will attempt migration (Any information below is purely informational)
• lxqt-metapackages/armel (32 to 32)
  • Migration status for lxqt-metapackages/armel (32 to 32): Will attempt migration (Any information below is purely informational)
• lxqt-metapackages/armhf (32 to 32)
  • Migration status for lxqt-metapackages/armhf (32 to 32): Will attempt migration (Any information below is purely informational)
• lxqt-metapackages/i386 (32 to 32)
  • Migration status for lxqt-metapackages/i386 (32 to 32): Will attempt migration (Any information below is purely informational)
• lxqt-metapackages/mips64el (32 to 32)
  • Migration status for lxqt-metapackages/mips64el (32 to 32): Will attempt migration (Any information below is purely informational)
• lxqt-metapackages/s390x (32 to 32)
  • Migration status for lxqt-metapackages/s390x (32 to 32): Will attempt migration (Any information below is purely informational)
• m17n-lib/amd64 (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/amd64 (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• m17n-lib/arm64 (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/arm64 (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• m17n-lib/armel (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/armel (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• m17n-lib/armhf (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/armhf (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• m17n-lib/i386 (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/i386 (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• m17n-lib/mips64el (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/mips64el (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• m17n-lib/ppc64el (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/ppc64el (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• m17n-lib/s390x (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/s390x (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• malcontent/amd64 (0.11.1-1 to 0.11.1-1)
  • Migration status for malcontent/amd64 (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
• malcontent/arm64 (0.11.1-1 to 0.11.1-1)
  • Migration status for malcontent/arm64 (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
• malcontent/armel (0.11.1-1 to 0.11.1-1)
  • Migration status for malcontent/armel (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
• malcontent/armhf (0.11.1-1 to 0.11.1-1)
  • Migration status for malcontent/armhf (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
• malcontent/i386 (0.11.1-1 to 0.11.1-1)
  • Migration status for malcontent/i386 (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
• malcontent/mips64el (0.11.1-1 to 0.11.1-1)
  • Migration status for malcontent/mips64el (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
• malcontent/ppc64el (0.11.1-1 to 0.11.1-1)
  • Migration status for malcontent/ppc64el (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
• malcontent/s390x (0.11.1-1 to 0.11.1-1)
  • Migration status for malcontent/s390x (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
• mangler/amd64 (1.2.5-5 to 1.2.5-5)
  • Migration status for mangler/amd64 (1.2.5-5 to 1.2.5-5): Will attempt migration (Any information below is purely informational)
• mangler/arm64 (1.2.5-5 to 1.2.5-5)
  • Migration status for mangler/arm64 (1.2.5-5 to 1.2.5-5): Will attempt migration (Any information below is purely informational)
• mangler/armel (1.2.5-5 to 1.2.5-5)
  • Migration status for mangler/armel (1.2.5-5 to 1.2.5-5): Will attempt migration (Any information below is purely informational)
• mangler/armhf (1.2.5-5 to 1.2.5-5)
  • Migration status for mangler/armhf (1.2.5-5 to 1.2.5-5): Will attempt migration (Any information below is purely informational)
• mangler/i386 (1.2.5-5 to 1.2.5-5)
  • Migration status for mangler/i386 (1.2.5-5 to 1.2.5-5): Will attempt migration (Any information below is purely informational)
• mangler/mips64el (1.2.5-5 to 1.2.5-5)
  • Migration status for mangler/mips64el (1.2.5-5 to 1.2.5-5): Will attempt migration (Any information below is purely informational)
• mangler/ppc64el (1.2.5-5 to 1.2.5-5)
  • Migration status for mangler/ppc64el (1.2.5-5 to 1.2.5-5): Will attempt migration (Any information below is purely informational)
• mangler/s390x (1.2.5-5 to 1.2.5-5)
  • Migration status for mangler/s390x (1.2.5-5 to 1.2.5-5): Will attempt migration (Any information below is purely informational)
• mangohud/amd64 (0.6.9.1-2 to 0.6.9.1-2)
  • Migration status for mangohud/amd64 (0.6.9.1-2 to 0.6.9.1-2): Will attempt migration (Any information below is purely informational)
• mangohud/arm64 (0.6.9.1-2 to 0.6.9.1-2)
  • Migration status for mangohud/arm64 (0.6.9.1-2 to 0.6.9.1-2): Will attempt migration (Any information below is purely informational)
• mangohud/armel (0.6.9.1-2 to 0.6.9.1-2)
  • Migration status for mangohud/armel (0.6.9.1-2 to 0.6.9.1-2): Will attempt migration (Any information below is purely informational)
• mangohud/armhf (0.6.9.1-2 to 0.6.9.1-2)
  • Migration status for mangohud/armhf (0.6.9.1-2 to 0.6.9.1-2): Will attempt migration (Any information below is purely informational)
• mangohud/i386 (0.6.9.1-2 to 0.6.9.1-2)
  • Migration status for mangohud/i386 (0.6.9.1-2 to 0.6.9.1-2): Will attempt migration (Any information below is purely informational)
• mangohud/mips64el (0.6.9.1-2 to 0.6.9.1-2)
  • Migration status for mangohud/mips64el (0.6.9.1-2 to 0.6.9.1-2): Will attempt migration (Any information below is purely informational)
• mangohud/ppc64el (0.6.9.1-2 to 0.6.9.1-2)
  • Migration status for mangohud/ppc64el (0.6.9.1-2 to 0.6.9.1-2): Will attempt migration (Any information below is purely informational)
• mangohud/s390x (0.6.9.1-2 to 0.6.9.1-2)
  • Migration status for mangohud/s390x (0.6.9.1-2 to 0.6.9.1-2): Will attempt migration (Any information below is purely informational)
• marco/amd64 (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/amd64 (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• marco/arm64 (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/arm64 (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• marco/armel (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/armel (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• marco/armhf (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/armhf (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• marco/i386 (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/i386 (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• marco/mips64el (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/mips64el (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• marco/ppc64el (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/ppc64el (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• marco/s390x (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/s390x (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• mate-control-center/amd64 (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-control-center/amd64 (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-control-center/arm64 (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-control-center/arm64 (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-control-center/armel (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-control-center/armel (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-control-center/armhf (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-control-center/armhf (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-control-center/i386 (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-control-center/i386 (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-control-center/mips64el (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-control-center/mips64el (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-control-center/ppc64el (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-control-center/ppc64el (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-control-center/s390x (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-control-center/s390x (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-desktop/amd64 (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-desktop/amd64 (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-desktop/arm64 (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-desktop/arm64 (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-desktop/armel (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-desktop/armel (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-desktop/armhf (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-desktop/armhf (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-desktop/i386 (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-desktop/i386 (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-desktop/mips64el (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-desktop/mips64el (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-desktop/ppc64el (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-desktop/ppc64el (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-desktop/s390x (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-desktop/s390x (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-panel/amd64 (1.27.1-2 to 1.27.1-2)
  • Migration status for mate-panel/amd64 (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• mate-panel/arm64 (1.27.1-2 to 1.27.1-2)
  • Migration status for mate-panel/arm64 (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• mate-panel/armel (1.27.1-2 to 1.27.1-2)
  • Migration status for mate-panel/armel (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• mate-panel/armhf (1.27.1-2 to 1.27.1-2)
  • Migration status for mate-panel/armhf (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• mate-panel/i386 (1.27.1-2 to 1.27.1-2)
  • Migration status for mate-panel/i386 (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• mate-panel/mips64el (1.27.1-2 to 1.27.1-2)
  • Migration status for mate-panel/mips64el (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• mate-panel/ppc64el (1.27.1-2 to 1.27.1-2)
  • Migration status for mate-panel/ppc64el (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• mate-panel/s390x (1.27.1-2 to 1.27.1-2)
  • Migration status for mate-panel/s390x (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• mathcomp-algebra-tactics/amd64 (1.2.3-1 to 1.2.3-1)
  • Migration status for mathcomp-algebra-tactics/amd64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-algebra-tactics/amd64 coq-elpi/amd64
    • Depends: mathcomp-algebra-tactics/amd64 mathcomp-zify/amd64
    • Depends: mathcomp-algebra-tactics/amd64 ssreflect/amd64
• mathcomp-algebra-tactics/arm64 (1.2.3-1 to 1.2.3-1)
  • Migration status for mathcomp-algebra-tactics/arm64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-algebra-tactics/arm64 coq-elpi/arm64
    • Depends: mathcomp-algebra-tactics/arm64 mathcomp-zify/arm64
    • Depends: mathcomp-algebra-tactics/arm64 ssreflect/arm64
• mathcomp-algebra-tactics/armhf (1.2.3-1 to 1.2.3-1)
  • Migration status for mathcomp-algebra-tactics/armhf (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-algebra-tactics/armhf coq-elpi/armhf
    • Depends: mathcomp-algebra-tactics/armhf mathcomp-zify/armhf
    • Depends: mathcomp-algebra-tactics/armhf ssreflect/armhf
• mathcomp-algebra-tactics/i386 (1.2.3-1 to 1.2.3-1)
  • Migration status for mathcomp-algebra-tactics/i386 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-algebra-tactics/i386 coq-elpi/i386
    • Depends: mathcomp-algebra-tactics/i386 mathcomp-zify/i386
    • Depends: mathcomp-algebra-tactics/i386 ssreflect/i386
• mathcomp-algebra-tactics/ppc64el (1.2.3-1 to 1.2.3-1)
  • Migration status for mathcomp-algebra-tactics/ppc64el (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-algebra-tactics/ppc64el coq-elpi/ppc64el
    • Depends: mathcomp-algebra-tactics/ppc64el mathcomp-zify/ppc64el
    • Depends: mathcomp-algebra-tactics/ppc64el ssreflect/ppc64el
• mathcomp-algebra-tactics/s390x (1.2.3-1 to 1.2.3-1)
  • Migration status for mathcomp-algebra-tactics/s390x (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-algebra-tactics/s390x coq-elpi/s390x
    • Depends: mathcomp-algebra-tactics/s390x mathcomp-zify/s390x
    • Depends: mathcomp-algebra-tactics/s390x ssreflect/s390x
• mathcomp-analysis/amd64 (1.0.0-1 to 1.0.0-1)
  • Migration status for mathcomp-analysis/amd64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-analysis/amd64 coq-elpi/amd64
    • Depends: mathcomp-analysis/amd64 coq-hierarchy-builder/amd64
    • Depends: mathcomp-analysis/amd64 mathcomp-bigenough/amd64
    • Depends: mathcomp-analysis/amd64 mathcomp-finmap/amd64
    • Depends: mathcomp-analysis/amd64 ssreflect/amd64
• mathcomp-analysis/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for mathcomp-analysis/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-analysis/arm64 coq-elpi/arm64
    • Depends: mathcomp-analysis/arm64 coq-hierarchy-builder/arm64
    • Depends: mathcomp-analysis/arm64 mathcomp-bigenough/arm64
    • Depends: mathcomp-analysis/arm64 mathcomp-finmap/arm64
    • Depends: mathcomp-analysis/arm64 ssreflect/arm64
• mathcomp-analysis/armhf (1.0.0-1 to 1.0.0-1)
  • Migration status for mathcomp-analysis/armhf (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-analysis/armhf coq-elpi/armhf
    • Depends: mathcomp-analysis/armhf coq-hierarchy-builder/armhf
    • Depends: mathcomp-analysis/armhf mathcomp-bigenough/armhf
    • Depends: mathcomp-analysis/armhf mathcomp-finmap/armhf
    • Depends: mathcomp-analysis/armhf ssreflect/armhf
• mathcomp-analysis/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for mathcomp-analysis/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-analysis/i386 coq-elpi/i386
    • Depends: mathcomp-analysis/i386 coq-hierarchy-builder/i386
    • Depends: mathcomp-analysis/i386 mathcomp-bigenough/i386
    • Depends: mathcomp-analysis/i386 mathcomp-finmap/i386
    • Depends: mathcomp-analysis/i386 ssreflect/i386
• mathcomp-analysis/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for mathcomp-analysis/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-analysis/ppc64el coq-elpi/ppc64el
    • Depends: mathcomp-analysis/ppc64el coq-hierarchy-builder/ppc64el
    • Depends: mathcomp-analysis/ppc64el mathcomp-bigenough/ppc64el
    • Depends: mathcomp-analysis/ppc64el mathcomp-finmap/ppc64el
    • Depends: mathcomp-analysis/ppc64el ssreflect/ppc64el
• mathcomp-analysis/s390x (1.0.0-1 to 1.0.0-1)
  • Migration status for mathcomp-analysis/s390x (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-analysis/s390x coq-elpi/s390x
    • Depends: mathcomp-analysis/s390x coq-hierarchy-builder/s390x
    • Depends: mathcomp-analysis/s390x mathcomp-bigenough/s390x
    • Depends: mathcomp-analysis/s390x mathcomp-finmap/s390x
    • Depends: mathcomp-analysis/s390x ssreflect/s390x
• mathcomp-bigenough/amd64 (1.0.1-12 to 1.0.1-12)
  • Migration status for mathcomp-bigenough/amd64 (1.0.1-12 to 1.0.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-bigenough/amd64 ssreflect/amd64
    • Implicit dependency: mathcomp-bigenough/amd64 mathcomp-analysis/amd64
    • Implicit dependency: mathcomp-bigenough/amd64 mathcomp-multinomials/amd64
    • Implicit dependency: mathcomp-bigenough/amd64 mathcomp-real-closed/amd64
• mathcomp-bigenough/arm64 (1.0.1-12 to 1.0.1-12)
  • Migration status for mathcomp-bigenough/arm64 (1.0.1-12 to 1.0.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-bigenough/arm64 ssreflect/arm64
    • Implicit dependency: mathcomp-bigenough/arm64 mathcomp-analysis/arm64
    • Implicit dependency: mathcomp-bigenough/arm64 mathcomp-multinomials/arm64
    • Implicit dependency: mathcomp-bigenough/arm64 mathcomp-real-closed/arm64
• mathcomp-bigenough/armhf (1.0.1-12 to 1.0.1-12)
  • Migration status for mathcomp-bigenough/armhf (1.0.1-12 to 1.0.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-bigenough/armhf ssreflect/armhf
    • Implicit dependency: mathcomp-bigenough/armhf mathcomp-analysis/armhf
    • Implicit dependency: mathcomp-bigenough/armhf mathcomp-multinomials/armhf
    • Implicit dependency: mathcomp-bigenough/armhf mathcomp-real-closed/armhf
• mathcomp-bigenough/i386 (1.0.1-12 to 1.0.1-12)
  • Migration status for mathcomp-bigenough/i386 (1.0.1-12 to 1.0.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-bigenough/i386 ssreflect/i386
    • Implicit dependency: mathcomp-bigenough/i386 mathcomp-analysis/i386
    • Implicit dependency: mathcomp-bigenough/i386 mathcomp-multinomials/i386
    • Implicit dependency: mathcomp-bigenough/i386 mathcomp-real-closed/i386
• mathcomp-bigenough/ppc64el (1.0.1-12 to 1.0.1-12)
  • Migration status for mathcomp-bigenough/ppc64el (1.0.1-12 to 1.0.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-bigenough/ppc64el ssreflect/ppc64el
    • Implicit dependency: mathcomp-bigenough/ppc64el mathcomp-analysis/ppc64el
    • Implicit dependency: mathcomp-bigenough/ppc64el mathcomp-multinomials/ppc64el
    • Implicit dependency: mathcomp-bigenough/ppc64el mathcomp-real-closed/ppc64el
• mathcomp-bigenough/s390x (1.0.1-12 to 1.0.1-12)
  • Migration status for mathcomp-bigenough/s390x (1.0.1-12 to 1.0.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-bigenough/s390x ssreflect/s390x
    • Implicit dependency: mathcomp-bigenough/s390x mathcomp-analysis/s390x
    • Implicit dependency: mathcomp-bigenough/s390x mathcomp-multinomials/s390x
    • Implicit dependency: mathcomp-bigenough/s390x mathcomp-real-closed/s390x
• mathcomp-finmap/amd64 (2.0.0-2 to 2.0.0-2)
  • Migration status for mathcomp-finmap/amd64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-finmap/amd64 ssreflect/amd64
    • Implicit dependency: mathcomp-finmap/amd64 mathcomp-analysis/amd64
    • Implicit dependency: mathcomp-finmap/amd64 mathcomp-multinomials/amd64
• mathcomp-finmap/arm64 (2.0.0-2 to 2.0.0-2)
  • Migration status for mathcomp-finmap/arm64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-finmap/arm64 ssreflect/arm64
    • Implicit dependency: mathcomp-finmap/arm64 mathcomp-analysis/arm64
    • Implicit dependency: mathcomp-finmap/arm64 mathcomp-multinomials/arm64
• mathcomp-finmap/armhf (2.0.0-2 to 2.0.0-2)
  • Migration status for mathcomp-finmap/armhf (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-finmap/armhf ssreflect/armhf
    • Implicit dependency: mathcomp-finmap/armhf mathcomp-analysis/armhf
    • Implicit dependency: mathcomp-finmap/armhf mathcomp-multinomials/armhf
• mathcomp-finmap/i386 (2.0.0-2 to 2.0.0-2)
  • Migration status for mathcomp-finmap/i386 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-finmap/i386 ssreflect/i386
    • Implicit dependency: mathcomp-finmap/i386 mathcomp-analysis/i386
    • Implicit dependency: mathcomp-finmap/i386 mathcomp-multinomials/i386
• mathcomp-finmap/ppc64el (2.0.0-2 to 2.0.0-2)
  • Migration status for mathcomp-finmap/ppc64el (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-finmap/ppc64el ssreflect/ppc64el
    • Implicit dependency: mathcomp-finmap/ppc64el mathcomp-analysis/ppc64el
    • Implicit dependency: mathcomp-finmap/ppc64el mathcomp-multinomials/ppc64el
• mathcomp-finmap/s390x (2.0.0-2 to 2.0.0-2)
  • Migration status for mathcomp-finmap/s390x (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-finmap/s390x ssreflect/s390x
    • Implicit dependency: mathcomp-finmap/s390x mathcomp-analysis/s390x
    • Implicit dependency: mathcomp-finmap/s390x mathcomp-multinomials/s390x
• mathcomp-multinomials/amd64 (2.2.0-1 to 2.2.0-1)
  • Migration status for mathcomp-multinomials/amd64 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-multinomials/amd64 mathcomp-bigenough/amd64
    • Depends: mathcomp-multinomials/amd64 mathcomp-finmap/amd64
    • Depends: mathcomp-multinomials/amd64 ssreflect/amd64
• mathcomp-multinomials/arm64 (2.2.0-1 to 2.2.0-1)
  • Migration status for mathcomp-multinomials/arm64 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-multinomials/arm64 mathcomp-bigenough/arm64
    • Depends: mathcomp-multinomials/arm64 mathcomp-finmap/arm64
    • Depends: mathcomp-multinomials/arm64 ssreflect/arm64
• mathcomp-multinomials/armhf (2.2.0-1 to 2.2.0-1)
  • Migration status for mathcomp-multinomials/armhf (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-multinomials/armhf mathcomp-bigenough/armhf
    • Depends: mathcomp-multinomials/armhf mathcomp-finmap/armhf
    • Depends: mathcomp-multinomials/armhf ssreflect/armhf
• mathcomp-multinomials/i386 (2.2.0-1 to 2.2.0-1)
  • Migration status for mathcomp-multinomials/i386 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-multinomials/i386 mathcomp-bigenough/i386
    • Depends: mathcomp-multinomials/i386 mathcomp-finmap/i386
    • Depends: mathcomp-multinomials/i386 ssreflect/i386
• mathcomp-multinomials/ppc64el (2.2.0-1 to 2.2.0-1)
  • Migration status for mathcomp-multinomials/ppc64el (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-multinomials/ppc64el mathcomp-bigenough/ppc64el
    • Depends: mathcomp-multinomials/ppc64el mathcomp-finmap/ppc64el
    • Depends: mathcomp-multinomials/ppc64el ssreflect/ppc64el
• mathcomp-multinomials/s390x (2.2.0-1 to 2.2.0-1)
  • Migration status for mathcomp-multinomials/s390x (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-multinomials/s390x mathcomp-bigenough/s390x
    • Depends: mathcomp-multinomials/s390x mathcomp-finmap/s390x
    • Depends: mathcomp-multinomials/s390x ssreflect/s390x
• mathcomp-real-closed/amd64 (2.0.0-1 to 2.0.0-1)
  • Migration status for mathcomp-real-closed/amd64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-real-closed/amd64 mathcomp-bigenough/amd64
    • Depends: mathcomp-real-closed/amd64 ssreflect/amd64
    • Implicit dependency: mathcomp-real-closed/amd64 coqeal/amd64
• mathcomp-real-closed/arm64 (2.0.0-1 to 2.0.0-1)
  • Migration status for mathcomp-real-closed/arm64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-real-closed/arm64 mathcomp-bigenough/arm64
    • Depends: mathcomp-real-closed/arm64 ssreflect/arm64
    • Implicit dependency: mathcomp-real-closed/arm64 coqeal/arm64
• mathcomp-real-closed/armhf (2.0.0-1 to 2.0.0-1)
  • Migration status for mathcomp-real-closed/armhf (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-real-closed/armhf mathcomp-bigenough/armhf
    • Depends: mathcomp-real-closed/armhf ssreflect/armhf
    • Implicit dependency: mathcomp-real-closed/armhf coqeal/armhf
• mathcomp-real-closed/i386 (2.0.0-1 to 2.0.0-1)
  • Migration status for mathcomp-real-closed/i386 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-real-closed/i386 mathcomp-bigenough/i386
    • Depends: mathcomp-real-closed/i386 ssreflect/i386
    • Implicit dependency: mathcomp-real-closed/i386 coqeal/i386
• mathcomp-real-closed/ppc64el (2.0.0-1 to 2.0.0-1)
  • Migration status for mathcomp-real-closed/ppc64el (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-real-closed/ppc64el mathcomp-bigenough/ppc64el
    • Depends: mathcomp-real-closed/ppc64el ssreflect/ppc64el
    • Implicit dependency: mathcomp-real-closed/ppc64el coqeal/ppc64el
• mathcomp-real-closed/s390x (2.0.0-1 to 2.0.0-1)
  • Migration status for mathcomp-real-closed/s390x (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-real-closed/s390x mathcomp-bigenough/s390x
    • Depends: mathcomp-real-closed/s390x ssreflect/s390x
    • Implicit dependency: mathcomp-real-closed/s390x coqeal/s390x
• mathcomp-zify/amd64 (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1)
  • Migration status for mathcomp-zify/amd64 (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-zify/amd64 ssreflect/amd64
    • Implicit dependency: mathcomp-zify/amd64 mathcomp-algebra-tactics/amd64
• mathcomp-zify/arm64 (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1)
  • Migration status for mathcomp-zify/arm64 (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-zify/arm64 ssreflect/arm64
    • Implicit dependency: mathcomp-zify/arm64 mathcomp-algebra-tactics/arm64
• mathcomp-zify/armhf (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1)
  • Migration status for mathcomp-zify/armhf (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-zify/armhf ssreflect/armhf
    • Implicit dependency: mathcomp-zify/armhf mathcomp-algebra-tactics/armhf
• mathcomp-zify/i386 (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1)
  • Migration status for mathcomp-zify/i386 (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-zify/i386 ssreflect/i386
    • Implicit dependency: mathcomp-zify/i386 mathcomp-algebra-tactics/i386
• mathcomp-zify/ppc64el (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1)
  • Migration status for mathcomp-zify/ppc64el (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-zify/ppc64el ssreflect/ppc64el
    • Implicit dependency: mathcomp-zify/ppc64el mathcomp-algebra-tactics/ppc64el
• mathcomp-zify/s390x (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1)
  • Migration status for mathcomp-zify/s390x (1.5.0+2.0+8.16-1 to 1.5.0+2.0+8.16-1): Will attempt migration (Any information below is purely informational)
    • Depends: mathcomp-zify/s390x ssreflect/s390x
    • Implicit dependency: mathcomp-zify/s390x mathcomp-algebra-tactics/s390x
• mathic/amd64 (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/amd64 (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mathic/arm64 (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/arm64 (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mathic/armel (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/armel (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mathic/armhf (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/armhf (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mathic/i386 (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/i386 (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mathic/mips64el (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/mips64el (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mathic/ppc64el (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/ppc64el (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mathic/s390x (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/s390x (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mbt/amd64 (3.6-3 to 3.6-3)
  • Migration status for mbt/amd64 (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• mbt/arm64 (3.6-3 to 3.6-3)
  • Migration status for mbt/arm64 (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• mbt/armel (3.6-3 to 3.6-3)
  • Migration status for mbt/armel (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• mbt/armhf (3.6-3 to 3.6-3)
  • Migration status for mbt/armhf (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• mbt/i386 (3.6-3 to 3.6-3)
  • Migration status for mbt/i386 (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• mbt/mips64el (3.6-3 to 3.6-3)
  • Migration status for mbt/mips64el (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• mbt/ppc64el (3.6-3 to 3.6-3)
  • Migration status for mbt/ppc64el (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• mbt/s390x (3.6-3 to 3.6-3)
  • Migration status for mbt/s390x (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• mcpp/amd64 (2.7.2-5 to 2.7.2-5)
  • Migration status for mcpp/amd64 (2.7.2-5 to 2.7.2-5): Will attempt migration (Any information below is purely informational)
• mcpp/arm64 (2.7.2-5 to 2.7.2-5)
  • Migration status for mcpp/arm64 (2.7.2-5 to 2.7.2-5): Will attempt migration (Any information below is purely informational)
• mcpp/armel (2.7.2-5 to 2.7.2-5)
  • Migration status for mcpp/armel (2.7.2-5 to 2.7.2-5): Will attempt migration (Any information below is purely informational)
• mcpp/armhf (2.7.2-5 to 2.7.2-5)
  • Migration status for mcpp/armhf (2.7.2-5 to 2.7.2-5): Will attempt migration (Any information below is purely informational)
• mcpp/i386 (2.7.2-5 to 2.7.2-5)
  • Migration status for mcpp/i386 (2.7.2-5 to 2.7.2-5): Will attempt migration (Any information below is purely informational)
• mcpp/mips64el (2.7.2-5 to 2.7.2-5)
  • Migration status for mcpp/mips64el (2.7.2-5 to 2.7.2-5): Will attempt migration (Any information below is purely informational)
• mcpp/ppc64el (2.7.2-5 to 2.7.2-5)
  • Migration status for mcpp/ppc64el (2.7.2-5 to 2.7.2-5): Will attempt migration (Any information below is purely informational)
• mcpp/s390x (2.7.2-5 to 2.7.2-5)
  • Migration status for mcpp/s390x (2.7.2-5 to 2.7.2-5): Will attempt migration (Any information below is purely informational)
• md4c/amd64 (0.4.8-1 to 0.4.8-1)
  • Migration status for md4c/amd64 (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• md4c/arm64 (0.4.8-1 to 0.4.8-1)
  • Migration status for md4c/arm64 (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• md4c/armel (0.4.8-1 to 0.4.8-1)
  • Migration status for md4c/armel (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• md4c/armhf (0.4.8-1 to 0.4.8-1)
  • Migration status for md4c/armhf (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• md4c/i386 (0.4.8-1 to 0.4.8-1)
  • Migration status for md4c/i386 (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• md4c/mips64el (0.4.8-1 to 0.4.8-1)
  • Migration status for md4c/mips64el (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• md4c/ppc64el (0.4.8-1 to 0.4.8-1)
  • Migration status for md4c/ppc64el (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• md4c/s390x (0.4.8-1 to 0.4.8-1)
  • Migration status for md4c/s390x (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• mdbtools/amd64 (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1)
  • Migration status for mdbtools/amd64 (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• mdbtools/arm64 (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1)
  • Migration status for mdbtools/arm64 (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• mdbtools/armel (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1)
  • Migration status for mdbtools/armel (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• mdbtools/armhf (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1)
  • Migration status for mdbtools/armhf (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• mdbtools/i386 (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1)
  • Migration status for mdbtools/i386 (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• mdbtools/mips64el (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1)
  • Migration status for mdbtools/mips64el (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• mdbtools/ppc64el (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1)
  • Migration status for mdbtools/ppc64el (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• mdbtools/s390x (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1)
  • Migration status for mdbtools/s390x (1.0.0+dfsg-1.1 to 1.0.0+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• meanwhile/amd64 (1.1.1-2 to 1.1.1-2)
  • Migration status for meanwhile/amd64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• meanwhile/arm64 (1.1.1-2 to 1.1.1-2)
  • Migration status for meanwhile/arm64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• meanwhile/armel (1.1.1-2 to 1.1.1-2)
  • Migration status for meanwhile/armel (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• meanwhile/armhf (1.1.1-2 to 1.1.1-2)
  • Migration status for meanwhile/armhf (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• meanwhile/i386 (1.1.1-2 to 1.1.1-2)
  • Migration status for meanwhile/i386 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• meanwhile/mips64el (1.1.1-2 to 1.1.1-2)
  • Migration status for meanwhile/mips64el (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• meanwhile/ppc64el (1.1.1-2 to 1.1.1-2)
  • Migration status for meanwhile/ppc64el (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• meanwhile/s390x (1.1.1-2 to 1.1.1-2)
  • Migration status for meanwhile/s390x (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• med-fichier/amd64 (4.1.0+repack-4 to 4.1.0+repack-4)
  • Migration status for med-fichier/amd64 (4.1.0+repack-4 to 4.1.0+repack-4): Will attempt migration (Any information below is purely informational)
• med-fichier/arm64 (4.1.0+repack-4 to 4.1.0+repack-4)
  • Migration status for med-fichier/arm64 (4.1.0+repack-4 to 4.1.0+repack-4): Will attempt migration (Any information below is purely informational)
• med-fichier/armel (4.1.0+repack-4 to 4.1.0+repack-4)
  • Migration status for med-fichier/armel (4.1.0+repack-4 to 4.1.0+repack-4): Will attempt migration (Any information below is purely informational)
• med-fichier/armhf (4.1.0+repack-4 to 4.1.0+repack-4)
  • Migration status for med-fichier/armhf (4.1.0+repack-4 to 4.1.0+repack-4): Will attempt migration (Any information below is purely informational)
• med-fichier/i386 (4.1.0+repack-4 to 4.1.0+repack-4)
  • Migration status for med-fichier/i386 (4.1.0+repack-4 to 4.1.0+repack-4): Will attempt migration (Any information below is purely informational)
• med-fichier/ppc64el (4.1.0+repack-4 to 4.1.0+repack-4)
  • Migration status for med-fichier/ppc64el (4.1.0+repack-4 to 4.1.0+repack-4): Will attempt migration (Any information below is purely informational)
• med-fichier/s390x (4.1.0+repack-4 to 4.1.0+repack-4)
  • Migration status for med-fichier/s390x (4.1.0+repack-4 to 4.1.0+repack-4): Will attempt migration (Any information below is purely informational)
• mediascanner2/amd64 (0.115-4 to 0.115-4)
  • Migration status for mediascanner2/amd64 (0.115-4 to 0.115-4): Will attempt migration (Any information below is purely informational)
• mediascanner2/arm64 (0.115-4 to 0.115-4)
  • Migration status for mediascanner2/arm64 (0.115-4 to 0.115-4): Will attempt migration (Any information below is purely informational)
• mediascanner2/armel (0.115-4 to 0.115-4)
  • Migration status for mediascanner2/armel (0.115-4 to 0.115-4): Will attempt migration (Any information below is purely informational)
• mediascanner2/armhf (0.115-4 to 0.115-4)
  • Migration status for mediascanner2/armhf (0.115-4 to 0.115-4): Will attempt migration (Any information below is purely informational)
• mediascanner2/i386 (0.115-4 to 0.115-4)
  • Migration status for mediascanner2/i386 (0.115-4 to 0.115-4): Will attempt migration (Any information below is purely informational)
• mediascanner2/mips64el (0.115-4 to 0.115-4)
  • Migration status for mediascanner2/mips64el (0.115-4 to 0.115-4): Will attempt migration (Any information below is purely informational)
• mediascanner2/ppc64el (0.115-4 to 0.115-4)
  • Migration status for mediascanner2/ppc64el (0.115-4 to 0.115-4): Will attempt migration (Any information below is purely informational)
• mediascanner2/s390x (0.115-4 to 0.115-4)
  • Migration status for mediascanner2/s390x (0.115-4 to 0.115-4): Will attempt migration (Any information below is purely informational)
• memkind/amd64 (1.14.0-3 to 1.14.0-3)
  • Migration status for memkind/amd64 (1.14.0-3 to 1.14.0-3): Will attempt migration (Any information below is purely informational)
• memkind/arm64 (1.14.0-3 to 1.14.0-3)
  • Migration status for memkind/arm64 (1.14.0-3 to 1.14.0-3): Will attempt migration (Any information below is purely informational)
• memkind/mips64el (1.14.0-3 to 1.14.0-3)
  • Migration status for memkind/mips64el (1.14.0-3 to 1.14.0-3): Will attempt migration (Any information below is purely informational)
• memkind/ppc64el (1.14.0-3 to 1.14.0-3)
  • Migration status for memkind/ppc64el (1.14.0-3 to 1.14.0-3): Will attempt migration (Any information below is purely informational)
• menu-cache/amd64 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/amd64 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• menu-cache/arm64 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/arm64 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• menu-cache/armel (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/armel (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• menu-cache/armhf (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/armhf (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• menu-cache/i386 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/i386 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• menu-cache/mips64el (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/mips64el (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• menu-cache/ppc64el (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/ppc64el (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• menu-cache/s390x (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/s390x (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• meschach/amd64 (1.2b-17 to 1.2b-17)
  • Migration status for meschach/amd64 (1.2b-17 to 1.2b-17): Will attempt migration (Any information below is purely informational)
• meschach/arm64 (1.2b-17 to 1.2b-17)
  • Migration status for meschach/arm64 (1.2b-17 to 1.2b-17): Will attempt migration (Any information below is purely informational)
• meschach/armel (1.2b-17 to 1.2b-17)
  • Migration status for meschach/armel (1.2b-17 to 1.2b-17): Will attempt migration (Any information below is purely informational)
• meschach/armhf (1.2b-17 to 1.2b-17)
  • Migration status for meschach/armhf (1.2b-17 to 1.2b-17): Will attempt migration (Any information below is purely informational)
• meschach/i386 (1.2b-17 to 1.2b-17)
  • Migration status for meschach/i386 (1.2b-17 to 1.2b-17): Will attempt migration (Any information below is purely informational)
• meschach/mips64el (1.2b-17 to 1.2b-17)
  • Migration status for meschach/mips64el (1.2b-17 to 1.2b-17): Will attempt migration (Any information below is purely informational)
• meschach/ppc64el (1.2b-17 to 1.2b-17)
  • Migration status for meschach/ppc64el (1.2b-17 to 1.2b-17): Will attempt migration (Any information below is purely informational)
• meschach/s390x (1.2b-17 to 1.2b-17)
  • Migration status for meschach/s390x (1.2b-17 to 1.2b-17): Will attempt migration (Any information below is purely informational)
• meshoptimizer/amd64 (0.20+dfsg-1 to 0.20+dfsg-1)
  • Migration status for meshoptimizer/amd64 (0.20+dfsg-1 to 0.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• meshoptimizer/arm64 (0.20+dfsg-1 to 0.20+dfsg-1)
  • Migration status for meshoptimizer/arm64 (0.20+dfsg-1 to 0.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• meshoptimizer/armel (0.20+dfsg-1 to 0.20+dfsg-1)
  • Migration status for meshoptimizer/armel (0.20+dfsg-1 to 0.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• meshoptimizer/armhf (0.20+dfsg-1 to 0.20+dfsg-1)
  • Migration status for meshoptimizer/armhf (0.20+dfsg-1 to 0.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• meshoptimizer/i386 (0.20+dfsg-1 to 0.20+dfsg-1)
  • Migration status for meshoptimizer/i386 (0.20+dfsg-1 to 0.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• meshoptimizer/mips64el (0.20+dfsg-1 to 0.20+dfsg-1)
  • Migration status for meshoptimizer/mips64el (0.20+dfsg-1 to 0.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• meshoptimizer/ppc64el (0.20+dfsg-1 to 0.20+dfsg-1)
  • Migration status for meshoptimizer/ppc64el (0.20+dfsg-1 to 0.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• meshoptimizer/s390x (0.20+dfsg-1 to 0.20+dfsg-1)
  • Migration status for meshoptimizer/s390x (0.20+dfsg-1 to 0.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• metacity/amd64 (1:3.50.0-1 to 1:3.50.0-1)
  • Migration status for metacity/amd64 (1:3.50.0-1 to 1:3.50.0-1): Will attempt migration (Any information below is purely informational)
• metacity/arm64 (1:3.50.0-1 to 1:3.50.0-1)
  • Migration status for metacity/arm64 (1:3.50.0-1 to 1:3.50.0-1): Will attempt migration (Any information below is purely informational)
• metacity/armel (1:3.50.0-1 to 1:3.50.0-1)
  • Migration status for metacity/armel (1:3.50.0-1 to 1:3.50.0-1): Will attempt migration (Any information below is purely informational)
• metacity/armhf (1:3.50.0-1 to 1:3.50.0-1)
  • Migration status for metacity/armhf (1:3.50.0-1 to 1:3.50.0-1): Will attempt migration (Any information below is purely informational)
• metacity/i386 (1:3.50.0-1 to 1:3.50.0-1)
  • Migration status for metacity/i386 (1:3.50.0-1 to 1:3.50.0-1): Will attempt migration (Any information below is purely informational)
• metacity/mips64el (1:3.50.0-1 to 1:3.50.0-1)
  • Migration status for metacity/mips64el (1:3.50.0-1 to 1:3.50.0-1): Will attempt migration (Any information below is purely informational)
• metacity/ppc64el (1:3.50.0-1 to 1:3.50.0-1)
  • Migration status for metacity/ppc64el (1:3.50.0-1 to 1:3.50.0-1): Will attempt migration (Any information below is purely informational)
• metacity/s390x (1:3.50.0-1 to 1:3.50.0-1)
  • Migration status for metacity/s390x (1:3.50.0-1 to 1:3.50.0-1): Will attempt migration (Any information below is purely informational)
• metis/amd64 (5.1.0.dfsg-7 to 5.1.0.dfsg-7)
  • Migration status for metis/amd64 (5.1.0.dfsg-7 to 5.1.0.dfsg-7): Will attempt migration (Any information below is purely informational)
• metis/arm64 (5.1.0.dfsg-7 to 5.1.0.dfsg-7)
  • Migration status for metis/arm64 (5.1.0.dfsg-7 to 5.1.0.dfsg-7): Will attempt migration (Any information below is purely informational)
• metis/armel (5.1.0.dfsg-7 to 5.1.0.dfsg-7)
  • Migration status for metis/armel (5.1.0.dfsg-7 to 5.1.0.dfsg-7): Will attempt migration (Any information below is purely informational)
• metis/armhf (5.1.0.dfsg-7 to 5.1.0.dfsg-7)
  • Migration status for metis/armhf (5.1.0.dfsg-7 to 5.1.0.dfsg-7): Will attempt migration (Any information below is purely informational)
• metis/i386 (5.1.0.dfsg-7 to 5.1.0.dfsg-7)
  • Migration status for metis/i386 (5.1.0.dfsg-7 to 5.1.0.dfsg-7): Will attempt migration (Any information below is purely informational)
• metis/mips64el (5.1.0.dfsg-7 to 5.1.0.dfsg-7)
  • Migration status for metis/mips64el (5.1.0.dfsg-7 to 5.1.0.dfsg-7): Will attempt migration (Any information below is purely informational)
• metis/ppc64el (5.1.0.dfsg-7 to 5.1.0.dfsg-7)
  • Migration status for metis/ppc64el (5.1.0.dfsg-7 to 5.1.0.dfsg-7): Will attempt migration (Any information below is purely informational)
• metis/s390x (5.1.0.dfsg-7 to 5.1.0.dfsg-7)
  • Migration status for metis/s390x (5.1.0.dfsg-7 to 5.1.0.dfsg-7): Will attempt migration (Any information below is purely informational)
• metrohash/amd64 (1.1.3-4 to 1.1.3-4)
  • Migration status for metrohash/amd64 (1.1.3-4 to 1.1.3-4): Will attempt migration (Any information below is purely informational)
• metrohash/arm64 (1.1.3-4 to 1.1.3-4)
  • Migration status for metrohash/arm64 (1.1.3-4 to 1.1.3-4): Will attempt migration (Any information below is purely informational)
• metrohash/armel (1.1.3-4 to 1.1.3-4)
  • Migration status for metrohash/armel (1.1.3-4 to 1.1.3-4): Will attempt migration (Any information below is purely informational)
• metrohash/armhf (1.1.3-4 to 1.1.3-4)
  • Migration status for metrohash/armhf (1.1.3-4 to 1.1.3-4): Will attempt migration (Any information below is purely informational)
• metrohash/i386 (1.1.3-4 to 1.1.3-4)
  • Migration status for metrohash/i386 (1.1.3-4 to 1.1.3-4): Will attempt migration (Any information below is purely informational)
• metrohash/mips64el (1.1.3-4 to 1.1.3-4)
  • Migration status for metrohash/mips64el (1.1.3-4 to 1.1.3-4): Will attempt migration (Any information below is purely informational)
• metrohash/ppc64el (1.1.3-4 to 1.1.3-4)
  • Migration status for metrohash/ppc64el (1.1.3-4 to 1.1.3-4): Will attempt migration (Any information below is purely informational)
• metrohash/s390x (1.1.3-4 to 1.1.3-4)
  • Migration status for metrohash/s390x (1.1.3-4 to 1.1.3-4): Will attempt migration (Any information below is purely informational)
• mfem/amd64 (4.5.2+ds-1.4 to 4.5.2+ds-1.4)
  • Migration status for mfem/amd64 (4.5.2+ds-1.4 to 4.5.2+ds-1.4): Will attempt migration (Any information below is purely informational)
• mfem/arm64 (4.5.2+ds-1.4 to 4.5.2+ds-1.4)
  • Migration status for mfem/arm64 (4.5.2+ds-1.4 to 4.5.2+ds-1.4): Will attempt migration (Any information below is purely informational)
• mfem/armel (4.5.2+ds-1.4 to 4.5.2+ds-1.4)
  • Migration status for mfem/armel (4.5.2+ds-1.4 to 4.5.2+ds-1.4): Will attempt migration (Any information below is purely informational)
• mfem/armhf (4.5.2+ds-1.4 to 4.5.2+ds-1.4)
  • Migration status for mfem/armhf (4.5.2+ds-1.4 to 4.5.2+ds-1.4): Will attempt migration (Any information below is purely informational)
• mfem/i386 (4.5.2+ds-1.4 to 4.5.2+ds-1.4)
  • Migration status for mfem/i386 (4.5.2+ds-1.4 to 4.5.2+ds-1.4): Will attempt migration (Any information below is purely informational)
• mfem/mips64el (4.5.2+ds-1.4 to 4.5.2+ds-1.4)
  • Migration status for mfem/mips64el (4.5.2+ds-1.4 to 4.5.2+ds-1.4): Will attempt migration (Any information below is purely informational)
• mfem/ppc64el (4.5.2+ds-1.4 to 4.5.2+ds-1.4)
  • Migration status for mfem/ppc64el (4.5.2+ds-1.4 to 4.5.2+ds-1.4): Will attempt migration (Any information below is purely informational)
• mfem/s390x (4.5.2+ds-1.4 to 4.5.2+ds-1.4)
  • Migration status for mfem/s390x (4.5.2+ds-1.4 to 4.5.2+ds-1.4): Will attempt migration (Any information below is purely informational)
• mhash/amd64 (0.9.9.9-9 to 0.9.9.9-9)
  • Migration status for mhash/amd64 (0.9.9.9-9 to 0.9.9.9-9): Will attempt migration (Any information below is purely informational)
• mhash/arm64 (0.9.9.9-9 to 0.9.9.9-9)
  • Migration status for mhash/arm64 (0.9.9.9-9 to 0.9.9.9-9): Will attempt migration (Any information below is purely informational)
• mhash/armel (0.9.9.9-9 to 0.9.9.9-9)
  • Migration status for mhash/armel (0.9.9.9-9 to 0.9.9.9-9): Will attempt migration (Any information below is purely informational)
• mhash/armhf (0.9.9.9-9 to 0.9.9.9-9)
  • Migration status for mhash/armhf (0.9.9.9-9 to 0.9.9.9-9): Will attempt migration (Any information below is purely informational)
• mhash/i386 (0.9.9.9-9 to 0.9.9.9-9)
  • Migration status for mhash/i386 (0.9.9.9-9 to 0.9.9.9-9): Will attempt migration (Any information below is purely informational)
• mhash/mips64el (0.9.9.9-9 to 0.9.9.9-9)
  • Migration status for mhash/mips64el (0.9.9.9-9 to 0.9.9.9-9): Will attempt migration (Any information below is purely informational)
• mhash/ppc64el (0.9.9.9-9 to 0.9.9.9-9)
  • Migration status for mhash/ppc64el (0.9.9.9-9 to 0.9.9.9-9): Will attempt migration (Any information below is purely informational)
• mhash/s390x (0.9.9.9-9 to 0.9.9.9-9)
  • Migration status for mhash/s390x (0.9.9.9-9 to 0.9.9.9-9): Will attempt migration (Any information below is purely informational)
• mimalloc/amd64 (2.1.2+ds-2 to 2.1.2+ds-2)
  • Migration status for mimalloc/amd64 (2.1.2+ds-2 to 2.1.2+ds-2): Will attempt migration (Any information below is purely informational)
• mimalloc/arm64 (2.1.2+ds-2 to 2.1.2+ds-2)
  • Migration status for mimalloc/arm64 (2.1.2+ds-2 to 2.1.2+ds-2): Will attempt migration (Any information below is purely informational)
• mimalloc/armel (2.1.2+ds-2 to 2.1.2+ds-2)
  • Migration status for mimalloc/armel (2.1.2+ds-2 to 2.1.2+ds-2): Will attempt migration (Any information below is purely informational)
• mimalloc/armhf (2.1.2+ds-2 to 2.1.2+ds-2)
  • Migration status for mimalloc/armhf (2.1.2+ds-2 to 2.1.2+ds-2): Will attempt migration (Any information below is purely informational)
• mimalloc/i386 (2.1.2+ds-2 to 2.1.2+ds-2)
  • Migration status for mimalloc/i386 (2.1.2+ds-2 to 2.1.2+ds-2): Will attempt migration (Any information below is purely informational)
• mimalloc/mips64el (2.1.2+ds-2 to 2.1.2+ds-2)
  • Migration status for mimalloc/mips64el (2.1.2+ds-2 to 2.1.2+ds-2): Will attempt migration (Any information below is purely informational)
• mimalloc/ppc64el (2.1.2+ds-2 to 2.1.2+ds-2)
  • Migration status for mimalloc/ppc64el (2.1.2+ds-2 to 2.1.2+ds-2): Will attempt migration (Any information below is purely informational)
• mimalloc/s390x (2.1.2+ds-2 to 2.1.2+ds-2)
  • Migration status for mimalloc/s390x (2.1.2+ds-2 to 2.1.2+ds-2): Will attempt migration (Any information below is purely informational)
• mini18n/amd64 (0.2.1-2 to 0.2.1-2)
  • Migration status for mini18n/amd64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• mini18n/arm64 (0.2.1-2 to 0.2.1-2)
  • Migration status for mini18n/arm64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• mini18n/armel (0.2.1-2 to 0.2.1-2)
  • Migration status for mini18n/armel (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• mini18n/armhf (0.2.1-2 to 0.2.1-2)
  • Migration status for mini18n/armhf (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• mini18n/i386 (0.2.1-2 to 0.2.1-2)
  • Migration status for mini18n/i386 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• mini18n/mips64el (0.2.1-2 to 0.2.1-2)
  • Migration status for mini18n/mips64el (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• mini18n/ppc64el (0.2.1-2 to 0.2.1-2)
  • Migration status for mini18n/ppc64el (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• mini18n/s390x (0.2.1-2 to 0.2.1-2)
  • Migration status for mini18n/s390x (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• minimap/amd64 (0.2-8 to 0.2-8)
  • Migration status for minimap/amd64 (0.2-8 to 0.2-8): Will attempt migration (Any information below is purely informational)
• minimap/arm64 (0.2-8 to 0.2-8)
  • Migration status for minimap/arm64 (0.2-8 to 0.2-8): Will attempt migration (Any information below is purely informational)
• minimap/armel (0.2-8 to 0.2-8)
  • Migration status for minimap/armel (0.2-8 to 0.2-8): Will attempt migration (Any information below is purely informational)
• minimap/armhf (0.2-8 to 0.2-8)
  • Migration status for minimap/armhf (0.2-8 to 0.2-8): Will attempt migration (Any information below is purely informational)
• minimap/i386 (0.2-8 to 0.2-8)
  • Migration status for minimap/i386 (0.2-8 to 0.2-8): Will attempt migration (Any information below is purely informational)
• minimap/mips64el (0.2-8 to 0.2-8)
  • Migration status for minimap/mips64el (0.2-8 to 0.2-8): Will attempt migration (Any information below is purely informational)
• minimap/ppc64el (0.2-8 to 0.2-8)
  • Migration status for minimap/ppc64el (0.2-8 to 0.2-8): Will attempt migration (Any information below is purely informational)
• minimap/s390x (0.2-8 to 0.2-8)
  • Migration status for minimap/s390x (0.2-8 to 0.2-8): Will attempt migration (Any information below is purely informational)
• minpack/amd64 (19961126+dfsg1-5 to 19961126+dfsg1-5)
  • Migration status for minpack/amd64 (19961126+dfsg1-5 to 19961126+dfsg1-5): Will attempt migration (Any information below is purely informational)
• minpack/arm64 (19961126+dfsg1-5 to 19961126+dfsg1-5)
  • Migration status for minpack/arm64 (19961126+dfsg1-5 to 19961126+dfsg1-5): Will attempt migration (Any information below is purely informational)
• minpack/armel (19961126+dfsg1-5 to 19961126+dfsg1-5)
  • Migration status for minpack/armel (19961126+dfsg1-5 to 19961126+dfsg1-5): Will attempt migration (Any information below is purely informational)
• minpack/armhf (19961126+dfsg1-5 to 19961126+dfsg1-5)
  • Migration status for minpack/armhf (19961126+dfsg1-5 to 19961126+dfsg1-5): Will attempt migration (Any information below is purely informational)
• minpack/i386 (19961126+dfsg1-5 to 19961126+dfsg1-5)
  • Migration status for minpack/i386 (19961126+dfsg1-5 to 19961126+dfsg1-5): Will attempt migration (Any information below is purely informational)
• minpack/mips64el (19961126+dfsg1-5 to 19961126+dfsg1-5)
  • Migration status for minpack/mips64el (19961126+dfsg1-5 to 19961126+dfsg1-5): Will attempt migration (Any information below is purely informational)
• minpack/ppc64el (19961126+dfsg1-5 to 19961126+dfsg1-5)
  • Migration status for minpack/ppc64el (19961126+dfsg1-5 to 19961126+dfsg1-5): Will attempt migration (Any information below is purely informational)
• minpack/s390x (19961126+dfsg1-5 to 19961126+dfsg1-5)
  • Migration status for minpack/s390x (19961126+dfsg1-5 to 19961126+dfsg1-5): Will attempt migration (Any information below is purely informational)
• mjpegtools/amd64 (1:2.1.0+debian-8 to 1:2.1.0+debian-8)
  • Migration status for mjpegtools/amd64 (1:2.1.0+debian-8 to 1:2.1.0+debian-8): Will attempt migration (Any information below is purely informational)
• mjpegtools/arm64 (1:2.1.0+debian-8 to 1:2.1.0+debian-8)
  • Migration status for mjpegtools/arm64 (1:2.1.0+debian-8 to 1:2.1.0+debian-8): Will attempt migration (Any information below is purely informational)
• mjpegtools/armel (1:2.1.0+debian-8 to 1:2.1.0+debian-8)
  • Migration status for mjpegtools/armel (1:2.1.0+debian-8 to 1:2.1.0+debian-8): Will attempt migration (Any information below is purely informational)
• mjpegtools/armhf (1:2.1.0+debian-8 to 1:2.1.0+debian-8)
  • Migration status for mjpegtools/armhf (1:2.1.0+debian-8 to 1:2.1.0+debian-8): Will attempt migration (Any information below is purely informational)
• mjpegtools/i386 (1:2.1.0+debian-8 to 1:2.1.0+debian-8)
  • Migration status for mjpegtools/i386 (1:2.1.0+debian-8 to 1:2.1.0+debian-8): Will attempt migration (Any information below is purely informational)
• mjpegtools/mips64el (1:2.1.0+debian-8 to 1:2.1.0+debian-8)
  • Migration status for mjpegtools/mips64el (1:2.1.0+debian-8 to 1:2.1.0+debian-8): Will attempt migration (Any information below is purely informational)
• mjpegtools/ppc64el (1:2.1.0+debian-8 to 1:2.1.0+debian-8)
  • Migration status for mjpegtools/ppc64el (1:2.1.0+debian-8 to 1:2.1.0+debian-8): Will attempt migration (Any information below is purely informational)
• mjpegtools/s390x (1:2.1.0+debian-8 to 1:2.1.0+debian-8)
  • Migration status for mjpegtools/s390x (1:2.1.0+debian-8 to 1:2.1.0+debian-8): Will attempt migration (Any information below is purely informational)
• mlpost/amd64 (0.9-5 to 0.9-5)
  • Migration status for mlpost/amd64 (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
    • Depends: mlpost/amd64 ocaml-bitstring/amd64
• mlpost/arm64 (0.9-5 to 0.9-5)
  • Migration status for mlpost/arm64 (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
    • Depends: mlpost/arm64 ocaml-bitstring/arm64
• mlpost/armel (0.9-5 to 0.9-5)
  • Migration status for mlpost/armel (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
    • Depends: mlpost/armel ocaml-bitstring/armel
• mlpost/armhf (0.9-5 to 0.9-5)
  • Migration status for mlpost/armhf (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
    • Depends: mlpost/armhf ocaml-bitstring/armhf
• mlpost/i386 (0.9-5 to 0.9-5)
  • Migration status for mlpost/i386 (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
    • Depends: mlpost/i386 ocaml-bitstring/i386
• mlpost/mips64el (0.9-5 to 0.9-5)
  • Migration status for mlpost/mips64el (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
    • Depends: mlpost/mips64el ocaml-bitstring/mips64el
• mlpost/ppc64el (0.9-5 to 0.9-5)
  • Migration status for mlpost/ppc64el (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
    • Depends: mlpost/ppc64el ocaml-bitstring/ppc64el
• mlpost/s390x (0.9-5 to 0.9-5)
  • Migration status for mlpost/s390x (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
    • Depends: mlpost/s390x ocaml-bitstring/s390x
• mlt/amd64 (7.22.0-1 to 7.22.0-1)
  • Migration status for mlt/amd64 (7.22.0-1 to 7.22.0-1): Will attempt migration (Any information below is purely informational)
• mlt/arm64 (7.22.0-1 to 7.22.0-1)
  • Migration status for mlt/arm64 (7.22.0-1 to 7.22.0-1): Will attempt migration (Any information below is purely informational)
• mlt/armel (7.22.0-1 to 7.22.0-1)
  • Migration status for mlt/armel (7.22.0-1 to 7.22.0-1): Will attempt migration (Any information below is purely informational)
• mlt/armhf (7.22.0-1 to 7.22.0-1)
  • Migration status for mlt/armhf (7.22.0-1 to 7.22.0-1): Will attempt migration (Any information below is purely informational)
• mlt/i386 (7.22.0-1 to 7.22.0-1)
  • Migration status for mlt/i386 (7.22.0-1 to 7.22.0-1): Will attempt migration (Any information below is purely informational)
• mlt/ppc64el (7.22.0-1 to 7.22.0-1)
  • Migration status for mlt/ppc64el (7.22.0-1 to 7.22.0-1): Will attempt migration (Any information below is purely informational)
• mlt/s390x (7.22.0-1 to 7.22.0-1)
  • Migration status for mlt/s390x (7.22.0-1 to 7.22.0-1): Will attempt migration (Any information below is purely informational)
• mlterm/amd64 (3.9.3-1 to 3.9.3-1)
  • Migration status for mlterm/amd64 (3.9.3-1 to 3.9.3-1): Will attempt migration (Any information below is purely informational)
• mlterm/arm64 (3.9.3-1 to 3.9.3-1)
  • Migration status for mlterm/arm64 (3.9.3-1 to 3.9.3-1): Will attempt migration (Any information below is purely informational)
• mlterm/armhf (3.9.3-1 to 3.9.3-1)
  • Migration status for mlterm/armhf (3.9.3-1 to 3.9.3-1): Will attempt migration (Any information below is purely informational)
• mlterm/i386 (3.9.3-1 to 3.9.3-1)
  • Migration status for mlterm/i386 (3.9.3-1 to 3.9.3-1): Will attempt migration (Any information below is purely informational)
• mlterm/mips64el (3.9.3-1 to 3.9.3-1)
  • Migration status for mlterm/mips64el (3.9.3-1 to 3.9.3-1): Will attempt migration (Any information below is purely informational)
• mlterm/ppc64el (3.9.3-1 to 3.9.3-1)
  • Migration status for mlterm/ppc64el (3.9.3-1 to 3.9.3-1): Will attempt migration (Any information below is purely informational)
• mlterm/s390x (3.9.3-1 to 3.9.3-1)
  • Migration status for mlterm/s390x (3.9.3-1 to 3.9.3-1): Will attempt migration (Any information below is purely informational)
• mmdb/amd64 (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/amd64 (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmdb/arm64 (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/arm64 (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmdb/armel (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/armel (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmdb/armhf (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/armhf (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmdb/i386 (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/i386 (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmdb/mips64el (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/mips64el (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmdb/ppc64el (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/ppc64el (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmdb/s390x (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/s390x (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmlib/amd64 (1.4.2-2 to 1.4.2-2)
  • Migration status for mmlib/amd64 (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• mmlib/arm64 (1.4.2-2 to 1.4.2-2)
  • Migration status for mmlib/arm64 (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• mmlib/armel (1.4.2-2 to 1.4.2-2)
  • Migration status for mmlib/armel (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• mmlib/armhf (1.4.2-2 to 1.4.2-2)
  • Migration status for mmlib/armhf (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• mmlib/i386 (1.4.2-2 to 1.4.2-2)
  • Migration status for mmlib/i386 (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• mmlib/mips64el (1.4.2-2 to 1.4.2-2)
  • Migration status for mmlib/mips64el (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• mmlib/ppc64el (1.4.2-2 to 1.4.2-2)
  • Migration status for mmlib/ppc64el (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• mmlib/s390x (1.4.2-2 to 1.4.2-2)
  • Migration status for mmlib/s390x (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• moc/amd64 (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/amd64 (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• moc/arm64 (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/arm64 (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• moc/armel (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/armel (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• moc/armhf (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/armhf (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• moc/i386 (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/i386 (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• moc/mips64el (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/mips64el (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• moc/ppc64el (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/ppc64el (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• moc/s390x (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/s390x (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/amd64 (5.107.0-1 to 5.107.0-1)
  • Migration status for modemmanager-qt/amd64 (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/arm64 (5.107.0-1 to 5.107.0-1)
  • Migration status for modemmanager-qt/arm64 (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/armel (5.107.0-1 to 5.107.0-1)
  • Migration status for modemmanager-qt/armel (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/armhf (5.107.0-1 to 5.107.0-1)
  • Migration status for modemmanager-qt/armhf (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/i386 (5.107.0-1 to 5.107.0-1)
  • Migration status for modemmanager-qt/i386 (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/mips64el (5.107.0-1 to 5.107.0-1)
  • Migration status for modemmanager-qt/mips64el (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/ppc64el (5.107.0-1 to 5.107.0-1)
  • Migration status for modemmanager-qt/ppc64el (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/s390x (5.107.0-1 to 5.107.0-1)
  • Migration status for modemmanager-qt/s390x (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• modest/amd64 (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2)
  • Migration status for modest/amd64 (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2): Will attempt migration (Any information below is purely informational)
• modest/arm64 (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2)
  • Migration status for modest/arm64 (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2): Will attempt migration (Any information below is purely informational)
• modest/armhf (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2)
  • Migration status for modest/armhf (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2): Will attempt migration (Any information below is purely informational)
• modest/i386 (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2)
  • Migration status for modest/i386 (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2): Will attempt migration (Any information below is purely informational)
• modest/mips64el (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2)
  • Migration status for modest/mips64el (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2): Will attempt migration (Any information below is purely informational)
• modest/ppc64el (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2)
  • Migration status for modest/ppc64el (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2): Will attempt migration (Any information below is purely informational)
• modest/s390x (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2)
  • Migration status for modest/s390x (0.0~git20210803.2540a03+ds-2 to 0.0~git20210803.2540a03+ds-2): Will attempt migration (Any information below is purely informational)
• monado/amd64 (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2)
  • Migration status for monado/amd64 (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2): Will attempt migration (Any information below is purely informational)
• monado/arm64 (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2)
  • Migration status for monado/arm64 (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2): Will attempt migration (Any information below is purely informational)
• monado/armel (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2)
  • Migration status for monado/armel (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2): Will attempt migration (Any information below is purely informational)
• monado/armhf (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2)
  • Migration status for monado/armhf (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2): Will attempt migration (Any information below is purely informational)
• monado/i386 (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2)
  • Migration status for monado/i386 (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2): Will attempt migration (Any information below is purely informational)
• monado/ppc64el (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2)
  • Migration status for monado/ppc64el (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2): Will attempt migration (Any information below is purely informational)
• monado/s390x (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2)
  • Migration status for monado/s390x (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2): Will attempt migration (Any information below is purely informational)
• moonshot-trust-router/amd64 (3.5.4+2 to 3.5.4+2)
  • Migration status for moonshot-trust-router/amd64 (3.5.4+2 to 3.5.4+2): Will attempt migration (Any information below is purely informational)
• moonshot-trust-router/arm64 (3.5.4+2 to 3.5.4+2)
  • Migration status for moonshot-trust-router/arm64 (3.5.4+2 to 3.5.4+2): Will attempt migration (Any information below is purely informational)
• moonshot-trust-router/armel (3.5.4+2 to 3.5.4+2)
  • Migration status for moonshot-trust-router/armel (3.5.4+2 to 3.5.4+2): Will attempt migration (Any information below is purely informational)
• moonshot-trust-router/armhf (3.5.4+2 to 3.5.4+2)
  • Migration status for moonshot-trust-router/armhf (3.5.4+2 to 3.5.4+2): Will attempt migration (Any information below is purely informational)
• moonshot-trust-router/i386 (3.5.4+2 to 3.5.4+2)
  • Migration status for moonshot-trust-router/i386 (3.5.4+2 to 3.5.4+2): Will attempt migration (Any information below is purely informational)
• moonshot-trust-router/mips64el (3.5.4+2 to 3.5.4+2)
  • Migration status for moonshot-trust-router/mips64el (3.5.4+2 to 3.5.4+2): Will attempt migration (Any information below is purely informational)
• moonshot-trust-router/ppc64el (3.5.4+2 to 3.5.4+2)
  • Migration status for moonshot-trust-router/ppc64el (3.5.4+2 to 3.5.4+2): Will attempt migration (Any information below is purely informational)
• moonshot-trust-router/s390x (3.5.4+2 to 3.5.4+2)
  • Migration status for moonshot-trust-router/s390x (3.5.4+2 to 3.5.4+2): Will attempt migration (Any information below is purely informational)
• moosefs/amd64 (3.0.117-1 to 3.0.117-1)
  • Migration status for moosefs/amd64 (3.0.117-1 to 3.0.117-1): Will attempt migration (Any information below is purely informational)
• moosefs/arm64 (3.0.117-1 to 3.0.117-1)
  • Migration status for moosefs/arm64 (3.0.117-1 to 3.0.117-1): Will attempt migration (Any information below is purely informational)
• moosefs/armel (3.0.117-1 to 3.0.117-1)
  • Migration status for moosefs/armel (3.0.117-1 to 3.0.117-1): Will attempt migration (Any information below is purely informational)
• moosefs/armhf (3.0.117-1 to 3.0.117-1)
  • Migration status for moosefs/armhf (3.0.117-1 to 3.0.117-1): Will attempt migration (Any information below is purely informational)
• moosefs/i386 (3.0.117-1 to 3.0.117-1)
  • Migration status for moosefs/i386 (3.0.117-1 to 3.0.117-1): Will attempt migration (Any information below is purely informational)
• moosefs/mips64el (3.0.117-1 to 3.0.117-1)
  • Migration status for moosefs/mips64el (3.0.117-1 to 3.0.117-1): Will attempt migration (Any information below is purely informational)
• moosefs/ppc64el (3.0.117-1 to 3.0.117-1)
  • Migration status for moosefs/ppc64el (3.0.117-1 to 3.0.117-1): Will attempt migration (Any information below is purely informational)
• moosefs/s390x (3.0.117-1 to 3.0.117-1)
  • Migration status for moosefs/s390x (3.0.117-1 to 3.0.117-1): Will attempt migration (Any information below is purely informational)
• morbig/amd64 (0.10.4-7 to 0.10.4-7)
  • Migration status for morbig/amd64 (0.10.4-7 to 0.10.4-7): Will attempt migration (Any information below is purely informational)
    • Depends: morbig/amd64 menhir
    • Depends: morbig/amd64 ocaml-visitors/amd64
    • Depends: morbig/amd64 ppx-deriving/amd64
    • Depends: morbig/amd64 ppx-deriving-yojson/amd64
    • Implicit dependency: morbig/amd64 morsmall/amd64
• morbig/arm64 (0.10.4-7 to 0.10.4-7)
  • Migration status for morbig/arm64 (0.10.4-7 to 0.10.4-7): Will attempt migration (Any information below is purely informational)
    • Depends: morbig/arm64 menhir
    • Depends: morbig/arm64 ocaml-visitors/arm64
    • Depends: morbig/arm64 ppx-deriving/arm64
    • Depends: morbig/arm64 ppx-deriving-yojson/arm64
    • Implicit dependency: morbig/arm64 morsmall/arm64
• morbig/armel (0.10.4-7 to 0.10.4-7)
  • Migration status for morbig/armel (0.10.4-7 to 0.10.4-7): Will attempt migration (Any information below is purely informational)
    • Depends: morbig/armel menhir
    • Depends: morbig/armel ocaml-visitors/armel
    • Depends: morbig/armel ppx-deriving/armel
    • Depends: morbig/armel ppx-deriving-yojson/armel
    • Implicit dependency: morbig/armel morsmall/armel
• morbig/armhf (0.10.4-7 to 0.10.4-7)
  • Migration status for morbig/armhf (0.10.4-7 to 0.10.4-7): Will attempt migration (Any information below is purely informational)
    • Depends: morbig/armhf menhir
    • Depends: morbig/armhf ocaml-visitors/armhf
    • Depends: morbig/armhf ppx-deriving/armhf
    • Depends: morbig/armhf ppx-deriving-yojson/armhf
    • Implicit dependency: morbig/armhf morsmall/armhf
• morbig/i386 (0.10.4-7 to 0.10.4-7)
  • Migration status for morbig/i386 (0.10.4-7 to 0.10.4-7): Will attempt migration (Any information below is purely informational)
    • Depends: morbig/i386 menhir
    • Depends: morbig/i386 ocaml-visitors/i386
    • Depends: morbig/i386 ppx-deriving/i386
    • Depends: morbig/i386 ppx-deriving-yojson/i386
    • Implicit dependency: morbig/i386 morsmall/i386
• morbig/mips64el (0.10.4-7 to 0.10.4-7)
  • Migration status for morbig/mips64el (0.10.4-7 to 0.10.4-7): Will attempt migration (Any information below is purely informational)
    • Depends: morbig/mips64el menhir
    • Depends: morbig/mips64el ocaml-visitors/mips64el
    • Depends: morbig/mips64el ppx-deriving/mips64el
    • Depends: morbig/mips64el ppx-deriving-yojson/mips64el
    • Implicit dependency: morbig/mips64el morsmall/mips64el
• morbig/ppc64el (0.10.4-7 to 0.10.4-7)
  • Migration status for morbig/ppc64el (0.10.4-7 to 0.10.4-7): Will attempt migration (Any information below is purely informational)
    • Depends: morbig/ppc64el menhir
    • Depends: morbig/ppc64el ocaml-visitors/ppc64el
    • Depends: morbig/ppc64el ppx-deriving/ppc64el
    • Depends: morbig/ppc64el ppx-deriving-yojson/ppc64el
    • Implicit dependency: morbig/ppc64el morsmall/ppc64el
• morbig/s390x (0.10.4-7 to 0.10.4-7)
  • Migration status for morbig/s390x (0.10.4-7 to 0.10.4-7): Will attempt migration (Any information below is purely informational)
    • Depends: morbig/s390x menhir
    • Depends: morbig/s390x ocaml-visitors/s390x
    • Depends: morbig/s390x ppx-deriving/s390x
    • Depends: morbig/s390x ppx-deriving-yojson/s390x
    • Implicit dependency: morbig/s390x morsmall/s390x
• morsmall/amd64 (0.3.0-6 to 0.3.0-6)
  • Migration status for morsmall/amd64 (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: morsmall/amd64 morbig/amd64
    • Depends: morsmall/amd64 ocaml-visitors/amd64
    • Depends: morsmall/amd64 ppx-deriving/amd64
    • Depends: morsmall/amd64 ppx-deriving-yojson/amd64
• morsmall/arm64 (0.3.0-6 to 0.3.0-6)
  • Migration status for morsmall/arm64 (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: morsmall/arm64 morbig/arm64
    • Depends: morsmall/arm64 ocaml-visitors/arm64
    • Depends: morsmall/arm64 ppx-deriving/arm64
    • Depends: morsmall/arm64 ppx-deriving-yojson/arm64
• morsmall/armel (0.3.0-6 to 0.3.0-6)
  • Migration status for morsmall/armel (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: morsmall/armel morbig/armel
    • Depends: morsmall/armel ocaml-visitors/armel
    • Depends: morsmall/armel ppx-deriving/armel
    • Depends: morsmall/armel ppx-deriving-yojson/armel
• morsmall/armhf (0.3.0-6 to 0.3.0-6)
  • Migration status for morsmall/armhf (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: morsmall/armhf morbig/armhf
    • Depends: morsmall/armhf ocaml-visitors/armhf
    • Depends: morsmall/armhf ppx-deriving/armhf
    • Depends: morsmall/armhf ppx-deriving-yojson/armhf
• morsmall/i386 (0.3.0-6 to 0.3.0-6)
  • Migration status for morsmall/i386 (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: morsmall/i386 morbig/i386
    • Depends: morsmall/i386 ocaml-visitors/i386
    • Depends: morsmall/i386 ppx-deriving/i386
    • Depends: morsmall/i386 ppx-deriving-yojson/i386
• morsmall/mips64el (0.3.0-6 to 0.3.0-6)
  • Migration status for morsmall/mips64el (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: morsmall/mips64el morbig/mips64el
    • Depends: morsmall/mips64el ocaml-visitors/mips64el
    • Depends: morsmall/mips64el ppx-deriving/mips64el
    • Depends: morsmall/mips64el ppx-deriving-yojson/mips64el
• morsmall/ppc64el (0.3.0-6 to 0.3.0-6)
  • Migration status for morsmall/ppc64el (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: morsmall/ppc64el morbig/ppc64el
    • Depends: morsmall/ppc64el ocaml-visitors/ppc64el
    • Depends: morsmall/ppc64el ppx-deriving/ppc64el
    • Depends: morsmall/ppc64el ppx-deriving-yojson/ppc64el
• morsmall/s390x (0.3.0-6 to 0.3.0-6)
  • Migration status for morsmall/s390x (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: morsmall/s390x morbig/s390x
    • Depends: morsmall/s390x ocaml-visitors/s390x
    • Depends: morsmall/s390x ppx-deriving/s390x
    • Depends: morsmall/s390x ppx-deriving-yojson/s390x
• mosquitto/amd64 (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/amd64 (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• mosquitto/arm64 (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/arm64 (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• mosquitto/armel (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/armel (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• mosquitto/armhf (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/armhf (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• mosquitto/i386 (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/i386 (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• mosquitto/mips64el (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/mips64el (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• mosquitto/ppc64el (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/ppc64el (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• mosquitto/s390x (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/s390x (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• motif/amd64 (2.3.8-3 to 2.3.8-3)
  • Migration status for motif/amd64 (2.3.8-3 to 2.3.8-3): Will attempt migration (Any information below is purely informational)
• motif/arm64 (2.3.8-3 to 2.3.8-3)
  • Migration status for motif/arm64 (2.3.8-3 to 2.3.8-3): Will attempt migration (Any information below is purely informational)
• motif/armhf (2.3.8-3 to 2.3.8-3)
  • Migration status for motif/armhf (2.3.8-3 to 2.3.8-3): Will attempt migration (Any information below is purely informational)
• motif/i386 (2.3.8-3 to 2.3.8-3)
  • Migration status for motif/i386 (2.3.8-3 to 2.3.8-3): Will attempt migration (Any information below is purely informational)
• motif/mips64el (2.3.8-3 to 2.3.8-3)
  • Migration status for motif/mips64el (2.3.8-3 to 2.3.8-3): Will attempt migration (Any information below is purely informational)
• motif/ppc64el (2.3.8-3 to 2.3.8-3)
  • Migration status for motif/ppc64el (2.3.8-3 to 2.3.8-3): Will attempt migration (Any information below is purely informational)
• motif/s390x (2.3.8-3 to 2.3.8-3)
  • Migration status for motif/s390x (2.3.8-3 to 2.3.8-3): Will attempt migration (Any information below is purely informational)
• mousepad/amd64 (0.6.1-1 to 0.6.1-1)
  • Migration status for mousepad/amd64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• mousepad/arm64 (0.6.1-1 to 0.6.1-1)
  • Migration status for mousepad/arm64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• mousepad/armel (0.6.1-1 to 0.6.1-1)
  • Migration status for mousepad/armel (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• mousepad/armhf (0.6.1-1 to 0.6.1-1)
  • Migration status for mousepad/armhf (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• mousepad/i386 (0.6.1-1 to 0.6.1-1)
  • Migration status for mousepad/i386 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• mousepad/mips64el (0.6.1-1 to 0.6.1-1)
  • Migration status for mousepad/mips64el (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• mousepad/ppc64el (0.6.1-1 to 0.6.1-1)
  • Migration status for mousepad/ppc64el (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• mousepad/s390x (0.6.1-1 to 0.6.1-1)
  • Migration status for mousepad/s390x (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• movit/amd64 (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/amd64 (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• movit/arm64 (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/arm64 (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• movit/armel (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/armel (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• movit/armhf (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/armhf (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• movit/i386 (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/i386 (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• movit/mips64el (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/mips64el (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• movit/ppc64el (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/ppc64el (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• movit/s390x (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/s390x (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• mozc/amd64 (2.28.4715.102+dfsg-2.2 to 2.28.4715.102+dfsg-2.2)
  • Migration status for mozc/amd64 (2.28.4715.102+dfsg-2.2 to 2.28.4715.102+dfsg-2.2): Will attempt migration (Any information below is purely informational)
• mozc/arm64 (2.28.4715.102+dfsg-2.2 to 2.28.4715.102+dfsg-2.2)
  • Migration status for mozc/arm64 (2.28.4715.102+dfsg-2.2 to 2.28.4715.102+dfsg-2.2): Will attempt migration (Any information below is purely informational)
• mozc/armhf (2.28.4715.102+dfsg-2.2 to 2.28.4715.102+dfsg-2.2)
  • Migration status for mozc/armhf (2.28.4715.102+dfsg-2.2 to 2.28.4715.102+dfsg-2.2): Will attempt migration (Any information below is purely informational)
• mozc/i386 (2.28.4715.102+dfsg-2.2 to 2.28.4715.102+dfsg-2.2)
  • Migration status for mozc/i386 (2.28.4715.102+dfsg-2.2 to 2.28.4715.102+dfsg-2.2): Will attempt migration (Any information below is purely informational)
• mozjs102/amd64 (102.15.1-1 to 102.15.1-1)
  • Migration status for mozjs102/amd64 (102.15.1-1 to 102.15.1-1): Will attempt migration (Any information below is purely informational)
• mozjs102/arm64 (102.15.1-1 to 102.15.1-1)
  • Migration status for mozjs102/arm64 (102.15.1-1 to 102.15.1-1): Will attempt migration (Any information below is purely informational)
• mozjs102/armel (102.15.1-1 to 102.15.1-1)
  • Migration status for mozjs102/armel (102.15.1-1 to 102.15.1-1): Will attempt migration (Any information below is purely informational)
• mozjs102/armhf (102.15.1-1 to 102.15.1-1)
  • Migration status for mozjs102/armhf (102.15.1-1 to 102.15.1-1): Will attempt migration (Any information below is purely informational)
• mozjs102/i386 (102.15.1-1 to 102.15.1-1)
  • Migration status for mozjs102/i386 (102.15.1-1 to 102.15.1-1): Will attempt migration (Any information below is purely informational)
• mozjs102/mips64el (102.15.1-1 to 102.15.1-1)
  • Migration status for mozjs102/mips64el (102.15.1-1 to 102.15.1-1): Will attempt migration (Any information below is purely informational)
• mozjs102/ppc64el (102.15.1-1 to 102.15.1-1)
  • Migration status for mozjs102/ppc64el (102.15.1-1 to 102.15.1-1): Will attempt migration (Any information below is purely informational)
• mozjs102/s390x (102.15.1-1 to 102.15.1-1)
  • Migration status for mozjs102/s390x (102.15.1-1 to 102.15.1-1): Will attempt migration (Any information below is purely informational)
• mpeg2dec/amd64 (0.5.1-9 to 0.5.1-9)
  • Migration status for mpeg2dec/amd64 (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• mpeg2dec/arm64 (0.5.1-9 to 0.5.1-9)
  • Migration status for mpeg2dec/arm64 (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• mpeg2dec/armel (0.5.1-9 to 0.5.1-9)
  • Migration status for mpeg2dec/armel (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• mpeg2dec/armhf (0.5.1-9 to 0.5.1-9)
  • Migration status for mpeg2dec/armhf (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• mpeg2dec/i386 (0.5.1-9 to 0.5.1-9)
  • Migration status for mpeg2dec/i386 (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• mpeg2dec/mips64el (0.5.1-9 to 0.5.1-9)
  • Migration status for mpeg2dec/mips64el (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• mpeg2dec/ppc64el (0.5.1-9 to 0.5.1-9)
  • Migration status for mpeg2dec/ppc64el (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• mpeg2dec/s390x (0.5.1-9 to 0.5.1-9)
  • Migration status for mpeg2dec/s390x (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• mpfr4/amd64 (4.2.1-1 to 4.2.1-1)
  • Migration status for mpfr4/amd64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• mpfr4/arm64 (4.2.1-1 to 4.2.1-1)
  • Migration status for mpfr4/arm64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• mpfr4/armel (4.2.1-1 to 4.2.1-1)
  • Migration status for mpfr4/armel (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• mpfr4/armhf (4.2.1-1 to 4.2.1-1)
  • Migration status for mpfr4/armhf (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• mpfr4/i386 (4.2.1-1 to 4.2.1-1)
  • Migration status for mpfr4/i386 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• mpfr4/mips64el (4.2.1-1 to 4.2.1-1)
  • Migration status for mpfr4/mips64el (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• mpfr4/ppc64el (4.2.1-1 to 4.2.1-1)
  • Migration status for mpfr4/ppc64el (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• mpfr4/s390x (4.2.1-1 to 4.2.1-1)
  • Migration status for mpfr4/s390x (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• mrgingham/amd64 (1.24-1 to 1.24-1)
  • Migration status for mrgingham/amd64 (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• mrgingham/arm64 (1.24-1 to 1.24-1)
  • Migration status for mrgingham/arm64 (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• mrgingham/armel (1.24-1 to 1.24-1)
  • Migration status for mrgingham/armel (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• mrgingham/armhf (1.24-1 to 1.24-1)
  • Migration status for mrgingham/armhf (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• mrgingham/i386 (1.24-1 to 1.24-1)
  • Migration status for mrgingham/i386 (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• mrgingham/mips64el (1.24-1 to 1.24-1)
  • Migration status for mrgingham/mips64el (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• mrgingham/ppc64el (1.24-1 to 1.24-1)
  • Migration status for mrgingham/ppc64el (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• mrgingham/s390x (1.24-1 to 1.24-1)
  • Migration status for mrgingham/s390x (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• msgpack-c/amd64 (4.0.0-3 to 4.0.0-3)
  • Migration status for msgpack-c/amd64 (4.0.0-3 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
• msgpack-c/arm64 (4.0.0-3 to 4.0.0-3)
  • Migration status for msgpack-c/arm64 (4.0.0-3 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
• msgpack-c/armel (4.0.0-3 to 4.0.0-3)
  • Migration status for msgpack-c/armel (4.0.0-3 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
• msgpack-c/armhf (4.0.0-3 to 4.0.0-3)
  • Migration status for msgpack-c/armhf (4.0.0-3 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
• msgpack-c/i386 (4.0.0-3 to 4.0.0-3)
  • Migration status for msgpack-c/i386 (4.0.0-3 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
• msgpack-c/mips64el (4.0.0-3 to 4.0.0-3)
  • Migration status for msgpack-c/mips64el (4.0.0-3 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
• msgpack-c/ppc64el (4.0.0-3 to 4.0.0-3)
  • Migration status for msgpack-c/ppc64el (4.0.0-3 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
• msgpack-c/s390x (4.0.0-3 to 4.0.0-3)
  • Migration status for msgpack-c/s390x (4.0.0-3 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
• msgpack-cxx/amd64 (4.1.3-1 to 4.1.3-1)
  • Migration status for msgpack-cxx/amd64 (4.1.3-1 to 4.1.3-1): Will attempt migration (Any information below is purely informational)
• msgpack-cxx/arm64 (4.1.3-1 to 4.1.3-1)
  • Migration status for msgpack-cxx/arm64 (4.1.3-1 to 4.1.3-1): Will attempt migration (Any information below is purely informational)
• msgpack-cxx/armel (4.1.3-1 to 4.1.3-1)
  • Migration status for msgpack-cxx/armel (4.1.3-1 to 4.1.3-1): Will attempt migration (Any information below is purely informational)
• msgpack-cxx/armhf (4.1.3-1 to 4.1.3-1)
  • Migration status for msgpack-cxx/armhf (4.1.3-1 to 4.1.3-1): Will attempt migration (Any information below is purely informational)
• msgpack-cxx/i386 (4.1.3-1 to 4.1.3-1)
  • Migration status for msgpack-cxx/i386 (4.1.3-1 to 4.1.3-1): Will attempt migration (Any information below is purely informational)
• msgpack-cxx/ppc64el (4.1.3-1 to 4.1.3-1)
  • Migration status for msgpack-cxx/ppc64el (4.1.3-1 to 4.1.3-1): Will attempt migration (Any information below is purely informational)
• msgpack-cxx/s390x (4.1.3-1 to 4.1.3-1)
  • Migration status for msgpack-cxx/s390x (4.1.3-1 to 4.1.3-1): Will attempt migration (Any information below is purely informational)
• msitools/amd64 (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/amd64 (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• msitools/arm64 (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/arm64 (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• msitools/armel (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/armel (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• msitools/armhf (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/armhf (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• msitools/i386 (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/i386 (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• msitools/mips64el (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/mips64el (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• msitools/ppc64el (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/ppc64el (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• msitools/s390x (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/s390x (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• msopenh264/amd64 (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/amd64 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• msopenh264/arm64 (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/arm64 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• msopenh264/armel (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/armel (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• msopenh264/armhf (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/armhf (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• msopenh264/i386 (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/i386 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• msopenh264/mips64el (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/mips64el (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• msopenh264/ppc64el (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/ppc64el (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• msopenh264/s390x (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/s390x (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• mstch/amd64 (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/amd64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mstch/arm64 (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/arm64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mstch/armel (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/armel (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mstch/armhf (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/armhf (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mstch/i386 (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/i386 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mstch/mips64el (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/mips64el (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mstch/ppc64el (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/ppc64el (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mstch/s390x (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/s390x (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mtbl/amd64 (1.3.0-1 to 1.3.0-1)
  • Migration status for mtbl/amd64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• mtbl/arm64 (1.3.0-1 to 1.3.0-1)
  • Migration status for mtbl/arm64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• mtbl/armel (1.3.0-1 to 1.3.0-1)
  • Migration status for mtbl/armel (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• mtbl/armhf (1.3.0-1 to 1.3.0-1)
  • Migration status for mtbl/armhf (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• mtbl/i386 (1.3.0-1 to 1.3.0-1)
  • Migration status for mtbl/i386 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• mtbl/mips64el (1.3.0-1 to 1.3.0-1)
  • Migration status for mtbl/mips64el (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• mtbl/ppc64el (1.3.0-1 to 1.3.0-1)
  • Migration status for mtbl/ppc64el (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• mtbl/s390x (1.3.0-1 to 1.3.0-1)
  • Migration status for mtbl/s390x (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• mtd-utils/amd64 (1:2.1.6-1 to 1:2.1.6-1)
  • Migration status for mtd-utils/amd64 (1:2.1.6-1 to 1:2.1.6-1): Will attempt migration (Any information below is purely informational)
• mtd-utils/arm64 (1:2.1.6-1 to 1:2.1.6-1)
  • Migration status for mtd-utils/arm64 (1:2.1.6-1 to 1:2.1.6-1): Will attempt migration (Any information below is purely informational)
• mtd-utils/armel (1:2.1.6-1 to 1:2.1.6-1)
  • Migration status for mtd-utils/armel (1:2.1.6-1 to 1:2.1.6-1): Will attempt migration (Any information below is purely informational)
• mtd-utils/armhf (1:2.1.6-1 to 1:2.1.6-1)
  • Migration status for mtd-utils/armhf (1:2.1.6-1 to 1:2.1.6-1): Will attempt migration (Any information below is purely informational)
• mtd-utils/i386 (1:2.1.6-1 to 1:2.1.6-1)
  • Migration status for mtd-utils/i386 (1:2.1.6-1 to 1:2.1.6-1): Will attempt migration (Any information below is purely informational)
• mtd-utils/mips64el (1:2.1.6-1 to 1:2.1.6-1)
  • Migration status for mtd-utils/mips64el (1:2.1.6-1 to 1:2.1.6-1): Will attempt migration (Any information below is purely informational)
• mtd-utils/ppc64el (1:2.1.6-1 to 1:2.1.6-1)
  • Migration status for mtd-utils/ppc64el (1:2.1.6-1 to 1:2.1.6-1): Will attempt migration (Any information below is purely informational)
• mtd-utils/s390x (1:2.1.6-1 to 1:2.1.6-1)
  • Migration status for mtd-utils/s390x (1:2.1.6-1 to 1:2.1.6-1): Will attempt migration (Any information below is purely informational)
• mtdev/amd64 (1.1.6-1 to 1.1.6-1)
  • Migration status for mtdev/amd64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• mtdev/arm64 (1.1.6-1 to 1.1.6-1)
  • Migration status for mtdev/arm64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• mtdev/armel (1.1.6-1 to 1.1.6-1)
  • Migration status for mtdev/armel (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• mtdev/armhf (1.1.6-1 to 1.1.6-1)
  • Migration status for mtdev/armhf (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• mtdev/i386 (1.1.6-1 to 1.1.6-1)
  • Migration status for mtdev/i386 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• mtdev/mips64el (1.1.6-1 to 1.1.6-1)
  • Migration status for mtdev/mips64el (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• mtdev/ppc64el (1.1.6-1 to 1.1.6-1)
  • Migration status for mtdev/ppc64el (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• mtdev/s390x (1.1.6-1 to 1.1.6-1)
  • Migration status for mtdev/s390x (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• muffin/amd64 (5.8.1-2 to 5.8.1-2)
  • Migration status for muffin/amd64 (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• muffin/arm64 (5.8.1-2 to 5.8.1-2)
  • Migration status for muffin/arm64 (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• muffin/armel (5.8.1-2 to 5.8.1-2)
  • Migration status for muffin/armel (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• muffin/armhf (5.8.1-2 to 5.8.1-2)
  • Migration status for muffin/armhf (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• muffin/i386 (5.8.1-2 to 5.8.1-2)
  • Migration status for muffin/i386 (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• muffin/mips64el (5.8.1-2 to 5.8.1-2)
  • Migration status for muffin/mips64el (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• muffin/ppc64el (5.8.1-2 to 5.8.1-2)
  • Migration status for muffin/ppc64el (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• muffin/s390x (5.8.1-2 to 5.8.1-2)
  • Migration status for muffin/s390x (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• mujs/amd64 (1.3.3-3 to 1.3.3-3)
  • Migration status for mujs/amd64 (1.3.3-3 to 1.3.3-3): Will attempt migration (Any information below is purely informational)
• mujs/arm64 (1.3.3-3 to 1.3.3-3)
  • Migration status for mujs/arm64 (1.3.3-3 to 1.3.3-3): Will attempt migration (Any information below is purely informational)
• mujs/armel (1.3.3-3 to 1.3.3-3)
  • Migration status for mujs/armel (1.3.3-3 to 1.3.3-3): Will attempt migration (Any information below is purely informational)
• mujs/armhf (1.3.3-3 to 1.3.3-3)
  • Migration status for mujs/armhf (1.3.3-3 to 1.3.3-3): Will attempt migration (Any information below is purely informational)
• mujs/i386 (1.3.3-3 to 1.3.3-3)
  • Migration status for mujs/i386 (1.3.3-3 to 1.3.3-3): Will attempt migration (Any information below is purely informational)
• mujs/mips64el (1.3.3-3 to 1.3.3-3)
  • Migration status for mujs/mips64el (1.3.3-3 to 1.3.3-3): Will attempt migration (Any information below is purely informational)
• mujs/ppc64el (1.3.3-3 to 1.3.3-3)
  • Migration status for mujs/ppc64el (1.3.3-3 to 1.3.3-3): Will attempt migration (Any information below is purely informational)
• mujs/s390x (1.3.3-3 to 1.3.3-3)
  • Migration status for mujs/s390x (1.3.3-3 to 1.3.3-3): Will attempt migration (Any information below is purely informational)
• mumps/arm64 (5.6.2-2 to 5.6.2-2)
  • Migration status for mumps/arm64 (5.6.2-2 to 5.6.2-2): Will attempt migration (Any information below is purely informational)
• mumps/ppc64el (5.6.2-2 to 5.6.2-2)
  • Migration status for mumps/ppc64el (5.6.2-2 to 5.6.2-2): Will attempt migration (Any information below is purely informational)
• mumps/s390x (5.6.2-2 to 5.6.2-2)
  • Migration status for mumps/s390x (5.6.2-2 to 5.6.2-2): Will attempt migration (Any information below is purely informational)
• munge/amd64 (0.5.15-3 to 0.5.15-3)
  • Migration status for munge/amd64 (0.5.15-3 to 0.5.15-3): Will attempt migration (Any information below is purely informational)
• munge/arm64 (0.5.15-3 to 0.5.15-3)
  • Migration status for munge/arm64 (0.5.15-3 to 0.5.15-3): Will attempt migration (Any information below is purely informational)
• munge/armel (0.5.15-3 to 0.5.15-3)
  • Migration status for munge/armel (0.5.15-3 to 0.5.15-3): Will attempt migration (Any information below is purely informational)
• munge/armhf (0.5.15-3 to 0.5.15-3)
  • Migration status for munge/armhf (0.5.15-3 to 0.5.15-3): Will attempt migration (Any information below is purely informational)
• munge/i386 (0.5.15-3 to 0.5.15-3)
  • Migration status for munge/i386 (0.5.15-3 to 0.5.15-3): Will attempt migration (Any information below is purely informational)
• munge/mips64el (0.5.15-3 to 0.5.15-3)
  • Migration status for munge/mips64el (0.5.15-3 to 0.5.15-3): Will attempt migration (Any information below is purely informational)
• munge/ppc64el (0.5.15-3 to 0.5.15-3)
  • Migration status for munge/ppc64el (0.5.15-3 to 0.5.15-3): Will attempt migration (Any information below is purely informational)
• munge/s390x (0.5.15-3 to 0.5.15-3)
  • Migration status for munge/s390x (0.5.15-3 to 0.5.15-3): Will attempt migration (Any information below is purely informational)
• munipack/armhf (0.6.1-1 to 0.6.1-1)
  • Migration status for munipack/armhf (0.6.1-1 to 0.6.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: munipack/armhf plplot (not considered)
    • Invalidated by dependency
• muparser/amd64 (2.3.3-0.1 to 2.3.3-0.1)
  • Migration status for muparser/amd64 (2.3.3-0.1 to 2.3.3-0.1): Will attempt migration (Any information below is purely informational)
• muparser/arm64 (2.3.3-0.1 to 2.3.3-0.1)
  • Migration status for muparser/arm64 (2.3.3-0.1 to 2.3.3-0.1): Will attempt migration (Any information below is purely informational)
• muparser/armel (2.3.3-0.1 to 2.3.3-0.1)
  • Migration status for muparser/armel (2.3.3-0.1 to 2.3.3-0.1): Will attempt migration (Any information below is purely informational)
• muparser/armhf (2.3.3-0.1 to 2.3.3-0.1)
  • Migration status for muparser/armhf (2.3.3-0.1 to 2.3.3-0.1): Will attempt migration (Any information below is purely informational)
• muparser/i386 (2.3.3-0.1 to 2.3.3-0.1)
  • Migration status for muparser/i386 (2.3.3-0.1 to 2.3.3-0.1): Will attempt migration (Any information below is purely informational)
• muparser/mips64el (2.3.3-0.1 to 2.3.3-0.1)
  • Migration status for muparser/mips64el (2.3.3-0.1 to 2.3.3-0.1): Will attempt migration (Any information below is purely informational)
• muparser/ppc64el (2.3.3-0.1 to 2.3.3-0.1)
  • Migration status for muparser/ppc64el (2.3.3-0.1 to 2.3.3-0.1): Will attempt migration (Any information below is purely informational)
• muparser/s390x (2.3.3-0.1 to 2.3.3-0.1)
  • Migration status for muparser/s390x (2.3.3-0.1 to 2.3.3-0.1): Will attempt migration (Any information below is purely informational)
• muparserx/amd64 (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/amd64 (4.0.11-2 to 4.0.11-2): Will attempt migration (Any information below is purely informational)
• muparserx/arm64 (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/arm64 (4.0.11-2 to 4.0.11-2): Will attempt migration (Any information below is purely informational)
• muparserx/armel (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/armel (4.0.11-2 to 4.0.11-2): Will attempt migration (Any information below is purely informational)
• muparserx/armhf (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/armhf (4.0.11-2 to 4.0.11-2): Will attempt migration (Any information below is purely informational)
• muparserx/i386 (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/i386 (4.0.11-2 to 4.0.11-2): Will attempt migration (Any information below is purely informational)
• muparserx/mips64el (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/mips64el (4.0.11-2 to 4.0.11-2): Will attempt migration (Any information below is purely informational)
• muparserx/ppc64el (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/ppc64el (4.0.11-2 to 4.0.11-2): Will attempt migration (Any information below is purely informational)
• muparserx/s390x (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/s390x (4.0.11-2 to 4.0.11-2): Will attempt migration (Any information below is purely informational)
• musl/amd64 (1.2.4-2 to 1.2.4-2)
  • Migration status for musl/amd64 (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• musl/arm64 (1.2.4-2 to 1.2.4-2)
  • Migration status for musl/arm64 (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• musl/armel (1.2.4-2 to 1.2.4-2)
  • Migration status for musl/armel (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• musl/armhf (1.2.4-2 to 1.2.4-2)
  • Migration status for musl/armhf (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• musl/i386 (1.2.4-2 to 1.2.4-2)
  • Migration status for musl/i386 (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• musl/mips64el (1.2.4-2 to 1.2.4-2)
  • Migration status for musl/mips64el (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• musl/ppc64el (1.2.4-2 to 1.2.4-2)
  • Migration status for musl/ppc64el (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• musl/s390x (1.2.4-2 to 1.2.4-2)
  • Migration status for musl/s390x (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• mustache-d/amd64 (0.1.4-1 to 0.1.4-1)
  • Migration status for mustache-d/amd64 (0.1.4-1 to 0.1.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: mustache-d/amd64 ldc (not considered)
    • Invalidated by dependency
• mustache-d/arm64 (0.1.4-1 to 0.1.4-1)
  • Migration status for mustache-d/arm64 (0.1.4-1 to 0.1.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: mustache-d/arm64 ldc (not considered)
    • Invalidated by dependency
• mustache-d/i386 (0.1.4-1 to 0.1.4-1)
  • Migration status for mustache-d/i386 (0.1.4-1 to 0.1.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: mustache-d/i386 ldc (not considered)
    • Invalidated by dependency
• mxml/amd64 (3.3.1-1 to 3.3.1-1)
  • Migration status for mxml/amd64 (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• mxml/arm64 (3.3.1-1 to 3.3.1-1)
  • Migration status for mxml/arm64 (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• mxml/armel (3.3.1-1 to 3.3.1-1)
  • Migration status for mxml/armel (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• mxml/armhf (3.3.1-1 to 3.3.1-1)
  • Migration status for mxml/armhf (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• mxml/i386 (3.3.1-1 to 3.3.1-1)
  • Migration status for mxml/i386 (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• mxml/mips64el (3.3.1-1 to 3.3.1-1)
  • Migration status for mxml/mips64el (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• mxml/ppc64el (3.3.1-1 to 3.3.1-1)
  • Migration status for mxml/ppc64el (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• mxml/s390x (3.3.1-1 to 3.3.1-1)
  • Migration status for mxml/s390x (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• mysql-connector-c++/amd64 (1.1.12-4 to 1.1.12-4)
  • Migration status for mysql-connector-c++/amd64 (1.1.12-4 to 1.1.12-4): Will attempt migration (Any information below is purely informational)
• mysql-connector-c++/arm64 (1.1.12-4 to 1.1.12-4)
  • Migration status for mysql-connector-c++/arm64 (1.1.12-4 to 1.1.12-4): Will attempt migration (Any information below is purely informational)
• mysql-connector-c++/armel (1.1.12-4 to 1.1.12-4)
  • Migration status for mysql-connector-c++/armel (1.1.12-4 to 1.1.12-4): Will attempt migration (Any information below is purely informational)
• mysql-connector-c++/armhf (1.1.12-4 to 1.1.12-4)
  • Migration status for mysql-connector-c++/armhf (1.1.12-4 to 1.1.12-4): Will attempt migration (Any information below is purely informational)
• mysql-connector-c++/i386 (1.1.12-4 to 1.1.12-4)
  • Migration status for mysql-connector-c++/i386 (1.1.12-4 to 1.1.12-4): Will attempt migration (Any information below is purely informational)
• mysql-connector-c++/ppc64el (1.1.12-4 to 1.1.12-4)
  • Migration status for mysql-connector-c++/ppc64el (1.1.12-4 to 1.1.12-4): Will attempt migration (Any information below is purely informational)
• mysql-connector-c++/s390x (1.1.12-4 to 1.1.12-4)
  • Migration status for mysql-connector-c++/s390x (1.1.12-4 to 1.1.12-4): Will attempt migration (Any information below is purely informational)
• mysql-defaults/amd64 (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/amd64 (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysql-defaults/arm64 (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/arm64 (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysql-defaults/armel (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/armel (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysql-defaults/armhf (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/armhf (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysql-defaults/i386 (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/i386 (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysql-defaults/mips64el (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/mips64el (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysql-defaults/ppc64el (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/ppc64el (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysql-defaults/s390x (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/s390x (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysqltcl/amd64 (3.052-4 to 3.052-4)
  • Migration status for mysqltcl/amd64 (3.052-4 to 3.052-4): Will attempt migration (Any information below is purely informational)
• mysqltcl/arm64 (3.052-4 to 3.052-4)
  • Migration status for mysqltcl/arm64 (3.052-4 to 3.052-4): Will attempt migration (Any information below is purely informational)
• mysqltcl/armel (3.052-4 to 3.052-4)
  • Migration status for mysqltcl/armel (3.052-4 to 3.052-4): Will attempt migration (Any information below is purely informational)
• mysqltcl/armhf (3.052-4 to 3.052-4)
  • Migration status for mysqltcl/armhf (3.052-4 to 3.052-4): Will attempt migration (Any information below is purely informational)
• mysqltcl/i386 (3.052-4 to 3.052-4)
  • Migration status for mysqltcl/i386 (3.052-4 to 3.052-4): Will attempt migration (Any information below is purely informational)
• mysqltcl/mips64el (3.052-4 to 3.052-4)
  • Migration status for mysqltcl/mips64el (3.052-4 to 3.052-4): Will attempt migration (Any information below is purely informational)
• mysqltcl/ppc64el (3.052-4 to 3.052-4)
  • Migration status for mysqltcl/ppc64el (3.052-4 to 3.052-4): Will attempt migration (Any information below is purely informational)
• mysqltcl/s390x (3.052-4 to 3.052-4)
  • Migration status for mysqltcl/s390x (3.052-4 to 3.052-4): Will attempt migration (Any information below is purely informational)
• mythes/amd64 (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/amd64 (2:1.2.5-1 to 2:1.2.5-1): Will attempt migration (Any information below is purely informational)
• mythes/arm64 (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/arm64 (2:1.2.5-1 to 2:1.2.5-1): Will attempt migration (Any information below is purely informational)
• mythes/armel (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/armel (2:1.2.5-1 to 2:1.2.5-1): Will attempt migration (Any information below is purely informational)
• mythes/armhf (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/armhf (2:1.2.5-1 to 2:1.2.5-1): Will attempt migration (Any information below is purely informational)
• mythes/i386 (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/i386 (2:1.2.5-1 to 2:1.2.5-1): Will attempt migration (Any information below is purely informational)
• mythes/mips64el (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/mips64el (2:1.2.5-1 to 2:1.2.5-1): Will attempt migration (Any information below is purely informational)
• mythes/ppc64el (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/ppc64el (2:1.2.5-1 to 2:1.2.5-1): Will attempt migration (Any information below is purely informational)
• mythes/s390x (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/s390x (2:1.2.5-1 to 2:1.2.5-1): Will attempt migration (Any information below is purely informational)
• nanopb/amd64 (0.4.8-1 to 0.4.8-1)
  • Migration status for nanopb/amd64 (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• nanopb/arm64 (0.4.8-1 to 0.4.8-1)
  • Migration status for nanopb/arm64 (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• nanopb/armel (0.4.8-1 to 0.4.8-1)
  • Migration status for nanopb/armel (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• nanopb/armhf (0.4.8-1 to 0.4.8-1)
  • Migration status for nanopb/armhf (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• nanopb/i386 (0.4.8-1 to 0.4.8-1)
  • Migration status for nanopb/i386 (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• nanopb/ppc64el (0.4.8-1 to 0.4.8-1)
  • Migration status for nanopb/ppc64el (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• nanopb/s390x (0.4.8-1 to 0.4.8-1)
  • Migration status for nanopb/s390x (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• nas/amd64 (1.9.4-7 to 1.9.4-7)
  • Migration status for nas/amd64 (1.9.4-7 to 1.9.4-7): Will attempt migration (Any information below is purely informational)
• nas/arm64 (1.9.4-7 to 1.9.4-7)
  • Migration status for nas/arm64 (1.9.4-7 to 1.9.4-7): Will attempt migration (Any information below is purely informational)
• nas/armel (1.9.4-7 to 1.9.4-7)
  • Migration status for nas/armel (1.9.4-7 to 1.9.4-7): Will attempt migration (Any information below is purely informational)
• nas/armhf (1.9.4-7 to 1.9.4-7)
  • Migration status for nas/armhf (1.9.4-7 to 1.9.4-7): Will attempt migration (Any information below is purely informational)
• nas/i386 (1.9.4-7 to 1.9.4-7)
  • Migration status for nas/i386 (1.9.4-7 to 1.9.4-7): Will attempt migration (Any information below is purely informational)
• nas/mips64el (1.9.4-7 to 1.9.4-7)
  • Migration status for nas/mips64el (1.9.4-7 to 1.9.4-7): Will attempt migration (Any information below is purely informational)
• nas/ppc64el (1.9.4-7 to 1.9.4-7)
  • Migration status for nas/ppc64el (1.9.4-7 to 1.9.4-7): Will attempt migration (Any information below is purely informational)
• nas/s390x (1.9.4-7 to 1.9.4-7)
  • Migration status for nas/s390x (1.9.4-7 to 1.9.4-7): Will attempt migration (Any information below is purely informational)
• naspro-core/amd64 (0.5.1-3.1 to 0.5.1-3.1)
  • Migration status for naspro-core/amd64 (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
• naspro-core/arm64 (0.5.1-3.1 to 0.5.1-3.1)
  • Migration status for naspro-core/arm64 (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
• naspro-core/armel (0.5.1-3.1 to 0.5.1-3.1)
  • Migration status for naspro-core/armel (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
• naspro-core/armhf (0.5.1-3.1 to 0.5.1-3.1)
  • Migration status for naspro-core/armhf (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
• naspro-core/i386 (0.5.1-3.1 to 0.5.1-3.1)
  • Migration status for naspro-core/i386 (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
• naspro-core/mips64el (0.5.1-3.1 to 0.5.1-3.1)
  • Migration status for naspro-core/mips64el (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
• naspro-core/ppc64el (0.5.1-3.1 to 0.5.1-3.1)
  • Migration status for naspro-core/ppc64el (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
• naspro-core/s390x (0.5.1-3.1 to 0.5.1-3.1)
  • Migration status for naspro-core/s390x (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
• nats.c/amd64 (3.7.0-1 to 3.7.0-1)
  • Migration status for nats.c/amd64 (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• nats.c/arm64 (3.7.0-1 to 3.7.0-1)
  • Migration status for nats.c/arm64 (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• nats.c/armel (3.7.0-1 to 3.7.0-1)
  • Migration status for nats.c/armel (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• nats.c/armhf (3.7.0-1 to 3.7.0-1)
  • Migration status for nats.c/armhf (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• nats.c/i386 (3.7.0-1 to 3.7.0-1)
  • Migration status for nats.c/i386 (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• nats.c/mips64el (3.7.0-1 to 3.7.0-1)
  • Migration status for nats.c/mips64el (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• nats.c/ppc64el (3.7.0-1 to 3.7.0-1)
  • Migration status for nats.c/ppc64el (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• nats.c/s390x (3.7.0-1 to 3.7.0-1)
  • Migration status for nats.c/s390x (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• nautilus-wipe/amd64 (0.4.alpha2-0.1 to 0.4.alpha2-0.1)
  • Migration status for nautilus-wipe/amd64 (0.4.alpha2-0.1 to 0.4.alpha2-0.1): Will attempt migration (Any information below is purely informational)
• nautilus-wipe/arm64 (0.4.alpha2-0.1 to 0.4.alpha2-0.1)
  • Migration status for nautilus-wipe/arm64 (0.4.alpha2-0.1 to 0.4.alpha2-0.1): Will attempt migration (Any information below is purely informational)
• nautilus-wipe/armel (0.4.alpha2-0.1 to 0.4.alpha2-0.1)
  • Migration status for nautilus-wipe/armel (0.4.alpha2-0.1 to 0.4.alpha2-0.1): Will attempt migration (Any information below is purely informational)
• nautilus-wipe/armhf (0.4.alpha2-0.1 to 0.4.alpha2-0.1)
  • Migration status for nautilus-wipe/armhf (0.4.alpha2-0.1 to 0.4.alpha2-0.1): Will attempt migration (Any information below is purely informational)
• nautilus-wipe/i386 (0.4.alpha2-0.1 to 0.4.alpha2-0.1)
  • Migration status for nautilus-wipe/i386 (0.4.alpha2-0.1 to 0.4.alpha2-0.1): Will attempt migration (Any information below is purely informational)
• nautilus-wipe/mips64el (0.4.alpha2-0.1 to 0.4.alpha2-0.1)
  • Migration status for nautilus-wipe/mips64el (0.4.alpha2-0.1 to 0.4.alpha2-0.1): Will attempt migration (Any information below is purely informational)
• nautilus-wipe/ppc64el (0.4.alpha2-0.1 to 0.4.alpha2-0.1)
  • Migration status for nautilus-wipe/ppc64el (0.4.alpha2-0.1 to 0.4.alpha2-0.1): Will attempt migration (Any information below is purely informational)
• nautilus-wipe/s390x (0.4.alpha2-0.1 to 0.4.alpha2-0.1)
  • Migration status for nautilus-wipe/s390x (0.4.alpha2-0.1 to 0.4.alpha2-0.1): Will attempt migration (Any information below is purely informational)
• ncap/amd64 (1.9.2-8 to 1.9.2-8)
  • Migration status for ncap/amd64 (1.9.2-8 to 1.9.2-8): Will attempt migration (Any information below is purely informational)
• ncap/arm64 (1.9.2-8 to 1.9.2-8)
  • Migration status for ncap/arm64 (1.9.2-8 to 1.9.2-8): Will attempt migration (Any information below is purely informational)
• ncap/armel (1.9.2-8 to 1.9.2-8)
  • Migration status for ncap/armel (1.9.2-8 to 1.9.2-8): Will attempt migration (Any information below is purely informational)
• ncap/armhf (1.9.2-8 to 1.9.2-8)
  • Migration status for ncap/armhf (1.9.2-8 to 1.9.2-8): Will attempt migration (Any information below is purely informational)
• ncap/i386 (1.9.2-8 to 1.9.2-8)
  • Migration status for ncap/i386 (1.9.2-8 to 1.9.2-8): Will attempt migration (Any information below is purely informational)
• ncap/mips64el (1.9.2-8 to 1.9.2-8)
  • Migration status for ncap/mips64el (1.9.2-8 to 1.9.2-8): Will attempt migration (Any information below is purely informational)
• ncap/ppc64el (1.9.2-8 to 1.9.2-8)
  • Migration status for ncap/ppc64el (1.9.2-8 to 1.9.2-8): Will attempt migration (Any information below is purely informational)
• ncap/s390x (1.9.2-8 to 1.9.2-8)
  • Migration status for ncap/s390x (1.9.2-8 to 1.9.2-8): Will attempt migration (Any information below is purely informational)
• ncbi-tools6/amd64 (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10)
  • Migration status for ncbi-tools6/amd64 (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10): Will attempt migration (Any information below is purely informational)
• ncbi-tools6/arm64 (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10)
  • Migration status for ncbi-tools6/arm64 (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10): Will attempt migration (Any information below is purely informational)
• ncbi-tools6/armel (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10)
  • Migration status for ncbi-tools6/armel (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10): Will attempt migration (Any information below is purely informational)
• ncbi-tools6/armhf (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10)
  • Migration status for ncbi-tools6/armhf (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10): Will attempt migration (Any information below is purely informational)
• ncbi-tools6/i386 (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10)
  • Migration status for ncbi-tools6/i386 (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10): Will attempt migration (Any information below is purely informational)
• ncbi-tools6/ppc64el (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10)
  • Migration status for ncbi-tools6/ppc64el (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10): Will attempt migration (Any information below is purely informational)
• ncbi-tools6/s390x (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10)
  • Migration status for ncbi-tools6/s390x (6.1.20170106+dfsg1-10 to 6.1.20170106+dfsg1-10): Will attempt migration (Any information below is purely informational)
• ncrystal/amd64 (3.4.1+ds1-1 to 3.4.1+ds1-1)
  • Migration status for ncrystal/amd64 (3.4.1+ds1-1 to 3.4.1+ds1-1): Will attempt migration (Any information below is purely informational)
• ncrystal/arm64 (3.4.1+ds1-1 to 3.4.1+ds1-1)
  • Migration status for ncrystal/arm64 (3.4.1+ds1-1 to 3.4.1+ds1-1): Will attempt migration (Any information below is purely informational)
• ncrystal/armel (3.4.1+ds1-1 to 3.4.1+ds1-1)
  • Migration status for ncrystal/armel (3.4.1+ds1-1 to 3.4.1+ds1-1): Will attempt migration (Any information below is purely informational)
• ncrystal/armhf (3.4.1+ds1-1 to 3.4.1+ds1-1)
  • Migration status for ncrystal/armhf (3.4.1+ds1-1 to 3.4.1+ds1-1): Will attempt migration (Any information below is purely informational)
• ncrystal/i386 (3.4.1+ds1-1 to 3.4.1+ds1-1)
  • Migration status for ncrystal/i386 (3.4.1+ds1-1 to 3.4.1+ds1-1): Will attempt migration (Any information below is purely informational)
• ncrystal/mips64el (3.4.1+ds1-1 to 3.4.1+ds1-1)
  • Migration status for ncrystal/mips64el (3.4.1+ds1-1 to 3.4.1+ds1-1): Will attempt migration (Any information below is purely informational)
• ncrystal/ppc64el (3.4.1+ds1-1 to 3.4.1+ds1-1)
  • Migration status for ncrystal/ppc64el (3.4.1+ds1-1 to 3.4.1+ds1-1): Will attempt migration (Any information below is purely informational)
• ncrystal/s390x (3.4.1+ds1-1 to 3.4.1+ds1-1)
  • Migration status for ncrystal/s390x (3.4.1+ds1-1 to 3.4.1+ds1-1): Will attempt migration (Any information below is purely informational)
• ndctl/amd64 (77-2 to 77-2)
  • Migration status for ndctl/amd64 (77-2 to 77-2): Will attempt migration (Any information below is purely informational)
• ndctl/arm64 (77-2 to 77-2)
  • Migration status for ndctl/arm64 (77-2 to 77-2): Will attempt migration (Any information below is purely informational)
• ndctl/armel (77-2 to 77-2)
  • Migration status for ndctl/armel (77-2 to 77-2): Will attempt migration (Any information below is purely informational)
• ndctl/armhf (77-2 to 77-2)
  • Migration status for ndctl/armhf (77-2 to 77-2): Will attempt migration (Any information below is purely informational)
• ndctl/i386 (77-2 to 77-2)
  • Migration status for ndctl/i386 (77-2 to 77-2): Will attempt migration (Any information below is purely informational)
• ndctl/mips64el (77-2 to 77-2)
  • Migration status for ndctl/mips64el (77-2 to 77-2): Will attempt migration (Any information below is purely informational)
• ndctl/ppc64el (77-2 to 77-2)
  • Migration status for ndctl/ppc64el (77-2 to 77-2): Will attempt migration (Any information below is purely informational)
• ndctl/s390x (77-2 to 77-2)
  • Migration status for ndctl/s390x (77-2 to 77-2): Will attempt migration (Any information below is purely informational)
• ndpi/amd64 (4.2-2 to 4.2-2)
  • Migration status for ndpi/amd64 (4.2-2 to 4.2-2): Will attempt migration (Any information below is purely informational)
• ndpi/arm64 (4.2-2 to 4.2-2)
  • Migration status for ndpi/arm64 (4.2-2 to 4.2-2): Will attempt migration (Any information below is purely informational)
• ndpi/armel (4.2-2 to 4.2-2)
  • Migration status for ndpi/armel (4.2-2 to 4.2-2): Will attempt migration (Any information below is purely informational)
• ndpi/armhf (4.2-2 to 4.2-2)
  • Migration status for ndpi/armhf (4.2-2 to 4.2-2): Will attempt migration (Any information below is purely informational)
• ndpi/i386 (4.2-2 to 4.2-2)
  • Migration status for ndpi/i386 (4.2-2 to 4.2-2): Will attempt migration (Any information below is purely informational)
• ndpi/mips64el (4.2-2 to 4.2-2)
  • Migration status for ndpi/mips64el (4.2-2 to 4.2-2): Will attempt migration (Any information below is purely informational)
• ndpi/ppc64el (4.2-2 to 4.2-2)
  • Migration status for ndpi/ppc64el (4.2-2 to 4.2-2): Will attempt migration (Any information below is purely informational)
• neartree/amd64 (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2)
  • Migration status for neartree/amd64 (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2): Will attempt migration (Any information below is purely informational)
• neartree/arm64 (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2)
  • Migration status for neartree/arm64 (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2): Will attempt migration (Any information below is purely informational)
• neartree/armel (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2)
  • Migration status for neartree/armel (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2): Will attempt migration (Any information below is purely informational)
• neartree/armhf (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2)
  • Migration status for neartree/armhf (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2): Will attempt migration (Any information below is purely informational)
• neartree/i386 (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2)
  • Migration status for neartree/i386 (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2): Will attempt migration (Any information below is purely informational)
• neartree/mips64el (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2)
  • Migration status for neartree/mips64el (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2): Will attempt migration (Any information below is purely informational)
• neartree/ppc64el (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2)
  • Migration status for neartree/ppc64el (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2): Will attempt migration (Any information below is purely informational)
• neartree/s390x (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2)
  • Migration status for neartree/s390x (5.1.1+dfsg1-2 to 5.1.1+dfsg1-2): Will attempt migration (Any information below is purely informational)
• neko/amd64 (2.3.0-2 to 2.3.0-2)
  • Migration status for neko/amd64 (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• neko/arm64 (2.3.0-2 to 2.3.0-2)
  • Migration status for neko/arm64 (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• neko/armel (2.3.0-2 to 2.3.0-2)
  • Migration status for neko/armel (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• neko/armhf (2.3.0-2 to 2.3.0-2)
  • Migration status for neko/armhf (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• neko/i386 (2.3.0-2 to 2.3.0-2)
  • Migration status for neko/i386 (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• neko/mips64el (2.3.0-2 to 2.3.0-2)
  • Migration status for neko/mips64el (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• neko/ppc64el (2.3.0-2 to 2.3.0-2)
  • Migration status for neko/ppc64el (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• neko/s390x (2.3.0-2 to 2.3.0-2)
  • Migration status for neko/s390x (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• nemo/amd64 (5.8.5-2 to 5.8.5-2)
  • Migration status for nemo/amd64 (5.8.5-2 to 5.8.5-2): Will attempt migration (Any information below is purely informational)
• nemo/arm64 (5.8.5-2 to 5.8.5-2)
  • Migration status for nemo/arm64 (5.8.5-2 to 5.8.5-2): Will attempt migration (Any information below is purely informational)
• nemo/armel (5.8.5-2 to 5.8.5-2)
  • Migration status for nemo/armel (5.8.5-2 to 5.8.5-2): Will attempt migration (Any information below is purely informational)
• nemo/armhf (5.8.5-2 to 5.8.5-2)
  • Migration status for nemo/armhf (5.8.5-2 to 5.8.5-2): Will attempt migration (Any information below is purely informational)
• nemo/i386 (5.8.5-2 to 5.8.5-2)
  • Migration status for nemo/i386 (5.8.5-2 to 5.8.5-2): Will attempt migration (Any information below is purely informational)
• nemo/mips64el (5.8.5-2 to 5.8.5-2)
  • Migration status for nemo/mips64el (5.8.5-2 to 5.8.5-2): Will attempt migration (Any information below is purely informational)
• nemo/ppc64el (5.8.5-2 to 5.8.5-2)
  • Migration status for nemo/ppc64el (5.8.5-2 to 5.8.5-2): Will attempt migration (Any information below is purely informational)
• nemo/s390x (5.8.5-2 to 5.8.5-2)
  • Migration status for nemo/s390x (5.8.5-2 to 5.8.5-2): Will attempt migration (Any information below is purely informational)
• netcdf-fortran/amd64 (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3)
  • Migration status for netcdf-fortran/amd64 (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3): Will attempt migration (Any information below is purely informational)
• netcdf-fortran/arm64 (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3)
  • Migration status for netcdf-fortran/arm64 (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3): Will attempt migration (Any information below is purely informational)
• netcdf-fortran/armel (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3)
  • Migration status for netcdf-fortran/armel (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3): Will attempt migration (Any information below is purely informational)
• netcdf-fortran/armhf (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3)
  • Migration status for netcdf-fortran/armhf (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3): Will attempt migration (Any information below is purely informational)
• netcdf-fortran/i386 (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3)
  • Migration status for netcdf-fortran/i386 (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3): Will attempt migration (Any information below is purely informational)
• netcdf-fortran/mips64el (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3)
  • Migration status for netcdf-fortran/mips64el (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3): Will attempt migration (Any information below is purely informational)
• netcdf-fortran/ppc64el (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3)
  • Migration status for netcdf-fortran/ppc64el (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3): Will attempt migration (Any information below is purely informational)
• netcdf-parallel/amd64 (1:4.9.0-1 to 1:4.9.0-1)
  • Migration status for netcdf-parallel/amd64 (1:4.9.0-1 to 1:4.9.0-1): Will attempt migration (Any information below is purely informational)
• netcdf-parallel/arm64 (1:4.9.0-1 to 1:4.9.0-1)
  • Migration status for netcdf-parallel/arm64 (1:4.9.0-1 to 1:4.9.0-1): Will attempt migration (Any information below is purely informational)
• netcdf-parallel/armel (1:4.9.0-1 to 1:4.9.0-1)
  • Migration status for netcdf-parallel/armel (1:4.9.0-1 to 1:4.9.0-1): Will attempt migration (Any information below is purely informational)
• netcdf-parallel/armhf (1:4.9.0-1 to 1:4.9.0-1)
  • Migration status for netcdf-parallel/armhf (1:4.9.0-1 to 1:4.9.0-1): Will attempt migration (Any information below is purely informational)
• netcdf-parallel/i386 (1:4.9.0-1 to 1:4.9.0-1)
  • Migration status for netcdf-parallel/i386 (1:4.9.0-1 to 1:4.9.0-1): Will attempt migration (Any information below is purely informational)
• netcdf-parallel/ppc64el (1:4.9.0-1 to 1:4.9.0-1)
  • Migration status for netcdf-parallel/ppc64el (1:4.9.0-1 to 1:4.9.0-1): Will attempt migration (Any information below is purely informational)
• netcdf/amd64 (1:4.9.2-3 to 1:4.9.2-3)
  • Migration status for netcdf/amd64 (1:4.9.2-3 to 1:4.9.2-3): Will attempt migration (Any information below is purely informational)
• netcdf/arm64 (1:4.9.2-3 to 1:4.9.2-3)
  • Migration status for netcdf/arm64 (1:4.9.2-3 to 1:4.9.2-3): Will attempt migration (Any information below is purely informational)
• netcdf/armhf (1:4.9.2-3 to 1:4.9.2-3)
  • Migration status for netcdf/armhf (1:4.9.2-3 to 1:4.9.2-3): Will attempt migration (Any information below is purely informational)
• netcdf/i386 (1:4.9.2-3 to 1:4.9.2-3)
  • Migration status for netcdf/i386 (1:4.9.2-3 to 1:4.9.2-3): Will attempt migration (Any information below is purely informational)
• netcdf/mips64el (1:4.9.2-3 to 1:4.9.2-3)
  • Migration status for netcdf/mips64el (1:4.9.2-3 to 1:4.9.2-3): Will attempt migration (Any information below is purely informational)
• netcdf/ppc64el (1:4.9.2-3 to 1:4.9.2-3)
  • Migration status for netcdf/ppc64el (1:4.9.2-3 to 1:4.9.2-3): Will attempt migration (Any information below is purely informational)
• nettle/amd64 (3.9.1-2 to 3.9.1-2)
  • Migration status for nettle/amd64 (3.9.1-2 to 3.9.1-2): Will attempt migration (Any information below is purely informational)
• nettle/arm64 (3.9.1-2 to 3.9.1-2)
  • Migration status for nettle/arm64 (3.9.1-2 to 3.9.1-2): Will attempt migration (Any information below is purely informational)
• nettle/armel (3.9.1-2 to 3.9.1-2)
  • Migration status for nettle/armel (3.9.1-2 to 3.9.1-2): Will attempt migration (Any information below is purely informational)
• nettle/armhf (3.9.1-2 to 3.9.1-2)
  • Migration status for nettle/armhf (3.9.1-2 to 3.9.1-2): Will attempt migration (Any information below is purely informational)
• nettle/i386 (3.9.1-2 to 3.9.1-2)
  • Migration status for nettle/i386 (3.9.1-2 to 3.9.1-2): Will attempt migration (Any information below is purely informational)
• nettle/mips64el (3.9.1-2 to 3.9.1-2)
  • Migration status for nettle/mips64el (3.9.1-2 to 3.9.1-2): Will attempt migration (Any information below is purely informational)
• nettle/ppc64el (3.9.1-2 to 3.9.1-2)
  • Migration status for nettle/ppc64el (3.9.1-2 to 3.9.1-2): Will attempt migration (Any information below is purely informational)
• nghttp3/amd64 (0.8.0-2 to 0.8.0-2)
  • Migration status for nghttp3/amd64 (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• nghttp3/arm64 (0.8.0-2 to 0.8.0-2)
  • Migration status for nghttp3/arm64 (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• nghttp3/armel (0.8.0-2 to 0.8.0-2)
  • Migration status for nghttp3/armel (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• nghttp3/armhf (0.8.0-2 to 0.8.0-2)
  • Migration status for nghttp3/armhf (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• nghttp3/i386 (0.8.0-2 to 0.8.0-2)
  • Migration status for nghttp3/i386 (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• nghttp3/mips64el (0.8.0-2 to 0.8.0-2)
  • Migration status for nghttp3/mips64el (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• nghttp3/ppc64el (0.8.0-2 to 0.8.0-2)
  • Migration status for nghttp3/ppc64el (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• nifticlib/amd64 (3.0.1-9 to 3.0.1-9)
  • Migration status for nifticlib/amd64 (3.0.1-9 to 3.0.1-9): Will attempt migration (Any information below is purely informational)
• nifticlib/arm64 (3.0.1-9 to 3.0.1-9)
  • Migration status for nifticlib/arm64 (3.0.1-9 to 3.0.1-9): Will attempt migration (Any information below is purely informational)
• nifticlib/armel (3.0.1-9 to 3.0.1-9)
  • Migration status for nifticlib/armel (3.0.1-9 to 3.0.1-9): Will attempt migration (Any information below is purely informational)
• nifticlib/armhf (3.0.1-9 to 3.0.1-9)
  • Migration status for nifticlib/armhf (3.0.1-9 to 3.0.1-9): Will attempt migration (Any information below is purely informational)
• nifticlib/i386 (3.0.1-9 to 3.0.1-9)
  • Migration status for nifticlib/i386 (3.0.1-9 to 3.0.1-9): Will attempt migration (Any information below is purely informational)
• nifticlib/mips64el (3.0.1-9 to 3.0.1-9)
  • Migration status for nifticlib/mips64el (3.0.1-9 to 3.0.1-9): Will attempt migration (Any information below is purely informational)
• nifticlib/ppc64el (3.0.1-9 to 3.0.1-9)
  • Migration status for nifticlib/ppc64el (3.0.1-9 to 3.0.1-9): Will attempt migration (Any information below is purely informational)
• node-leveldown/amd64 (5.6.0+dfsg-4 to 5.6.0+dfsg-4)
  • Migration status for node-leveldown/amd64 (5.6.0+dfsg-4 to 5.6.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• node-leveldown/arm64 (5.6.0+dfsg-4 to 5.6.0+dfsg-4)
  • Migration status for node-leveldown/arm64 (5.6.0+dfsg-4 to 5.6.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• node-leveldown/armel (5.6.0+dfsg-4 to 5.6.0+dfsg-4)
  • Migration status for node-leveldown/armel (5.6.0+dfsg-4 to 5.6.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• node-leveldown/armhf (5.6.0+dfsg-4 to 5.6.0+dfsg-4)
  • Migration status for node-leveldown/armhf (5.6.0+dfsg-4 to 5.6.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• node-leveldown/i386 (5.6.0+dfsg-4 to 5.6.0+dfsg-4)
  • Migration status for node-leveldown/i386 (5.6.0+dfsg-4 to 5.6.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• node-leveldown/ppc64el (5.6.0+dfsg-4 to 5.6.0+dfsg-4)
  • Migration status for node-leveldown/ppc64el (5.6.0+dfsg-4 to 5.6.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• node-sqlite3/amd64 (5.1.5+ds1-1 to 5.1.5+ds1-1)
  • Migration status for node-sqlite3/amd64 (5.1.5+ds1-1 to 5.1.5+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: node-sqlite3/amd64 nodejs (not considered)
    • Invalidated by dependency
• node-sqlite3/arm64 (5.1.5+ds1-1 to 5.1.5+ds1-1)
  • Migration status for node-sqlite3/arm64 (5.1.5+ds1-1 to 5.1.5+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: node-sqlite3/arm64 nodejs (not considered)
    • Invalidated by dependency
• node-sqlite3/armel (5.1.5+ds1-1 to 5.1.5+ds1-1)
  • Migration status for node-sqlite3/armel (5.1.5+ds1-1 to 5.1.5+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: node-sqlite3/armel nodejs (not considered)
    • Invalidated by dependency
• node-sqlite3/armhf (5.1.5+ds1-1 to 5.1.5+ds1-1)
  • Migration status for node-sqlite3/armhf (5.1.5+ds1-1 to 5.1.5+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: node-sqlite3/armhf nodejs (not considered)
    • Invalidated by dependency
• node-sqlite3/i386 (5.1.5+ds1-1 to 5.1.5+ds1-1)
  • Migration status for node-sqlite3/i386 (5.1.5+ds1-1 to 5.1.5+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: node-sqlite3/i386 nodejs (not considered)
    • Invalidated by dependency
• node-sqlite3/mips64el (5.1.5+ds1-1 to 5.1.5+ds1-1)
  • Migration status for node-sqlite3/mips64el (5.1.5+ds1-1 to 5.1.5+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: node-sqlite3/mips64el nodejs (not considered)
    • Invalidated by dependency
• node-sqlite3/ppc64el (5.1.5+ds1-1 to 5.1.5+ds1-1)
  • Migration status for node-sqlite3/ppc64el (5.1.5+ds1-1 to 5.1.5+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: node-sqlite3/ppc64el nodejs (not considered)
    • Invalidated by dependency
• nproc/amd64 (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/amd64 (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: nproc/amd64 lwt/amd64
• nproc/arm64 (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/arm64 (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: nproc/arm64 lwt/arm64
• nproc/armel (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/armel (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: nproc/armel lwt/armel
• nproc/armhf (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/armhf (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: nproc/armhf lwt/armhf
• nproc/i386 (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/i386 (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: nproc/i386 lwt/i386
• nproc/mips64el (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/mips64el (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: nproc/mips64el lwt/mips64el
• nproc/ppc64el (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/ppc64el (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: nproc/ppc64el lwt/ppc64el
• nproc/s390x (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/s390x (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: nproc/s390x lwt/s390x
• npth/amd64 (1.6-3 to 1.6-3)
  • Migration status for npth/amd64 (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• npth/arm64 (1.6-3 to 1.6-3)
  • Migration status for npth/arm64 (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• npth/armel (1.6-3 to 1.6-3)
  • Migration status for npth/armel (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• npth/armhf (1.6-3 to 1.6-3)
  • Migration status for npth/armhf (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• npth/i386 (1.6-3 to 1.6-3)
  • Migration status for npth/i386 (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• npth/mips64el (1.6-3 to 1.6-3)
  • Migration status for npth/mips64el (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• npth/ppc64el (1.6-3 to 1.6-3)
  • Migration status for npth/ppc64el (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• ns2/amd64 (2.35+dfsg-5 to 2.35+dfsg-5)
  • Migration status for ns2/amd64 (2.35+dfsg-5 to 2.35+dfsg-5): Will attempt migration (Any information below is purely informational)
• ns2/arm64 (2.35+dfsg-5 to 2.35+dfsg-5)
  • Migration status for ns2/arm64 (2.35+dfsg-5 to 2.35+dfsg-5): Will attempt migration (Any information below is purely informational)
• ns2/armel (2.35+dfsg-5 to 2.35+dfsg-5)
  • Migration status for ns2/armel (2.35+dfsg-5 to 2.35+dfsg-5): Will attempt migration (Any information below is purely informational)
• ns2/armhf (2.35+dfsg-5 to 2.35+dfsg-5)
  • Migration status for ns2/armhf (2.35+dfsg-5 to 2.35+dfsg-5): Will attempt migration (Any information below is purely informational)
• ns2/i386 (2.35+dfsg-5 to 2.35+dfsg-5)
  • Migration status for ns2/i386 (2.35+dfsg-5 to 2.35+dfsg-5): Will attempt migration (Any information below is purely informational)
• ns2/ppc64el (2.35+dfsg-5 to 2.35+dfsg-5)
  • Migration status for ns2/ppc64el (2.35+dfsg-5 to 2.35+dfsg-5): Will attempt migration (Any information below is purely informational)
• nspr/amd64 (2:4.35-1.1 to 2:4.35-1.1)
  • Migration status for nspr/amd64 (2:4.35-1.1 to 2:4.35-1.1): Will attempt migration (Any information below is purely informational)
• nspr/arm64 (2:4.35-1.1 to 2:4.35-1.1)
  • Migration status for nspr/arm64 (2:4.35-1.1 to 2:4.35-1.1): Will attempt migration (Any information below is purely informational)
• nspr/armel (2:4.35-1.1 to 2:4.35-1.1)
  • Migration status for nspr/armel (2:4.35-1.1 to 2:4.35-1.1): Will attempt migration (Any information below is purely informational)
• nspr/armhf (2:4.35-1.1 to 2:4.35-1.1)
  • Migration status for nspr/armhf (2:4.35-1.1 to 2:4.35-1.1): Will attempt migration (Any information below is purely informational)
• nspr/i386 (2:4.35-1.1 to 2:4.35-1.1)
  • Migration status for nspr/i386 (2:4.35-1.1 to 2:4.35-1.1): Will attempt migration (Any information below is purely informational)
• nspr/mips64el (2:4.35-1.1 to 2:4.35-1.1)
  • Migration status for nspr/mips64el (2:4.35-1.1 to 2:4.35-1.1): Will attempt migration (Any information below is purely informational)
• nspr/ppc64el (2:4.35-1.1 to 2:4.35-1.1)
  • Migration status for nspr/ppc64el (2:4.35-1.1 to 2:4.35-1.1): Will attempt migration (Any information below is purely informational)
• nss-pam-ldapd/amd64 (0.9.12-4 to 0.9.12-4)
  • Migration status for nss-pam-ldapd/amd64 (0.9.12-4 to 0.9.12-4): Will attempt migration (Any information below is purely informational)
• nss-pam-ldapd/arm64 (0.9.12-4 to 0.9.12-4)
  • Migration status for nss-pam-ldapd/arm64 (0.9.12-4 to 0.9.12-4): Will attempt migration (Any information below is purely informational)
• nss-pam-ldapd/armel (0.9.12-4 to 0.9.12-4)
  • Migration status for nss-pam-ldapd/armel (0.9.12-4 to 0.9.12-4): Will attempt migration (Any information below is purely informational)
• nss-pam-ldapd/armhf (0.9.12-4 to 0.9.12-4)
  • Migration status for nss-pam-ldapd/armhf (0.9.12-4 to 0.9.12-4): Will attempt migration (Any information below is purely informational)
• nss-pam-ldapd/i386 (0.9.12-4 to 0.9.12-4)
  • Migration status for nss-pam-ldapd/i386 (0.9.12-4 to 0.9.12-4): Will attempt migration (Any information below is purely informational)
• nss-pam-ldapd/mips64el (0.9.12-4 to 0.9.12-4)
  • Migration status for nss-pam-ldapd/mips64el (0.9.12-4 to 0.9.12-4): Will attempt migration (Any information below is purely informational)
• nss-pam-ldapd/ppc64el (0.9.12-4 to 0.9.12-4)
  • Migration status for nss-pam-ldapd/ppc64el (0.9.12-4 to 0.9.12-4): Will attempt migration (Any information below is purely informational)
• nss-wrapper/amd64 (1.1.15-2 to 1.1.15-2)
  • Migration status for nss-wrapper/amd64 (1.1.15-2 to 1.1.15-2): Will attempt migration (Any information below is purely informational)
• nss-wrapper/arm64 (1.1.15-2 to 1.1.15-2)
  • Migration status for nss-wrapper/arm64 (1.1.15-2 to 1.1.15-2): Will attempt migration (Any information below is purely informational)
• nss-wrapper/armel (1.1.15-2 to 1.1.15-2)
  • Migration status for nss-wrapper/armel (1.1.15-2 to 1.1.15-2): Will attempt migration (Any information below is purely informational)
• nss-wrapper/armhf (1.1.15-2 to 1.1.15-2)
  • Migration status for nss-wrapper/armhf (1.1.15-2 to 1.1.15-2): Will attempt migration (Any information below is purely informational)
• nss-wrapper/i386 (1.1.15-2 to 1.1.15-2)
  • Migration status for nss-wrapper/i386 (1.1.15-2 to 1.1.15-2): Will attempt migration (Any information below is purely informational)
• nss-wrapper/mips64el (1.1.15-2 to 1.1.15-2)
  • Migration status for nss-wrapper/mips64el (1.1.15-2 to 1.1.15-2): Will attempt migration (Any information below is purely informational)
• nss-wrapper/ppc64el (1.1.15-2 to 1.1.15-2)
  • Migration status for nss-wrapper/ppc64el (1.1.15-2 to 1.1.15-2): Will attempt migration (Any information below is purely informational)
• nsync/amd64 (1.26.0-1 to 1.26.0-1)
  • Migration status for nsync/amd64 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• nsync/arm64 (1.26.0-1 to 1.26.0-1)
  • Migration status for nsync/arm64 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• nsync/armel (1.26.0-1 to 1.26.0-1)
  • Migration status for nsync/armel (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• nsync/armhf (1.26.0-1 to 1.26.0-1)
  • Migration status for nsync/armhf (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• nsync/i386 (1.26.0-1 to 1.26.0-1)
  • Migration status for nsync/i386 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• nsync/mips64el (1.26.0-1 to 1.26.0-1)
  • Migration status for nsync/mips64el (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• nsync/ppc64el (1.26.0-1 to 1.26.0-1)
  • Migration status for nsync/ppc64el (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• ntirpc/amd64 (4.3-3 to 4.3-3)
  • Migration status for ntirpc/amd64 (4.3-3 to 4.3-3): Will attempt migration (Any information below is purely informational)
• ntirpc/arm64 (4.3-3 to 4.3-3)
  • Migration status for ntirpc/arm64 (4.3-3 to 4.3-3): Will attempt migration (Any information below is purely informational)
• ntirpc/armel (4.3-3 to 4.3-3)
  • Migration status for ntirpc/armel (4.3-3 to 4.3-3): Will attempt migration (Any information below is purely informational)
• ntirpc/armhf (4.3-3 to 4.3-3)
  • Migration status for ntirpc/armhf (4.3-3 to 4.3-3): Will attempt migration (Any information below is purely informational)
• ntirpc/i386 (4.3-3 to 4.3-3)
  • Migration status for ntirpc/i386 (4.3-3 to 4.3-3): Will attempt migration (Any information below is purely informational)
• ntirpc/mips64el (4.3-3 to 4.3-3)
  • Migration status for ntirpc/mips64el (4.3-3 to 4.3-3): Will attempt migration (Any information below is purely informational)
• ntirpc/ppc64el (4.3-3 to 4.3-3)
  • Migration status for ntirpc/ppc64el (4.3-3 to 4.3-3): Will attempt migration (Any information below is purely informational)
• nurpawiki/amd64 (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/amd64 (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: nurpawiki/amd64 js-of-ocaml
    • Depends: nurpawiki/amd64 lwt/amd64
    • Depends: nurpawiki/amd64 ocaml-angstrom
    • Depends: nurpawiki/amd64 ocaml-cohttp/amd64
    • Depends: nurpawiki/amd64 ocaml-uri/amd64
    • Depends: nurpawiki/amd64 ocsigenserver/amd64
• nurpawiki/arm64 (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/arm64 (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: nurpawiki/arm64 js-of-ocaml
    • Depends: nurpawiki/arm64 lwt/arm64
    • Depends: nurpawiki/arm64 ocaml-angstrom
    • Depends: nurpawiki/arm64 ocaml-cohttp/arm64
    • Depends: nurpawiki/arm64 ocaml-uri/arm64
    • Depends: nurpawiki/arm64 ocsigenserver/arm64
• nurpawiki/armel (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/armel (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: nurpawiki/armel js-of-ocaml
    • Depends: nurpawiki/armel lwt/armel
    • Depends: nurpawiki/armel ocaml-angstrom
    • Depends: nurpawiki/armel ocaml-uri/armel
• nurpawiki/armhf (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/armhf (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: nurpawiki/armhf js-of-ocaml
    • Depends: nurpawiki/armhf lwt/armhf
    • Depends: nurpawiki/armhf ocaml-angstrom
    • Depends: nurpawiki/armhf ocaml-cohttp/armhf
    • Depends: nurpawiki/armhf ocaml-uri/armhf
    • Depends: nurpawiki/armhf ocsigenserver/armhf
• nurpawiki/i386 (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/i386 (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: nurpawiki/i386 js-of-ocaml
    • Depends: nurpawiki/i386 lwt/i386
    • Depends: nurpawiki/i386 ocaml-angstrom
    • Depends: nurpawiki/i386 ocaml-cohttp/i386
    • Depends: nurpawiki/i386 ocaml-uri/i386
    • Depends: nurpawiki/i386 ocsigenserver/i386
• nurpawiki/mips64el (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/mips64el (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: nurpawiki/mips64el js-of-ocaml
    • Depends: nurpawiki/mips64el lwt/mips64el
    • Depends: nurpawiki/mips64el ocaml-angstrom
    • Depends: nurpawiki/mips64el ocaml-uri/mips64el
• nurpawiki/ppc64el (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/ppc64el (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: nurpawiki/ppc64el js-of-ocaml
    • Depends: nurpawiki/ppc64el lwt/ppc64el
    • Depends: nurpawiki/ppc64el ocaml-angstrom
    • Depends: nurpawiki/ppc64el ocaml-cohttp/ppc64el
    • Depends: nurpawiki/ppc64el ocaml-uri/ppc64el
    • Depends: nurpawiki/ppc64el ocsigenserver/ppc64el
• nurpawiki/s390x (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/s390x (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: nurpawiki/s390x js-of-ocaml
    • Depends: nurpawiki/s390x lwt/s390x
    • Depends: nurpawiki/s390x ocaml-angstrom
    • Depends: nurpawiki/s390x ocaml-cohttp/s390x
    • Depends: nurpawiki/s390x ocaml-uri/s390x
    • Depends: nurpawiki/s390x ocsigenserver/s390x
• nuspell/amd64 (5.1.4-1 to 5.1.4-1)
  • Migration status for nuspell/amd64 (5.1.4-1 to 5.1.4-1): Will attempt migration (Any information below is purely informational)
• nuspell/arm64 (5.1.4-1 to 5.1.4-1)
  • Migration status for nuspell/arm64 (5.1.4-1 to 5.1.4-1): Will attempt migration (Any information below is purely informational)
• nuspell/armel (5.1.4-1 to 5.1.4-1)
  • Migration status for nuspell/armel (5.1.4-1 to 5.1.4-1): Will attempt migration (Any information below is purely informational)
• nuspell/armhf (5.1.4-1 to 5.1.4-1)
  • Migration status for nuspell/armhf (5.1.4-1 to 5.1.4-1): Will attempt migration (Any information below is purely informational)
• nuspell/i386 (5.1.4-1 to 5.1.4-1)
  • Migration status for nuspell/i386 (5.1.4-1 to 5.1.4-1): Will attempt migration (Any information below is purely informational)
• nuspell/mips64el (5.1.4-1 to 5.1.4-1)
  • Migration status for nuspell/mips64el (5.1.4-1 to 5.1.4-1): Will attempt migration (Any information below is purely informational)
• nuspell/ppc64el (5.1.4-1 to 5.1.4-1)
  • Migration status for nuspell/ppc64el (5.1.4-1 to 5.1.4-1): Will attempt migration (Any information below is purely informational)
• nvidia-graphics-drivers-tesla-470_pu (470.223.02-4 to 470.223.02-4~deb12u1)
  • Migration status for nvidia-graphics-drivers-tesla-470_pu (470.223.02-4 to 470.223.02-4~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-graphics-drivers-tesla-470 is newer in the target suite (470.223.02-4 470.223.02-4~deb12u1)
• nvidia-graphics-drivers-tesla_pu (525.147.05-7 to 525.147.05-7~deb12u1)
  • Migration status for nvidia-graphics-drivers-tesla_pu (525.147.05-7 to 525.147.05-7~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-graphics-drivers-tesla is newer in the target suite (525.147.05-7 525.147.05-7~deb12u1)
• nvidia-graphics-drivers_pu (525.147.05-7 to 525.147.05-7~deb12u1)
  • Migration status for nvidia-graphics-drivers_pu (525.147.05-7 to 525.147.05-7~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-graphics-drivers is newer in the target suite (525.147.05-7 525.147.05-7~deb12u1)
• nvidia-settings_pu (525.147.05-1 to 525.147.05-1~deb12u1)
  • Migration status for nvidia-settings_pu (525.147.05-1 to 525.147.05-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-settings is newer in the target suite (525.147.05-1 525.147.05-1~deb12u1)
• nvidia-vaapi-driver/amd64 (0.0.8-1 to 0.0.8-1)
  • Migration status for nvidia-vaapi-driver/amd64 (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• nvidia-vaapi-driver/arm64 (0.0.8-1 to 0.0.8-1)
  • Migration status for nvidia-vaapi-driver/arm64 (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• nvidia-vaapi-driver/armel (0.0.8-1 to 0.0.8-1)
  • Migration status for nvidia-vaapi-driver/armel (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• nvidia-vaapi-driver/armhf (0.0.8-1 to 0.0.8-1)
  • Migration status for nvidia-vaapi-driver/armhf (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• nvidia-vaapi-driver/i386 (0.0.8-1 to 0.0.8-1)
  • Migration status for nvidia-vaapi-driver/i386 (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• nvidia-vaapi-driver/mips64el (0.0.8-1 to 0.0.8-1)
  • Migration status for nvidia-vaapi-driver/mips64el (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• nvidia-vaapi-driver/ppc64el (0.0.8-1 to 0.0.8-1)
  • Migration status for nvidia-vaapi-driver/ppc64el (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• nx-libs/amd64 (2:3.5.99.27-1 to 2:3.5.99.27-1)
  • Migration status for nx-libs/amd64 (2:3.5.99.27-1 to 2:3.5.99.27-1): Will attempt migration (Any information below is purely informational)
• nx-libs/arm64 (2:3.5.99.27-1 to 2:3.5.99.27-1)
  • Migration status for nx-libs/arm64 (2:3.5.99.27-1 to 2:3.5.99.27-1): Will attempt migration (Any information below is purely informational)
• nx-libs/armel (2:3.5.99.27-1 to 2:3.5.99.27-1)
  • Migration status for nx-libs/armel (2:3.5.99.27-1 to 2:3.5.99.27-1): Will attempt migration (Any information below is purely informational)
• nx-libs/armhf (2:3.5.99.27-1 to 2:3.5.99.27-1)
  • Migration status for nx-libs/armhf (2:3.5.99.27-1 to 2:3.5.99.27-1): Will attempt migration (Any information below is purely informational)
• nx-libs/i386 (2:3.5.99.27-1 to 2:3.5.99.27-1)
  • Migration status for nx-libs/i386 (2:3.5.99.27-1 to 2:3.5.99.27-1): Will attempt migration (Any information below is purely informational)
• nx-libs/ppc64el (2:3.5.99.27-1 to 2:3.5.99.27-1)
  • Migration status for nx-libs/ppc64el (2:3.5.99.27-1 to 2:3.5.99.27-1): Will attempt migration (Any information below is purely informational)
• o2/amd64 (1.1~ds-4 to 1.1~ds-4)
  • Migration status for o2/amd64 (1.1~ds-4 to 1.1~ds-4): Will attempt migration (Any information below is purely informational)
• o2/arm64 (1.1~ds-4 to 1.1~ds-4)
  • Migration status for o2/arm64 (1.1~ds-4 to 1.1~ds-4): Will attempt migration (Any information below is purely informational)
• o2/armel (1.1~ds-4 to 1.1~ds-4)
  • Migration status for o2/armel (1.1~ds-4 to 1.1~ds-4): Will attempt migration (Any information below is purely informational)
• o2/armhf (1.1~ds-4 to 1.1~ds-4)
  • Migration status for o2/armhf (1.1~ds-4 to 1.1~ds-4): Will attempt migration (Any information below is purely informational)
• o2/i386 (1.1~ds-4 to 1.1~ds-4)
  • Migration status for o2/i386 (1.1~ds-4 to 1.1~ds-4): Will attempt migration (Any information below is purely informational)
• o2/mips64el (1.1~ds-4 to 1.1~ds-4)
  • Migration status for o2/mips64el (1.1~ds-4 to 1.1~ds-4): Will attempt migration (Any information below is purely informational)
• o2/ppc64el (1.1~ds-4 to 1.1~ds-4)
  • Migration status for o2/ppc64el (1.1~ds-4 to 1.1~ds-4): Will attempt migration (Any information below is purely informational)
• o3dgc/amd64 (0~20131011-5 to 0~20131011-5)
  • Migration status for o3dgc/amd64 (0~20131011-5 to 0~20131011-5): Will attempt migration (Any information below is purely informational)
• o3dgc/arm64 (0~20131011-5 to 0~20131011-5)
  • Migration status for o3dgc/arm64 (0~20131011-5 to 0~20131011-5): Will attempt migration (Any information below is purely informational)
• o3dgc/armel (0~20131011-5 to 0~20131011-5)
  • Migration status for o3dgc/armel (0~20131011-5 to 0~20131011-5): Will attempt migration (Any information below is purely informational)
• o3dgc/armhf (0~20131011-5 to 0~20131011-5)
  • Migration status for o3dgc/armhf (0~20131011-5 to 0~20131011-5): Will attempt migration (Any information below is purely informational)
• o3dgc/i386 (0~20131011-5 to 0~20131011-5)
  • Migration status for o3dgc/i386 (0~20131011-5 to 0~20131011-5): Will attempt migration (Any information below is purely informational)
• o3dgc/mips64el (0~20131011-5 to 0~20131011-5)
  • Migration status for o3dgc/mips64el (0~20131011-5 to 0~20131011-5): Will attempt migration (Any information below is purely informational)
• o3dgc/ppc64el (0~20131011-5 to 0~20131011-5)
  • Migration status for o3dgc/ppc64el (0~20131011-5 to 0~20131011-5): Will attempt migration (Any information below is purely informational)
• oakleaf/amd64 (0.0.1-3 to 0.0.1-3)
  • Migration status for oakleaf/amd64 (0.0.1-3 to 0.0.1-3): Will attempt migration (Any information below is purely informational)
• oakleaf/arm64 (0.0.1-3 to 0.0.1-3)
  • Migration status for oakleaf/arm64 (0.0.1-3 to 0.0.1-3): Will attempt migration (Any information below is purely informational)
• oakleaf/armel (0.0.1-3 to 0.0.1-3)
  • Migration status for oakleaf/armel (0.0.1-3 to 0.0.1-3): Will attempt migration (Any information below is purely informational)
• oakleaf/armhf (0.0.1-3 to 0.0.1-3)
  • Migration status for oakleaf/armhf (0.0.1-3 to 0.0.1-3): Will attempt migration (Any information below is purely informational)
• oakleaf/i386 (0.0.1-3 to 0.0.1-3)
  • Migration status for oakleaf/i386 (0.0.1-3 to 0.0.1-3): Will attempt migration (Any information below is purely informational)
• oakleaf/mips64el (0.0.1-3 to 0.0.1-3)
  • Migration status for oakleaf/mips64el (0.0.1-3 to 0.0.1-3): Will attempt migration (Any information below is purely informational)
• oakleaf/ppc64el (0.0.1-3 to 0.0.1-3)
  • Migration status for oakleaf/ppc64el (0.0.1-3 to 0.0.1-3): Will attempt migration (Any information below is purely informational)
• oasis/amd64 (0.4.11-3 to 0.4.11-3)
  • Migration status for oasis/amd64 (0.4.11-3 to 0.4.11-3): Will attempt migration (Any information below is purely informational)
    • Depends: oasis/amd64 ocamlbuild
• oasis/arm64 (0.4.11-3 to 0.4.11-3)
  • Migration status for oasis/arm64 (0.4.11-3 to 0.4.11-3): Will attempt migration (Any information below is purely informational)
    • Depends: oasis/arm64 ocamlbuild
• oasis/armel (0.4.11-3 to 0.4.11-3)
  • Migration status for oasis/armel (0.4.11-3 to 0.4.11-3): Will attempt migration (Any information below is purely informational)
    • Depends: oasis/armel ocamlbuild
• oasis/armhf (0.4.11-3 to 0.4.11-3)
  • Migration status for oasis/armhf (0.4.11-3 to 0.4.11-3): Will attempt migration (Any information below is purely informational)
    • Depends: oasis/armhf ocamlbuild
• oasis/i386 (0.4.11-3 to 0.4.11-3)
  • Migration status for oasis/i386 (0.4.11-3 to 0.4.11-3): Will attempt migration (Any information below is purely informational)
    • Depends: oasis/i386 ocamlbuild
• oasis/mips64el (0.4.11-3 to 0.4.11-3)
  • Migration status for oasis/mips64el (0.4.11-3 to 0.4.11-3): Will attempt migration (Any information below is purely informational)
    • Depends: oasis/mips64el ocamlbuild
• oasis/ppc64el (0.4.11-3 to 0.4.11-3)
  • Migration status for oasis/ppc64el (0.4.11-3 to 0.4.11-3): Will attempt migration (Any information below is purely informational)
    • Depends: oasis/ppc64el ocamlbuild
• oasis/s390x (0.4.11-3 to 0.4.11-3)
  • Migration status for oasis/s390x (0.4.11-3 to 0.4.11-3): Will attempt migration (Any information below is purely informational)
    • Depends: oasis/s390x ocamlbuild
• obus/amd64 (1.2.4-3 to 1.2.4-3)
  • Migration status for obus/amd64 (1.2.4-3 to 1.2.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: obus/amd64 lwt/amd64
    • Depends: obus/amd64 ppxlib
• obus/arm64 (1.2.4-3 to 1.2.4-3)
  • Migration status for obus/arm64 (1.2.4-3 to 1.2.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: obus/arm64 lwt/arm64
    • Depends: obus/arm64 ppxlib
• obus/armel (1.2.4-3 to 1.2.4-3)
  • Migration status for obus/armel (1.2.4-3 to 1.2.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: obus/armel lwt/armel
    • Depends: obus/armel ppxlib
• obus/armhf (1.2.4-3 to 1.2.4-3)
  • Migration status for obus/armhf (1.2.4-3 to 1.2.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: obus/armhf lwt/armhf
    • Depends: obus/armhf ppxlib
• obus/i386 (1.2.4-3 to 1.2.4-3)
  • Migration status for obus/i386 (1.2.4-3 to 1.2.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: obus/i386 lwt/i386
    • Depends: obus/i386 ppxlib
• obus/mips64el (1.2.4-3 to 1.2.4-3)
  • Migration status for obus/mips64el (1.2.4-3 to 1.2.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: obus/mips64el lwt/mips64el
    • Depends: obus/mips64el ppxlib
• obus/ppc64el (1.2.4-3 to 1.2.4-3)
  • Migration status for obus/ppc64el (1.2.4-3 to 1.2.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: obus/ppc64el lwt/ppc64el
    • Depends: obus/ppc64el ppxlib
• obus/s390x (1.2.4-3 to 1.2.4-3)
  • Migration status for obus/s390x (1.2.4-3 to 1.2.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: obus/s390x lwt/s390x
    • Depends: obus/s390x ppxlib
• ocaml-asn1-combinators/amd64 (0.2.6-4 to 0.2.6-4)
  • Migration status for ocaml-asn1-combinators/amd64 (0.2.6-4 to 0.2.6-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-asn1-combinators/amd64 ocaml-cstruct/amd64
• ocaml-asn1-combinators/arm64 (0.2.6-4 to 0.2.6-4)
  • Migration status for ocaml-asn1-combinators/arm64 (0.2.6-4 to 0.2.6-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-asn1-combinators/arm64 ocaml-cstruct/arm64
• ocaml-asn1-combinators/armhf (0.2.6-4 to 0.2.6-4)
  • Migration status for ocaml-asn1-combinators/armhf (0.2.6-4 to 0.2.6-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-asn1-combinators/armhf ocaml-cstruct/armhf
• ocaml-asn1-combinators/i386 (0.2.6-4 to 0.2.6-4)
  • Migration status for ocaml-asn1-combinators/i386 (0.2.6-4 to 0.2.6-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-asn1-combinators/i386 ocaml-cstruct/i386
• ocaml-asn1-combinators/ppc64el (0.2.6-4 to 0.2.6-4)
  • Migration status for ocaml-asn1-combinators/ppc64el (0.2.6-4 to 0.2.6-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-asn1-combinators/ppc64el ocaml-cstruct/ppc64el
• ocaml-asn1-combinators/s390x (0.2.6-4 to 0.2.6-4)
  • Migration status for ocaml-asn1-combinators/s390x (0.2.6-4 to 0.2.6-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-asn1-combinators/s390x ocaml-cstruct/s390x
• ocaml-bitstring/amd64 (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/amd64 (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bitstring/amd64 ppxlib
    • Implicit dependency: ocaml-bitstring/amd64 mlpost/amd64
• ocaml-bitstring/arm64 (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/arm64 (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bitstring/arm64 ppxlib
    • Implicit dependency: ocaml-bitstring/arm64 mlpost/arm64
• ocaml-bitstring/armel (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/armel (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bitstring/armel ppxlib
    • Implicit dependency: ocaml-bitstring/armel mlpost/armel
• ocaml-bitstring/armhf (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/armhf (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bitstring/armhf ppxlib
    • Implicit dependency: ocaml-bitstring/armhf mlpost/armhf
• ocaml-bitstring/i386 (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/i386 (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bitstring/i386 ppxlib
    • Implicit dependency: ocaml-bitstring/i386 mlpost/i386
• ocaml-bitstring/mips64el (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/mips64el (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bitstring/mips64el ppxlib
    • Implicit dependency: ocaml-bitstring/mips64el mlpost/mips64el
• ocaml-bitstring/ppc64el (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/ppc64el (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bitstring/ppc64el ppxlib
    • Implicit dependency: ocaml-bitstring/ppc64el mlpost/ppc64el
• ocaml-bitstring/s390x (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/s390x (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bitstring/s390x ppxlib
    • Implicit dependency: ocaml-bitstring/s390x mlpost/s390x
• ocaml-bos/amd64 (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-bos/amd64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bos/amd64 ocaml-logs/amd64
• ocaml-bos/arm64 (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-bos/arm64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bos/arm64 ocaml-logs/arm64
• ocaml-bos/armhf (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-bos/armhf (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bos/armhf ocaml-logs/armhf
• ocaml-bos/i386 (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-bos/i386 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bos/i386 ocaml-logs/i386
• ocaml-bos/ppc64el (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-bos/ppc64el (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bos/ppc64el ocaml-logs/ppc64el
• ocaml-bos/s390x (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-bos/s390x (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-bos/s390x ocaml-logs/s390x
• ocaml-ca-certs/amd64 (0.2.3-3 to 0.2.3-3)
  • Migration status for ocaml-ca-certs/amd64 (0.2.3-3 to 0.2.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ca-certs/amd64 ocaml-cstruct/amd64
    • Depends: ocaml-ca-certs/amd64 ocaml-logs/amd64
• ocaml-ca-certs/arm64 (0.2.3-3 to 0.2.3-3)
  • Migration status for ocaml-ca-certs/arm64 (0.2.3-3 to 0.2.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ca-certs/arm64 ocaml-cstruct/arm64
    • Depends: ocaml-ca-certs/arm64 ocaml-logs/arm64
• ocaml-ca-certs/armhf (0.2.3-3 to 0.2.3-3)
  • Migration status for ocaml-ca-certs/armhf (0.2.3-3 to 0.2.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ca-certs/armhf ocaml-cstruct/armhf
    • Depends: ocaml-ca-certs/armhf ocaml-logs/armhf
• ocaml-ca-certs/i386 (0.2.3-3 to 0.2.3-3)
  • Migration status for ocaml-ca-certs/i386 (0.2.3-3 to 0.2.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ca-certs/i386 ocaml-cstruct/i386
    • Depends: ocaml-ca-certs/i386 ocaml-logs/i386
• ocaml-ca-certs/ppc64el (0.2.3-3 to 0.2.3-3)
  • Migration status for ocaml-ca-certs/ppc64el (0.2.3-3 to 0.2.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ca-certs/ppc64el ocaml-cstruct/ppc64el
    • Depends: ocaml-ca-certs/ppc64el ocaml-logs/ppc64el
• ocaml-ca-certs/s390x (0.2.3-3 to 0.2.3-3)
  • Migration status for ocaml-ca-certs/s390x (0.2.3-3 to 0.2.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ca-certs/s390x ocaml-cstruct/s390x
    • Depends: ocaml-ca-certs/s390x ocaml-logs/s390x
• ocaml-cohttp/amd64 (5.3.0-1 to 5.3.0-1)
  • Migration status for ocaml-cohttp/amd64 (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cohttp/amd64 js-of-ocaml
    • Depends: ocaml-cohttp/amd64 lwt/amd64
    • Depends: ocaml-cohttp/amd64 ocaml-angstrom
    • Depends: ocaml-cohttp/amd64 ocaml-conduit
    • Depends: ocaml-cohttp/amd64 ocaml-logs/amd64
    • Depends: ocaml-cohttp/amd64 ocaml-uri/amd64
    • Implicit dependency: ocaml-cohttp/amd64 eliom
    • Implicit dependency: ocaml-cohttp/amd64 nurpawiki/amd64
    • Implicit dependency: ocaml-cohttp/amd64 ocsigenserver/amd64
    • Implicit dependency: ocaml-cohttp/amd64 ocsipersist/amd64
• ocaml-cohttp/arm64 (5.3.0-1 to 5.3.0-1)
  • Migration status for ocaml-cohttp/arm64 (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cohttp/arm64 js-of-ocaml
    • Depends: ocaml-cohttp/arm64 lwt/arm64
    • Depends: ocaml-cohttp/arm64 ocaml-angstrom
    • Depends: ocaml-cohttp/arm64 ocaml-conduit
    • Depends: ocaml-cohttp/arm64 ocaml-logs/arm64
    • Depends: ocaml-cohttp/arm64 ocaml-uri/arm64
    • Implicit dependency: ocaml-cohttp/arm64 eliom
    • Implicit dependency: ocaml-cohttp/arm64 nurpawiki/arm64
    • Implicit dependency: ocaml-cohttp/arm64 ocsigenserver/arm64
    • Implicit dependency: ocaml-cohttp/arm64 ocsipersist/arm64
• ocaml-cohttp/armel (5.3.0-1 to 5.3.0-1)
  • Migration status for ocaml-cohttp/armel (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cohttp/armel js-of-ocaml
    • Depends: ocaml-cohttp/armel lwt/armel
    • Depends: ocaml-cohttp/armel ocaml-angstrom
    • Depends: ocaml-cohttp/armel ocaml-uri/armel
• ocaml-cohttp/armhf (5.3.0-1 to 5.3.0-1)
  • Migration status for ocaml-cohttp/armhf (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cohttp/armhf js-of-ocaml
    • Depends: ocaml-cohttp/armhf lwt/armhf
    • Depends: ocaml-cohttp/armhf ocaml-angstrom
    • Depends: ocaml-cohttp/armhf ocaml-conduit
    • Depends: ocaml-cohttp/armhf ocaml-logs/armhf
    • Depends: ocaml-cohttp/armhf ocaml-uri/armhf
    • Implicit dependency: ocaml-cohttp/armhf eliom
    • Implicit dependency: ocaml-cohttp/armhf nurpawiki/armhf
    • Implicit dependency: ocaml-cohttp/armhf ocsigenserver/armhf
    • Implicit dependency: ocaml-cohttp/armhf ocsipersist/armhf
• ocaml-cohttp/i386 (5.3.0-1 to 5.3.0-1)
  • Migration status for ocaml-cohttp/i386 (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cohttp/i386 js-of-ocaml
    • Depends: ocaml-cohttp/i386 lwt/i386
    • Depends: ocaml-cohttp/i386 ocaml-angstrom
    • Depends: ocaml-cohttp/i386 ocaml-conduit
    • Depends: ocaml-cohttp/i386 ocaml-logs/i386
    • Depends: ocaml-cohttp/i386 ocaml-uri/i386
    • Implicit dependency: ocaml-cohttp/i386 eliom
    • Implicit dependency: ocaml-cohttp/i386 nurpawiki/i386
    • Implicit dependency: ocaml-cohttp/i386 ocsigenserver/i386
    • Implicit dependency: ocaml-cohttp/i386 ocsipersist/i386
• ocaml-cohttp/mips64el (5.3.0-1 to 5.3.0-1)
  • Migration status for ocaml-cohttp/mips64el (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cohttp/mips64el js-of-ocaml
    • Depends: ocaml-cohttp/mips64el lwt/mips64el
    • Depends: ocaml-cohttp/mips64el ocaml-angstrom
    • Depends: ocaml-cohttp/mips64el ocaml-uri/mips64el
• ocaml-cohttp/ppc64el (5.3.0-1 to 5.3.0-1)
  • Migration status for ocaml-cohttp/ppc64el (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cohttp/ppc64el js-of-ocaml
    • Depends: ocaml-cohttp/ppc64el lwt/ppc64el
    • Depends: ocaml-cohttp/ppc64el ocaml-angstrom
    • Depends: ocaml-cohttp/ppc64el ocaml-conduit
    • Depends: ocaml-cohttp/ppc64el ocaml-logs/ppc64el
    • Depends: ocaml-cohttp/ppc64el ocaml-uri/ppc64el
    • Implicit dependency: ocaml-cohttp/ppc64el eliom
    • Implicit dependency: ocaml-cohttp/ppc64el nurpawiki/ppc64el
    • Implicit dependency: ocaml-cohttp/ppc64el ocsigenserver/ppc64el
    • Implicit dependency: ocaml-cohttp/ppc64el ocsipersist/ppc64el
• ocaml-cohttp/s390x (5.3.0-1 to 5.3.0-1)
  • Migration status for ocaml-cohttp/s390x (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cohttp/s390x js-of-ocaml
    • Depends: ocaml-cohttp/s390x lwt/s390x
    • Depends: ocaml-cohttp/s390x ocaml-angstrom
    • Depends: ocaml-cohttp/s390x ocaml-conduit
    • Depends: ocaml-cohttp/s390x ocaml-logs/s390x
    • Depends: ocaml-cohttp/s390x ocaml-uri/s390x
    • Implicit dependency: ocaml-cohttp/s390x eliom
    • Implicit dependency: ocaml-cohttp/s390x nurpawiki/s390x
    • Implicit dependency: ocaml-cohttp/s390x ocsigenserver/s390x
    • Implicit dependency: ocaml-cohttp/s390x ocsipersist/s390x
• ocaml-cstruct/amd64 (6.2.0-2 to 6.2.0-2)
  • Migration status for ocaml-cstruct/amd64 (6.2.0-2 to 6.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cstruct/amd64 lwt/amd64
    • Depends: ocaml-cstruct/amd64 ppxlib
    • Depends: ocaml-cstruct/amd64 sexplib310/amd64
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-asn1-combinators/amd64
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-ca-certs/amd64
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-eqaf/amd64
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-hex/amd64
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-ipaddr/amd64
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-mirage-crypto
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-pbkdf/amd64
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-randomconv/amd64
    • Implicit dependency: ocaml-cstruct/amd64 ocaml-x509/amd64
    • Implicit dependency: ocaml-cstruct/amd64 pgocaml/amd64
• ocaml-cstruct/arm64 (6.2.0-2 to 6.2.0-2)
  • Migration status for ocaml-cstruct/arm64 (6.2.0-2 to 6.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cstruct/arm64 lwt/arm64
    • Depends: ocaml-cstruct/arm64 ppxlib
    • Depends: ocaml-cstruct/arm64 sexplib310/arm64
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-asn1-combinators/arm64
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-ca-certs/arm64
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-eqaf/arm64
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-hex/arm64
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-ipaddr/arm64
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-mirage-crypto
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-pbkdf/arm64
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-randomconv/arm64
    • Implicit dependency: ocaml-cstruct/arm64 ocaml-x509/arm64
    • Implicit dependency: ocaml-cstruct/arm64 pgocaml/arm64
• ocaml-cstruct/armel (6.2.0-2 to 6.2.0-2)
  • Migration status for ocaml-cstruct/armel (6.2.0-2 to 6.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cstruct/armel lwt/armel
    • Depends: ocaml-cstruct/armel ppxlib
    • Depends: ocaml-cstruct/armel sexplib310/armel
• ocaml-cstruct/armhf (6.2.0-2 to 6.2.0-2)
  • Migration status for ocaml-cstruct/armhf (6.2.0-2 to 6.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cstruct/armhf lwt/armhf
    • Depends: ocaml-cstruct/armhf ppxlib
    • Depends: ocaml-cstruct/armhf sexplib310/armhf
    • Implicit dependency: ocaml-cstruct/armhf ocaml-asn1-combinators/armhf
    • Implicit dependency: ocaml-cstruct/armhf ocaml-ca-certs/armhf
    • Implicit dependency: ocaml-cstruct/armhf ocaml-eqaf/armhf
    • Implicit dependency: ocaml-cstruct/armhf ocaml-hex/armhf
    • Implicit dependency: ocaml-cstruct/armhf ocaml-ipaddr/armhf
    • Implicit dependency: ocaml-cstruct/armhf ocaml-mirage-crypto
    • Implicit dependency: ocaml-cstruct/armhf ocaml-pbkdf/armhf
    • Implicit dependency: ocaml-cstruct/armhf ocaml-randomconv/armhf
    • Implicit dependency: ocaml-cstruct/armhf ocaml-x509/armhf
    • Implicit dependency: ocaml-cstruct/armhf pgocaml/armhf
• ocaml-cstruct/i386 (6.2.0-2 to 6.2.0-2)
  • Migration status for ocaml-cstruct/i386 (6.2.0-2 to 6.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cstruct/i386 lwt/i386
    • Depends: ocaml-cstruct/i386 ppxlib
    • Depends: ocaml-cstruct/i386 sexplib310/i386
    • Implicit dependency: ocaml-cstruct/i386 ocaml-asn1-combinators/i386
    • Implicit dependency: ocaml-cstruct/i386 ocaml-ca-certs/i386
    • Implicit dependency: ocaml-cstruct/i386 ocaml-eqaf/i386
    • Implicit dependency: ocaml-cstruct/i386 ocaml-hex/i386
    • Implicit dependency: ocaml-cstruct/i386 ocaml-ipaddr/i386
    • Implicit dependency: ocaml-cstruct/i386 ocaml-mirage-crypto
    • Implicit dependency: ocaml-cstruct/i386 ocaml-pbkdf/i386
    • Implicit dependency: ocaml-cstruct/i386 ocaml-randomconv/i386
    • Implicit dependency: ocaml-cstruct/i386 ocaml-x509/i386
    • Implicit dependency: ocaml-cstruct/i386 pgocaml/i386
• ocaml-cstruct/mips64el (6.2.0-2 to 6.2.0-2)
  • Migration status for ocaml-cstruct/mips64el (6.2.0-2 to 6.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cstruct/mips64el lwt/mips64el
    • Depends: ocaml-cstruct/mips64el ppxlib
    • Depends: ocaml-cstruct/mips64el sexplib310/mips64el
• ocaml-cstruct/ppc64el (6.2.0-2 to 6.2.0-2)
  • Migration status for ocaml-cstruct/ppc64el (6.2.0-2 to 6.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cstruct/ppc64el lwt/ppc64el
    • Depends: ocaml-cstruct/ppc64el ppxlib
    • Depends: ocaml-cstruct/ppc64el sexplib310/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-asn1-combinators/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-ca-certs/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-eqaf/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-hex/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-ipaddr/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-mirage-crypto
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-pbkdf/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-randomconv/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el ocaml-x509/ppc64el
    • Implicit dependency: ocaml-cstruct/ppc64el pgocaml/ppc64el
• ocaml-cstruct/s390x (6.2.0-2 to 6.2.0-2)
  • Migration status for ocaml-cstruct/s390x (6.2.0-2 to 6.2.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-cstruct/s390x lwt/s390x
    • Depends: ocaml-cstruct/s390x ppxlib
    • Depends: ocaml-cstruct/s390x sexplib310/s390x
    • Implicit dependency: ocaml-cstruct/s390x ocaml-asn1-combinators/s390x
    • Implicit dependency: ocaml-cstruct/s390x ocaml-ca-certs/s390x
    • Implicit dependency: ocaml-cstruct/s390x ocaml-eqaf/s390x
    • Implicit dependency: ocaml-cstruct/s390x ocaml-hex/s390x
    • Implicit dependency: ocaml-cstruct/s390x ocaml-ipaddr/s390x
    • Implicit dependency: ocaml-cstruct/s390x ocaml-mirage-crypto
    • Implicit dependency: ocaml-cstruct/s390x ocaml-pbkdf/s390x
    • Implicit dependency: ocaml-cstruct/s390x ocaml-randomconv/s390x
    • Implicit dependency: ocaml-cstruct/s390x ocaml-x509/s390x
    • Implicit dependency: ocaml-cstruct/s390x pgocaml/s390x
• ocaml-eqaf/amd64 (0.9-4 to 0.9-4)
  • Migration status for ocaml-eqaf/amd64 (0.9-4 to 0.9-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-eqaf/amd64 ocaml-cstruct/amd64
• ocaml-eqaf/arm64 (0.9-4 to 0.9-4)
  • Migration status for ocaml-eqaf/arm64 (0.9-4 to 0.9-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-eqaf/arm64 ocaml-cstruct/arm64
• ocaml-eqaf/armhf (0.9-4 to 0.9-4)
  • Migration status for ocaml-eqaf/armhf (0.9-4 to 0.9-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-eqaf/armhf ocaml-cstruct/armhf
• ocaml-eqaf/i386 (0.9-4 to 0.9-4)
  • Migration status for ocaml-eqaf/i386 (0.9-4 to 0.9-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-eqaf/i386 ocaml-cstruct/i386
• ocaml-eqaf/ppc64el (0.9-4 to 0.9-4)
  • Migration status for ocaml-eqaf/ppc64el (0.9-4 to 0.9-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-eqaf/ppc64el ocaml-cstruct/ppc64el
• ocaml-eqaf/s390x (0.9-4 to 0.9-4)
  • Migration status for ocaml-eqaf/s390x (0.9-4 to 0.9-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-eqaf/s390x ocaml-cstruct/s390x
• ocaml-expect/amd64 (0.0.6-3 to 0.0.6-3)
  • Migration status for ocaml-expect/amd64 (0.0.6-3 to 0.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-expect/amd64 ocaml-batteries
• ocaml-expect/arm64 (0.0.6-3 to 0.0.6-3)
  • Migration status for ocaml-expect/arm64 (0.0.6-3 to 0.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-expect/arm64 ocaml-batteries
• ocaml-expect/armhf (0.0.6-3 to 0.0.6-3)
  • Migration status for ocaml-expect/armhf (0.0.6-3 to 0.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-expect/armhf ocaml-batteries
• ocaml-expect/i386 (0.0.6-3 to 0.0.6-3)
  • Migration status for ocaml-expect/i386 (0.0.6-3 to 0.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-expect/i386 ocaml-batteries
• ocaml-expect/ppc64el (0.0.6-3 to 0.0.6-3)
  • Migration status for ocaml-expect/ppc64el (0.0.6-3 to 0.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-expect/ppc64el ocaml-batteries
• ocaml-expect/s390x (0.0.6-3 to 0.0.6-3)
  • Migration status for ocaml-expect/s390x (0.0.6-3 to 0.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-expect/s390x ocaml-batteries
• ocaml-hex/amd64 (1.5.0-3 to 1.5.0-3)
  • Migration status for ocaml-hex/amd64 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-hex/amd64 ocaml-cstruct/amd64
• ocaml-hex/arm64 (1.5.0-3 to 1.5.0-3)
  • Migration status for ocaml-hex/arm64 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-hex/arm64 ocaml-cstruct/arm64
• ocaml-hex/armhf (1.5.0-3 to 1.5.0-3)
  • Migration status for ocaml-hex/armhf (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-hex/armhf ocaml-cstruct/armhf
• ocaml-hex/i386 (1.5.0-3 to 1.5.0-3)
  • Migration status for ocaml-hex/i386 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-hex/i386 ocaml-cstruct/i386
• ocaml-hex/ppc64el (1.5.0-3 to 1.5.0-3)
  • Migration status for ocaml-hex/ppc64el (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-hex/ppc64el ocaml-cstruct/ppc64el
• ocaml-hex/s390x (1.5.0-3 to 1.5.0-3)
  • Migration status for ocaml-hex/s390x (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-hex/s390x ocaml-cstruct/s390x
• ocaml-ipaddr/amd64 (5.5.0-3 to 5.5.0-3)
  • Migration status for ocaml-ipaddr/amd64 (5.5.0-3 to 5.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ipaddr/amd64 ocaml-cstruct/amd64
• ocaml-ipaddr/arm64 (5.5.0-3 to 5.5.0-3)
  • Migration status for ocaml-ipaddr/arm64 (5.5.0-3 to 5.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ipaddr/arm64 ocaml-cstruct/arm64
• ocaml-ipaddr/armhf (5.5.0-3 to 5.5.0-3)
  • Migration status for ocaml-ipaddr/armhf (5.5.0-3 to 5.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ipaddr/armhf ocaml-cstruct/armhf
• ocaml-ipaddr/i386 (5.5.0-3 to 5.5.0-3)
  • Migration status for ocaml-ipaddr/i386 (5.5.0-3 to 5.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ipaddr/i386 ocaml-cstruct/i386
• ocaml-ipaddr/ppc64el (5.5.0-3 to 5.5.0-3)
  • Migration status for ocaml-ipaddr/ppc64el (5.5.0-3 to 5.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ipaddr/ppc64el ocaml-cstruct/ppc64el
• ocaml-ipaddr/s390x (5.5.0-3 to 5.5.0-3)
  • Migration status for ocaml-ipaddr/s390x (5.5.0-3 to 5.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ipaddr/s390x ocaml-cstruct/s390x
• ocaml-logs/amd64 (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/amd64 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-logs/amd64 js-of-ocaml
    • Depends: ocaml-logs/amd64 lwt/amd64
    • Implicit dependency: ocaml-logs/amd64 camlp5/amd64
    • Implicit dependency: ocaml-logs/amd64 camlp5-buildscripts/amd64
    • Implicit dependency: ocaml-logs/amd64 lambda-term/amd64
    • Implicit dependency: ocaml-logs/amd64 ocaml-bos/amd64
    • Implicit dependency: ocaml-logs/amd64 ocaml-ca-certs/amd64
    • Implicit dependency: ocaml-logs/amd64 ocaml-cohttp/amd64
    • Implicit dependency: ocaml-logs/amd64 ocaml-conduit
    • Implicit dependency: ocaml-logs/amd64 ocaml-mirage-crypto
    • Implicit dependency: ocaml-logs/amd64 ocaml-x509/amd64
    • Implicit dependency: ocaml-logs/amd64 ocplib-simplex/amd64
    • Implicit dependency: ocaml-logs/amd64 ocsigenserver/amd64
    • Implicit dependency: ocaml-logs/amd64 utop/amd64
• ocaml-logs/arm64 (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/arm64 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-logs/arm64 js-of-ocaml
    • Depends: ocaml-logs/arm64 lwt/arm64
    • Implicit dependency: ocaml-logs/arm64 camlp5/arm64
    • Implicit dependency: ocaml-logs/arm64 camlp5-buildscripts/arm64
    • Implicit dependency: ocaml-logs/arm64 lambda-term/arm64
    • Implicit dependency: ocaml-logs/arm64 ocaml-bos/arm64
    • Implicit dependency: ocaml-logs/arm64 ocaml-ca-certs/arm64
    • Implicit dependency: ocaml-logs/arm64 ocaml-cohttp/arm64
    • Implicit dependency: ocaml-logs/arm64 ocaml-conduit
    • Implicit dependency: ocaml-logs/arm64 ocaml-mirage-crypto
    • Implicit dependency: ocaml-logs/arm64 ocaml-x509/arm64
    • Implicit dependency: ocaml-logs/arm64 ocplib-simplex/arm64
    • Implicit dependency: ocaml-logs/arm64 ocsigenserver/arm64
    • Implicit dependency: ocaml-logs/arm64 utop/arm64
• ocaml-logs/armel (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/armel (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-logs/armel js-of-ocaml
    • Depends: ocaml-logs/armel lwt/armel
• ocaml-logs/armhf (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/armhf (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-logs/armhf js-of-ocaml
    • Depends: ocaml-logs/armhf lwt/armhf
    • Implicit dependency: ocaml-logs/armhf camlp5/armhf
    • Implicit dependency: ocaml-logs/armhf camlp5-buildscripts/armhf
    • Implicit dependency: ocaml-logs/armhf lambda-term/armhf
    • Implicit dependency: ocaml-logs/armhf ocaml-bos/armhf
    • Implicit dependency: ocaml-logs/armhf ocaml-ca-certs/armhf
    • Implicit dependency: ocaml-logs/armhf ocaml-cohttp/armhf
    • Implicit dependency: ocaml-logs/armhf ocaml-conduit
    • Implicit dependency: ocaml-logs/armhf ocaml-mirage-crypto
    • Implicit dependency: ocaml-logs/armhf ocaml-x509/armhf
    • Implicit dependency: ocaml-logs/armhf ocplib-simplex/armhf
    • Implicit dependency: ocaml-logs/armhf ocsigenserver/armhf
    • Implicit dependency: ocaml-logs/armhf utop/armhf
• ocaml-logs/i386 (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/i386 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-logs/i386 js-of-ocaml
    • Depends: ocaml-logs/i386 lwt/i386
    • Implicit dependency: ocaml-logs/i386 camlp5/i386
    • Implicit dependency: ocaml-logs/i386 camlp5-buildscripts/i386
    • Implicit dependency: ocaml-logs/i386 lambda-term/i386
    • Implicit dependency: ocaml-logs/i386 ocaml-bos/i386
    • Implicit dependency: ocaml-logs/i386 ocaml-ca-certs/i386
    • Implicit dependency: ocaml-logs/i386 ocaml-cohttp/i386
    • Implicit dependency: ocaml-logs/i386 ocaml-conduit
    • Implicit dependency: ocaml-logs/i386 ocaml-mirage-crypto
    • Implicit dependency: ocaml-logs/i386 ocaml-x509/i386
    • Implicit dependency: ocaml-logs/i386 ocplib-simplex/i386
    • Implicit dependency: ocaml-logs/i386 ocsigenserver/i386
    • Implicit dependency: ocaml-logs/i386 utop/i386
• ocaml-logs/mips64el (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/mips64el (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-logs/mips64el js-of-ocaml
    • Depends: ocaml-logs/mips64el lwt/mips64el
• ocaml-logs/ppc64el (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/ppc64el (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-logs/ppc64el js-of-ocaml
    • Depends: ocaml-logs/ppc64el lwt/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el camlp5/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el camlp5-buildscripts/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el lambda-term/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el ocaml-bos/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el ocaml-ca-certs/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el ocaml-cohttp/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el ocaml-conduit
    • Implicit dependency: ocaml-logs/ppc64el ocaml-mirage-crypto
    • Implicit dependency: ocaml-logs/ppc64el ocaml-x509/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el ocplib-simplex/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el ocsigenserver/ppc64el
    • Implicit dependency: ocaml-logs/ppc64el utop/ppc64el
• ocaml-logs/s390x (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/s390x (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-logs/s390x js-of-ocaml
    • Depends: ocaml-logs/s390x lwt/s390x
    • Implicit dependency: ocaml-logs/s390x camlp5/s390x
    • Implicit dependency: ocaml-logs/s390x camlp5-buildscripts/s390x
    • Implicit dependency: ocaml-logs/s390x lambda-term/s390x
    • Implicit dependency: ocaml-logs/s390x ocaml-bos/s390x
    • Implicit dependency: ocaml-logs/s390x ocaml-ca-certs/s390x
    • Implicit dependency: ocaml-logs/s390x ocaml-cohttp/s390x
    • Implicit dependency: ocaml-logs/s390x ocaml-conduit
    • Implicit dependency: ocaml-logs/s390x ocaml-mirage-crypto
    • Implicit dependency: ocaml-logs/s390x ocaml-x509/s390x
    • Implicit dependency: ocaml-logs/s390x ocplib-simplex/s390x
    • Implicit dependency: ocaml-logs/s390x ocsigenserver/s390x
    • Implicit dependency: ocaml-logs/s390x utop/s390x
• ocaml-pbkdf/amd64 (1.2.0-3 to 1.2.0-3)
  • Migration status for ocaml-pbkdf/amd64 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-pbkdf/amd64 ocaml-cstruct/amd64
• ocaml-pbkdf/arm64 (1.2.0-3 to 1.2.0-3)
  • Migration status for ocaml-pbkdf/arm64 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-pbkdf/arm64 ocaml-cstruct/arm64
• ocaml-pbkdf/armhf (1.2.0-3 to 1.2.0-3)
  • Migration status for ocaml-pbkdf/armhf (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-pbkdf/armhf ocaml-cstruct/armhf
• ocaml-pbkdf/i386 (1.2.0-3 to 1.2.0-3)
  • Migration status for ocaml-pbkdf/i386 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-pbkdf/i386 ocaml-cstruct/i386
• ocaml-pbkdf/ppc64el (1.2.0-3 to 1.2.0-3)
  • Migration status for ocaml-pbkdf/ppc64el (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-pbkdf/ppc64el ocaml-cstruct/ppc64el
• ocaml-pbkdf/s390x (1.2.0-3 to 1.2.0-3)
  • Migration status for ocaml-pbkdf/s390x (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-pbkdf/s390x ocaml-cstruct/s390x
• ocaml-randomconv/amd64 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-randomconv/amd64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-randomconv/amd64 ocaml-cstruct/amd64
• ocaml-randomconv/arm64 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-randomconv/arm64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-randomconv/arm64 ocaml-cstruct/arm64
• ocaml-randomconv/armhf (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-randomconv/armhf (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-randomconv/armhf ocaml-cstruct/armhf
• ocaml-randomconv/i386 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-randomconv/i386 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-randomconv/i386 ocaml-cstruct/i386
• ocaml-randomconv/ppc64el (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-randomconv/ppc64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-randomconv/ppc64el ocaml-cstruct/ppc64el
• ocaml-randomconv/s390x (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-randomconv/s390x (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-randomconv/s390x ocaml-cstruct/s390x
• ocaml-reins/amd64 (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/amd64 (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-reins/amd64 ocaml-num
• ocaml-reins/arm64 (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/arm64 (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-reins/arm64 ocaml-num
• ocaml-reins/armel (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/armel (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-reins/armel ocaml-num
• ocaml-reins/armhf (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/armhf (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-reins/armhf ocaml-num
• ocaml-reins/i386 (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/i386 (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-reins/i386 ocaml-num
• ocaml-reins/mips64el (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/mips64el (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-reins/mips64el ocaml-num
• ocaml-reins/ppc64el (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/ppc64el (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-reins/ppc64el ocaml-num
• ocaml-reins/s390x (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/s390x (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-reins/s390x ocaml-num
• ocaml-sedlex/amd64 (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/amd64 (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-sedlex/amd64 ppxlib
    • Implicit dependency: ocaml-sedlex/amd64 js-of-ocaml
• ocaml-sedlex/arm64 (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/arm64 (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-sedlex/arm64 ppxlib
    • Implicit dependency: ocaml-sedlex/arm64 js-of-ocaml
• ocaml-sedlex/armel (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/armel (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-sedlex/armel ppxlib
    • Implicit dependency: ocaml-sedlex/armel js-of-ocaml
• ocaml-sedlex/armhf (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/armhf (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-sedlex/armhf ppxlib
    • Implicit dependency: ocaml-sedlex/armhf js-of-ocaml
• ocaml-sedlex/i386 (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/i386 (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-sedlex/i386 ppxlib
    • Implicit dependency: ocaml-sedlex/i386 js-of-ocaml
• ocaml-sedlex/mips64el (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/mips64el (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-sedlex/mips64el ppxlib
    • Implicit dependency: ocaml-sedlex/mips64el js-of-ocaml
• ocaml-sedlex/ppc64el (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/ppc64el (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-sedlex/ppc64el ppxlib
    • Implicit dependency: ocaml-sedlex/ppc64el js-of-ocaml
• ocaml-sedlex/s390x (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/s390x (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-sedlex/s390x ppxlib
    • Implicit dependency: ocaml-sedlex/s390x js-of-ocaml
• ocaml-uri/amd64 (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/amd64 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-uri/amd64 ocaml-angstrom
    • Implicit dependency: ocaml-uri/amd64 eliom
    • Implicit dependency: ocaml-uri/amd64 nurpawiki/amd64
    • Implicit dependency: ocaml-uri/amd64 ocaml-cohttp/amd64
    • Implicit dependency: ocaml-uri/amd64 ocaml-conduit
    • Implicit dependency: ocaml-uri/amd64 ocsigenserver/amd64
    • Implicit dependency: ocaml-uri/amd64 ocsipersist/amd64
• ocaml-uri/arm64 (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/arm64 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-uri/arm64 ocaml-angstrom
    • Implicit dependency: ocaml-uri/arm64 eliom
    • Implicit dependency: ocaml-uri/arm64 nurpawiki/arm64
    • Implicit dependency: ocaml-uri/arm64 ocaml-cohttp/arm64
    • Implicit dependency: ocaml-uri/arm64 ocaml-conduit
    • Implicit dependency: ocaml-uri/arm64 ocsigenserver/arm64
    • Implicit dependency: ocaml-uri/arm64 ocsipersist/arm64
• ocaml-uri/armel (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/armel (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-uri/armel ocaml-angstrom
    • Implicit dependency: ocaml-uri/armel eliom
    • Implicit dependency: ocaml-uri/armel nurpawiki/armel
    • Implicit dependency: ocaml-uri/armel ocaml-cohttp/armel
    • Implicit dependency: ocaml-uri/armel ocaml-conduit
    • Implicit dependency: ocaml-uri/armel ocsigenserver/armel
    • Implicit dependency: ocaml-uri/armel ocsipersist/armel
• ocaml-uri/armhf (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/armhf (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-uri/armhf ocaml-angstrom
    • Implicit dependency: ocaml-uri/armhf eliom
    • Implicit dependency: ocaml-uri/armhf nurpawiki/armhf
    • Implicit dependency: ocaml-uri/armhf ocaml-cohttp/armhf
    • Implicit dependency: ocaml-uri/armhf ocaml-conduit
    • Implicit dependency: ocaml-uri/armhf ocsigenserver/armhf
    • Implicit dependency: ocaml-uri/armhf ocsipersist/armhf
• ocaml-uri/i386 (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/i386 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-uri/i386 ocaml-angstrom
    • Implicit dependency: ocaml-uri/i386 eliom
    • Implicit dependency: ocaml-uri/i386 nurpawiki/i386
    • Implicit dependency: ocaml-uri/i386 ocaml-cohttp/i386
    • Implicit dependency: ocaml-uri/i386 ocaml-conduit
    • Implicit dependency: ocaml-uri/i386 ocsigenserver/i386
    • Implicit dependency: ocaml-uri/i386 ocsipersist/i386
• ocaml-uri/mips64el (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/mips64el (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-uri/mips64el ocaml-angstrom
    • Implicit dependency: ocaml-uri/mips64el eliom
    • Implicit dependency: ocaml-uri/mips64el nurpawiki/mips64el
    • Implicit dependency: ocaml-uri/mips64el ocaml-cohttp/mips64el
    • Implicit dependency: ocaml-uri/mips64el ocaml-conduit
    • Implicit dependency: ocaml-uri/mips64el ocsigenserver/mips64el
    • Implicit dependency: ocaml-uri/mips64el ocsipersist/mips64el
• ocaml-uri/ppc64el (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/ppc64el (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-uri/ppc64el ocaml-angstrom
    • Implicit dependency: ocaml-uri/ppc64el eliom
    • Implicit dependency: ocaml-uri/ppc64el nurpawiki/ppc64el
    • Implicit dependency: ocaml-uri/ppc64el ocaml-cohttp/ppc64el
    • Implicit dependency: ocaml-uri/ppc64el ocaml-conduit
    • Implicit dependency: ocaml-uri/ppc64el ocsigenserver/ppc64el
    • Implicit dependency: ocaml-uri/ppc64el ocsipersist/ppc64el
• ocaml-uri/s390x (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/s390x (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-uri/s390x ocaml-angstrom
    • Implicit dependency: ocaml-uri/s390x eliom
    • Implicit dependency: ocaml-uri/s390x nurpawiki/s390x
    • Implicit dependency: ocaml-uri/s390x ocaml-cohttp/s390x
    • Implicit dependency: ocaml-uri/s390x ocaml-conduit
    • Implicit dependency: ocaml-uri/s390x ocsigenserver/s390x
    • Implicit dependency: ocaml-uri/s390x ocsipersist/s390x
• ocaml-usb/amd64 (1.3.1-5 to 1.3.1-5)
  • Migration status for ocaml-usb/amd64 (1.3.1-5 to 1.3.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-usb/amd64 lwt/amd64
• ocaml-usb/arm64 (1.3.1-5 to 1.3.1-5)
  • Migration status for ocaml-usb/arm64 (1.3.1-5 to 1.3.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-usb/arm64 lwt/arm64
• ocaml-usb/armel (1.3.1-5 to 1.3.1-5)
  • Migration status for ocaml-usb/armel (1.3.1-5 to 1.3.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-usb/armel lwt/armel
• ocaml-usb/armhf (1.3.1-5 to 1.3.1-5)
  • Migration status for ocaml-usb/armhf (1.3.1-5 to 1.3.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-usb/armhf lwt/armhf
• ocaml-usb/i386 (1.3.1-5 to 1.3.1-5)
  • Migration status for ocaml-usb/i386 (1.3.1-5 to 1.3.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-usb/i386 lwt/i386
• ocaml-usb/mips64el (1.3.1-5 to 1.3.1-5)
  • Migration status for ocaml-usb/mips64el (1.3.1-5 to 1.3.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-usb/mips64el lwt/mips64el
• ocaml-usb/ppc64el (1.3.1-5 to 1.3.1-5)
  • Migration status for ocaml-usb/ppc64el (1.3.1-5 to 1.3.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-usb/ppc64el lwt/ppc64el
• ocaml-usb/s390x (1.3.1-5 to 1.3.1-5)
  • Migration status for ocaml-usb/s390x (1.3.1-5 to 1.3.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-usb/s390x lwt/s390x
• ocaml-visitors/amd64 (20210608-5 to 20210608-5)
  • Migration status for ocaml-visitors/amd64 (20210608-5 to 20210608-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-visitors/amd64 ppx-deriving/amd64
    • Depends: ocaml-visitors/amd64 ppxlib
    • Implicit dependency: ocaml-visitors/amd64 morbig/amd64
    • Implicit dependency: ocaml-visitors/amd64 morsmall/amd64
• ocaml-visitors/arm64 (20210608-5 to 20210608-5)
  • Migration status for ocaml-visitors/arm64 (20210608-5 to 20210608-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-visitors/arm64 ppx-deriving/arm64
    • Depends: ocaml-visitors/arm64 ppxlib
    • Implicit dependency: ocaml-visitors/arm64 morbig/arm64
    • Implicit dependency: ocaml-visitors/arm64 morsmall/arm64
• ocaml-visitors/armel (20210608-5 to 20210608-5)
  • Migration status for ocaml-visitors/armel (20210608-5 to 20210608-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-visitors/armel ppx-deriving/armel
    • Depends: ocaml-visitors/armel ppxlib
    • Implicit dependency: ocaml-visitors/armel morbig/armel
    • Implicit dependency: ocaml-visitors/armel morsmall/armel
• ocaml-visitors/armhf (20210608-5 to 20210608-5)
  • Migration status for ocaml-visitors/armhf (20210608-5 to 20210608-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-visitors/armhf ppx-deriving/armhf
    • Depends: ocaml-visitors/armhf ppxlib
    • Implicit dependency: ocaml-visitors/armhf morbig/armhf
    • Implicit dependency: ocaml-visitors/armhf morsmall/armhf
• ocaml-visitors/i386 (20210608-5 to 20210608-5)
  • Migration status for ocaml-visitors/i386 (20210608-5 to 20210608-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-visitors/i386 ppx-deriving/i386
    • Depends: ocaml-visitors/i386 ppxlib
    • Implicit dependency: ocaml-visitors/i386 morbig/i386
    • Implicit dependency: ocaml-visitors/i386 morsmall/i386
• ocaml-visitors/mips64el (20210608-5 to 20210608-5)
  • Migration status for ocaml-visitors/mips64el (20210608-5 to 20210608-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-visitors/mips64el ppx-deriving/mips64el
    • Depends: ocaml-visitors/mips64el ppxlib
    • Implicit dependency: ocaml-visitors/mips64el morbig/mips64el
    • Implicit dependency: ocaml-visitors/mips64el morsmall/mips64el
• ocaml-visitors/ppc64el (20210608-5 to 20210608-5)
  • Migration status for ocaml-visitors/ppc64el (20210608-5 to 20210608-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-visitors/ppc64el ppx-deriving/ppc64el
    • Depends: ocaml-visitors/ppc64el ppxlib
    • Implicit dependency: ocaml-visitors/ppc64el morbig/ppc64el
    • Implicit dependency: ocaml-visitors/ppc64el morsmall/ppc64el
• ocaml-visitors/s390x (20210608-5 to 20210608-5)
  • Migration status for ocaml-visitors/s390x (20210608-5 to 20210608-5): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-visitors/s390x ppx-deriving/s390x
    • Depends: ocaml-visitors/s390x ppxlib
    • Implicit dependency: ocaml-visitors/s390x morbig/s390x
    • Implicit dependency: ocaml-visitors/s390x morsmall/s390x
• ocaml-x509/amd64 (0.16.5-2 to 0.16.5-2)
  • Migration status for ocaml-x509/amd64 (0.16.5-2 to 0.16.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-x509/amd64 ocaml-cstruct/amd64
    • Depends: ocaml-x509/amd64 ocaml-logs/amd64
• ocaml-x509/arm64 (0.16.5-2 to 0.16.5-2)
  • Migration status for ocaml-x509/arm64 (0.16.5-2 to 0.16.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-x509/arm64 ocaml-cstruct/arm64
    • Depends: ocaml-x509/arm64 ocaml-logs/arm64
• ocaml-x509/armhf (0.16.5-2 to 0.16.5-2)
  • Migration status for ocaml-x509/armhf (0.16.5-2 to 0.16.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-x509/armhf ocaml-cstruct/armhf
    • Depends: ocaml-x509/armhf ocaml-logs/armhf
• ocaml-x509/i386 (0.16.5-2 to 0.16.5-2)
  • Migration status for ocaml-x509/i386 (0.16.5-2 to 0.16.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-x509/i386 ocaml-cstruct/i386
    • Depends: ocaml-x509/i386 ocaml-logs/i386
• ocaml-x509/ppc64el (0.16.5-2 to 0.16.5-2)
  • Migration status for ocaml-x509/ppc64el (0.16.5-2 to 0.16.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-x509/ppc64el ocaml-cstruct/ppc64el
    • Depends: ocaml-x509/ppc64el ocaml-logs/ppc64el
• ocaml-x509/s390x (0.16.5-2 to 0.16.5-2)
  • Migration status for ocaml-x509/s390x (0.16.5-2 to 0.16.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-x509/s390x ocaml-cstruct/s390x
    • Depends: ocaml-x509/s390x ocaml-logs/s390x
• ocplib-simplex/amd64 (0.5-4 to 0.5-4)
  • Migration status for ocplib-simplex/amd64 (0.5-4 to 0.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocplib-simplex/amd64 ocaml-logs/amd64
• ocplib-simplex/arm64 (0.5-4 to 0.5-4)
  • Migration status for ocplib-simplex/arm64 (0.5-4 to 0.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocplib-simplex/arm64 ocaml-logs/arm64
• ocplib-simplex/armhf (0.5-4 to 0.5-4)
  • Migration status for ocplib-simplex/armhf (0.5-4 to 0.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocplib-simplex/armhf ocaml-logs/armhf
• ocplib-simplex/i386 (0.5-4 to 0.5-4)
  • Migration status for ocplib-simplex/i386 (0.5-4 to 0.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocplib-simplex/i386 ocaml-logs/i386
• ocplib-simplex/ppc64el (0.5-4 to 0.5-4)
  • Migration status for ocplib-simplex/ppc64el (0.5-4 to 0.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocplib-simplex/ppc64el ocaml-logs/ppc64el
• ocplib-simplex/s390x (0.5-4 to 0.5-4)
  • Migration status for ocplib-simplex/s390x (0.5-4 to 0.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: ocplib-simplex/s390x ocaml-logs/s390x
• ocsigenserver/amd64 (5.1.2-1 to 5.1.2-1)
  • Migration status for ocsigenserver/amd64 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/amd64 lwt/amd64
    • Depends: ocsigenserver/amd64 ocaml-angstrom
    • Depends: ocsigenserver/amd64 ocaml-cohttp/amd64
    • Depends: ocsigenserver/amd64 ocaml-conduit
    • Depends: ocsigenserver/amd64 ocaml-logs/amd64
    • Depends: ocsigenserver/amd64 ocaml-uri/amd64
    • Depends: ocsigenserver/amd64 ppx-sexp-conv/amd64
    • Depends: ocsigenserver/amd64 sexplib310/amd64
    • Implicit dependency: ocsigenserver/amd64 eliom
    • Implicit dependency: ocsigenserver/amd64 nurpawiki/amd64
    • Implicit dependency: ocsigenserver/amd64 ocsipersist/amd64
• ocsigenserver/arm64 (5.1.2-1 to 5.1.2-1)
  • Migration status for ocsigenserver/arm64 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/arm64 lwt/arm64
    • Depends: ocsigenserver/arm64 ocaml-angstrom
    • Depends: ocsigenserver/arm64 ocaml-cohttp/arm64
    • Depends: ocsigenserver/arm64 ocaml-conduit
    • Depends: ocsigenserver/arm64 ocaml-logs/arm64
    • Depends: ocsigenserver/arm64 ocaml-uri/arm64
    • Depends: ocsigenserver/arm64 ppx-sexp-conv/arm64
    • Depends: ocsigenserver/arm64 sexplib310/arm64
    • Implicit dependency: ocsigenserver/arm64 eliom
    • Implicit dependency: ocsigenserver/arm64 nurpawiki/arm64
    • Implicit dependency: ocsigenserver/arm64 ocsipersist/arm64
• ocsigenserver/armel (5.1.2-1 to 5.1.2-1)
  • Migration status for ocsigenserver/armel (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/armel lwt/armel
    • Depends: ocsigenserver/armel ocaml-angstrom
    • Depends: ocsigenserver/armel ocaml-uri/armel
    • Depends: ocsigenserver/armel ppx-sexp-conv/armel
    • Depends: ocsigenserver/armel sexplib310/armel
• ocsigenserver/armhf (5.1.2-1 to 5.1.2-1)
  • Migration status for ocsigenserver/armhf (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/armhf lwt/armhf
    • Depends: ocsigenserver/armhf ocaml-angstrom
    • Depends: ocsigenserver/armhf ocaml-cohttp/armhf
    • Depends: ocsigenserver/armhf ocaml-conduit
    • Depends: ocsigenserver/armhf ocaml-logs/armhf
    • Depends: ocsigenserver/armhf ocaml-uri/armhf
    • Depends: ocsigenserver/armhf ppx-sexp-conv/armhf
    • Depends: ocsigenserver/armhf sexplib310/armhf
    • Implicit dependency: ocsigenserver/armhf eliom
    • Implicit dependency: ocsigenserver/armhf nurpawiki/armhf
    • Implicit dependency: ocsigenserver/armhf ocsipersist/armhf
• ocsigenserver/i386 (5.1.2-1 to 5.1.2-1)
  • Migration status for ocsigenserver/i386 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/i386 lwt/i386
    • Depends: ocsigenserver/i386 ocaml-angstrom
    • Depends: ocsigenserver/i386 ocaml-cohttp/i386
    • Depends: ocsigenserver/i386 ocaml-conduit
    • Depends: ocsigenserver/i386 ocaml-logs/i386
    • Depends: ocsigenserver/i386 ocaml-uri/i386
    • Depends: ocsigenserver/i386 ppx-sexp-conv/i386
    • Depends: ocsigenserver/i386 sexplib310/i386
    • Implicit dependency: ocsigenserver/i386 eliom
    • Implicit dependency: ocsigenserver/i386 nurpawiki/i386
    • Implicit dependency: ocsigenserver/i386 ocsipersist/i386
• ocsigenserver/mips64el (5.1.2-1 to 5.1.2-1)
  • Migration status for ocsigenserver/mips64el (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/mips64el lwt/mips64el
    • Depends: ocsigenserver/mips64el ocaml-angstrom
    • Depends: ocsigenserver/mips64el ocaml-uri/mips64el
    • Depends: ocsigenserver/mips64el ppx-sexp-conv/mips64el
    • Depends: ocsigenserver/mips64el sexplib310/mips64el
• ocsigenserver/ppc64el (5.1.2-1 to 5.1.2-1)
  • Migration status for ocsigenserver/ppc64el (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/ppc64el lwt/ppc64el
    • Depends: ocsigenserver/ppc64el ocaml-angstrom
    • Depends: ocsigenserver/ppc64el ocaml-cohttp/ppc64el
    • Depends: ocsigenserver/ppc64el ocaml-conduit
    • Depends: ocsigenserver/ppc64el ocaml-logs/ppc64el
    • Depends: ocsigenserver/ppc64el ocaml-uri/ppc64el
    • Depends: ocsigenserver/ppc64el ppx-sexp-conv/ppc64el
    • Depends: ocsigenserver/ppc64el sexplib310/ppc64el
    • Implicit dependency: ocsigenserver/ppc64el eliom
    • Implicit dependency: ocsigenserver/ppc64el nurpawiki/ppc64el
    • Implicit dependency: ocsigenserver/ppc64el ocsipersist/ppc64el
• ocsigenserver/s390x (5.1.2-1 to 5.1.2-1)
  • Migration status for ocsigenserver/s390x (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/s390x lwt/s390x
    • Depends: ocsigenserver/s390x ocaml-angstrom
    • Depends: ocsigenserver/s390x ocaml-cohttp/s390x
    • Depends: ocsigenserver/s390x ocaml-conduit
    • Depends: ocsigenserver/s390x ocaml-logs/s390x
    • Depends: ocsigenserver/s390x ocaml-uri/s390x
    • Depends: ocsigenserver/s390x ppx-sexp-conv/s390x
    • Depends: ocsigenserver/s390x sexplib310/s390x
    • Implicit dependency: ocsigenserver/s390x eliom
    • Implicit dependency: ocsigenserver/s390x nurpawiki/s390x
    • Implicit dependency: ocsigenserver/s390x ocsipersist/s390x
• ocsipersist/amd64 (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/amd64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocsipersist/amd64 lwt/amd64
    • Depends: ocsipersist/amd64 ocaml-angstrom
    • Depends: ocsipersist/amd64 ocaml-cohttp/amd64
    • Depends: ocsipersist/amd64 ocaml-uri/amd64
    • Depends: ocsipersist/amd64 ocsigenserver/amd64
    • Depends: ocsipersist/amd64 pgocaml/amd64
    • Depends: ocsipersist/amd64 ppx-deriving/amd64
• ocsipersist/arm64 (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/arm64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocsipersist/arm64 lwt/arm64
    • Depends: ocsipersist/arm64 ocaml-angstrom
    • Depends: ocsipersist/arm64 ocaml-cohttp/arm64
    • Depends: ocsipersist/arm64 ocaml-uri/arm64
    • Depends: ocsipersist/arm64 ocsigenserver/arm64
    • Depends: ocsipersist/arm64 pgocaml/arm64
    • Depends: ocsipersist/arm64 ppx-deriving/arm64
• ocsipersist/armel (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/armel (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocsipersist/armel lwt/armel
    • Depends: ocsipersist/armel ocaml-angstrom
    • Depends: ocsipersist/armel ocaml-uri/armel
    • Depends: ocsipersist/armel pgocaml/armel
    • Depends: ocsipersist/armel ppx-deriving/armel
• ocsipersist/armhf (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/armhf (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocsipersist/armhf lwt/armhf
    • Depends: ocsipersist/armhf ocaml-angstrom
    • Depends: ocsipersist/armhf ocaml-cohttp/armhf
    • Depends: ocsipersist/armhf ocaml-uri/armhf
    • Depends: ocsipersist/armhf ocsigenserver/armhf
    • Depends: ocsipersist/armhf pgocaml/armhf
    • Depends: ocsipersist/armhf ppx-deriving/armhf
• ocsipersist/i386 (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/i386 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocsipersist/i386 lwt/i386
    • Depends: ocsipersist/i386 ocaml-angstrom
    • Depends: ocsipersist/i386 ocaml-cohttp/i386
    • Depends: ocsipersist/i386 ocaml-uri/i386
    • Depends: ocsipersist/i386 ocsigenserver/i386
    • Depends: ocsipersist/i386 pgocaml/i386
    • Depends: ocsipersist/i386 ppx-deriving/i386
• ocsipersist/mips64el (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/mips64el (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocsipersist/mips64el lwt/mips64el
    • Depends: ocsipersist/mips64el ocaml-angstrom
    • Depends: ocsipersist/mips64el ocaml-uri/mips64el
    • Depends: ocsipersist/mips64el pgocaml/mips64el
    • Depends: ocsipersist/mips64el ppx-deriving/mips64el
• ocsipersist/ppc64el (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/ppc64el (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocsipersist/ppc64el lwt/ppc64el
    • Depends: ocsipersist/ppc64el ocaml-angstrom
    • Depends: ocsipersist/ppc64el ocaml-cohttp/ppc64el
    • Depends: ocsipersist/ppc64el ocaml-uri/ppc64el
    • Depends: ocsipersist/ppc64el ocsigenserver/ppc64el
    • Depends: ocsipersist/ppc64el pgocaml/ppc64el
    • Depends: ocsipersist/ppc64el ppx-deriving/ppc64el
• ocsipersist/s390x (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/s390x (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocsipersist/s390x lwt/s390x
    • Depends: ocsipersist/s390x ocaml-angstrom
    • Depends: ocsipersist/s390x ocaml-cohttp/s390x
    • Depends: ocsipersist/s390x ocaml-uri/s390x
    • Depends: ocsipersist/s390x ocsigenserver/s390x
    • Depends: ocsipersist/s390x pgocaml/s390x
    • Depends: ocsipersist/s390x ppx-deriving/s390x
• ocurl/amd64 (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/amd64 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocurl/amd64 lwt/amd64
• ocurl/arm64 (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/arm64 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocurl/arm64 lwt/arm64
• ocurl/armel (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/armel (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocurl/armel lwt/armel
• ocurl/armhf (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/armhf (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocurl/armhf lwt/armhf
• ocurl/i386 (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/i386 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocurl/i386 lwt/i386
• ocurl/mips64el (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/mips64el (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocurl/mips64el lwt/mips64el
• ocurl/ppc64el (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/ppc64el (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocurl/ppc64el lwt/ppc64el
• ocurl/s390x (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/s390x (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: ocurl/s390x lwt/s390x
• odil/amd64 (0.12.2-4 to 0.12.2-4)
  • Migration status for odil/amd64 (0.12.2-4 to 0.12.2-4): Will attempt migration (Any information below is purely informational)
• odil/ppc64el (0.12.2-4 to 0.12.2-4)
  • Migration status for odil/ppc64el (0.12.2-4 to 0.12.2-4): Will attempt migration (Any information below is purely informational)
• odil/s390x (0.12.2-4 to 0.12.2-4)
  • Migration status for odil/s390x (0.12.2-4 to 0.12.2-4): Will attempt migration (Any information below is purely informational)
• oflib/amd64 (0git20070620-9 to 0git20070620-9)
  • Migration status for oflib/amd64 (0git20070620-9 to 0git20070620-9): Will attempt migration (Any information below is purely informational)
• oflib/arm64 (0git20070620-9 to 0git20070620-9)
  • Migration status for oflib/arm64 (0git20070620-9 to 0git20070620-9): Will attempt migration (Any information below is purely informational)
• oflib/armel (0git20070620-9 to 0git20070620-9)
  • Migration status for oflib/armel (0git20070620-9 to 0git20070620-9): Will attempt migration (Any information below is purely informational)
• oflib/armhf (0git20070620-9 to 0git20070620-9)
  • Migration status for oflib/armhf (0git20070620-9 to 0git20070620-9): Will attempt migration (Any information below is purely informational)
• oflib/i386 (0git20070620-9 to 0git20070620-9)
  • Migration status for oflib/i386 (0git20070620-9 to 0git20070620-9): Will attempt migration (Any information below is purely informational)
• oflib/mips64el (0git20070620-9 to 0git20070620-9)
  • Migration status for oflib/mips64el (0git20070620-9 to 0git20070620-9): Will attempt migration (Any information below is purely informational)
• oflib/ppc64el (0git20070620-9 to 0git20070620-9)
  • Migration status for oflib/ppc64el (0git20070620-9 to 0git20070620-9): Will attempt migration (Any information below is purely informational)
• ois/amd64 (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7)
  • Migration status for ois/amd64 (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7): Will attempt migration (Any information below is purely informational)
• ois/arm64 (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7)
  • Migration status for ois/arm64 (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7): Will attempt migration (Any information below is purely informational)
• ois/armel (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7)
  • Migration status for ois/armel (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7): Will attempt migration (Any information below is purely informational)
• ois/armhf (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7)
  • Migration status for ois/armhf (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7): Will attempt migration (Any information below is purely informational)
• ois/i386 (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7)
  • Migration status for ois/i386 (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7): Will attempt migration (Any information below is purely informational)
• ois/mips64el (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7)
  • Migration status for ois/mips64el (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7): Will attempt migration (Any information below is purely informational)
• ois/ppc64el (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7)
  • Migration status for ois/ppc64el (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7): Will attempt migration (Any information below is purely informational)
• ola/amd64 (0.10.9.nojsmin-4 to 0.10.9.nojsmin-4)
  • Migration status for ola/amd64 (0.10.9.nojsmin-4 to 0.10.9.nojsmin-4): Will attempt migration (Any information below is purely informational)
• ola/arm64 (0.10.9.nojsmin-4 to 0.10.9.nojsmin-4)
  • Migration status for ola/arm64 (0.10.9.nojsmin-4 to 0.10.9.nojsmin-4): Will attempt migration (Any information below is purely informational)
• ola/i386 (0.10.9.nojsmin-4 to 0.10.9.nojsmin-4)
  • Migration status for ola/i386 (0.10.9.nojsmin-4 to 0.10.9.nojsmin-4): Will attempt migration (Any information below is purely informational)
• ola/ppc64el (0.10.9.nojsmin-4 to 0.10.9.nojsmin-4)
  • Migration status for ola/ppc64el (0.10.9.nojsmin-4 to 0.10.9.nojsmin-4): Will attempt migration (Any information below is purely informational)
• ompl/amd64 (1.5.2+ds1-1 to 1.5.2+ds1-1)
  • Migration status for ompl/amd64 (1.5.2+ds1-1 to 1.5.2+ds1-1): Will attempt migration (Any information below is purely informational)
• ompl/arm64 (1.5.2+ds1-1 to 1.5.2+ds1-1)
  • Migration status for ompl/arm64 (1.5.2+ds1-1 to 1.5.2+ds1-1): Will attempt migration (Any information below is purely informational)
• ompl/i386 (1.5.2+ds1-1 to 1.5.2+ds1-1)
  • Migration status for ompl/i386 (1.5.2+ds1-1 to 1.5.2+ds1-1): Will attempt migration (Any information below is purely informational)
• ompl/ppc64el (1.5.2+ds1-1 to 1.5.2+ds1-1)
  • Migration status for ompl/ppc64el (1.5.2+ds1-1 to 1.5.2+ds1-1): Will attempt migration (Any information below is purely informational)
• onedrive/amd64 (2.4.25-1 to 2.4.25-1)
  • Migration status for onedrive/amd64 (2.4.25-1 to 2.4.25-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: onedrive/amd64 ldc (not considered)
    • Invalidated by dependency
• onedrive/arm64 (2.4.25-1 to 2.4.25-1)
  • Migration status for onedrive/arm64 (2.4.25-1 to 2.4.25-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: onedrive/arm64 ldc (not considered)
    • Invalidated by dependency
• onedrive/armhf (2.4.25-1 to 2.4.25-1)
  • Migration status for onedrive/armhf (2.4.25-1 to 2.4.25-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: onedrive/armhf ldc (not considered)
    • Invalidated by dependency
• onedrive/i386 (2.4.25-1 to 2.4.25-1)
  • Migration status for onedrive/i386 (2.4.25-1 to 2.4.25-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: onedrive/i386 ldc (not considered)
    • Invalidated by dependency
• opari/amd64 (1.1+dfsg-9 to 1.1+dfsg-9)
  • Migration status for opari/amd64 (1.1+dfsg-9 to 1.1+dfsg-9): Will attempt migration (Any information below is purely informational)
• opari/arm64 (1.1+dfsg-9 to 1.1+dfsg-9)
  • Migration status for opari/arm64 (1.1+dfsg-9 to 1.1+dfsg-9): Will attempt migration (Any information below is purely informational)
• opari/armel (1.1+dfsg-9 to 1.1+dfsg-9)
  • Migration status for opari/armel (1.1+dfsg-9 to 1.1+dfsg-9): Will attempt migration (Any information below is purely informational)
• opari/armhf (1.1+dfsg-9 to 1.1+dfsg-9)
  • Migration status for opari/armhf (1.1+dfsg-9 to 1.1+dfsg-9): Will attempt migration (Any information below is purely informational)
• opari/i386 (1.1+dfsg-9 to 1.1+dfsg-9)
  • Migration status for opari/i386 (1.1+dfsg-9 to 1.1+dfsg-9): Will attempt migration (Any information below is purely informational)
• opari/mips64el (1.1+dfsg-9 to 1.1+dfsg-9)
  • Migration status for opari/mips64el (1.1+dfsg-9 to 1.1+dfsg-9): Will attempt migration (Any information below is purely informational)
• opari/ppc64el (1.1+dfsg-9 to 1.1+dfsg-9)
  • Migration status for opari/ppc64el (1.1+dfsg-9 to 1.1+dfsg-9): Will attempt migration (Any information below is purely informational)
• open-gram/amd64 (0.1.22+20170109-2 to 0.1.22+20170109-2)
  • Migration status for open-gram/amd64 (0.1.22+20170109-2 to 0.1.22+20170109-2): Will attempt migration (Any information below is purely informational)
• open-gram/arm64 (0.1.22+20170109-2 to 0.1.22+20170109-2)
  • Migration status for open-gram/arm64 (0.1.22+20170109-2 to 0.1.22+20170109-2): Will attempt migration (Any information below is purely informational)
• open-gram/armel (0.1.22+20170109-2 to 0.1.22+20170109-2)
  • Migration status for open-gram/armel (0.1.22+20170109-2 to 0.1.22+20170109-2): Will attempt migration (Any information below is purely informational)
• open-gram/armhf (0.1.22+20170109-2 to 0.1.22+20170109-2)
  • Migration status for open-gram/armhf (0.1.22+20170109-2 to 0.1.22+20170109-2): Will attempt migration (Any information below is purely informational)
• open-gram/i386 (0.1.22+20170109-2 to 0.1.22+20170109-2)
  • Migration status for open-gram/i386 (0.1.22+20170109-2 to 0.1.22+20170109-2): Will attempt migration (Any information below is purely informational)
• open-gram/mips64el (0.1.22+20170109-2 to 0.1.22+20170109-2)
  • Migration status for open-gram/mips64el (0.1.22+20170109-2 to 0.1.22+20170109-2): Will attempt migration (Any information below is purely informational)
• open-gram/ppc64el (0.1.22+20170109-2 to 0.1.22+20170109-2)
  • Migration status for open-gram/ppc64el (0.1.22+20170109-2 to 0.1.22+20170109-2): Will attempt migration (Any information below is purely informational)
• openal-soft/amd64 (1:1.23.1-4 to 1:1.23.1-4)
  • Migration status for openal-soft/amd64 (1:1.23.1-4 to 1:1.23.1-4): Will attempt migration (Any information below is purely informational)
• openal-soft/arm64 (1:1.23.1-4 to 1:1.23.1-4)
  • Migration status for openal-soft/arm64 (1:1.23.1-4 to 1:1.23.1-4): Will attempt migration (Any information below is purely informational)
• openal-soft/armel (1:1.23.1-4 to 1:1.23.1-4)
  • Migration status for openal-soft/armel (1:1.23.1-4 to 1:1.23.1-4): Will attempt migration (Any information below is purely informational)
• openal-soft/armhf (1:1.23.1-4 to 1:1.23.1-4)
  • Migration status for openal-soft/armhf (1:1.23.1-4 to 1:1.23.1-4): Will attempt migration (Any information below is purely informational)
• openal-soft/i386 (1:1.23.1-4 to 1:1.23.1-4)
  • Migration status for openal-soft/i386 (1:1.23.1-4 to 1:1.23.1-4): Will attempt migration (Any information below is purely informational)
• openal-soft/mips64el (1:1.23.1-4 to 1:1.23.1-4)
  • Migration status for openal-soft/mips64el (1:1.23.1-4 to 1:1.23.1-4): Will attempt migration (Any information below is purely informational)
• openal-soft/ppc64el (1:1.23.1-4 to 1:1.23.1-4)
  • Migration status for openal-soft/ppc64el (1:1.23.1-4 to 1:1.23.1-4): Will attempt migration (Any information below is purely informational)
• opencamlib/amd64 (2023.01.11-4 to 2023.01.11-4)
  • Migration status for opencamlib/amd64 (2023.01.11-4 to 2023.01.11-4): Will attempt migration (Any information below is purely informational)
• opencamlib/arm64 (2023.01.11-4 to 2023.01.11-4)
  • Migration status for opencamlib/arm64 (2023.01.11-4 to 2023.01.11-4): Will attempt migration (Any information below is purely informational)
• opencamlib/armel (2023.01.11-4 to 2023.01.11-4)
  • Migration status for opencamlib/armel (2023.01.11-4 to 2023.01.11-4): Will attempt migration (Any information below is purely informational)
• opencamlib/armhf (2023.01.11-4 to 2023.01.11-4)
  • Migration status for opencamlib/armhf (2023.01.11-4 to 2023.01.11-4): Will attempt migration (Any information below is purely informational)
• opencamlib/i386 (2023.01.11-4 to 2023.01.11-4)
  • Migration status for opencamlib/i386 (2023.01.11-4 to 2023.01.11-4): Will attempt migration (Any information below is purely informational)
• opencamlib/mips64el (2023.01.11-4 to 2023.01.11-4)
  • Migration status for opencamlib/mips64el (2023.01.11-4 to 2023.01.11-4): Will attempt migration (Any information below is purely informational)
• opencamlib/ppc64el (2023.01.11-4 to 2023.01.11-4)
  • Migration status for opencamlib/ppc64el (2023.01.11-4 to 2023.01.11-4): Will attempt migration (Any information below is purely informational)
• opencascade/amd64 (7.6.3+dfsg1-7 to 7.6.3+dfsg1-7)
  • Migration status for opencascade/amd64 (7.6.3+dfsg1-7 to 7.6.3+dfsg1-7): Will attempt migration (Any information below is purely informational)
• opencascade/arm64 (7.6.3+dfsg1-7 to 7.6.3+dfsg1-7)
  • Migration status for opencascade/arm64 (7.6.3+dfsg1-7 to 7.6.3+dfsg1-7): Will attempt migration (Any information below is purely informational)
• opencascade/ppc64el (7.6.3+dfsg1-7 to 7.6.3+dfsg1-7)
  • Migration status for opencascade/ppc64el (7.6.3+dfsg1-7 to 7.6.3+dfsg1-7): Will attempt migration (Any information below is purely informational)
• opencascade/s390x (7.6.3+dfsg1-7 to 7.6.3+dfsg1-7)
  • Migration status for opencascade/s390x (7.6.3+dfsg1-7 to 7.6.3+dfsg1-7): Will attempt migration (Any information below is purely informational)
• opencc/amd64 (1.1.7+ds1-1 to 1.1.7+ds1-1)
  • Migration status for opencc/amd64 (1.1.7+ds1-1 to 1.1.7+ds1-1): Will attempt migration (Any information below is purely informational)
• opencc/arm64 (1.1.7+ds1-1 to 1.1.7+ds1-1)
  • Migration status for opencc/arm64 (1.1.7+ds1-1 to 1.1.7+ds1-1): Will attempt migration (Any information below is purely informational)
• opencc/armel (1.1.7+ds1-1 to 1.1.7+ds1-1)
  • Migration status for opencc/armel (1.1.7+ds1-1 to 1.1.7+ds1-1): Will attempt migration (Any information below is purely informational)
• opencc/armhf (1.1.7+ds1-1 to 1.1.7+ds1-1)
  • Migration status for opencc/armhf (1.1.7+ds1-1 to 1.1.7+ds1-1): Will attempt migration (Any information below is purely informational)
• opencc/i386 (1.1.7+ds1-1 to 1.1.7+ds1-1)
  • Migration status for opencc/i386 (1.1.7+ds1-1 to 1.1.7+ds1-1): Will attempt migration (Any information below is purely informational)
• opencc/mips64el (1.1.7+ds1-1 to 1.1.7+ds1-1)
  • Migration status for opencc/mips64el (1.1.7+ds1-1 to 1.1.7+ds1-1): Will attempt migration (Any information below is purely informational)
• opencc/ppc64el (1.1.7+ds1-1 to 1.1.7+ds1-1)
  • Migration status for opencc/ppc64el (1.1.7+ds1-1 to 1.1.7+ds1-1): Will attempt migration (Any information below is purely informational)
• opencl-clang-14/amd64 (14.0.0-4 to 14.0.0-4)
  • Migration status for opencl-clang-14/amd64 (14.0.0-4 to 14.0.0-4): Will attempt migration (Any information below is purely informational)
• opencl-clang-14/arm64 (14.0.0-4 to 14.0.0-4)
  • Migration status for opencl-clang-14/arm64 (14.0.0-4 to 14.0.0-4): Will attempt migration (Any information below is purely informational)
• opencl-clang-14/armel (14.0.0-4 to 14.0.0-4)
  • Migration status for opencl-clang-14/armel (14.0.0-4 to 14.0.0-4): Will attempt migration (Any information below is purely informational)
• opencl-clang-14/armhf (14.0.0-4 to 14.0.0-4)
  • Migration status for opencl-clang-14/armhf (14.0.0-4 to 14.0.0-4): Will attempt migration (Any information below is purely informational)
• opencl-clang-14/i386 (14.0.0-4 to 14.0.0-4)
  • Migration status for opencl-clang-14/i386 (14.0.0-4 to 14.0.0-4): Will attempt migration (Any information below is purely informational)
• opencl-clang-14/mips64el (14.0.0-4 to 14.0.0-4)
  • Migration status for opencl-clang-14/mips64el (14.0.0-4 to 14.0.0-4): Will attempt migration (Any information below is purely informational)
• opencl-clang-14/ppc64el (14.0.0-4 to 14.0.0-4)
  • Migration status for opencl-clang-14/ppc64el (14.0.0-4 to 14.0.0-4): Will attempt migration (Any information below is purely informational)
• opencl-clang-15/amd64 (15.0.0-3 to 15.0.0-3)
  • Migration status for opencl-clang-15/amd64 (15.0.0-3 to 15.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-15/arm64 (15.0.0-3 to 15.0.0-3)
  • Migration status for opencl-clang-15/arm64 (15.0.0-3 to 15.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-15/armel (15.0.0-3 to 15.0.0-3)
  • Migration status for opencl-clang-15/armel (15.0.0-3 to 15.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-15/armhf (15.0.0-3 to 15.0.0-3)
  • Migration status for opencl-clang-15/armhf (15.0.0-3 to 15.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-15/i386 (15.0.0-3 to 15.0.0-3)
  • Migration status for opencl-clang-15/i386 (15.0.0-3 to 15.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-15/mips64el (15.0.0-3 to 15.0.0-3)
  • Migration status for opencl-clang-15/mips64el (15.0.0-3 to 15.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-15/ppc64el (15.0.0-3 to 15.0.0-3)
  • Migration status for opencl-clang-15/ppc64el (15.0.0-3 to 15.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-16/amd64 (16.0.0-3 to 16.0.0-3)
  • Migration status for opencl-clang-16/amd64 (16.0.0-3 to 16.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-16/arm64 (16.0.0-3 to 16.0.0-3)
  • Migration status for opencl-clang-16/arm64 (16.0.0-3 to 16.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-16/armel (16.0.0-3 to 16.0.0-3)
  • Migration status for opencl-clang-16/armel (16.0.0-3 to 16.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-16/armhf (16.0.0-3 to 16.0.0-3)
  • Migration status for opencl-clang-16/armhf (16.0.0-3 to 16.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-16/i386 (16.0.0-3 to 16.0.0-3)
  • Migration status for opencl-clang-16/i386 (16.0.0-3 to 16.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-16/mips64el (16.0.0-3 to 16.0.0-3)
  • Migration status for opencl-clang-16/mips64el (16.0.0-3 to 16.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-16/ppc64el (16.0.0-3 to 16.0.0-3)
  • Migration status for opencl-clang-16/ppc64el (16.0.0-3 to 16.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-17/amd64 (17.0.0-2 to 17.0.0-2)
  • Migration status for opencl-clang-17/amd64 (17.0.0-2 to 17.0.0-2): Will attempt migration (Any information below is purely informational)
• opencl-clang-17/arm64 (17.0.0-2 to 17.0.0-2)
  • Migration status for opencl-clang-17/arm64 (17.0.0-2 to 17.0.0-2): Will attempt migration (Any information below is purely informational)
• opencl-clang-17/armel (17.0.0-2 to 17.0.0-2)
  • Migration status for opencl-clang-17/armel (17.0.0-2 to 17.0.0-2): Will attempt migration (Any information below is purely informational)
• opencl-clang-17/armhf (17.0.0-2 to 17.0.0-2)
  • Migration status for opencl-clang-17/armhf (17.0.0-2 to 17.0.0-2): Will attempt migration (Any information below is purely informational)
• opencl-clang-17/i386 (17.0.0-2 to 17.0.0-2)
  • Migration status for opencl-clang-17/i386 (17.0.0-2 to 17.0.0-2): Will attempt migration (Any information below is purely informational)
• opencl-clang-17/ppc64el (17.0.0-2 to 17.0.0-2)
  • Migration status for opencl-clang-17/ppc64el (17.0.0-2 to 17.0.0-2): Will attempt migration (Any information below is purely informational)
• opencolorio/amd64 (2.1.3+dfsg-1 to 2.1.3+dfsg-1)
  • Migration status for opencolorio/amd64 (2.1.3+dfsg-1 to 2.1.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• opencolorio/arm64 (2.1.3+dfsg-1 to 2.1.3+dfsg-1)
  • Migration status for opencolorio/arm64 (2.1.3+dfsg-1 to 2.1.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• opencolorio/armel (2.1.3+dfsg-1 to 2.1.3+dfsg-1)
  • Migration status for opencolorio/armel (2.1.3+dfsg-1 to 2.1.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• opencolorio/armhf (2.1.3+dfsg-1 to 2.1.3+dfsg-1)
  • Migration status for opencolorio/armhf (2.1.3+dfsg-1 to 2.1.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• opencolorio/i386 (2.1.3+dfsg-1 to 2.1.3+dfsg-1)
  • Migration status for opencolorio/i386 (2.1.3+dfsg-1 to 2.1.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• opencolorio/ppc64el (2.1.3+dfsg-1 to 2.1.3+dfsg-1)
  • Migration status for opencolorio/ppc64el (2.1.3+dfsg-1 to 2.1.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• opencore-amr/amd64 (0.1.6-1 to 0.1.6-1)
  • Migration status for opencore-amr/amd64 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• opencore-amr/arm64 (0.1.6-1 to 0.1.6-1)
  • Migration status for opencore-amr/arm64 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• opencore-amr/armel (0.1.6-1 to 0.1.6-1)
  • Migration status for opencore-amr/armel (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• opencore-amr/armhf (0.1.6-1 to 0.1.6-1)
  • Migration status for opencore-amr/armhf (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• opencore-amr/i386 (0.1.6-1 to 0.1.6-1)
  • Migration status for opencore-amr/i386 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• opencore-amr/mips64el (0.1.6-1 to 0.1.6-1)
  • Migration status for opencore-amr/mips64el (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• opencore-amr/ppc64el (0.1.6-1 to 0.1.6-1)
  • Migration status for opencore-amr/ppc64el (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• openctm/amd64 (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3)
  • Migration status for openctm/amd64 (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• openctm/arm64 (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3)
  • Migration status for openctm/arm64 (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• openctm/armel (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3)
  • Migration status for openctm/armel (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• openctm/armhf (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3)
  • Migration status for openctm/armhf (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• openctm/i386 (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3)
  • Migration status for openctm/i386 (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• openctm/mips64el (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3)
  • Migration status for openctm/mips64el (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• openctm/ppc64el (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3)
  • Migration status for openctm/ppc64el (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• opendkim/amd64 (2.11.0~beta2-9 to 2.11.0~beta2-9)
  • Migration status for opendkim/amd64 (2.11.0~beta2-9 to 2.11.0~beta2-9): Will attempt migration (Any information below is purely informational)
• opendkim/arm64 (2.11.0~beta2-9 to 2.11.0~beta2-9)
  • Migration status for opendkim/arm64 (2.11.0~beta2-9 to 2.11.0~beta2-9): Will attempt migration (Any information below is purely informational)
• opendkim/armel (2.11.0~beta2-9 to 2.11.0~beta2-9)
  • Migration status for opendkim/armel (2.11.0~beta2-9 to 2.11.0~beta2-9): Will attempt migration (Any information below is purely informational)
• opendkim/armhf (2.11.0~beta2-9 to 2.11.0~beta2-9)
  • Migration status for opendkim/armhf (2.11.0~beta2-9 to 2.11.0~beta2-9): Will attempt migration (Any information below is purely informational)
• opendkim/i386 (2.11.0~beta2-9 to 2.11.0~beta2-9)
  • Migration status for opendkim/i386 (2.11.0~beta2-9 to 2.11.0~beta2-9): Will attempt migration (Any information below is purely informational)
• opendkim/mips64el (2.11.0~beta2-9 to 2.11.0~beta2-9)
  • Migration status for opendkim/mips64el (2.11.0~beta2-9 to 2.11.0~beta2-9): Will attempt migration (Any information below is purely informational)
• opendkim/ppc64el (2.11.0~beta2-9 to 2.11.0~beta2-9)
  • Migration status for opendkim/ppc64el (2.11.0~beta2-9 to 2.11.0~beta2-9): Will attempt migration (Any information below is purely informational)
• opendmarc/amd64 (1.4.2-4 to 1.4.2-4)
  • Migration status for opendmarc/amd64 (1.4.2-4 to 1.4.2-4): Will attempt migration (Any information below is purely informational)
• opendmarc/arm64 (1.4.2-4 to 1.4.2-4)
  • Migration status for opendmarc/arm64 (1.4.2-4 to 1.4.2-4): Will attempt migration (Any information below is purely informational)
• opendmarc/armel (1.4.2-4 to 1.4.2-4)
  • Migration status for opendmarc/armel (1.4.2-4 to 1.4.2-4): Will attempt migration (Any information below is purely informational)
• opendmarc/armhf (1.4.2-4 to 1.4.2-4)
  • Migration status for opendmarc/armhf (1.4.2-4 to 1.4.2-4): Will attempt migration (Any information below is purely informational)
• opendmarc/i386 (1.4.2-4 to 1.4.2-4)
  • Migration status for opendmarc/i386 (1.4.2-4 to 1.4.2-4): Will attempt migration (Any information below is purely informational)
• opendmarc/mips64el (1.4.2-4 to 1.4.2-4)
  • Migration status for opendmarc/mips64el (1.4.2-4 to 1.4.2-4): Will attempt migration (Any information below is purely informational)
• opendmarc/ppc64el (1.4.2-4 to 1.4.2-4)
  • Migration status for opendmarc/ppc64el (1.4.2-4 to 1.4.2-4): Will attempt migration (Any information below is purely informational)
• openexr/amd64 (3.1.5-5.1 to 3.1.5-5.1)
  • Migration status for openexr/amd64 (3.1.5-5.1 to 3.1.5-5.1): Will attempt migration (Any information below is purely informational)
• openexr/arm64 (3.1.5-5.1 to 3.1.5-5.1)
  • Migration status for openexr/arm64 (3.1.5-5.1 to 3.1.5-5.1): Will attempt migration (Any information below is purely informational)
• openexr/armhf (3.1.5-5.1 to 3.1.5-5.1)
  • Migration status for openexr/armhf (3.1.5-5.1 to 3.1.5-5.1): Will attempt migration (Any information below is purely informational)
• openexr/i386 (3.1.5-5.1 to 3.1.5-5.1)
  • Migration status for openexr/i386 (3.1.5-5.1 to 3.1.5-5.1): Will attempt migration (Any information below is purely informational)
• openexr/mips64el (3.1.5-5.1 to 3.1.5-5.1)
  • Migration status for openexr/mips64el (3.1.5-5.1 to 3.1.5-5.1): Will attempt migration (Any information below is purely informational)
• openexr/ppc64el (3.1.5-5.1 to 3.1.5-5.1)
  • Migration status for openexr/ppc64el (3.1.5-5.1 to 3.1.5-5.1): Will attempt migration (Any information below is purely informational)
• openkim-models/amd64 (1:2021.01.28-2 to 1:2021.01.28-2)
  • Migration status for openkim-models/amd64 (1:2021.01.28-2 to 1:2021.01.28-2): Will attempt migration (Any information below is purely informational)
• openkim-models/arm64 (1:2021.01.28-2 to 1:2021.01.28-2)
  • Migration status for openkim-models/arm64 (1:2021.01.28-2 to 1:2021.01.28-2): Will attempt migration (Any information below is purely informational)
• openkim-models/armel (1:2021.01.28-2 to 1:2021.01.28-2)
  • Migration status for openkim-models/armel (1:2021.01.28-2 to 1:2021.01.28-2): Will attempt migration (Any information below is purely informational)
• openkim-models/armhf (1:2021.01.28-2 to 1:2021.01.28-2)
  • Migration status for openkim-models/armhf (1:2021.01.28-2 to 1:2021.01.28-2): Will attempt migration (Any information below is purely informational)
• openkim-models/i386 (1:2021.01.28-2 to 1:2021.01.28-2)
  • Migration status for openkim-models/i386 (1:2021.01.28-2 to 1:2021.01.28-2): Will attempt migration (Any information below is purely informational)
• openkim-models/mips64el (1:2021.01.28-2 to 1:2021.01.28-2)
  • Migration status for openkim-models/mips64el (1:2021.01.28-2 to 1:2021.01.28-2): Will attempt migration (Any information below is purely informational)
• openkim-models/ppc64el (1:2021.01.28-2 to 1:2021.01.28-2)
  • Migration status for openkim-models/ppc64el (1:2021.01.28-2 to 1:2021.01.28-2): Will attempt migration (Any information below is purely informational)
• openni/amd64 (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7)
  • Migration status for openni/amd64 (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7): Will attempt migration (Any information below is purely informational)
• openni/arm64 (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7)
  • Migration status for openni/arm64 (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7): Will attempt migration (Any information below is purely informational)
• openni/armel (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7)
  • Migration status for openni/armel (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7): Will attempt migration (Any information below is purely informational)
• openni/armhf (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7)
  • Migration status for openni/armhf (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7): Will attempt migration (Any information below is purely informational)
• openni/i386 (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7)
  • Migration status for openni/i386 (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7): Will attempt migration (Any information below is purely informational)
• openni/mips64el (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7)
  • Migration status for openni/mips64el (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7): Will attempt migration (Any information below is purely informational)
• openni/ppc64el (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7)
  • Migration status for openni/ppc64el (1.5.4.0+dfsg-7 to 1.5.4.0+dfsg-7): Will attempt migration (Any information below is purely informational)
• openpace/amd64 (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1)
  • Migration status for openpace/amd64 (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1): Will attempt migration (Any information below is purely informational)
• openpace/arm64 (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1)
  • Migration status for openpace/arm64 (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1): Will attempt migration (Any information below is purely informational)
• openpace/armel (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1)
  • Migration status for openpace/armel (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1): Will attempt migration (Any information below is purely informational)
• openpace/armhf (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1)
  • Migration status for openpace/armhf (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1): Will attempt migration (Any information below is purely informational)
• openpace/i386 (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1)
  • Migration status for openpace/i386 (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1): Will attempt migration (Any information below is purely informational)
• openpace/mips64el (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1)
  • Migration status for openpace/mips64el (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1): Will attempt migration (Any information below is purely informational)
• openpace/ppc64el (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1)
  • Migration status for openpace/ppc64el (1.1.2+ds+git20220117+453c3d6b03a0-1.1 to 1.1.2+ds+git20220117+453c3d6b03a0-1.1): Will attempt migration (Any information below is purely informational)
• opensaml/amd64 (3.2.1-4 to 3.2.1-4)
  • Migration status for opensaml/amd64 (3.2.1-4 to 3.2.1-4): Will attempt migration (Any information below is purely informational)
• opensaml/arm64 (3.2.1-4 to 3.2.1-4)
  • Migration status for opensaml/arm64 (3.2.1-4 to 3.2.1-4): Will attempt migration (Any information below is purely informational)
• opensaml/armhf (3.2.1-4 to 3.2.1-4)
  • Migration status for opensaml/armhf (3.2.1-4 to 3.2.1-4): Will attempt migration (Any information below is purely informational)
• opensaml/i386 (3.2.1-4 to 3.2.1-4)
  • Migration status for opensaml/i386 (3.2.1-4 to 3.2.1-4): Will attempt migration (Any information below is purely informational)
• opensaml/mips64el (3.2.1-4 to 3.2.1-4)
  • Migration status for opensaml/mips64el (3.2.1-4 to 3.2.1-4): Will attempt migration (Any information below is purely informational)
• opensaml/ppc64el (3.2.1-4 to 3.2.1-4)
  • Migration status for opensaml/ppc64el (3.2.1-4 to 3.2.1-4): Will attempt migration (Any information below is purely informational)
• opensubdiv/amd64 (3.5.0-2 to 3.5.0-2)
  • Migration status for opensubdiv/amd64 (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• opensubdiv/arm64 (3.5.0-2 to 3.5.0-2)
  • Migration status for opensubdiv/arm64 (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• opensubdiv/armel (3.5.0-2 to 3.5.0-2)
  • Migration status for opensubdiv/armel (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• opensubdiv/armhf (3.5.0-2 to 3.5.0-2)
  • Migration status for opensubdiv/armhf (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• opensubdiv/i386 (3.5.0-2 to 3.5.0-2)
  • Migration status for opensubdiv/i386 (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• opensubdiv/mips64el (3.5.0-2 to 3.5.0-2)
  • Migration status for opensubdiv/mips64el (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• opensubdiv/ppc64el (3.5.0-2 to 3.5.0-2)
  • Migration status for opensubdiv/ppc64el (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• opentracing-cpp/amd64 (1.6.0-4 to 1.6.0-4)
  • Migration status for opentracing-cpp/amd64 (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• opentracing-cpp/arm64 (1.6.0-4 to 1.6.0-4)
  • Migration status for opentracing-cpp/arm64 (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• opentracing-cpp/armel (1.6.0-4 to 1.6.0-4)
  • Migration status for opentracing-cpp/armel (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• opentracing-cpp/armhf (1.6.0-4 to 1.6.0-4)
  • Migration status for opentracing-cpp/armhf (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• opentracing-cpp/i386 (1.6.0-4 to 1.6.0-4)
  • Migration status for opentracing-cpp/i386 (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• opentracing-cpp/mips64el (1.6.0-4 to 1.6.0-4)
  • Migration status for opentracing-cpp/mips64el (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• opentracing-cpp/ppc64el (1.6.0-4 to 1.6.0-4)
  • Migration status for opentracing-cpp/ppc64el (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• openvdb/arm64 (10.0.1-2 to 10.0.1-2)
  • Migration status for openvdb/arm64 (10.0.1-2 to 10.0.1-2): Will attempt migration (Any information below is purely informational)
• openvdb/ppc64el (10.0.1-2 to 10.0.1-2)
  • Migration status for openvdb/ppc64el (10.0.1-2 to 10.0.1-2): Will attempt migration (Any information below is purely informational)
• openvdb/s390x (10.0.1-2 to 10.0.1-2)
  • Migration status for openvdb/s390x (10.0.1-2 to 10.0.1-2): Will attempt migration (Any information below is purely informational)
• openvlbi/amd64 (3.0.2-2 to 3.0.2-2)
  • Migration status for openvlbi/amd64 (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• openvlbi/arm64 (3.0.2-2 to 3.0.2-2)
  • Migration status for openvlbi/arm64 (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• openvlbi/armel (3.0.2-2 to 3.0.2-2)
  • Migration status for openvlbi/armel (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• openvlbi/armhf (3.0.2-2 to 3.0.2-2)
  • Migration status for openvlbi/armhf (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• openvlbi/i386 (3.0.2-2 to 3.0.2-2)
  • Migration status for openvlbi/i386 (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• openvlbi/mips64el (3.0.2-2 to 3.0.2-2)
  • Migration status for openvlbi/mips64el (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• openvlbi/ppc64el (3.0.2-2 to 3.0.2-2)
  • Migration status for openvlbi/ppc64el (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• openvpn-systemd-resolved/amd64 (1.3.0-4 to 1.3.0-4)
  • Migration status for openvpn-systemd-resolved/amd64 (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• openvpn-systemd-resolved/arm64 (1.3.0-4 to 1.3.0-4)
  • Migration status for openvpn-systemd-resolved/arm64 (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• openvpn-systemd-resolved/armel (1.3.0-4 to 1.3.0-4)
  • Migration status for openvpn-systemd-resolved/armel (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• openvpn-systemd-resolved/armhf (1.3.0-4 to 1.3.0-4)
  • Migration status for openvpn-systemd-resolved/armhf (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• 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)
• openvpn-systemd-resolved/ppc64el (1.3.0-4 to 1.3.0-4)
  • Migration status for openvpn-systemd-resolved/ppc64el (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• opt/amd64 (3.19-3 to 3.19-3)
  • Migration status for opt/amd64 (3.19-3 to 3.19-3): Will attempt migration (Any information below is purely informational)
• opt/arm64 (3.19-3 to 3.19-3)
  • Migration status for opt/arm64 (3.19-3 to 3.19-3): Will attempt migration (Any information below is purely informational)
• opt/armel (3.19-3 to 3.19-3)
  • Migration status for opt/armel (3.19-3 to 3.19-3): Will attempt migration (Any information below is purely informational)
• opt/armhf (3.19-3 to 3.19-3)
  • Migration status for opt/armhf (3.19-3 to 3.19-3): Will attempt migration (Any information below is purely informational)
• opt/i386 (3.19-3 to 3.19-3)
  • Migration status for opt/i386 (3.19-3 to 3.19-3): Will attempt migration (Any information below is purely informational)
• opt/mips64el (3.19-3 to 3.19-3)
  • Migration status for opt/mips64el (3.19-3 to 3.19-3): Will attempt migration (Any information below is purely informational)
• opt/ppc64el (3.19-3 to 3.19-3)
  • Migration status for opt/ppc64el (3.19-3 to 3.19-3): Will attempt migration (Any information below is purely informational)
• opus/amd64 (1.4-1 to 1.4-1)
  • Migration status for opus/amd64 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• opus/arm64 (1.4-1 to 1.4-1)
  • Migration status for opus/arm64 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• opus/armel (1.4-1 to 1.4-1)
  • Migration status for opus/armel (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• opus/armhf (1.4-1 to 1.4-1)
  • Migration status for opus/armhf (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• opus/i386 (1.4-1 to 1.4-1)
  • Migration status for opus/i386 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• opus/mips64el (1.4-1 to 1.4-1)
  • Migration status for opus/mips64el (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• opus/ppc64el (1.4-1 to 1.4-1)
  • Migration status for opus/ppc64el (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• opusfile/amd64 (0.12-4 to 0.12-4)
  • Migration status for opusfile/amd64 (0.12-4 to 0.12-4): Will attempt migration (Any information below is purely informational)
• opusfile/arm64 (0.12-4 to 0.12-4)
  • Migration status for opusfile/arm64 (0.12-4 to 0.12-4): Will attempt migration (Any information below is purely informational)
• opusfile/armel (0.12-4 to 0.12-4)
  • Migration status for opusfile/armel (0.12-4 to 0.12-4): Will attempt migration (Any information below is purely informational)
• opusfile/armhf (0.12-4 to 0.12-4)
  • Migration status for opusfile/armhf (0.12-4 to 0.12-4): Will attempt migration (Any information below is purely informational)
• opusfile/i386 (0.12-4 to 0.12-4)
  • Migration status for opusfile/i386 (0.12-4 to 0.12-4): Will attempt migration (Any information below is purely informational)
• opusfile/mips64el (0.12-4 to 0.12-4)
  • Migration status for opusfile/mips64el (0.12-4 to 0.12-4): Will attempt migration (Any information below is purely informational)
• opusfile/ppc64el (0.12-4 to 0.12-4)
  • Migration status for opusfile/ppc64el (0.12-4 to 0.12-4): Will attempt migration (Any information below is purely informational)
• orc/amd64 (1:0.4.34-3 to 1:0.4.34-3)
  • Migration status for orc/amd64 (1:0.4.34-3 to 1:0.4.34-3): Will attempt migration (Any information below is purely informational)
• orc/arm64 (1:0.4.34-3 to 1:0.4.34-3)
  • Migration status for orc/arm64 (1:0.4.34-3 to 1:0.4.34-3): Will attempt migration (Any information below is purely informational)
• orc/armel (1:0.4.34-3 to 1:0.4.34-3)
  • Migration status for orc/armel (1:0.4.34-3 to 1:0.4.34-3): Will attempt migration (Any information below is purely informational)
• orc/armhf (1:0.4.34-3 to 1:0.4.34-3)
  • Migration status for orc/armhf (1:0.4.34-3 to 1:0.4.34-3): Will attempt migration (Any information below is purely informational)
• orc/i386 (1:0.4.34-3 to 1:0.4.34-3)
  • Migration status for orc/i386 (1:0.4.34-3 to 1:0.4.34-3): Will attempt migration (Any information below is purely informational)
• orc/mips64el (1:0.4.34-3 to 1:0.4.34-3)
  • Migration status for orc/mips64el (1:0.4.34-3 to 1:0.4.34-3): Will attempt migration (Any information below is purely informational)
• orc/ppc64el (1:0.4.34-3 to 1:0.4.34-3)
  • Migration status for orc/ppc64el (1:0.4.34-3 to 1:0.4.34-3): Will attempt migration (Any information below is purely informational)
• orcania/amd64 (2.3.3-1 to 2.3.3-1)
  • Migration status for orcania/amd64 (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
• orcania/arm64 (2.3.3-1 to 2.3.3-1)
  • Migration status for orcania/arm64 (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
• orcania/armel (2.3.3-1 to 2.3.3-1)
  • Migration status for orcania/armel (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
• orcania/armhf (2.3.3-1 to 2.3.3-1)
  • Migration status for orcania/armhf (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
• orcania/i386 (2.3.3-1 to 2.3.3-1)
  • Migration status for orcania/i386 (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
• orcania/mips64el (2.3.3-1 to 2.3.3-1)
  • Migration status for orcania/mips64el (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
• orcania/ppc64el (2.3.3-1 to 2.3.3-1)
  • Migration status for orcania/ppc64el (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
• ortp/amd64 (1:5.2.0-2 to 1:5.2.0-2)
  • Migration status for ortp/amd64 (1:5.2.0-2 to 1:5.2.0-2): Will attempt migration (Any information below is purely informational)
• ortp/arm64 (1:5.2.0-2 to 1:5.2.0-2)
  • Migration status for ortp/arm64 (1:5.2.0-2 to 1:5.2.0-2): Will attempt migration (Any information below is purely informational)
• ortp/armel (1:5.2.0-2 to 1:5.2.0-2)
  • Migration status for ortp/armel (1:5.2.0-2 to 1:5.2.0-2): Will attempt migration (Any information below is purely informational)
• ortp/armhf (1:5.2.0-2 to 1:5.2.0-2)
  • Migration status for ortp/armhf (1:5.2.0-2 to 1:5.2.0-2): Will attempt migration (Any information below is purely informational)
• ortp/i386 (1:5.2.0-2 to 1:5.2.0-2)
  • Migration status for ortp/i386 (1:5.2.0-2 to 1:5.2.0-2): Will attempt migration (Any information below is purely informational)
• ortp/mips64el (1:5.2.0-2 to 1:5.2.0-2)
  • Migration status for ortp/mips64el (1:5.2.0-2 to 1:5.2.0-2): Will attempt migration (Any information below is purely informational)
• ortp/ppc64el (1:5.2.0-2 to 1:5.2.0-2)
  • Migration status for ortp/ppc64el (1:5.2.0-2 to 1:5.2.0-2): Will attempt migration (Any information below is purely informational)
• oscpack/amd64 (1.1.0-3 to 1.1.0-3)
  • Migration status for oscpack/amd64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• oscpack/arm64 (1.1.0-3 to 1.1.0-3)
  • Migration status for oscpack/arm64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• oscpack/armel (1.1.0-3 to 1.1.0-3)
  • Migration status for oscpack/armel (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• oscpack/armhf (1.1.0-3 to 1.1.0-3)
  • Migration status for oscpack/armhf (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• oscpack/i386 (1.1.0-3 to 1.1.0-3)
  • Migration status for oscpack/i386 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• oscpack/mips64el (1.1.0-3 to 1.1.0-3)
  • Migration status for oscpack/mips64el (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• oscpack/ppc64el (1.1.0-3 to 1.1.0-3)
  • Migration status for oscpack/ppc64el (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• osm-gps-map/arm64 (1.2.0-2 to 1.2.0-2)
  • Migration status for osm-gps-map/arm64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• osm-gps-map/armel (1.2.0-2 to 1.2.0-2)
  • Migration status for osm-gps-map/armel (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• osm-gps-map/armhf (1.2.0-2 to 1.2.0-2)
  • Migration status for osm-gps-map/armhf (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• osm-gps-map/i386 (1.2.0-2 to 1.2.0-2)
  • Migration status for osm-gps-map/i386 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• osm-gps-map/mips64el (1.2.0-2 to 1.2.0-2)
  • Migration status for osm-gps-map/mips64el (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• osm-gps-map/ppc64el (1.2.0-2 to 1.2.0-2)
  • Migration status for osm-gps-map/ppc64el (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• osmo-fl2k/arm64 (0.1.1-2 to 0.1.1-2)
  • Migration status for osmo-fl2k/arm64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• osmo-fl2k/armel (0.1.1-2 to 0.1.1-2)
  • Migration status for osmo-fl2k/armel (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• osmo-fl2k/armhf (0.1.1-2 to 0.1.1-2)
  • Migration status for osmo-fl2k/armhf (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• osmo-fl2k/i386 (0.1.1-2 to 0.1.1-2)
  • Migration status for osmo-fl2k/i386 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• osmo-fl2k/mips64el (0.1.1-2 to 0.1.1-2)
  • Migration status for osmo-fl2k/mips64el (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• osmo-fl2k/ppc64el (0.1.1-2 to 0.1.1-2)
  • Migration status for osmo-fl2k/ppc64el (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• osmo-iuh/arm64 (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5)
  • Migration status for osmo-iuh/arm64 (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5): Will attempt migration (Any information below is purely informational)
• osmo-iuh/armel (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5)
  • Migration status for osmo-iuh/armel (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5): Will attempt migration (Any information below is purely informational)
• osmo-iuh/armhf (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5)
  • Migration status for osmo-iuh/armhf (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5): Will attempt migration (Any information below is purely informational)
• osmo-iuh/i386 (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5)
  • Migration status for osmo-iuh/i386 (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5): Will attempt migration (Any information below is purely informational)
• osmo-iuh/mips64el (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5)
  • Migration status for osmo-iuh/mips64el (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5): Will attempt migration (Any information below is purely informational)
• osmo-iuh/ppc64el (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5)
  • Migration status for osmo-iuh/ppc64el (1.3.0+dfsg1-5 to 1.3.0+dfsg1-5): Will attempt migration (Any information below is purely informational)
• osmo-libasn1c/arm64 (0.9.36-1 to 0.9.36-1)
  • Migration status for osmo-libasn1c/arm64 (0.9.36-1 to 0.9.36-1): Will attempt migration (Any information below is purely informational)
• osmo-libasn1c/armel (0.9.36-1 to 0.9.36-1)
  • Migration status for osmo-libasn1c/armel (0.9.36-1 to 0.9.36-1): Will attempt migration (Any information below is purely informational)
• osmo-libasn1c/armhf (0.9.36-1 to 0.9.36-1)
  • Migration status for osmo-libasn1c/armhf (0.9.36-1 to 0.9.36-1): Will attempt migration (Any information below is purely informational)
• osmo-libasn1c/i386 (0.9.36-1 to 0.9.36-1)
  • Migration status for osmo-libasn1c/i386 (0.9.36-1 to 0.9.36-1): Will attempt migration (Any information below is purely informational)
• osmo-libasn1c/mips64el (0.9.36-1 to 0.9.36-1)
  • Migration status for osmo-libasn1c/mips64el (0.9.36-1 to 0.9.36-1): Will attempt migration (Any information below is purely informational)
• osmo-libasn1c/ppc64el (0.9.36-1 to 0.9.36-1)
  • Migration status for osmo-libasn1c/ppc64el (0.9.36-1 to 0.9.36-1): Will attempt migration (Any information below is purely informational)
• otcl/arm64 (1.14+dfsg-8 to 1.14+dfsg-8)
  • Migration status for otcl/arm64 (1.14+dfsg-8 to 1.14+dfsg-8): Will attempt migration (Any information below is purely informational)
• otcl/armel (1.14+dfsg-8 to 1.14+dfsg-8)
  • Migration status for otcl/armel (1.14+dfsg-8 to 1.14+dfsg-8): Will attempt migration (Any information below is purely informational)
• otcl/armhf (1.14+dfsg-8 to 1.14+dfsg-8)
  • Migration status for otcl/armhf (1.14+dfsg-8 to 1.14+dfsg-8): Will attempt migration (Any information below is purely informational)
• otcl/i386 (1.14+dfsg-8 to 1.14+dfsg-8)
  • Migration status for otcl/i386 (1.14+dfsg-8 to 1.14+dfsg-8): Will attempt migration (Any information below is purely informational)
• otcl/mips64el (1.14+dfsg-8 to 1.14+dfsg-8)
  • Migration status for otcl/mips64el (1.14+dfsg-8 to 1.14+dfsg-8): Will attempt migration (Any information below is purely informational)
• otcl/ppc64el (1.14+dfsg-8 to 1.14+dfsg-8)
  • Migration status for otcl/ppc64el (1.14+dfsg-8 to 1.14+dfsg-8): Will attempt migration (Any information below is purely informational)
• otf/arm64 (1.12.5+dfsg-8 to 1.12.5+dfsg-8)
  • Migration status for otf/arm64 (1.12.5+dfsg-8 to 1.12.5+dfsg-8): Will attempt migration (Any information below is purely informational)
• otf/armel (1.12.5+dfsg-8 to 1.12.5+dfsg-8)
  • Migration status for otf/armel (1.12.5+dfsg-8 to 1.12.5+dfsg-8): Will attempt migration (Any information below is purely informational)
• otf/armhf (1.12.5+dfsg-8 to 1.12.5+dfsg-8)
  • Migration status for otf/armhf (1.12.5+dfsg-8 to 1.12.5+dfsg-8): Will attempt migration (Any information below is purely informational)
• otf/i386 (1.12.5+dfsg-8 to 1.12.5+dfsg-8)
  • Migration status for otf/i386 (1.12.5+dfsg-8 to 1.12.5+dfsg-8): Will attempt migration (Any information below is purely informational)
• otf/mips64el (1.12.5+dfsg-8 to 1.12.5+dfsg-8)
  • Migration status for otf/mips64el (1.12.5+dfsg-8 to 1.12.5+dfsg-8): Will attempt migration (Any information below is purely informational)
• otf/ppc64el (1.12.5+dfsg-8 to 1.12.5+dfsg-8)
  • Migration status for otf/ppc64el (1.12.5+dfsg-8 to 1.12.5+dfsg-8): Will attempt migration (Any information below is purely informational)
• ots/arm64 (0.5.0-8 to 0.5.0-8)
  • Migration status for ots/arm64 (0.5.0-8 to 0.5.0-8): Will attempt migration (Any information below is purely informational)
• ots/armel (0.5.0-8 to 0.5.0-8)
  • Migration status for ots/armel (0.5.0-8 to 0.5.0-8): Will attempt migration (Any information below is purely informational)
• ots/armhf (0.5.0-8 to 0.5.0-8)
  • Migration status for ots/armhf (0.5.0-8 to 0.5.0-8): Will attempt migration (Any information below is purely informational)
• ots/i386 (0.5.0-8 to 0.5.0-8)
  • Migration status for ots/i386 (0.5.0-8 to 0.5.0-8): Will attempt migration (Any information below is purely informational)
• ots/mips64el (0.5.0-8 to 0.5.0-8)
  • Migration status for ots/mips64el (0.5.0-8 to 0.5.0-8): Will attempt migration (Any information below is purely informational)
• ots/ppc64el (0.5.0-8 to 0.5.0-8)
  • Migration status for ots/ppc64el (0.5.0-8 to 0.5.0-8): Will attempt migration (Any information below is purely informational)
• ovn_pu (24.03.0~git20240205.ebb7076-1 to 23.03.1-1~deb12u1)
  • Migration status for ovn_pu (24.03.0~git20240205.ebb7076-1 to 23.03.1-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ovn is newer in the target suite (24.03.0~git20240205.ebb7076-1 23.03.1-1~deb12u1)
• owncloud-client/arm64 (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1)
  • Migration status for owncloud-client/arm64 (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1): Will attempt migration (Any information below is purely informational)
• owncloud-client/armel (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1)
  • Migration status for owncloud-client/armel (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1): Will attempt migration (Any information below is purely informational)
• owncloud-client/armhf (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1)
  • Migration status for owncloud-client/armhf (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1): Will attempt migration (Any information below is purely informational)
• owncloud-client/i386 (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1)
  • Migration status for owncloud-client/i386 (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1): Will attempt migration (Any information below is purely informational)
• owncloud-client/mips64el (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1)
  • Migration status for owncloud-client/mips64el (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1): Will attempt migration (Any information below is purely informational)
• owncloud-client/ppc64el (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1)
  • Migration status for owncloud-client/ppc64el (4.2.0.11670+dfsg-1 to 4.2.0.11670+dfsg-1): Will attempt migration (Any information below is purely informational)
• p4est/arm64 (2.3.6-1 to 2.3.6-1)
  • Migration status for p4est/arm64 (2.3.6-1 to 2.3.6-1): Will attempt migration (Any information below is purely informational)
• p4est/ppc64el (2.3.6-1 to 2.3.6-1)
  • Migration status for p4est/ppc64el (2.3.6-1 to 2.3.6-1): Will attempt migration (Any information below is purely informational)
• p8-platform/arm64 (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4)
  • Migration status for p8-platform/arm64 (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4): Will attempt migration (Any information below is purely informational)
• p8-platform/armel (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4)
  • Migration status for p8-platform/armel (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4): Will attempt migration (Any information below is purely informational)
• p8-platform/armhf (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4)
  • Migration status for p8-platform/armhf (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4): Will attempt migration (Any information below is purely informational)
• p8-platform/i386 (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4)
  • Migration status for p8-platform/i386 (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4): Will attempt migration (Any information below is purely informational)
• p8-platform/ppc64el (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4)
  • Migration status for p8-platform/ppc64el (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4): Will attempt migration (Any information below is purely informational)
• packagekit-qt/arm64 (1.1.1-1 to 1.1.1-1)
  • Migration status for packagekit-qt/arm64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• packagekit-qt/armel (1.1.1-1 to 1.1.1-1)
  • Migration status for packagekit-qt/armel (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• packagekit-qt/armhf (1.1.1-1 to 1.1.1-1)
  • Migration status for packagekit-qt/armhf (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• packagekit-qt/i386 (1.1.1-1 to 1.1.1-1)
  • Migration status for packagekit-qt/i386 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• packagekit-qt/ppc64el (1.1.1-1 to 1.1.1-1)
  • Migration status for packagekit-qt/ppc64el (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• pagmo/arm64 (2.19.0-3 to 2.19.0-3)
  • Migration status for pagmo/arm64 (2.19.0-3 to 2.19.0-3): Will attempt migration (Any information below is purely informational)
• pagmo/armel (2.19.0-3 to 2.19.0-3)
  • Migration status for pagmo/armel (2.19.0-3 to 2.19.0-3): Will attempt migration (Any information below is purely informational)
• pagmo/armhf (2.19.0-3 to 2.19.0-3)
  • Migration status for pagmo/armhf (2.19.0-3 to 2.19.0-3): Will attempt migration (Any information below is purely informational)
• pagmo/i386 (2.19.0-3 to 2.19.0-3)
  • Migration status for pagmo/i386 (2.19.0-3 to 2.19.0-3): Will attempt migration (Any information below is purely informational)
• pagmo/ppc64el (2.19.0-3 to 2.19.0-3)
  • Migration status for pagmo/ppc64el (2.19.0-3 to 2.19.0-3): Will attempt migration (Any information below is purely informational)
• paho.mqtt.c/arm64 (1.3.13-1 to 1.3.13-1)
  • Migration status for paho.mqtt.c/arm64 (1.3.13-1 to 1.3.13-1): Will attempt migration (Any information below is purely informational)
• paho.mqtt.c/armel (1.3.13-1 to 1.3.13-1)
  • Migration status for paho.mqtt.c/armel (1.3.13-1 to 1.3.13-1): Will attempt migration (Any information below is purely informational)
• paho.mqtt.c/armhf (1.3.13-1 to 1.3.13-1)
  • Migration status for paho.mqtt.c/armhf (1.3.13-1 to 1.3.13-1): Will attempt migration (Any information below is purely informational)
• paho.mqtt.c/i386 (1.3.13-1 to 1.3.13-1)
  • Migration status for paho.mqtt.c/i386 (1.3.13-1 to 1.3.13-1): Will attempt migration (Any information below is purely informational)
• paho.mqtt.c/ppc64el (1.3.13-1 to 1.3.13-1)
  • Migration status for paho.mqtt.c/ppc64el (1.3.13-1 to 1.3.13-1): Will attempt migration (Any information below is purely informational)
• paho.mqtt.cpp/arm64 (1.2.0-2 to 1.2.0-2)
  • Migration status for paho.mqtt.cpp/arm64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• paho.mqtt.cpp/armel (1.2.0-2 to 1.2.0-2)
  • Migration status for paho.mqtt.cpp/armel (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• paho.mqtt.cpp/armhf (1.2.0-2 to 1.2.0-2)
  • Migration status for paho.mqtt.cpp/armhf (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• paho.mqtt.cpp/i386 (1.2.0-2 to 1.2.0-2)
  • Migration status for paho.mqtt.cpp/i386 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• paho.mqtt.cpp/ppc64el (1.2.0-2 to 1.2.0-2)
  • Migration status for paho.mqtt.cpp/ppc64el (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• pajeng/arm64 (1.3.6-4 to 1.3.6-4)
  • Migration status for pajeng/arm64 (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• pajeng/armel (1.3.6-4 to 1.3.6-4)
  • Migration status for pajeng/armel (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• pajeng/armhf (1.3.6-4 to 1.3.6-4)
  • Migration status for pajeng/armhf (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• pajeng/i386 (1.3.6-4 to 1.3.6-4)
  • Migration status for pajeng/i386 (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• pajeng/ppc64el (1.3.6-4 to 1.3.6-4)
  • Migration status for pajeng/ppc64el (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• palabos/arm64 (1.5~r1+repack1-5 to 1.5~r1+repack1-5)
  • Migration status for palabos/arm64 (1.5~r1+repack1-5 to 1.5~r1+repack1-5): Will attempt migration (Any information below is purely informational)
• palabos/armel (1.5~r1+repack1-5 to 1.5~r1+repack1-5)
  • Migration status for palabos/armel (1.5~r1+repack1-5 to 1.5~r1+repack1-5): Will attempt migration (Any information below is purely informational)
• palabos/armhf (1.5~r1+repack1-5 to 1.5~r1+repack1-5)
  • Migration status for palabos/armhf (1.5~r1+repack1-5 to 1.5~r1+repack1-5): Will attempt migration (Any information below is purely informational)
• palabos/i386 (1.5~r1+repack1-5 to 1.5~r1+repack1-5)
  • Migration status for palabos/i386 (1.5~r1+repack1-5 to 1.5~r1+repack1-5): Will attempt migration (Any information below is purely informational)
• palabos/ppc64el (1.5~r1+repack1-5 to 1.5~r1+repack1-5)
  • Migration status for palabos/ppc64el (1.5~r1+repack1-5 to 1.5~r1+repack1-5): Will attempt migration (Any information below is purely informational)
• pam-mysql/arm64 (0.8.2-2 to 0.8.2-2)
  • Migration status for pam-mysql/arm64 (0.8.2-2 to 0.8.2-2): Will attempt migration (Any information below is purely informational)
• pam-mysql/armel (0.8.2-2 to 0.8.2-2)
  • Migration status for pam-mysql/armel (0.8.2-2 to 0.8.2-2): Will attempt migration (Any information below is purely informational)
• pam-mysql/armhf (0.8.2-2 to 0.8.2-2)
  • Migration status for pam-mysql/armhf (0.8.2-2 to 0.8.2-2): Will attempt migration (Any information below is purely informational)
• pam-mysql/i386 (0.8.2-2 to 0.8.2-2)
  • Migration status for pam-mysql/i386 (0.8.2-2 to 0.8.2-2): Will attempt migration (Any information below is purely informational)
• pam-mysql/ppc64el (0.8.2-2 to 0.8.2-2)
  • Migration status for pam-mysql/ppc64el (0.8.2-2 to 0.8.2-2): Will attempt migration (Any information below is purely informational)
• pam-wrapper/arm64 (1.1.5-1 to 1.1.5-1)
  • Migration status for pam-wrapper/arm64 (1.1.5-1 to 1.1.5-1): Will attempt migration (Any information below is purely informational)
• pam-wrapper/armel (1.1.5-1 to 1.1.5-1)
  • Migration status for pam-wrapper/armel (1.1.5-1 to 1.1.5-1): Will attempt migration (Any information below is purely informational)
• pam-wrapper/armhf (1.1.5-1 to 1.1.5-1)
  • Migration status for pam-wrapper/armhf (1.1.5-1 to 1.1.5-1): Will attempt migration (Any information below is purely informational)
• pam-wrapper/i386 (1.1.5-1 to 1.1.5-1)
  • Migration status for pam-wrapper/i386 (1.1.5-1 to 1.1.5-1): Will attempt migration (Any information below is purely informational)
• pam-wrapper/ppc64el (1.1.5-1 to 1.1.5-1)
  • Migration status for pam-wrapper/ppc64el (1.1.5-1 to 1.1.5-1): Will attempt migration (Any information below is purely informational)
• pangomm2.48/arm64 (2.50.1-5 to 2.50.1-5)
  • Migration status for pangomm2.48/arm64 (2.50.1-5 to 2.50.1-5): Will attempt migration (Any information below is purely informational)
• pangomm2.48/armel (2.50.1-5 to 2.50.1-5)
  • Migration status for pangomm2.48/armel (2.50.1-5 to 2.50.1-5): Will attempt migration (Any information below is purely informational)
• pangomm2.48/armhf (2.50.1-5 to 2.50.1-5)
  • Migration status for pangomm2.48/armhf (2.50.1-5 to 2.50.1-5): Will attempt migration (Any information below is purely informational)
• pangomm2.48/i386 (2.50.1-5 to 2.50.1-5)
  • Migration status for pangomm2.48/i386 (2.50.1-5 to 2.50.1-5): Will attempt migration (Any information below is purely informational)
• pangomm2.48/ppc64el (2.50.1-5 to 2.50.1-5)
  • Migration status for pangomm2.48/ppc64el (2.50.1-5 to 2.50.1-5): Will attempt migration (Any information below is purely informational)
• pappl/arm64 (1.3.1-2 to 1.3.1-2)
  • Migration status for pappl/arm64 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
• pappl/armel (1.3.1-2 to 1.3.1-2)
  • Migration status for pappl/armel (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
• pappl/armhf (1.3.1-2 to 1.3.1-2)
  • Migration status for pappl/armhf (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
• pappl/i386 (1.3.1-2 to 1.3.1-2)
  • Migration status for pappl/i386 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
• pappl/ppc64el (1.3.1-2 to 1.3.1-2)
  • Migration status for pappl/ppc64el (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
• paraglob/arm64 (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/arm64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• paraglob/armel (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/armel (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• paraglob/armhf (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/armhf (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• paraglob/i386 (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/i386 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• paraglob/ppc64el (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/ppc64el (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• parasail/arm64 (2.6.2+dfsg-1 to 2.6.2+dfsg-1)
  • Migration status for parasail/arm64 (2.6.2+dfsg-1 to 2.6.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• parasail/armel (2.6.2+dfsg-1 to 2.6.2+dfsg-1)
  • Migration status for parasail/armel (2.6.2+dfsg-1 to 2.6.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• parasail/armhf (2.6.2+dfsg-1 to 2.6.2+dfsg-1)
  • Migration status for parasail/armhf (2.6.2+dfsg-1 to 2.6.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• parasail/i386 (2.6.2+dfsg-1 to 2.6.2+dfsg-1)
  • Migration status for parasail/i386 (2.6.2+dfsg-1 to 2.6.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• parasail/ppc64el (2.6.2+dfsg-1 to 2.6.2+dfsg-1)
  • Migration status for parasail/ppc64el (2.6.2+dfsg-1 to 2.6.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• pari/arm64 (2.15.4-2 to 2.15.4-2)
  • Migration status for pari/arm64 (2.15.4-2 to 2.15.4-2): Will attempt migration (Any information below is purely informational)
• pari/armhf (2.15.4-2 to 2.15.4-2)
  • Migration status for pari/armhf (2.15.4-2 to 2.15.4-2): Will attempt migration (Any information below is purely informational)
• pari/i386 (2.15.4-2 to 2.15.4-2)
  • Migration status for pari/i386 (2.15.4-2 to 2.15.4-2): Will attempt migration (Any information below is purely informational)
• pari/ppc64el (2.15.4-2 to 2.15.4-2)
  • Migration status for pari/ppc64el (2.15.4-2 to 2.15.4-2): Will attempt migration (Any information below is purely informational)
• parlatype/arm64 (3.1-3 to 3.1-3)
  • Migration status for parlatype/arm64 (3.1-3 to 3.1-3): Will attempt migration (Any information below is purely informational)
• parlatype/armel (3.1-3 to 3.1-3)
  • Migration status for parlatype/armel (3.1-3 to 3.1-3): Will attempt migration (Any information below is purely informational)
• parlatype/armhf (3.1-3 to 3.1-3)
  • Migration status for parlatype/armhf (3.1-3 to 3.1-3): Will attempt migration (Any information below is purely informational)
• parlatype/i386 (3.1-3 to 3.1-3)
  • Migration status for parlatype/i386 (3.1-3 to 3.1-3): Will attempt migration (Any information below is purely informational)
• parlatype/ppc64el (3.1-3 to 3.1-3)
  • Migration status for parlatype/ppc64el (3.1-3 to 3.1-3): Will attempt migration (Any information below is purely informational)
• parole/arm64 (4.18.1-1 to 4.18.1-1)
  • Migration status for parole/arm64 (4.18.1-1 to 4.18.1-1): Will attempt migration (Any information below is purely informational)
• parole/armel (4.18.1-1 to 4.18.1-1)
  • Migration status for parole/armel (4.18.1-1 to 4.18.1-1): Will attempt migration (Any information below is purely informational)
• parole/armhf (4.18.1-1 to 4.18.1-1)
  • Migration status for parole/armhf (4.18.1-1 to 4.18.1-1): Will attempt migration (Any information below is purely informational)
• parole/i386 (4.18.1-1 to 4.18.1-1)
  • Migration status for parole/i386 (4.18.1-1 to 4.18.1-1): Will attempt migration (Any information below is purely informational)
• parole/ppc64el (4.18.1-1 to 4.18.1-1)
  • Migration status for parole/ppc64el (4.18.1-1 to 4.18.1-1): Will attempt migration (Any information below is purely informational)
• parted/arm64 (3.6-3 to 3.6-3)
  • Migration status for parted/arm64 (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• parted/armhf (3.6-3 to 3.6-3)
  • Migration status for parted/armhf (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• parted/i386 (3.6-3 to 3.6-3)
  • Migration status for parted/i386 (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• parted/ppc64el (3.6-3 to 3.6-3)
  • Migration status for parted/ppc64el (3.6-3 to 3.6-3): Will attempt migration (Any information below is purely informational)
• passwdqc/arm64 (2.0.3-1 to 2.0.3-1)
  • Migration status for passwdqc/arm64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• passwdqc/armel (2.0.3-1 to 2.0.3-1)
  • Migration status for passwdqc/armel (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• passwdqc/armhf (2.0.3-1 to 2.0.3-1)
  • Migration status for passwdqc/armhf (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• passwdqc/i386 (2.0.3-1 to 2.0.3-1)
  • Migration status for passwdqc/i386 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• passwdqc/ppc64el (2.0.3-1 to 2.0.3-1)
  • Migration status for passwdqc/ppc64el (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• pcaudiolib/arm64 (1.2-2 to 1.2-2)
  • Migration status for pcaudiolib/arm64 (1.2-2 to 1.2-2): Will attempt migration (Any information below is purely informational)
• pcaudiolib/armel (1.2-2 to 1.2-2)
  • Migration status for pcaudiolib/armel (1.2-2 to 1.2-2): Will attempt migration (Any information below is purely informational)
• pcaudiolib/armhf (1.2-2 to 1.2-2)
  • Migration status for pcaudiolib/armhf (1.2-2 to 1.2-2): Will attempt migration (Any information below is purely informational)
• pcaudiolib/i386 (1.2-2 to 1.2-2)
  • Migration status for pcaudiolib/i386 (1.2-2 to 1.2-2): Will attempt migration (Any information below is purely informational)
• pcaudiolib/ppc64el (1.2-2 to 1.2-2)
  • Migration status for pcaudiolib/ppc64el (1.2-2 to 1.2-2): Will attempt migration (Any information below is purely informational)
• pciutils/arm64 (1:3.10.0-2 to 1:3.10.0-2)
  • Migration status for pciutils/arm64 (1:3.10.0-2 to 1:3.10.0-2): Will attempt migration (Any information below is purely informational)
• pciutils/armel (1:3.10.0-2 to 1:3.10.0-2)
  • Migration status for pciutils/armel (1:3.10.0-2 to 1:3.10.0-2): Will attempt migration (Any information below is purely informational)
• pciutils/armhf (1:3.10.0-2 to 1:3.10.0-2)
  • Migration status for pciutils/armhf (1:3.10.0-2 to 1:3.10.0-2): Will attempt migration (Any information below is purely informational)
• pciutils/i386 (1:3.10.0-2 to 1:3.10.0-2)
  • Migration status for pciutils/i386 (1:3.10.0-2 to 1:3.10.0-2): Will attempt migration (Any information below is purely informational)
• pciutils/ppc64el (1:3.10.0-2 to 1:3.10.0-2)
  • Migration status for pciutils/ppc64el (1:3.10.0-2 to 1:3.10.0-2): Will attempt migration (Any information below is purely informational)
• pcre2/arm64 (10.42-4 to 10.42-4)
  • Migration status for pcre2/arm64 (10.42-4 to 10.42-4): Will attempt migration (Any information below is purely informational)
• pcre2/armel (10.42-4 to 10.42-4)
  • Migration status for pcre2/armel (10.42-4 to 10.42-4): Will attempt migration (Any information below is purely informational)
• pcre2/armhf (10.42-4 to 10.42-4)
  • Migration status for pcre2/armhf (10.42-4 to 10.42-4): Will attempt migration (Any information below is purely informational)
• pcre2/i386 (10.42-4 to 10.42-4)
  • Migration status for pcre2/i386 (10.42-4 to 10.42-4): Will attempt migration (Any information below is purely informational)
• pcre2/ppc64el (10.42-4 to 10.42-4)
  • Migration status for pcre2/ppc64el (10.42-4 to 10.42-4): Will attempt migration (Any information below is purely informational)
• pcre3/arm64 (2:8.39-15 to 2:8.39-15)
  • Migration status for pcre3/arm64 (2:8.39-15 to 2:8.39-15): Will attempt migration (Any information below is purely informational)
• pcre3/armel (2:8.39-15 to 2:8.39-15)
  • Migration status for pcre3/armel (2:8.39-15 to 2:8.39-15): Will attempt migration (Any information below is purely informational)
• pcre3/armhf (2:8.39-15 to 2:8.39-15)
  • Migration status for pcre3/armhf (2:8.39-15 to 2:8.39-15): Will attempt migration (Any information below is purely informational)
• pcre3/i386 (2:8.39-15 to 2:8.39-15)
  • Migration status for pcre3/i386 (2:8.39-15 to 2:8.39-15): Will attempt migration (Any information below is purely informational)
• pcre3/ppc64el (2:8.39-15 to 2:8.39-15)
  • Migration status for pcre3/ppc64el (2:8.39-15 to 2:8.39-15): Will attempt migration (Any information below is purely informational)
• pcsc-lite/arm64 (2.0.1-1 to 2.0.1-1)
  • Migration status for pcsc-lite/arm64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• pcsc-lite/armel (2.0.1-1 to 2.0.1-1)
  • Migration status for pcsc-lite/armel (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• pcsc-lite/armhf (2.0.1-1 to 2.0.1-1)
  • Migration status for pcsc-lite/armhf (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• pcsc-lite/i386 (2.0.1-1 to 2.0.1-1)
  • Migration status for pcsc-lite/i386 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• pcsc-lite/ppc64el (2.0.1-1 to 2.0.1-1)
  • Migration status for pcsc-lite/ppc64el (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• pdns-recursor_pu (4.9.3-1 to 4.8.6-1)
  • Migration status for pdns-recursor_pu (4.9.3-1 to 4.8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: pdns-recursor is newer in the target suite (4.9.3-1 4.8.6-1)
• pfqueue/arm64 (0.5.6-9.2 to 0.5.6-9.2)
  • Migration status for pfqueue/arm64 (0.5.6-9.2 to 0.5.6-9.2): Will attempt migration (Any information below is purely informational)
• pfqueue/armel (0.5.6-9.2 to 0.5.6-9.2)
  • Migration status for pfqueue/armel (0.5.6-9.2 to 0.5.6-9.2): Will attempt migration (Any information below is purely informational)
• pfqueue/armhf (0.5.6-9.2 to 0.5.6-9.2)
  • Migration status for pfqueue/armhf (0.5.6-9.2 to 0.5.6-9.2): Will attempt migration (Any information below is purely informational)
• pfqueue/i386 (0.5.6-9.2 to 0.5.6-9.2)
  • Migration status for pfqueue/i386 (0.5.6-9.2 to 0.5.6-9.2): Will attempt migration (Any information below is purely informational)
• pfqueue/ppc64el (0.5.6-9.2 to 0.5.6-9.2)
  • Migration status for pfqueue/ppc64el (0.5.6-9.2 to 0.5.6-9.2): Will attempt migration (Any information below is purely informational)
• pgocaml/amd64 (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/amd64 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgocaml/amd64 ocaml-cstruct/amd64
    • Depends: pgocaml/amd64 ppx-deriving/amd64
    • Depends: pgocaml/amd64 ppxlib
    • Depends: pgocaml/amd64 sexplib310/amd64
    • Implicit dependency: pgocaml/amd64 ocsipersist/amd64
• pgocaml/arm64 (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/arm64 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgocaml/arm64 ocaml-cstruct/arm64
    • Depends: pgocaml/arm64 ppx-deriving/arm64
    • Depends: pgocaml/arm64 ppxlib
    • Depends: pgocaml/arm64 sexplib310/arm64
    • Implicit dependency: pgocaml/arm64 ocsipersist/arm64
• pgocaml/armel (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/armel (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgocaml/armel ppx-deriving/armel
    • Depends: pgocaml/armel ppxlib
    • Depends: pgocaml/armel sexplib310/armel
    • Implicit dependency: pgocaml/armel ocsipersist/armel
• pgocaml/armhf (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/armhf (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgocaml/armhf ocaml-cstruct/armhf
    • Depends: pgocaml/armhf ppx-deriving/armhf
    • Depends: pgocaml/armhf ppxlib
    • Depends: pgocaml/armhf sexplib310/armhf
    • Implicit dependency: pgocaml/armhf ocsipersist/armhf
• pgocaml/i386 (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/i386 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgocaml/i386 ocaml-cstruct/i386
    • Depends: pgocaml/i386 ppx-deriving/i386
    • Depends: pgocaml/i386 ppxlib
    • Depends: pgocaml/i386 sexplib310/i386
    • Implicit dependency: pgocaml/i386 ocsipersist/i386
• pgocaml/mips64el (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/mips64el (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgocaml/mips64el ppx-deriving/mips64el
    • Depends: pgocaml/mips64el ppxlib
    • Depends: pgocaml/mips64el sexplib310/mips64el
    • Implicit dependency: pgocaml/mips64el ocsipersist/mips64el
• pgocaml/ppc64el (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/ppc64el (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgocaml/ppc64el ocaml-cstruct/ppc64el
    • Depends: pgocaml/ppc64el ppx-deriving/ppc64el
    • Depends: pgocaml/ppc64el ppxlib
    • Depends: pgocaml/ppc64el sexplib310/ppc64el
    • Implicit dependency: pgocaml/ppc64el ocsipersist/ppc64el
• pgocaml/s390x (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/s390x (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgocaml/s390x ocaml-cstruct/s390x
    • Depends: pgocaml/s390x ppx-deriving/s390x
    • Depends: pgocaml/s390x ppxlib
    • Depends: pgocaml/s390x sexplib310/s390x
    • Implicit dependency: pgocaml/s390x ocsipersist/s390x
• phodav/arm64 (3.0-8 to 3.0-8)
  • Migration status for phodav/arm64 (3.0-8 to 3.0-8): Will attempt migration (Any information below is purely informational)
• phodav/armel (3.0-8 to 3.0-8)
  • Migration status for phodav/armel (3.0-8 to 3.0-8): Will attempt migration (Any information below is purely informational)
• phodav/armhf (3.0-8 to 3.0-8)
  • Migration status for phodav/armhf (3.0-8 to 3.0-8): Will attempt migration (Any information below is purely informational)
• phodav/i386 (3.0-8 to 3.0-8)
  • Migration status for phodav/i386 (3.0-8 to 3.0-8): Will attempt migration (Any information below is purely informational)
• phodav/ppc64el (3.0-8 to 3.0-8)
  • Migration status for phodav/ppc64el (3.0-8 to 3.0-8): Will attempt migration (Any information below is purely informational)
• phonon-backend-gstreamer/arm64 (4:4.10.0-2 to 4:4.10.0-2)
  • Migration status for phonon-backend-gstreamer/arm64 (4:4.10.0-2 to 4:4.10.0-2): Will attempt migration (Any information below is purely informational)
• phonon-backend-gstreamer/armel (4:4.10.0-2 to 4:4.10.0-2)
  • Migration status for phonon-backend-gstreamer/armel (4:4.10.0-2 to 4:4.10.0-2): Will attempt migration (Any information below is purely informational)
• phonon-backend-gstreamer/armhf (4:4.10.0-2 to 4:4.10.0-2)
  • Migration status for phonon-backend-gstreamer/armhf (4:4.10.0-2 to 4:4.10.0-2): Will attempt migration (Any information below is purely informational)
• phonon-backend-gstreamer/i386 (4:4.10.0-2 to 4:4.10.0-2)
  • Migration status for phonon-backend-gstreamer/i386 (4:4.10.0-2 to 4:4.10.0-2): Will attempt migration (Any information below is purely informational)
• phonon-backend-gstreamer/ppc64el (4:4.10.0-2 to 4:4.10.0-2)
  • Migration status for phonon-backend-gstreamer/ppc64el (4:4.10.0-2 to 4:4.10.0-2): Will attempt migration (Any information below is purely informational)
• phonon-backend-vlc/arm64 (0.12.0-3 to 0.12.0-3)
  • Migration status for phonon-backend-vlc/arm64 (0.12.0-3 to 0.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon-backend-vlc/armel (0.12.0-3 to 0.12.0-3)
  • Migration status for phonon-backend-vlc/armel (0.12.0-3 to 0.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon-backend-vlc/armhf (0.12.0-3 to 0.12.0-3)
  • Migration status for phonon-backend-vlc/armhf (0.12.0-3 to 0.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon-backend-vlc/i386 (0.12.0-3 to 0.12.0-3)
  • Migration status for phonon-backend-vlc/i386 (0.12.0-3 to 0.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon-backend-vlc/ppc64el (0.12.0-3 to 0.12.0-3)
  • Migration status for phonon-backend-vlc/ppc64el (0.12.0-3 to 0.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon/arm64 (4:4.12.0-3 to 4:4.12.0-3)
  • Migration status for phonon/arm64 (4:4.12.0-3 to 4:4.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon/armhf (4:4.12.0-3 to 4:4.12.0-3)
  • Migration status for phonon/armhf (4:4.12.0-3 to 4:4.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon/i386 (4:4.12.0-3 to 4:4.12.0-3)
  • Migration status for phonon/i386 (4:4.12.0-3 to 4:4.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon/ppc64el (4:4.12.0-3 to 4:4.12.0-3)
  • Migration status for phonon/ppc64el (4:4.12.0-3 to 4:4.12.0-3): Will attempt migration (Any information below is purely informational)
• pillow-sane/arm64 (2.9.1-3 to 2.9.1-3)
  • Migration status for pillow-sane/arm64 (2.9.1-3 to 2.9.1-3): Will attempt migration (Any information below is purely informational)
• pillow-sane/armel (2.9.1-3 to 2.9.1-3)
  • Migration status for pillow-sane/armel (2.9.1-3 to 2.9.1-3): Will attempt migration (Any information below is purely informational)
• pillow-sane/armhf (2.9.1-3 to 2.9.1-3)
  • Migration status for pillow-sane/armhf (2.9.1-3 to 2.9.1-3): Will attempt migration (Any information below is purely informational)
• pillow-sane/i386 (2.9.1-3 to 2.9.1-3)
  • Migration status for pillow-sane/i386 (2.9.1-3 to 2.9.1-3): Will attempt migration (Any information below is purely informational)
• pillow-sane/ppc64el (2.9.1-3 to 2.9.1-3)
  • Migration status for pillow-sane/ppc64el (2.9.1-3 to 2.9.1-3): Will attempt migration (Any information below is purely informational)
• pistache/arm64 (0.0.5+ds-5 to 0.0.5+ds-5)
  • Migration status for pistache/arm64 (0.0.5+ds-5 to 0.0.5+ds-5): Will attempt migration (Any information below is purely informational)
• pistache/armel (0.0.5+ds-5 to 0.0.5+ds-5)
  • Migration status for pistache/armel (0.0.5+ds-5 to 0.0.5+ds-5): Will attempt migration (Any information below is purely informational)
• pistache/armhf (0.0.5+ds-5 to 0.0.5+ds-5)
  • Migration status for pistache/armhf (0.0.5+ds-5 to 0.0.5+ds-5): Will attempt migration (Any information below is purely informational)
• pistache/i386 (0.0.5+ds-5 to 0.0.5+ds-5)
  • Migration status for pistache/i386 (0.0.5+ds-5 to 0.0.5+ds-5): Will attempt migration (Any information below is purely informational)
• pistache/s390x (0.0.5+ds-5 to 0.0.5+ds-5)
  • Migration status for pistache/s390x (0.0.5+ds-5 to 0.0.5+ds-5): Will attempt migration (Any information below is purely informational)
• pixman/arm64 (0.42.2-1 to 0.42.2-1)
  • Migration status for pixman/arm64 (0.42.2-1 to 0.42.2-1): Will attempt migration (Any information below is purely informational)
• pixman/armel (0.42.2-1 to 0.42.2-1)
  • Migration status for pixman/armel (0.42.2-1 to 0.42.2-1): Will attempt migration (Any information below is purely informational)
• pixman/armhf (0.42.2-1 to 0.42.2-1)
  • Migration status for pixman/armhf (0.42.2-1 to 0.42.2-1): Will attempt migration (Any information below is purely informational)
• pixman/i386 (0.42.2-1 to 0.42.2-1)
  • Migration status for pixman/i386 (0.42.2-1 to 0.42.2-1): Will attempt migration (Any information below is purely informational)
• pixman/ppc64el (0.42.2-1 to 0.42.2-1)
  • Migration status for pixman/ppc64el (0.42.2-1 to 0.42.2-1): Will attempt migration (Any information below is purely informational)
• pkcs11-helper/arm64 (1.29.0-2 to 1.29.0-2)
  • Migration status for pkcs11-helper/arm64 (1.29.0-2 to 1.29.0-2): Will attempt migration (Any information below is purely informational)
• pkcs11-helper/armel (1.29.0-2 to 1.29.0-2)
  • Migration status for pkcs11-helper/armel (1.29.0-2 to 1.29.0-2): Will attempt migration (Any information below is purely informational)
• pkcs11-helper/armhf (1.29.0-2 to 1.29.0-2)
  • Migration status for pkcs11-helper/armhf (1.29.0-2 to 1.29.0-2): Will attempt migration (Any information below is purely informational)
• pkcs11-helper/i386 (1.29.0-2 to 1.29.0-2)
  • Migration status for pkcs11-helper/i386 (1.29.0-2 to 1.29.0-2): Will attempt migration (Any information below is purely informational)
• pkcs11-helper/ppc64el (1.29.0-2 to 1.29.0-2)
  • Migration status for pkcs11-helper/ppc64el (1.29.0-2 to 1.29.0-2): Will attempt migration (Any information below is purely informational)
• plank/arm64 (0.11.89-4.1 to 0.11.89-4.1)
  • Migration status for plank/arm64 (0.11.89-4.1 to 0.11.89-4.1): Will attempt migration (Any information below is purely informational)
• plank/armel (0.11.89-4.1 to 0.11.89-4.1)
  • Migration status for plank/armel (0.11.89-4.1 to 0.11.89-4.1): Will attempt migration (Any information below is purely informational)
• plank/armhf (0.11.89-4.1 to 0.11.89-4.1)
  • Migration status for plank/armhf (0.11.89-4.1 to 0.11.89-4.1): Will attempt migration (Any information below is purely informational)
• plank/i386 (0.11.89-4.1 to 0.11.89-4.1)
  • Migration status for plank/i386 (0.11.89-4.1 to 0.11.89-4.1): Will attempt migration (Any information below is purely informational)
• plank/ppc64el (0.11.89-4.1 to 0.11.89-4.1)
  • Migration status for plank/ppc64el (0.11.89-4.1 to 0.11.89-4.1): Will attempt migration (Any information below is purely informational)
• plasma-framework/arm64 (5.107.0-1 to 5.107.0-1)
  • Migration status for plasma-framework/arm64 (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• plasma-framework/armel (5.107.0-1 to 5.107.0-1)
  • Migration status for plasma-framework/armel (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• plasma-framework/armhf (5.107.0-1 to 5.107.0-1)
  • Migration status for plasma-framework/armhf (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• plasma-framework/i386 (5.107.0-1 to 5.107.0-1)
  • Migration status for plasma-framework/i386 (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• plasma-framework/ppc64el (5.107.0-1 to 5.107.0-1)
  • Migration status for plasma-framework/ppc64el (5.107.0-1 to 5.107.0-1): 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/armel (1.3+dfsg-3 to 1.3+dfsg-3)
  • Migration status for plasmidseeker/armel (1.3+dfsg-3 to 1.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• plasmidseeker/armhf (1.3+dfsg-3 to 1.3+dfsg-3)
  • Migration status for plasmidseeker/armhf (1.3+dfsg-3 to 1.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• plasmidseeker/i386 (1.3+dfsg-3 to 1.3+dfsg-3)
  • Migration status for plasmidseeker/i386 (1.3+dfsg-3 to 1.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• plasmidseeker/ppc64el (1.3+dfsg-3 to 1.3+dfsg-3)
  • Migration status for plasmidseeker/ppc64el (1.3+dfsg-3 to 1.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• playerctl/arm64 (2.4.1-2 to 2.4.1-2)
  • Migration status for playerctl/arm64 (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
• playerctl/armel (2.4.1-2 to 2.4.1-2)
  • Migration status for playerctl/armel (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
• playerctl/armhf (2.4.1-2 to 2.4.1-2)
  • Migration status for playerctl/armhf (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
• playerctl/i386 (2.4.1-2 to 2.4.1-2)
  • Migration status for playerctl/i386 (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
• playerctl/ppc64el (2.4.1-2 to 2.4.1-2)
  • Migration status for playerctl/ppc64el (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
• ploop/arm64 (1.15-13 to 1.15-13)
  • Migration status for ploop/arm64 (1.15-13 to 1.15-13): Will attempt migration (Any information below is purely informational)
• ploop/armel (1.15-13 to 1.15-13)
  • Migration status for ploop/armel (1.15-13 to 1.15-13): Will attempt migration (Any information below is purely informational)
• ploop/armhf (1.15-13 to 1.15-13)
  • Migration status for ploop/armhf (1.15-13 to 1.15-13): Will attempt migration (Any information below is purely informational)
• ploop/i386 (1.15-13 to 1.15-13)
  • Migration status for ploop/i386 (1.15-13 to 1.15-13): Will attempt migration (Any information below is purely informational)
• ploop/ppc64el (1.15-13 to 1.15-13)
  • Migration status for ploop/ppc64el (1.15-13 to 1.15-13): Will attempt migration (Any information below is purely informational)
• plotutils/arm64 (2.6-14 to 2.6-14)
  • Migration status for plotutils/arm64 (2.6-14 to 2.6-14): Will attempt migration (Any information below is purely informational)
• plotutils/armhf (2.6-14 to 2.6-14)
  • Migration status for plotutils/armhf (2.6-14 to 2.6-14): Will attempt migration (Any information below is purely informational)
• plotutils/i386 (2.6-14 to 2.6-14)
  • Migration status for plotutils/i386 (2.6-14 to 2.6-14): Will attempt migration (Any information below is purely informational)
• plotutils/ppc64el (2.6-14 to 2.6-14)
  • Migration status for plotutils/ppc64el (2.6-14 to 2.6-14): Will attempt migration (Any information below is purely informational)
• pmdk/arm64 (1.13.1-1.1 to 1.13.1-1.1)
  • Migration status for pmdk/arm64 (1.13.1-1.1 to 1.13.1-1.1): Will attempt migration (Any information below is purely informational)
• pmix/arm64 (5.0.1-4 to 5.0.1-4)
  • Migration status for pmix/arm64 (5.0.1-4 to 5.0.1-4): Will attempt migration (Any information below is purely informational)
• pmix/armel (5.0.1-4 to 5.0.1-4)
  • Migration status for pmix/armel (5.0.1-4 to 5.0.1-4): Will attempt migration (Any information below is purely informational)
• pmix/armhf (5.0.1-4 to 5.0.1-4)
  • Migration status for pmix/armhf (5.0.1-4 to 5.0.1-4): Will attempt migration (Any information below is purely informational)
• pmix/i386 (5.0.1-4 to 5.0.1-4)
  • Migration status for pmix/i386 (5.0.1-4 to 5.0.1-4): Will attempt migration (Any information below is purely informational)
• pmix/ppc64el (5.0.1-4 to 5.0.1-4)
  • Migration status for pmix/ppc64el (5.0.1-4 to 5.0.1-4): Will attempt migration (Any information below is purely informational)
• pnetcdf/arm64 (1.12.3-2 to 1.12.3-2)
  • Migration status for pnetcdf/arm64 (1.12.3-2 to 1.12.3-2): Will attempt migration (Any information below is purely informational)
• pnetcdf/ppc64el (1.12.3-2 to 1.12.3-2)
  • Migration status for pnetcdf/ppc64el (1.12.3-2 to 1.12.3-2): Will attempt migration (Any information below is purely informational)
• pnglite/arm64 (0.1.17-3 to 0.1.17-3)
  • Migration status for pnglite/arm64 (0.1.17-3 to 0.1.17-3): Will attempt migration (Any information below is purely informational)
• pnglite/armel (0.1.17-3 to 0.1.17-3)
  • Migration status for pnglite/armel (0.1.17-3 to 0.1.17-3): Will attempt migration (Any information below is purely informational)
• pnglite/armhf (0.1.17-3 to 0.1.17-3)
  • Migration status for pnglite/armhf (0.1.17-3 to 0.1.17-3): Will attempt migration (Any information below is purely informational)
• pnglite/i386 (0.1.17-3 to 0.1.17-3)
  • Migration status for pnglite/i386 (0.1.17-3 to 0.1.17-3): Will attempt migration (Any information below is purely informational)
• pnglite/ppc64el (0.1.17-3 to 0.1.17-3)
  • Migration status for pnglite/ppc64el (0.1.17-3 to 0.1.17-3): Will attempt migration (Any information below is purely informational)
• pocketsphinx/arm64 (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15)
  • Migration status for pocketsphinx/arm64 (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15): Will attempt migration (Any information below is purely informational)
• pocketsphinx/armel (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15)
  • Migration status for pocketsphinx/armel (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15): Will attempt migration (Any information below is purely informational)
• pocketsphinx/armhf (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15)
  • Migration status for pocketsphinx/armhf (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15): Will attempt migration (Any information below is purely informational)
• pocketsphinx/i386 (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15)
  • Migration status for pocketsphinx/i386 (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15): Will attempt migration (Any information below is purely informational)
• pocketsphinx/ppc64el (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15)
  • Migration status for pocketsphinx/ppc64el (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15): Will attempt migration (Any information below is purely informational)
• poezio/arm64 (0.14-3 to 0.14-3)
  • Migration status for poezio/arm64 (0.14-3 to 0.14-3): Will attempt migration (Any information below is purely informational)
• poezio/armel (0.14-3 to 0.14-3)
  • Migration status for poezio/armel (0.14-3 to 0.14-3): Will attempt migration (Any information below is purely informational)
• poezio/armhf (0.14-3 to 0.14-3)
  • Migration status for poezio/armhf (0.14-3 to 0.14-3): Will attempt migration (Any information below is purely informational)
• poezio/i386 (0.14-3 to 0.14-3)
  • Migration status for poezio/i386 (0.14-3 to 0.14-3): Will attempt migration (Any information below is purely informational)
• poezio/ppc64el (0.14-3 to 0.14-3)
  • Migration status for poezio/ppc64el (0.14-3 to 0.14-3): Will attempt migration (Any information below is purely informational)
• poldi/arm64 (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2)
  • Migration status for poldi/arm64 (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2): Will attempt migration (Any information below is purely informational)
• poldi/armel (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2)
  • Migration status for poldi/armel (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2): Will attempt migration (Any information below is purely informational)
• poldi/armhf (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2)
  • Migration status for poldi/armhf (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2): Will attempt migration (Any information below is purely informational)
• poldi/i386 (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2)
  • Migration status for poldi/i386 (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2): Will attempt migration (Any information below is purely informational)
• poldi/ppc64el (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2)
  • Migration status for poldi/ppc64el (0.4.2+git20161115.553060d-1.2 to 0.4.2+git20161115.553060d-1.2): Will attempt migration (Any information below is purely informational)
• polkit-qt-1/arm64 (0.114.0-2 to 0.114.0-2)
  • Migration status for polkit-qt-1/arm64 (0.114.0-2 to 0.114.0-2): Will attempt migration (Any information below is purely informational)
• polkit-qt-1/armel (0.114.0-2 to 0.114.0-2)
  • Migration status for polkit-qt-1/armel (0.114.0-2 to 0.114.0-2): Will attempt migration (Any information below is purely informational)
• polkit-qt-1/armhf (0.114.0-2 to 0.114.0-2)
  • Migration status for polkit-qt-1/armhf (0.114.0-2 to 0.114.0-2): Will attempt migration (Any information below is purely informational)
• polkit-qt-1/i386 (0.114.0-2 to 0.114.0-2)
  • Migration status for polkit-qt-1/i386 (0.114.0-2 to 0.114.0-2): Will attempt migration (Any information below is purely informational)
• polkit-qt-1/ppc64el (0.114.0-2 to 0.114.0-2)
  • Migration status for polkit-qt-1/ppc64el (0.114.0-2 to 0.114.0-2): Will attempt migration (Any information below is purely informational)
• popt/arm64 (1.19+dfsg-1 to 1.19+dfsg-1)
  • Migration status for popt/arm64 (1.19+dfsg-1 to 1.19+dfsg-1): Will attempt migration (Any information below is purely informational)
• popt/armel (1.19+dfsg-1 to 1.19+dfsg-1)
  • Migration status for popt/armel (1.19+dfsg-1 to 1.19+dfsg-1): Will attempt migration (Any information below is purely informational)
• popt/armhf (1.19+dfsg-1 to 1.19+dfsg-1)
  • Migration status for popt/armhf (1.19+dfsg-1 to 1.19+dfsg-1): Will attempt migration (Any information below is purely informational)
• popt/i386 (1.19+dfsg-1 to 1.19+dfsg-1)
  • Migration status for popt/i386 (1.19+dfsg-1 to 1.19+dfsg-1): Will attempt migration (Any information below is purely informational)
• popt/ppc64el (1.19+dfsg-1 to 1.19+dfsg-1)
  • Migration status for popt/ppc64el (1.19+dfsg-1 to 1.19+dfsg-1): Will attempt migration (Any information below is purely informational)
• portaudio19/arm64 (19.6.0-1.2 to 19.6.0-1.2)
  • Migration status for portaudio19/arm64 (19.6.0-1.2 to 19.6.0-1.2): Will attempt migration (Any information below is purely informational)
• portaudio19/armel (19.6.0-1.2 to 19.6.0-1.2)
  • Migration status for portaudio19/armel (19.6.0-1.2 to 19.6.0-1.2): Will attempt migration (Any information below is purely informational)
• portaudio19/armhf (19.6.0-1.2 to 19.6.0-1.2)
  • Migration status for portaudio19/armhf (19.6.0-1.2 to 19.6.0-1.2): Will attempt migration (Any information below is purely informational)
• portaudio19/i386 (19.6.0-1.2 to 19.6.0-1.2)
  • Migration status for portaudio19/i386 (19.6.0-1.2 to 19.6.0-1.2): Will attempt migration (Any information below is purely informational)
• portaudio19/ppc64el (19.6.0-1.2 to 19.6.0-1.2)
  • Migration status for portaudio19/ppc64el (19.6.0-1.2 to 19.6.0-1.2): Will attempt migration (Any information below is purely informational)
• portmidi/arm64 (1:217-6.1 to 1:217-6.1)
  • Migration status for portmidi/arm64 (1:217-6.1 to 1:217-6.1): Will attempt migration (Any information below is purely informational)
• portmidi/armel (1:217-6.1 to 1:217-6.1)
  • Migration status for portmidi/armel (1:217-6.1 to 1:217-6.1): Will attempt migration (Any information below is purely informational)
• portmidi/armhf (1:217-6.1 to 1:217-6.1)
  • Migration status for portmidi/armhf (1:217-6.1 to 1:217-6.1): Will attempt migration (Any information below is purely informational)
• portmidi/i386 (1:217-6.1 to 1:217-6.1)
  • Migration status for portmidi/i386 (1:217-6.1 to 1:217-6.1): Will attempt migration (Any information below is purely informational)
• portmidi/ppc64el (1:217-6.1 to 1:217-6.1)
  • Migration status for portmidi/ppc64el (1:217-6.1 to 1:217-6.1): Will attempt migration (Any information below is purely informational)
• portsmf/arm64 (0.1~svn20101010-6 to 0.1~svn20101010-6)
  • Migration status for portsmf/arm64 (0.1~svn20101010-6 to 0.1~svn20101010-6): Will attempt migration (Any information below is purely informational)
• portsmf/armel (0.1~svn20101010-6 to 0.1~svn20101010-6)
  • Migration status for portsmf/armel (0.1~svn20101010-6 to 0.1~svn20101010-6): Will attempt migration (Any information below is purely informational)
• portsmf/armhf (0.1~svn20101010-6 to 0.1~svn20101010-6)
  • Migration status for portsmf/armhf (0.1~svn20101010-6 to 0.1~svn20101010-6): Will attempt migration (Any information below is purely informational)
• portsmf/i386 (0.1~svn20101010-6 to 0.1~svn20101010-6)
  • Migration status for portsmf/i386 (0.1~svn20101010-6 to 0.1~svn20101010-6): Will attempt migration (Any information below is purely informational)
• portsmf/ppc64el (0.1~svn20101010-6 to 0.1~svn20101010-6)
  • Migration status for portsmf/ppc64el (0.1~svn20101010-6 to 0.1~svn20101010-6): Will attempt migration (Any information below is purely informational)
• posixsignalmanager/arm64 (0.3-4 to 0.3-4)
  • Migration status for posixsignalmanager/arm64 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• posixsignalmanager/armel (0.3-4 to 0.3-4)
  • Migration status for posixsignalmanager/armel (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• posixsignalmanager/armhf (0.3-4 to 0.3-4)
  • Migration status for posixsignalmanager/armhf (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• posixsignalmanager/i386 (0.3-4 to 0.3-4)
  • Migration status for posixsignalmanager/i386 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• posixsignalmanager/ppc64el (0.3-4 to 0.3-4)
  • Migration status for posixsignalmanager/ppc64el (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• posixtestsuite/arm64 (1.5.2-8 to 1.5.2-8)
  • Migration status for posixtestsuite/arm64 (1.5.2-8 to 1.5.2-8): Will attempt migration (Any information below is purely informational)
• posixtestsuite/armhf (1.5.2-8 to 1.5.2-8)
  • Migration status for posixtestsuite/armhf (1.5.2-8 to 1.5.2-8): Will attempt migration (Any information below is purely informational)
• posixtestsuite/i386 (1.5.2-8 to 1.5.2-8)
  • Migration status for posixtestsuite/i386 (1.5.2-8 to 1.5.2-8): Will attempt migration (Any information below is purely informational)
• posixtestsuite/ppc64el (1.5.2-8 to 1.5.2-8)
  • Migration status for posixtestsuite/ppc64el (1.5.2-8 to 1.5.2-8): Will attempt migration (Any information below is purely informational)
• postgresql-15_pu (- to 15.6-0+deb12u1)
  • Migration status for postgresql-15_pu (- to 15.6-0+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • postgresql-plperl-15/amd64 has unsatisfiable dependency
    • postgresql-plperl-15/arm64 has unsatisfiable dependency
    • postgresql-plperl-15/armel has unsatisfiable dependency
    • postgresql-plperl-15/armhf has unsatisfiable dependency
    • postgresql-plperl-15/i386 has unsatisfiable dependency
    • postgresql-plperl-15/mips64el has unsatisfiable dependency
    • postgresql-plperl-15/ppc64el has unsatisfiable dependency
    • postgresql-plperl-15/s390x has unsatisfiable dependency
    • NEEDS APPROVAL BY RM
• potrace/arm64 (1.16-2 to 1.16-2)
  • Migration status for potrace/arm64 (1.16-2 to 1.16-2): Will attempt migration (Any information below is purely informational)
• potrace/armel (1.16-2 to 1.16-2)
  • Migration status for potrace/armel (1.16-2 to 1.16-2): Will attempt migration (Any information below is purely informational)
• potrace/armhf (1.16-2 to 1.16-2)
  • Migration status for potrace/armhf (1.16-2 to 1.16-2): Will attempt migration (Any information below is purely informational)
• potrace/i386 (1.16-2 to 1.16-2)
  • Migration status for potrace/i386 (1.16-2 to 1.16-2): Will attempt migration (Any information below is purely informational)
• potrace/ppc64el (1.16-2 to 1.16-2)
  • Migration status for potrace/ppc64el (1.16-2 to 1.16-2): Will attempt migration (Any information below is purely informational)
• powercap/arm64 (0.6.0-1 to 0.6.0-1)
  • Migration status for powercap/arm64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• powercap/armel (0.6.0-1 to 0.6.0-1)
  • Migration status for powercap/armel (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• powercap/armhf (0.6.0-1 to 0.6.0-1)
  • Migration status for powercap/armhf (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• powercap/i386 (0.6.0-1 to 0.6.0-1)
  • Migration status for powercap/i386 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• powercap/ppc64el (0.6.0-1 to 0.6.0-1)
  • Migration status for powercap/ppc64el (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• ppx-assert/amd64 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-assert/amd64 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-assert/amd64 ppx-compare/amd64
    • Depends: ppx-assert/amd64 ppx-here/amd64
    • Depends: ppx-assert/amd64 ppx-sexp-conv/amd64
    • Depends: ppx-assert/amd64 ppxlib
• ppx-assert/arm64 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-assert/arm64 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-assert/arm64 ppx-compare/arm64
    • Depends: ppx-assert/arm64 ppx-here/arm64
    • Depends: ppx-assert/arm64 ppx-sexp-conv/arm64
    • Depends: ppx-assert/arm64 ppxlib
• ppx-assert/armel (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-assert/armel (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-assert/armel ppx-compare/armel
    • Depends: ppx-assert/armel ppx-here/armel
    • Depends: ppx-assert/armel ppx-sexp-conv/armel
    • Depends: ppx-assert/armel ppxlib
• ppx-assert/armhf (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-assert/armhf (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-assert/armhf ppx-compare/armhf
    • Depends: ppx-assert/armhf ppx-here/armhf
    • Depends: ppx-assert/armhf ppx-sexp-conv/armhf
    • Depends: ppx-assert/armhf ppxlib
• ppx-assert/i386 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-assert/i386 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-assert/i386 ppx-compare/i386
    • Depends: ppx-assert/i386 ppx-here/i386
    • Depends: ppx-assert/i386 ppx-sexp-conv/i386
    • Depends: ppx-assert/i386 ppxlib
• ppx-assert/mips64el (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-assert/mips64el (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-assert/mips64el ppx-compare/mips64el
    • Depends: ppx-assert/mips64el ppx-here/mips64el
    • Depends: ppx-assert/mips64el ppx-sexp-conv/mips64el
    • Depends: ppx-assert/mips64el ppxlib
• ppx-assert/ppc64el (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-assert/ppc64el (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-assert/ppc64el ppx-compare/ppc64el
    • Depends: ppx-assert/ppc64el ppx-here/ppc64el
    • Depends: ppx-assert/ppc64el ppx-sexp-conv/ppc64el
    • Depends: ppx-assert/ppc64el ppxlib
• ppx-assert/s390x (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-assert/s390x (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-assert/s390x ppx-compare/s390x
    • Depends: ppx-assert/s390x ppx-here/s390x
    • Depends: ppx-assert/s390x ppx-sexp-conv/s390x
    • Depends: ppx-assert/s390x ppxlib
• ppx-bin-prot/amd64 (0.16.0-3 to 0.16.0-3)
  • Migration status for ppx-bin-prot/amd64 (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-bin-prot/amd64 ppx-here/amd64
    • Depends: ppx-bin-prot/amd64 ppxlib
• ppx-bin-prot/arm64 (0.16.0-3 to 0.16.0-3)
  • Migration status for ppx-bin-prot/arm64 (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-bin-prot/arm64 ppx-here/arm64
    • Depends: ppx-bin-prot/arm64 ppxlib
• ppx-bin-prot/armel (0.16.0-3 to 0.16.0-3)
  • Migration status for ppx-bin-prot/armel (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-bin-prot/armel ppx-here/armel
    • Depends: ppx-bin-prot/armel ppxlib
• ppx-bin-prot/armhf (0.16.0-3 to 0.16.0-3)
  • Migration status for ppx-bin-prot/armhf (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-bin-prot/armhf ppx-here/armhf
    • Depends: ppx-bin-prot/armhf ppxlib
• ppx-bin-prot/i386 (0.16.0-3 to 0.16.0-3)
  • Migration status for ppx-bin-prot/i386 (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-bin-prot/i386 ppx-here/i386
    • Depends: ppx-bin-prot/i386 ppxlib
• ppx-bin-prot/mips64el (0.16.0-3 to 0.16.0-3)
  • Migration status for ppx-bin-prot/mips64el (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-bin-prot/mips64el ppx-here/mips64el
    • Depends: ppx-bin-prot/mips64el ppxlib
• ppx-bin-prot/ppc64el (0.16.0-3 to 0.16.0-3)
  • Migration status for ppx-bin-prot/ppc64el (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-bin-prot/ppc64el ppx-here/ppc64el
    • Depends: ppx-bin-prot/ppc64el ppxlib
• ppx-bin-prot/s390x (0.16.0-3 to 0.16.0-3)
  • Migration status for ppx-bin-prot/s390x (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-bin-prot/s390x ppx-here/s390x
    • Depends: ppx-bin-prot/s390x ppxlib
• ppx-cold/amd64 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-cold/amd64 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-cold/amd64 ppxlib
• ppx-cold/arm64 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-cold/arm64 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-cold/arm64 ppxlib
• ppx-cold/armel (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-cold/armel (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-cold/armel ppxlib
• ppx-cold/armhf (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-cold/armhf (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-cold/armhf ppxlib
• ppx-cold/i386 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-cold/i386 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-cold/i386 ppxlib
• ppx-cold/mips64el (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-cold/mips64el (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-cold/mips64el ppxlib
• ppx-cold/ppc64el (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-cold/ppc64el (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-cold/ppc64el ppxlib
• ppx-cold/s390x (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-cold/s390x (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-cold/s390x ppxlib
• ppx-compare/amd64 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-compare/amd64 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-compare/amd64 ppxlib
    • Implicit dependency: ppx-compare/amd64 bin-prot
    • Implicit dependency: ppx-compare/amd64 ppx-assert/amd64
    • Implicit dependency: ppx-compare/amd64 ppx-hash/amd64
• ppx-compare/arm64 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-compare/arm64 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-compare/arm64 ppxlib
    • Implicit dependency: ppx-compare/arm64 bin-prot
    • Implicit dependency: ppx-compare/arm64 ppx-assert/arm64
    • Implicit dependency: ppx-compare/arm64 ppx-hash/arm64
• ppx-compare/armel (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-compare/armel (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-compare/armel ppxlib
    • Implicit dependency: ppx-compare/armel bin-prot
    • Implicit dependency: ppx-compare/armel ppx-assert/armel
    • Implicit dependency: ppx-compare/armel ppx-hash/armel
• ppx-compare/armhf (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-compare/armhf (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-compare/armhf ppxlib
    • Implicit dependency: ppx-compare/armhf bin-prot
    • Implicit dependency: ppx-compare/armhf ppx-assert/armhf
    • Implicit dependency: ppx-compare/armhf ppx-hash/armhf
• ppx-compare/i386 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-compare/i386 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-compare/i386 ppxlib
    • Implicit dependency: ppx-compare/i386 bin-prot
    • Implicit dependency: ppx-compare/i386 ppx-assert/i386
    • Implicit dependency: ppx-compare/i386 ppx-hash/i386
• ppx-compare/mips64el (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-compare/mips64el (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-compare/mips64el ppxlib
    • Implicit dependency: ppx-compare/mips64el bin-prot
    • Implicit dependency: ppx-compare/mips64el ppx-assert/mips64el
    • Implicit dependency: ppx-compare/mips64el ppx-hash/mips64el
• ppx-compare/ppc64el (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-compare/ppc64el (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-compare/ppc64el ppxlib
    • Implicit dependency: ppx-compare/ppc64el bin-prot
    • Implicit dependency: ppx-compare/ppc64el ppx-assert/ppc64el
    • Implicit dependency: ppx-compare/ppc64el ppx-hash/ppc64el
• ppx-compare/s390x (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-compare/s390x (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-compare/s390x ppxlib
    • Implicit dependency: ppx-compare/s390x bin-prot
    • Implicit dependency: ppx-compare/s390x ppx-assert/s390x
    • Implicit dependency: ppx-compare/s390x ppx-hash/s390x
• ppx-custom-printf/amd64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-custom-printf/amd64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-custom-printf/amd64 ppx-sexp-conv/amd64
    • Depends: ppx-custom-printf/amd64 ppxlib
• ppx-custom-printf/arm64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-custom-printf/arm64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-custom-printf/arm64 ppx-sexp-conv/arm64
    • Depends: ppx-custom-printf/arm64 ppxlib
• ppx-custom-printf/armel (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-custom-printf/armel (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-custom-printf/armel ppx-sexp-conv/armel
    • Depends: ppx-custom-printf/armel ppxlib
• ppx-custom-printf/armhf (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-custom-printf/armhf (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-custom-printf/armhf ppx-sexp-conv/armhf
    • Depends: ppx-custom-printf/armhf ppxlib
• ppx-custom-printf/i386 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-custom-printf/i386 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-custom-printf/i386 ppx-sexp-conv/i386
    • Depends: ppx-custom-printf/i386 ppxlib
• ppx-custom-printf/mips64el (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-custom-printf/mips64el (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-custom-printf/mips64el ppx-sexp-conv/mips64el
    • Depends: ppx-custom-printf/mips64el ppxlib
• ppx-custom-printf/ppc64el (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-custom-printf/ppc64el (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-custom-printf/ppc64el ppx-sexp-conv/ppc64el
    • Depends: ppx-custom-printf/ppc64el ppxlib
• ppx-custom-printf/s390x (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-custom-printf/s390x (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-custom-printf/s390x ppx-sexp-conv/s390x
    • Depends: ppx-custom-printf/s390x ppxlib
• ppx-deriving-yojson/amd64 (3.7.0-4 to 3.7.0-4)
  • Migration status for ppx-deriving-yojson/amd64 (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving-yojson/amd64 ppx-deriving/amd64
    • Depends: ppx-deriving-yojson/amd64 ppxlib
    • Implicit dependency: ppx-deriving-yojson/amd64 morbig/amd64
    • Implicit dependency: ppx-deriving-yojson/amd64 morsmall/amd64
• ppx-deriving-yojson/arm64 (3.7.0-4 to 3.7.0-4)
  • Migration status for ppx-deriving-yojson/arm64 (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving-yojson/arm64 ppx-deriving/arm64
    • Depends: ppx-deriving-yojson/arm64 ppxlib
    • Implicit dependency: ppx-deriving-yojson/arm64 morbig/arm64
    • Implicit dependency: ppx-deriving-yojson/arm64 morsmall/arm64
• ppx-deriving-yojson/armel (3.7.0-4 to 3.7.0-4)
  • Migration status for ppx-deriving-yojson/armel (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving-yojson/armel ppx-deriving/armel
    • Depends: ppx-deriving-yojson/armel ppxlib
    • Implicit dependency: ppx-deriving-yojson/armel morbig/armel
    • Implicit dependency: ppx-deriving-yojson/armel morsmall/armel
• ppx-deriving-yojson/armhf (3.7.0-4 to 3.7.0-4)
  • Migration status for ppx-deriving-yojson/armhf (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving-yojson/armhf ppx-deriving/armhf
    • Depends: ppx-deriving-yojson/armhf ppxlib
    • Implicit dependency: ppx-deriving-yojson/armhf morbig/armhf
    • Implicit dependency: ppx-deriving-yojson/armhf morsmall/armhf
• ppx-deriving-yojson/i386 (3.7.0-4 to 3.7.0-4)
  • Migration status for ppx-deriving-yojson/i386 (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving-yojson/i386 ppx-deriving/i386
    • Depends: ppx-deriving-yojson/i386 ppxlib
    • Implicit dependency: ppx-deriving-yojson/i386 morbig/i386
    • Implicit dependency: ppx-deriving-yojson/i386 morsmall/i386
• ppx-deriving-yojson/mips64el (3.7.0-4 to 3.7.0-4)
  • Migration status for ppx-deriving-yojson/mips64el (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving-yojson/mips64el ppx-deriving/mips64el
    • Depends: ppx-deriving-yojson/mips64el ppxlib
    • Implicit dependency: ppx-deriving-yojson/mips64el morbig/mips64el
    • Implicit dependency: ppx-deriving-yojson/mips64el morsmall/mips64el
• ppx-deriving-yojson/ppc64el (3.7.0-4 to 3.7.0-4)
  • Migration status for ppx-deriving-yojson/ppc64el (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving-yojson/ppc64el ppx-deriving/ppc64el
    • Depends: ppx-deriving-yojson/ppc64el ppxlib
    • Implicit dependency: ppx-deriving-yojson/ppc64el morbig/ppc64el
    • Implicit dependency: ppx-deriving-yojson/ppc64el morsmall/ppc64el
• ppx-deriving-yojson/s390x (3.7.0-4 to 3.7.0-4)
  • Migration status for ppx-deriving-yojson/s390x (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving-yojson/s390x ppx-deriving/s390x
    • Depends: ppx-deriving-yojson/s390x ppxlib
    • Implicit dependency: ppx-deriving-yojson/s390x morbig/s390x
    • Implicit dependency: ppx-deriving-yojson/s390x morsmall/s390x
• ppx-deriving/amd64 (5.2.1-4 to 5.2.1-4)
  • Migration status for ppx-deriving/amd64 (5.2.1-4 to 5.2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving/amd64 ppxlib
    • Implicit dependency: ppx-deriving/amd64 elpi/amd64
    • Implicit dependency: ppx-deriving/amd64 frama-c/amd64
    • Implicit dependency: ppx-deriving/amd64 morbig/amd64
    • Implicit dependency: ppx-deriving/amd64 morsmall/amd64
    • Implicit dependency: ppx-deriving/amd64 ocaml-visitors/amd64
    • Implicit dependency: ppx-deriving/amd64 ocsipersist/amd64
    • Implicit dependency: ppx-deriving/amd64 pgocaml/amd64
    • Implicit dependency: ppx-deriving/amd64 ppx-deriving-yojson/amd64
• ppx-deriving/arm64 (5.2.1-4 to 5.2.1-4)
  • Migration status for ppx-deriving/arm64 (5.2.1-4 to 5.2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving/arm64 ppxlib
    • Implicit dependency: ppx-deriving/arm64 elpi/arm64
    • Implicit dependency: ppx-deriving/arm64 frama-c/arm64
    • Implicit dependency: ppx-deriving/arm64 morbig/arm64
    • Implicit dependency: ppx-deriving/arm64 morsmall/arm64
    • Implicit dependency: ppx-deriving/arm64 ocaml-visitors/arm64
    • Implicit dependency: ppx-deriving/arm64 ocsipersist/arm64
    • Implicit dependency: ppx-deriving/arm64 pgocaml/arm64
    • Implicit dependency: ppx-deriving/arm64 ppx-deriving-yojson/arm64
• ppx-deriving/armel (5.2.1-4 to 5.2.1-4)
  • Migration status for ppx-deriving/armel (5.2.1-4 to 5.2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving/armel ppxlib
    • Implicit dependency: ppx-deriving/armel frama-c/armel
    • Implicit dependency: ppx-deriving/armel morbig/armel
    • Implicit dependency: ppx-deriving/armel morsmall/armel
    • Implicit dependency: ppx-deriving/armel ocaml-visitors/armel
    • Implicit dependency: ppx-deriving/armel ocsipersist/armel
    • Implicit dependency: ppx-deriving/armel pgocaml/armel
    • Implicit dependency: ppx-deriving/armel ppx-deriving-yojson/armel
• ppx-deriving/armhf (5.2.1-4 to 5.2.1-4)
  • Migration status for ppx-deriving/armhf (5.2.1-4 to 5.2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving/armhf ppxlib
    • Implicit dependency: ppx-deriving/armhf elpi/armhf
    • Implicit dependency: ppx-deriving/armhf frama-c/armhf
    • Implicit dependency: ppx-deriving/armhf morbig/armhf
    • Implicit dependency: ppx-deriving/armhf morsmall/armhf
    • Implicit dependency: ppx-deriving/armhf ocaml-visitors/armhf
    • Implicit dependency: ppx-deriving/armhf ocsipersist/armhf
    • Implicit dependency: ppx-deriving/armhf pgocaml/armhf
    • Implicit dependency: ppx-deriving/armhf ppx-deriving-yojson/armhf
• ppx-deriving/i386 (5.2.1-4 to 5.2.1-4)
  • Migration status for ppx-deriving/i386 (5.2.1-4 to 5.2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving/i386 ppxlib
    • Implicit dependency: ppx-deriving/i386 elpi/i386
    • Implicit dependency: ppx-deriving/i386 frama-c/i386
    • Implicit dependency: ppx-deriving/i386 morbig/i386
    • Implicit dependency: ppx-deriving/i386 morsmall/i386
    • Implicit dependency: ppx-deriving/i386 ocaml-visitors/i386
    • Implicit dependency: ppx-deriving/i386 ocsipersist/i386
    • Implicit dependency: ppx-deriving/i386 pgocaml/i386
    • Implicit dependency: ppx-deriving/i386 ppx-deriving-yojson/i386
• ppx-deriving/mips64el (5.2.1-4 to 5.2.1-4)
  • Migration status for ppx-deriving/mips64el (5.2.1-4 to 5.2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving/mips64el ppxlib
    • Implicit dependency: ppx-deriving/mips64el frama-c/mips64el
    • Implicit dependency: ppx-deriving/mips64el morbig/mips64el
    • Implicit dependency: ppx-deriving/mips64el morsmall/mips64el
    • Implicit dependency: ppx-deriving/mips64el ocaml-visitors/mips64el
    • Implicit dependency: ppx-deriving/mips64el ocsipersist/mips64el
    • Implicit dependency: ppx-deriving/mips64el pgocaml/mips64el
    • Implicit dependency: ppx-deriving/mips64el ppx-deriving-yojson/mips64el
• ppx-deriving/ppc64el (5.2.1-4 to 5.2.1-4)
  • Migration status for ppx-deriving/ppc64el (5.2.1-4 to 5.2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving/ppc64el ppxlib
    • Implicit dependency: ppx-deriving/ppc64el elpi/ppc64el
    • Implicit dependency: ppx-deriving/ppc64el frama-c/ppc64el
    • Implicit dependency: ppx-deriving/ppc64el morbig/ppc64el
    • Implicit dependency: ppx-deriving/ppc64el morsmall/ppc64el
    • Implicit dependency: ppx-deriving/ppc64el ocaml-visitors/ppc64el
    • Implicit dependency: ppx-deriving/ppc64el ocsipersist/ppc64el
    • Implicit dependency: ppx-deriving/ppc64el pgocaml/ppc64el
    • Implicit dependency: ppx-deriving/ppc64el ppx-deriving-yojson/ppc64el
• ppx-deriving/s390x (5.2.1-4 to 5.2.1-4)
  • Migration status for ppx-deriving/s390x (5.2.1-4 to 5.2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-deriving/s390x ppxlib
    • Implicit dependency: ppx-deriving/s390x elpi/s390x
    • Implicit dependency: ppx-deriving/s390x frama-c/s390x
    • Implicit dependency: ppx-deriving/s390x morbig/s390x
    • Implicit dependency: ppx-deriving/s390x morsmall/s390x
    • Implicit dependency: ppx-deriving/s390x ocaml-visitors/s390x
    • Implicit dependency: ppx-deriving/s390x ocsipersist/s390x
    • Implicit dependency: ppx-deriving/s390x pgocaml/s390x
    • Implicit dependency: ppx-deriving/s390x ppx-deriving-yojson/s390x
• ppx-enumerate/amd64 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-enumerate/amd64 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-enumerate/amd64 ppxlib
• ppx-enumerate/arm64 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-enumerate/arm64 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-enumerate/arm64 ppxlib
• ppx-enumerate/armel (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-enumerate/armel (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-enumerate/armel ppxlib
• ppx-enumerate/armhf (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-enumerate/armhf (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-enumerate/armhf ppxlib
• ppx-enumerate/i386 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-enumerate/i386 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-enumerate/i386 ppxlib
• ppx-enumerate/mips64el (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-enumerate/mips64el (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-enumerate/mips64el ppxlib
• ppx-enumerate/ppc64el (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-enumerate/ppc64el (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-enumerate/ppc64el ppxlib
• ppx-enumerate/s390x (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-enumerate/s390x (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-enumerate/s390x ppxlib
• ppx-expect/amd64 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-expect/amd64 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-expect/amd64 ppx-here/amd64
    • Depends: ppx-expect/amd64 ppx-inline-test/amd64
    • Depends: ppx-expect/amd64 ppxlib
• ppx-expect/arm64 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-expect/arm64 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-expect/arm64 ppx-here/arm64
    • Depends: ppx-expect/arm64 ppx-inline-test/arm64
    • Depends: ppx-expect/arm64 ppxlib
• ppx-expect/armel (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-expect/armel (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-expect/armel ppx-here/armel
    • Depends: ppx-expect/armel ppx-inline-test/armel
    • Depends: ppx-expect/armel ppxlib
• ppx-expect/armhf (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-expect/armhf (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-expect/armhf ppx-here/armhf
    • Depends: ppx-expect/armhf ppx-inline-test/armhf
    • Depends: ppx-expect/armhf ppxlib
• ppx-expect/i386 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-expect/i386 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-expect/i386 ppx-here/i386
    • Depends: ppx-expect/i386 ppx-inline-test/i386
    • Depends: ppx-expect/i386 ppxlib
• ppx-expect/mips64el (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-expect/mips64el (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-expect/mips64el ppx-here/mips64el
    • Depends: ppx-expect/mips64el ppx-inline-test/mips64el
    • Depends: ppx-expect/mips64el ppxlib
• ppx-expect/ppc64el (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-expect/ppc64el (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-expect/ppc64el ppx-here/ppc64el
    • Depends: ppx-expect/ppc64el ppx-inline-test/ppc64el
    • Depends: ppx-expect/ppc64el ppxlib
• ppx-expect/s390x (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-expect/s390x (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-expect/s390x ppx-here/s390x
    • Depends: ppx-expect/s390x ppx-inline-test/s390x
    • Depends: ppx-expect/s390x ppxlib
• ppx-fields-conv/amd64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-fields-conv/amd64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-fields-conv/amd64 ppxlib
• ppx-fields-conv/arm64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-fields-conv/arm64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-fields-conv/arm64 ppxlib
• ppx-fields-conv/armel (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-fields-conv/armel (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-fields-conv/armel ppxlib
• ppx-fields-conv/armhf (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-fields-conv/armhf (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-fields-conv/armhf ppxlib
• ppx-fields-conv/i386 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-fields-conv/i386 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-fields-conv/i386 ppxlib
• ppx-fields-conv/mips64el (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-fields-conv/mips64el (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-fields-conv/mips64el ppxlib
• ppx-fields-conv/ppc64el (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-fields-conv/ppc64el (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-fields-conv/ppc64el ppxlib
• ppx-fields-conv/s390x (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-fields-conv/s390x (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-fields-conv/s390x ppxlib
• ppx-globalize/amd64 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-globalize/amd64 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-globalize/amd64 ppxlib
• ppx-globalize/arm64 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-globalize/arm64 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-globalize/arm64 ppxlib
• ppx-globalize/armel (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-globalize/armel (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-globalize/armel ppxlib
• ppx-globalize/armhf (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-globalize/armhf (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-globalize/armhf ppxlib
• ppx-globalize/i386 (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-globalize/i386 (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-globalize/i386 ppxlib
• ppx-globalize/mips64el (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-globalize/mips64el (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-globalize/mips64el ppxlib
• ppx-globalize/ppc64el (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-globalize/ppc64el (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-globalize/ppc64el ppxlib
• ppx-globalize/s390x (0.16.0-5 to 0.16.0-5)
  • Migration status for ppx-globalize/s390x (0.16.0-5 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-globalize/s390x ppxlib
• ppx-hash/amd64 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-hash/amd64 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-hash/amd64 ppx-compare/amd64
    • Depends: ppx-hash/amd64 ppxlib
• ppx-hash/arm64 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-hash/arm64 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-hash/arm64 ppx-compare/arm64
    • Depends: ppx-hash/arm64 ppxlib
• ppx-hash/armel (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-hash/armel (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-hash/armel ppx-compare/armel
    • Depends: ppx-hash/armel ppxlib
• ppx-hash/armhf (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-hash/armhf (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-hash/armhf ppx-compare/armhf
    • Depends: ppx-hash/armhf ppxlib
• ppx-hash/i386 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-hash/i386 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-hash/i386 ppx-compare/i386
    • Depends: ppx-hash/i386 ppxlib
• ppx-hash/mips64el (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-hash/mips64el (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-hash/mips64el ppx-compare/mips64el
    • Depends: ppx-hash/mips64el ppxlib
• ppx-hash/ppc64el (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-hash/ppc64el (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-hash/ppc64el ppx-compare/ppc64el
    • Depends: ppx-hash/ppc64el ppxlib
• ppx-hash/s390x (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-hash/s390x (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-hash/s390x ppx-compare/s390x
    • Depends: ppx-hash/s390x ppxlib
• ppx-here/amd64 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-here/amd64 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-here/amd64 ppxlib
    • Implicit dependency: ppx-here/amd64 ppx-assert/amd64
    • Implicit dependency: ppx-here/amd64 ppx-bin-prot/amd64
    • Implicit dependency: ppx-here/amd64 ppx-expect/amd64
• ppx-here/arm64 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-here/arm64 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-here/arm64 ppxlib
    • Implicit dependency: ppx-here/arm64 ppx-assert/arm64
    • Implicit dependency: ppx-here/arm64 ppx-bin-prot/arm64
    • Implicit dependency: ppx-here/arm64 ppx-expect/arm64
• ppx-here/armel (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-here/armel (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-here/armel ppxlib
    • Implicit dependency: ppx-here/armel ppx-assert/armel
    • Implicit dependency: ppx-here/armel ppx-bin-prot/armel
    • Implicit dependency: ppx-here/armel ppx-expect/armel
• ppx-here/armhf (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-here/armhf (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-here/armhf ppxlib
    • Implicit dependency: ppx-here/armhf ppx-assert/armhf
    • Implicit dependency: ppx-here/armhf ppx-bin-prot/armhf
    • Implicit dependency: ppx-here/armhf ppx-expect/armhf
• ppx-here/i386 (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-here/i386 (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-here/i386 ppxlib
    • Implicit dependency: ppx-here/i386 ppx-assert/i386
    • Implicit dependency: ppx-here/i386 ppx-bin-prot/i386
    • Implicit dependency: ppx-here/i386 ppx-expect/i386
• ppx-here/mips64el (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-here/mips64el (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-here/mips64el ppxlib
    • Implicit dependency: ppx-here/mips64el ppx-assert/mips64el
    • Implicit dependency: ppx-here/mips64el ppx-bin-prot/mips64el
    • Implicit dependency: ppx-here/mips64el ppx-expect/mips64el
• ppx-here/ppc64el (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-here/ppc64el (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-here/ppc64el ppxlib
    • Implicit dependency: ppx-here/ppc64el ppx-assert/ppc64el
    • Implicit dependency: ppx-here/ppc64el ppx-bin-prot/ppc64el
    • Implicit dependency: ppx-here/ppc64el ppx-expect/ppc64el
• ppx-here/s390x (0.16.0-4 to 0.16.0-4)
  • Migration status for ppx-here/s390x (0.16.0-4 to 0.16.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-here/s390x ppxlib
    • Implicit dependency: ppx-here/s390x ppx-assert/s390x
    • Implicit dependency: ppx-here/s390x ppx-bin-prot/s390x
    • Implicit dependency: ppx-here/s390x ppx-expect/s390x
• ppx-import/amd64 (1.10.0-3 to 1.10.0-3)
  • Migration status for ppx-import/amd64 (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-import/amd64 ppxlib
• ppx-import/arm64 (1.10.0-3 to 1.10.0-3)
  • Migration status for ppx-import/arm64 (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-import/arm64 ppxlib
• ppx-import/armel (1.10.0-3 to 1.10.0-3)
  • Migration status for ppx-import/armel (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-import/armel ppxlib
• ppx-import/armhf (1.10.0-3 to 1.10.0-3)
  • Migration status for ppx-import/armhf (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-import/armhf ppxlib
• ppx-import/i386 (1.10.0-3 to 1.10.0-3)
  • Migration status for ppx-import/i386 (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-import/i386 ppxlib
• ppx-import/mips64el (1.10.0-3 to 1.10.0-3)
  • Migration status for ppx-import/mips64el (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-import/mips64el ppxlib
• ppx-import/ppc64el (1.10.0-3 to 1.10.0-3)
  • Migration status for ppx-import/ppc64el (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-import/ppc64el ppxlib
• ppx-import/s390x (1.10.0-3 to 1.10.0-3)
  • Migration status for ppx-import/s390x (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-import/s390x ppxlib
• ppx-inline-test/amd64 (0.16.1-1 to 0.16.1-1)
  • Migration status for ppx-inline-test/amd64 (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-inline-test/amd64 ppxlib
    • Implicit dependency: ppx-inline-test/amd64 ppx-expect/amd64
• ppx-inline-test/arm64 (0.16.1-1 to 0.16.1-1)
  • Migration status for ppx-inline-test/arm64 (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-inline-test/arm64 ppxlib
    • Implicit dependency: ppx-inline-test/arm64 ppx-expect/arm64
• ppx-inline-test/armel (0.16.1-1 to 0.16.1-1)
  • Migration status for ppx-inline-test/armel (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-inline-test/armel ppxlib
    • Implicit dependency: ppx-inline-test/armel ppx-expect/armel
• ppx-inline-test/armhf (0.16.1-1 to 0.16.1-1)
  • Migration status for ppx-inline-test/armhf (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-inline-test/armhf ppxlib
    • Implicit dependency: ppx-inline-test/armhf ppx-expect/armhf
• ppx-inline-test/i386 (0.16.1-1 to 0.16.1-1)
  • Migration status for ppx-inline-test/i386 (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-inline-test/i386 ppxlib
    • Implicit dependency: ppx-inline-test/i386 ppx-expect/i386
• ppx-inline-test/mips64el (0.16.1-1 to 0.16.1-1)
  • Migration status for ppx-inline-test/mips64el (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-inline-test/mips64el ppxlib
    • Implicit dependency: ppx-inline-test/mips64el ppx-expect/mips64el
• ppx-inline-test/ppc64el (0.16.1-1 to 0.16.1-1)
  • Migration status for ppx-inline-test/ppc64el (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-inline-test/ppc64el ppxlib
    • Implicit dependency: ppx-inline-test/ppc64el ppx-expect/ppc64el
• ppx-inline-test/s390x (0.16.1-1 to 0.16.1-1)
  • Migration status for ppx-inline-test/s390x (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-inline-test/s390x ppxlib
    • Implicit dependency: ppx-inline-test/s390x ppx-expect/s390x
• ppx-optcomp/amd64 (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-optcomp/amd64 (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-optcomp/amd64 ppxlib
• ppx-optcomp/arm64 (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-optcomp/arm64 (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-optcomp/arm64 ppxlib
• ppx-optcomp/armel (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-optcomp/armel (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-optcomp/armel ppxlib
• ppx-optcomp/armhf (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-optcomp/armhf (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-optcomp/armhf ppxlib
• ppx-optcomp/i386 (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-optcomp/i386 (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-optcomp/i386 ppxlib
• ppx-optcomp/mips64el (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-optcomp/mips64el (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-optcomp/mips64el ppxlib
• ppx-optcomp/ppc64el (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-optcomp/ppc64el (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-optcomp/ppc64el ppxlib
• ppx-optcomp/s390x (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-optcomp/s390x (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-optcomp/s390x ppxlib
• ppx-sexp-conv/amd64 (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-sexp-conv/amd64 (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-sexp-conv/amd64 ppxlib
    • Implicit dependency: ppx-sexp-conv/amd64 bin-prot
    • Implicit dependency: ppx-sexp-conv/amd64 ocsigenserver/amd64
    • Implicit dependency: ppx-sexp-conv/amd64 ppx-assert/amd64
    • Implicit dependency: ppx-sexp-conv/amd64 ppx-custom-printf/amd64
• ppx-sexp-conv/arm64 (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-sexp-conv/arm64 (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-sexp-conv/arm64 ppxlib
    • Implicit dependency: ppx-sexp-conv/arm64 bin-prot
    • Implicit dependency: ppx-sexp-conv/arm64 ocsigenserver/arm64
    • Implicit dependency: ppx-sexp-conv/arm64 ppx-assert/arm64
    • Implicit dependency: ppx-sexp-conv/arm64 ppx-custom-printf/arm64
• ppx-sexp-conv/armel (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-sexp-conv/armel (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-sexp-conv/armel ppxlib
    • Implicit dependency: ppx-sexp-conv/armel bin-prot
    • Implicit dependency: ppx-sexp-conv/armel ocsigenserver/armel
    • Implicit dependency: ppx-sexp-conv/armel ppx-assert/armel
    • Implicit dependency: ppx-sexp-conv/armel ppx-custom-printf/armel
• ppx-sexp-conv/armhf (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-sexp-conv/armhf (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-sexp-conv/armhf ppxlib
    • Implicit dependency: ppx-sexp-conv/armhf bin-prot
    • Implicit dependency: ppx-sexp-conv/armhf ocsigenserver/armhf
    • Implicit dependency: ppx-sexp-conv/armhf ppx-assert/armhf
    • Implicit dependency: ppx-sexp-conv/armhf ppx-custom-printf/armhf
• ppx-sexp-conv/i386 (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-sexp-conv/i386 (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-sexp-conv/i386 ppxlib
    • Implicit dependency: ppx-sexp-conv/i386 bin-prot
    • Implicit dependency: ppx-sexp-conv/i386 ocsigenserver/i386
    • Implicit dependency: ppx-sexp-conv/i386 ppx-assert/i386
    • Implicit dependency: ppx-sexp-conv/i386 ppx-custom-printf/i386
• ppx-sexp-conv/mips64el (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-sexp-conv/mips64el (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-sexp-conv/mips64el ppxlib
    • Implicit dependency: ppx-sexp-conv/mips64el bin-prot
    • Implicit dependency: ppx-sexp-conv/mips64el ocsigenserver/mips64el
    • Implicit dependency: ppx-sexp-conv/mips64el ppx-assert/mips64el
    • Implicit dependency: ppx-sexp-conv/mips64el ppx-custom-printf/mips64el
• ppx-sexp-conv/ppc64el (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-sexp-conv/ppc64el (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-sexp-conv/ppc64el ppxlib
    • Implicit dependency: ppx-sexp-conv/ppc64el bin-prot
    • Implicit dependency: ppx-sexp-conv/ppc64el ocsigenserver/ppc64el
    • Implicit dependency: ppx-sexp-conv/ppc64el ppx-assert/ppc64el
    • Implicit dependency: ppx-sexp-conv/ppc64el ppx-custom-printf/ppc64el
• ppx-sexp-conv/s390x (1:0.16.0-3 to 1:0.16.0-3)
  • Migration status for ppx-sexp-conv/s390x (1:0.16.0-3 to 1:0.16.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-sexp-conv/s390x ppxlib
    • Implicit dependency: ppx-sexp-conv/s390x bin-prot
    • Implicit dependency: ppx-sexp-conv/s390x ocsigenserver/s390x
    • Implicit dependency: ppx-sexp-conv/s390x ppx-assert/s390x
    • Implicit dependency: ppx-sexp-conv/s390x ppx-custom-printf/s390x
• ppx-stable-witness/amd64 (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/amd64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-stable-witness/amd64 ppxlib
• ppx-stable-witness/arm64 (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/arm64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-stable-witness/arm64 ppxlib
• ppx-stable-witness/armel (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/armel (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-stable-witness/armel ppxlib
• ppx-stable-witness/armhf (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/armhf (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-stable-witness/armhf ppxlib
• ppx-stable-witness/i386 (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/i386 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-stable-witness/i386 ppxlib
• ppx-stable-witness/mips64el (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/mips64el (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-stable-witness/mips64el ppxlib
• ppx-stable-witness/ppc64el (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/ppc64el (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-stable-witness/ppc64el ppxlib
• ppx-stable-witness/s390x (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/s390x (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-stable-witness/s390x ppxlib
• ppx-string/amd64 (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-string/amd64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-string/amd64 ppxlib
• ppx-string/arm64 (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-string/arm64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-string/arm64 ppxlib
• ppx-string/armel (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-string/armel (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-string/armel ppxlib
• ppx-string/armhf (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-string/armhf (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-string/armhf ppxlib
• ppx-string/i386 (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-string/i386 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-string/i386 ppxlib
• ppx-string/mips64el (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-string/mips64el (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-string/mips64el ppxlib
• ppx-string/ppc64el (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-string/ppc64el (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-string/ppc64el ppxlib
• ppx-string/s390x (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-string/s390x (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-string/s390x ppxlib
• ppx-variants-conv/amd64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-variants-conv/amd64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-variants-conv/amd64 ppxlib
• ppx-variants-conv/arm64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-variants-conv/arm64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-variants-conv/arm64 ppxlib
• ppx-variants-conv/armel (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-variants-conv/armel (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-variants-conv/armel ppxlib
• ppx-variants-conv/armhf (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-variants-conv/armhf (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-variants-conv/armhf ppxlib
• ppx-variants-conv/i386 (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-variants-conv/i386 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-variants-conv/i386 ppxlib
• ppx-variants-conv/mips64el (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-variants-conv/mips64el (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-variants-conv/mips64el ppxlib
• ppx-variants-conv/ppc64el (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-variants-conv/ppc64el (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-variants-conv/ppc64el ppxlib
• ppx-variants-conv/s390x (0.16.0-2 to 0.16.0-2)
  • Migration status for ppx-variants-conv/s390x (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: ppx-variants-conv/s390x ppxlib
• presage/arm64 (0.9.1-2.6 to 0.9.1-2.6)
  • Migration status for presage/arm64 (0.9.1-2.6 to 0.9.1-2.6): Will attempt migration (Any information below is purely informational)
• presage/armhf (0.9.1-2.6 to 0.9.1-2.6)
  • Migration status for presage/armhf (0.9.1-2.6 to 0.9.1-2.6): Will attempt migration (Any information below is purely informational)
• presage/i386 (0.9.1-2.6 to 0.9.1-2.6)
  • Migration status for presage/i386 (0.9.1-2.6 to 0.9.1-2.6): Will attempt migration (Any information below is purely informational)
• presage/ppc64el (0.9.1-2.6 to 0.9.1-2.6)
  • Migration status for presage/ppc64el (0.9.1-2.6 to 0.9.1-2.6): Will attempt migration (Any information below is purely informational)
• priv-wrapper/arm64 (1.0.1-3 to 1.0.1-3)
  • Migration status for priv-wrapper/arm64 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• priv-wrapper/armel (1.0.1-3 to 1.0.1-3)
  • Migration status for priv-wrapper/armel (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• priv-wrapper/armhf (1.0.1-3 to 1.0.1-3)
  • Migration status for priv-wrapper/armhf (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• priv-wrapper/i386 (1.0.1-3 to 1.0.1-3)
  • Migration status for priv-wrapper/i386 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• priv-wrapper/ppc64el (1.0.1-3 to 1.0.1-3)
  • Migration status for priv-wrapper/ppc64el (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• proj/arm64 (9.3.1-1 to 9.3.1-1)
  • Migration status for proj/arm64 (9.3.1-1 to 9.3.1-1): Will attempt migration (Any information below is purely informational)
• proj/armel (9.3.1-1 to 9.3.1-1)
  • Migration status for proj/armel (9.3.1-1 to 9.3.1-1): Will attempt migration (Any information below is purely informational)
• proj/armhf (9.3.1-1 to 9.3.1-1)
  • Migration status for proj/armhf (9.3.1-1 to 9.3.1-1): Will attempt migration (Any information below is purely informational)
• proj/i386 (9.3.1-1 to 9.3.1-1)
  • Migration status for proj/i386 (9.3.1-1 to 9.3.1-1): Will attempt migration (Any information below is purely informational)
• proj/ppc64el (9.3.1-1 to 9.3.1-1)
  • Migration status for proj/ppc64el (9.3.1-1 to 9.3.1-1): Will attempt migration (Any information below is purely informational)
• prometheus-cpp/arm64 (1.0.2-2 to 1.0.2-2)
  • Migration status for prometheus-cpp/arm64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• prometheus-cpp/armel (1.0.2-2 to 1.0.2-2)
  • Migration status for prometheus-cpp/armel (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• prometheus-cpp/armhf (1.0.2-2 to 1.0.2-2)
  • Migration status for prometheus-cpp/armhf (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• prometheus-cpp/i386 (1.0.2-2 to 1.0.2-2)
  • Migration status for prometheus-cpp/i386 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• prometheus-cpp/ppc64el (1.0.2-2 to 1.0.2-2)
  • Migration status for prometheus-cpp/ppc64el (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• properties-cpp/arm64 (0.0.3-1 to 0.0.3-1)
  • Migration status for properties-cpp/arm64 (0.0.3-1 to 0.0.3-1): Will attempt migration (Any information below is purely informational)
• properties-cpp/armel (0.0.3-1 to 0.0.3-1)
  • Migration status for properties-cpp/armel (0.0.3-1 to 0.0.3-1): Will attempt migration (Any information below is purely informational)
• properties-cpp/armhf (0.0.3-1 to 0.0.3-1)
  • Migration status for properties-cpp/armhf (0.0.3-1 to 0.0.3-1): Will attempt migration (Any information below is purely informational)
• properties-cpp/i386 (0.0.3-1 to 0.0.3-1)
  • Migration status for properties-cpp/i386 (0.0.3-1 to 0.0.3-1): Will attempt migration (Any information below is purely informational)
• properties-cpp/ppc64el (0.0.3-1 to 0.0.3-1)
  • Migration status for properties-cpp/ppc64el (0.0.3-1 to 0.0.3-1): Will attempt migration (Any information below is purely informational)
• proxychains/arm64 (3.1-9 to 3.1-9)
  • Migration status for proxychains/arm64 (3.1-9 to 3.1-9): Will attempt migration (Any information below is purely informational)
• proxychains/armel (3.1-9 to 3.1-9)
  • Migration status for proxychains/armel (3.1-9 to 3.1-9): Will attempt migration (Any information below is purely informational)
• proxychains/armhf (3.1-9 to 3.1-9)
  • Migration status for proxychains/armhf (3.1-9 to 3.1-9): Will attempt migration (Any information below is purely informational)
• proxychains/i386 (3.1-9 to 3.1-9)
  • Migration status for proxychains/i386 (3.1-9 to 3.1-9): Will attempt migration (Any information below is purely informational)
• proxychains/ppc64el (3.1-9 to 3.1-9)
  • Migration status for proxychains/ppc64el (3.1-9 to 3.1-9): Will attempt migration (Any information below is purely informational)
• pseudo/arm64 (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1)
  • Migration status for pseudo/arm64 (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1): Will attempt migration (Any information below is purely informational)
• pseudo/armel (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1)
  • Migration status for pseudo/armel (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1): Will attempt migration (Any information below is purely informational)
• pseudo/armhf (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1)
  • Migration status for pseudo/armhf (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1): Will attempt migration (Any information below is purely informational)
• pseudo/i386 (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1)
  • Migration status for pseudo/i386 (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1): Will attempt migration (Any information below is purely informational)
• pseudo/ppc64el (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1)
  • Migration status for pseudo/ppc64el (1.9.0+git20230301+ec6151a2b057-1 to 1.9.0+git20230301+ec6151a2b057-1): Will attempt migration (Any information below is purely informational)
• psocksxx/arm64 (1.1.1-3 to 1.1.1-3)
  • Migration status for psocksxx/arm64 (1.1.1-3 to 1.1.1-3): Will attempt migration (Any information below is purely informational)
• psocksxx/armel (1.1.1-3 to 1.1.1-3)
  • Migration status for psocksxx/armel (1.1.1-3 to 1.1.1-3): Will attempt migration (Any information below is purely informational)
• psocksxx/armhf (1.1.1-3 to 1.1.1-3)
  • Migration status for psocksxx/armhf (1.1.1-3 to 1.1.1-3): Will attempt migration (Any information below is purely informational)
• psocksxx/i386 (1.1.1-3 to 1.1.1-3)
  • Migration status for psocksxx/i386 (1.1.1-3 to 1.1.1-3): Will attempt migration (Any information below is purely informational)
• psocksxx/ppc64el (1.1.1-3 to 1.1.1-3)
  • Migration status for psocksxx/ppc64el (1.1.1-3 to 1.1.1-3): Will attempt migration (Any information below is purely informational)
• psqlodbc/arm64 (1:16.00.0000-1 to 1:16.00.0000-1)
  • Migration status for psqlodbc/arm64 (1:16.00.0000-1 to 1:16.00.0000-1): Will attempt migration (Any information below is purely informational)
• psqlodbc/armel (1:16.00.0000-1 to 1:16.00.0000-1)
  • Migration status for psqlodbc/armel (1:16.00.0000-1 to 1:16.00.0000-1): Will attempt migration (Any information below is purely informational)
• psqlodbc/armhf (1:16.00.0000-1 to 1:16.00.0000-1)
  • Migration status for psqlodbc/armhf (1:16.00.0000-1 to 1:16.00.0000-1): Will attempt migration (Any information below is purely informational)
• psqlodbc/i386 (1:16.00.0000-1 to 1:16.00.0000-1)
  • Migration status for psqlodbc/i386 (1:16.00.0000-1 to 1:16.00.0000-1): Will attempt migration (Any information below is purely informational)
• psqlodbc/ppc64el (1:16.00.0000-1 to 1:16.00.0000-1)
  • Migration status for psqlodbc/ppc64el (1:16.00.0000-1 to 1:16.00.0000-1): Will attempt migration (Any information below is purely informational)
• pstoedit/arm64 (4.00-1 to 4.00-1)
  • Migration status for pstoedit/arm64 (4.00-1 to 4.00-1): Will attempt migration (Any information below is purely informational)
• pstoedit/armel (4.00-1 to 4.00-1)
  • Migration status for pstoedit/armel (4.00-1 to 4.00-1): Will attempt migration (Any information below is purely informational)
• pstoedit/armhf (4.00-1 to 4.00-1)
  • Migration status for pstoedit/armhf (4.00-1 to 4.00-1): Will attempt migration (Any information below is purely informational)
• pstoedit/i386 (4.00-1 to 4.00-1)
  • Migration status for pstoedit/i386 (4.00-1 to 4.00-1): Will attempt migration (Any information below is purely informational)
• pstoedit/ppc64el (4.00-1 to 4.00-1)
  • Migration status for pstoedit/ppc64el (4.00-1 to 4.00-1): Will attempt migration (Any information below is purely informational)
• pth/arm64 (2.0.7-22 to 2.0.7-22)
  • Migration status for pth/arm64 (2.0.7-22 to 2.0.7-22): Will attempt migration (Any information below is purely informational)
• pth/armel (2.0.7-22 to 2.0.7-22)
  • Migration status for pth/armel (2.0.7-22 to 2.0.7-22): Will attempt migration (Any information below is purely informational)
• pth/armhf (2.0.7-22 to 2.0.7-22)
  • Migration status for pth/armhf (2.0.7-22 to 2.0.7-22): Will attempt migration (Any information below is purely informational)
• pth/i386 (2.0.7-22 to 2.0.7-22)
  • Migration status for pth/i386 (2.0.7-22 to 2.0.7-22): Will attempt migration (Any information below is purely informational)
• pth/ppc64el (2.0.7-22 to 2.0.7-22)
  • Migration status for pth/ppc64el (2.0.7-22 to 2.0.7-22): Will attempt migration (Any information below is purely informational)
• pthreadpool/arm64 (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2)
  • Migration status for pthreadpool/arm64 (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2): Will attempt migration (Any information below is purely informational)
• pthreadpool/armel (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2)
  • Migration status for pthreadpool/armel (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2): Will attempt migration (Any information below is purely informational)
• pthreadpool/armhf (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2)
  • Migration status for pthreadpool/armhf (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2): Will attempt migration (Any information below is purely informational)
• pthreadpool/i386 (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2)
  • Migration status for pthreadpool/i386 (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2): Will attempt migration (Any information below is purely informational)
• pthreadpool/ppc64el (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2)
  • Migration status for pthreadpool/ppc64el (0.0~git20210507.1787867-2 to 0.0~git20210507.1787867-2): Will attempt migration (Any information below is purely informational)
• ptl/arm64 (2.3.3-2 to 2.3.3-2)
  • Migration status for ptl/arm64 (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• ptl/armel (2.3.3-2 to 2.3.3-2)
  • Migration status for ptl/armel (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• ptl/armhf (2.3.3-2 to 2.3.3-2)
  • Migration status for ptl/armhf (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• ptl/i386 (2.3.3-2 to 2.3.3-2)
  • Migration status for ptl/i386 (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• ptl/ppc64el (2.3.3-2 to 2.3.3-2)
  • Migration status for ptl/ppc64el (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• pugixml/arm64 (1.14-0.1 to 1.14-0.1)
  • Migration status for pugixml/arm64 (1.14-0.1 to 1.14-0.1): Will attempt migration (Any information below is purely informational)
• pugixml/armel (1.14-0.1 to 1.14-0.1)
  • Migration status for pugixml/armel (1.14-0.1 to 1.14-0.1): Will attempt migration (Any information below is purely informational)
• pugixml/armhf (1.14-0.1 to 1.14-0.1)
  • Migration status for pugixml/armhf (1.14-0.1 to 1.14-0.1): Will attempt migration (Any information below is purely informational)
• pugixml/i386 (1.14-0.1 to 1.14-0.1)
  • Migration status for pugixml/i386 (1.14-0.1 to 1.14-0.1): Will attempt migration (Any information below is purely informational)
• pugixml/ppc64el (1.14-0.1 to 1.14-0.1)
  • Migration status for pugixml/ppc64el (1.14-0.1 to 1.14-0.1): Will attempt migration (Any information below is purely informational)
• pugl/arm64 (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4)
  • Migration status for pugl/arm64 (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4): Will attempt migration (Any information below is purely informational)
• pugl/armel (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4)
  • Migration status for pugl/armel (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4): Will attempt migration (Any information below is purely informational)
• pugl/armhf (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4)
  • Migration status for pugl/armhf (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4): Will attempt migration (Any information below is purely informational)
• pugl/i386 (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4)
  • Migration status for pugl/i386 (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4): Will attempt migration (Any information below is purely informational)
• pugl/ppc64el (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4)
  • Migration status for pugl/ppc64el (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4): Will attempt migration (Any information below is purely informational)
• pulseeffects/arm64 (4.8.7-2 to 4.8.7-2)
  • Migration status for pulseeffects/arm64 (4.8.7-2 to 4.8.7-2): Will attempt migration (Any information below is purely informational)
• pulseeffects/armel (4.8.7-2 to 4.8.7-2)
  • Migration status for pulseeffects/armel (4.8.7-2 to 4.8.7-2): Will attempt migration (Any information below is purely informational)
• pulseeffects/armhf (4.8.7-2 to 4.8.7-2)
  • Migration status for pulseeffects/armhf (4.8.7-2 to 4.8.7-2): Will attempt migration (Any information below is purely informational)
• pulseeffects/i386 (4.8.7-2 to 4.8.7-2)
  • Migration status for pulseeffects/i386 (4.8.7-2 to 4.8.7-2): Will attempt migration (Any information below is purely informational)
• pulseeffects/ppc64el (4.8.7-2 to 4.8.7-2)
  • Migration status for pulseeffects/ppc64el (4.8.7-2 to 4.8.7-2): Will attempt migration (Any information below is purely informational)
• pupnp/arm64 (1:1.14.18-1 to 1:1.14.18-1)
  • Migration status for pupnp/arm64 (1:1.14.18-1 to 1:1.14.18-1): Will attempt migration (Any information below is purely informational)
• pupnp/armel (1:1.14.18-1 to 1:1.14.18-1)
  • Migration status for pupnp/armel (1:1.14.18-1 to 1:1.14.18-1): Will attempt migration (Any information below is purely informational)
• pupnp/armhf (1:1.14.18-1 to 1:1.14.18-1)
  • Migration status for pupnp/armhf (1:1.14.18-1 to 1:1.14.18-1): Will attempt migration (Any information below is purely informational)
• pupnp/i386 (1:1.14.18-1 to 1:1.14.18-1)
  • Migration status for pupnp/i386 (1:1.14.18-1 to 1:1.14.18-1): Will attempt migration (Any information below is purely informational)
• pupnp/ppc64el (1:1.14.18-1 to 1:1.14.18-1)
  • Migration status for pupnp/ppc64el (1:1.14.18-1 to 1:1.14.18-1): Will attempt migration (Any information below is purely informational)
• purelibc/arm64 (1.0.6-1 to 1.0.6-1)
  • Migration status for purelibc/arm64 (1.0.6-1 to 1.0.6-1): Will attempt migration (Any information below is purely informational)
• purelibc/armel (1.0.6-1 to 1.0.6-1)
  • Migration status for purelibc/armel (1.0.6-1 to 1.0.6-1): Will attempt migration (Any information below is purely informational)
• purelibc/armhf (1.0.6-1 to 1.0.6-1)
  • Migration status for purelibc/armhf (1.0.6-1 to 1.0.6-1): Will attempt migration (Any information below is purely informational)
• purelibc/i386 (1.0.6-1 to 1.0.6-1)
  • Migration status for purelibc/i386 (1.0.6-1 to 1.0.6-1): Will attempt migration (Any information below is purely informational)
• purelibc/ppc64el (1.0.6-1 to 1.0.6-1)
  • Migration status for purelibc/ppc64el (1.0.6-1 to 1.0.6-1): Will attempt migration (Any information below is purely informational)
• purple-discord/arm64 (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1)
  • Migration status for purple-discord/arm64 (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1): Will attempt migration (Any information below is purely informational)
• purple-discord/armel (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1)
  • Migration status for purple-discord/armel (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1): Will attempt migration (Any information below is purely informational)
• purple-discord/armhf (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1)
  • Migration status for purple-discord/armhf (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1): Will attempt migration (Any information below is purely informational)
• purple-discord/i386 (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1)
  • Migration status for purple-discord/i386 (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1): Will attempt migration (Any information below is purely informational)
• purple-discord/ppc64el (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1)
  • Migration status for purple-discord/ppc64el (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1): Will attempt migration (Any information below is purely informational)
• purpose/arm64 (5.107.0-1 to 5.107.0-1)
  • Migration status for purpose/arm64 (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• purpose/armel (5.107.0-1 to 5.107.0-1)
  • Migration status for purpose/armel (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• purpose/armhf (5.107.0-1 to 5.107.0-1)
  • Migration status for purpose/armhf (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• purpose/i386 (5.107.0-1 to 5.107.0-1)
  • Migration status for purpose/i386 (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• purpose/ppc64el (5.107.0-1 to 5.107.0-1)
  • Migration status for purpose/ppc64el (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• qcodeeditor/arm64 (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2)
  • Migration status for qcodeeditor/arm64 (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2): Will attempt migration (Any information below is purely informational)
• qcodeeditor/armel (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2)
  • Migration status for qcodeeditor/armel (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2): Will attempt migration (Any information below is purely informational)
• qcodeeditor/armhf (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2)
  • Migration status for qcodeeditor/armhf (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2): Will attempt migration (Any information below is purely informational)
• qcodeeditor/i386 (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2)
  • Migration status for qcodeeditor/i386 (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2): Will attempt migration (Any information below is purely informational)
• qcodeeditor/ppc64el (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2)
  • Migration status for qcodeeditor/ppc64el (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2): Will attempt migration (Any information below is purely informational)
• qcustomplot/arm64 (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1)
  • Migration status for qcustomplot/arm64 (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1): Will attempt migration (Any information below is purely informational)
• qcustomplot/armel (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1)
  • Migration status for qcustomplot/armel (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1): Will attempt migration (Any information below is purely informational)
• qcustomplot/armhf (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1)
  • Migration status for qcustomplot/armhf (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1): Will attempt migration (Any information below is purely informational)
• qcustomplot/i386 (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1)
  • Migration status for qcustomplot/i386 (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1): Will attempt migration (Any information below is purely informational)
• qcustomplot/ppc64el (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1)
  • Migration status for qcustomplot/ppc64el (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1): Will attempt migration (Any information below is purely informational)
• qd/arm64 (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1)
  • Migration status for qd/arm64 (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1): Will attempt migration (Any information below is purely informational)
• qd/armel (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1)
  • Migration status for qd/armel (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1): Will attempt migration (Any information below is purely informational)
• qd/armhf (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1)
  • Migration status for qd/armhf (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1): Will attempt migration (Any information below is purely informational)
• qd/i386 (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1)
  • Migration status for qd/i386 (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1): Will attempt migration (Any information below is purely informational)
• qd/ppc64el (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1)
  • Migration status for qd/ppc64el (2.3.23+dfsg.1-1 to 2.3.23+dfsg.1-1): Will attempt migration (Any information below is purely informational)
• qdjango/arm64 (0.6.2-3.3 to 0.6.2-3.3)
  • Migration status for qdjango/arm64 (0.6.2-3.3 to 0.6.2-3.3): Will attempt migration (Any information below is purely informational)
• qdjango/armel (0.6.2-3.3 to 0.6.2-3.3)
  • Migration status for qdjango/armel (0.6.2-3.3 to 0.6.2-3.3): Will attempt migration (Any information below is purely informational)
• qdjango/armhf (0.6.2-3.3 to 0.6.2-3.3)
  • Migration status for qdjango/armhf (0.6.2-3.3 to 0.6.2-3.3): Will attempt migration (Any information below is purely informational)
• qdjango/i386 (0.6.2-3.3 to 0.6.2-3.3)
  • Migration status for qdjango/i386 (0.6.2-3.3 to 0.6.2-3.3): Will attempt migration (Any information below is purely informational)
• qdjango/ppc64el (0.6.2-3.3 to 0.6.2-3.3)
  • Migration status for qdjango/ppc64el (0.6.2-3.3 to 0.6.2-3.3): Will attempt migration (Any information below is purely informational)
• qgnomeplatform/arm64 (0.9.2-1 to 0.9.2-1)
  • Migration status for qgnomeplatform/arm64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• qgnomeplatform/armel (0.9.2-1 to 0.9.2-1)
  • Migration status for qgnomeplatform/armel (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• qgnomeplatform/armhf (0.9.2-1 to 0.9.2-1)
  • Migration status for qgnomeplatform/armhf (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• qgnomeplatform/i386 (0.9.2-1 to 0.9.2-1)
  • Migration status for qgnomeplatform/i386 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• qgnomeplatform/ppc64el (0.9.2-1 to 0.9.2-1)
  • Migration status for qgnomeplatform/ppc64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• qhull/arm64 (2020.2-6 to 2020.2-6)
  • Migration status for qhull/arm64 (2020.2-6 to 2020.2-6): Will attempt migration (Any information below is purely informational)
• qhull/armel (2020.2-6 to 2020.2-6)
  • Migration status for qhull/armel (2020.2-6 to 2020.2-6): Will attempt migration (Any information below is purely informational)
• qhull/armhf (2020.2-6 to 2020.2-6)
  • Migration status for qhull/armhf (2020.2-6 to 2020.2-6): Will attempt migration (Any information below is purely informational)
• qhull/i386 (2020.2-6 to 2020.2-6)
  • Migration status for qhull/i386 (2020.2-6 to 2020.2-6): Will attempt migration (Any information below is purely informational)
• qhull/ppc64el (2020.2-6 to 2020.2-6)
  • Migration status for qhull/ppc64el (2020.2-6 to 2020.2-6): Will attempt migration (Any information below is purely informational)
• qmltermwidget/arm64 (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3)
  • Migration status for qmltermwidget/arm64 (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3): Will attempt migration (Any information below is purely informational)
• qmltermwidget/armel (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3)
  • Migration status for qmltermwidget/armel (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3): Will attempt migration (Any information below is purely informational)
• qmltermwidget/armhf (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3)
  • Migration status for qmltermwidget/armhf (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3): Will attempt migration (Any information below is purely informational)
• qmltermwidget/i386 (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3)
  • Migration status for qmltermwidget/i386 (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3): Will attempt migration (Any information below is purely informational)
• qmltermwidget/ppc64el (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3)
  • Migration status for qmltermwidget/ppc64el (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3): Will attempt migration (Any information below is purely informational)
• qr-code-generator/arm64 (1.8.0-1.2 to 1.8.0-1.2)
  • Migration status for qr-code-generator/arm64 (1.8.0-1.2 to 1.8.0-1.2): Will attempt migration (Any information below is purely informational)
• qr-code-generator/armel (1.8.0-1.2 to 1.8.0-1.2)
  • Migration status for qr-code-generator/armel (1.8.0-1.2 to 1.8.0-1.2): Will attempt migration (Any information below is purely informational)
• qr-code-generator/armhf (1.8.0-1.2 to 1.8.0-1.2)
  • Migration status for qr-code-generator/armhf (1.8.0-1.2 to 1.8.0-1.2): Will attempt migration (Any information below is purely informational)
• qr-code-generator/i386 (1.8.0-1.2 to 1.8.0-1.2)
  • Migration status for qr-code-generator/i386 (1.8.0-1.2 to 1.8.0-1.2): Will attempt migration (Any information below is purely informational)
• qr-code-generator/ppc64el (1.8.0-1.2 to 1.8.0-1.2)
  • Migration status for qr-code-generator/ppc64el (1.8.0-1.2 to 1.8.0-1.2): Will attempt migration (Any information below is purely informational)
• qrencode/arm64 (4.1.1-1 to 4.1.1-1)
  • Migration status for qrencode/arm64 (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• qrencode/armel (4.1.1-1 to 4.1.1-1)
  • Migration status for qrencode/armel (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• qrencode/armhf (4.1.1-1 to 4.1.1-1)
  • Migration status for qrencode/armhf (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• qrencode/i386 (4.1.1-1 to 4.1.1-1)
  • Migration status for qrencode/i386 (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• qrencode/ppc64el (4.1.1-1 to 4.1.1-1)
  • Migration status for qrencode/ppc64el (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• qrupdate/arm64 (1.1.2-4 to 1.1.2-4)
  • Migration status for qrupdate/arm64 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
• qrupdate/armel (1.1.2-4 to 1.1.2-4)
  • Migration status for qrupdate/armel (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
• qrupdate/armhf (1.1.2-4 to 1.1.2-4)
  • Migration status for qrupdate/armhf (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
• qrupdate/i386 (1.1.2-4 to 1.1.2-4)
  • Migration status for qrupdate/i386 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
• qrupdate/ppc64el (1.1.2-4 to 1.1.2-4)
  • Migration status for qrupdate/ppc64el (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
• qscintilla2/arm64 (2.14.1+dfsg-1 to 2.14.1+dfsg-1)
  • Migration status for qscintilla2/arm64 (2.14.1+dfsg-1 to 2.14.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• qscintilla2/armhf (2.14.1+dfsg-1 to 2.14.1+dfsg-1)
  • Migration status for qscintilla2/armhf (2.14.1+dfsg-1 to 2.14.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• qscintilla2/i386 (2.14.1+dfsg-1 to 2.14.1+dfsg-1)
  • Migration status for qscintilla2/i386 (2.14.1+dfsg-1 to 2.14.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• qscintilla2/ppc64el (2.14.1+dfsg-1 to 2.14.1+dfsg-1)
  • Migration status for qscintilla2/ppc64el (2.14.1+dfsg-1 to 2.14.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• qt-color-widgets/arm64 (2.2.0-2 to 2.2.0-2)
  • Migration status for qt-color-widgets/arm64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• qt-color-widgets/armel (2.2.0-2 to 2.2.0-2)
  • Migration status for qt-color-widgets/armel (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• qt-color-widgets/armhf (2.2.0-2 to 2.2.0-2)
  • Migration status for qt-color-widgets/armhf (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• qt-color-widgets/i386 (2.2.0-2 to 2.2.0-2)
  • Migration status for qt-color-widgets/i386 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• qt-color-widgets/ppc64el (2.2.0-2 to 2.2.0-2)
  • Migration status for qt-color-widgets/ppc64el (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• qt-gstreamer/arm64 (1.2.0-5.2 to 1.2.0-5.2)
  • Migration status for qt-gstreamer/arm64 (1.2.0-5.2 to 1.2.0-5.2): Will attempt migration (Any information below is purely informational)
• qt-gstreamer/armel (1.2.0-5.2 to 1.2.0-5.2)
  • Migration status for qt-gstreamer/armel (1.2.0-5.2 to 1.2.0-5.2): Will attempt migration (Any information below is purely informational)
• qt-gstreamer/armhf (1.2.0-5.2 to 1.2.0-5.2)
  • Migration status for qt-gstreamer/armhf (1.2.0-5.2 to 1.2.0-5.2): Will attempt migration (Any information below is purely informational)
• qt-gstreamer/i386 (1.2.0-5.2 to 1.2.0-5.2)
  • Migration status for qt-gstreamer/i386 (1.2.0-5.2 to 1.2.0-5.2): Will attempt migration (Any information below is purely informational)
• qt-gstreamer/ppc64el (1.2.0-5.2 to 1.2.0-5.2)
  • Migration status for qt-gstreamer/ppc64el (1.2.0-5.2 to 1.2.0-5.2): Will attempt migration (Any information below is purely informational)
• qt3d-opensource-src/armel (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qt3d-opensource-src/armel (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qt3d-opensource-src/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qt3d-opensource-src/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qt3d-opensource-src/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qt3d-opensource-src/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qt3d-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qt3d-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qt6-3d/arm64 (6.4.2+dfsg-6 to 6.4.2+dfsg-6)
  • Migration status for qt6-3d/arm64 (6.4.2+dfsg-6 to 6.4.2+dfsg-6): Will attempt migration (Any information below is purely informational)
• qt6-3d/armhf (6.4.2+dfsg-6 to 6.4.2+dfsg-6)
  • Migration status for qt6-3d/armhf (6.4.2+dfsg-6 to 6.4.2+dfsg-6): Will attempt migration (Any information below is purely informational)
• qt6-3d/i386 (6.4.2+dfsg-6 to 6.4.2+dfsg-6)
  • Migration status for qt6-3d/i386 (6.4.2+dfsg-6 to 6.4.2+dfsg-6): Will attempt migration (Any information below is purely informational)
• qt6-3d/ppc64el (6.4.2+dfsg-6 to 6.4.2+dfsg-6)
  • Migration status for qt6-3d/ppc64el (6.4.2+dfsg-6 to 6.4.2+dfsg-6): Will attempt migration (Any information below is purely informational)
• qt6-5compat/arm64 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-5compat/arm64 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-5compat/armel (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-5compat/armel (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-5compat/armhf (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-5compat/armhf (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-5compat/i386 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-5compat/i386 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-5compat/ppc64el (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-5compat/ppc64el (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-charts/arm64 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-charts/arm64 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-charts/armel (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-charts/armel (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-charts/armhf (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-charts/armhf (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-charts/i386 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-charts/i386 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-charts/ppc64el (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-charts/ppc64el (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-connectivity/arm64 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-connectivity/arm64 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-connectivity/armel (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-connectivity/armel (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-connectivity/armhf (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-connectivity/armhf (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-connectivity/i386 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-connectivity/i386 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-connectivity/ppc64el (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-connectivity/ppc64el (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-datavis3d/arm64 (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-datavis3d/arm64 (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-datavis3d/armel (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-datavis3d/armel (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-datavis3d/armhf (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-datavis3d/armhf (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-datavis3d/i386 (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-datavis3d/i386 (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-datavis3d/ppc64el (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-datavis3d/ppc64el (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-declarative/arm64 (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-declarative/arm64 (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-declarative/armhf (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-declarative/armhf (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-declarative/i386 (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-declarative/i386 (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-declarative/ppc64el (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-declarative/ppc64el (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-declarative/s390x (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-declarative/s390x (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-httpserver/arm64 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-httpserver/arm64 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-httpserver/armel (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-httpserver/armel (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-httpserver/armhf (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-httpserver/armhf (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-httpserver/i386 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-httpserver/i386 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-httpserver/ppc64el (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-httpserver/ppc64el (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-languageserver/arm64 (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-languageserver/arm64 (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-languageserver/armel (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-languageserver/armel (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-languageserver/armhf (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-languageserver/armhf (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-languageserver/i386 (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-languageserver/i386 (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-languageserver/ppc64el (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-languageserver/ppc64el (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-lottie/arm64 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-lottie/arm64 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-lottie/armel (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-lottie/armel (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-lottie/armhf (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-lottie/armhf (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-lottie/i386 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-lottie/i386 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-lottie/ppc64el (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-lottie/ppc64el (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-multimedia/arm64 (6.4.2-11 to 6.4.2-11)
  • Migration status for qt6-multimedia/arm64 (6.4.2-11 to 6.4.2-11): Will attempt migration (Any information below is purely informational)
• qt6-multimedia/armel (6.4.2-11 to 6.4.2-11)
  • Migration status for qt6-multimedia/armel (6.4.2-11 to 6.4.2-11): Will attempt migration (Any information below is purely informational)
• qt6-multimedia/armhf (6.4.2-11 to 6.4.2-11)
  • Migration status for qt6-multimedia/armhf (6.4.2-11 to 6.4.2-11): Will attempt migration (Any information below is purely informational)
• qt6-multimedia/i386 (6.4.2-11 to 6.4.2-11)
  • Migration status for qt6-multimedia/i386 (6.4.2-11 to 6.4.2-11): Will attempt migration (Any information below is purely informational)
• qt6-multimedia/ppc64el (6.4.2-11 to 6.4.2-11)
  • Migration status for qt6-multimedia/ppc64el (6.4.2-11 to 6.4.2-11): Will attempt migration (Any information below is purely informational)
• qt6-networkauth/arm64 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-networkauth/arm64 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-networkauth/armel (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-networkauth/armel (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-networkauth/armhf (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-networkauth/armhf (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-networkauth/i386 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-networkauth/i386 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-networkauth/ppc64el (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-networkauth/ppc64el (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-positioning/arm64 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-positioning/arm64 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-positioning/armel (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-positioning/armel (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-positioning/armhf (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-positioning/armhf (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-positioning/i386 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-positioning/i386 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-positioning/ppc64el (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-positioning/ppc64el (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-quick3d/arm64 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-quick3d/arm64 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-quick3d/armel (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-quick3d/armel (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-quick3d/armhf (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-quick3d/armhf (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-quick3d/i386 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-quick3d/i386 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-quick3d/ppc64el (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-quick3d/ppc64el (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-quicktimeline/arm64 (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-quicktimeline/arm64 (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-quicktimeline/armel (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-quicktimeline/armel (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-quicktimeline/armhf (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-quicktimeline/armhf (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-quicktimeline/i386 (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-quicktimeline/i386 (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-quicktimeline/ppc64el (6.4.2-2 to 6.4.2-2)
  • Migration status for qt6-quicktimeline/ppc64el (6.4.2-2 to 6.4.2-2): Will attempt migration (Any information below is purely informational)
• qt6-remoteobjects/arm64 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-remoteobjects/arm64 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-remoteobjects/armel (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-remoteobjects/armel (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-remoteobjects/armhf (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-remoteobjects/armhf (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-remoteobjects/i386 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-remoteobjects/i386 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-remoteobjects/ppc64el (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-remoteobjects/ppc64el (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-scxml/arm64 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-scxml/arm64 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-scxml/armel (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-scxml/armel (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-scxml/armhf (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-scxml/armhf (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-scxml/i386 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-scxml/i386 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-scxml/ppc64el (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-scxml/ppc64el (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-sensors/arm64 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-sensors/arm64 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-sensors/armel (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-sensors/armel (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-sensors/armhf (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-sensors/armhf (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-sensors/i386 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-sensors/i386 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-sensors/ppc64el (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-sensors/ppc64el (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialbus/arm64 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialbus/arm64 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialbus/armel (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialbus/armel (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialbus/armhf (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialbus/armhf (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialbus/i386 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialbus/i386 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialbus/ppc64el (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialbus/ppc64el (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialport/arm64 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialport/arm64 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialport/armel (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialport/armel (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialport/armhf (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialport/armhf (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialport/i386 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialport/i386 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-serialport/ppc64el (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-serialport/ppc64el (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-shadertools/arm64 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-shadertools/arm64 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-shadertools/armel (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-shadertools/armel (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-shadertools/armhf (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-shadertools/armhf (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-shadertools/i386 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-shadertools/i386 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-shadertools/ppc64el (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-shadertools/ppc64el (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-speech/arm64 (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-speech/arm64 (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-speech/armel (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-speech/armel (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-speech/armhf (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-speech/armhf (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-speech/i386 (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-speech/i386 (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-speech/ppc64el (6.4.2-6 to 6.4.2-6)
  • Migration status for qt6-speech/ppc64el (6.4.2-6 to 6.4.2-6): Will attempt migration (Any information below is purely informational)
• qt6-svg/arm64 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-svg/arm64 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-svg/armel (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-svg/armel (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-svg/armhf (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-svg/armhf (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-svg/i386 (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-svg/i386 (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-svg/ppc64el (6.4.2-4 to 6.4.2-4)
  • Migration status for qt6-svg/ppc64el (6.4.2-4 to 6.4.2-4): Will attempt migration (Any information below is purely informational)
• qt6-tools/arm64 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-tools/arm64 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-tools/armel (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-tools/armel (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-tools/armhf (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-tools/armhf (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-tools/i386 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-tools/i386 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-tools/ppc64el (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-tools/ppc64el (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-virtualkeyboard/arm64 (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-virtualkeyboard/arm64 (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-virtualkeyboard/armel (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-virtualkeyboard/armel (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-virtualkeyboard/armhf (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-virtualkeyboard/armhf (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-virtualkeyboard/i386 (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-virtualkeyboard/i386 (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-virtualkeyboard/ppc64el (6.4.2+dfsg-4 to 6.4.2+dfsg-4)
  • Migration status for qt6-virtualkeyboard/ppc64el (6.4.2+dfsg-4 to 6.4.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• qt6-wayland/arm64 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-wayland/arm64 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-wayland/armel (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-wayland/armel (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-wayland/armhf (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-wayland/armhf (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-wayland/i386 (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-wayland/i386 (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-wayland/ppc64el (6.4.2-5 to 6.4.2-5)
  • Migration status for qt6-wayland/ppc64el (6.4.2-5 to 6.4.2-5): Will attempt migration (Any information below is purely informational)
• qt6-webchannel/arm64 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-webchannel/arm64 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-webchannel/armel (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-webchannel/armel (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-webchannel/armhf (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-webchannel/armhf (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-webchannel/i386 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-webchannel/i386 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-webchannel/ppc64el (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-webchannel/ppc64el (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-websockets/arm64 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-websockets/arm64 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-websockets/armel (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-websockets/armel (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-websockets/armhf (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-websockets/armhf (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-websockets/i386 (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-websockets/i386 (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qt6-websockets/ppc64el (6.4.2-3 to 6.4.2-3)
  • Migration status for qt6-websockets/ppc64el (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
• qtcharts-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtcharts-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtcharts-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtcharts-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtcharts-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtcharts-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtcharts-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtcharts-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtcharts-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtcharts-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtconnectivity-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtconnectivity-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtconnectivity-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtconnectivity-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtconnectivity-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtconnectivity-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtconnectivity-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtconnectivity-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtconnectivity-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtconnectivity-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdatavis3d-everywhere-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdatavis3d-everywhere-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdatavis3d-everywhere-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdatavis3d-everywhere-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdatavis3d-everywhere-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdatavis3d-everywhere-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdatavis3d-everywhere-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdatavis3d-everywhere-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdatavis3d-everywhere-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdatavis3d-everywhere-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdbusextended/arm64 (0.0.3-6 to 0.0.3-6)
  • Migration status for qtdbusextended/arm64 (0.0.3-6 to 0.0.3-6): Will attempt migration (Any information below is purely informational)
• qtdbusextended/armel (0.0.3-6 to 0.0.3-6)
  • Migration status for qtdbusextended/armel (0.0.3-6 to 0.0.3-6): Will attempt migration (Any information below is purely informational)
• qtdbusextended/armhf (0.0.3-6 to 0.0.3-6)
  • Migration status for qtdbusextended/armhf (0.0.3-6 to 0.0.3-6): Will attempt migration (Any information below is purely informational)
• qtdbusextended/i386 (0.0.3-6 to 0.0.3-6)
  • Migration status for qtdbusextended/i386 (0.0.3-6 to 0.0.3-6): Will attempt migration (Any information below is purely informational)
• qtdbusextended/ppc64el (0.0.3-6 to 0.0.3-6)
  • Migration status for qtdbusextended/ppc64el (0.0.3-6 to 0.0.3-6): Will attempt migration (Any information below is purely informational)
• qtdeclarative-opensource-src-gles/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtdeclarative-opensource-src-gles/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtdeclarative-opensource-src-gles/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtdeclarative-opensource-src-gles/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtdeclarative-opensource-src-gles/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtdeclarative-opensource-src-gles/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtdeclarative-opensource-src-gles/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtdeclarative-opensource-src-gles/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtdeclarative-opensource-src/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtdeclarative-opensource-src/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtdeclarative-opensource-src/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtdeclarative-opensource-src/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtdeclarative-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtdeclarative-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtdoc-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdoc-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdoc-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdoc-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdoc-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdoc-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdoc-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdoc-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtdoc-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtdoc-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtermwidget/arm64 (1.4.0-1 to 1.4.0-1)
  • Migration status for qtermwidget/arm64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• qtermwidget/armel (1.4.0-1 to 1.4.0-1)
  • Migration status for qtermwidget/armel (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• qtermwidget/armhf (1.4.0-1 to 1.4.0-1)
  • Migration status for qtermwidget/armhf (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• qtermwidget/i386 (1.4.0-1 to 1.4.0-1)
  • Migration status for qtermwidget/i386 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• qtermwidget/ppc64el (1.4.0-1 to 1.4.0-1)
  • Migration status for qtermwidget/ppc64el (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• qtfeedback-opensource-src/arm64 (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5)
  • Migration status for qtfeedback-opensource-src/arm64 (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5): Will attempt migration (Any information below is purely informational)
• qtfeedback-opensource-src/armel (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5)
  • Migration status for qtfeedback-opensource-src/armel (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5): Will attempt migration (Any information below is purely informational)
• qtfeedback-opensource-src/armhf (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5)
  • Migration status for qtfeedback-opensource-src/armhf (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5): Will attempt migration (Any information below is purely informational)
• qtfeedback-opensource-src/i386 (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5)
  • Migration status for qtfeedback-opensource-src/i386 (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5): Will attempt migration (Any information below is purely informational)
• qtfeedback-opensource-src/ppc64el (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5)
  • Migration status for qtfeedback-opensource-src/ppc64el (5.0~git20180903.a14bd0b-5 to 5.0~git20180903.a14bd0b-5): Will attempt migration (Any information below is purely informational)
• qtgamepad-everywhere-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgamepad-everywhere-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgamepad-everywhere-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgamepad-everywhere-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgamepad-everywhere-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgamepad-everywhere-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgamepad-everywhere-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgamepad-everywhere-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgamepad-everywhere-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgamepad-everywhere-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgraphicaleffects-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgraphicaleffects-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgraphicaleffects-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgraphicaleffects-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgraphicaleffects-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgraphicaleffects-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgraphicaleffects-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgraphicaleffects-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtgraphicaleffects-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtgraphicaleffects-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtimageformats-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtimageformats-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtimageformats-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtimageformats-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtimageformats-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtimageformats-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtimageformats-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtimageformats-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtimageformats-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtimageformats-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtlocation-opensource-src/arm64 (5.15.10+dfsg-3 to 5.15.10+dfsg-3)
  • Migration status for qtlocation-opensource-src/arm64 (5.15.10+dfsg-3 to 5.15.10+dfsg-3): Will attempt migration (Any information below is purely informational)
• qtlocation-opensource-src/armhf (5.15.10+dfsg-3 to 5.15.10+dfsg-3)
  • Migration status for qtlocation-opensource-src/armhf (5.15.10+dfsg-3 to 5.15.10+dfsg-3): Will attempt migration (Any information below is purely informational)
• qtlocation-opensource-src/i386 (5.15.10+dfsg-3 to 5.15.10+dfsg-3)
  • Migration status for qtlocation-opensource-src/i386 (5.15.10+dfsg-3 to 5.15.10+dfsg-3): Will attempt migration (Any information below is purely informational)
• qtlocation-opensource-src/ppc64el (5.15.10+dfsg-3 to 5.15.10+dfsg-3)
  • Migration status for qtlocation-opensource-src/ppc64el (5.15.10+dfsg-3 to 5.15.10+dfsg-3): Will attempt migration (Any information below is purely informational)
• qtmpris/arm64 (1.0.6-2 to 1.0.6-2)
  • Migration status for qtmpris/arm64 (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
• qtmpris/armel (1.0.6-2 to 1.0.6-2)
  • Migration status for qtmpris/armel (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
• qtmpris/armhf (1.0.6-2 to 1.0.6-2)
  • Migration status for qtmpris/armhf (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
• qtmpris/i386 (1.0.6-2 to 1.0.6-2)
  • Migration status for qtmpris/i386 (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
• qtmpris/ppc64el (1.0.6-2 to 1.0.6-2)
  • Migration status for qtmpris/ppc64el (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
• qtmultimedia-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtmultimedia-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtmultimedia-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtmultimedia-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtmultimedia-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtmultimedia-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtmultimedia-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtmultimedia-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtnetworkauth-everywhere-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtnetworkauth-everywhere-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtnetworkauth-everywhere-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtnetworkauth-everywhere-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtnetworkauth-everywhere-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtnetworkauth-everywhere-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtnetworkauth-everywhere-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtnetworkauth-everywhere-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtnetworkauth-everywhere-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtnetworkauth-everywhere-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtquickcontrols-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtquickcontrols-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtquickcontrols-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtquickcontrols-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtquickcontrols-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols2-opensource-src/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtquickcontrols2-opensource-src/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols2-opensource-src/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtquickcontrols2-opensource-src/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols2-opensource-src/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtquickcontrols2-opensource-src/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtquickcontrols2-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtquickcontrols2-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtscript-opensource-src/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtscript-opensource-src/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtscript-opensource-src/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtscript-opensource-src/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtscript-opensource-src/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtscript-opensource-src/i386 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtscript-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtscript-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtscxml-everywhere-src/arm64 (5.15.10-3 to 5.15.10-3)
  • Migration status for qtscxml-everywhere-src/arm64 (5.15.10-3 to 5.15.10-3): Will attempt migration (Any information below is purely informational)
• qtscxml-everywhere-src/armel (5.15.10-3 to 5.15.10-3)
  • Migration status for qtscxml-everywhere-src/armel (5.15.10-3 to 5.15.10-3): Will attempt migration (Any information below is purely informational)
• qtscxml-everywhere-src/armhf (5.15.10-3 to 5.15.10-3)
  • Migration status for qtscxml-everywhere-src/armhf (5.15.10-3 to 5.15.10-3): Will attempt migration (Any information below is purely informational)
• qtscxml-everywhere-src/i386 (5.15.10-3 to 5.15.10-3)
  • Migration status for qtscxml-everywhere-src/i386 (5.15.10-3 to 5.15.10-3): Will attempt migration (Any information below is purely informational)
• qtscxml-everywhere-src/ppc64el (5.15.10-3 to 5.15.10-3)
  • Migration status for qtscxml-everywhere-src/ppc64el (5.15.10-3 to 5.15.10-3): Will attempt migration (Any information below is purely informational)
• qtsensors-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtsensors-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtsensors-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtsensors-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtsensors-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtsensors-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtsensors-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtsensors-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialbus-everywhere-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialbus-everywhere-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialbus-everywhere-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialbus-everywhere-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialbus-everywhere-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialbus-everywhere-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialbus-everywhere-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialbus-everywhere-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialbus-everywhere-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialbus-everywhere-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialport-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialport-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialport-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialport-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialport-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialport-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialport-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialport-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtserialport-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtserialport-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtspeech-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtspeech-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtspeech-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtspeech-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtspeech-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtspeech-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtspeech-opensource-src/i386 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtspeech-opensource-src/i386 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtspeech-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtspeech-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtspell/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for qtspell/arm64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• qtspell/armel (1.0.1-2 to 1.0.1-2)
  • Migration status for qtspell/armel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• qtspell/armhf (1.0.1-2 to 1.0.1-2)
  • Migration status for qtspell/armhf (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• qtspell/i386 (1.0.1-2 to 1.0.1-2)
  • Migration status for qtspell/i386 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• qtspell/ppc64el (1.0.1-2 to 1.0.1-2)
  • Migration status for qtspell/ppc64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• qtstyleplugins-src/arm64 (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6)
  • Migration status for qtstyleplugins-src/arm64 (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6): Will attempt migration (Any information below is purely informational)
• qtstyleplugins-src/armel (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6)
  • Migration status for qtstyleplugins-src/armel (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6): Will attempt migration (Any information below is purely informational)
• qtstyleplugins-src/armhf (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6)
  • Migration status for qtstyleplugins-src/armhf (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6): Will attempt migration (Any information below is purely informational)
• qtstyleplugins-src/ppc64el (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6)
  • Migration status for qtstyleplugins-src/ppc64el (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6): Will attempt migration (Any information below is purely informational)
• qtsvg-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtsvg-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtsvg-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtsvg-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtsvg-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtsvg-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtsvg-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtsvg-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtvirtualkeyboard-opensource-src/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtvirtualkeyboard-opensource-src/arm64 (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtvirtualkeyboard-opensource-src/armel (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtvirtualkeyboard-opensource-src/armel (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtvirtualkeyboard-opensource-src/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtvirtualkeyboard-opensource-src/armhf (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtvirtualkeyboard-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2)
  • Migration status for qtvirtualkeyboard-opensource-src/ppc64el (5.15.10+dfsg-2 to 5.15.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• qtwayland-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwayland-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwayland-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwayland-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwayland-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwayland-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwayland-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwayland-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwebchannel-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwebchannel-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwebchannel-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwebchannel-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwebchannel-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwebchannel-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwebchannel-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwebchannel-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwebkit-opensource-src/arm64 (5.212.0~alpha4-33 to 5.212.0~alpha4-33)
  • Migration status for qtwebkit-opensource-src/arm64 (5.212.0~alpha4-33 to 5.212.0~alpha4-33): Will attempt migration (Any information below is purely informational)
• qtwebkit-opensource-src/ppc64el (5.212.0~alpha4-33 to 5.212.0~alpha4-33)
  • Migration status for qtwebkit-opensource-src/ppc64el (5.212.0~alpha4-33 to 5.212.0~alpha4-33): Will attempt migration (Any information below is purely informational)
• qtwebkit-opensource-src/s390x (5.212.0~alpha4-33 to 5.212.0~alpha4-33)
  • Migration status for qtwebkit-opensource-src/s390x (5.212.0~alpha4-33 to 5.212.0~alpha4-33): Will attempt migration (Any information below is purely informational)
• qtwebsockets-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwebsockets-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwebsockets-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwebsockets-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwebsockets-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwebsockets-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtwebsockets-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtwebsockets-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtx11extras-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtx11extras-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtx11extras-opensource-src/armel (5.15.10-2 to 5.15.10-2)
  • Migration status for qtx11extras-opensource-src/armel (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtx11extras-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtx11extras-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtx11extras-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtx11extras-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtxmlpatterns-opensource-src/arm64 (5.15.10-2 to 5.15.10-2)
  • Migration status for qtxmlpatterns-opensource-src/arm64 (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtxmlpatterns-opensource-src/armhf (5.15.10-2 to 5.15.10-2)
  • Migration status for qtxmlpatterns-opensource-src/armhf (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qtxmlpatterns-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2)
  • Migration status for qtxmlpatterns-opensource-src/ppc64el (5.15.10-2 to 5.15.10-2): Will attempt migration (Any information below is purely informational)
• qxmpp/arm64 (1.5.5-0.3 to 1.5.5-0.3)
  • Migration status for qxmpp/arm64 (1.5.5-0.3 to 1.5.5-0.3): Will attempt migration (Any information below is purely informational)
• qxmpp/armel (1.5.5-0.3 to 1.5.5-0.3)
  • Migration status for qxmpp/armel (1.5.5-0.3 to 1.5.5-0.3): Will attempt migration (Any information below is purely informational)
• qxmpp/armhf (1.5.5-0.3 to 1.5.5-0.3)
  • Migration status for qxmpp/armhf (1.5.5-0.3 to 1.5.5-0.3): Will attempt migration (Any information below is purely informational)
• qxmpp/ppc64el (1.5.5-0.3 to 1.5.5-0.3)
  • Migration status for qxmpp/ppc64el (1.5.5-0.3 to 1.5.5-0.3): Will attempt migration (Any information below is purely informational)
• qzxing/arm64 (3.3.0+dfsg-5 to 3.3.0+dfsg-5)
  • Migration status for qzxing/arm64 (3.3.0+dfsg-5 to 3.3.0+dfsg-5): Will attempt migration (Any information below is purely informational)
• qzxing/armel (3.3.0+dfsg-5 to 3.3.0+dfsg-5)
  • Migration status for qzxing/armel (3.3.0+dfsg-5 to 3.3.0+dfsg-5): Will attempt migration (Any information below is purely informational)
• qzxing/armhf (3.3.0+dfsg-5 to 3.3.0+dfsg-5)
  • Migration status for qzxing/armhf (3.3.0+dfsg-5 to 3.3.0+dfsg-5): Will attempt migration (Any information below is purely informational)
• qzxing/ppc64el (3.3.0+dfsg-5 to 3.3.0+dfsg-5)
  • Migration status for qzxing/ppc64el (3.3.0+dfsg-5 to 3.3.0+dfsg-5): Will attempt migration (Any information below is purely informational)
• rapidcheck/arm64 (0~1048-a5724ea-1 to 0~1048-a5724ea-1)
  • Migration status for rapidcheck/arm64 (0~1048-a5724ea-1 to 0~1048-a5724ea-1): Will attempt migration (Any information below is purely informational)
• rapidcheck/armel (0~1048-a5724ea-1 to 0~1048-a5724ea-1)
  • Migration status for rapidcheck/armel (0~1048-a5724ea-1 to 0~1048-a5724ea-1): Will attempt migration (Any information below is purely informational)
• rapidcheck/armhf (0~1048-a5724ea-1 to 0~1048-a5724ea-1)
  • Migration status for rapidcheck/armhf (0~1048-a5724ea-1 to 0~1048-a5724ea-1): Will attempt migration (Any information below is purely informational)
• rapidcheck/ppc64el (0~1048-a5724ea-1 to 0~1048-a5724ea-1)
  • Migration status for rapidcheck/ppc64el (0~1048-a5724ea-1 to 0~1048-a5724ea-1): Will attempt migration (Any information below is purely informational)
• raptor2/arm64 (2.0.16-3 to 2.0.16-3)
  • Migration status for raptor2/arm64 (2.0.16-3 to 2.0.16-3): Will attempt migration (Any information below is purely informational)
• raptor2/armel (2.0.16-3 to 2.0.16-3)
  • Migration status for raptor2/armel (2.0.16-3 to 2.0.16-3): Will attempt migration (Any information below is purely informational)
• raptor2/armhf (2.0.16-3 to 2.0.16-3)
  • Migration status for raptor2/armhf (2.0.16-3 to 2.0.16-3): Will attempt migration (Any information below is purely informational)
• raptor2/ppc64el (2.0.16-3 to 2.0.16-3)
  • Migration status for raptor2/ppc64el (2.0.16-3 to 2.0.16-3): Will attempt migration (Any information below is purely informational)
• raqm/arm64 (0.10.1-1 to 0.10.1-1)
  • Migration status for raqm/arm64 (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• raqm/armel (0.10.1-1 to 0.10.1-1)
  • Migration status for raqm/armel (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• raqm/armhf (0.10.1-1 to 0.10.1-1)
  • Migration status for raqm/armhf (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• raqm/ppc64el (0.10.1-1 to 0.10.1-1)
  • Migration status for raqm/ppc64el (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• rasqal/arm64 (0.9.33-2 to 0.9.33-2)
  • Migration status for rasqal/arm64 (0.9.33-2 to 0.9.33-2): Will attempt migration (Any information below is purely informational)
• rasqal/armel (0.9.33-2 to 0.9.33-2)
  • Migration status for rasqal/armel (0.9.33-2 to 0.9.33-2): Will attempt migration (Any information below is purely informational)
• rasqal/armhf (0.9.33-2 to 0.9.33-2)
  • Migration status for rasqal/armhf (0.9.33-2 to 0.9.33-2): Will attempt migration (Any information below is purely informational)
• rasqal/ppc64el (0.9.33-2 to 0.9.33-2)
  • Migration status for rasqal/ppc64el (0.9.33-2 to 0.9.33-2): Will attempt migration (Any information below is purely informational)
• rcheevos/arm64 (10.7.1-1 to 10.7.1-1)
  • Migration status for rcheevos/arm64 (10.7.1-1 to 10.7.1-1): Will attempt migration (Any information below is purely informational)
• rcheevos/armel (10.7.1-1 to 10.7.1-1)
  • Migration status for rcheevos/armel (10.7.1-1 to 10.7.1-1): Will attempt migration (Any information below is purely informational)
• rcheevos/armhf (10.7.1-1 to 10.7.1-1)
  • Migration status for rcheevos/armhf (10.7.1-1 to 10.7.1-1): Will attempt migration (Any information below is purely informational)
• rcheevos/ppc64el (10.7.1-1 to 10.7.1-1)
  • Migration status for rcheevos/ppc64el (10.7.1-1 to 10.7.1-1): Will attempt migration (Any information below is purely informational)
• readline/arm64 (8.2-3 to 8.2-3)
  • Migration status for readline/arm64 (8.2-3 to 8.2-3): Will attempt migration (Any information below is purely informational)
• readline/armel (8.2-3 to 8.2-3)
  • Migration status for readline/armel (8.2-3 to 8.2-3): Will attempt migration (Any information below is purely informational)
• readline/armhf (8.2-3 to 8.2-3)
  • Migration status for readline/armhf (8.2-3 to 8.2-3): Will attempt migration (Any information below is purely informational)
• readline/ppc64el (8.2-3 to 8.2-3)
  • Migration status for readline/ppc64el (8.2-3 to 8.2-3): Will attempt migration (Any information below is purely informational)
• readosm/arm64 (1:1.1.0a+dfsg-2 to 1:1.1.0a+dfsg-2)
  • Migration status for readosm/arm64 (1:1.1.0a+dfsg-2 to 1:1.1.0a+dfsg-2): Will attempt migration (Any information below is purely informational)
• readosm/armel (1:1.1.0a+dfsg-2 to 1:1.1.0a+dfsg-2)
  • Migration status for readosm/armel (1:1.1.0a+dfsg-2 to 1:1.1.0a+dfsg-2): Will attempt migration (Any information below is purely informational)
• readosm/armhf (1:1.1.0a+dfsg-2 to 1:1.1.0a+dfsg-2)
  • Migration status for readosm/armhf (1:1.1.0a+dfsg-2 to 1:1.1.0a+dfsg-2): Will attempt migration (Any information below is purely informational)
• readosm/ppc64el (1:1.1.0a+dfsg-2 to 1:1.1.0a+dfsg-2)
  • Migration status for readosm/ppc64el (1:1.1.0a+dfsg-2 to 1:1.1.0a+dfsg-2): Will attempt migration (Any information below is purely informational)
• readstat/arm64 (1.1.9-2 to 1.1.9-2)
  • Migration status for readstat/arm64 (1.1.9-2 to 1.1.9-2): Will attempt migration (Any information below is purely informational)
• readstat/armel (1.1.9-2 to 1.1.9-2)
  • Migration status for readstat/armel (1.1.9-2 to 1.1.9-2): Will attempt migration (Any information below is purely informational)
• readstat/armhf (1.1.9-2 to 1.1.9-2)
  • Migration status for readstat/armhf (1.1.9-2 to 1.1.9-2): Will attempt migration (Any information below is purely informational)
• readstat/ppc64el (1.1.9-2 to 1.1.9-2)
  • Migration status for readstat/ppc64el (1.1.9-2 to 1.1.9-2): Will attempt migration (Any information below is purely informational)
• recode/arm64 (3.6-25 to 3.6-25)
  • Migration status for recode/arm64 (3.6-25 to 3.6-25): Will attempt migration (Any information below is purely informational)
• recode/armel (3.6-25 to 3.6-25)
  • Migration status for recode/armel (3.6-25 to 3.6-25): Will attempt migration (Any information below is purely informational)
• recode/armhf (3.6-25 to 3.6-25)
  • Migration status for recode/armhf (3.6-25 to 3.6-25): Will attempt migration (Any information below is purely informational)
• recode/ppc64el (3.6-25 to 3.6-25)
  • Migration status for recode/ppc64el (3.6-25 to 3.6-25): Will attempt migration (Any information below is purely informational)
• recutils/arm64 (1.9-3 to 1.9-3)
  • Migration status for recutils/arm64 (1.9-3 to 1.9-3): Will attempt migration (Any information below is purely informational)
• recutils/armel (1.9-3 to 1.9-3)
  • Migration status for recutils/armel (1.9-3 to 1.9-3): Will attempt migration (Any information below is purely informational)
• recutils/armhf (1.9-3 to 1.9-3)
  • Migration status for recutils/armhf (1.9-3 to 1.9-3): Will attempt migration (Any information below is purely informational)
• recutils/ppc64el (1.9-3 to 1.9-3)
  • Migration status for recutils/ppc64el (1.9-3 to 1.9-3): Will attempt migration (Any information below is purely informational)
• redland/arm64 (1.0.17-3 to 1.0.17-3)
  • Migration status for redland/arm64 (1.0.17-3 to 1.0.17-3): Will attempt migration (Any information below is purely informational)
• redland/armel (1.0.17-3 to 1.0.17-3)
  • Migration status for redland/armel (1.0.17-3 to 1.0.17-3): Will attempt migration (Any information below is purely informational)
• redland/armhf (1.0.17-3 to 1.0.17-3)
  • Migration status for redland/armhf (1.0.17-3 to 1.0.17-3): Will attempt migration (Any information below is purely informational)
• redland/ppc64el (1.0.17-3 to 1.0.17-3)
  • Migration status for redland/ppc64el (1.0.17-3 to 1.0.17-3): Will attempt migration (Any information below is purely informational)
• rem/arm64 (0.6.0-4 to 0.6.0-4)
  • Migration status for rem/arm64 (0.6.0-4 to 0.6.0-4): Will attempt migration (Any information below is purely informational)
• rem/armel (0.6.0-4 to 0.6.0-4)
  • Migration status for rem/armel (0.6.0-4 to 0.6.0-4): Will attempt migration (Any information below is purely informational)
• rem/armhf (0.6.0-4 to 0.6.0-4)
  • Migration status for rem/armhf (0.6.0-4 to 0.6.0-4): Will attempt migration (Any information below is purely informational)
• rem/ppc64el (0.6.0-4 to 0.6.0-4)
  • Migration status for rem/ppc64el (0.6.0-4 to 0.6.0-4): Will attempt migration (Any information below is purely informational)
• resolv-wrapper/arm64 (1.1.8-2 to 1.1.8-2)
  • Migration status for resolv-wrapper/arm64 (1.1.8-2 to 1.1.8-2): Will attempt migration (Any information below is purely informational)
• resolv-wrapper/armel (1.1.8-2 to 1.1.8-2)
  • Migration status for resolv-wrapper/armel (1.1.8-2 to 1.1.8-2): Will attempt migration (Any information below is purely informational)
• resolv-wrapper/armhf (1.1.8-2 to 1.1.8-2)
  • Migration status for resolv-wrapper/armhf (1.1.8-2 to 1.1.8-2): Will attempt migration (Any information below is purely informational)
• resolv-wrapper/ppc64el (1.1.8-2 to 1.1.8-2)
  • Migration status for resolv-wrapper/ppc64el (1.1.8-2 to 1.1.8-2): Will attempt migration (Any information below is purely informational)
• restinio/arm64 (0.6.19+ds-1 to 0.6.19+ds-1)
  • Migration status for restinio/arm64 (0.6.19+ds-1 to 0.6.19+ds-1): Will attempt migration (Any information below is purely informational)
• restinio/armhf (0.6.19+ds-1 to 0.6.19+ds-1)
  • Migration status for restinio/armhf (0.6.19+ds-1 to 0.6.19+ds-1): Will attempt migration (Any information below is purely informational)
• restinio/ppc64el (0.6.19+ds-1 to 0.6.19+ds-1)
  • Migration status for restinio/ppc64el (0.6.19+ds-1 to 0.6.19+ds-1): Will attempt migration (Any information below is purely informational)
• rgxg/arm64 (0.1.2-5 to 0.1.2-5)
  • Migration status for rgxg/arm64 (0.1.2-5 to 0.1.2-5): Will attempt migration (Any information below is purely informational)
• rgxg/armel (0.1.2-5 to 0.1.2-5)
  • Migration status for rgxg/armel (0.1.2-5 to 0.1.2-5): Will attempt migration (Any information below is purely informational)
• rgxg/armhf (0.1.2-5 to 0.1.2-5)
  • Migration status for rgxg/armhf (0.1.2-5 to 0.1.2-5): Will attempt migration (Any information below is purely informational)
• rgxg/ppc64el (0.1.2-5 to 0.1.2-5)
  • Migration status for rgxg/ppc64el (0.1.2-5 to 0.1.2-5): Will attempt migration (Any information below is purely informational)
• rhash/arm64 (1.4.3-3 to 1.4.3-3)
  • Migration status for rhash/arm64 (1.4.3-3 to 1.4.3-3): Will attempt migration (Any information below is purely informational)
• rhash/armel (1.4.3-3 to 1.4.3-3)
  • Migration status for rhash/armel (1.4.3-3 to 1.4.3-3): Will attempt migration (Any information below is purely informational)
• rhash/armhf (1.4.3-3 to 1.4.3-3)
  • Migration status for rhash/armhf (1.4.3-3 to 1.4.3-3): Will attempt migration (Any information below is purely informational)
• rhash/ppc64el (1.4.3-3 to 1.4.3-3)
  • Migration status for rhash/ppc64el (1.4.3-3 to 1.4.3-3): Will attempt migration (Any information below is purely informational)
• riemann-c-client/arm64 (1.10.4-3 to 1.10.4-3)
  • Migration status for riemann-c-client/arm64 (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• riemann-c-client/armel (1.10.4-3 to 1.10.4-3)
  • Migration status for riemann-c-client/armel (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• riemann-c-client/armhf (1.10.4-3 to 1.10.4-3)
  • Migration status for riemann-c-client/armhf (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• riemann-c-client/ppc64el (1.10.4-3 to 1.10.4-3)
  • Migration status for riemann-c-client/ppc64el (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• rlottie/arm64 (0.1+dfsg-4 to 0.1+dfsg-4)
  • Migration status for rlottie/arm64 (0.1+dfsg-4 to 0.1+dfsg-4): Will attempt migration (Any information below is purely informational)
• rlottie/armel (0.1+dfsg-4 to 0.1+dfsg-4)
  • Migration status for rlottie/armel (0.1+dfsg-4 to 0.1+dfsg-4): Will attempt migration (Any information below is purely informational)
• rlottie/armhf (0.1+dfsg-4 to 0.1+dfsg-4)
  • Migration status for rlottie/armhf (0.1+dfsg-4 to 0.1+dfsg-4): Will attempt migration (Any information below is purely informational)
• rlottie/ppc64el (0.1+dfsg-4 to 0.1+dfsg-4)
  • Migration status for rlottie/ppc64el (0.1+dfsg-4 to 0.1+dfsg-4): Will attempt migration (Any information below is purely informational)
• robot-testing-framework/arm64 (2.0.1+ds1-3 to 2.0.1+ds1-3)
  • Migration status for robot-testing-framework/arm64 (2.0.1+ds1-3 to 2.0.1+ds1-3): Will attempt migration (Any information below is purely informational)
• robot-testing-framework/armhf (2.0.1+ds1-3 to 2.0.1+ds1-3)
  • Migration status for robot-testing-framework/armhf (2.0.1+ds1-3 to 2.0.1+ds1-3): Will attempt migration (Any information below is purely informational)
• robot-testing-framework/ppc64el (2.0.1+ds1-3 to 2.0.1+ds1-3)
  • Migration status for robot-testing-framework/ppc64el (2.0.1+ds1-3 to 2.0.1+ds1-3): Will attempt migration (Any information below is purely informational)
• ros-bond-core/arm64 (1.8.6-10 to 1.8.6-10)
  • Migration status for ros-bond-core/arm64 (1.8.6-10 to 1.8.6-10): Will attempt migration (Any information below is purely informational)
• ros-bond-core/armhf (1.8.6-10 to 1.8.6-10)
  • Migration status for ros-bond-core/armhf (1.8.6-10 to 1.8.6-10): Will attempt migration (Any information below is purely informational)
• ros-bond-core/ppc64el (1.8.6-10 to 1.8.6-10)
  • Migration status for ros-bond-core/ppc64el (1.8.6-10 to 1.8.6-10): Will attempt migration (Any information below is purely informational)
• ros-common-msgs/arm64 (1.13.1-2 to 1.13.1-2)
  • Migration status for ros-common-msgs/arm64 (1.13.1-2 to 1.13.1-2): Will attempt migration (Any information below is purely informational)
• ros-common-msgs/armhf (1.13.1-2 to 1.13.1-2)
  • Migration status for ros-common-msgs/armhf (1.13.1-2 to 1.13.1-2): Will attempt migration (Any information below is purely informational)
• ros-common-msgs/ppc64el (1.13.1-2 to 1.13.1-2)
  • Migration status for ros-common-msgs/ppc64el (1.13.1-2 to 1.13.1-2): Will attempt migration (Any information below is purely informational)
• ros-dynamic-reconfigure/arm64 (1.7.3-1 to 1.7.3-1)
  • Migration status for ros-dynamic-reconfigure/arm64 (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
• ros-dynamic-reconfigure/armhf (1.7.3-1 to 1.7.3-1)
  • Migration status for ros-dynamic-reconfigure/armhf (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
• ros-dynamic-reconfigure/ppc64el (1.7.3-1 to 1.7.3-1)
  • Migration status for ros-dynamic-reconfigure/ppc64el (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
• ros-image-transport-plugins/arm64 (1.15.0-3 to 1.15.0-3)
  • Migration status for ros-image-transport-plugins/arm64 (1.15.0-3 to 1.15.0-3): Will attempt migration (Any information below is purely informational)
• ros-image-transport-plugins/armhf (1.15.0-3 to 1.15.0-3)
  • Migration status for ros-image-transport-plugins/armhf (1.15.0-3 to 1.15.0-3): Will attempt migration (Any information below is purely informational)
• ros-image-transport-plugins/ppc64el (1.15.0-3 to 1.15.0-3)
  • Migration status for ros-image-transport-plugins/ppc64el (1.15.0-3 to 1.15.0-3): Will attempt migration (Any information below is purely informational)
• ros-interactive-markers/arm64 (1.12.0-9 to 1.12.0-9)
  • Migration status for ros-interactive-markers/arm64 (1.12.0-9 to 1.12.0-9): Will attempt migration (Any information below is purely informational)
• ros-interactive-markers/armhf (1.12.0-9 to 1.12.0-9)
  • Migration status for ros-interactive-markers/armhf (1.12.0-9 to 1.12.0-9): Will attempt migration (Any information below is purely informational)
• ros-interactive-markers/ppc64el (1.12.0-9 to 1.12.0-9)
  • Migration status for ros-interactive-markers/ppc64el (1.12.0-9 to 1.12.0-9): Will attempt migration (Any information below is purely informational)
• ros-laser-geometry/arm64 (1.6.7-5 to 1.6.7-5)
  • Migration status for ros-laser-geometry/arm64 (1.6.7-5 to 1.6.7-5): Will attempt migration (Any information below is purely informational)
• ros-laser-geometry/armhf (1.6.7-5 to 1.6.7-5)
  • Migration status for ros-laser-geometry/armhf (1.6.7-5 to 1.6.7-5): Will attempt migration (Any information below is purely informational)
• ros-laser-geometry/ppc64el (1.6.7-5 to 1.6.7-5)
  • Migration status for ros-laser-geometry/ppc64el (1.6.7-5 to 1.6.7-5): Will attempt migration (Any information below is purely informational)
• ros-message-runtime/arm64 (0.4.13-5 to 0.4.13-5)
  • Migration status for ros-message-runtime/arm64 (0.4.13-5 to 0.4.13-5): Will attempt migration (Any information below is purely informational)
• ros-message-runtime/armhf (0.4.13-5 to 0.4.13-5)
  • Migration status for ros-message-runtime/armhf (0.4.13-5 to 0.4.13-5): Will attempt migration (Any information below is purely informational)
• ros-message-runtime/ppc64el (0.4.13-5 to 0.4.13-5)
  • Migration status for ros-message-runtime/ppc64el (0.4.13-5 to 0.4.13-5): Will attempt migration (Any information below is purely informational)
• ros-navigation-msgs/arm64 (1.14.1-3 to 1.14.1-3)
  • Migration status for ros-navigation-msgs/arm64 (1.14.1-3 to 1.14.1-3): Will attempt migration (Any information below is purely informational)
• ros-navigation-msgs/armhf (1.14.1-3 to 1.14.1-3)
  • Migration status for ros-navigation-msgs/armhf (1.14.1-3 to 1.14.1-3): Will attempt migration (Any information below is purely informational)
• ros-navigation-msgs/ppc64el (1.14.1-3 to 1.14.1-3)
  • Migration status for ros-navigation-msgs/ppc64el (1.14.1-3 to 1.14.1-3): Will attempt migration (Any information below is purely informational)
• ros-resource-retriever/arm64 (1.12.7-4 to 1.12.7-4)
  • Migration status for ros-resource-retriever/arm64 (1.12.7-4 to 1.12.7-4): Will attempt migration (Any information below is purely informational)
• ros-resource-retriever/armhf (1.12.7-4 to 1.12.7-4)
  • Migration status for ros-resource-retriever/armhf (1.12.7-4 to 1.12.7-4): Will attempt migration (Any information below is purely informational)
• ros-resource-retriever/ppc64el (1.12.7-4 to 1.12.7-4)
  • Migration status for ros-resource-retriever/ppc64el (1.12.7-4 to 1.12.7-4): Will attempt migration (Any information below is purely informational)
• ros-ros-comm-msgs/arm64 (1.11.3-3 to 1.11.3-3)
  • Migration status for ros-ros-comm-msgs/arm64 (1.11.3-3 to 1.11.3-3): Will attempt migration (Any information below is purely informational)
• ros-ros-comm-msgs/armhf (1.11.3-3 to 1.11.3-3)
  • Migration status for ros-ros-comm-msgs/armhf (1.11.3-3 to 1.11.3-3): Will attempt migration (Any information below is purely informational)
• ros-ros-comm-msgs/ppc64el (1.11.3-3 to 1.11.3-3)
  • Migration status for ros-ros-comm-msgs/ppc64el (1.11.3-3 to 1.11.3-3): Will attempt migration (Any information below is purely informational)
• ros-ros/arm64 (1.15.8-5 to 1.15.8-5)
  • Migration status for ros-ros/arm64 (1.15.8-5 to 1.15.8-5): Will attempt migration (Any information below is purely informational)
• ros-ros/armhf (1.15.8-5 to 1.15.8-5)
  • Migration status for ros-ros/armhf (1.15.8-5 to 1.15.8-5): Will attempt migration (Any information below is purely informational)
• ros-ros/ppc64el (1.15.8-5 to 1.15.8-5)
  • Migration status for ros-ros/ppc64el (1.15.8-5 to 1.15.8-5): Will attempt migration (Any information below is purely informational)
• ros-roscpp-core/arm64 (0.7.3-1 to 0.7.3-1)
  • Migration status for ros-roscpp-core/arm64 (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• ros-roscpp-core/armhf (0.7.3-1 to 0.7.3-1)
  • Migration status for ros-roscpp-core/armhf (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• ros-roscpp-core/ppc64el (0.7.3-1 to 0.7.3-1)
  • Migration status for ros-roscpp-core/ppc64el (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• ros-std-msgs/arm64 (0.5.13-3 to 0.5.13-3)
  • Migration status for ros-std-msgs/arm64 (0.5.13-3 to 0.5.13-3): Will attempt migration (Any information below is purely informational)
• ros-std-msgs/armhf (0.5.13-3 to 0.5.13-3)
  • Migration status for ros-std-msgs/armhf (0.5.13-3 to 0.5.13-3): Will attempt migration (Any information below is purely informational)
• ros-std-msgs/ppc64el (0.5.13-3 to 0.5.13-3)
  • Migration status for ros-std-msgs/ppc64el (0.5.13-3 to 0.5.13-3): Will attempt migration (Any information below is purely informational)
• ros2-ament-index/arm64 (1.7.0-1 to 1.7.0-1)
  • Migration status for ros2-ament-index/arm64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ros2-ament-index/armhf (1.7.0-1 to 1.7.0-1)
  • Migration status for ros2-ament-index/armhf (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ros2-ament-index/ppc64el (1.7.0-1 to 1.7.0-1)
  • Migration status for ros2-ament-index/ppc64el (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ros2-osrf-testing-tools-cpp/arm64 (1.7.0+ds-1 to 1.7.0+ds-1)
  • Migration status for ros2-osrf-testing-tools-cpp/arm64 (1.7.0+ds-1 to 1.7.0+ds-1): Will attempt migration (Any information below is purely informational)
• ros2-osrf-testing-tools-cpp/armhf (1.7.0+ds-1 to 1.7.0+ds-1)
  • Migration status for ros2-osrf-testing-tools-cpp/armhf (1.7.0+ds-1 to 1.7.0+ds-1): Will attempt migration (Any information below is purely informational)
• ros2-osrf-testing-tools-cpp/ppc64el (1.7.0+ds-1 to 1.7.0+ds-1)
  • Migration status for ros2-osrf-testing-tools-cpp/ppc64el (1.7.0+ds-1 to 1.7.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-sanitize_pu (6.0.2-2 to 6.0.0-1.1+deb12u1)
  • Migration status for ruby-sanitize_pu (6.0.2-2 to 6.0.0-1.1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ruby-sanitize is newer in the target suite (6.0.2-2 6.0.0-1.1+deb12u1)
• rust-arrayvec/mips64el (0.7.4-2 to 0.7.4-2)
  • Migration status for rust-arrayvec/mips64el (0.7.4-2 to 0.7.4-2): Will attempt migration (Any information below is purely informational)
• rw/arm64 (0.9+ds1-1 to 0.9+ds1-1)
  • Migration status for rw/arm64 (0.9+ds1-1 to 0.9+ds1-1): Will attempt migration (Any information below is purely informational)
• rw/armhf (0.9+ds1-1 to 0.9+ds1-1)
  • Migration status for rw/armhf (0.9+ds1-1 to 0.9+ds1-1): Will attempt migration (Any information below is purely informational)
• rw/ppc64el (0.9+ds1-1 to 0.9+ds1-1)
  • Migration status for rw/ppc64el (0.9+ds1-1 to 0.9+ds1-1): Will attempt migration (Any information below is purely informational)
• rxp/arm64 (1.5.0-3 to 1.5.0-3)
  • Migration status for rxp/arm64 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
• rxp/armhf (1.5.0-3 to 1.5.0-3)
  • Migration status for rxp/armhf (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
• rxp/ppc64el (1.5.0-3 to 1.5.0-3)
  • Migration status for rxp/ppc64el (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
• sambamba/amd64 (1.0.1+dfsg-1 to 1.0.1+dfsg-1)
  • Migration status for sambamba/amd64 (1.0.1+dfsg-1 to 1.0.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: sambamba/amd64 ldc (not considered)
    • Invalidated by dependency
• sambamba/arm64 (1.0.1+dfsg-1 to 1.0.1+dfsg-1)
  • Migration status for sambamba/arm64 (1.0.1+dfsg-1 to 1.0.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: sambamba/arm64 ldc (not considered)
    • Invalidated by dependency
• sexplib310/amd64 (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/amd64 (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: sexplib310/amd64 ocaml-num
    • Implicit dependency: sexplib310/amd64 ocaml-conduit
    • Implicit dependency: sexplib310/amd64 ocaml-cstruct/amd64
    • Implicit dependency: sexplib310/amd64 ocsigenserver/amd64
    • Implicit dependency: sexplib310/amd64 pgocaml/amd64
• sexplib310/arm64 (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/arm64 (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: sexplib310/arm64 ocaml-num
    • Implicit dependency: sexplib310/arm64 ocaml-conduit
    • Implicit dependency: sexplib310/arm64 ocaml-cstruct/arm64
    • Implicit dependency: sexplib310/arm64 ocsigenserver/arm64
    • Implicit dependency: sexplib310/arm64 pgocaml/arm64
• sexplib310/armel (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/armel (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: sexplib310/armel ocaml-num
    • Implicit dependency: sexplib310/armel ocaml-conduit
    • Implicit dependency: sexplib310/armel ocaml-cstruct/armel
    • Implicit dependency: sexplib310/armel ocsigenserver/armel
    • Implicit dependency: sexplib310/armel pgocaml/armel
• sexplib310/armhf (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/armhf (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: sexplib310/armhf ocaml-num
    • Implicit dependency: sexplib310/armhf ocaml-conduit
    • Implicit dependency: sexplib310/armhf ocaml-cstruct/armhf
    • Implicit dependency: sexplib310/armhf ocsigenserver/armhf
    • Implicit dependency: sexplib310/armhf pgocaml/armhf
• sexplib310/i386 (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/i386 (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: sexplib310/i386 ocaml-num
    • Implicit dependency: sexplib310/i386 ocaml-conduit
    • Implicit dependency: sexplib310/i386 ocaml-cstruct/i386
    • Implicit dependency: sexplib310/i386 ocsigenserver/i386
    • Implicit dependency: sexplib310/i386 pgocaml/i386
• sexplib310/mips64el (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/mips64el (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: sexplib310/mips64el ocaml-num
    • Implicit dependency: sexplib310/mips64el ocaml-conduit
    • Implicit dependency: sexplib310/mips64el ocaml-cstruct/mips64el
    • Implicit dependency: sexplib310/mips64el ocsigenserver/mips64el
    • Implicit dependency: sexplib310/mips64el pgocaml/mips64el
• sexplib310/ppc64el (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/ppc64el (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: sexplib310/ppc64el ocaml-num
    • Implicit dependency: sexplib310/ppc64el ocaml-conduit
    • Implicit dependency: sexplib310/ppc64el ocaml-cstruct/ppc64el
    • Implicit dependency: sexplib310/ppc64el ocsigenserver/ppc64el
    • Implicit dependency: sexplib310/ppc64el pgocaml/ppc64el
• sexplib310/s390x (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/s390x (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: sexplib310/s390x ocaml-num
    • Implicit dependency: sexplib310/s390x ocaml-conduit
    • Implicit dependency: sexplib310/s390x ocaml-cstruct/s390x
    • Implicit dependency: sexplib310/s390x ocsigenserver/s390x
    • Implicit dependency: sexplib310/s390x pgocaml/s390x
• simgrid/amd64 (3.35-1 to 3.35-1)
  • Migration status for simgrid/amd64 (3.35-1 to 3.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simgrid/amd64 ns3 (not considered)
    • Invalidated by dependency
• simgrid/arm64 (3.35-1 to 3.35-1)
  • Migration status for simgrid/arm64 (3.35-1 to 3.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simgrid/arm64 ns3 (not considered)
    • Invalidated by dependency
• simgrid/armel (3.35-1 to 3.35-1)
  • Migration status for simgrid/armel (3.35-1 to 3.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simgrid/armel ns3 (not considered)
    • Invalidated by dependency
• simgrid/armhf (3.35-1 to 3.35-1)
  • Migration status for simgrid/armhf (3.35-1 to 3.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simgrid/armhf ns3 (not considered)
    • Invalidated by dependency
• simgrid/i386 (3.35-1 to 3.35-1)
  • Migration status for simgrid/i386 (3.35-1 to 3.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simgrid/i386 ns3 (not considered)
    • Invalidated by dependency
• simgrid/mips64el (3.35-1 to 3.35-1)
  • Migration status for simgrid/mips64el (3.35-1 to 3.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simgrid/mips64el ns3 (not considered)
    • Invalidated by dependency
• simgrid/ppc64el (3.35-1 to 3.35-1)
  • Migration status for simgrid/ppc64el (3.35-1 to 3.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simgrid/ppc64el ns3 (not considered)
    • Invalidated by dependency
• simgrid/s390x (3.35-1 to 3.35-1)
  • Migration status for simgrid/s390x (3.35-1 to 3.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simgrid/s390x ns3 (not considered)
    • Invalidated by dependency
• slurm-wlm-contrib_pu (- to 22.05.8-4+deb12u2)
  • Migration status for slurm-wlm-contrib_pu (- to 22.05.8-4+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • slurm-wlm-nvml-plugin/amd64 has unsatisfiable dependency
    • slurm-wlm-nvml-plugin-dev/amd64 has unsatisfiable dependency
    • NEEDS APPROVAL BY RM
• slurm-wlm/amd64 (23.11.3-2 to 23.11.3-2)
  • Migration status for slurm-wlm/amd64 (23.11.3-2 to 23.11.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: slurm-wlm/amd64 libjwt (not considered)
    • Invalidated by dependency
• slurm-wlm/arm64 (23.11.3-2 to 23.11.3-2)
  • Migration status for slurm-wlm/arm64 (23.11.3-2 to 23.11.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: slurm-wlm/arm64 libjwt (not considered)
    • Invalidated by dependency
• slurm-wlm/armel (23.11.3-2 to 23.11.3-2)
  • Migration status for slurm-wlm/armel (23.11.3-2 to 23.11.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: slurm-wlm/armel libjwt (not considered)
    • Invalidated by dependency
• slurm-wlm/armhf (23.11.3-2 to 23.11.3-2)
  • Migration status for slurm-wlm/armhf (23.11.3-2 to 23.11.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: slurm-wlm/armhf libjwt (not considered)
    • Invalidated by dependency
• slurm-wlm/i386 (23.11.3-2 to 23.11.3-2)
  • Migration status for slurm-wlm/i386 (23.11.3-2 to 23.11.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: slurm-wlm/i386 libjwt (not considered)
    • Invalidated by dependency
• slurm-wlm/mips64el (23.11.3-2 to 23.11.3-2)
  • Migration status for slurm-wlm/mips64el (23.11.3-2 to 23.11.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: slurm-wlm/mips64el libjwt (not considered)
    • Invalidated by dependency
• slurm-wlm/ppc64el (23.11.3-2 to 23.11.3-2)
  • Migration status for slurm-wlm/ppc64el (23.11.3-2 to 23.11.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: slurm-wlm/ppc64el libjwt (not considered)
    • Invalidated by dependency
• slurm-wlm/s390x (23.11.3-2 to 23.11.3-2)
  • Migration status for slurm-wlm/s390x (23.11.3-2 to 23.11.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: slurm-wlm/s390x libjwt (not considered)
    • Invalidated by dependency
• ssreflect/amd64 (2.1.0-1 to 2.1.0-1)
  • Migration status for ssreflect/amd64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ssreflect/amd64 coq-hierarchy-builder/amd64
    • Implicit dependency: ssreflect/amd64 coq-deriving/amd64
    • Implicit dependency: ssreflect/amd64 coq-extructures/amd64
    • Implicit dependency: ssreflect/amd64 coq-interval/amd64
    • Implicit dependency: ssreflect/amd64 coq-quickchick/amd64
    • Implicit dependency: ssreflect/amd64 coq-reglang/amd64
    • Implicit dependency: ssreflect/amd64 coq-relation-algebra/amd64
    • Implicit dependency: ssreflect/amd64 coqeal/amd64
    • Implicit dependency: ssreflect/amd64 coquelicot/amd64
    • Implicit dependency: ssreflect/amd64 mathcomp-algebra-tactics/amd64
    • Implicit dependency: ssreflect/amd64 mathcomp-analysis/amd64
    • Implicit dependency: ssreflect/amd64 mathcomp-bigenough/amd64
    • Implicit dependency: ssreflect/amd64 mathcomp-finmap/amd64
    • Implicit dependency: ssreflect/amd64 mathcomp-multinomials/amd64
    • Implicit dependency: ssreflect/amd64 mathcomp-real-closed/amd64
    • Implicit dependency: ssreflect/amd64 mathcomp-zify/amd64
• ssreflect/arm64 (2.1.0-1 to 2.1.0-1)
  • Migration status for ssreflect/arm64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ssreflect/arm64 coq-hierarchy-builder/arm64
    • Implicit dependency: ssreflect/arm64 coq-deriving/arm64
    • Implicit dependency: ssreflect/arm64 coq-extructures/arm64
    • Implicit dependency: ssreflect/arm64 coq-interval/arm64
    • Implicit dependency: ssreflect/arm64 coq-quickchick/arm64
    • Implicit dependency: ssreflect/arm64 coq-reglang/arm64
    • Implicit dependency: ssreflect/arm64 coq-relation-algebra/arm64
    • Implicit dependency: ssreflect/arm64 coqeal/arm64
    • Implicit dependency: ssreflect/arm64 coquelicot/arm64
    • Implicit dependency: ssreflect/arm64 mathcomp-algebra-tactics/arm64
    • Implicit dependency: ssreflect/arm64 mathcomp-analysis/arm64
    • Implicit dependency: ssreflect/arm64 mathcomp-bigenough/arm64
    • Implicit dependency: ssreflect/arm64 mathcomp-finmap/arm64
    • Implicit dependency: ssreflect/arm64 mathcomp-multinomials/arm64
    • Implicit dependency: ssreflect/arm64 mathcomp-real-closed/arm64
    • Implicit dependency: ssreflect/arm64 mathcomp-zify/arm64
• ssreflect/armhf (2.1.0-1 to 2.1.0-1)
  • Migration status for ssreflect/armhf (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ssreflect/armhf coq-hierarchy-builder/armhf
    • Implicit dependency: ssreflect/armhf coq-deriving/armhf
    • Implicit dependency: ssreflect/armhf coq-extructures/armhf
    • Implicit dependency: ssreflect/armhf coq-interval/armhf
    • Implicit dependency: ssreflect/armhf coq-quickchick/armhf
    • Implicit dependency: ssreflect/armhf coq-reglang/armhf
    • Implicit dependency: ssreflect/armhf coq-relation-algebra/armhf
    • Implicit dependency: ssreflect/armhf coqeal/armhf
    • Implicit dependency: ssreflect/armhf coquelicot/armhf
    • Implicit dependency: ssreflect/armhf mathcomp-algebra-tactics/armhf
    • Implicit dependency: ssreflect/armhf mathcomp-analysis/armhf
    • Implicit dependency: ssreflect/armhf mathcomp-bigenough/armhf
    • Implicit dependency: ssreflect/armhf mathcomp-finmap/armhf
    • Implicit dependency: ssreflect/armhf mathcomp-multinomials/armhf
    • Implicit dependency: ssreflect/armhf mathcomp-real-closed/armhf
    • Implicit dependency: ssreflect/armhf mathcomp-zify/armhf
• ssreflect/i386 (2.1.0-1 to 2.1.0-1)
  • Migration status for ssreflect/i386 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ssreflect/i386 coq-hierarchy-builder/i386
    • Implicit dependency: ssreflect/i386 coq-deriving/i386
    • Implicit dependency: ssreflect/i386 coq-extructures/i386
    • Implicit dependency: ssreflect/i386 coq-interval/i386
    • Implicit dependency: ssreflect/i386 coq-quickchick/i386
    • Implicit dependency: ssreflect/i386 coq-reglang/i386
    • Implicit dependency: ssreflect/i386 coq-relation-algebra/i386
    • Implicit dependency: ssreflect/i386 coqeal/i386
    • Implicit dependency: ssreflect/i386 coquelicot/i386
    • Implicit dependency: ssreflect/i386 mathcomp-algebra-tactics/i386
    • Implicit dependency: ssreflect/i386 mathcomp-analysis/i386
    • Implicit dependency: ssreflect/i386 mathcomp-bigenough/i386
    • Implicit dependency: ssreflect/i386 mathcomp-finmap/i386
    • Implicit dependency: ssreflect/i386 mathcomp-multinomials/i386
    • Implicit dependency: ssreflect/i386 mathcomp-real-closed/i386
    • Implicit dependency: ssreflect/i386 mathcomp-zify/i386
• ssreflect/ppc64el (2.1.0-1 to 2.1.0-1)
  • Migration status for ssreflect/ppc64el (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ssreflect/ppc64el coq-hierarchy-builder/ppc64el
    • Implicit dependency: ssreflect/ppc64el coq-deriving/ppc64el
    • Implicit dependency: ssreflect/ppc64el coq-extructures/ppc64el
    • Implicit dependency: ssreflect/ppc64el coq-interval/ppc64el
    • Implicit dependency: ssreflect/ppc64el coq-quickchick/ppc64el
    • Implicit dependency: ssreflect/ppc64el coq-reglang/ppc64el
    • Implicit dependency: ssreflect/ppc64el coq-relation-algebra/ppc64el
    • Implicit dependency: ssreflect/ppc64el coqeal/ppc64el
    • Implicit dependency: ssreflect/ppc64el coquelicot/ppc64el
    • Implicit dependency: ssreflect/ppc64el mathcomp-algebra-tactics/ppc64el
    • Implicit dependency: ssreflect/ppc64el mathcomp-analysis/ppc64el
    • Implicit dependency: ssreflect/ppc64el mathcomp-bigenough/ppc64el
    • Implicit dependency: ssreflect/ppc64el mathcomp-finmap/ppc64el
    • Implicit dependency: ssreflect/ppc64el mathcomp-multinomials/ppc64el
    • Implicit dependency: ssreflect/ppc64el mathcomp-real-closed/ppc64el
    • Implicit dependency: ssreflect/ppc64el mathcomp-zify/ppc64el
• ssreflect/s390x (2.1.0-1 to 2.1.0-1)
  • Migration status for ssreflect/s390x (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: ssreflect/s390x coq-hierarchy-builder/s390x
    • Implicit dependency: ssreflect/s390x coq-deriving/s390x
    • Implicit dependency: ssreflect/s390x coq-extructures/s390x
    • Implicit dependency: ssreflect/s390x coq-interval/s390x
    • Implicit dependency: ssreflect/s390x coq-quickchick/s390x
    • Implicit dependency: ssreflect/s390x coq-reglang/s390x
    • Implicit dependency: ssreflect/s390x coq-relation-algebra/s390x
    • Implicit dependency: ssreflect/s390x coqeal/s390x
    • Implicit dependency: ssreflect/s390x coquelicot/s390x
    • Implicit dependency: ssreflect/s390x mathcomp-algebra-tactics/s390x
    • Implicit dependency: ssreflect/s390x mathcomp-analysis/s390x
    • Implicit dependency: ssreflect/s390x mathcomp-bigenough/s390x
    • Implicit dependency: ssreflect/s390x mathcomp-finmap/s390x
    • Implicit dependency: ssreflect/s390x mathcomp-multinomials/s390x
    • Implicit dependency: ssreflect/s390x mathcomp-real-closed/s390x
    • Implicit dependency: ssreflect/s390x mathcomp-zify/s390x
• tcltk-defaults/arm64 (8.6.13 to 8.6.13)
  • Migration status for tcltk-defaults/arm64 (8.6.13 to 8.6.13): Will attempt migration (Any information below is purely informational)
• tcltk-defaults/armhf (8.6.13 to 8.6.13)
  • Migration status for tcltk-defaults/armhf (8.6.13 to 8.6.13): Will attempt migration (Any information below is purely informational)
• tcltk-defaults/ppc64el (8.6.13 to 8.6.13)
  • Migration status for tcltk-defaults/ppc64el (8.6.13 to 8.6.13): Will attempt migration (Any information below is purely informational)
• tilix/amd64 (1.9.6-1 to 1.9.6-1)
  • Migration status for tilix/amd64 (1.9.6-1 to 1.9.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: tilix/amd64 ldc (not considered)
    • Invalidated by dependency
• tilix/arm64 (1.9.6-1 to 1.9.6-1)
  • Migration status for tilix/arm64 (1.9.6-1 to 1.9.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: tilix/arm64 ldc (not considered)
    • Invalidated by dependency
• tilix/i386 (1.9.6-1 to 1.9.6-1)
  • Migration status for tilix/i386 (1.9.6-1 to 1.9.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: tilix/i386 ldc (not considered)
    • Invalidated by dependency
• unbound_pu (1.19.1-1 to 1.17.1-2+deb12u2)
  • Migration status for unbound_pu (1.19.1-1 to 1.17.1-2+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: unbound is newer in the target suite (1.19.1-1 1.17.1-2+deb12u2)
• utop/amd64 (2.13.1-2 to 2.13.1-2)
  • Migration status for utop/amd64 (2.13.1-2 to 2.13.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: utop/amd64 lwt/amd64
    • Depends: utop/amd64 ocaml-dune
    • Depends: utop/amd64 ocaml-logs/amd64
• utop/arm64 (2.13.1-2 to 2.13.1-2)
  • Migration status for utop/arm64 (2.13.1-2 to 2.13.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: utop/arm64 lwt/arm64
    • Depends: utop/arm64 ocaml-dune
    • Depends: utop/arm64 ocaml-logs/arm64
• utop/armel (2.13.1-2 to 2.13.1-2)
  • Migration status for utop/armel (2.13.1-2 to 2.13.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: utop/armel lwt/armel
    • Depends: utop/armel ocaml-dune
• utop/armhf (2.13.1-2 to 2.13.1-2)
  • Migration status for utop/armhf (2.13.1-2 to 2.13.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: utop/armhf lwt/armhf
    • Depends: utop/armhf ocaml-dune
    • Depends: utop/armhf ocaml-logs/armhf
• utop/i386 (2.13.1-2 to 2.13.1-2)
  • Migration status for utop/i386 (2.13.1-2 to 2.13.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: utop/i386 lwt/i386
    • Depends: utop/i386 ocaml-dune
    • Depends: utop/i386 ocaml-logs/i386
• utop/mips64el (2.13.1-2 to 2.13.1-2)
  • Migration status for utop/mips64el (2.13.1-2 to 2.13.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: utop/mips64el lwt/mips64el
    • Depends: utop/mips64el ocaml-dune
• utop/ppc64el (2.13.1-2 to 2.13.1-2)
  • Migration status for utop/ppc64el (2.13.1-2 to 2.13.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: utop/ppc64el lwt/ppc64el
    • Depends: utop/ppc64el ocaml-dune
    • Depends: utop/ppc64el ocaml-logs/ppc64el
• utop/s390x (2.13.1-2 to 2.13.1-2)
  • Migration status for utop/s390x (2.13.1-2 to 2.13.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: utop/s390x lwt/s390x
    • Depends: utop/s390x ocaml-dune
    • Depends: utop/s390x ocaml-logs/s390x
• wayfire_pu (0.8.0+git20240110-2 to 0.7.4-3+deb12u1)
  • Migration status for wayfire_pu (0.8.0+git20240110-2 to 0.7.4-3+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: wayfire is newer in the target suite (0.8.0+git20240110-2 0.7.4-3+deb12u1)
• why3/amd64 (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/amd64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: why3/amd64 lablgtk3
    • Depends: why3/amd64 menhir
    • Depends: why3/amd64 ocaml-num
• why3/arm64 (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/arm64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: why3/arm64 lablgtk3
    • Depends: why3/arm64 menhir
    • Depends: why3/arm64 ocaml-num
• why3/armel (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/armel (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: why3/armel lablgtk3
    • Depends: why3/armel menhir
    • Depends: why3/armel ocaml-num
• why3/armhf (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/armhf (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: why3/armhf lablgtk3
    • Depends: why3/armhf menhir
    • Depends: why3/armhf ocaml-num
• why3/i386 (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/i386 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: why3/i386 lablgtk3
    • Depends: why3/i386 menhir
    • Depends: why3/i386 ocaml-num
• why3/mips64el (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/mips64el (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: why3/mips64el lablgtk3
    • Depends: why3/mips64el menhir
    • Depends: why3/mips64el ocaml-num
• why3/ppc64el (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/ppc64el (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: why3/ppc64el lablgtk3
    • Depends: why3/ppc64el menhir
    • Depends: why3/ppc64el ocaml-num
• why3/s390x (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/s390x (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: why3/s390x lablgtk3
    • Depends: why3/s390x menhir
    • Depends: why3/s390x ocaml-num
• xfce4-goodies/arm64 (4.18.2 to 4.18.2)
  • Migration status for xfce4-goodies/arm64 (4.18.2 to 4.18.2): Will attempt migration (Any information below is purely informational)
• xfce4-goodies/armhf (4.18.2 to 4.18.2)
  • Migration status for xfce4-goodies/armhf (4.18.2 to 4.18.2): Will attempt migration (Any information below is purely informational)
• xfce4-goodies/ppc64el (4.18.2 to 4.18.2)
  • Migration status for xfce4-goodies/ppc64el (4.18.2 to 4.18.2): Will attempt migration (Any information below is purely informational)
• botan (2.19.3+dfsg-1 to 2.19.4+dfsg-1)
  • Migration status for botan (2.19.3+dfsg-1 to 2.19.4+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 armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • 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/b/botan.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• camitk (5.1.0-1 to 5.2.0-1)
  • Migration status for camitk (5.1.0-1 to 5.2.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camitk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• carburetor (4.5.0-1 to 4.5.1-1)
  • Migration status for carburetor (4.5.0-1 to 4.5.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/c/carburetor.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• finalcif (127+dfsg-2 to 134+dfsg-1)
  • Migration status for finalcif (127+dfsg-2 to 134+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/f/finalcif.html
    • Too young, only 0 of 2 days old
  • Additional info:
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for finalcif/134+dfsg-1: amd64: Pass, arm64: Pass, armhf: 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
• gfxreconstruct (1.0.1+dfsg-1 to 1.0.2+dfsg-1)
  • Migration status for gfxreconstruct (1.0.1+dfsg-1 to 1.0.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/g/gfxreconstruct.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-maps (45.3-1 to 45.4-1)
  • Migration status for gnome-maps (45.3-1 to 45.4-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-maps.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-mattn-go-xmpp (0.0~git20240201.b369b7d-1 to 0.1.0-1)
  • Migration status for golang-github-mattn-go-xmpp (0.0~git20240201.b369b7d-1 to 0.1.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/g/golang-github-mattn-go-xmpp.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-crypton-x509-system (- to 1.6.7-1)
  • Migration status for haskell-crypton-x509-system (- to 1.6.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by i.tsitsimpis@gmail.com
    • Not built on buildd: arch all binaries uploaded by i.tsitsimpis@gmail.com, a new source-only upload is needed to allow migration
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/h/haskell-crypton-x509-system.html
    • Too young, only 0 of 10 days old
    • Build-Depends(-Arch): haskell-crypton-x509-system haskell-crypton-x509-store
    • Build-Depends-Indep: haskell-crypton-x509-system haskell-crypton-x509-store
    • Depends: haskell-crypton-x509-system haskell-crypton-x509-store
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-crypton-x509-validation (- to 1.6.12-1)
  • Migration status for haskell-crypton-x509-validation (- to 1.6.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by i.tsitsimpis@gmail.com
    • Not built on buildd: arch all binaries uploaded by i.tsitsimpis@gmail.com, a new source-only upload is needed to allow migration
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/h/haskell-crypton-x509-validation.html
    • Too young, only 0 of 10 days old
    • Build-Depends(-Arch): haskell-crypton-x509-validation haskell-crypton-x509-store
    • Build-Depends-Indep: haskell-crypton-x509-validation haskell-crypton-x509-store
    • Depends: haskell-crypton-x509-validation haskell-crypton-x509-store
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• httpbin (0.10.1+dfsg-5 to 0.10.2+dfsg-1)
  • Migration status for httpbin (0.10.1+dfsg-5 to 0.10.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/h/httpbin.html
    • Too young, only 0 of 2 days old
  • Additional info:
    • autopkgtest for httpbin/0.10.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• icingaweb2-module-businessprocess (2.4.0-2 to 2.5.0-1)
  • Migration status for icingaweb2-module-businessprocess (2.4.0-2 to 2.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/i/icingaweb2-module-businessprocess.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• icingaweb2-module-cube (1.3.1-1 to 1.3.2-1)
  • Migration status for icingaweb2-module-cube (1.3.1-1 to 1.3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/i/icingaweb2-module-cube.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ioquake3 (1.36+u20231123.972635e+dfsg-1 to 1.36+u20240217.7d711f8+dfsg-1)
  • Migration status for ioquake3 (1.36+u20231123.972635e+dfsg-1 to 1.36+u20240217.7d711f8+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/i/ioquake3.html
    • arch:armhf not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• isc-dhcp (4.4.3-P1-4 to 4.4.3-P1-5)
  • Migration status for isc-dhcp (4.4.3-P1-4 to 4.4.3-P1-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • 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:s390x not built yet, autopkgtest delayed there
    • autopkgtest for isc-dhcp/4.4.3-P1-5: ppc64el: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/isc-dhcp.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• keyman (16.0.145-1 to 17.0.272-1)
  • Migration status for keyman (16.0.145-1 to 17.0.272-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for keyman/17.0.272-1: amd64: Regression or new test ♻ (reference ♻)
    • Not built on buildd: arch amd64 binaries uploaded by 073plan@gmail.com
    • Not built on buildd: arch all binaries uploaded by 073plan@gmail.com, 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 i386
    • missing build on mips64el
    • missing build on ppc64el
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/k/keyman.html
    • 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
    • Too young, only 0 of 5 days old
  • Additional info:
    • 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 ♻
• libcompress-raw-zlib-perl (2.208-1 to 2.208-2)
  • Migration status for libcompress-raw-zlib-perl (2.208-1 to 2.208-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armhf
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/libc/libcompress-raw-zlib-perl.html
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for libcompress-raw-zlib-perl/2.208-2: amd64: Pass, armel: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libfile-loadlines-perl (- to 1.046-1)
  • Migration status for libfile-loadlines-perl (- to 1.046-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by roland, a new source-only upload is needed to allow migration
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/libf/libfile-loadlines-perl.html
    • Too young, only 0 of 7 days old
  • Additional info:
    • autopkgtest for libfile-loadlines-perl/1.046-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libio-compress-perl (2.206-1 to 2.207-1)
  • Migration status for libio-compress-perl (2.206-1 to 2.207-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/libi/libio-compress-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 ♻
• librarian-puppet (3.0.1-1 to 5.0.0-1)
  • Migration status for librarian-puppet (3.0.1-1 to 5.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/libr/librarian-puppet.html
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): librarian-puppet ruby-puppet-forge
  • Additional info:
    • autopkgtest for librarian-puppet/5.0.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libstring-interpolate-named-perl (- to 1.03-1)
  • Migration status for libstring-interpolate-named-perl (- to 1.03-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by roland, a new source-only upload is needed to allow migration
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/libs/libstring-interpolate-named-perl.html
    • Too young, only 0 of 7 days old
  • Additional info:
    • autopkgtest for libstring-interpolate-named-perl/1.03-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libtext-layout-perl (- to 0.035-1)
  • Migration status for libtext-layout-perl (- to 0.035-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by roland, a new source-only upload is needed to allow migration
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/libt/libtext-layout-perl.html
    • Too young, only 0 of 7 days old
  • Additional info:
    • autopkgtest for libtext-layout-perl/0.035-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• llvm-toolchain-18 (- to 1:18.1.0~rc2-4)
  • Migration status for llvm-toolchain-18 (- to 1:18.1.0~rc2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating llvm-toolchain-18 would introduce bugs in testing: #1063048
    • 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 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/l/llvm-toolchain-18.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mediawiki2latex (8.7-3 to 8.7-5)
  • Migration status for mediawiki2latex (8.7-3 to 8.7-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/m/mediawiki2latex.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mongo-c-driver (1.25.4-1 to 1.26.0-1)
  • Migration status for mongo-c-driver (1.25.4-1 to 1.26.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on 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/m/mongo-c-driver.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• network-manager (1.44.2-7 to 1.46.0-1)
  • Migration status for network-manager (1.44.2-7 to 1.46.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
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/n/network-manager.html
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocrad (0.28-3 to 0.28-4)
  • Migration status for ocrad (0.28-3 to 0.28-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/o/ocrad.html
    • Too young, only 0 of 2 days old
  • Additional info:
    • autopkgtest for ocrad/0.28-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• puppet-module-saz-memcached (3.1.0-1 to 8.2.0-1)
  • Migration status for puppet-module-saz-memcached (3.1.0-1 to 8.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for puppet-module-saz-memcached/8.2.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/p/puppet-module-saz-memcached.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pyopenssl (23.2.0-1 to 24.0.0-1)
  • Migration status for pyopenssl (23.2.0-1 to 24.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for barbican/1:17.0.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for foolscap/23.11.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-cheroot/10.0.0+ds1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-oauth2client/4.1.3-5: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Reference test in progress, but real test failed already, ppc64el: Reference test in progress, but real test failed already, s390x: Reference test in progress, but real test failed already
    • autopkgtest for python-scrapy/2.11.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-truststore/0.8.0-2: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for twisted/23.10.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/p/pyopenssl.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pyroute2 (0.7.7-3 to 0.7.7-4)
  • Migration status for pyroute2 (0.7.7-3 to 0.7.7-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyroute2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-blessed (1.19.1-1 to 1.20.0-1)
  • Migration status for python-blessed (1.19.1-1 to 1.20.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/p/python-blessed.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-tz (2024.1-1 to 2024.1-2)
  • Migration status for python-tz (2024.1-1 to 2024.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for flask-restful/0.3.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Reference test in progress, but real test failed already, s390x: Pass
    • autopkgtest for horizon/3:23.3.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for keystone/2:24.0.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for murano-dashboard/1:16.0.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for numpy/1:1.24.2-2: 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: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for pandas/1.5.3+dfsg-12: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Test in progress, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pg8000/1.30.3-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for plotly/5.15.0+dfsg1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for prometheus-xmpp-alerts/0.5.3-1.1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pyhamtools/0.9.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pyrfc3339/1.1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-a38/0.1.8-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-acme/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-caldav/0.11.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-certbot/2.9.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-ciso8601/2.3.1-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-croniter/1.3.15-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-cryptography/41.0.7-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-django-modelcluster/6.2.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-fs/2.4.16-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-graphene/3.3.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-icalendar/5.0.11-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-miio/0.5.12-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-mongomock/4.1.3-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-oslo.serialization/5.2.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-oslo.utils/6.2.1-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Reference test in progress, but real test failed already, s390x: Pass
    • autopkgtest for python-pbcommand/2.1.1+git20220616.3f2e6c2-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for python-recurring-ical-events/2.1.2-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-ring-doorbell/0.8.5-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-tempora/5.5.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-timeline/0.0.7-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-typepy/1.3.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-tz/2024.1-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-x-wr-timezone/0.0.6-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-zeep/4.2.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for pytz-deprecation-shim/0.1.0.post0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for s4cmd/2.1.0+ds-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for sahara-dashboard/19.0.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for skyfield/1.48+ds-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for spyne/2.14.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for stravalib/1.3.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for toil/6.0.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for turing/0.11~beta-7: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for undertime/4.0.0: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for xsar/2024.02.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/p/python-tz.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• roct-thunk-interface (5.2.3+dfsg-1 to 5.7.0-1)
  • Migration status for roct-thunk-interface (5.2.3+dfsg-1 to 5.7.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/roct-thunk-interface.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-puppet-forge (3.0.0-1 to 5.0.3-1)
  • Migration status for ruby-puppet-forge (3.0.0-1 to 5.0.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/ruby-puppet-forge.html
    • autopkgtest for ruby-puppet-forge/5.0.3-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-ahash (0.8.7-5 to 0.8.9-1)
  • Migration status for rust-ahash (0.8.7-5 to 0.8.9-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ahash.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-futures-timer (3.0.2-3 to 3.0.3-1)
  • Migration status for rust-futures-timer (3.0.2-3 to 3.0.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-futures-timer.html
    • autopkgtest for rust-futures-timer/3.0.3-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-rstest/0.17.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-leptonica-plumbing (1.1.0-1 to 1.3.0-1)
  • Migration status for rust-leptonica-plumbing (1.1.0-1 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-leptonica-plumbing.html
    • autopkgtest for rust-leptonica-plumbing/1.3.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-tesseract-plumbing/0.11.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-zerocopy-derive (0.3.1-1 to 0.7.32-1)
  • Migration status for rust-zerocopy-derive (0.3.1-1 to 0.7.32-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-zerocopy-derive-dev/0.7.32-1/amd64 to testing makes librust-zerocopy-dev/0.6.1-1+b1/amd64 uninstallable
    • migrating librust-zerocopy-derive-dev/0.7.32-1/arm64 to testing makes librust-zerocopy-dev/0.6.1-1+b1/arm64 uninstallable
    • migrating librust-zerocopy-derive-dev/0.7.32-1/armel to testing makes librust-zerocopy-dev/0.6.1-1+b1/armel uninstallable
    • migrating librust-zerocopy-derive-dev/0.7.32-1/armhf to testing makes librust-zerocopy-dev/0.6.1-1+b1/armhf uninstallable
    • migrating librust-zerocopy-derive-dev/0.7.32-1/i386 to testing makes librust-zerocopy-dev/0.6.1-1+b1/i386 uninstallable
    • migrating librust-zerocopy-derive-dev/0.7.32-1/mips64el to testing makes librust-zerocopy-dev/0.6.1-1+b1/mips64el uninstallable
    • migrating librust-zerocopy-derive-dev/0.7.32-1/ppc64el to testing makes librust-zerocopy-dev/0.6.1-1+b1/ppc64el uninstallable
    • migrating librust-zerocopy-derive-dev/0.7.32-1/s390x to testing makes librust-zerocopy-dev/0.6.1-1+b1/s390x uninstallable
    • autopkgtest for rust-zerocopy-derive/0.7.32-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Test in progress, armhf: Regression or new test ♻ (reference ♻), i386: Reference test in progress, but real test failed already, ppc64el: Reference test in progress, but real test failed already, s390x: Reference test in progress, but real test failed already
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-zerocopy-derive.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• scipy (1.10.1-10 to 1.11.4-5)
  • Migration status for scipy (1.10.1-10 to 1.11.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for astropy/6.0.0-1: amd64: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for dipy/1.8.0-2: amd64: Pass, i386: Test in progress (will not be considered a regression), ppc64el: Test in progress, s390x: Pass
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for einsteinpy/0.4.0-3: amd64: 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 fenics-dolfinx/1:0.7.3-3: amd64: Pass, i386: Test in progress, ppc64el: Pass, s390x: Pass
    • autopkgtest for mdanalysis/2.5.0+dfsg1-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress
    • autopkgtest for pandas/1.5.3+dfsg-12: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pybind11/2.11.1-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pycorrfit/1.1.7+dfsg-2: amd64: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pygac/1.7.2-2: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pymatgen/2024.1.27+dfsg1-5: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pyorbital/1.8.2-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pysatellites/2.7-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pyscanfcs/0.3.6+ds-4: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pysolid/0.3.2-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pyspectral/0.13.0+ds-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pysurfer/0.11.2-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pyswarms/1.3.0-6: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-ase/3.22.1-4: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-bayespy/0.5.26-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-biom-format/2.1.15.2-3: amd64: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-bumps/0.9.1-2: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-cai/1.0.2-4: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-cmaes/0.10.0-2: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-cobra/0.29.0-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for python-csb/1.2.5+dfsg-10: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-czt/0.0.7-2: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-deeptools/3.5.4+dfsg-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for python-dmsh/0.2.19-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-dtcwt/0.12.0-5: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for python-fluids/1.0.22-2: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-geotiepoints/1.7.2-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-griddataformats/1.0.2-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-hdf5storage/0.1.19-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-hmmlearn/0.3.0-4: amd64: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-igraph/0.11.4+ds-1: amd64: Pass, i386: Pass, ppc64el: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for python-ltfatpy/1.0.16-10: amd64: Pass, i386: Test in progress, ppc64el: Test in progress
    • autopkgtest for python-matplotlib-venn/0.11.6-3: amd64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test in progress, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-meshplex/0.17.1-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-mne/1.3.0+dfsg-1: amd64: No tests, superficial or marked flaky ♻, i386: Test in progress, ppc64el: Test in progress, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-pauvre/0.2.3-3: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-peakutils/1.3.4+ds-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-pomegranate/0.14.8-4: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-pot/0.9.3+dfsg-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-pweave/0.30.3-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-pyani/0.2.12-3: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-pymbar/3.1.0-4: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-pyrgg/1.4-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-pyspike/0.8.0+dfsg-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-qmix/1.0.6-7: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-questplus/2019.4-6: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-rioxarray/0.15.1-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-skbio/0.5.9-4: amd64: Pass, ppc64el: Test in progress
    • autopkgtest for python-svgelements/1.7.2-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-threadpoolctl/3.1.0-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-treetime/0.11.1-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-weblogo/3.7.12-5: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for python-xarray/2023.12.0-3: amd64: Test in progress, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for pythran: amd64: Test in progress, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for q2-metadata/2023.9.0+dfsg-1: amd64: Pass, ppc64el: Test in progress
    • autopkgtest for q2-quality-control/2022.11.1-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for qutip/4.7.3-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for r-bioc-mofa/1.6.1+dfsg-12: amd64: No tests, superficial or marked flaky ♻, i386: Test in progress, ppc64el: Test in progress, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for radio-beam/0.3.7-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for reproject/0.13.0-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for sasmodels/1.0.7-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for sasview/5.0.6-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for satpy/0.46.0-3: amd64: Pass, i386: Test in progress (will not be considered a regression), ppc64el: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for scikit-learn/1.2.1+dfsg-1: amd64: Regression or new test ♻ (reference ♻), i386: Test in progress, ppc64el: Test in progress, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for scikit-rf/0.30.0-1.1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for scipy/1.11.4-5: amd64: Regression or new test ♻ (reference ♻), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression), s390x: Failed (not a regression)
    • autopkgtest for scoary/1.6.16-6: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for seaborn/0.13.2-2: amd64: Pass, i386: Test in progress (will not be considered a regression), ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for seirsplus/1.0.9-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for siconos/4.4.0+dfsg-3: amd64: Pass, i386: Test in progress (will not be considered a regression), ppc64el: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for skimage/0.22.0-3: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for sncosmo/2.10.3-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for specutils/1.13.0-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for speechpy-fast/2.4-4: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for spyder/5.5.0+ds-3: amd64: Pass, i386: Test in progress, ppc64el: Test in progress (will not be considered a regression), s390x: Failed (not a regression)
    • autopkgtest for spyder-kernels/2.5.0-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for srst2/0.2.0-11: amd64: Pass, ppc64el: Test in progress
    • autopkgtest for statsmodels/0.14.1+dfsg-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for svim/2.0.0-3: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for symfit/0.5.6-2: amd64: Pass, i386: Test in progress (will not be considered a regression), ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for synphot/1.3.0-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for tnseq-transit/3.3.4-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for tombo/1.5.1-6: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for uc-echo/1.12-18: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for umis/1.0.9-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress
    • autopkgtest for uranium/5.0.0-3: amd64: No tests, superficial or marked flaky ♻, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for vedo/2023.4.6-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for xgboost/2.0.3-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for xpore/2.1-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for xraydb/4.5.3-2: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for xrayutilities/1.7.4-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for xsar/2024.02.1-1: amd64: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for yanosim/0.1-5: amd64: No tests, superficial or marked flaky ♻, i386: Test in progress, ppc64el: Test in progress
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/s/scipy.html
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating scipy will fix bugs in testing: #1061605
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• snakeyaml-engine (- to 2.7+ds-3)
  • Migration status for snakeyaml-engine (- to 2.7+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/s/snakeyaml-engine.html
    • autopkgtest for snakeyaml-engine/2.7+ds-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• stayrtr (0.5.1+20231221-1 to 0.5.1+20240209-1)
  • Migration status for stayrtr (0.5.1+20231221-1 to 0.5.1+20240209-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/s/stayrtr.html
    • autopkgtest for stayrtr/0.5.1+20240209-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • Too young, only 0 of 5 days old
    • Built-Using: stayrtr golang-1.21
    • Built-Using: stayrtr golang-github-prometheus-client-model
    • Built-Using: stayrtr golang-github-prometheus-common
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tractor (4.5.0-1 to 4.5.1-1)
  • Migration status for tractor (4.5.0-1 to 4.5.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/t/tractor.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ukui-control-center (3.0.5.1-2 to 3.22.1.25-1)
  • Migration status for ukui-control-center (3.0.5.1-2 to 3.22.1.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armel: libkysdk-applications-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armhf: libkysdk-applications-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on i386: libkysdk-applications-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on mips64el: libkysdk-applications-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on ppc64el: libkysdk-applications-dev
    • Not built on buildd: arch amd64 binaries uploaded by happyaron.xu@gmail.com
    • 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
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/u/ukui-control-center.html
    • 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
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): ukui-control-center libkysdk-base
    • Depends: ukui-control-center libkysdk-base
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• utidylib (0.8-1 to 0.9-1)
  • Migration status for utidylib (0.8-1 to 0.9-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utidylib.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• vulkan-tools (1.3.268.0+dfsg1-1 to 1.3.275.0+dfsg1-1)
  • Migration status for vulkan-tools (1.3.268.0+dfsg1-1 to 1.3.275.0+dfsg1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on 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:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): vulkan-tools vulkan-volk
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vulkan-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 ♻
• weston (13.0.0-1 to 13.0.0-2)
  • Migration status for weston (13.0.0-1 to 13.0.0-2): 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 s390x
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/w/weston.html
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for gtk4/4.12.5+ds-2: amd64: Pass, armel: Test in progress, i386: Test in progress, ppc64el: Test in progress
    • autopkgtest for libdecor-0/0.2.2-1: amd64: No tests, superficial or marked flaky ♻, armel: Test in progress, i386: Test in progress, ppc64el: Test in progress
    • autopkgtest for weston/13.0.0-2: amd64: Pass, armel: Test in progress, i386: Test in progress, ppc64el: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• adios4dolfinx (- to 0.7.3-2)
  • Migration status for adios4dolfinx (- to 0.7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adios4dolfinx/0.7.3-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adios4dolfinx.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • 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 ♻
• archlinux-keyring (0~20231222-1 to 0~20240208-1)
  • Migration status for archlinux-keyring (0~20231222-1 to 0~20240208-1): 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/archlinux-keyring.html
    • autopkgtest for archlinux-keyring/0~20240208-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• authprogs (0.7.5-1 to 0.7.5-2)
  • Migration status for authprogs (0.7.5-1 to 0.7.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/authprogs.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 ♻
• binutils (2.42-2 to 2.42-3)
  • Migration status for binutils (2.42-2 to 2.42-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/b/binutils.html
    • autopkgtest for binutils/2.42-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for llvm-toolchain-17/blocked-on-ci-infra: ppc64el: Ignored failure
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• chromium (121.0.6167.160-1 to 122.0.6261.57-1)
  • Migration status for chromium (121.0.6167.160-1 to 122.0.6261.57-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sabnzbdplus/4.2.2+dfsg-1: armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻)
    • 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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chromium.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dhcp-helper (1.2-3.1 to 1.2-3.2)
  • Migration status for dhcp-helper (1.2-3.1 to 1.2-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by srk
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dhcp-helper.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 ♻
• edk2 (2023.11-6 to 2023.11-8)
  • Migration status for edk2 (2023.11-6 to 2023.11-8): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/edk2.html
    • autopkgtest for edk2/2023.11-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ensmallen (2.21.0-1 to 2.21.1-1)
  • Migration status for ensmallen (2.21.0-1 to 2.21.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/e/ensmallen.html
    • Too young, only 1 of 2 days old
  • Additional info:
    • autopkgtest for ensmallen/2.21.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• fdb (5.11.99-1 to 5.11.101-1)
  • Migration status for fdb (5.11.99-1 to 5.11.101-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: fdb metkit
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fenics-dolfinx (1:0.7.3-3 to 1:0.7.3-4)
  • Migration status for fenics-dolfinx (1:0.7.3-3 to 1:0.7.3-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/f/fenics-dolfinx.html
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for fenics-dolfinx/1:0.7.3-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gcl27 (- to 2.7.0-14)
  • Migration status for gcl27 (- to 2.7.0-14): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcl27.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• generate-ninja (0.0~git20240112.5fd939d-1 to 0.0~git20240221.03d10f1-1)
  • Migration status for generate-ninja (0.0~git20240112.5fd939d-1 to 0.0~git20240221.03d10f1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/generate-ninja.html
    • autopkgtest for generate-ninja/0.0~git20240221.03d10f1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• gitlab (- to 16.8.2-8)
  • Migration status for gitlab (- to 16.8.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gitlab/amd64 has unsatisfiable dependency
    • gitlab/arm64 has unsatisfiable dependency
    • Updating gitlab would introduce bugs in testing: #1009942, #983915
    • autopkgtest for gitlab/16.8.2-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 ♻, s390x: Regression or new test ♻
    • Too young, only 1 of 5 days old
    • Built-Using: gitlab gitaly
    • Built-Using: gitlab golang-1.21
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-builder (45.0-2 to 46~beta-1)
  • Migration status for gnome-builder (45.0-2 to 46~beta-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/g/gnome-builder.html
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): gnome-builder libpanel
    • Depends: gnome-builder libpanel
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-terminal (3.50.1-1 to 3.51.90-1)
  • Migration status for gnome-terminal (3.50.1-1 to 3.51.90-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-terminal.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-github-cilium-ebpf (0.9.1-1 to 0.11.0-2)
  • Migration status for golang-github-cilium-ebpf (0.9.1-1 to 0.11.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-cilium-ebpf.html
    • autopkgtest for golang-github-cilium-ebpf/0.11.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-evanw-esbuild (0.19.12-2 to 0.20.1-1)
  • Migration status for golang-github-evanw-esbuild (0.19.12-2 to 0.20.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Built-Using: golang-github-evanw-esbuild golang-1.21
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-evanw-esbuild.html
    • autopkgtest for golang-github-evanw-esbuild/0.20.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• golang-github-getkin-kin-openapi (0.122.0-3 to 0.123.0-1)
  • Migration status for golang-github-getkin-kin-openapi (0.122.0-3 to 0.123.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): golang-github-getkin-kin-openapi golang-github-go-openapi-jsonpointer
    • Depends: golang-github-getkin-kin-openapi golang-github-go-openapi-jsonpointer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getkin-kin-openapi.html
    • autopkgtest for golang-github-getkin-kin-openapi/0.123.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• golang-github-go-openapi-jsonpointer (1:0.19.6-1 to 1:0.20.2-1)
  • Migration status for golang-github-go-openapi-jsonpointer (1:0.19.6-1 to 1:0.20.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): golang-github-go-openapi-jsonpointer golang-github-go-openapi-swag
    • Depends: golang-github-go-openapi-jsonpointer golang-github-go-openapi-swag
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-openapi-jsonpointer.html
    • autopkgtest for golang-github-go-openapi-jsonpointer/1:0.20.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• golang-github-go-openapi-swag (1:0.22.4-1 to 1:0.22.8-1)
  • Migration status for golang-github-go-openapi-swag (1:0.22.4-1 to 1:0.22.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-openapi-swag.html
    • autopkgtest for golang-github-go-openapi-swag/1:0.22.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• golang-github-go-sql-driver-mysql (1.5.0-2 to 1.7.1-2)
  • Migration status for golang-github-go-sql-driver-mysql (1.5.0-2 to 1.7.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-sql-driver-mysql.html
    • autopkgtest for golang-github-go-sql-driver-mysql/1.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-prometheus-client-model (0.5.0-1 to 0.6.0-1)
  • Migration status for golang-github-prometheus-client-model (0.5.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-prometheus-client-model/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for golang-github-prometheus-common/0.47.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: Failed (not a regression), ppc64el: 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/g/golang-github-prometheus-client-model.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-prometheus-common (0.47.0-1 to 0.47.0-2)
  • Migration status for golang-github-prometheus-common (0.47.0-1 to 0.47.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/g/golang-github-prometheus-common.html
    • Too young, only 1 of 2 days old
  • Additional info:
    • autopkgtest for golang-github-prometheus-common/0.47.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• gst-omx (1.22.9-1 to 1.22.10-1)
  • Migration status for gst-omx (1.22.9-1 to 1.22.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 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gst-omx.html
    • autopkgtest for gst-omx/1.22.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• iceoryx (2.0.5+dfsg-1 to 2.0.5+dfsg-2)
  • Migration status for iceoryx (2.0.5+dfsg-1 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/i/iceoryx.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• intel-cmt-cat (23.11-1.1 to 23.11-2)
  • Migration status for intel-cmt-cat (23.11-1.1 to 23.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/i/intel-cmt-cat.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 ♻
• ipywidgets (8.1.1-2 to 8.1.1-4)
  • Migration status for ipywidgets (8.1.1-2 to 8.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/i/ipywidgets.html
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating ipywidgets will fix bugs in testing: #1063908
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• iraf-st4gem (- to 1.0+ds-2)
  • Migration status for iraf-st4gem (- to 1.0+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iraf-st4gem.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• iraf-xdimsum (- to 2003.01.24-2)
  • Migration status for iraf-xdimsum (- to 2003.01.24-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iraf-xdimsum.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jruby (- to 9.4.5.0+ds-1)
  • Migration status for jruby (- to 9.4.5.0+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): jruby jruby-maven-plugins
    • Build-Depends(-Arch): jruby jruby-mavengem
    • Build-Depends(-Arch): jruby takari-polyglot-maven
    • Depends: jruby snakeyaml-engine
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby.html
    • autopkgtest for jruby/9.4.5.0+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: 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 armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jruby-utils-clojure (- to 5.1.0-1)
  • Migration status for jruby-utils-clojure (- to 5.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jruby-utils-clojure would introduce bugs in testing: #1042031
    • autopkgtest for jruby-utils-clojure/5.1.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): jruby-utils-clojure jruby
    • Depends: jruby-utils-clojure jruby
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby-utils-clojure.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• klibc (2.0.13-2 to 2.0.13-4)
  • Migration status for klibc (2.0.13-2 to 2.0.13-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/klibc.html
    • autopkgtest for klibc/2.0.13-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• libcompress-raw-lzma-perl (2.206-2 to 2.209-1)
  • Migration status for libcompress-raw-lzma-perl (2.206-2 to 2.209-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcompress-raw-lzma-perl.html
    • autopkgtest for libcompress-raw-lzma-perl/2.209-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• libdbix-class-inflatecolumn-ip-perl (0.02003-2 to 0.02003-3)
  • Migration status for libdbix-class-inflatecolumn-ip-perl (0.02003-2 to 0.02003-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/libd/libdbix-class-inflatecolumn-ip-perl.html
    • autopkgtest for libdbix-class-inflatecolumn-ip-perl/0.02003-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• libdemeter-perl (- to 0.9.27+ds6-3)
  • Migration status for libdemeter-perl (- to 0.9.27+ds6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdemeter-perl would introduce bugs in testing: #1064482
    • autopkgtest for libdemeter-perl/0.9.27+ds6-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libffi (3.4.4-2 to 3.4.6-1)
  • Migration status for libffi (3.4.4-2 to 3.4.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for llvm-toolchain-17/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for thunderbird/1:115.7.0-1: amd64: Pass, arm64: Pass, i386: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for thunderbird/blocked-on-ci-infra: ppc64el: Ignored failure
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libffi.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 ♻
• libjloda-java (2.1-2 to 2.1+ds-3)
  • Migration status for libjloda-java (2.1-2 to 2.1+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/libj/libjloda-java.html
    • Too young, only 1 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libpanel (1.4.1-1 to 1.5.0-1)
  • Migration status for libpanel (1.4.1-1 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpanel.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 ♻
• libpfm4 (4.13.0+git16-g535c204-1 to 4.13.0+git32-g0d4ed0e-1)
  • Migration status for libpfm4 (4.13.0+git16-g535c204-1 to 4.13.0+git32-g0d4ed0e-1): Waiting for test 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/libp/libpfm4.html
    • autopkgtest for llvm-toolchain-17/blocked-on-ci-infra: ppc64el: Ignored failure
    • 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 ♻
• libpgjava (42.7.1-1 to 42.7.2-1)
  • Migration status for libpgjava (42.7.1-1 to 42.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/libp/libpgjava.html
    • autopkgtest for libpgjava/42.7.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libpod-tests-perl (1.20-3 to 1.20-4)
  • Migration status for libpod-tests-perl (1.20-3 to 1.20-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpod-tests-perl.html
    • autopkgtest for libpod-tests-perl/1.20-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• libshumate (1.2~alpha-1 to 1.2~beta-3)
  • Migration status for libshumate (1.2~alpha-1 to 1.2~beta-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libshumate.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 ♻
• libtest-checkmanifest-perl (1.43-1 to 1.43-2)
  • Migration status for libtest-checkmanifest-perl (1.43-1 to 1.43-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/libt/libtest-checkmanifest-perl.html
    • autopkgtest for libtest-checkmanifest-perl/1.43-2: 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• matomo-referrer-spam-list (- to 4.0.0-2)
  • Migration status for matomo-referrer-spam-list (- to 4.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-referrer-spam-list.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 ♻
• matomo-searchengine-and-social-list (- to 3.14.0-1)
  • Migration status for matomo-searchengine-and-social-list (- to 3.14.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-searchengine-and-social-list.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 ♻
• mdadm (4.2+20240118-1 to 4.3-1)
  • Migration status for mdadm (4.2+20240118-1 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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdadm.html
    • autopkgtest for mdadm/4.3-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• metkit (1.11.5-1 to 1.11.6-1)
  • Migration status for metkit (1.11.5-1 to 1.11.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/m/metkit.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• minisat2 (1:2.2.1-5 to 1:2.2.1-7)
  • Migration status for minisat2 (1:2.2.1-5 to 1:2.2.1-7): 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 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minisat2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mkdocs-material (9.4.0-1 to 9.4.0-1.1)
  • Migration status for mkdocs-material (9.4.0-1 to 9.4.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 mkdocs-material will fix bugs in testing: #1062582
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkdocs-material.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 ♻
• node-ipydatagrid (- to 1.2.1+~cs13.21.94-1)
  • Migration status for node-ipydatagrid (- to 1.2.1+~cs13.21.94-1): 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-ipydatagrid.html
    • autopkgtest for node-ipydatagrid/1.2.1+~cs13.21.94-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• node-neo-async (2.6.2+~cs3.0.0-2 to 2.6.2+~cs3.0.0-3)
  • Migration status for node-neo-async (2.6.2+~cs3.0.0-2 to 2.6.2+~cs3.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/n/node-neo-async.html
    • autopkgtest for node-neo-async/2.6.2+~cs3.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• nodejs (18.19.0+dfsg-6 to 18.19.1+dfsg-3)
  • Migration status for nodejs (18.19.0+dfsg-6 to 18.19.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-openpgp-seek-bzip/1.0.5-3: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for node-reinterval/1.1.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for nodejs/18.19.1+dfsg-3: amd64: Pass, arm64: Pass, armel: Test in progress (will not be considered a regression), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating nodejs will fix bugs in testing: #1059168, #1064055
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nodejs.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• puppet-lint (3.0.1-1 to 4.2.4-2)
  • Migration status for puppet-lint (3.0.1-1 to 4.2.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-lint.html
    • autopkgtest for puppet-lint/4.2.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pydevd (2.10.0+ds-8 to 2.10.0+ds-10)
  • Migration status for pydevd (2.10.0+ds-8 to 2.10.0+ds-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 pydevd will fix bugs in testing: #1063274
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydevd.html
    • autopkgtest for pydevd/2.10.0+ds-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-apt (2.7.5 to 2.7.6)
  • Migration status for python-apt (2.7.5 to 2.7.6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-apt.html
    • autopkgtest for python-apt/2.7.6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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-boto3 (1.34.18+dfsg-1 to 1.34.46+dfsg-1)
  • Migration status for python-boto3 (1.34.18+dfsg-1 to 1.34.46+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-boto3.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-botocore (1.34.18+repack-1 to 1.34.46+repack-1)
  • Migration status for python-botocore (1.34.18+repack-1 to 1.34.46+repack-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-botocore.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-certbot-dns-standalone (1.1-1 to 1.1-2)
  • Migration status for python-certbot-dns-standalone (1.1-1 to 1.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-standalone.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-drf-spectacular-sidecar-nonfree (2023.6.1-1 to 2024.2.1-1)
  • Migration status for python-drf-spectacular-sidecar-nonfree (2023.6.1-1 to 2024.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating python-drf-spectacular-sidecar-nonfree will fix bugs in testing: #1062008
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-hsluv (- to 5.0.4-1)
  • Migration status for python-hsluv (- to 5.0.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hsluv.html
    • autopkgtest for python-hsluv/5.0.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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-redmine (- to 2.4.0-1)
  • Migration status for python-redmine (- 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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-redmine.html
    • autopkgtest for python-redmine/2.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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-selenium (4.17.2+dfsg-1 to 4.18.1+dfsg-1)
  • Migration status for python-selenium (4.17.2+dfsg-1 to 4.18.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-selenium.html
    • autopkgtest for python-selenium/4.18.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• qutip (4.7.3-1 to 4.7.5-2)
  • Migration status for qutip (4.7.3-1 to 4.7.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qutip.html
    • autopkgtest for qutip/4.7.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rocm-device-libs (5.2.3-3 to 6.0+git20231212.5a852ed-1)
  • Migration status for rocm-device-libs (5.2.3-3 to 6.0+git20231212.5a852ed-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: clangd-17
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: clang-17
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: clang-format-17
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: clang-tidy-17
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: clang-tools-17
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: libclang-17-dev
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: libmlir-17-dev
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: llvm-17-dev
    • rocm-device-libs unsatisfiable Build-Depends(-Arch) on mips64el: mlir-17-tools
    • missing build on mips64el
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocm-device-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 ♻
• ros2-ament-cmake (2.3.2-1 to 2.3.2-2)
  • Migration status for ros2-ament-cmake (2.3.2-1 to 2.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-ament-cmake.html
    • autopkgtest for ros2-ament-cmake/2.3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• ruby-grape (1.7.1-1 to 2.0.0-3)
  • Migration status for ruby-grape (1.7.1-1 to 2.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Implicit dependency: ruby-grape ruby-grape-path-helpers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-grape.html
    • autopkgtest for ruby-grape/2.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
• ruby-puppetlabs-spec-helper (4.0.1-2 to 7.0.5-1)
  • Migration status for ruby-puppetlabs-spec-helper (4.0.1-2 to 7.0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): ruby-puppetlabs-spec-helper puppet-lint
    • Build-Depends(-Arch): ruby-puppetlabs-spec-helper ruby-puppet-syntax
    • Build-Depends(-Arch): ruby-puppetlabs-spec-helper ruby-rspec-puppet
    • Depends: ruby-puppetlabs-spec-helper puppet-lint
    • Depends: ruby-puppetlabs-spec-helper ruby-puppet-syntax
    • Depends: ruby-puppetlabs-spec-helper ruby-rspec-puppet
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-puppetlabs-spec-helper.html
    • autopkgtest for ruby-puppetlabs-spec-helper/7.0.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ruby-rspec-puppet (2.9.0+ds-1 to 4.0.2+ds-1)
  • Migration status for ruby-rspec-puppet (2.9.0+ds-1 to 4.0.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 2 days old
    • Build-Depends(-Arch): ruby-rspec-puppet puppet-agent
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-puppet.html
    • autopkgtest for ruby-rspec-puppet/4.0.2+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• ruby-shindo (0.3.10-1 to 0.3.10-2)
  • Migration status for ruby-shindo (0.3.10-1 to 0.3.10-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-shindo.html
    • autopkgtest for ruby-shindo/0.3.10-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ruby-spider (0.5.0-4 to 0.5.0-5)
  • Migration status for ruby-spider (0.5.0-4 to 0.5.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-spider/0.5.0-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-spider.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-wavefile (0.6.0-2.1 to 1.1.2-1)
  • Migration status for ruby-wavefile (0.6.0-2.1 to 1.1.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-wavefile.html
    • autopkgtest for ruby-wavefile/1.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-fmt2io (- to 0.2.0-1)
  • Migration status for rust-fmt2io (- to 0.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/r/rust-fmt2io.html
    • autopkgtest for rust-fmt2io/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-rfc822-like (- to 0.2.1-1)
  • Migration status for rust-rfc822-like (- 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 1 of 2 days old
    • Build-Depends(-Arch): rust-rfc822-like rust-fmt2io
    • Depends: rust-rfc822-like rust-fmt2io
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rfc822-like.html
    • autopkgtest for rust-rfc822-like/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-sequoia-chameleon-gnupg (0.4.0-1 to 0.5.1-1)
  • Migration status for rust-sequoia-chameleon-gnupg (0.4.0-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:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-sequoia-chameleon-gnupg.html
    • Too young, only 1 of 5 days old
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• smplayer (23.6.0+ds0-1 to 23.12.0+ds0-1)
  • Migration status for smplayer (23.6.0+ds0-1 to 23.12.0+ds0-1): Waiting for test 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/smplayer.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 ♻
• snappy-tools (0-1 to 1-1)
  • Migration status for snappy-tools (0-1 to 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/s/snappy-tools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• splitpatch (1.0+20190128+git3b2edf2-4 to 1.0+20190128+git3b2edf2-5)
  • Migration status for splitpatch (1.0+20190128+git3b2edf2-4 to 1.0+20190128+git3b2edf2-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/s/splitpatch.html
    • autopkgtest for splitpatch/1.0+20190128+git3b2edf2-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• spyder (5.5.0+ds-3 to 5.5.1+ds-1)
  • Migration status for spyder (5.5.0+ds-3 to 5.5.1+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/s/spyder.html
    • autopkgtest for guidata/3.0.4+dfsg1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test in progress
    • autopkgtest for spyder/5.5.1+ds-1: amd64: Pass, arm64: Pass, armhf: Test in progress, i386: Test in progress
    • autopkgtest for spyder-line-profiler/0.3.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test in progress
    • autopkgtest for spyder-unittest/0.6.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test in progress
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): spyder python-lsp-server
    • Depends: spyder python-lsp-server
  • Additional info:
    • 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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sqlfluff (- to 2.3.5-1)
  • Migration status for sqlfluff (- to 2.3.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/s/sqlfluff.html
    • autopkgtest for sqlfluff/2.3.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• stompserver (0.9.9gem-4.1 to 0.9.9gem-5)
  • Migration status for stompserver (0.9.9gem-4.1 to 0.9.9gem-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/s/stompserver.html
    • autopkgtest for stompserver/0.9.9gem-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• streamlink (6.6.1-1 to 6.6.2-1)
  • Migration status for streamlink (6.6.1-1 to 6.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/streamlink.html
    • autopkgtest for streamlink/6.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• teckit (2.5.11+ds1-1 to 2.5.12+ds1-1)
  • Migration status for teckit (2.5.11+ds1-1 to 2.5.12+ds1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/teckit.html
    • autopkgtest for teckit/2.5.12+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
• thunderbird (1:115.7.0-1 to 1:115.8.0-1)
  • Migration status for thunderbird (1:115.7.0-1 to 1:115.8.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • autopkgtest for thunderbird/1:115.8.0-1: arm64: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thunderbird.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• vulkan-volk (1.3.268.0-1 to 1.3.275.0-1)
  • Migration status for vulkan-volk (1.3.268.0-1 to 1.3.275.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/v/vulkan-volk.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 ♻
• xdaliclock (2.46-1 to 2.48-1)
  • Migration status for xdaliclock (2.46-1 to 2.48-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdaliclock.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xterm (389-1 to 390-1)
  • Migration status for xterm (389-1 to 390-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xterm.html
    • autopkgtest for awesome/4.3-7: amd64: Ignored failure, arm64: Ignored failure, armel: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for xterm/390-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• adios2 (2.9.2+dfsg1-9 to 2.9.2+dfsg1-11)
  • Migration status for adios2 (2.9.2+dfsg1-9 to 2.9.2+dfsg1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adios2/2.9.2+dfsg1-11: arm64: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for adios2/blocked-on-ci-infra: amd64: Failed (not a regression)
    • autopkgtest for fenics-dolfinx/1:0.7.3-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
    • Depends: adios2 ucx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adios2.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 ♻
• altdns (- to 1.0.2+git20210909.8c1de0f-2)
  • Migration status for altdns (- to 1.0.2+git20210909.8c1de0f-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/altdns.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• apt (2.7.11 to 2.7.12)
  • Migration status for apt (2.7.11 to 2.7.12): Waiting for test results or 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/apt.html
    • autopkgtest for apt/2.7.12: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• arctica-greeter (0.99.3.0-4 to 0.99.5.0-2)
  • Migration status for arctica-greeter (0.99.3.0-4 to 0.99.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arctica-greeter.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• asdf-standard (1.0.3-3 to 1.0.3-4)
  • Migration status for asdf-standard (1.0.3-3 to 1.0.3-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating asdf-standard will fix bugs in testing: #1064275
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asdf-standard.html
    • autopkgtest for asdf-standard/1.0.3-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• asn (- to 0.75.3-1.1)
  • Migration status for asn (- to 0.75.3-1.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asn.html
    • autopkgtest for asn/0.75.3-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ayatana-indicator-power (24.1.0-1 to 24.1.0-2)
  • Migration status for ayatana-indicator-power (24.1.0-1 to 24.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/a/ayatana-indicator-power.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• b4 (0.12.4-1 to 0.13.0-1)
  • Migration status for b4 (0.12.4-1 to 0.13.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/b4.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• betamax (0.8.1-3 to 0.9.0-1)
  • Migration status for betamax (0.8.1-3 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/betamax.html
    • autopkgtest for betamax/0.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• capstone (4.0.2-5 to 4.0.2-5.1)
  • Migration status for capstone (4.0.2-5 to 4.0.2-5.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating capstone will fix bugs in testing: #1059671
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/capstone.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cmlxom (4.7-1 to 4.8-1)
  • Migration status for cmlxom (4.7-1 to 4.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: cmlxom libeuclid-java
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmlxom.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dav1d (1.3.0-2 to 1.4.0-1)
  • Migration status for dav1d (1.3.0-2 to 1.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating dav1d will fix bugs in testing: #1064310
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dav1d.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• debspawn (0.6.3-1 to 0.6.4-1)
  • Migration status for debspawn (0.6.3-1 to 0.6.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debspawn.html
    • autopkgtest for debspawn/0.6.4-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 ♻, 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 ♻
• dnspython (2.6.0-1 to 2.6.1-1)
  • Migration status for dnspython (2.6.0-1 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/d/dnspython.html
    • autopkgtest for dnspython/2.6.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 2 days old (needed 2 days)
• elan (3.0.0-3 to 3.1.0-1)
  • Migration status for elan (3.0.0-3 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/e/elan.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 ♻
• expeyes (5.3.1+repack-1 to 5.3.1+repack-5)
  • Migration status for expeyes (5.3.1+repack-1 to 5.3.1+repack-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 expeyes will fix bugs in testing: #1064212
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/expeyes.html
    • autopkgtest for expeyes/5.3.1+repack-5: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: Pass, i386: Pass, ppc64el: 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 ♻
• far2l (2.5.3~beta+ds-1 to 2.6.0~beta+ds-1)
  • Migration status for far2l (2.5.3~beta+ds-1 to 2.6.0~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 2 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 ♻
• firefox (- to 123.0-1)
  • Migration status for firefox (- to 123.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 mips64el
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): firefox nss
    • Depends: firefox nss
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox.html
    • 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 armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• firefox-esr (115.7.0esr-1 to 115.8.0esr-1)
  • Migration status for firefox-esr (115.7.0esr-1 to 115.8.0esr-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:
    • Updating firefox-esr will fix bugs in testing: #1061437
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox-esr.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 armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• flask-limiter (3.5.0-1 to 3.5.1-1)
  • Migration status for flask-limiter (3.5.0-1 to 3.5.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-limiter.html
    • autopkgtest for flask-limiter/3.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility reference results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• fortunes-it (2.2-3 to 2.3-1)
  • Migration status for fortunes-it (2.2-3 to 2.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 10 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 ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-1.20 (1.20.13-1 to 1.20.14-1)
  • Migration status for golang-1.20 (1.20.13-1 to 1.20.14-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/g/golang-1.20.html
    • autopkgtest for golang-1.20/1.20.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-1.21 (1.21.6-1 to 1.21.7-1)
  • Migration status for golang-1.21 (1.21.6-1 to 1.21.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.21.html
    • autopkgtest for golang-1.21/1.21.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-1.22 (1.22~rc2-1 to 1.22.0-1)
  • Migration status for golang-1.22 (1.22~rc2-1 to 1.22.0-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/g/golang-1.22.html
    • autopkgtest for golang-1.22/1.22.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-defaults (2:1.21~2 to 2:1.21~3)
  • Migration status for golang-defaults (2:1.21~2 to 2:1.21~3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-defaults.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• halide (16.0.0-3 to 17.0.0-2)
  • Migration status for halide (16.0.0-3 to 17.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/h/halide.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-crypton-x509-store (- to 1.6.9-2)
  • Migration status for haskell-crypton-x509-store (- to 1.6.9-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/h/haskell-crypton-x509-store.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• homebank (5.7.3-1 to 5.7.4-1)
  • Migration status for homebank (5.7.3-1 to 5.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by franam
    • Not built on buildd: arch all binaries uploaded by franam, 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/h/homebank.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ikos (- to 3.2-3)
  • Migration status for ikos (- to 3.2-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• kdump-tools (1:1.10 to 1:1.10.1)
  • Migration status for kdump-tools (1:1.10 to 1:1.10.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdump-tools.html
    • autopkgtest for kdump-tools/1:1.10.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• keystone (2:24.0.0-2 to 2:24.0.0-3)
  • Migration status for keystone (2:24.0.0-2 to 2:24.0.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keystone.html
    • autopkgtest for keystone/2:24.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• laniakea-spark (- to 0.1.1-1)
  • Migration status for laniakea-spark (- 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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/laniakea-spark.html
    • autopkgtest for laniakea-spark/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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• last-align (1540-1 to 1542-1)
  • Migration status for last-align (1540-1 to 1542-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/last-align.html
    • autopkgtest for last-align/1542-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• lf (30-1 to 31+ds-1)
  • Migration status for lf (30-1 to 31+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lf.html
    • autopkgtest for lf/31+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libgzstream (1.5+git20171107.9a20658-1 to 1.5+git20171107.9a20658-2)
  • Migration status for libgzstream (1.5+git20171107.9a20658-1 to 1.5+git20171107.9a20658-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/libg/libgzstream.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libjwt (1.10.2-1 to 1.17.0-2)
  • Migration status for libjwt (1.10.2-1 to 1.17.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
    • Implicit dependency: libjwt slurm-wlm/amd64
    • Implicit dependency: libjwt slurm-wlm/arm64
    • Implicit dependency: libjwt slurm-wlm/armel
    • Implicit dependency: libjwt slurm-wlm/armhf
    • Implicit dependency: libjwt slurm-wlm/i386
    • Implicit dependency: libjwt slurm-wlm/mips64el
    • Implicit dependency: libjwt slurm-wlm/ppc64el
    • Implicit dependency: libjwt slurm-wlm/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjwt.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libpdl-linearalgebra-perl (0.37-1 to 0.38-1)
  • Migration status for libpdl-linearalgebra-perl (0.37-1 to 0.38-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpdl-linearalgebra-perl.html
    • autopkgtest for libpdl-linearalgebra-perl/0.38-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libstdc++-arm-none-eabi (25 to 26)
  • Migration status for libstdc++-arm-none-eabi (25 to 26): Will attempt migration (Any information below is purely informational)
    • Depends: libstdc++-arm-none-eabi gcc-arm-none-eabi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libstdc++-arm-none-eabi.html
    • autopkgtest for libstdc++-arm-none-eabi/26: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• linux-apfs-rw (0.3.5-1 to 0.3.7-2)
  • Migration status for linux-apfs-rw (0.3.5-1 to 0.3.7-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 linux-apfs-rw will fix bugs in testing: #1063432
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-apfs-rw.html
    • autopkgtest for linux-apfs-rw/0.3.7-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lomiri (- to 0.2.1-4)
  • Migration status for lomiri (- to 0.2.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: lomiri ayatana-indicator-display
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lomiri-session (- to 0.2-7)
  • Migration status for lomiri-session (- to 0.2-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
    • Depends: lomiri-session lomiri
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-session.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• luametatex (2.10.08+ds-1 to 2.11.01+ds-2)
  • Migration status for luametatex (2.10.08+ds-1 to 2.11.01+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating luametatex would introduce bugs in testing: #1064402
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/luametatex.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mir-core (1.1.111-2 to 1.7.0-1)
  • Migration status for mir-core (1.1.111-2 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 2 of 5 days old
    • Depends: mir-core ldc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mir-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 ♻
• mmsd-tng (2.5.0-1 to 2.6.0-1)
  • Migration status for mmsd-tng (2.5.0-1 to 2.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mmsd-tng.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nanobind (1.8.0-4 to 1.9.0-1)
  • Migration status for nanobind (1.8.0-4 to 1.9.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanobind.html
    • autopkgtest for nanobind/1.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-html5-qrcode (2.3.8+repack-4 to 2.3.8+repack-5)
  • Migration status for node-html5-qrcode (2.3.8+repack-4 to 2.3.8+repack-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-html5-qrcode.html
    • autopkgtest for node-html5-qrcode/2.3.8+repack-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 2 days old (needed 2 days)
• nss (2:3.96.1-1 to 2:3.98-1)
  • Migration status for nss (2:3.96.1-1 to 2:3.98-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/nss.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for nut/2.8.1-3: amd64: Pass, arm64: Pass, armel: Ignored failure, armhf: Ignored failure, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for thunderbird/blocked-on-ci-infra: ppc64el: Ignored failure
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nsxiv (31-1 to 32-1)
  • Migration status for nsxiv (31-1 to 32-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/nsxiv.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• numix-icon-theme-circle (23.12.10-1 to 24.02.05-1)
  • Migration status for numix-icon-theme-circle (23.12.10-1 to 24.02.05-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/numix-icon-theme-circle.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 ♻
• packagekit (1.2.8-1 to 1.2.8-2)
  • Migration status for packagekit (1.2.8-1 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packagekit.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pdf2svg (0.2.3-4 to 0.2.3-5)
  • Migration status for pdf2svg (0.2.3-4 to 0.2.3-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdf2svg.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• phonopy (2.21.0-1 to 2.21.2-1)
  • Migration status for phonopy (2.21.0-1 to 2.21.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phonopy.html
    • autopkgtest for phonopy/2.21.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• picolibc (1.8.6-1 to 1.8.6-2)
  • Migration status for picolibc (1.8.6-1 to 1.8.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picolibc.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • autopkgtest for picolibc/1.8.6-2: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, i386: Pass, ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pooch (1.8.0-1 to 1.8.1-1)
  • Migration status for pooch (1.8.0-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pooch.html
    • autopkgtest for pooch/1.8.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pre-commit (3.6.1-1 to 3.6.2-1)
  • Migration status for pre-commit (3.6.1-1 to 3.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pre-commit.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 ♻
• puppet-agent (7.23.0-1 to 8.4.0-1)
  • Migration status for puppet-agent (7.23.0-1 to 8.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for puppet-agent/8.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for puppet-module-puppetlabs-apache/5.5.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for puppet-module-puppetlabs-apt/9.0.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for puppet-module-puppetlabs-firewall/3.4.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for puppet-module-puppetlabs-mysql/8.1.0-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for puppet-module-puppetlabs-postgresql/6.7.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for puppet-module-puppetlabs-stdlib/8.5.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for puppet-module-puppetlabs-xinetd/3.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 ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for puppet-module-saz-memcached/3.1.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating puppet-agent will fix bugs in testing: #1064295
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-agent.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• puppet-module-puppetlabs-apache (5.5.0-2 to 12.0.2-1)
  • Migration status for puppet-module-puppetlabs-apache (5.5.0-2 to 12.0.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-apache.html
    • autopkgtest for puppet-module-puppetlabs-apache/12.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• puppet-module-puppetlabs-rsync (1.1.0-3 to 1.2.0-1)
  • Migration status for puppet-module-puppetlabs-rsync (1.1.0-3 to 1.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-rsync.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pylabels (1.2.1+repack-2 to 1.2.1+repack-3)
  • Migration status for pylabels (1.2.1+repack-2 to 1.2.1+repack-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pylabels.html
    • autopkgtest for pylabels/1.2.1+repack-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pypdf (4.0.1-1 to 4.0.2-1)
  • Migration status for pypdf (4.0.1-1 to 4.0.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pypdf.html
    • autopkgtest for pypdf/4.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pyrsistent (0.18.1-1 to 0.20.0-1)
  • Migration status for pyrsistent (0.18.1-1 to 0.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by alexandre.detiste@gmail.com
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrsistent.html
    • autopkgtest for pyrsistent/0.20.0-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 ♻, 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 ♻
• python-argh (0.28.1-1 to 0.31.2-1)
  • Migration status for python-argh (0.28.1-1 to 0.31.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-argh.html
    • autopkgtest for python-argh/0.31.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 ♻, 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 ♻
• python-cassandra-driver (- to 3.29.0-2)
  • Migration status for python-cassandra-driver (- to 3.29.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-cassandra-driver would introduce bugs in testing: #1064403
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for python-cassandra-driver/3.29.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cassandra-driver.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 ♻
• python-django-debug-toolbar (1:4.2-1 to 1:4.3-2)
  • Migration status for python-django-debug-toolbar (1:4.2-1 to 1:4.3-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating python-django-debug-toolbar will fix bugs in testing: #1061751
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-debug-toolbar.html
    • autopkgtest for python-django-debug-toolbar/1:4.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-hypothesis (6.98.4-1 to 6.98.9-1)
  • Migration status for python-hypothesis (6.98.4-1 to 6.98.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for numpy/1:1.24.2-2: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for python-hypothesis/6.98.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hypothesis.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-ntlm-auth (1.4.0-2 to 1.5.0-1)
  • Migration status for python-ntlm-auth (1.4.0-2 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ntlm-auth.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-nudatus (- to 0.0.5-3)
  • Migration status for python-nudatus (- to 0.0.5-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nudatus.html
    • autopkgtest for python-nudatus/0.0.5-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-pbr (5.11.1-5 to 6.0.0-1)
  • Migration status for python-pbr (5.11.1-5 to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ceilometer/blocked-on-ci-infra: i386: Ignored failure
    • autopkgtest for mistral/17.0.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-pbr/6.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pbr.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-rebulk (3.1.0-1 to 3.3.0-1)
  • Migration status for python-rebulk (3.1.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rebulk.html
    • autopkgtest for python-rebulk/3.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-requests-oauthlib (1.3.0+ds-1 to 1.3.1-1)
  • Migration status for python-requests-oauthlib (1.3.0+ds-1 to 1.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-requests-oauthlib.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-scantree (0.0.1-2 to 0.0.2-1)
  • Migration status for python-scantree (0.0.1-2 to 0.0.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-scantree.html
    • autopkgtest for python-scantree/0.0.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 ♻, 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 ♻
• python-serializable (0.2.1+ds-2 to 0.4.0+ds-1)
  • Migration status for python-serializable (0.2.1+ds-2 to 0.4.0+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-serializable.html
    • autopkgtest for python-serializable/0.4.0+ds-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 ♻, 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 ♻
• python-traits (6.3.2-1 to 6.4.3-1)
  • Migration status for python-traits (6.3.2-1 to 6.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nipype/1.8.6-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-traits/6.4.3-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-traits.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-uvicorn (0.27.0-1 to 0.27.1-1)
  • Migration status for python-uvicorn (0.27.0-1 to 0.27.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 7 days old
    • Build-Depends(-Arch): python-uvicorn python-watchfiles
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-uvicorn.html
    • autopkgtest for python-uvicorn/0.27.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• qpid-proton-j-extensions (- to 1.2.4-2)
  • Migration status for qpid-proton-j-extensions (- to 1.2.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends-Indep: qpid-proton-j-extensions qpid-proton-j
    • Depends: qpid-proton-j-extensions qpid-proton-j
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-proton-j-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 ♻
• r-bioc-beachmat (2.18.0+ds-1 to 2.18.1+ds-1)
  • Migration status for r-bioc-beachmat (2.18.0+ds-1 to 2.18.1+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-beachmat.html
    • autopkgtest for r-bioc-beachmat/2.18.1+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 2 days old (needed 2 days)
• r-bioc-hdf5array (1.30.0-1 to 1.30.1-1)
  • Migration status for r-bioc-hdf5array (1.30.0-1 to 1.30.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-hdf5array.html
    • autopkgtest for r-bioc-hdf5array/1.30.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-collapse (2.0.9-1 to 2.0.10-1)
  • Migration status for r-cran-collapse (2.0.9-1 to 2.0.10-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-collapse.html
    • autopkgtest for r-cran-collapse/2.0.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rocalution (- to 5.7.1-2)
  • Migration status for rocalution (- to 5.7.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocalution.html
    • autopkgtest for rocalution/5.7.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rpki-client (8.9-1 to 8.9-2)
  • Migration status for rpki-client (8.9-1 to 8.9-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/r/rpki-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 ♻
• ruby-google-cloud-core (1.2.0-2 to 1.6.1-1.1)
  • Migration status for ruby-google-cloud-core (1.2.0-2 to 1.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 2 of 5 days old
  • Additional info:
    • Updating ruby-google-cloud-core will fix bugs in testing: #1063245
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-google-cloud-core.html
    • autopkgtest for ruby-google-cloud-core/1.6.1-1.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 ♻, 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 ♻
• ruby-puppet-syntax (3.2.1-1 to 4.0.0-1)
  • Migration status for ruby-puppet-syntax (3.2.1-1 to 4.0.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Implicit dependency: ruby-puppet-syntax ruby-puppetlabs-spec-helper (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-puppet-syntax.html
    • autopkgtest for ruby-puppet-syntax/4.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rxvt-unicode (9.31-2 to 9.31-3)
  • Migration status for rxvt-unicode (9.31-2 to 9.31-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rxvt-unicode.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• scalene (1.5.31.1-1 to 1.5.34-1)
  • Migration status for scalene (1.5.31.1-1 to 1.5.34-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scalene.html
    • autopkgtest for scalene/1.5.34-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• scribus (1.5.8+dfsg-4 to 1.5.8+dfsg-5)
  • Migration status for scribus (1.5.8+dfsg-4 to 1.5.8+dfsg-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 scribus will fix bugs in testing: #1061305
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scribus.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• siconos (4.4.0+dfsg-3 to 4.4.0+dfsg-4)
  • Migration status for siconos (4.4.0+dfsg-3 to 4.4.0+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/siconos.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 siconos/4.4.0+dfsg-4: amd64: Pass, arm64: 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
    • 2 days old (needed 2 days)
• sncosmo (2.10.3-1 to 2.10.4-1)
  • Migration status for sncosmo (2.10.3-1 to 2.10.4-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sncosmo.html
    • autopkgtest for sncosmo/2.10.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• spglib (2.2.0-3 to 2.3.1-1)
  • Migration status for spglib (2.2.0-3 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spglib.html
    • autopkgtest for spglib/2.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • 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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• sphinx-argparse-cli (1.11.1-1 to 1.13.0-1)
  • Migration status for sphinx-argparse-cli (1.11.1-1 to 1.13.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-argparse-cli.html
    • autopkgtest for sphinx-argparse-cli/1.13.0-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 ♻, 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 ♻
• tiles-autotag (1.2-4 to 1.2-5)
  • Migration status for tiles-autotag (1.2-4 to 1.2-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiles-autotag.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 ♻
• tox (4.12.1-1 to 4.13.0-1)
  • Migration status for tox (4.12.1-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tox.html
    • autopkgtest for tox/4.13.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ueberzug (- to 18.2.2-1)
  • Migration status for ueberzug (- to 18.2.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ueberzug.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ugrep (4.5.2+dfsg-1 to 5.0.0+dfsg-1)
  • Migration status for ugrep (4.5.2+dfsg-1 to 5.0.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ugrep.html
    • autopkgtest for ugrep/5.0.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• valinor (1.1.4-9 to 1.1.4+ds-10)
  • Migration status for valinor (1.1.4-9 to 1.1.4+ds-10): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valinor.html
    • autopkgtest for valinor/1.1.4+ds-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• variety (0.8.11-1 to 0.8.12-1)
  • Migration status for variety (0.8.11-1 to 0.8.12-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/variety.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 ♻
• virtme-ng (1.19-1 to 1.21-1)
  • Migration status for virtme-ng (1.19-1 to 1.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/v/virtme-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 ♻
• vvmd (0.17-1 to 0.18-1)
  • Migration status for vvmd (0.17-1 to 0.18-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vvmd.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xarray-safe-rcm (2023.06.1-3 to 2024.02.0-1)
  • Migration status for xarray-safe-rcm (2023.06.1-3 to 2024.02.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xarray-safe-rcm.html
    • autopkgtest for xarray-safe-rcm/2024.02.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• xscreensaver (6.06+dfsg1-3 to 6.08+dfsg1-1)
  • Migration status for xscreensaver (6.06+dfsg1-3 to 6.08+dfsg1-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/xscreensaver.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• boinc (7.20.5+dfsg-1.1 to 7.24.1+dfsg-2)
  • Migration status for boinc (7.20.5+dfsg-1.1 to 7.24.1+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boinc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• boot (1.3-28.1-1 to 1.3-29-1)
  • Migration status for boot (1.3-28.1-1 to 1.3-29-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/boot.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 ♻
• cross-gcc (248 to 249)
  • Migration status for cross-gcc (248 to 249): Waiting for test results or another package, or too young (no action required now - 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/cross-gcc.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 ♻
• curl (8.5.0-2 to 8.6.0-3)
  • Migration status for curl (8.5.0-2 to 8.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for curl/8.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for llvm-toolchain-17/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for mariadb/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for pdns/4.8.3-3: amd64: Ignored failure, arm64: Failed (not a regression), ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for r-bioc-rhtslib/n/a: armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻)
    • autopkgtest for siridb-server/2.0.51-2: amd64: Regression or new test ♻ (reference ♻), 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/c/curl.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 ♻
• dia (0.97.3+git20220525-5 to 0.98+git20240130-1)
  • Migration status for dia (0.97.3+git20220525-5 to 0.98+git20240130-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dia.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 ♻
• errands (45.0.4-2 to 45.1.9-1)
  • Migration status for errands (45.0.4-2 to 45.1.9-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/errands.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 ♻
• flatpak-builder (1.4.0-1 to 1.4.1-1)
  • Migration status for flatpak-builder (1.4.0-1 to 1.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flatpak-builder.html
    • autopkgtest for flatpak-builder/1.4.1-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 ♻, 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 ♻
• fonts-beng-extra (3.2.1-1 to 3.3.1-2)
  • Migration status for fonts-beng-extra (3.2.1-1 to 3.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 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-beng-extra.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 ♻
• gcc-arm-none-eabi (15:13.2.rel1-1 to 15:13.2.rel1-2)
  • Migration status for gcc-arm-none-eabi (15:13.2.rel1-1 to 15:13.2.rel1-2): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: gcc-arm-none-eabi libstdc++-arm-none-eabi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-arm-none-eabi.html
    • autopkgtest for gcc-arm-none-eabi/15:13.2.rel1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• gnuastro (0.22-1 to 0.22-3)
  • Migration status for gnuastro (0.22-1 to 0.22-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/gnuastro.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gpu-burn (0+git20240115+ds-1 to 0+git20240115+ds-2)
  • Migration status for gpu-burn (0+git20240115+ds-1 to 0+git20240115+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gsettings-desktop-schemas (45.0-2 to 46~beta-3)
  • Migration status for gsettings-desktop-schemas (45.0-2 to 46~beta-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsettings-desktop-schemas.html
    • autopkgtest for ayatana-indicator-session/blocked-on-ci-infra: amd64: Ignored failure, arm64: Ignored failure, armel: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • 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 ♻
• h2orestart (- to 0.6.0-2)
  • Migration status for h2orestart (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for h2orestart/0.6.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/h2orestart.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 ♻
• hfst-ospell (0.5.3-2 to 0.5.4-1)
  • Migration status for hfst-ospell (0.5.3-2 to 0.5.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hfst-ospell.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• identify (2.5.34-1 to 2.5.35-1)
  • Migration status for identify (2.5.34-1 to 2.5.35-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/identify.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• igtf-policy-bundle (1.126-1 to 1.127-1)
  • Migration status for igtf-policy-bundle (1.126-1 to 1.127-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/igtf-policy-bundle.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• iredis (1.14.0-1 to 1.14.1-1)
  • Migration status for iredis (1.14.0-1 to 1.14.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iredis.html
    • autopkgtest for iredis/1.14.1-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 ♻, 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 ♻
• jffi (1.3.12+ds-1 to 1.3.13+ds-1)
  • Migration status for jffi (1.3.12+ds-1 to 1.3.13+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jffi.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 ♻
• kdenlive (23.08.4-1 to 23.08.5-1)
  • Migration status for kdenlive (23.08.4-1 to 23.08.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdenlive.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 ♻
• ldc (1:1.35.0-1.2 to 1:1.36.0-2)
  • Migration status for ldc (1:1.35.0-1.2 to 1:1.36.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/l/ldc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libapache2-mod-rivet (3.2.3-1 to 3.2.4-1)
  • Migration status for libapache2-mod-rivet (3.2.3-1 to 3.2.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-rivet.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 ♻
• libeuclid-java (2.7-1 to 2.8-1)
  • Migration status for libeuclid-java (2.7-1 to 2.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libeuclid-java.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 ♻
• libfprint (- to 1:1.94.7-2)
  • Migration status for libfprint (- to 1:1.94.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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfprint.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libnative-platform-java (0.14-5 to 0.14-6)
  • Migration status for libnative-platform-java (0.14-5 to 0.14-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/libn/libnative-platform-java.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 ♻
• libnss-nis (3.1-4 to 3.1-5)
  • Migration status for libnss-nis (3.1-4 to 3.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnss-nis.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 ♻
• libnss-nisplus (1.3-4 to 1.3-5)
  • Migration status for libnss-nisplus (1.3-4 to 1.3-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/libn/libnss-nisplus.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 ♻
• libnvme (1.7.1-1 to 1.8-2)
  • Migration status for libnvme (1.7.1-1 to 1.8-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnvme.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 ♻
• libtorrent-rasterbar (2.0.9-2 to 2.0.10-1)
  • Migration status for libtorrent-rasterbar (2.0.9-2 to 2.0.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtorrent-rasterbar.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ltris (1.2.7-1 to 1.2.8-1)
  • Migration status for ltris (1.2.7-1 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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ltris.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 ♻
• mbr (1.2.1 to 1.2.2)
  • Migration status for mbr (1.2.1 to 1.2.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mbr.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 ♻
• meld (3.22.0-2 to 3.22.1-1)
  • Migration status for meld (3.22.0-2 to 3.22.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/m/meld.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 ♻
• mmdebstrap (1.4.3-3 to 1.4.3-4)
  • Migration status for mmdebstrap (1.4.3-3 to 1.4.3-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mmdebstrap.html
    • autopkgtest for mmdebstrap/1.4.3-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mozjs115 (115.7.0-3 to 115.8.0-1)
  • Migration status for mozjs115 (115.7.0-3 to 115.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/m/mozjs115.html
    • autopkgtest for mozjs115/115.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• msc-generator (8.4.2-1 to 8.5-1)
  • Migration status for msc-generator (8.4.2-1 to 8.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/msc-generator.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 ♻
• ocp (1:0.2.106+ds-1 to 1:0.2.107+ds-1)
  • Migration status for ocp (1:0.2.106+ds-1 to 1:0.2.107+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/o/ocp.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 ♻
• papi (7.1.0-2 to 7.1.0-3)
  • Migration status for papi (7.1.0-2 to 7.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for papi/7.1.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/papi.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 armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• perftest (4.5+0.17-1 to 24.01.0+0.38-1)
  • Migration status for perftest (4.5+0.17-1 to 24.01.0+0.38-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/perftest.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 ♻
• powertop (2.15-2 to 2.15-3)
  • Migration status for powertop (2.15-2 to 2.15-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/p/powertop.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• prometheus-flask-exporter (- to 0.23.0-2)
  • Migration status for prometheus-flask-exporter (- to 0.23.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-flask-exporter.html
    • autopkgtest for prometheus-flask-exporter/0.23.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• puppet-module-puppetlabs-apt (9.0.1-1 to 9.4.0-1)
  • Migration status for puppet-module-puppetlabs-apt (9.0.1-1 to 9.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: puppet-module-puppetlabs-apt puppet-module-puppetlabs-stdlib (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-apt.html
    • autopkgtest for puppet-module-puppetlabs-apt/9.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 3 days old (needed 2 days)
• puppet-module-puppetlabs-stdlib (8.5.0-1 to 9.4.1-1)
  • Migration status for puppet-module-puppetlabs-stdlib (8.5.0-1 to 9.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for puppet-module-puppetlabs-apache/5.5.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for puppet-module-puppetlabs-stdlib/9.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for puppet-module-saz-memcached/3.1.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-stdlib.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-jsonschema (4.10.3-2 to 4.19.2-2)
  • Migration status for python-jsonschema (4.10.3-2 to 4.19.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating python3-jsonschema/4.19.2-2/mips64el to testing makes gnuradio/3.10.9.2-1/mips64el uninstallable
    • migrating python3-jsonschema/4.19.2-2/mips64el to testing makes matrix-synapse/1.100.0-1/mips64el uninstallable
    • migrating python3-jsonschema/4.19.2-2/mips64el to testing makes python3-falcon/3.1.1-2+b1/mips64el uninstallable
    • migrating python3-jsonschema/4.19.2-2/mips64el to testing makes python3-nftables/1.0.9-1+b2/mips64el uninstallable
    • autopkgtest for asdf-standard/1.0.3-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for dt-schema/2022.08.2-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-jsonschema/4.19.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for yotta/0.20.5-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 3 of 5 days old
    • Build-Depends-Indep: python-jsonschema python-jsonschema-specifications
    • Build-Depends-Indep: python-jsonschema referencing
    • Build-Depends-Indep: python-jsonschema rpds-py
    • Depends: python-jsonschema python-jsonschema-specifications
    • Depends: python-jsonschema referencing
    • Depends: python-jsonschema rpds-py
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jsonschema.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-noseofyeti (2.4.6-1 to 2.4.7-1)
  • Migration status for python-noseofyeti (2.4.6-1 to 2.4.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-noseofyeti.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 ♻
• rawtherapee (5.9-2 to 5.10-1)
  • Migration status for rawtherapee (5.9-2 to 5.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rawtherapee.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 ♻
• rpds-py (- to 0.12.0-3)
  • Migration status for rpds-py (- to 0.12.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rpds-py.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 ♻
• shed (- to 1.16-1)
  • Migration status for shed (- to 1.16-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shed.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sqlglot (20.11.0-1 to 21.1.2-1)
  • Migration status for sqlglot (20.11.0-1 to 21.1.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlglot.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• toppler (1.3-1 to 1.3-2)
  • Migration status for toppler (1.3-1 to 1.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toppler.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 ♻
• virtualbox (- to 7.0.14-dfsg-2)
  • Migration status for virtualbox (- to 7.0.14-dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualbox would introduce bugs in testing: #794466
    • autopkgtest for virtualbox/7.0.14-dfsg-2: amd64: No tests, superficial or marked flaky ♻, i386: Regression or new test ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• wsdd (2:0.7.0-2.1 to 2:0.7.1-5)
  • Migration status for wsdd (2:0.7.0-2.1 to 2:0.7.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by grantma, a new source-only upload is needed to allow migration
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wsdd.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 ♻
• wxmaxima (23.08.0-1 to 24.02.1-1)
  • Migration status for wxmaxima (23.08.0-1 to 24.02.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wxmaxima.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 ♻
• yasnippet-snippets (1.0+28.gcd665c9-1 to 1.0+57.gf55b7ce-1)
  • Migration status for yasnippet-snippets (1.0+28.gcd665c9-1 to 1.0+57.gf55b7ce-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yasnippet-snippets.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 ♻
• adwaita-icon-theme (45.0-2 to 46~beta-4)
  • Migration status for adwaita-icon-theme (45.0-2 to 46~beta-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/a/adwaita-icon-theme.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 ♻
• bcm2835 (1.73+ds-1 to 1.75+ds-1)
  • Migration status for bcm2835 (1.73+ds-1 to 1.75+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bcm2835.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 ♻
• biosig (2.5.2-2 to 2.6.0-1)
  • Migration status for biosig (2.5.2-2 to 2.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biosig.html
    • autopkgtest for biosig/2.6.0-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• cbmc (5.89.0-2 to 5.95.1-4)
  • Migration status for cbmc (5.89.0-2 to 5.95.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cbmc.html
    • autopkgtest for cbmc/5.95.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• cpufetch (1.04-1 to 1.05-1)
  • Migration status for cpufetch (1.04-1 to 1.05-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpufetch.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• darktable (4.4.2-1.1 to 4.6.1-2)
  • Migration status for darktable (4.4.2-1.1 to 4.6.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/darktable.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 ♻
• dh-dlang (0.6.5 to 0.6.6)
  • Migration status for dh-dlang (0.6.5 to 0.6.6): 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
    • Too young, only 4 of 5 days old
    • Depends: dh-dlang ldc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-dlang.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 ♻
• doclifter (2.20-2 to 2.21-2)
  • Migration status for doclifter (2.20-2 to 2.21-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doclifter.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 ♻
• dub (1.34.0-1 to 1.36.0-1)
  • Migration status for dub (1.34.0-1 to 1.36.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for dub/1.36.0-1: amd64: Pass, arm64: Pass, armel: Pass, i386: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dub.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 ♻
• firmware-free (20200122-2 to 20200122-4)
  • Migration status for firmware-free (20200122-2 to 20200122-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firmware-free.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 ♻
• font-manager (0.8.8-3 to 0.8.8-4)
  • Migration status for font-manager (0.8.8-3 to 0.8.8-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating font-manager will fix bugs in testing: #1061412
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/font-manager.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fop (1:2.8-2 to 1:2.8-3)
  • Migration status for fop (1:2.8-2 to 1:2.8-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fop.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 ♻
• gdal (3.8.3+dfsg-1 to 3.8.4+dfsg-1)
  • Migration status for gdal (3.8.3+dfsg-1 to 3.8.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/g/gdal.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 ♻
• geoip-database (20231212-1 to 20240219-1)
  • Migration status for geoip-database (20231212-1 to 20240219-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/geoip-database.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 ♻
• gimagereader (3.4.2-1 to 3.4.2-2)
  • Migration status for gimagereader (3.4.2-1 to 3.4.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gimagereader.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 ♻
• gir-to-d (0.23.1-1 to 0.23.2-1)
  • Migration status for gir-to-d (0.23.1-1 to 0.23.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Depends: gir-to-d ldc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gir-to-d.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 ♻
• gitaly (16.6.5+ds1-7 to 16.8.2+ds3-2)
  • Migration status for gitaly (16.6.5+ds1-7 to 16.8.2+ds3-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: gitaly gitlab-shell
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitaly.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-shell (14.30.0-2 to 14.33.0-2)
  • Migration status for gitlab-shell (14.30.0-2 to 14.33.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-shell.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• glib-d (2.4.2-1 to 2.4.3-1)
  • Migration status for glib-d (2.4.2-1 to 2.4.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): glib-d gir-to-d
    • Depends: glib-d ldc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glib-d.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-boxes (45.0-2 to 45.0-3)
  • Migration status for gnome-boxes (45.0-2 to 45.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/gnome-boxes.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 ♻
• gnome-snapshot (45.2-2 to 46~beta-2)
  • Migration status for gnome-snapshot (45.2-2 to 46~beta-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-snapshot.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 ♻
• gr-satellites (4.4.0-2 to 5.5.0-2)
  • Migration status for gr-satellites (4.4.0-2 to 5.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gr-satellites.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 ♻
• grpc-java (1.41.3+ds-2 to 1.41.3+ds-3)
  • Migration status for grpc-java (1.41.3+ds-2 to 1.41.3+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grpc-java.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 ♻
• gstreamer-editing-services1.0 (1.22.9-1 to 1.23.2-1)
  • Migration status for gstreamer-editing-services1.0 (1.22.9-1 to 1.23.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: libgstreamer1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: libgstreamer-plugins-base1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: libgstreamer-plugins-bad1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: gir1.2-gstreamer-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: gir1.2-gst-plugins-base-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: gstreamer1.0-plugins-base (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: gstreamer1.0-x (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: gstreamer1.0-plugins-good (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on amd64: gstreamer1.0-plugins-bad (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: libgstreamer1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: libgstreamer-plugins-base1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: libgstreamer-plugins-bad1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: gir1.2-gstreamer-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: gir1.2-gst-plugins-base-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: gstreamer1.0-plugins-base (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: gstreamer1.0-x (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: gstreamer1.0-plugins-good (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on arm64: gstreamer1.0-plugins-bad (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: libgstreamer1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: libgstreamer-plugins-base1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: libgstreamer-plugins-bad1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: gir1.2-gstreamer-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: gir1.2-gst-plugins-base-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: gstreamer1.0-plugins-base (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: gstreamer1.0-x (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: gstreamer1.0-plugins-good (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armel: gstreamer1.0-plugins-bad (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: libgstreamer1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: libgstreamer-plugins-base1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: libgstreamer-plugins-bad1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: gir1.2-gstreamer-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: gir1.2-gst-plugins-base-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: gstreamer1.0-plugins-base (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: gstreamer1.0-x (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: gstreamer1.0-plugins-good (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on armhf: gstreamer1.0-plugins-bad (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: libgstreamer1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: libgstreamer-plugins-base1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: libgstreamer-plugins-bad1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: gir1.2-gstreamer-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: gir1.2-gst-plugins-base-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: gstreamer1.0-plugins-base (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: gstreamer1.0-x (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: gstreamer1.0-plugins-good (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on i386: gstreamer1.0-plugins-bad (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: libgstreamer1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: libgstreamer-plugins-base1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: libgstreamer-plugins-bad1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: gir1.2-gstreamer-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: gir1.2-gst-plugins-base-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: gstreamer1.0-plugins-base (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: gstreamer1.0-x (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: gstreamer1.0-plugins-good (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on mips64el: gstreamer1.0-plugins-bad (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: libgstreamer1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: libgstreamer-plugins-base1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: libgstreamer-plugins-bad1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: gir1.2-gstreamer-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: gir1.2-gst-plugins-base-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: gstreamer1.0-plugins-base (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: gstreamer1.0-x (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: gstreamer1.0-plugins-good (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on ppc64el: gstreamer1.0-plugins-bad (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: libgstreamer1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: libgstreamer-plugins-base1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: libgstreamer-plugins-bad1.0-dev (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: gir1.2-gstreamer-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: gir1.2-gst-plugins-base-1.0 (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: gstreamer1.0-plugins-base (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: gstreamer1.0-x (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: gstreamer1.0-plugins-good (>= 1.23.1)
    • gstreamer-editing-services1.0 unsatisfiable Build-Depends(-Arch) on s390x: gstreamer1.0-plugins-bad (>= 1.23.1)
    • 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
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gstreamer-editing-services1.0.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gtk-layer-shell (0.8.1-1 to 0.8.2-1)
  • Migration status for gtk-layer-shell (0.8.1-1 to 0.8.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-layer-shell.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 ♻
• gvfs (1.52.2-1 to 1.53.90-2)
  • Migration status for gvfs (1.52.2-1 to 1.53.90-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvfs.html
    • autopkgtest for gvfs/1.53.90-2: 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 ♻, 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 ♻
• ibus-chewing (1.6.2-1 to 2.0.0-1)
  • Migration status for ibus-chewing (1.6.2-1 to 2.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-chewing.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 ♻
• kpublictransport (22.12.3-1 to 23.04.3-1)
  • Migration status for kpublictransport (22.12.3-1 to 23.04.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kpublictransport.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 ♻
• kwartz-client (3.0-2 to 3.0-3)
  • Migration status for kwartz-client (3.0-2 to 3.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwartz-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 ♻
• libervia-backend (0.9.0~hg4208-1 to 0.9.0~hg4211-1)
  • Migration status for libervia-backend (0.9.0~hg4208-1 to 0.9.0~hg4211-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/libe/libervia-backend.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 ♻
• libuv1 (1.46.0-3 to 1.48.0-1)
  • Migration status for libuv1 (1.46.0-3 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 4 of 5 days old
  • Additional info:
    • Updating libuv1 will fix bugs in testing: #1063484
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libuv1.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 ♻
• lincity-ng (2.9~git20150314-5 to 2.9.0-1)
  • Migration status for lincity-ng (2.9~git20150314-5 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lincity-ng.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 ♻
• live-clone (2.8-1 to 3.1-1)
  • Migration status for live-clone (2.8-1 to 3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/live-clone.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 ♻
• nco (5.1.9-1 to 5.2.1-1)
  • Migration status for nco (5.1.9-1 to 5.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nco.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nvme-cli (2.7.1-1 to 2.8-1)
  • Migration status for nvme-cli (2.7.1-1 to 2.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): nvme-cli libnvme
    • Depends: nvme-cli libnvme
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvme-cli.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 ♻
• ocaml-odoc (2.3.0-2 to 2.4.1-1)
  • Migration status for ocaml-odoc (2.3.0-2 to 2.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ocaml-odoc/2.4.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-odoc.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 ♻
• openjdk-23 (23~4ea-1 to 23~10ea-1)
  • Migration status for openjdk-23 (23~4ea-1 to 23~10ea-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 libreoffice/blocked-on-ci-infra: armel: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-23/23~10ea-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 ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-23.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 ♻
• opensc (0.24.0~rc1-1 to 0.25.0~rc1-1)
  • Migration status for opensc (0.24.0~rc1-1 to 0.25.0~rc1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensc.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 ♻
• opm-grid (2023.04+ds-1 to 2023.10+ds-2)
  • Migration status for opm-grid (2023.04+ds-1 to 2023.10+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • opm-grid unsatisfiable Build-Depends(-Arch) on arm64: libopm-common-dev (>= 2023.10)
    • opm-grid unsatisfiable Build-Depends(-Arch) on ppc64el: libopm-common-dev (>= 2023.10)
    • missing build on arm64
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for opm-grid/2023.10+ds-2: amd64: Pass
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): opm-grid opm-common
    • Depends: opm-grid opm-common
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opm-grid.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• opm-models (2023.04+ds-3 to 2023.10+ds-2)
  • Migration status for opm-models (2023.04+ds-3 to 2023.10+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • opm-models unsatisfiable Build-Depends(-Arch) on arm64: libopm-grid-dev (>= 2023.10) [!mips64el]
    • opm-models unsatisfiable Build-Depends(-Arch) on arm64: libopm-common-dev (>= 2023.10)
    • opm-models unsatisfiable Build-Depends(-Arch) on ppc64el: libopm-grid-dev (>= 2023.10) [!mips64el]
    • opm-models unsatisfiable Build-Depends(-Arch) on ppc64el: libopm-common-dev (>= 2023.10)
    • missing build on arm64
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for opm-models/2023.10+ds-2: amd64: Pass
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): opm-models opm-common
    • Build-Depends(-Arch): opm-models opm-grid
    • Depends: opm-models opm-common
    • Depends: opm-models opm-grid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opm-models.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• opm-simulators (2023.04+ds-1 to 2023.10+ds-2)
  • Migration status for opm-simulators (2023.04+ds-1 to 2023.10+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • opm-simulators unsatisfiable Build-Depends(-Arch) on arm64: libopm-grid-dev (>= 2023.10)
    • opm-simulators unsatisfiable Build-Depends(-Arch) on arm64: libopm-models-dev (>= 2023.10)
    • opm-simulators unsatisfiable Build-Depends(-Arch) on ppc64el: libopm-grid-dev (>= 2023.10)
    • opm-simulators unsatisfiable Build-Depends(-Arch) on ppc64el: libopm-models-dev (>= 2023.10)
    • missing build on arm64
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for opm-simulators/2023.10+ds-2: amd64: Pass
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): opm-simulators opm-grid
    • Build-Depends(-Arch): opm-simulators opm-models
    • Depends: opm-simulators opm-common
    • Depends: opm-simulators opm-grid
    • Depends: opm-simulators opm-models
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opm-simulators.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• opm-upscaling (2023.04+ds-1 to 2023.10+ds-3)
  • Migration status for opm-upscaling (2023.04+ds-1 to 2023.10+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • opm-upscaling unsatisfiable Build-Depends(-Arch) on arm64: libopm-grid-dev (>= 2023.10)
    • opm-upscaling unsatisfiable Build-Depends(-Arch) on ppc64el: libopm-grid-dev (>= 2023.10)
    • missing build on arm64
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for opm-upscaling/2023.10+ds-3: amd64: Pass
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): opm-upscaling opm-grid
    • Depends: opm-upscaling opm-common
    • Depends: opm-upscaling opm-grid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opm-upscaling.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• packmol (1:20.14.2-1 to 1:20.14.3-1)
  • Migration status for packmol (1:20.14.2-1 to 1:20.14.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packmol.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 ♻
• pandas (1.5.3+dfsg-12 to 2.1.4+dfsg-5)
  • Migration status for pandas (1.5.3+dfsg-12 to 2.1.4+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pandas/2.1.4+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pydevd/2.10.0+ds-8: amd64: Failed (not a regression), arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for python-geopandas/0.14.3-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for q2-demux/2024.2.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for q2-quality-control/2024.2.0-2: 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 ♻, ppc64el: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
    • Too young, only 4 of 5 days old
    • Implicit dependency: pandas python-nanoget
    • Implicit dependency: pandas q2-demux
    • Implicit dependency: pandas q2-quality-control
    • Implicit dependency: pandas q2-taxa
    • Implicit dependency: pandas q2-types
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pandas.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 ♻
• pushpin (1.36.0-3 to 1.38.0-4)
  • Migration status for pushpin (1.36.0-3 to 1.38.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
    • Build-Depends(-Arch): pushpin rust-zmq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pushpin.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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-dnaio (1.0.1-1 to 1.2.0-1)
  • Migration status for python-dnaio (1.0.1-1 to 1.2.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for python-dnaio/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dnaio.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-mne (1.3.0+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for python-mne (1.3.0+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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mne.html
    • autopkgtest for python-mne/1.6.1+dfsg-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• q2-alignment (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-alignment (2023.9.0-1 to 2024.2.0-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): q2-alignment q2-types
    • Build-Depends(-Arch): q2-alignment qiime
    • Depends: q2-alignment q2-types
    • Depends: q2-alignment qiime
  • 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
    • autopkgtest for q2-alignment/2024.2.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• q2-cutadapt (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-cutadapt (2023.9.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-cutadapt/2024.2.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2-cutadapt q2-types
    • Build-Depends(-Arch): q2-cutadapt qiime
    • Depends: q2-cutadapt q2-types
    • Depends: q2-cutadapt qiime
  • 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 ♻
• q2-demux (2023.9.1+dfsg-1 to 2024.2.0+dfsg-1)
  • Migration status for q2-demux (2023.9.1+dfsg-1 to 2024.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-demux/2024.2.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2-demux q2-types
    • Build-Depends(-Arch): q2-demux qiime
    • Depends: q2-demux q2-types
    • Depends: q2-demux qiime
  • 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
    • 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 ♻
• q2-diversity-lib (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-diversity-lib (2023.9.0-1 to 2024.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2-diversity-lib qiime
    • Depends: q2-diversity-lib q2-emperor
    • Depends: q2-diversity-lib q2-feature-table
    • Depends: q2-diversity-lib qiime
  • 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
    • autopkgtest for q2-diversity-lib/2024.2.0-1: amd64: Failed (not a regression), arm64: Failed (not a regression), ppc64el: Failed (not a regression)
    • 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 ♻
• q2-feature-classifier (2023.7.0-1 to 2024.2.0-1)
  • Migration status for q2-feature-classifier (2023.7.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-feature-classifier/2024.2.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2-feature-classifier q2-feature-table
    • Build-Depends(-Arch): q2-feature-classifier q2-quality-control
    • Build-Depends(-Arch): q2-feature-classifier q2-taxa
    • Build-Depends(-Arch): q2-feature-classifier q2-types
    • Build-Depends(-Arch): q2-feature-classifier qiime
    • Depends: q2-feature-classifier q2-feature-table
    • Depends: q2-feature-classifier q2-quality-control
    • Depends: q2-feature-classifier q2-taxa
    • Depends: q2-feature-classifier q2-types
    • Depends: q2-feature-classifier qiime
  • 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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• q2-fragment-insertion (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-fragment-insertion (2023.9.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-fragment-insertion/2024.2.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2-fragment-insertion qiime
    • Depends: q2-fragment-insertion q2-types
    • Depends: q2-fragment-insertion qiime
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-fragment-insertion.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• q2-metadata (2023.9.0+dfsg-1 to 2024.2.0+dfsg-1)
  • Migration status for q2-metadata (2023.9.0+dfsg-1 to 2024.2.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 q2-quality-filter (not considered)
    • Depends: q2-metadata q2-quality-filter (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): q2-metadata q2-types
    • Build-Depends(-Arch): q2-metadata qiime
    • Depends: q2-metadata q2-types
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-metadata.html
    • autopkgtest for q2-metadata/2024.2.0+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: 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
    • 4 days old (needed 2 days)
• q2-phylogeny (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-phylogeny (2023.9.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-phylogeny/2024.2.0-1: amd64: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Depends: q2-phylogeny q2-alignment
    • Depends: q2-phylogeny q2-types
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-phylogeny.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• q2-quality-control (2022.11.1-2 to 2024.2.0-2)
  • Migration status for q2-quality-control (2022.11.1-2 to 2024.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-quality-control/2024.2.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2-quality-control q2-feature-table
    • Build-Depends(-Arch): q2-quality-control q2-taxa
    • Build-Depends(-Arch): q2-quality-control qiime
    • Depends: q2-quality-control q2-taxa
    • Depends: q2-quality-control qiime
  • Additional info:
    • Updating q2-quality-control will fix bugs in testing: #1044060
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-quality-control.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• q2-quality-filter (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-quality-filter (2023.9.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-quality-filter/2024.2.0-1: 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 ♻, ppc64el: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2-quality-filter q2-types
    • Build-Depends(-Arch): q2-quality-filter qiime
    • Depends: q2-quality-filter q2-types
    • Depends: q2-quality-filter qiime
  • 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 ♻
• q2-sample-classifier (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-sample-classifier (2023.9.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-sample-classifier/2024.2.0-1: 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 ♻, ppc64el: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2-sample-classifier qiime
    • Depends: q2-sample-classifier q2-feature-table
    • Depends: q2-sample-classifier q2-types
    • Depends: q2-sample-classifier qiime
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-sample-classifier.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 ♻
• q2-taxa (2023.9.0+dfsg-1 to 2024.2.0+dfsg-1)
  • Migration status for q2-taxa (2023.9.0+dfsg-1 to 2024.2.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
    • Build-Depends(-Arch): q2-taxa q2-types
    • Build-Depends(-Arch): q2-taxa qiime
    • Depends: q2-taxa q2-types
    • Depends: q2-taxa qiime
  • Additional info:
    • Updating q2-taxa will fix bugs in testing: #1053943
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-taxa.html
    • autopkgtest for q2-taxa/2024.2.0+dfsg-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 ♻, ppc64el: 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 ♻
• q2cli (2022.11.1-2 to 2024.2.0-1)
  • Migration status for q2cli (2022.11.1-2 to 2024.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): q2cli qiime
    • Depends: q2cli q2-feature-table
    • Depends: q2cli qiime
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2cli.html
    • autopkgtest for q2cli/2024.2.0-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, s390x: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-cran-quantmod (0.4.25-1 to 0.4.26-1)
  • Migration status for r-cran-quantmod (0.4.25-1 to 0.4.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/r/r-cran-quantmod.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-concurrent (1.1.6+dfsg-5 to 1.2.3-2)
  • Migration status for ruby-concurrent (1.1.6+dfsg-5 to 1.2.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: ruby-concurrent puppet-agent (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends-Indep: ruby-concurrent jruby
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-concurrent.html
    • autopkgtest for ruby-concurrent/1.2.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• ruby-gitlab-experiment (0.8.0-2 to 0.9.1-2)
  • Migration status for ruby-gitlab-experiment (0.8.0-2 to 0.9.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-experiment.html
    • autopkgtest for ruby-gitlab-experiment/0.9.1-2: 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-grape-path-helpers (1.7.1-1 to 2.0.1-2)
  • Migration status for ruby-grape-path-helpers (1.7.1-1 to 2.0.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-grape-path-helpers ruby-grape (not considered)
    • Invalidated by build-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, 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
    • 4 days old (needed 2 days)
• rust-assorted-debian-utils (- to 0.7.0-1)
  • Migration status for rust-assorted-debian-utils (- to 0.7.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-assorted-debian-utils rust-rfc822-like (not considered)
    • Depends: rust-assorted-debian-utils rust-rfc822-like (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-assorted-debian-utils.html
    • autopkgtest for rust-assorted-debian-utils/0.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 4 days old (needed 2 days)
• rust-async-task (4.5.0-1.1 to 4.7.0-2)
  • Migration status for rust-async-task (4.5.0-1.1 to 4.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-task/4.7.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating rust-async-task will fix bugs in testing: #1064210
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-task.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-drt-tools (- to 0.2.20-1)
  • Migration status for rust-drt-tools (- to 0.2.20-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): rust-drt-tools rust-assorted-debian-utils
    • Built-Using: rust-drt-tools rust-assorted-debian-utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-drt-tools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-futures-rustls (- to 0.24.0-2)
  • Migration status for rust-futures-rustls (- to 0.24.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-futures-rustls has no binaries on any arch
    • nothing built yet, autopkgtest delayed
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• shadow (1:4.13+dfsg1-3 to 1:4.13+dfsg1-4)
  • Migration status for shadow (1:4.13+dfsg1-3 to 1:4.13+dfsg1-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/s/shadow.html
    • autopkgtest for mariadb/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for shadow/1:4.13+dfsg1-4: 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sklearn-pandas (- to 2.2.0-3)
  • Migration status for sklearn-pandas (- to 2.2.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: sklearn-pandas pandas (not considered)
    • Depends: sklearn-pandas pandas (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sklearn-pandas.html
    • autopkgtest for sklearn-pandas/2.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 4 days old (needed 2 days)
• slidge (- to 0.1.0~rc2+git20240217.72ce4cc0-1)
  • Migration status for slidge (- to 0.1.0~rc2+git20240217.72ce4cc0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slidge.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 ♻
• slidge-matridge (- to 0+git20240208.c1f6bbf9-1)
  • Migration status for slidge-matridge (- to 0+git20240208.c1f6bbf9-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): slidge-matridge slidge
    • Depends: slidge-matridge slidge
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slidge-matridge.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 ♻
• sshuttle (1.1.1-2 to 1.1.2-1)
  • Migration status for sshuttle (1.1.1-2 to 1.1.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sshuttle.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 ♻
• uronode (2.15-2 to 2.15-3)
  • Migration status for uronode (2.15-2 to 2.15-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/u/uronode.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 ♻
• weasyprint (60.2-1 to 61.0-1)
  • Migration status for weasyprint (60.2-1 to 61.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/w/weasyprint.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 ♻
• xmlstarlet (1.6.1-3 to 1.6.1-4)
  • Migration status for xmlstarlet (1.6.1-3 to 1.6.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmlstarlet.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 ♻
• xom (1.3.8-1 to 1.3.9-1)
  • Migration status for xom (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/x/xom.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 ♻
• ax25-tools (0.0.10-rc5+git20190411+3595f87-6 to 0.0.10-rc5+git20230513+d3e6d4f-1)
  • Migration status for ax25-tools (0.0.10-rc5+git20190411+3595f87-6 to 0.0.10-rc5+git20230513+d3e6d4f-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ax25-tools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• btm (0.9.6-3 to 0.9.6-4)
  • Migration status for btm (0.9.6-3 to 0.9.6-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating btm will fix bugs in testing: #1064136
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btm.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 ♻
    • 5 days old (needed 5 days)
• budgie-control-center (1.3.0-1 to 1.4.0-1)
  • Migration status for budgie-control-center (1.3.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/budgie-control-center.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 ♻
    • 5 days old (needed 5 days)
• claws-mail (4.2.0-1 to 4.2.0-2)
  • Migration status for claws-mail (4.2.0-1 to 4.2.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/claws-mail.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 ♻
    • 5 days old (needed 5 days)
• codetiming (- to 1.4.0-2)
  • Migration status for codetiming (- to 1.4.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/codetiming.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 ♻
    • 5 days old (needed 5 days)
• cpdb-libs (1.2.0-3 to 2.0~b5-1)
  • Migration status for cpdb-libs (1.2.0-3 to 2.0~b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cpdb-libs/2.0~b5-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 ♻)
    • Not built on buildd: arch amd64 binaries uploaded by alteholz
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpdb-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 ♻
    • 5 days old (needed 5 days)
• cppad (2024.00.00.2-2 to 2024.00.00.3-1)
  • Migration status for cppad (2024.00.00.2-2 to 2024.00.00.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cppad.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 ♻
    • 5 days old (needed 5 days)
• esda (- to 2.5.1-2)
  • Migration status for esda (- to 2.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): esda numba (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): esda libpysal
    • Depends: esda libpysal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esda.html
    • autopkgtest for esda/2.5.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 5 days old (needed 2 days)
• fangfrisch (1.7.0-1 to 1.8.0-1)
  • Migration status for fangfrisch (1.7.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating fangfrisch will fix bugs in testing: #1063476
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fangfrisch.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• flake8-quotes (3.3.2-1.1 to 3.4.0-1)
  • Migration status for flake8-quotes (3.3.2-1.1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flake8-quotes.html
    • autopkgtest for flake8-quotes/3.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 ♻, 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 ♻
    • 5 days old (needed 5 days)
• fontconfig (2.14.2-6 to 2.15.0-1)
  • Migration status for fontconfig (2.14.2-6 to 2.15.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fontconfig.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for thunderbird/blocked-on-ci-infra: ppc64el: Ignored failure
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• gcpegg (5.1-15 to 5.1-16)
  • Migration status for gcpegg (5.1-15 to 5.1-16): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcpegg.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 ♻
    • 5 days old (needed 5 days)
• hinawa-utils (- to 0.4.0-1)
  • Migration status for hinawa-utils (- to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: hinawa-utils libhitaki
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hinawa-utils.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 ♻
    • 5 days old (needed 5 days)
• hipcub (5.3.3-5 to 5.7.1-2)
  • Migration status for hipcub (5.3.3-5 to 5.7.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hipcub.html
    • autopkgtest for hipcub/5.7.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• ibus-m17n (1.4.27-1 to 1.4.28-1)
  • Migration status for ibus-m17n (1.4.27-1 to 1.4.28-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-m17n.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 ♻
    • 5 days old (needed 5 days)
• igv (2.16.2+dfsg-2 to 2.17.1+dfsg-1)
  • Migration status for igv (2.16.2+dfsg-2 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/igv.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 ♻
    • 5 days old (needed 5 days)
• js-of-ocaml (5.4.0-2 to 5.6.0-1)
  • Migration status for js-of-ocaml (5.4.0-2 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: js-of-ocaml lwt/amd64
    • Depends: js-of-ocaml lwt/arm64
    • Depends: js-of-ocaml lwt/armel
    • Depends: js-of-ocaml lwt/armhf
    • Depends: js-of-ocaml lwt/i386
    • Depends: js-of-ocaml lwt/mips64el
    • Depends: js-of-ocaml lwt/ppc64el
    • Depends: js-of-ocaml lwt/s390x
    • Depends: js-of-ocaml menhir
    • Depends: js-of-ocaml ocaml-sedlex/amd64
    • Depends: js-of-ocaml ocaml-sedlex/arm64
    • Depends: js-of-ocaml ocaml-sedlex/armel
    • Depends: js-of-ocaml ocaml-sedlex/armhf
    • Depends: js-of-ocaml ocaml-sedlex/i386
    • Depends: js-of-ocaml ocaml-sedlex/mips64el
    • Depends: js-of-ocaml ocaml-sedlex/ppc64el
    • Depends: js-of-ocaml ocaml-sedlex/s390x
    • Depends: js-of-ocaml ppxlib
    • Implicit dependency: js-of-ocaml eliom
    • Implicit dependency: js-of-ocaml nurpawiki/amd64
    • Implicit dependency: js-of-ocaml nurpawiki/arm64
    • Implicit dependency: js-of-ocaml nurpawiki/armel
    • Implicit dependency: js-of-ocaml nurpawiki/armhf
    • Implicit dependency: js-of-ocaml nurpawiki/i386
    • Implicit dependency: js-of-ocaml nurpawiki/mips64el
    • Implicit dependency: js-of-ocaml nurpawiki/ppc64el
    • Implicit dependency: js-of-ocaml nurpawiki/s390x
    • Implicit dependency: js-of-ocaml ocaml-cohttp/amd64
    • Implicit dependency: js-of-ocaml ocaml-cohttp/arm64
    • Implicit dependency: js-of-ocaml ocaml-cohttp/armel
    • Implicit dependency: js-of-ocaml ocaml-cohttp/armhf
    • Implicit dependency: js-of-ocaml ocaml-cohttp/i386
    • Implicit dependency: js-of-ocaml ocaml-cohttp/mips64el
    • Implicit dependency: js-of-ocaml ocaml-cohttp/ppc64el
    • Implicit dependency: js-of-ocaml ocaml-cohttp/s390x
    • Implicit dependency: js-of-ocaml ocaml-logs/amd64
    • Implicit dependency: js-of-ocaml ocaml-logs/arm64
    • Implicit dependency: js-of-ocaml ocaml-logs/armel
    • Implicit dependency: js-of-ocaml ocaml-logs/armhf
    • Implicit dependency: js-of-ocaml ocaml-logs/i386
    • Implicit dependency: js-of-ocaml ocaml-logs/mips64el
    • Implicit dependency: js-of-ocaml ocaml-logs/ppc64el
    • Implicit dependency: js-of-ocaml ocaml-logs/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/js-of-ocaml.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 ♻
    • 5 days old (needed 5 days)
• kitty (0.32.1-1 to 0.32.2-1)
  • Migration status for kitty (0.32.1-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kitty.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 ♻
    • 5 days old (needed 5 days)
• kmc (3.2.3+dfsg-1 to 3.2.4+dfsg-1)
  • Migration status for kmc (3.2.3+dfsg-1 to 3.2.4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmc.html
    • autopkgtest for kmc/3.2.4+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• lablgtk3 (3.1.3-2 to 3.1.4-1)
  • Migration status for lablgtk3 (3.1.3-2 to 3.1.4-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: lablgtk3 frama-c/amd64
    • Implicit dependency: lablgtk3 frama-c/arm64
    • Implicit dependency: lablgtk3 frama-c/armel
    • Implicit dependency: lablgtk3 frama-c/armhf
    • Implicit dependency: lablgtk3 frama-c/i386
    • Implicit dependency: lablgtk3 frama-c/mips64el
    • Implicit dependency: lablgtk3 frama-c/ppc64el
    • Implicit dependency: lablgtk3 frama-c/s390x
    • Implicit dependency: lablgtk3 laby/armel
    • Implicit dependency: lablgtk3 laby/mips64el
    • Implicit dependency: lablgtk3 why3/amd64
    • Implicit dependency: lablgtk3 why3/arm64
    • Implicit dependency: lablgtk3 why3/armel
    • Implicit dependency: lablgtk3 why3/armhf
    • Implicit dependency: lablgtk3 why3/i386
    • Implicit dependency: lablgtk3 why3/mips64el
    • Implicit dependency: lablgtk3 why3/ppc64el
    • Implicit dependency: lablgtk3 why3/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lablgtk3.html
    • autopkgtest for lablgtk3/3.1.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• libbgcode (0.0~git20231219.7aaf717-1 to 0.0~git20240206.27ebf16-1)
  • Migration status for libbgcode (0.0~git20231219.7aaf717-1 to 0.0~git20240206.27ebf16-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbgcode.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 ♻
    • 5 days old (needed 5 days)
• libhitaki (- to 0.2.1-1)
  • Migration status for libhitaki (- to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhitaki.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 ♻
    • 5 days old (needed 5 days)
• libkysdk-base (2.2.0.0-1 to 2.2.0.1-1)
  • Migration status for libkysdk-base (2.2.0.0-1 to 2.2.0.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkysdk-base.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 ♻
    • 5 days old (needed 5 days)
• libspnav (1.1-1 to 1.1-2)
  • Migration status for libspnav (1.1-1 to 1.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libspnav.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 ♻
    • 5 days old (needed 5 days)
• loki-ecmwf (- to 0.1.6-2)
  • Migration status for loki-ecmwf (- to 0.1.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-loki-ecmwf/amd64 has unsatisfiable dependency
    • python3-loki-ecmwf-lint-rules/amd64 has unsatisfiable dependency
    • python3-loki-ecmwf-transformations/amd64 has unsatisfiable dependency
    • python3-loki-ecmwf/arm64 has unsatisfiable dependency
    • python3-loki-ecmwf-lint-rules/arm64 has unsatisfiable dependency
    • python3-loki-ecmwf-transformations/arm64 has unsatisfiable dependency
    • Build-Depends(-Arch): loki-ecmwf codetiming
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/loki-ecmwf.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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)
• low-memory-monitor (2.1-1 to 2.1-2)
  • Migration status for low-memory-monitor (2.1-1 to 2.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/low-memory-monitor.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 ♻
    • 5 days old (needed 5 days)
• lwm (1.2.4-1 to 1.2.4-2)
  • Migration status for lwm (1.2.4-1 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lwm.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 ♻
    • 5 days old (needed 5 days)
• members (20080128.1+nmu1 to 20080128.1+nmu2)
  • Migration status for members (20080128.1+nmu1 to 20080128.1+nmu2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/members.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 ♻
    • 5 days old (needed 5 days)
• ocaml-atd (2.14.1-1 to 2.15.0-1)
  • Migration status for ocaml-atd (2.14.1-1 to 2.15.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-atd.html
    • autopkgtest for ocaml-atd/2.15.0-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • 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 ♻
    • 5 days old (needed 5 days)
• ocaml-cry (1.0.1-1 to 1.0.2-2)
  • Migration status for ocaml-cry (1.0.1-1 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-cry.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 ♻
    • 5 days old (needed 5 days)
• ocaml-inotify (2.4.1-5 to 2.5-1)
  • Migration status for ocaml-inotify (2.4.1-5 to 2.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-inotify lwt/amd64
    • Depends: ocaml-inotify lwt/arm64
    • Depends: ocaml-inotify lwt/armel
    • Depends: ocaml-inotify lwt/armhf
    • Depends: ocaml-inotify lwt/i386
    • Depends: ocaml-inotify lwt/mips64el
    • Depends: ocaml-inotify lwt/ppc64el
    • Depends: ocaml-inotify lwt/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-inotify.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 ♻
    • 5 days old (needed 5 days)
• ocaml-mccs (1.1+16-1 to 1.1+17-1)
  • Migration status for ocaml-mccs (1.1+16-1 to 1.1+17-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-mccs.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 ♻
    • 5 days old (needed 5 days)
• ocaml-qcheck (0.21.2-1 to 0.21.3-1)
  • Migration status for ocaml-qcheck (0.21.2-1 to 0.21.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ocaml-qcheck/0.21.3-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-qcheck.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 ♻
    • 5 days old (needed 5 days)
• opm-common (2023.04+ds-5 to 2023.10+ds-2)
  • Migration status for opm-common (2023.04+ds-5 to 2023.10+ds-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for opm-common/2023.10+ds-2: amd64: Pass
  • Additional info:
    • Updating opm-common will fix bugs in testing: #1061426
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opm-common.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• php-amqplib (3.6.0-1 to 3.6.1-1)
  • Migration status for php-amqplib (3.6.0-1 to 3.6.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-amqplib.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 ♻
    • 5 days old (needed 5 days)
• php8.2 (8.2.12-1 to 8.2.16-2)
  • Migration status for php8.2 (8.2.12-1 to 8.2.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php8.2/8.2.16-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 symfony/5.4.35+dfsg-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php8.2.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 ♻
    • 5 days old (needed 5 days)
• pyfai (- to 2024.02-1)
  • Migration status for pyfai (- to 2024.02-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pyfai/2024.02-1: amd64: No tests, superficial or marked flaky ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: Regression or new test ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻
    • Build-Depends(-Arch): pyfai silx
    • Depends: pyfai silx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfai.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• pyhamcrest (2.0.3-2 to 2.1.0-1)
  • Migration status for pyhamcrest (2.0.3-2 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyhamcrest.html
    • autopkgtest for pyhamcrest/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 ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on 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)
• pymbolic (- to 2022.2-2)
  • Migration status for pymbolic (- to 2022.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymbolic.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 ♻
    • 5 days old (needed 5 days)
• python-configargparse (1.5.3-1 to 1.7-1)
  • Migration status for python-configargparse (1.5.3-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-configargparse.html
    • autopkgtest for python-configargparse/1.7-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
    • 5 days old (needed 5 days)
• python-geopandas (0.14.3-1 to 0.14.3-2)
  • Migration status for python-geopandas (0.14.3-1 to 0.14.3-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating python-geopandas will fix bugs in testing: #1063435
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-geopandas.html
    • autopkgtest for python-geopandas/0.14.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
    • 5 days old (needed 5 days)
• python-pmw (2.1-2 to 2.1-3)
  • Migration status for python-pmw (2.1-2 to 2.1-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pmw.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 ♻
    • 5 days old (needed 5 days)
• q2-dada2 (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-dada2 (2023.9.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-dada2/2024.2.0-1: amd64: Regression or new test ♻ (reference ♻)
    • Build-Depends(-Arch): q2-dada2 qiime
    • Depends: q2-dada2 q2-types
    • Depends: q2-dada2 qiime
  • 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 armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• q2-emperor (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-emperor (2023.9.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-emperor/2024.2.0-1: 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 ♻, ppc64el: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): q2-emperor q2-types
    • Build-Depends(-Arch): q2-emperor qiime
    • Depends: q2-emperor q2-types
    • Depends: q2-emperor qiime
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-emperor.html
    • 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)
• q2-feature-table (2023.9.0+dfsg-1 to 2024.2.0+dfsg-1)
  • Migration status for q2-feature-table (2023.9.0+dfsg-1 to 2024.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-feature-table/2024.2.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • Build-Depends(-Arch): q2-feature-table q2-types
    • Build-Depends(-Arch): q2-feature-table qiime
    • Depends: q2-feature-table q2-types
    • Depends: q2-feature-table qiime
  • 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 ♻
    • 5 days old (needed 5 days)
• q2-types (2023.9.0-1 to 2024.2.0-1)
  • Migration status for q2-types (2023.9.0-1 to 2024.2.0-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): q2-types qiime
    • Depends: q2-types qiime
  • Additional info:
    • Updating q2-types will fix bugs in testing: #1053944
    • 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
    • autopkgtest for q2-types/2024.2.0-1: amd64: Pass, arm64: Pass, ppc64el: 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
    • 5 days old (needed 2 days)
• qastools (1.2.0-1 to 1.4.0-1)
  • Migration status for qastools (1.2.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qastools.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 ♻
    • 5 days old (needed 5 days)
• qbrz (0.23.2+bzr1663-1 to 0.23.2+bzr1665-1)
  • Migration status for qbrz (0.23.2+bzr1663-1 to 0.23.2+bzr1665-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qbrz.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 ♻
• qiime (2023.9.2-1 to 2024.2.0-1)
  • Migration status for qiime (2023.9.2-1 to 2024.2.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiime.html
    • autopkgtest for qiime/2024.2.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 ♻, ppc64el: 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 ♻
    • 5 days old (needed 5 days)
• qtbase-opensource-src (5.15.10+dfsg-6 to 5.15.10+dfsg-7)
  • Migration status for qtbase-opensource-src (5.15.10+dfsg-6 to 5.15.10+dfsg-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtbase-opensource-src.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• qttools-opensource-src (5.15.10-5 to 5.15.10-6)
  • Migration status for qttools-opensource-src (5.15.10-5 to 5.15.10-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qttools-opensource-src.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 ♻
    • 5 days old (needed 5 days)
• rednotebook (2.31+ds-6 to 2.32+ds-2)
  • Migration status for rednotebook (2.31+ds-6 to 2.32+ds-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rednotebook.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 ♻
    • 5 days old (needed 5 days)
• reprepro (5.3.1-4 to 5.3.1-5)
  • Migration status for reprepro (5.3.1-4 to 5.3.1-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reprepro.html
    • autopkgtest for reprepro/5.3.1-5: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: 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 ♻
    • 5 days old (needed 5 days)
• ringdove (- to 2)
  • Migration status for ringdove (- to 2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ringdove.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 ♻
    • 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)
• rinse (4.1 to 4.2)
  • Migration status for rinse (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 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rinse.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 ♻
• rocthrust (5.3.3-5 to 5.7.1-1)
  • Migration status for rocthrust (5.3.3-5 to 5.7.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocthrust.html
    • autopkgtest for rocthrust/5.7.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-axum (- to 0.6.20-16)
  • Migration status for rust-axum (- to 0.6.20-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-axum would introduce bugs in testing: #1064232
    • autopkgtest for rust-axum/0.6.20-16: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-axum.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 ♻
    • 5 days old (needed 5 days)
• rust-palette (0.7.4-1 to 0.7.4.0+dfsg-2)
  • Migration status for rust-palette (0.7.4-1 to 0.7.4.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-palette would introduce bugs in testing: #1064234
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-palette.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 ♻
    • 5 days old (needed 5 days)
• rust-tonic (- to 0.10.2+dfsg-2)
  • Migration status for rust-tonic (- to 0.10.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-tonic/0.10.2+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-tonic rust-axum
    • Build-Depends(-Arch): rust-tonic rust-hyper-timeout
    • Depends: rust-tonic rust-axum
    • Depends: rust-tonic rust-hyper-timeout
  • 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 armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-zmq (0.9.2-2 to 0.9.2-3)
  • Migration status for rust-zmq (0.9.2-2 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zmq.html
    • autopkgtest for rust-zmq/0.9.2-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on 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)
• sccache (0.7.6-1 to 0.7.7-1)
  • Migration status for sccache (0.7.6-1 to 0.7.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sccache.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 ♻
    • 5 days old (needed 5 days)
• scikit-learn (1.2.1+dfsg-1 to 1.4.1.post1+dfsg-1)
  • Migration status for scikit-learn (1.2.1+dfsg-1 to 1.4.1.post1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for imbalanced-learn/0.10.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for scikit-learn/1.4.1.post1+dfsg-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating scikit-learn will fix bugs in testing: #1029701
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scikit-learn.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 ♻
    • 5 days old (needed 5 days)
• simple-revision-control (1.29-1 to 1.33-1)
  • Migration status for simple-revision-control (1.29-1 to 1.33-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simple-revision-control.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 ♻
    • 5 days old (needed 5 days)
• sm (2.2-5.7.1-1 to 2.2-6.0-1)
  • Migration status for sm (2.2-5.7.1-1 to 2.2-6.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sm.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 ♻
    • 5 days old (needed 5 days)
• sway (1.9~rc.3-1 to 1.9~rc.4-1)
  • Migration status for sway (1.9~rc.3-1 to 1.9~rc.4-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sway.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 ♻
    • 5 days old (needed 5 days)
• sysprof (45.1-2 to 46~beta-1)
  • Migration status for sysprof (45.1-2 to 46~beta-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysprof.html
    • autopkgtest for sysprof/46~beta-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
    • 5 days old (needed 5 days)
• tiktoken (0.4.0-2 to 0.6.0-2)
  • Migration status for tiktoken (0.4.0-2 to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tiktoken/0.6.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiktoken.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 ♻
    • 5 days old (needed 5 days)
• tmuxp (- to 1.38.0-1)
  • Migration status for tmuxp (- to 1.38.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tmuxp would introduce bugs in testing: #1060775
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tmuxp.html
    • autopkgtest for tmuxp/1.38.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 5 days old (needed 2 days)
• triangle (1.6-5 to 1.6-6)
  • Migration status for triangle (1.6-5 to 1.6-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 5 days old (needed 5 days)
• ucx (1.15.0-1 to 1.16.0+ds-1)
  • Migration status for ucx (1.15.0-1 to 1.16.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch arm64 binaries uploaded by mckinstry
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ucx.html
    • 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 ♻
    • 5 days old (needed 5 days)
• vagrant-libvirt (0.11.2-1 to 0.12.2-1)
  • Migration status for vagrant-libvirt (0.11.2-1 to 0.12.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-libvirt.html
    • autopkgtest for vagrant-libvirt/0.12.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
    • 5 days old (needed 5 days)
• visidata (- to 3.0.2-1)
  • Migration status for visidata (- to 3.0.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/visidata.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 ♻
    • 5 days old (needed 5 days)
• wl-mirror (0.15.0-1 to 0.16.1-1)
  • Migration status for wl-mirror (0.15.0-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wl-mirror.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 ♻
    • 5 days old (needed 5 days)
• xfsprogs (6.5.0-1 to 6.6.0-1)
  • Migration status for xfsprogs (6.5.0-1 to 6.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfsprogs.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 ♻
• xpdf (3.04+git20240124-1 to 3.04+git20240202-1)
  • Migration status for xpdf (3.04+git20240124-1 to 3.04+git20240202-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xpdf.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• zarr (2.16.1+ds-2 to 2.17.0+ds-1)
  • Migration status for zarr (2.16.1+ds-2 to 2.17.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for zarr/2.17.0+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zarr.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 ♻
    • 5 days old (needed 5 days)
• golang-github-openzipkin-zipkin-go (0.1.5+git20190103.2fd7f4a-1.1 to 0.1.5+git20190103.2fd7f4a-2)
  • Migration status for golang-github-openzipkin-zipkin-go (0.1.5+git20190103.2fd7f4a-1.1 to 0.1.5+git20190103.2fd7f4a-2): 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/g/golang-github-openzipkin-zipkin-go.html
    • autopkgtest for golang-github-openzipkin-zipkin-go/0.1.5+git20190103.2fd7f4a-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ocaml-mirage-crypto (0.11.2-1 to 0.11.2-2)
  • Migration status for ocaml-mirage-crypto (0.11.2-1 to 0.11.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-mirage-crypto ocaml-cstruct/amd64
    • Depends: ocaml-mirage-crypto ocaml-cstruct/arm64
    • Depends: ocaml-mirage-crypto ocaml-cstruct/armhf
    • Depends: ocaml-mirage-crypto ocaml-cstruct/i386
    • Depends: ocaml-mirage-crypto ocaml-cstruct/ppc64el
    • Depends: ocaml-mirage-crypto ocaml-cstruct/s390x
    • Depends: ocaml-mirage-crypto ocaml-logs/amd64
    • Depends: ocaml-mirage-crypto ocaml-logs/arm64
    • Depends: ocaml-mirage-crypto ocaml-logs/armhf
    • Depends: ocaml-mirage-crypto ocaml-logs/i386
    • Depends: ocaml-mirage-crypto ocaml-logs/ppc64el
    • Depends: ocaml-mirage-crypto ocaml-logs/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-mirage-crypto.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 ♻
    • 6 days old (needed 5 days)
• auxilium (- to 0.0.9)
  • Migration status for auxilium (- to 0.0.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/auxilium.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 ♻
    • 7 days old (needed 5 days)
• bin-prot (1:0.15.0-3 to 1:0.16.0-1)
  • Migration status for bin-prot (1:0.15.0-3 to 1:0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: bin-prot ppx-compare/amd64
    • Depends: bin-prot ppx-compare/arm64
    • Depends: bin-prot ppx-compare/armel
    • Depends: bin-prot ppx-compare/armhf
    • Depends: bin-prot ppx-compare/i386
    • Depends: bin-prot ppx-compare/mips64el
    • Depends: bin-prot ppx-compare/ppc64el
    • Depends: bin-prot ppx-compare/s390x
    • Depends: bin-prot ppx-sexp-conv/amd64
    • Depends: bin-prot ppx-sexp-conv/arm64
    • Depends: bin-prot ppx-sexp-conv/armel
    • Depends: bin-prot ppx-sexp-conv/armhf
    • Depends: bin-prot ppx-sexp-conv/i386
    • Depends: bin-prot ppx-sexp-conv/mips64el
    • Depends: bin-prot ppx-sexp-conv/ppc64el
    • Depends: bin-prot ppx-sexp-conv/s390x
    • Depends: bin-prot ppx-stable-witness/amd64
    • Depends: bin-prot ppx-stable-witness/arm64
    • Depends: bin-prot ppx-stable-witness/armhf
    • Depends: bin-prot ppx-stable-witness/i386
    • Depends: bin-prot ppx-stable-witness/ppc64el
    • Depends: bin-prot ppx-stable-witness/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bin-prot.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 ♻
    • 7 days old (needed 5 days)
• dar (2.7.13-2 to 2.7.13-5)
  • Migration status for dar (2.7.13-2 to 2.7.13-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: dar curl (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dar.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 ♻
    • 7 days old (needed 2 days)
• libcbor (0.10.2-1.1 to 0.10.2-1.2)
  • Migration status for libcbor (0.10.2-1.1 to 0.10.2-1.2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcbor.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 ♻
    • 7 days old (needed 5 days)
• libmediainfo (23.11+dfsg-1 to 24.01+dfsg-1)
  • Migration status for libmediainfo (23.11+dfsg-1 to 24.01+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmediainfo.html
    • autopkgtest for libmediainfo/24.01+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 7 days)
• ocaml-mm (- to 0.8.5-1)
  • Migration status for ocaml-mm (- to 0.8.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-mm ocamlsdl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-mm.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 ♻
    • 7 days old (needed 5 days)
• python-looseversion (- to 1.3.0-1)
  • Migration status for python-looseversion (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by 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/p/python-looseversion.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 ♻
    • 7 days old (needed 5 days)
• python-pyu2f (- to 0.1.5-1)
  • Migration status for python-pyu2f (- to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by H.LiebermanBerg@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyu2f.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 ♻
    • 7 days old (needed 5 days)
• snapraid (12.2-1 to 12.3-1)
  • Migration status for snapraid (12.2-1 to 12.3-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snapraid.html
    • 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 ♻
    • 7 days old (needed 5 days)
• virt-firmware (- to 24.1.1-1)
  • Migration status for virt-firmware (- to 24.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for virt-firmware/24.1.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virt-firmware.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 ♻
    • 7 days old (needed 5 days)
• eliom (10.1.0-2 to 10.2.0-1)
  • Migration status for eliom (10.1.0-2 to 10.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: eliom js-of-ocaml
    • Depends: eliom js-of-ocaml-ocamlbuild/amd64
    • Depends: eliom js-of-ocaml-ocamlbuild/arm64
    • Depends: eliom js-of-ocaml-ocamlbuild/armhf
    • Depends: eliom js-of-ocaml-ocamlbuild/i386
    • Depends: eliom js-of-ocaml-ocamlbuild/ppc64el
    • Depends: eliom js-of-ocaml-ocamlbuild/s390x
    • Depends: eliom lwt/amd64
    • Depends: eliom lwt/arm64
    • Depends: eliom lwt/armel
    • Depends: eliom lwt/armhf
    • Depends: eliom lwt/i386
    • Depends: eliom lwt/mips64el
    • Depends: eliom lwt/ppc64el
    • Depends: eliom lwt/s390x
    • Depends: eliom ocaml-angstrom
    • Depends: eliom ocaml-cohttp/amd64
    • Depends: eliom ocaml-cohttp/arm64
    • Depends: eliom ocaml-cohttp/armhf
    • Depends: eliom ocaml-cohttp/i386
    • Depends: eliom ocaml-cohttp/ppc64el
    • Depends: eliom ocaml-cohttp/s390x
    • Depends: eliom ocaml-conduit
    • Depends: eliom ocaml-uri/amd64
    • Depends: eliom ocaml-uri/arm64
    • Depends: eliom ocaml-uri/armel
    • Depends: eliom ocaml-uri/armhf
    • Depends: eliom ocaml-uri/i386
    • Depends: eliom ocaml-uri/mips64el
    • Depends: eliom ocaml-uri/ppc64el
    • Depends: eliom ocaml-uri/s390x
    • Depends: eliom ocamlbuild
    • Depends: eliom ocsigenserver/amd64
    • Depends: eliom ocsigenserver/arm64
    • Depends: eliom ocsigenserver/armhf
    • Depends: eliom ocsigenserver/i386
    • Depends: eliom ocsigenserver/ppc64el
    • Depends: eliom ocsigenserver/s390x
    • Depends: eliom ppxlib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eliom.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 ♻
    • 8 days old (needed 5 days)
• mathgl (8.0.1-4 to 8.0.1-7)
  • Migration status for mathgl (8.0.1-4 to 8.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mathgl/8.0.1-7: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Updating mathgl will fix bugs in testing: #1063797
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathgl.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 ♻
    • 8 days old (needed 5 days)
• menhir (20230608+ds-1 to 20231231+ds-1)
  • Migration status for menhir (20230608+ds-1 to 20231231+ds-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: menhir elpi/amd64
    • Implicit dependency: menhir elpi/arm64
    • Implicit dependency: menhir elpi/armhf
    • Implicit dependency: menhir elpi/i386
    • Implicit dependency: menhir elpi/ppc64el
    • Implicit dependency: menhir elpi/s390x
    • Implicit dependency: menhir js-of-ocaml
    • Implicit dependency: menhir morbig/amd64
    • Implicit dependency: menhir morbig/arm64
    • Implicit dependency: menhir morbig/armel
    • Implicit dependency: menhir morbig/armhf
    • Implicit dependency: menhir morbig/i386
    • Implicit dependency: menhir morbig/mips64el
    • Implicit dependency: menhir morbig/ppc64el
    • Implicit dependency: menhir morbig/s390x
    • Implicit dependency: menhir why3/amd64
    • Implicit dependency: menhir why3/arm64
    • Implicit dependency: menhir why3/armel
    • Implicit dependency: menhir why3/armhf
    • Implicit dependency: menhir why3/i386
    • Implicit dependency: menhir why3/mips64el
    • Implicit dependency: menhir why3/ppc64el
    • Implicit dependency: menhir why3/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/menhir.html
    • autopkgtest for menhir/20231231+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 8 days old (needed 2 days)
• mesa (23.3.5-1 to 24.0.1-1)
  • Migration status for mesa (23.3.5-1 to 24.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mesa would introduce bugs in testing: #1064123
  • Additional info:
    • Updating mesa will fix bugs in testing: #1059782
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mesa.html
    • autopkgtest for mesa/24.0.1-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• ocaml-angstrom (0.15.0-4 to 0.16.0-1)
  • Migration status for ocaml-angstrom (0.15.0-4 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: ocaml-angstrom eliom
    • Implicit dependency: ocaml-angstrom nurpawiki/amd64
    • Implicit dependency: ocaml-angstrom nurpawiki/arm64
    • Implicit dependency: ocaml-angstrom nurpawiki/armel
    • Implicit dependency: ocaml-angstrom nurpawiki/armhf
    • Implicit dependency: ocaml-angstrom nurpawiki/i386
    • Implicit dependency: ocaml-angstrom nurpawiki/mips64el
    • Implicit dependency: ocaml-angstrom nurpawiki/ppc64el
    • Implicit dependency: ocaml-angstrom nurpawiki/s390x
    • Implicit dependency: ocaml-angstrom ocaml-cohttp/amd64
    • Implicit dependency: ocaml-angstrom ocaml-cohttp/arm64
    • Implicit dependency: ocaml-angstrom ocaml-cohttp/armel
    • Implicit dependency: ocaml-angstrom ocaml-cohttp/armhf
    • Implicit dependency: ocaml-angstrom ocaml-cohttp/i386
    • Implicit dependency: ocaml-angstrom ocaml-cohttp/mips64el
    • Implicit dependency: ocaml-angstrom ocaml-cohttp/ppc64el
    • Implicit dependency: ocaml-angstrom ocaml-cohttp/s390x
    • Implicit dependency: ocaml-angstrom ocaml-conduit
    • Implicit dependency: ocaml-angstrom ocaml-uri/amd64
    • Implicit dependency: ocaml-angstrom ocaml-uri/arm64
    • Implicit dependency: ocaml-angstrom ocaml-uri/armel
    • Implicit dependency: ocaml-angstrom ocaml-uri/armhf
    • Implicit dependency: ocaml-angstrom ocaml-uri/i386
    • Implicit dependency: ocaml-angstrom ocaml-uri/mips64el
    • Implicit dependency: ocaml-angstrom ocaml-uri/ppc64el
    • Implicit dependency: ocaml-angstrom ocaml-uri/s390x
    • Implicit dependency: ocaml-angstrom ocsigenserver/amd64
    • Implicit dependency: ocaml-angstrom ocsigenserver/arm64
    • Implicit dependency: ocaml-angstrom ocsigenserver/armel
    • Implicit dependency: ocaml-angstrom ocsigenserver/armhf
    • Implicit dependency: ocaml-angstrom ocsigenserver/i386
    • Implicit dependency: ocaml-angstrom ocsigenserver/mips64el
    • Implicit dependency: ocaml-angstrom ocsigenserver/ppc64el
    • Implicit dependency: ocaml-angstrom ocsigenserver/s390x
    • Implicit dependency: ocaml-angstrom ocsipersist/amd64
    • Implicit dependency: ocaml-angstrom ocsipersist/arm64
    • Implicit dependency: ocaml-angstrom ocsipersist/armel
    • Implicit dependency: ocaml-angstrom ocsipersist/armhf
    • Implicit dependency: ocaml-angstrom ocsipersist/i386
    • Implicit dependency: ocaml-angstrom ocsipersist/mips64el
    • Implicit dependency: ocaml-angstrom ocsipersist/ppc64el
    • Implicit dependency: ocaml-angstrom ocsipersist/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-angstrom.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 ♻
    • 8 days old (needed 5 days)
• ocaml-batteries (3.7.1-3 to 3.7.2-1)
  • Migration status for ocaml-batteries (3.7.1-3 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-batteries ocaml-num
    • Implicit dependency: ocaml-batteries ocaml-expect/amd64
    • Implicit dependency: ocaml-batteries ocaml-expect/arm64
    • Implicit dependency: ocaml-batteries ocaml-expect/armhf
    • Implicit dependency: ocaml-batteries ocaml-expect/i386
    • Implicit dependency: ocaml-batteries ocaml-expect/ppc64el
    • Implicit dependency: ocaml-batteries ocaml-expect/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-batteries.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 ♻
    • 8 days old (needed 5 days)
• ocaml-conduit (6.2.0-3 to 6.2.1-1)
  • Migration status for ocaml-conduit (6.2.0-3 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-conduit lwt/amd64
    • Depends: ocaml-conduit lwt/arm64
    • Depends: ocaml-conduit lwt/armel
    • Depends: ocaml-conduit lwt/armhf
    • Depends: ocaml-conduit lwt/i386
    • Depends: ocaml-conduit lwt/mips64el
    • Depends: ocaml-conduit lwt/ppc64el
    • Depends: ocaml-conduit lwt/s390x
    • Depends: ocaml-conduit ocaml-angstrom
    • Depends: ocaml-conduit ocaml-logs/amd64
    • Depends: ocaml-conduit ocaml-logs/arm64
    • Depends: ocaml-conduit ocaml-logs/armhf
    • Depends: ocaml-conduit ocaml-logs/i386
    • Depends: ocaml-conduit ocaml-logs/ppc64el
    • Depends: ocaml-conduit ocaml-logs/s390x
    • Depends: ocaml-conduit ocaml-uri/amd64
    • Depends: ocaml-conduit ocaml-uri/arm64
    • Depends: ocaml-conduit ocaml-uri/armel
    • Depends: ocaml-conduit ocaml-uri/armhf
    • Depends: ocaml-conduit ocaml-uri/i386
    • Depends: ocaml-conduit ocaml-uri/mips64el
    • Depends: ocaml-conduit ocaml-uri/ppc64el
    • Depends: ocaml-conduit ocaml-uri/s390x
    • Depends: ocaml-conduit sexplib310/amd64
    • Depends: ocaml-conduit sexplib310/arm64
    • Depends: ocaml-conduit sexplib310/armel
    • Depends: ocaml-conduit sexplib310/armhf
    • Depends: ocaml-conduit sexplib310/i386
    • Depends: ocaml-conduit sexplib310/mips64el
    • Depends: ocaml-conduit sexplib310/ppc64el
    • Depends: ocaml-conduit sexplib310/s390x
    • Implicit dependency: ocaml-conduit eliom
    • Implicit dependency: ocaml-conduit ocaml-cohttp/amd64
    • Implicit dependency: ocaml-conduit ocaml-cohttp/arm64
    • Implicit dependency: ocaml-conduit ocaml-cohttp/armhf
    • Implicit dependency: ocaml-conduit ocaml-cohttp/i386
    • Implicit dependency: ocaml-conduit ocaml-cohttp/ppc64el
    • Implicit dependency: ocaml-conduit ocaml-cohttp/s390x
    • Implicit dependency: ocaml-conduit ocsigenserver/amd64
    • Implicit dependency: ocaml-conduit ocsigenserver/arm64
    • Implicit dependency: ocaml-conduit ocsigenserver/armhf
    • Implicit dependency: ocaml-conduit ocsigenserver/i386
    • Implicit dependency: ocaml-conduit ocsigenserver/ppc64el
    • Implicit dependency: ocaml-conduit ocsigenserver/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-conduit.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 ♻
    • 8 days old (needed 5 days)
• ocaml-dune (3.11.1-1 to 3.14.0-1)
  • Migration status for ocaml-dune (3.11.1-1 to 3.14.0-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: ocaml-dune camomile/amd64
    • Implicit dependency: ocaml-dune camomile/arm64
    • Implicit dependency: ocaml-dune camomile/armel
    • Implicit dependency: ocaml-dune camomile/armhf
    • Implicit dependency: ocaml-dune camomile/i386
    • Implicit dependency: ocaml-dune camomile/mips64el
    • Implicit dependency: ocaml-dune camomile/ppc64el
    • Implicit dependency: ocaml-dune camomile/s390x
    • Implicit dependency: ocaml-dune utop/amd64
    • Implicit dependency: ocaml-dune utop/arm64
    • Implicit dependency: ocaml-dune utop/armel
    • Implicit dependency: ocaml-dune utop/armhf
    • Implicit dependency: ocaml-dune utop/i386
    • Implicit dependency: ocaml-dune utop/mips64el
    • Implicit dependency: ocaml-dune utop/ppc64el
    • Implicit dependency: ocaml-dune utop/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-dune.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• ocaml-num (1.4-2 to 1.5-1)
  • Migration status for ocaml-num (1.4-2 to 1.5-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: ocaml-num ocaml-batteries
    • Implicit dependency: ocaml-num ocaml-reins/amd64
    • Implicit dependency: ocaml-num ocaml-reins/arm64
    • Implicit dependency: ocaml-num ocaml-reins/armel
    • Implicit dependency: ocaml-num ocaml-reins/armhf
    • Implicit dependency: ocaml-num ocaml-reins/i386
    • Implicit dependency: ocaml-num ocaml-reins/mips64el
    • Implicit dependency: ocaml-num ocaml-reins/ppc64el
    • Implicit dependency: ocaml-num ocaml-reins/s390x
    • Implicit dependency: ocaml-num sexplib310/amd64
    • Implicit dependency: ocaml-num sexplib310/arm64
    • Implicit dependency: ocaml-num sexplib310/armel
    • Implicit dependency: ocaml-num sexplib310/armhf
    • Implicit dependency: ocaml-num sexplib310/i386
    • Implicit dependency: ocaml-num sexplib310/mips64el
    • Implicit dependency: ocaml-num sexplib310/ppc64el
    • Implicit dependency: ocaml-num sexplib310/s390x
    • Implicit dependency: ocaml-num why3/amd64
    • Implicit dependency: ocaml-num why3/arm64
    • Implicit dependency: ocaml-num why3/armel
    • Implicit dependency: ocaml-num why3/armhf
    • Implicit dependency: ocaml-num why3/i386
    • Implicit dependency: ocaml-num why3/mips64el
    • Implicit dependency: ocaml-num why3/ppc64el
    • Implicit dependency: ocaml-num why3/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-num.html
    • autopkgtest for ocaml-num/1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 8 days old (needed 2 days)
• ocamlbuild (0.14.2-2 to 0.14.3-1)
  • Migration status for ocamlbuild (0.14.2-2 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: ocamlbuild eliom
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/amd64
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/arm64
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/armel
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/armhf
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/i386
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/mips64el
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/ppc64el
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/s390x
    • Implicit dependency: ocamlbuild oasis/amd64
    • Implicit dependency: ocamlbuild oasis/arm64
    • Implicit dependency: ocamlbuild oasis/armel
    • Implicit dependency: ocamlbuild oasis/armhf
    • Implicit dependency: ocamlbuild oasis/i386
    • Implicit dependency: ocamlbuild oasis/mips64el
    • Implicit dependency: ocamlbuild oasis/ppc64el
    • Implicit dependency: ocamlbuild oasis/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlbuild.html
    • 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 ♻
    • 8 days old (needed 5 days)
• open3d (- to 0.18.0+ds-3)
  • Migration status for open3d (- to 0.18.0+ds-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): open3d pytorch (not considered)
    • Depends: open3d pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open3d.html
    • autopkgtest for open3d/0.18.0+ds-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
    • 8 days old (needed 5 days)
• ppxlib (0.31.0-1 to 0.32.0-1)
  • Migration status for ppxlib (0.31.0-1 to 0.32.0-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: ppxlib eliom
    • Implicit dependency: ppxlib elpi/amd64
    • Implicit dependency: ppxlib elpi/arm64
    • Implicit dependency: ppxlib elpi/armhf
    • Implicit dependency: ppxlib elpi/i386
    • Implicit dependency: ppxlib elpi/ppc64el
    • Implicit dependency: ppxlib elpi/s390x
    • Implicit dependency: ppxlib js-of-ocaml
    • Implicit dependency: ppxlib lwt/amd64
    • Implicit dependency: ppxlib lwt/arm64
    • Implicit dependency: ppxlib lwt/armel
    • Implicit dependency: ppxlib lwt/armhf
    • Implicit dependency: ppxlib lwt/i386
    • Implicit dependency: ppxlib lwt/mips64el
    • Implicit dependency: ppxlib lwt/ppc64el
    • Implicit dependency: ppxlib lwt/s390x
    • Implicit dependency: ppxlib obus/amd64
    • Implicit dependency: ppxlib obus/arm64
    • Implicit dependency: ppxlib obus/armel
    • Implicit dependency: ppxlib obus/armhf
    • Implicit dependency: ppxlib obus/i386
    • Implicit dependency: ppxlib obus/mips64el
    • Implicit dependency: ppxlib obus/ppc64el
    • Implicit dependency: ppxlib obus/s390x
    • Implicit dependency: ppxlib ocaml-bitstring/amd64
    • Implicit dependency: ppxlib ocaml-bitstring/arm64
    • Implicit dependency: ppxlib ocaml-bitstring/armel
    • Implicit dependency: ppxlib ocaml-bitstring/armhf
    • Implicit dependency: ppxlib ocaml-bitstring/i386
    • Implicit dependency: ppxlib ocaml-bitstring/mips64el
    • Implicit dependency: ppxlib ocaml-bitstring/ppc64el
    • Implicit dependency: ppxlib ocaml-bitstring/s390x
    • Implicit dependency: ppxlib ocaml-cstruct/amd64
    • Implicit dependency: ppxlib ocaml-cstruct/arm64
    • Implicit dependency: ppxlib ocaml-cstruct/armel
    • Implicit dependency: ppxlib ocaml-cstruct/armhf
    • Implicit dependency: ppxlib ocaml-cstruct/i386
    • Implicit dependency: ppxlib ocaml-cstruct/mips64el
    • Implicit dependency: ppxlib ocaml-cstruct/ppc64el
    • Implicit dependency: ppxlib ocaml-cstruct/s390x
    • Implicit dependency: ppxlib ocaml-sedlex/amd64
    • Implicit dependency: ppxlib ocaml-sedlex/arm64
    • Implicit dependency: ppxlib ocaml-sedlex/armel
    • Implicit dependency: ppxlib ocaml-sedlex/armhf
    • Implicit dependency: ppxlib ocaml-sedlex/i386
    • Implicit dependency: ppxlib ocaml-sedlex/mips64el
    • Implicit dependency: ppxlib ocaml-sedlex/ppc64el
    • Implicit dependency: ppxlib ocaml-sedlex/s390x
    • Implicit dependency: ppxlib ocaml-visitors/amd64
    • Implicit dependency: ppxlib ocaml-visitors/arm64
    • Implicit dependency: ppxlib ocaml-visitors/armel
    • Implicit dependency: ppxlib ocaml-visitors/armhf
    • Implicit dependency: ppxlib ocaml-visitors/i386
    • Implicit dependency: ppxlib ocaml-visitors/mips64el
    • Implicit dependency: ppxlib ocaml-visitors/ppc64el
    • Implicit dependency: ppxlib ocaml-visitors/s390x
    • Implicit dependency: ppxlib pgocaml/amd64
    • Implicit dependency: ppxlib pgocaml/arm64
    • Implicit dependency: ppxlib pgocaml/armel
    • Implicit dependency: ppxlib pgocaml/armhf
    • Implicit dependency: ppxlib pgocaml/i386
    • Implicit dependency: ppxlib pgocaml/mips64el
    • Implicit dependency: ppxlib pgocaml/ppc64el
    • Implicit dependency: ppxlib pgocaml/s390x
    • Implicit dependency: ppxlib ppx-assert/amd64
    • Implicit dependency: ppxlib ppx-assert/arm64
    • Implicit dependency: ppxlib ppx-assert/armel
    • Implicit dependency: ppxlib ppx-assert/armhf
    • Implicit dependency: ppxlib ppx-assert/i386
    • Implicit dependency: ppxlib ppx-assert/mips64el
    • Implicit dependency: ppxlib ppx-assert/ppc64el
    • Implicit dependency: ppxlib ppx-assert/s390x
    • Implicit dependency: ppxlib ppx-bin-prot/amd64
    • Implicit dependency: ppxlib ppx-bin-prot/arm64
    • Implicit dependency: ppxlib ppx-bin-prot/armel
    • Implicit dependency: ppxlib ppx-bin-prot/armhf
    • Implicit dependency: ppxlib ppx-bin-prot/i386
    • Implicit dependency: ppxlib ppx-bin-prot/mips64el
    • Implicit dependency: ppxlib ppx-bin-prot/ppc64el
    • Implicit dependency: ppxlib ppx-bin-prot/s390x
    • Implicit dependency: ppxlib ppx-cold/amd64
    • Implicit dependency: ppxlib ppx-cold/arm64
    • Implicit dependency: ppxlib ppx-cold/armel
    • Implicit dependency: ppxlib ppx-cold/armhf
    • Implicit dependency: ppxlib ppx-cold/i386
    • Implicit dependency: ppxlib ppx-cold/mips64el
    • Implicit dependency: ppxlib ppx-cold/ppc64el
    • Implicit dependency: ppxlib ppx-cold/s390x
    • Implicit dependency: ppxlib ppx-compare/amd64
    • Implicit dependency: ppxlib ppx-compare/arm64
    • Implicit dependency: ppxlib ppx-compare/armel
    • Implicit dependency: ppxlib ppx-compare/armhf
    • Implicit dependency: ppxlib ppx-compare/i386
    • Implicit dependency: ppxlib ppx-compare/mips64el
    • Implicit dependency: ppxlib ppx-compare/ppc64el
    • Implicit dependency: ppxlib ppx-compare/s390x
    • Implicit dependency: ppxlib ppx-custom-printf/amd64
    • Implicit dependency: ppxlib ppx-custom-printf/arm64
    • Implicit dependency: ppxlib ppx-custom-printf/armel
    • Implicit dependency: ppxlib ppx-custom-printf/armhf
    • Implicit dependency: ppxlib ppx-custom-printf/i386
    • Implicit dependency: ppxlib ppx-custom-printf/mips64el
    • Implicit dependency: ppxlib ppx-custom-printf/ppc64el
    • Implicit dependency: ppxlib ppx-custom-printf/s390x
    • Implicit dependency: ppxlib ppx-deriving/amd64
    • Implicit dependency: ppxlib ppx-deriving/arm64
    • Implicit dependency: ppxlib ppx-deriving/armel
    • Implicit dependency: ppxlib ppx-deriving/armhf
    • Implicit dependency: ppxlib ppx-deriving/i386
    • Implicit dependency: ppxlib ppx-deriving/mips64el
    • Implicit dependency: ppxlib ppx-deriving/ppc64el
    • Implicit dependency: ppxlib ppx-deriving/s390x
    • Implicit dependency: ppxlib ppx-deriving-yojson/amd64
    • Implicit dependency: ppxlib ppx-deriving-yojson/arm64
    • Implicit dependency: ppxlib ppx-deriving-yojson/armel
    • Implicit dependency: ppxlib ppx-deriving-yojson/armhf
    • Implicit dependency: ppxlib ppx-deriving-yojson/i386
    • Implicit dependency: ppxlib ppx-deriving-yojson/mips64el
    • Implicit dependency: ppxlib ppx-deriving-yojson/ppc64el
    • Implicit dependency: ppxlib ppx-deriving-yojson/s390x
    • Implicit dependency: ppxlib ppx-enumerate/amd64
    • Implicit dependency: ppxlib ppx-enumerate/arm64
    • Implicit dependency: ppxlib ppx-enumerate/armel
    • Implicit dependency: ppxlib ppx-enumerate/armhf
    • Implicit dependency: ppxlib ppx-enumerate/i386
    • Implicit dependency: ppxlib ppx-enumerate/mips64el
    • Implicit dependency: ppxlib ppx-enumerate/ppc64el
    • Implicit dependency: ppxlib ppx-enumerate/s390x
    • Implicit dependency: ppxlib ppx-expect/amd64
    • Implicit dependency: ppxlib ppx-expect/arm64
    • Implicit dependency: ppxlib ppx-expect/armel
    • Implicit dependency: ppxlib ppx-expect/armhf
    • Implicit dependency: ppxlib ppx-expect/i386
    • Implicit dependency: ppxlib ppx-expect/mips64el
    • Implicit dependency: ppxlib ppx-expect/ppc64el
    • Implicit dependency: ppxlib ppx-expect/s390x
    • Implicit dependency: ppxlib ppx-fields-conv/amd64
    • Implicit dependency: ppxlib ppx-fields-conv/arm64
    • Implicit dependency: ppxlib ppx-fields-conv/armel
    • Implicit dependency: ppxlib ppx-fields-conv/armhf
    • Implicit dependency: ppxlib ppx-fields-conv/i386
    • Implicit dependency: ppxlib ppx-fields-conv/mips64el
    • Implicit dependency: ppxlib ppx-fields-conv/ppc64el
    • Implicit dependency: ppxlib ppx-fields-conv/s390x
    • Implicit dependency: ppxlib ppx-globalize/amd64
    • Implicit dependency: ppxlib ppx-globalize/arm64
    • Implicit dependency: ppxlib ppx-globalize/armel
    • Implicit dependency: ppxlib ppx-globalize/armhf
    • Implicit dependency: ppxlib ppx-globalize/i386
    • Implicit dependency: ppxlib ppx-globalize/mips64el
    • Implicit dependency: ppxlib ppx-globalize/ppc64el
    • Implicit dependency: ppxlib ppx-globalize/s390x
    • Implicit dependency: ppxlib ppx-hash/amd64
    • Implicit dependency: ppxlib ppx-hash/arm64
    • Implicit dependency: ppxlib ppx-hash/armel
    • Implicit dependency: ppxlib ppx-hash/armhf
    • Implicit dependency: ppxlib ppx-hash/i386
    • Implicit dependency: ppxlib ppx-hash/mips64el
    • Implicit dependency: ppxlib ppx-hash/ppc64el
    • Implicit dependency: ppxlib ppx-hash/s390x
    • Implicit dependency: ppxlib ppx-here/amd64
    • Implicit dependency: ppxlib ppx-here/arm64
    • Implicit dependency: ppxlib ppx-here/armel
    • Implicit dependency: ppxlib ppx-here/armhf
    • Implicit dependency: ppxlib ppx-here/i386
    • Implicit dependency: ppxlib ppx-here/mips64el
    • Implicit dependency: ppxlib ppx-here/ppc64el
    • Implicit dependency: ppxlib ppx-here/s390x
    • Implicit dependency: ppxlib ppx-import/amd64
    • Implicit dependency: ppxlib ppx-import/arm64
    • Implicit dependency: ppxlib ppx-import/armel
    • Implicit dependency: ppxlib ppx-import/armhf
    • Implicit dependency: ppxlib ppx-import/i386
    • Implicit dependency: ppxlib ppx-import/mips64el
    • Implicit dependency: ppxlib ppx-import/ppc64el
    • Implicit dependency: ppxlib ppx-import/s390x
    • Implicit dependency: ppxlib ppx-inline-test/amd64
    • Implicit dependency: ppxlib ppx-inline-test/arm64
    • Implicit dependency: ppxlib ppx-inline-test/armel
    • Implicit dependency: ppxlib ppx-inline-test/armhf
    • Implicit dependency: ppxlib ppx-inline-test/i386
    • Implicit dependency: ppxlib ppx-inline-test/mips64el
    • Implicit dependency: ppxlib ppx-inline-test/ppc64el
    • Implicit dependency: ppxlib ppx-inline-test/s390x
    • Implicit dependency: ppxlib ppx-optcomp/amd64
    • Implicit dependency: ppxlib ppx-optcomp/arm64
    • Implicit dependency: ppxlib ppx-optcomp/armel
    • Implicit dependency: ppxlib ppx-optcomp/armhf
    • Implicit dependency: ppxlib ppx-optcomp/i386
    • Implicit dependency: ppxlib ppx-optcomp/mips64el
    • Implicit dependency: ppxlib ppx-optcomp/ppc64el
    • Implicit dependency: ppxlib ppx-optcomp/s390x
    • Implicit dependency: ppxlib ppx-sexp-conv/amd64
    • Implicit dependency: ppxlib ppx-sexp-conv/arm64
    • Implicit dependency: ppxlib ppx-sexp-conv/armel
    • Implicit dependency: ppxlib ppx-sexp-conv/armhf
    • Implicit dependency: ppxlib ppx-sexp-conv/i386
    • Implicit dependency: ppxlib ppx-sexp-conv/mips64el
    • Implicit dependency: ppxlib ppx-sexp-conv/ppc64el
    • Implicit dependency: ppxlib ppx-sexp-conv/s390x
    • Implicit dependency: ppxlib ppx-stable-witness/amd64
    • Implicit dependency: ppxlib ppx-stable-witness/arm64
    • Implicit dependency: ppxlib ppx-stable-witness/armel
    • Implicit dependency: ppxlib ppx-stable-witness/armhf
    • Implicit dependency: ppxlib ppx-stable-witness/i386
    • Implicit dependency: ppxlib ppx-stable-witness/mips64el
    • Implicit dependency: ppxlib ppx-stable-witness/ppc64el
    • Implicit dependency: ppxlib ppx-stable-witness/s390x
    • Implicit dependency: ppxlib ppx-string/amd64
    • Implicit dependency: ppxlib ppx-string/arm64
    • Implicit dependency: ppxlib ppx-string/armel
    • Implicit dependency: ppxlib ppx-string/armhf
    • Implicit dependency: ppxlib ppx-string/i386
    • Implicit dependency: ppxlib ppx-string/mips64el
    • Implicit dependency: ppxlib ppx-string/ppc64el
    • Implicit dependency: ppxlib ppx-string/s390x
    • Implicit dependency: ppxlib ppx-variants-conv/amd64
    • Implicit dependency: ppxlib ppx-variants-conv/arm64
    • Implicit dependency: ppxlib ppx-variants-conv/armel
    • Implicit dependency: ppxlib ppx-variants-conv/armhf
    • Implicit dependency: ppxlib ppx-variants-conv/i386
    • Implicit dependency: ppxlib ppx-variants-conv/mips64el
    • Implicit dependency: ppxlib ppx-variants-conv/ppc64el
    • Implicit dependency: ppxlib ppx-variants-conv/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ppxlib.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 ♻
    • 8 days old (needed 5 days)
• tiv (- to 1.2.1+dfsg-1)
  • Migration status for tiv (- to 1.2.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiv.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 ♻
• xsnow (1:3.7.6-1 to 1:3.7.8-1)
  • Migration status for xsnow (1:3.7.6-1 to 1:3.7.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xsnow.html
    • autopkgtest for xsnow/1:3.7.8-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 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 ♻
• awf-gtk (- to 2.8.0-1)
  • Migration status for awf-gtk (- to 2.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 9 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/awf-gtk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-control-center (1:46~alpha-2 to 1:46~beta-1)
  • Migration status for gnome-control-center (1:46~alpha-2 to 1:46~beta-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnome-control-center gsettings-desktop-schemas (not considered)
    • Depends: gnome-control-center gsettings-desktop-schemas (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-control-center.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 ♻
    • 9 days old (needed 5 days)
• gnome-keyring (42.1-1 to 46.1-1)
  • Migration status for gnome-keyring (42.1-1 to 46.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
  • Additional info:
    • Updating gnome-keyring will fix bugs in testing: #1064423
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-keyring.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 ♻
    • 9 days old (needed 5 days)
• libpappsomspp (0.9.20-1 to 0.9.24-1)
  • Migration status for libpappsomspp (0.9.20-1 to 0.9.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libpappsomspp unsatisfiable Build-Depends(-Arch) on amd64: libodsstream-dev (>= 0.9.7)
    • libpappsomspp unsatisfiable Build-Depends(-Arch) on arm64: libodsstream-dev (>= 0.9.7)
    • libpappsomspp unsatisfiable Build-Depends(-Arch) on armel: libodsstream-dev (>= 0.9.7)
    • libpappsomspp unsatisfiable Build-Depends(-Arch) on armhf: libodsstream-dev (>= 0.9.7)
    • libpappsomspp unsatisfiable Build-Depends(-Arch) on i386: libodsstream-dev (>= 0.9.7)
    • libpappsomspp unsatisfiable Build-Depends(-Arch) on mips64el: libodsstream-dev (>= 0.9.7)
    • libpappsomspp unsatisfiable Build-Depends(-Arch) on ppc64el: libodsstream-dev (>= 0.9.7)
    • libpappsomspp unsatisfiable Build-Depends(-Arch) on s390x: libodsstream-dev (>= 0.9.7)
    • 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
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 9 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpappsomspp.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• meson (1.2.3-1 to 1.3.2-1)
  • Migration status for meson (1.2.3-1 to 1.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for meson/1.3.2-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meson.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 ♻
    • 9 days old (needed 5 days)
• minexpert2 (9.3.1-1 to 9.3.2-1)
  • Migration status for minexpert2 (9.3.1-1 to 9.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • minexpert2 unsatisfiable Build-Depends(-Arch) on amd64: libpappsomspp-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on amd64: libpappsomspp-widget-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on arm64: libpappsomspp-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on arm64: libpappsomspp-widget-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on armel: libpappsomspp-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on armel: libpappsomspp-widget-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on armhf: libpappsomspp-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on armhf: libpappsomspp-widget-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on i386: libpappsomspp-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on i386: libpappsomspp-widget-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on mips64el: libpappsomspp-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on mips64el: libpappsomspp-widget-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on ppc64el: libpappsomspp-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on ppc64el: libpappsomspp-widget-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on s390x: libpappsomspp-dev (>= 0.9.24)
    • minexpert2 unsatisfiable Build-Depends(-Arch) on s390x: libpappsomspp-widget-dev (>= 0.9.24)
    • 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
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 9 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minexpert2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nvidia-graphics-drivers-tesla-460 (- to 460.106.00-14)
  • Migration status for nvidia-graphics-drivers-tesla-460 (- to 460.106.00-14): 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-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 ♻
    • 9 days old (needed 5 days)
• prometheus-pgbouncer-exporter (- to 1.7-3)
  • Migration status for prometheus-pgbouncer-exporter (- to 1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prometheus-pgbouncer-exporter would introduce bugs in testing: #991879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-pgbouncer-exporter.html
    • 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 ♻
    • 9 days old (needed 5 days)
• python-telegram-bot (20.7-2 to 20.8-1)
  • Migration status for python-telegram-bot (20.7-2 to 20.8-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-telegram-bot.html
    • autopkgtest for python-telegram-bot/20.8-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pytorch (- to 2.1.2+dfsg-2)
  • Migration status for pytorch (- to 2.1.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytorch/2.1.2+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch.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 ♻
    • 9 days old (needed 5 days)
• tailspin (2.0.0+dfsg-1 to 3.0.0+dfsg-2)
  • Migration status for tailspin (2.0.0+dfsg-1 to 3.0.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tailspin would introduce bugs in testing: #1063601
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating tailspin will fix bugs in testing: #1063865
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tailspin.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 ♻
    • 9 days old (needed 5 days)
• tmux (3.3a-5 to 3.4-1)
  • Migration status for tmux (3.3a-5 to 3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tmux would introduce bugs in testing: #1064363
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tmux.html
    • autopkgtest for tmux/3.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 9 days old (needed 7 days)
• anymeal (1.23-1 to 1.25-1)
  • Migration status for anymeal (1.23-1 to 1.25-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/anymeal.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 ♻
    • 10 days old (needed 10 days)
• camelot-py (0.11.0-3 to 0.11.0-4)
  • Migration status for camelot-py (0.11.0-3 to 0.11.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for camelot-py/0.11.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camelot-py.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 ♻
    • 10 days old (needed 5 days)
• cdogs-sdl (- to 1.5.0+dfsg-1)
  • Migration status for cdogs-sdl (- to 1.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by apo@gambaru.de
    • Not built on buildd: arch all binaries uploaded by apo@gambaru.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdogs-sdl.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 ♻
    • 10 days old (needed 10 days)
• corectrl (- to 1.3.10+ds-1)
  • Migration status for corectrl (- to 1.3.10+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): corectrl -> patchelf/0.14.3-1+b1/mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/corectrl.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 ♻
    • 10 days old (needed 5 days)
• filezilla (3.66.4-2 to 3.66.5-2)
  • Migration status for filezilla (3.66.4-2 to 3.66.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): filezilla libfilezilla (not considered)
    • Depends: filezilla libfilezilla (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/filezilla.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 ♻
    • 10 days old (needed 5 days)
• fsspec (2023.10.0-1 to 2024.2.0-1)
  • Migration status for fsspec (2023.10.0-1 to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fsspec/2024.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for intake/0.6.6-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fsspec.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 ♻
    • 10 days old (needed 5 days)
• multiqc (1.14+dfsg-1.1 to 1.18+dfsg-1)
  • Migration status for multiqc (1.14+dfsg-1.1 to 1.18+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): multiqc python-pyaml-env (not considered)
    • Depends: multiqc python-pyaml-env (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multiqc.html
    • autopkgtest for multiqc/1.18+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 10 days old (needed 2 days)
• node-luxon (- to 3.4.4-1)
  • Migration status for node-luxon (- to 3.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kapouer@melix.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-luxon.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 ♻
    • 10 days old (needed 5 days)
• octave-vrml (- to 1.0.13-9)
  • Migration status for octave-vrml (- to 1.0.13-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: octave-vrml whitedune (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-vrml.html
    • autopkgtest for octave-vrml/1.0.13-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 10 days old (needed 2 days)
• prody (- to 2.4.1+dfsg-2)
  • Migration status for prody (- to 2.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prody would introduce bugs in testing: #1058454
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for prody/2.4.1+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prody.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 ♻
    • 10 days old (needed 5 days)
• pytango (- to 9.5.0-2)
  • Migration status for pytango (- to 9.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytango/9.5.0-2: amd64: Regression or new test ♻, arm64: Pass, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytango.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 ♻
    • 10 days old (needed 5 days)
• python-nmea2 (1.18.0-1 to 1.19.0-1)
  • Migration status for python-nmea2 (1.18.0-1 to 1.19.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by dererk, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating python-nmea2 will fix bugs in testing: #1058130
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nmea2.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 ♻
    • 10 days old (needed 5 days)
• cam2ip (- to 1.6-2)
  • Migration status for cam2ip (- to 1.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): cam2ip golang-github-pbnjay-pixfont (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): cam2ip golang-github-antonini-golibjpegturbo
    • Build-Depends(-Arch): cam2ip golang-github-jamiealquiza-envy
    • Build-Depends(-Arch): cam2ip golang-github-korandiz-v4l
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cam2ip.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 ♻
    • 11 days old (needed 5 days)
• deblur (- to 1.1.1-1)
  • Migration status for deblur (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deblur.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for deblur/1.1.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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)
• gcr4 (4.1.0-2 to 4.2.0-1)
  • Migration status for gcr4 (4.1.0-2 to 4.2.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for gcr4/4.2.0-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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcr4.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 ♻
    • 11 days old (needed 5 days)
• lfortran (- to 0.30.0-5)
  • Migration status for lfortran (- to 0.30.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lfortran/0.30.0-5: amd64: Pass, arm64: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass
    • Impossible Depends: lfortran -> clang-16/1:16.0.6-16/mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lfortran.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 ♻
    • 11 days old (needed 5 days)
• libcgi-tiny-perl (- to 1.002-1)
  • Migration status for libcgi-tiny-perl (- to 1.002-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by nickm, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcgi-tiny-perl.html
    • autopkgtest for libcgi-tiny-perl/1.002-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 11 days old (needed 2 days)
• libfilezilla (0.45.0-5 to 0.46.0-1)
  • Migration status for libfilezilla (0.45.0-5 to 0.46.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by costamagnagianfranco@yahoo.it
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfilezilla.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 ♻
    • 11 days old (needed 5 days)
• nfft (- to 3.5.3-3)
  • Migration status for nfft (- to 3.5.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nfft would introduce bugs in testing: #1016379, #1063922
    • autopkgtest for nfft/3.5.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nfft.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 ♻
    • 11 days old (needed 5 days)
• nmap (7.94+git20230807.3be01efb1+dfsg-2 to 7.94+git20230807.3be01efb1+dfsg-3)
  • Migration status for nmap (7.94+git20230807.3be01efb1+dfsg-2 to 7.94+git20230807.3be01efb1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by bengen
    • Not built on buildd: arch all binaries uploaded by bengen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nmap.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 ♻
    • 11 days old (needed 5 days)
• ns3 (3.40-2 to 3.41-1)
  • Migration status for ns3 (3.40-2 to 3.41-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by mquinson
    • Not built on buildd: arch all binaries uploaded by mquinson, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ns3.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 ♻
    • 11 days old (needed 5 days)
• routine-update (- to 0.2)
  • Migration status for routine-update (- to 0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: routine-update lintian-brush (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/routine-update.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• satdump (- to 1.1.2-1)
  • Migration status for satdump (- to 1.1.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: satdump nng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/satdump.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 ♻
    • 11 days old (needed 5 days)
• sway-contrib (- to 1.8.1+20240128-1)
  • Migration status for sway-contrib (- to 1.8.1+20240128-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by birger@rantanplan.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sway-contrib.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 ♻
    • 11 days old (needed 5 days)
• tahoe-lafs (- to 1.17.0-1)
  • Migration status for tahoe-lafs (- to 1.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tahoe-lafs/1.17.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 ♻
    • Not built on buildd: arch all binaries uploaded by andrius.merkys@gmail.com, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): tahoe-lafs python-future
    • Build-Depends(-Arch): tahoe-lafs python-klein
    • Depends: tahoe-lafs python-future
    • Depends: tahoe-lafs python-klein
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tahoe-lafs.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 ♻
    • 11 days old (needed 5 days)
• unattended-upgrades (2.9.1+nmu4 to 2.10)
  • Migration status for unattended-upgrades (2.9.1+nmu4 to 2.10): 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/u/unattended-upgrades.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 ♻
    • 11 days old (needed 5 days)
• xeus (3.1.3-1 to 3.1.3-2)
  • Migration status for xeus (3.1.3-1 to 3.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for xeus-python/0.15.10+~0.6.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating xeus will fix bugs in testing: #1060164
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xeus.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 ♻
    • 11 days old (needed 5 days)
• xeus-python (0.15.10+~0.6.1-1 to 0.15.10+~0.6.1-2)
  • Migration status for xeus-python (0.15.10+~0.6.1-1 to 0.15.10+~0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for xeus-python/0.15.10+~0.6.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Build-Depends(-Arch): xeus-python xeus-zmq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xeus-python.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 ♻
    • 11 days old (needed 5 days)
• xeus-zmq (1.1.1-1 to 1.1.1-2)
  • Migration status for xeus-zmq (1.1.1-1 to 1.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for xeus-python/0.15.10+~0.6.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Build-Depends(-Arch): xeus-zmq xeus
    • Depends: xeus-zmq xeus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xeus-zmq.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 ♻
    • 11 days old (needed 5 days)
• debian-installer (20230607+deb12u4 to 20230607+deb12u5)
  • Migration status for debian-installer (20230607+deb12u4 to 20230607+deb12u5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • debian-installer unsatisfiable Build-Depends(-Arch) on amd64: linux-image-6.1.0-18-amd64 [amd64]
    • debian-installer unsatisfiable Build-Depends(-Arch) on arm64: linux-image-6.1.0-18-arm64 [arm64]
    • debian-installer unsatisfiable Build-Depends(-Arch) on i386: linux-image-6.1.0-18-686 [i386]
    • debian-installer unsatisfiable Build-Depends(-Arch) on i386: linux-image-6.1.0-18-686-pae [i386]
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-installer.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 ♻
    • 12 days old (needed 5 days)
• html2text (1.3.2a-28 to 2.2.3-2)
  • Migration status for html2text (1.3.2a-28 to 2.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for html2text/2.2.3-2: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/html2text.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 ♻
    • 12 days old (needed 5 days)
• mariadb (1:10.11.6-2 to 1:10.11.7-1)
  • Migration status for mariadb (1:10.11.6-2 to 1:10.11.7-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for mariadb/1:10.11.7-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for pdns/4.8.3-3: amd64: Ignored failure, arm64: Pass, ppc64el: Pass, s390x: Failed (not a regression)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mariadb.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 ♻
    • 12 days old (needed 5 days)
• rust-trash (- to 3.3.0-1)
  • Migration status for rust-trash (- to 3.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-trash/3.3.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-trash.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 ♻
    • 12 days old (needed 5 days)
• slurm-wlm-contrib (- to 23.11.3-1)
  • Migration status for slurm-wlm-contrib (- to 23.11.3-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 13 days old (needed 5 days)
• sogo (- to 5.9.1-1)
  • Migration status for sogo (- to 5.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sogo/s390x has unsatisfiable dependency
    • Updating sogo would introduce bugs in testing: #1054486, #1063617
    • 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 all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sogo.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• spirv-llvm-translator-16 (16.0.0-5 to 16.0.0-6)
  • Migration status for spirv-llvm-translator-16 (16.0.0-5 to 16.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): spirv-llvm-translator-16 -> clang-16/1:16.0.6-16/mips64el
    • Impossible Build-Depends(-Arch): spirv-llvm-translator-16 -> libclang-16-dev/1:16.0.6-16/mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-llvm-translator-16.html
    • autopkgtest for spirv-llvm-translator-16/16.0.0-6: amd64: Pass, 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• breezy (3.3.4-1.1 to 3.3.5-5)
  • Migration status for breezy (3.3.4-1.1 to 3.3.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for breezy/3.3.5-5: 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 ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating breezy will fix bugs in testing: #1057860, #1064425
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breezy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 14 days old (needed 5 days)
• mysqltuner (2.2.12-2 to 2.5.2-1)
  • Migration status for mysqltuner (2.2.12-2 to 2.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by cord, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysqltuner.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 ♻
    • 14 days old (needed 10 days)
• rust-sqlx (- to 0.7.3-3)
  • Migration status for rust-sqlx (- 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): rust-sqlx rust-sqlx-mysql (not considered)
    • Depends: rust-sqlx rust-sqlx-mysql (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-sqlx rust-sqlx-macros
    • Depends: rust-sqlx rust-sqlx-macros
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx.html
    • autopkgtest for rust-sqlx/0.7.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 14 days old (needed 2 days)
• beaker (1.12.1-1.1 to 1.12.1-3)
  • Migration status for beaker (1.12.1-1.1 to 1.12.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: beaker pycryptodome (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Updating beaker will fix bugs in testing: #1058366
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beaker.html
    • autopkgtest for beaker/1.12.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 15 days old (needed 2 days)
• glslang (13.1.1-3 to 14.0.0-2)
  • Migration status for glslang (13.1.1-3 to 14.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glslang would introduce bugs in testing: #1062799
    • autopkgtest for glslang/14.0.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glslang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• python-pyknon (- to 1.2-6)
  • Migration status for python-pyknon (- to 1.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyknon would introduce bugs in testing: #1056496
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyknon.html
    • autopkgtest for python-pyknon/1.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 15 days old (needed 2 days)
• rocm-compilersupport (5.2.3-2 to 6.0+git20231212.4510c28+dfsg-1~exp2)
  • Migration status for rocm-compilersupport (5.2.3-2 to 6.0+git20231212.4510c28+dfsg-1~exp2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: clang-17
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: clang-tools-17
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: libclang-17-dev
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: libmlir-17-dev
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: lld-17
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: liblld-17-dev
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: llvm-17-dev
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: mlir-17-tools
    • rocm-compilersupport unsatisfiable Build-Depends(-Arch) on mips64el: rocm-device-libs-17
    • missing build on mips64el
    • Build-Depends(-Arch): rocm-compilersupport rocm-device-libs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocm-compilersupport.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• expat (2.5.0-2 to 2.6.0-1)
  • Migration status for expat (2.5.0-2 to 2.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for python3.11/3.11.8-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: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/expat.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 ♻
    • 16 days old (needed 2 days)
• python-lsp-server (1.9.0-1 to 1.10.0-1)
  • Migration status for python-lsp-server (1.9.0-1 to 1.10.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for python-lsp-server/1.10.0-1: amd64: Pass, arm64: Failed (not a regression), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for spyder/5.5.0+ds-3: armel: Failed (not a regression), armhf: Test in progress, i386: Test in progress, ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • Implicit dependency: python-lsp-server spyder
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lsp-server.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 ♻
    • 16 days old (needed 5 days)
• r-bioc-rhtslib (2.4.1+dfsg-1 to 2.4.1+dfsg-2)
  • Migration status for r-bioc-rhtslib (2.4.1+dfsg-1 to 2.4.1+dfsg-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for r-bioc-rhtslib/2.4.1+dfsg-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating r-bioc-rhtslib will fix bugs in testing: #1063275
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rhtslib.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 ♻
    • 16 days old (needed 5 days)
• phylonium (- to 1.7-2)
  • Migration status for phylonium (- to 1.7-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for phylonium/1.7-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phylonium.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 ♻
    • 17 days old (needed 5 days)
• pynpoint (- to 0.11.0-2)
  • Migration status for pynpoint (- to 0.11.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pynpoint/amd64 has unsatisfiable dependency
    • python3-pynpoint/arm64 has unsatisfiable dependency
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pynpoint.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 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 ♻
    • 17 days old (needed 5 days)
• rust-sqlx-macros (- to 0.7.3-1)
  • Migration status for rust-sqlx-macros (- to 0.7.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-sqlx-macros rust-sqlx-macros-core (not considered)
    • Depends: rust-sqlx-macros rust-sqlx-macros-core (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-macros.html
    • autopkgtest for rust-sqlx-macros/0.7.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 17 days old (needed 2 days)
• rust-sqlx-macros-core (- to 0.7.3-1)
  • Migration status for rust-sqlx-macros-core (- to 0.7.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-sqlx-macros-core rust-sqlx-mysql (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-macros-core.html
    • autopkgtest for rust-sqlx-macros-core/0.7.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 17 days old (needed 2 days)
• rust-sqlx-mysql (- to 0.7.3-1)
  • Migration status for rust-sqlx-mysql (- to 0.7.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-sqlx-mysql rust-rsa (not considered)
    • Depends: rust-sqlx-mysql rust-rsa (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-mysql.html
    • autopkgtest for rust-sqlx-mysql/0.7.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 17 days old (needed 2 days)
• shotcut (23.12.15+git20231218+ds-1 to 24.01.31+ds-1)
  • Migration status for shotcut (23.12.15+git20231218+ds-1 to 24.01.31+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): shotcut -> patchelf/0.14.3-1+b1/mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shotcut.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 17 days old (needed 5 days)
• sugar (0.120-1 to 0.121-1)
  • Migration status for sugar (0.120-1 to 0.121-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sugar-session/amd64 has unsatisfiable dependency
    • sugar-session/arm64 has unsatisfiable dependency
  • Additional info:
    • Updating sugar will fix bugs in testing: #1061531
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sugar.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 17 days old (needed 5 days)
• flint (3.0.1-2 to 3.0.1-3)
  • Migration status for flint (3.0.1-2 to 3.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flint would introduce bugs in testing: #1063596
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • autopkgtest for flint/3.0.1-3: arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flint.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 ♻
    • 18 days old (needed 5 days)
• graph-tool (- to 2.59+ds-4)
  • Migration status for graph-tool (- to 2.59+ds-4): 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 graph-tool/2.59+ds-4: amd64: Pass, arm64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graph-tool.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 18 days old (needed 5 days)
• python-cooler (- to 0.9.3-1)
  • Migration status for python-cooler (- to 0.9.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-cooler pandas (not considered)
    • Depends: python-cooler pandas (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cooler.html
    • autopkgtest for python-cooler/0.9.3-1: amd64: Pass, arm64: Pass, ppc64el: No tests, superficial or marked flaky ♻
    • 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 ♻
    • 18 days old (needed 5 days)
• gcc-10 (- to 10.5.0-3)
  • Migration status for gcc-10 (- to 10.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-10 would introduce bugs in testing: #1023666
    • missing build on arm64
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
    • arch:arm64 not built yet, autopkgtest delayed there
    • autopkgtest for gcc-10/10.5.0-3: amd64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 19 days old (needed 5 days)
• gcc-9 (- to 9.5.0-5)
  • Migration status for gcc-9 (- to 9.5.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9 would introduce bugs in testing: #994108
    • missing build on mips64el
    • Build-Depends(-Arch): gcc-9 gcc-10
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9.html
    • autopkgtest for gcc-9/9.5.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• golang-github-googleapis-enterprise-certificate-proxy (- to 0.2.0-2)
  • Migration status for golang-github-googleapis-enterprise-certificate-proxy (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by dparsons
    • Not built on buildd: arch all binaries uploaded by dparsons, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-googleapis-enterprise-certificate-proxy.html
    • autopkgtest for golang-github-googleapis-enterprise-certificate-proxy/0.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 19 days old (needed 2 days)
• kylin-process-manager (- to 4.0.0.0-1)
  • Migration status for kylin-process-manager (- to 4.0.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kylin-process-manager would introduce bugs in testing: #1063399
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kylin-process-manager.html
    • 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 ♻
    • 19 days old (needed 5 days)
• libpysal (- to 4.9.2-2)
  • Migration status for libpysal (- to 4.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libpysal numba (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpysal.html
    • autopkgtest for libpysal/4.9.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• nng (1.6.0-1 to 1.7.2-1)
  • Migration status for nng (1.6.0-1 to 1.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nng would introduce bugs in testing: #1063604
    • missing build on i386
    • missing build on ppc64el
    • missing build on s390x
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating nng will fix bugs in testing: #1063427
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nng.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 ♻
    • 19 days old (needed 5 days)
• python-django-adminplus (- to 0.6-1)
  • Migration status for python-django-adminplus (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-adminplus.html
    • autopkgtest for python-django-adminplus/0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 19 days old (needed 7 days)
• python-nanoget (1.16.1-2 to 1.19.3-1)
  • Migration status for python-nanoget (1.16.1-2 to 1.19.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-nanoget pandas (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating python-nanoget will fix bugs in testing: #1044056
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nanoget.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for python-nanoget/1.19.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• python-pyhanko-certvalidator (- to 0.26.3-1)
  • Migration status for python-pyhanko-certvalidator (- to 0.26.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by bastian.germann@linutronix.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyhanko-certvalidator.html
    • autopkgtest for python-pyhanko-certvalidator/0.26.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 19 days old (needed 2 days)
• dials (- to 3.17.0+dfsg3-3)
  • Migration status for dials (- to 3.17.0+dfsg3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): dials pyfai (not considered)
    • Depends: dials pyfai (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): dials cctbx
    • Depends: dials cctbx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dials.html
    • autopkgtest for dials/3.17.0+dfsg3-3: amd64: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 20 days old (needed 2 days)
• falcosecurity-libs (- to 0.14.1-5)
  • Migration status for falcosecurity-libs (- to 0.14.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating falcosecurity-libs would introduce bugs in testing: #1034881
    • 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 falcosecurity-libs/0.14.1-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): falcosecurity-libs valijson
  • 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 i386 - info ♻
    • 20 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: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-lsp-ruff ruff
    • Depends: python-lsp-ruff ruff
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lsp-ruff.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 20 days old (needed 5 days)
• ffcv (- to 1.0.0+git20240202+ds-1)
  • Migration status for ffcv (- to 1.0.0+git20240202+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ffcv numba (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ffcv.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 21 days old (needed 5 days)
• morph-browser (- to 1.1.0+dfsg-1)
  • Migration status for morph-browser (- to 1.1.0+dfsg-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/m/morph-browser.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 21 days old (needed 5 days)
• mystic (- to 0.4.2-1)
  • Migration status for mystic (- to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mystic would introduce bugs in testing: #1056429
    • autopkgtest for mystic/0.4.2-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mystic.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 21 days old (needed 5 days)
• r-cran-igraph (1.6.0-1 to 2.0.1.1-1)
  • Migration status for r-cran-igraph (1.6.0-1 to 2.0.1.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for r-cran-igraph/2.0.1.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-igraph.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 21 days old (needed 5 days)
• r-cran-rpact (3.4.0-1 to 3.5.0-1)
  • Migration status for r-cran-rpact (3.4.0-1 to 3.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-rpact/3.5.0-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Failed (not a regression), ppc64el: 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-rpact.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 21 days old (needed 5 days)
• r-cran-rstanarm (2.26.1-2 to 2.32.1-1)
  • Migration status for r-cran-rstanarm (2.26.1-2 to 2.32.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rstanarm.html
    • autopkgtest for r-cran-rstanarm/2.32.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 21 days old (needed 2 days)
• ruff (- to 0.0.291+dfsg1-3)
  • Migration status for ruff (- to 0.0.291+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-ruff/arm64 has unsatisfiable dependency
    • Build-Depends(-Arch): ruff rust-rustpython-ast
    • Build-Depends(-Arch): ruff rust-rustpython-common
    • Build-Depends(-Arch): ruff rust-rustpython-parser
    • Build-Depends(-Arch): ruff rust-tikv-jemallocator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruff.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 21 days old (needed 5 days)
• ayatana-indicator-display (- to 24.1.0-1)
  • Migration status for ayatana-indicator-display (- to 24.1.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-display.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 22 days old (needed 5 days)
• emboss (6.6.0+dfsg-12 to 6.6.0+dfsg-13)
  • Migration status for emboss (6.6.0+dfsg-12 to 6.6.0+dfsg-13): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for emboss/6.6.0+dfsg-13: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Failed (not a regression)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emboss.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 22 days old (needed 5 days)
• rust-ntp-udp (- to 1.1.2-1)
  • Migration status for rust-ntp-udp (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ntp-udp would introduce bugs in testing: #1056028
    • autopkgtest for rust-ntp-udp/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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ntp-udp.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 ♻
    • 22 days old (needed 5 days)
• rust-ntpd (- to 1.1.2-1)
  • Migration status for rust-ntpd (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ntpd/1.1.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-ntpd rust-ntp-udp
    • Depends: rust-ntpd rust-ntp-udp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ntpd.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 ♻
    • 22 days old (needed 5 days)
• asterisk (- to 1:20.6.0~dfsg+~cs6.13.40431414-2)
  • Migration status for asterisk (- to 1:20.6.0~dfsg+~cs6.13.40431414-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asterisk would introduce bugs in testing: #1031046, #1059303
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk.html
    • autopkgtest for asterisk/1:20.6.0~dfsg+~cs6.13.40431414-2: 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• openjdk-8 (- to 8u402-ga-2)
  • Migration status for openjdk-8 (- to 8u402-ga-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-8 would introduce bugs in testing: #989736
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/openjdk-8.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-8/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 23 days old (needed 10 days)
• vulkan-validationlayers (- to 1.3.275.0-1)
  • Migration status for vulkan-validationlayers (- to 1.3.275.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vulkan-validationlayers glslang (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vulkan-validationlayers.html
    • 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 ♻
    • 23 days old (needed 5 days)
• bpftrace (0.19.0-1 to 0.20.1-1)
  • Migration status for bpftrace (0.19.0-1 to 0.20.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bpftrace would introduce bugs in testing: #1061481
    • Depends: bpftrace bpfcc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpftrace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 24 days old (needed 5 days)
• commit-patch (2.6-2.1 to 2.6.2-1)
  • Migration status for commit-patch (2.6-2.1 to 2.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by dkogan, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/commit-patch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 25 days old (needed 5 days)
• dt-schema (2022.08.2-5 to 2023.11-3)
  • Migration status for dt-schema (2022.08.2-5 to 2023.11-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dt-schema/2023.11-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • 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 ♻
    • 25 days old (needed 5 days)
• filament (1.9.25+dfsg2-12 to 1.9.25+dfsg2-13)
  • Migration status for filament (1.9.25+dfsg2-12 to 1.9.25+dfsg2-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating filament would introduce bugs in testing: #1063143
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for filament/1.9.25+dfsg2-13: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating filament will fix bugs in testing: #1061621
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/filament.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 25 days old (needed 5 days)
• racket-mode (20231222git0-1 to 20240129git0-1)
  • Migration status for racket-mode (20231222git0-1 to 20240129git0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for racket-mode/20240129git0-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: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/racket-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 25 days old (needed 5 days)
• uncrustify (0.72.0+dfsg1-2 to 0.78.1+dfsg1-1)
  • Migration status for uncrustify (0.72.0+dfsg1-2 to 0.78.1+dfsg1-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/u/uncrustify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 25 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 ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): asterisk-espeak asterisk
    • Depends: asterisk-espeak asterisk
  • 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 27 days old (needed 5 days)
• openjdk-11 (- to 11.0.22+7-2)
  • Migration status for openjdk-11 (- to 11.0.22+7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-11 would introduce bugs in testing: #1023237
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-11/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11.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 ♻
    • 27 days old (needed 5 days)
• pointpats (- to 2.4.0-1)
  • Migration status for pointpats (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by andrius.merkys@gmail.com, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): pointpats libpysal
    • Depends: pointpats libpysal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pointpats.html
    • autopkgtest for pointpats/2.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• python-cogent (- to 2023.12.15a1+dfsg-1)
  • Migration status for python-cogent (- to 2023.12.15a1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-cogent/2023.12.15a1+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-cogent numba
    • Depends: python-cogent numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cogent.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 27 days old (needed 5 days)
• r-cran-estimatr (1.0.0-3 to 1.0.2-1)
  • Migration status for r-cran-estimatr (1.0.0-3 to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-estimatr/1.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-estimatr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 27 days old (needed 5 days)
• r-cran-gbm (2.1.8.1-1 to 2.1.9-1)
  • Migration status for r-cran-gbm (2.1.8.1-1 to 2.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-gbm/2.1.9-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: 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-gbm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 27 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: #988246
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine-development.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 27 days old (needed 5 days)
• rust-isahc (- to 1.7.2+ds-25)
  • Migration status for rust-isahc (- to 1.7.2+ds-25): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-isahc-dev/amd64 has unsatisfiable dependency
    • librust-isahc-dev/arm64 has unsatisfiable dependency
    • Updating rust-isahc would introduce bugs in testing: #1060848
    • rust-isahc unsatisfiable Build-Depends(-Arch) on amd64: librust-polling-2+default-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-isahc.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 5 days)
• rust-microformats (- to 0.6.1-2)
  • Migration status for rust-microformats (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-microformats would introduce bugs in testing: #1050087
    • autopkgtest for rust-microformats/0.6.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-microformats.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 5 days)
• srcpd (- to 2.1.6-1)
  • Migration status for srcpd (- to 2.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating srcpd would introduce bugs in testing: #1061546
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/srcpd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 5 days)
• sysdig (- to 0.35.0+repack-1)
  • Migration status for sysdig (- to 0.35.0+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sysdig unsatisfiable Build-Depends(-Arch) on armel: libfalcosecurity0-dev (>= 0.11.3)
    • sysdig unsatisfiable Build-Depends(-Arch) on armhf: libfalcosecurity0-dev (>= 0.11.3)
    • sysdig unsatisfiable Build-Depends(-Arch) on i386: libfalcosecurity0-dev (>= 0.11.3)
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): sysdig falcosecurity-libs
    • Depends: sysdig falcosecurity-libs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysdig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 5 days)
• aflplusplus (4.08c-1 to 4.09c-1)
  • Migration status for aflplusplus (4.08c-1 to 4.09c-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aflplusplus unsatisfiable Build-Depends(-Arch) on mips64el: clang-17
    • aflplusplus unsatisfiable Build-Depends(-Arch) on mips64el: lld-17 [!s390x]
    • aflplusplus unsatisfiable Build-Depends(-Arch) on mips64el: llvm-17-dev
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aflplusplus.html
    • autopkgtest for aflplusplus/4.09c-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• redmine-plugin-redhopper (- to 2.0.0-3)
  • Migration status for redmine-plugin-redhopper (- to 2.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-redhopper redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-redhopper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 29 days old (needed 5 days)
• rust-reqsign (- to 0.14.6-1)
  • Migration status for rust-reqsign (- to 0.14.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-reqsign rust-rsa (not considered)
    • Depends: rust-reqsign rust-rsa (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-reqsign.html
    • autopkgtest for rust-reqsign/0.14.6-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 29 days old (needed 5 days)
• cctbx (- to 2023.12+ds2+~3.17.0+ds1-3)
  • Migration status for cctbx (- to 2023.12+ds2+~3.17.0+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cctbx would introduce bugs in testing: #1061604
    • autopkgtest for cctbx/2023.12+ds2+~3.17.0+ds1-3: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cctbx.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 30 days old (needed 5 days)
• gnome-shell-extension-dash-to-panel (56-1 to 60-1~exp1)
  • Migration status for gnome-shell-extension-dash-to-panel (56-1 to 60-1~exp1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-dash-to-panel/amd64 has unsatisfiable dependency
    • gnome-shell-extension-dash-to-panel/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-dash-to-panel.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• heat (- to 1:21.0.0-4)
  • Migration status for heat (- to 1:21.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for heat/1:21.0.0-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 30 days old (needed 5 days)
• openstack-cluster-installer (- to 42.3.7)
  • Migration status for openstack-cluster-installer (- to 42.3.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: openstack-cluster-installer puppetserver (not considered)
    • Invalidated by dependency
    • Depends: openstack-cluster-installer openstack-meta-packages
    • Depends: openstack-cluster-installer puppet-module-rally
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openstack-cluster-installer.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 30 days old (needed 5 days)
• rust-half (1.6.0-2 to 1.8.2-1)
  • Migration status for rust-half (1.6.0-2 to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-half/1.8.2-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-half.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• taurus (- to 5.0.0-2)
  • Migration status for taurus (- to 5.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): taurus pytango (not considered)
    • Depends: taurus pytango (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taurus.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 30 days old (needed 5 days)
• pelican (- to 4.9.1+dfsg-3)
  • Migration status for pelican (- to 4.9.1+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pelican python-watchfiles (not considered)
    • Depends: pelican python-watchfiles (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pelican.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• peony (3.2.4-2 to 4.0.0.0-1)
  • Migration status for peony (3.2.4-2 to 4.0.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • peony unsatisfiable Build-Depends(-Arch) on armel: libkysdk-applications-dev
    • peony unsatisfiable Build-Depends(-Arch) on armhf: libkysdk-applications-dev
    • peony unsatisfiable Build-Depends(-Arch) on i386: libkysdk-applications-dev
    • peony unsatisfiable Build-Depends(-Arch) on mips64el: libkysdk-applications-dev
    • peony unsatisfiable Build-Depends(-Arch) on ppc64el: libkysdk-applications-dev
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/peony.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 31 days old (needed 5 days)
• plaso (- to 20201007-3)
  • Migration status for plaso (- to 20201007-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): plaso dfvfs (not considered)
    • Depends: plaso dfvfs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plaso.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• poco (- to 1.11.0-4)
  • Migration status for poco (- to 1.11.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating poco would introduce bugs in testing: #999989
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poco.html
    • 31 days old (needed 5 days)
• python-crispy-bootstrap4 (- to 2023.1-1)
  • Migration status for python-crispy-bootstrap4 (- to 2023.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-crispy-bootstrap4/2023.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 ♻
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-crispy-bootstrap4.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 31 days old (needed 10 days)
• python-watchfiles (- to 0.21.0-2)
  • Migration status for python-watchfiles (- to 0.21.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-watchfiles/0.21.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-watchfiles.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 31 days old (needed 5 days)
• jupyterlab (- to 4.0.11+ds1-1)
  • Migration status for jupyterlab (- to 4.0.11+ds1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: jupyterlab rpds-py (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): jupyterlab jupyter-events
    • Depends: jupyterlab jupyter-events
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyterlab.html
    • autopkgtest for jupyterlab/4.0.11+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 32 days old (needed 2 days)
• libdata-find-perl (- to 0.03-2)
  • Migration status for libdata-find-perl (- to 0.03-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by frankie, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdata-find-perl.html
    • autopkgtest for libdata-find-perl/0.03-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 32 days old (needed 2 days)
• libgeo-wkt-simple-perl (- to 0.05-1)
  • Migration status for libgeo-wkt-simple-perl (- to 0.05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by frankie, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgeo-wkt-simple-perl.html
    • autopkgtest for libgeo-wkt-simple-perl/0.05-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 32 days old (needed 7 days)
• pyfftw (- to 0.13.1-2)
  • Migration status for pyfftw (- to 0.13.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pyfftw/0.13.1-2: 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• pynfft (- to 1.3.2-8)
  • Migration status for pynfft (- to 1.3.2-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pynfft nfft (not considered)
    • Depends: pynfft nfft (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynfft.html
    • autopkgtest for pynfft/1.3.2-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 32 days old (needed 2 days)
• ruby-re2 (1.7.0-1 to 2.7.0-1)
  • Migration status for ruby-re2 (1.7.0-1 to 2.7.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 ruby-re2/2.7.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating ruby-re2 will fix bugs in testing: #1062796
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-re2.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducibility regression on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
    • 32 days old (needed 5 days)
• castxml (0.6.2-2 to 0.6.3-1)
  • Migration status for castxml (0.6.2-2 to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • castxml unsatisfiable Build-Depends(-Arch) on mips64el: libclang-17-dev
    • castxml unsatisfiable Build-Depends(-Arch) on mips64el: llvm-17-dev
    • castxml unsatisfiable Build-Depends(-Arch) on mips64el: libmlir-17-dev
    • castxml unsatisfiable Build-Depends(-Arch) on mips64el: mlir-17-tools
    • castxml unsatisfiable Build-Depends(-Arch) on mips64el: clang-tools-17
    • castxml unsatisfiable Build-Depends(-Arch) on mips64el: clang-format-17
    • castxml unsatisfiable Build-Depends(-Arch) on mips64el: clang-tidy-17
    • castxml unsatisfiable Build-Depends(-Arch) on mips64el: clangd-17
    • missing build on mips64el
  • Additional info:
    • Updating castxml will fix bugs in testing: #1064424
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/castxml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• fai (6.0.5 to 6.2)
  • Migration status for fai (6.0.5 to 6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fai/6.2: amd64: Regression or new test ♻ (reference ♻), 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 ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fai.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 10 days)
• ruby-omniauth-alicloud (2.0.1-2 to 3.0.0-2)
  • Migration status for ruby-omniauth-alicloud (2.0.1-2 to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by vivekkj@disroot.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating ruby-omniauth-alicloud will fix bugs in testing: #1064420
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-alicloud.html
    • autopkgtest for ruby-omniauth-alicloud/3.0.0-2: 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• rust-loom (- to 0.5.6-2)
  • Migration status for rust-loom (- to 0.5.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-loom/0.5.6-2: amd64: Pass, arm64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-loom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 33 days old (needed 5 days)
• astra-toolbox (- to 2.1.0-4)
  • Migration status for astra-toolbox (- to 2.1.0-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 34 days old (needed 5 days)
• endless-sky (- to 0.10.4-1)
  • Migration status for endless-sky (- to 0.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating endless-sky would introduce bugs in testing: #1061241
    • missing build on i386
    • missing build on ppc64el
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/endless-sky.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 days old (needed 5 days)
• mysql-8.0 (- to 8.0.36-1)
  • Migration status for mysql-8.0 (- to 8.0.36-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-8.0 would introduce bugs in testing: #853008
    • autopkgtest for mysql-8.0/8.0.36-1: amd64: Regression or new test ♻, arm64: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Pass
    • missing build on armhf
    • Not touching package due to block request by pochu (please contact debian-release if update is needed)
    • arch:armhf not built yet, autopkgtest delayed there
  • 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
    • Waiting for reproducibility test results on armhf - info ♻
    • 34 days old (needed 5 days)
• ohai (17.9.0-2 to 18.1.3-2)
  • Migration status for ohai (17.9.0-2 to 18.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by vivekkj@disroot.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating ohai will fix bugs in testing: #1064422
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ohai.html
    • autopkgtest for ohai/18.1.3-2: 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 days old (needed 5 days)
• plplot (5.15.0+dfsg2-6 to 5.15.0+dfsg2-7+deb13u1)
  • Migration status for plplot (5.15.0+dfsg2-6 to 5.15.0+dfsg2-7+deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): plplot -> patchelf/0.14.3-1+b1/mips64el
  • Additional info:
    • Updating plplot will fix bugs in testing: #1063796
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plplot.html
    • autopkgtest for plplot/5.15.0+dfsg2-7+deb13u1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Reproducible on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 34 days old (needed 2 days)
• python-pamqp (3.2.1-1 to 3.3.0-1)
  • Migration status for python-pamqp (3.2.1-1 to 3.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-pamqp/3.3.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating python-pamqp will fix bugs in testing: #1064309
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pamqp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 34 days old (needed 10 days)
• liquidsoap (- to 2.2.3-1)
  • Migration status for liquidsoap (- to 2.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liquidsoap would introduce bugs in testing: #1064128
    • Build-Depends(-Arch): liquidsoap ocaml-lastfm
    • Build-Depends(-Arch): liquidsoap ocaml-mm
    • Build-Depends(-Arch): liquidsoap pcre-ocaml
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/liquidsoap.html
    • autopkgtest for liquidsoap/2.2.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 35 days old (needed 2 days)
• python-molotov (- to 2.7-1)
  • Migration status for python-molotov (- to 2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-molotov/2.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, 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 ♻
    • 35 days old (needed 5 days)
• transmission (- to 4.0.5-1)
  • Migration status for transmission (- to 4.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating transmission would introduce bugs in testing: #1041519
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/transmission.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• gcc-snapshot (- to 1:20240117-1)
  • Migration status for gcc-snapshot (- to 1:20240117-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-snapshot would introduce bugs in testing: #321449, #651291
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for gcc-snapshot/1:20240117-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-snapshot.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 36 days old (needed 5 days)
• napari (- to 0.5.0~a1-5)
  • Migration status for napari (- to 0.5.0~a1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): napari python-vispy (not considered)
    • Depends: napari python-vispy (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): napari docstring-parser
    • Build-Depends(-Arch): napari magicgui
    • Depends: napari magicgui
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari.html
    • autopkgtest for napari/0.5.0~a1-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
    • 36 days old (needed 2 days)
• puppet-module-rally (- to 5.4.0-1)
  • Migration status for puppet-module-rally (- to 5.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-rally.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 36 days old (needed 5 days)
• golang-bitbucket-creachadair-shell (- to 0.0.8-1)
  • Migration status for golang-bitbucket-creachadair-shell (- to 0.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-bitbucket-creachadair-shell.html
    • autopkgtest for golang-bitbucket-creachadair-shell/0.0.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 37 days old (needed 2 days)
• golang-github-adamkorcz-go-fuzz-headers-1 (- to 0.0~git20230919.8b5d3ce-1)
  • Migration status for golang-github-adamkorcz-go-fuzz-headers-1 (- to 0.0~git20230919.8b5d3ce-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-adamkorcz-go-fuzz-headers-1.html
    • autopkgtest for golang-github-adamkorcz-go-fuzz-headers-1/0.0~git20230919.8b5d3ce-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 37 days old (needed 2 days)
• golang-github-sassoftware-go-rpmutils (- to 0.2.0-1)
  • Migration status for golang-github-sassoftware-go-rpmutils (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-sassoftware-go-rpmutils.html
    • autopkgtest for golang-github-sassoftware-go-rpmutils/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 37 days old (needed 2 days)
• golang-github-shibumi-go-pathspec (- to 1.3.0-1)
  • Migration status for golang-github-shibumi-go-pathspec (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-shibumi-go-pathspec.html
    • autopkgtest for golang-github-shibumi-go-pathspec/1.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 37 days old (needed 2 days)
• golang-github-sigstore-protobuf-specs (- to 0.2.1-1)
  • Migration status for golang-github-sigstore-protobuf-specs (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-sigstore-protobuf-specs.html
    • autopkgtest for golang-github-sigstore-protobuf-specs/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 37 days old (needed 2 days)
• r-cran-bigmemory (4.6.1-1 to 4.6.4-1)
  • Migration status for r-cran-bigmemory (4.6.1-1 to 4.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-bigmemory/4.6.4-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r-cran-bigmemory will fix bugs in testing: #1064135
    • 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 ♻
    • 37 days old (needed 5 days)
• singularity-container (- to 4.0.3+ds1-1)
  • Migration status for singularity-container (- to 4.0.3+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating singularity-container would introduce bugs in testing: #1029669
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singularity-container.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• virtualbox-ext-pack (- to 7.0.14-1)
  • Migration status for virtualbox-ext-pack (- to 7.0.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • virtualbox-ext-pack/arm64 has unsatisfiable dependency
    • Depends: virtualbox-ext-pack virtualbox
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 37 days old (needed 5 days)
• chemps2 (- to 1.8.12-3)
  • Migration status for chemps2 (- to 1.8.12-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for chemps2/1.8.12-3: arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for chemps2/blocked-on-ci-infra: amd64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chemps2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 38 days old (needed 5 days)
• mdp (- to 3.6-6)
  • Migration status for mdp (- to 3.6-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdp.html
    • 38 days old (needed 5 days)
• python-sparse (- to 0.15.1-1)
  • Migration status for python-sparse (- to 0.15.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-sparse would introduce bugs in testing: #1055847
    • autopkgtest for python-sparse/0.15.1-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Regression or new test ♻
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
    • Build-Depends(-Arch): python-sparse numba
    • Depends: python-sparse numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sparse.html
    • Reproducible on amd64 - info ♻
    • 40 days old (needed 5 days)
• rust-ruma-state-res (- to 0.8.0-2)
  • Migration status for rust-ruma-state-res (- to 0.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ruma-state-res/0.8.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ruma-state-res.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 40 days old (needed 5 days)
• python-aiortc (- to 1.6.0-1)
  • Migration status for python-aiortc (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-aiortc/1.6.0-1: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiortc.html
    • Reproducible on armhf - info ♻
    • 41 days old (needed 5 days)
• python-django-guid (- to 3.4.1-3)
  • Migration status for python-django-guid (- to 3.4.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-django-guid celery (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-guid.html
    • autopkgtest for python-django-guid/3.4.1-3: 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 42 days old (needed 2 days)
• rust-transmission-client (- to 0.1.4-1)
  • Migration status for rust-transmission-client (- to 0.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-transmission-client rust-isahc (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-transmission-client.html
    • autopkgtest for rust-transmission-client/0.1.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 42 days old (needed 2 days)
• golang-github-antonini-golibjpegturbo (- to 0.0~git20141208.c03a2fa-1)
  • Migration status for golang-github-antonini-golibjpegturbo (- to 0.0~git20141208.c03a2fa-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-antonini-golibjpegturbo.html
    • autopkgtest for golang-github-antonini-golibjpegturbo/0.0~git20141208.c03a2fa-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 43 days old (needed 2 days)
• golang-github-darkhz-mpvipc (- to 0.0~git20231124.eb73ba4-1)
  • Migration status for golang-github-darkhz-mpvipc (- to 0.0~git20231124.eb73ba4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-darkhz-mpvipc.html
    • autopkgtest for golang-github-darkhz-mpvipc/0.0~git20231124.eb73ba4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 43 days old (needed 2 days)
• golang-github-jamiealquiza-envy (- to 1.1.0-1)
  • Migration status for golang-github-jamiealquiza-envy (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jamiealquiza-envy.html
    • autopkgtest for golang-github-jamiealquiza-envy/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 43 days old (needed 2 days)
• golang-github-korandiz-v4l (- to 1.1.0-1)
  • Migration status for golang-github-korandiz-v4l (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-korandiz-v4l/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-korandiz-v4l.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 43 days old (needed 5 days)
• golang-github-pbnjay-pixfont (- to 0.0~git20200714.33b7446-1)
  • Migration status for golang-github-pbnjay-pixfont (- to 0.0~git20200714.33b7446-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-pbnjay-pixfont.html
    • autopkgtest for golang-github-pbnjay-pixfont/0.0~git20200714.33b7446-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 43 days old (needed 2 days)
• hypercorn (0.14.4-1 to 0.16.0-1)
  • Migration status for hypercorn (0.14.4-1 to 0.16.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): hypercorn node-mermaid (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Updating hypercorn will fix bugs in testing: #1057351
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hypercorn.html
    • autopkgtest for hypercorn/0.16.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 43 days old (needed 2 days)
• pycryptodome (3.11.0+dfsg1-4 to 3.20.0+dfsg-1)
  • Migration status for pycryptodome (3.11.0+dfsg1-4 to 3.20.0+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for pycryptodome/3.20.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating pycryptodome will fix bugs in testing: #1052336
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycryptodome.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• snapd-glib (1.63-5 to 1.63-5.1)
  • Migration status for snapd-glib (1.63-5 to 1.63-5.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for snapd-glib/1.63-5.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass
  • Additional info:
    • Updating snapd-glib will fix bugs in testing: #1063799
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snapd-glib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• libnss-db (- to 2.2.3pre1-9)
  • Migration status for libnss-db (- to 2.2.3pre1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libnss-db would introduce bugs in testing: #1057850
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnss-db.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• obs-studio (- to 30.0.2+dfsg-2)
  • Migration status for obs-studio (- to 30.0.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • obs-studio unsatisfiable Build-Depends(-Arch) on ppc64el: libluajit-5.1-dev
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-studio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• python-cramjam (- to 2.7.0.1+ds1-2)
  • Migration status for python-cramjam (- to 2.7.0.1+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-cramjam would introduce bugs in testing: #1061310
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cramjam.html
    • autopkgtest for python-cramjam/2.7.0.1+ds1-2: amd64: Pass, arm64: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 44 days old (needed 2 days)
• rust-cradle (- to 0.2.2-3)
  • Migration status for rust-cradle (- to 0.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-cradle/0.2.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cradle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• sopel (- to 6.6.9-2.2)
  • Migration status for sopel (- to 6.6.9-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sopel would introduce bugs in testing: #943405
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sopel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• mailman-hyperkitty (- to 1.2.1-2)
  • Migration status for mailman-hyperkitty (- to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): mailman-hyperkitty mailman3
    • Depends: mailman-hyperkitty mailman3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman-hyperkitty.html
    • autopkgtest for mailman-hyperkitty/1.2.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 45 days old (needed 2 days)
• r-cran-future.apply (1.11.0+dfsg-1 to 1.11.1+dfsg-1)
  • Migration status for r-cran-future.apply (1.11.0+dfsg-1 to 1.11.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-future.apply/1.11.1+dfsg-1: 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, s390x: Test in progress
    • autopkgtest for r-cran-future.batchtools/0.12.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for r-cran-gstat/2.1-1-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress (will not be considered a regression)
    • autopkgtest for r-cran-lava/1.7.3+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for r-cran-pbapply/1.7-2-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for r-cran-progressr/0.14.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for r-cran-sctransform/0.4.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for r-cran-seurat/5.0.1-1: amd64: Pass, arm64: Pass, armel: Test in progress (will not be considered a regression), armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for r-cran-seuratobject/5.0.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
    • autopkgtest for r-cran-stars/0.6-4-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Test in progress, ppc64el: Test in progress, s390x: Test in progress
  • Additional info:
    • Updating r-cran-future.apply will fix bugs in testing: #1063431
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-future.apply.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 45 days old (needed 5 days)
• slic3r-prusa (- to 2.7.1+dfsg-1)
  • Migration status for slic3r-prusa (- to 2.7.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • slic3r-prusa unsatisfiable Build-Depends(-Arch) on s390x: libbgcode-dev
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for slic3r-prusa/2.7.1+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r-prusa.html
    • Reproducible on i386 - info ♻
    • 45 days old (needed 5 days)
• bioxtasraw (- to 2.2.1-2)
  • Migration status for bioxtasraw (- to 2.2.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): bioxtasraw silx (not considered)
    • Depends: bioxtasraw silx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): bioxtasraw numba
    • Build-Depends(-Arch): bioxtasraw pyfai
    • Depends: bioxtasraw numba
    • Depends: bioxtasraw pyfai
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bioxtasraw.html
    • autopkgtest for bioxtasraw/2.2.1-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
• iwyu (8.18-2 to 8.21-1)
  • Migration status for iwyu (8.18-2 to 8.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • iwyu unsatisfiable Build-Depends(-Arch) on mips64el: clang-17
    • iwyu unsatisfiable Build-Depends(-Arch) on mips64el: libclang-17-dev
    • iwyu unsatisfiable Build-Depends(-Arch) on mips64el: llvm-17-dev
    • missing build on mips64el
  • Additional info:
    • Updating iwyu will fix bugs in testing: #1063428
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iwyu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
• networking-sfc (- to 17.0.0-2)
  • Migration status for networking-sfc (- to 17.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for networking-sfc/17.0.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 47 days old (needed 5 days)
• node-websocket (1.0.34+~cs10.0.25-1 to 1.0.34+~cs10.0.25-2)
  • Migration status for node-websocket (1.0.34+~cs10.0.25-1 to 1.0.34+~cs10.0.25-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for node-websocket/1.0.34+~cs10.0.25-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating node-websocket will fix bugs in testing: #1063426
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-websocket.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
• packagesearch (- to 2.8.1)
  • Migration status for packagesearch (- to 2.8.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: packagesearch debtags (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packagesearch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
• python-loompy (- to 3.0.7+dfsg-3)
  • Migration status for python-loompy (- to 3.0.7+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-loompy numba (not considered)
    • Depends: python-loompy numba (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-loompy.html
    • autopkgtest for python-loompy/3.0.7+dfsg-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 47 days old (needed 2 days)
• apt-verify (- to 2.0-1)
  • Migration status for apt-verify (- to 2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-verify would introduce bugs in testing: #1061185
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - 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 ♻
    • 48 days old (needed 5 days)
• golang-github-darkhz-tview (- to 0.0~git20231221.b7c392e-1)
  • Migration status for golang-github-darkhz-tview (- to 0.0~git20231221.b7c392e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-darkhz-tview.html
    • autopkgtest for golang-github-darkhz-tview/0.0~git20231221.b7c392e-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• golang-github-davidmytton-url-verifier (- to 1.0.0-1)
  • Migration status for golang-github-davidmytton-url-verifier (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-davidmytton-url-verifier.html
    • autopkgtest for golang-github-davidmytton-url-verifier/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• golang-github-etherlabsio-go-m3u8 (- to 1.0.0-1)
  • Migration status for golang-github-etherlabsio-go-m3u8 (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-etherlabsio-go-m3u8.html
    • autopkgtest for golang-github-etherlabsio-go-m3u8/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• golang-github-gammazero-deque (- to 0.2.1-1)
  • Migration status for golang-github-gammazero-deque (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gammazero-deque.html
    • autopkgtest for golang-github-gammazero-deque/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• invidtui (- to 0.3.7-1)
  • Migration status for invidtui (- to 0.3.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): invidtui golang-github-gammazero-deque (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): invidtui golang-github-darkhz-mpvipc
    • Build-Depends(-Arch): invidtui golang-github-darkhz-tview
    • Build-Depends(-Arch): invidtui golang-github-davidmytton-url-verifier
    • Build-Depends(-Arch): invidtui golang-github-etherlabsio-go-m3u8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/invidtui.html
    • autopkgtest for invidtui/0.3.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• libfreemarker-java (2.3.31-2 to 2.3.32-1)
  • Migration status for libfreemarker-java (2.3.31-2 to 2.3.32-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libfreemarker-java would introduce bugs in testing: #1060940
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating libfreemarker-java will fix bugs in testing: #1063247
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfreemarker-java.html
    • 48 days old (needed 5 days)
• massxpert2 (- to 8.3.0-1)
  • Migration status for massxpert2 (- to 8.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by lopippo, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by lopippo
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/massxpert2.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 48 days old (needed 5 days)
• mes (- to 0.26-1)
  • Migration status for mes (- to 0.26-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/mes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• octave-vibes (- to 0.2.0-9)
  • Migration status for octave-vibes (- to 0.2.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-vibes would introduce bugs in testing: #1057591
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-vibes.html
    • autopkgtest for octave-vibes/0.2.0-9: 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
    • 48 days old (needed 2 days)
• picom-conf (- to 0.17.0-1)
  • Migration status for picom-conf (- to 0.17.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): picom-conf qtilitools (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picom-conf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 48 days old (needed 5 days)
• rust-tikv-jemalloc-sys (- to 0.5.4-1)
  • Migration status for rust-tikv-jemalloc-sys (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-tikv-jemalloc-sys would introduce bugs in testing: #1061102
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tikv-jemalloc-sys.html
    • autopkgtest for rust-tikv-jemalloc-sys/0.5.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• rust-tikv-jemallocator (- to 0.5.4-1)
  • Migration status for rust-tikv-jemallocator (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-tikv-jemallocator/0.5.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 ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-tikv-jemallocator rust-tikv-jemalloc-sys
    • Depends: rust-tikv-jemallocator rust-tikv-jemalloc-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tikv-jemallocator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• bluez-firmware (1.2-9 to 1.2-11)
  • Migration status for bluez-firmware (1.2-9 to 1.2-11): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 49 days old (needed 5 days)
• olive-editor (20221024+ds-1 to 20230614+ds-1)
  • Migration status for olive-editor (20221024+ds-1 to 20230614+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating olive-editor would introduce bugs in testing: #1060206
    • missing build on amd64
    • missing build on arm64
    • 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:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating olive-editor will fix bugs in testing: #1063075
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/olive-editor.html
    • 50 days old (needed 5 days)
• ruby-semver-dialects (1.2.1-2 to 1.5.0-1)
  • Migration status for ruby-semver-dialects (1.2.1-2 to 1.5.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-semver-dialects ruby-deb-version (not considered)
    • Depends: ruby-semver-dialects ruby-deb-version (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating ruby-semver-dialects will fix bugs in testing: #1063070
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-semver-dialects.html
    • autopkgtest for ruby-semver-dialects/1.5.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 50 days old (needed 5 days)
• mumble (1.3.4-4 to 1.5.517-1)
  • Migration status for mumble (1.3.4-4 to 1.5.517-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mumble/1.5.517-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 ♻)
    • Build-Depends(-Arch): mumble poco
    • Depends: mumble poco
  • Additional info:
    • Updating mumble will fix bugs in testing: #1062798
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mumble.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducibility regression on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
    • 51 days old (needed 5 days)
• ruby-deb-version (- to 1.0.2-1)
  • Migration status for ruby-deb-version (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-deb-version.html
    • autopkgtest for ruby-deb-version/1.0.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 51 days old (needed 5 days)
• rust-async-zip (- to 0.0.16-1)
  • Migration status for rust-async-zip (- to 0.0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-zip/0.0.16-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-zip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 51 days old (needed 5 days)
• numba (- to 0.58.1+dfsg-1)
  • Migration status for numba (- to 0.58.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating numba would introduce bugs in testing: #1033907
    • autopkgtest for numba/0.58.1+dfsg-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for numba/blocked-on-ci-infra: ppc64el: 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/n/numba.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 days old (needed 5 days)
• pytables (3.7.0-10 to 3.9.2-1)
  • Migration status for pytables (3.7.0-10 to 3.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pytables unsatisfiable Build-Depends(-Arch) on s390x: libblosc2-dev
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for pytables/3.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytables.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 days old (needed 5 days)
• yt-dlp (2023.11.16-1 to 2023.12.30-1)
  • Migration status for yt-dlp (2023.11.16-1 to 2023.12.30-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for yt-dlp/2023.12.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 ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating yt-dlp will fix bugs in testing: #1062797
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yt-dlp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 days old (needed 5 days)
• courier (- to 1.0.16-3.2)
  • Migration status for courier (- to 1.0.16-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating courier would introduce bugs in testing: #1000053
    • Build-Depends(-Arch): courier courier-authlib
    • Depends: courier courier-authlib
    • Depends: courier maildrop
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier.html
    • autopkgtest for courier/1.0.16-3.2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• mapclassify (- to 2.6.1-3)
  • Migration status for mapclassify (- to 2.6.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mapclassify would introduce bugs in testing: #1057383
    • Build-Depends(-Arch): mapclassify libpysal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mapclassify.html
    • autopkgtest for mapclassify/2.6.1-3: 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
    • 54 days old (needed 2 days)
• devicexlib (- to 0.8.2-1)
  • Migration status for devicexlib (- to 0.8.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devicexlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 55 days old (needed 5 days)
• gnucash (- to 1:5.5-1)
  • Migration status for gnucash (- to 1:5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating gnucash would introduce bugs in testing: #1061395
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnucash.html
    • 55 days old (needed 5 days)
    • Remove hint for (transitive) dependency: gnucash
• libgridxc (- to 2.0.1-1)
  • Migration status for libgridxc (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgridxc would introduce bugs in testing: #1055110
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgridxc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 55 days old (needed 5 days)
• odr-dabmux (- to 4.4.1+ds-1)
  • Migration status for odr-dabmux (- to 4.4.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating odr-dabmux would introduce bugs in testing: #1033126
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odr-dabmux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 57 days old (needed 5 days)
• lyskom-elisp-client (- to 0.48+git.20231226.364902c3-1)
  • Migration status for lyskom-elisp-client (- to 0.48+git.20231226.364902c3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lyskom-elisp-client would introduce bugs in testing: #1058739
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/l/lyskom-elisp-client.html
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • 58 days old (needed 5 days)
• rust-secret-service (- to 3.0.1-1)
  • Migration status for rust-secret-service (- to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-secret-service-dev/amd64 has unsatisfiable dependency
    • librust-secret-service-dev/arm64 has unsatisfiable dependency
    • librust-secret-service-dev/armel has unsatisfiable dependency
    • librust-secret-service-dev/armhf has unsatisfiable dependency
    • librust-secret-service-dev/i386 has unsatisfiable dependency
    • librust-secret-service-dev/mips64el has unsatisfiable dependency
    • librust-secret-service-dev/ppc64el has unsatisfiable dependency
    • librust-secret-service-dev/s390x has unsatisfiable dependency
    • Updating rust-secret-service would introduce bugs in testing: #1060321
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-secret-service.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 59 days old (needed 5 days)
• magit-forge-el (- to 0.3.2-2)
  • Migration status for magit-forge-el (- to 0.3.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): magit-forge-el closql-el (not considered)
    • Depends: magit-forge-el closql-el (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magit-forge-el.html
    • autopkgtest for magit-forge-el/0.3.2-2: 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
    • 61 days old (needed 2 days)
• ruby-arr-pm (- to 0.0.12-1)
  • Migration status for ruby-arr-pm (- to 0.0.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-arr-pm/0.0.12-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): ruby-arr-pm ruby-flores
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-arr-pm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 61 days old (needed 5 days)
• ruby-flores (- to 0.0.8-1)
  • Migration status for ruby-flores (- to 0.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-flores.html
    • autopkgtest for ruby-flores/0.0.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 61 days old (needed 2 days)
• bfh-metapackages (- to 20211009-24)
  • Migration status for bfh-metapackages (- to 20211009-24): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bfh-metapackages netdata (not considered)
    • Invalidated by dependency
    • Depends: bfh-metapackages gnome-shell-extension-bluetooth-quick-connect
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bfh-metapackages.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• fprintd (- to 1.94.2-3)
  • Migration status for fprintd (- to 1.94.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): fprintd libfprint (not considered)
    • Depends: fprintd libfprint (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fprintd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• golang-github-cronokirby-saferith (- to 0.33.0-2)
  • Migration status for golang-github-cronokirby-saferith (- to 0.33.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-cronokirby-saferith/0.33.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-cronokirby-saferith.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• golang-github-henrybear327-go-proton-api (- to 1.0.0-3)
  • Migration status for golang-github-henrybear327-go-proton-api (- to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-henrybear327-go-proton-api/1.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-henrybear327-go-proton-api golang-github-protonmail-gluon
    • Build-Depends(-Arch): golang-github-henrybear327-go-proton-api golang-github-protonmail-go-srp
    • Depends: golang-github-henrybear327-go-proton-api golang-github-protonmail-gluon
    • Depends: golang-github-henrybear327-go-proton-api golang-github-protonmail-go-srp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-henrybear327-go-proton-api.html
    • 62 days old (needed 5 days)
• golang-github-henrybear327-proton-api-bridge (- to 1.0.0-2)
  • Migration status for golang-github-henrybear327-proton-api-bridge (- to 1.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-henrybear327-proton-api-bridge/1.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-henrybear327-proton-api-bridge golang-github-henrybear327-go-proton-api
    • Build-Depends(-Arch): golang-github-henrybear327-proton-api-bridge golang-github-protonmail-gluon
    • Depends: golang-github-henrybear327-proton-api-bridge golang-github-henrybear327-go-proton-api
    • Depends: golang-github-henrybear327-proton-api-bridge golang-github-protonmail-gluon
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-henrybear327-proton-api-bridge.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• golang-github-protonmail-gluon (- to 0.17.0-2)
  • Migration status for golang-github-protonmail-gluon (- to 0.17.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-protonmail-gluon/0.17.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-protonmail-gluon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 62 days old (needed 5 days)
• golang-github-protonmail-go-srp (- to 0.0.7+ds-2)
  • Migration status for golang-github-protonmail-go-srp (- to 0.0.7+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-protonmail-go-srp/0.0.7+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-protonmail-go-srp golang-github-cronokirby-saferith
    • Depends: golang-github-protonmail-go-srp golang-github-cronokirby-saferith
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-protonmail-go-srp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• progress-linux-metapackages (- to 20221002-12)
  • Migration status for progress-linux-metapackages (- to 20221002-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: progress-linux-metapackages netdata (not considered)
    • Invalidated by dependency
    • Depends: progress-linux-metapackages gnome-shell-extension-bluetooth-quick-connect
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/progress-linux-metapackages.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• qtilitools (- to 0.1.2-1)
  • Migration status for qtilitools (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtilitools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• ohcount (- to 4.0.0-4)
  • Migration status for ohcount (- to 4.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ohcount would introduce bugs in testing: #1051900
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ohcount.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 63 days old (needed 5 days)
• nitime (0.10.2-1 to 0.10.2-2)
  • Migration status for nitime (0.10.2-1 to 0.10.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nitime/0.10.2-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating nitime will fix bugs in testing: #1061233
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nitime.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 64 days old (needed 5 days)
• rust-heed (- to 0.20.0~alpha.9-1)
  • Migration status for rust-heed (- to 0.20.0~alpha.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-heed/0.20.0~alpha.9-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-heed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 65 days old (needed 5 days)
• freecad (- to 0.21.2+dfsg1-1)
  • Migration status for freecad (- to 0.21.2+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for freecad/0.21.2+dfsg1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freecad.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 66 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)
    • 66 days old (needed 5 days)
• openvas-scanner (- to 22.7.9-1)
  • Migration status for openvas-scanner (- to 22.7.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openvas-scanner gvm-libs (not considered)
    • Depends: openvas-scanner gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvas-scanner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 66 days old (needed 5 days)
• rust-scraper (- to 0.18.1-1)
  • Migration status for rust-scraper (- to 0.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-scraper-dev/amd64 has unsatisfiable dependency
    • Updating rust-scraper would introduce bugs in testing: #1059034
    • rust-scraper unsatisfiable Build-Depends(-Arch) on amd64: librust-ego-tree-0.6+default-dev (>= 0.6.2-~~)
    • Not built on buildd: arch amd64 binaries uploaded by jelmer
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-scraper.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 ♻
    • 66 days old (needed 5 days)
• xraylarch (- to 0.9.74+ds1-1)
  • Migration status for xraylarch (- to 0.9.74+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xraylarch silx (not considered)
    • Depends: xraylarch silx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): xraylarch pyfai
    • Build-Depends(-Arch): xraylarch python-pyepics
    • Depends: xraylarch pyfai
    • Depends: xraylarch python-pyepics
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xraylarch.html
    • autopkgtest for xraylarch/0.9.74+ds1-1: amd64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 66 days old (needed 2 days)
• hurd (- to 1:0.9.git20231217-1)
  • Migration status for hurd (- to 1:0.9.git20231217-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hurd would introduce bugs in testing: #650080, #838244, #943307
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libc0.3-dev (>= 2.33-2~1)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-disk-dev (>= 0~20211031-2)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-usb-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libacpica-dev
    • Not built on buildd: arch all binaries uploaded by sthibault, a new source-only upload is needed to allow migration
    • Not touching package due to block request by freeze (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hurd.html
    • 67 days old (needed 5 days)
• appstream-generator (- to 0.9.1-1)
  • Migration status for appstream-generator (- to 0.9.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Depends: appstream-generator glib-d
    • Depends: appstream-generator ldc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appstream-generator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 68 days old (needed 5 days)
• bpfcc (0.26.0+ds-1 to 0.29.1+ds-1)
  • Migration status for bpfcc (0.26.0+ds-1 to 0.29.1+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Updating bpfcc will fix bugs in testing: #1061086
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpfcc.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 68 days old (needed 5 days)
• python-pyaml-env (- to 1.2.1-1)
  • Migration status for python-pyaml-env (- to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyaml-env.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 68 days old (needed 5 days)
• pyferret (- to 7.6.5-5)
  • Migration status for pyferret (- to 7.6.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyferret would introduce bugs in testing: #1058888
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for pyferret/7.6.5-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): pyferret python-future
    • Depends: pyferret python-future
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyferret.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 70 days old (needed 5 days)
• pyfuse3 (- to 3.3.0-0.1)
  • Migration status for pyfuse3 (- to 3.3.0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfuse3 would introduce bugs in testing: #1056834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfuse3.html
    • autopkgtest for pyfuse3/3.3.0-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 71 days old (needed 2 days)
• pytorch-sparse (- to 0.6.18-2)
  • Migration status for pytorch-sparse (- to 0.6.18-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pytorch-sparse pytorch (not considered)
    • Depends: pytorch-sparse pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): pytorch-sparse pytorch-scatter
    • Depends: pytorch-sparse pytorch-scatter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-sparse.html
    • autopkgtest for pytorch-sparse/0.6.18-2: amd64: Pass, arm64: Pass, ppc64el: 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
    • 71 days old (needed 2 days)
• sahara-plugin-spark (- to 10.0.0-2)
  • Migration status for sahara-plugin-spark (- to 10.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: sahara-plugin-spark sahara (not considered)
    • Depends: sahara-plugin-spark sahara (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sahara-plugin-spark.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 71 days old (needed 5 days)
• terminado (0.17.1-1 to 0.18.0-1)
  • Migration status for terminado (0.17.1-1 to 0.18.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for terminado/0.18.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: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating terminado will fix bugs in testing: #1060780
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/terminado.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 71 days old (needed 5 days)
• cinder (- to 2:23.0.0-4)
  • Migration status for cinder (- to 2:23.0.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: cinder thin-provisioning-tools (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cinder.html
    • autopkgtest for cinder/2:23.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: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• fapolicyd (- to 1.3.2+20231212+git973a86d1b4-1)
  • Migration status for fapolicyd (- to 1.3.2+20231212+git973a86d1b4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fapolicyd would introduce bugs in testing: #1037547
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fapolicyd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• i2pd (- to 2.49.0-1)
  • Migration status for i2pd (- to 2.49.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating i2pd would introduce bugs in testing: #1060787
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i2pd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• pytorch-scatter (- to 2.1.2-1)
  • Migration status for pytorch-scatter (- to 2.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): pytorch-scatter pytorch (not considered)
    • Depends: pytorch-scatter pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-scatter.html
    • autopkgtest for pytorch-scatter/2.1.2-1: amd64: Pass, arm64: Pass, ppc64el: 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
    • 72 days old (needed 2 days)
• takari-polyglot-maven (- to 0.4.11-3)
  • Migration status for takari-polyglot-maven (- to 0.4.11-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): takari-polyglot-maven jruby (not considered)
    • Depends: takari-polyglot-maven jruby (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): takari-polyglot-maven jruby-maven-plugins
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/takari-polyglot-maven.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• vitrage (- to 11.0.0-2)
  • Migration status for vitrage (- to 11.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vitrage would introduce bugs in testing: #1060311
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vitrage.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• hg-git (- to 1.0.3-1)
  • Migration status for hg-git (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hg-git would introduce bugs in testing: #1058538
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hg-git.html
    • autopkgtest for hg-git/1.0.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 73 days old (needed 2 days)
• pyranges (- to 0.0.111+ds-6)
  • Migration status for pyranges (- to 0.0.111+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyranges would introduce bugs in testing: #1044064
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pyranges.html
    • autopkgtest for pyranges/0.0.111+ds-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 73 days old (needed 5 days)
• python-epimodels (- to 0.4.0-2)
  • Migration status for python-epimodels (- 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): python-epimodels numba (not considered)
    • Depends: python-epimodels numba (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-epimodels.html
    • autopkgtest for python-epimodels/0.4.0-2: 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
    • 73 days old (needed 2 days)
• pytorch-cluster (- to 1.6.3-1)
  • Migration status for pytorch-cluster (- to 1.6.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pytorch-cluster pytorch (not considered)
    • Depends: pytorch-cluster pytorch (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/p/pytorch-cluster.html
    • autopkgtest for pytorch-cluster/1.6.3-1: amd64: Pass, arm64: Pass, ppc64el: 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
    • 73 days old (needed 2 days)
• pytorch-geometric (- to 2.4.0-1)
  • Migration status for pytorch-geometric (- to 2.4.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(-Arch): pytorch-geometric pytorch
    • Build-Depends(-Arch): pytorch-geometric pytorch-cluster
    • Build-Depends(-Arch): pytorch-geometric pytorch-sparse
  • 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 ♻
    • 73 days old (needed 5 days)
• pandoc-sidenote (- to 0.23.0-1)
  • Migration status for pandoc-sidenote (- to 0.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pandoc-sidenote would introduce bugs in testing: #1055980
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pandoc-sidenote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• clojure-mode (- to 5.18.1-1)
  • Migration status for clojure-mode (- to 5.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for clojure-mode/5.18.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clojure-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 75 days old (needed 5 days)
• gitit (- to 0.15.1.1+dfsg-1)
  • Migration status for gitit (- to 0.15.1.1+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gitit haskell-hoauth2 (not considered)
    • Build-Depends-Indep: gitit haskell-hoauth2 (not considered)
    • Depends: gitit haskell-hoauth2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 75 days old (needed 5 days)
• maradns (- to 2.0.13-1.6)
  • Migration status for maradns (- to 2.0.13-1.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating maradns would introduce bugs in testing: #1024561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/maradns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 75 days old (needed 5 days)
• mintpy (- to 1.5.3-2)
  • Migration status for mintpy (- to 1.5.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mintpy/1.5.3-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): mintpy pyfftw
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mintpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 75 days old (needed 5 days)
• scanbd (- to 1.5.1-7)
  • Migration status for scanbd (- to 1.5.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scanbd would introduce bugs in testing: #1058749
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scanbd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 75 days old (needed 5 days)
• jruby-mavengem (- to 2.0.1-1)
  • Migration status for jruby-mavengem (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by lavamind, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): jruby-mavengem jruby
    • Build-Depends(-Arch): jruby-mavengem jruby-maven-plugins
    • Depends: jruby-mavengem jruby
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby-mavengem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 days old (needed 5 days)
• trafficserver (- to 9.2.3+ds-1+deb12u1)
  • Migration status for trafficserver (- to 9.2.3+ds-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trafficserver would introduce bugs in testing: #999938
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trafficserver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 76 days old (needed 5 days)
• php-symfony-mercure-bundle (- to 0.3.8-1)
  • Migration status for php-symfony-mercure-bundle (- to 0.3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-symfony-mercure-bundle php-lcobucci-jwt (not considered)
    • Depends: php-symfony-mercure-bundle php-lcobucci-jwt (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-symfony-mercure-bundle.html
    • autopkgtest for php-symfony-mercure-bundle/0.3.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 77 days old (needed 2 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 78 days old (needed 5 days)
• python-array-api-compat (- to 1.4-1)
  • Migration status for python-array-api-compat (- to 1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): python-array-api-compat pytorch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-array-api-compat.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 80 days old (needed 5 days)
• eric (- to 23.2+ds1-2)
  • Migration status for eric (- to 23.2+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: eric sip4 (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eric.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 81 days old (needed 5 days)
• circlator (- to 1.5.6-11)
  • Migration status for circlator (- to 1.5.6-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): circlator canu (not considered)
    • Depends: circlator canu (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/circlator.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for circlator/1.5.6-11: amd64: Pass, arm64: Pass, ppc64el: Pass
    • 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
    • 82 days old (needed 2 days)
• mkdocstrings-python-legacy (- to 0.2.3-6)
  • Migration status for mkdocstrings-python-legacy (- to 0.2.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mkdocstrings-python-legacy would introduce bugs in testing: #1058372
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkdocstrings-python-legacy.html
    • autopkgtest for mkdocstrings-python-legacy/0.2.3-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 82 days old (needed 2 days)
• openmolcas (- to 23.10-1)
  • Migration status for openmolcas (- to 23.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for openmolcas/23.10-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmolcas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 82 days old (needed 5 days)
• r-bioc-tcgabiolinks (- to 2.30.0+dfsg-1)
  • Migration status for r-bioc-tcgabiolinks (- to 2.30.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-tcgabiolinks/2.30.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tcgabiolinks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 84 days old (needed 5 days)
• ruby-psych (- to 5.0.2-2)
  • Migration status for ruby-psych (- to 5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-psych jruby (not considered)
    • Depends: ruby-psych jruby (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-psych.html
    • autopkgtest for ruby-psych/5.0.2-2: 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
    • 85 days old (needed 2 days)
• django-invitations (- to 2.1.0-1)
  • Migration status for django-invitations (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-invitations would introduce bugs in testing: #1058663
    • autopkgtest for django-invitations/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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-invitations.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 87 days old (needed 5 days)
• gammapy (- to 1.1-3)
  • Migration status for gammapy (- to 1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gammapy would introduce bugs in testing: #1058047
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gammapy.html
    • autopkgtest for gammapy/1.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 87 days old (needed 2 days)
• pplpy (- to 0.8.9-1)
  • Migration status for pplpy (- to 0.8.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pplpy would introduce bugs in testing: #1056832
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplpy.html
    • autopkgtest for pplpy/0.8.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 87 days old (needed 2 days)
• python-fastparquet (- to 2023.10.1-2)
  • Migration status for python-fastparquet (- to 2023.10.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-fastparquet would introduce bugs in testing: #1063598
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): python-fastparquet python-cramjam
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fastparquet.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 87 days old (needed 5 days)
• ifscheme (- to 1.7-8)
  • Migration status for ifscheme (- to 1.7-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ifscheme would introduce bugs in testing: #981637
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifscheme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 88 days old (needed 5 days)
• jruby-maven-plugins (- to 3.0.1-2)
  • Migration status for jruby-maven-plugins (- to 3.0.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): jruby-maven-plugins jruby (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby-maven-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 88 days old (needed 5 days)
• python-html-sanitizer (- to 2.2-1)
  • Migration status for python-html-sanitizer (- to 2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-html-sanitizer would introduce bugs in testing: #1008366
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-html-sanitizer.html
    • autopkgtest for python-html-sanitizer/2.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 88 days old (needed 5 days)
• python-jsonschema-specifications (- to 2023.11.1-2)
  • Migration status for python-jsonschema-specifications (- to 2023.11.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends-Indep: python-jsonschema-specifications rpds-py (not considered)
    • Depends: python-jsonschema-specifications rpds-py (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends-Indep: python-jsonschema-specifications referencing
    • Depends: python-jsonschema-specifications referencing
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jsonschema-specifications.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 88 days old (needed 5 days)
• lsp-mode (- to 8.0.0-6)
  • Migration status for lsp-mode (- to 8.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lsp-mode would introduce bugs in testing: #1052939
    • autopkgtest for lsp-mode/8.0.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsp-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 89 days old (needed 5 days)
• gvm (- to 23.11.1)
  • Migration status for gvm (- to 23.11.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gvm openvas-scanner (not considered)
    • Invalidated by dependency
    • Depends: gvm gsad
    • Depends: gvm gvmd
    • Depends: gvm ospd-openvas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• ccextractor (- to 0.94+ds1-3)
  • Migration status for ccextractor (- to 0.94+ds1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ccextractor gpac (not considered)
    • Depends: ccextractor gpac (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccextractor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 91 days old (needed 5 days)
• mysql-workbench (- to 8.0.32+dfsg-2)
  • Migration status for mysql-workbench (- to 8.0.32+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-workbench would introduce bugs in testing: #1000093
    • Depends: mysql-workbench mysql-connector-python
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-workbench.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 91 days old (needed 5 days)
• python-django-ratelimit (- to 4.1.0-1)
  • Migration status for python-django-ratelimit (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ratelimit.html
    • autopkgtest for python-django-ratelimit/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 91 days old (needed 2 days)
• rust-datasize (- to 0.2.13-1)
  • Migration status for rust-datasize (- to 0.2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-datasize/0.2.13-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-datasize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 91 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-wikibase-cli.html
    • autopkgtest for node-wikibase-cli/15.15.4-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 92 days old (needed 2 days)
• gvm-tools (- to 23.11.0-1)
  • Migration status for gvm-tools (- to 23.11.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gvm-tools python-gvm (not considered)
    • Depends: gvm-tools python-gvm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm-tools.html
    • autopkgtest for gvm-tools/23.11.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 93 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-450 (- to 450.248.02-4)
  • Migration status for nvidia-graphics-drivers-tesla-450 (- to 450.248.02-4): 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-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • 93 days old (needed 5 days)
• gsad (- to 22.8.0-1)
  • Migration status for gsad (- to 22.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gsad gvm-libs (not considered)
    • Depends: gsad gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: gsad gvmd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsad.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 94 days old (needed 5 days)
• gvm-libs (- to 22.7.3-1)
  • Migration status for gvm-libs (- to 22.7.3-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 ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 94 days old (needed 5 days)
• gvmd (- to 23.1.0-1)
  • Migration status for gvmd (- to 23.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): gvmd gvm-libs (not considered)
    • Depends: gvmd gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: gvmd greenbone-feed-sync
    • Depends: gvmd ospd-openvas
    • Depends: gvmd pg-gvm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvmd.html
    • autopkgtest for gvmd/23.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 94 days old (needed 2 days)
• ospd-openvas (- to 22.6.2-1)
  • Migration status for ospd-openvas (- to 22.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ospd-openvas openvas-scanner (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ospd-openvas.html
    • autopkgtest for ospd-openvas/22.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 94 days old (needed 2 days)
• php-lcobucci-jwt (- to 5.2.0-1)
  • Migration status for php-lcobucci-jwt (- to 5.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): php-lcobucci-jwt php-lcobucci-clock (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-lcobucci-jwt.html
    • autopkgtest for php-lcobucci-jwt/5.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 94 days old (needed 2 days)
• pontos (- to 23.11.4-1)
  • Migration status for pontos (- to 23.11.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pontos would introduce bugs in testing: #1056447
    • Build-Depends(-Arch): pontos python-colorful
    • Depends: pontos python-colorful
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pontos.html
    • autopkgtest for pontos/23.11.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 94 days old (needed 2 days)
• python-gvm (- to 23.11.0-1)
  • Migration status for python-gvm (- to 23.11.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-gvm pontos (not considered)
    • Invalidated by build-dependency
    • Depends: python-gvm gvmd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gvm.html
    • autopkgtest for python-gvm/23.11.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 94 days old (needed 5 days)
• virtuoso-opensource (- to 7.2.5.1+dfsg1-0.5)
  • Migration status for virtuoso-opensource (- to 7.2.5.1+dfsg1-0.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtuoso-opensource would introduce bugs in testing: #1036467, #999931
  • 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
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 94 days old (needed 5 days)
• golang-github-jamesruan-go-rfc1924 (- to 0.0~git20170108.2767ca7-1)
  • Migration status for golang-github-jamesruan-go-rfc1924 (- to 0.0~git20170108.2767ca7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jamesruan-go-rfc1924.html
    • autopkgtest for golang-github-jamesruan-go-rfc1924/0.0~git20170108.2767ca7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 95 days old (needed 2 days)
• python-django-celery-results (- to 2.5.1-2)
  • Migration status for python-django-celery-results (- to 2.5.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-django-celery-results celery (not considered)
    • Depends: python-django-celery-results celery (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-celery-results.html
    • autopkgtest for python-django-celery-results/2.5.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 95 days old (needed 2 days)
• ruby-rspec-parameterized-core (- to 1.0.0-1)
  • Migration status for ruby-rspec-parameterized-core (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-core.html
    • autopkgtest for ruby-rspec-parameterized-core/1.0.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 days old (needed 5 days)
• ruby-rspec-parameterized-table-syntax (- to 1.0.1-1)
  • Migration status for ruby-rspec-parameterized-table-syntax (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core
    • Depends: ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-table-syntax.html
    • autopkgtest for ruby-rspec-parameterized-table-syntax/1.0.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 days old (needed 5 days)
• rust-subversion (- to 0.0.3-1)
  • Migration status for rust-subversion (- to 0.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-subversion/0.0.3-1: amd64: Regression or new test ♻
    • Not built on buildd: arch amd64 binaries uploaded by jelmer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-subversion.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 95 days old (needed 5 days)
• python3-onelogin-saml2 (- to 1.12.0-3)
  • Migration status for python3-onelogin-saml2 (- to 1.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python3-onelogin-saml2 would introduce bugs in testing: #1056196
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3-onelogin-saml2.html
    • Reproducible on armhf - info ♻
    • 97 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 ♻
    • 98 days old (needed 5 days)
• python-django-celery-beat (- to 2.5.0-2)
  • Migration status for python-django-celery-beat (- to 2.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-django-celery-beat celery (not considered)
    • Depends: python-django-celery-beat celery (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-celery-beat.html
    • autopkgtest for python-django-celery-beat/2.5.0-2: 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
    • 98 days old (needed 2 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
    • autopkgtest for jupyter-ydoc/1.0.2-2: amd64: Pass
    • Build-Depends(-Arch): jupyter-ydoc ypy
    • Depends: jupyter-ydoc ypy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-ydoc.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 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 ♻
    • 99 days old (needed 5 days)
• pwntools (- to 4.11.1-1)
  • Migration status for pwntools (- to 4.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): pwntools ropgadget (not considered)
    • Depends: pwntools ropgadget (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pwntools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 99 days old (needed 5 days)
• referencing (- to 0.31.0-1)
  • Migration status for referencing (- to 0.31.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): referencing rpds-py (not considered)
    • Depends: referencing rpds-py (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/referencing.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 99 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:
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-lib0-dev
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-yrs-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 99 days old (needed 5 days)
• jupyter-events (- to 0.9.0-2)
  • Migration status for jupyter-events (- to 0.9.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: jupyter-events referencing (not considered)
    • Invalidated by dependency
    • Depends: jupyter-events python-jsonschema
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-events.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 101 days old (needed 5 days)
• obs-time-source (- to 0.2-3)
  • Migration status for obs-time-source (- to 0.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-time-source obs-studio (not considered)
    • Depends: obs-time-source obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-time-source.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 101 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 s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 101 days old (needed 5 days)
• cp2k (- to 2023.2-2)
  • Migration status for cp2k (- to 2023.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cp2k would introduce bugs in testing: #1060949
    • autopkgtest for cp2k/2023.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for cp2k/blocked-on-ci-infra: armel: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cp2k.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 102 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-340xx (- to 340.108-21)
  • Migration status for nvidia-graphics-drivers-legacy-340xx (- to 340.108-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-340xx would introduce bugs in testing: #1004848, #1011141, #1016615, #1025280, #1033775, #1039679, #1055137, #973599, #979671, #987217, #991352
    • autopkgtest for nvidia-graphics-drivers-legacy-340xx/340.108-21: amd64: No tests, superficial or marked flaky ♻, armhf: Regression or new test ♻, i386: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 102 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-390xx (- to 390.157-6)
  • Migration status for nvidia-graphics-drivers-legacy-390xx (- to 390.157-6): 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
    • Depends: nvidia-graphics-drivers-legacy-390xx nvidia-graphics-drivers-tesla-418
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-legacy-390xx/390.157-6: amd64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 102 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-418 (- to 418.226.00-13)
  • Migration status for nvidia-graphics-drivers-tesla-418 (- to 418.226.00-13): 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
    • autopkgtest for nvidia-graphics-drivers-tesla-418/418.226.00-13: 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
    • 102 days old (needed 5 days)
• dxvk (- to 2.3-1)
  • Migration status for dxvk (- to 2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dxvk/arm64 has unsatisfiable dependency
    • Updating dxvk would introduce bugs in testing: #982159
    • autopkgtest for dxvk/2.3-1: amd64: Regression or new test ♻, i386: Regression or new test ♻
    • Build-Depends(-Arch): dxvk wine-development
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dxvk.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 105 days old (needed 5 days)
• obs-ashmanix-blur-filter (- to 1.0.1-2)
  • Migration status for obs-ashmanix-blur-filter (- to 1.0.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-ashmanix-blur-filter obs-studio (not considered)
    • Depends: obs-ashmanix-blur-filter obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-ashmanix-blur-filter.html
    • autopkgtest for obs-ashmanix-blur-filter/1.0.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 105 days old (needed 5 days)
• django-assets (- to 2.0-3)
  • Migration status for django-assets (- to 2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-assets would introduce bugs in testing: #1056243, #1056288
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-assets.html
    • 106 days old (needed 5 days)
• obs-downstream-keyer (- to 0.2.7-2)
  • Migration status for obs-downstream-keyer (- to 0.2.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-downstream-keyer would introduce bugs in testing: #1060976
    • Build-Depends(-Arch): obs-downstream-keyer obs-studio
    • Depends: obs-downstream-keyer obs-studio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-downstream-keyer.html
    • autopkgtest for obs-downstream-keyer/0.2.7-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• obs-move-transition (- to 2.9.6-1)
  • Migration status for obs-move-transition (- to 2.9.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-move-transition obs-studio (not considered)
    • Depends: obs-move-transition obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-move-transition.html
    • autopkgtest for obs-move-transition/2.9.6-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• obs-scene-notes-dock (- to 0.2.0-2)
  • Migration status for obs-scene-notes-dock (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-scene-notes-dock would introduce bugs in testing: #1060974
    • Build-Depends(-Arch): obs-scene-notes-dock obs-studio
    • Depends: obs-scene-notes-dock obs-studio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-scene-notes-dock.html
    • autopkgtest for obs-scene-notes-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 ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• obs-transition-table (- to 0.2.7-1)
  • Migration status for obs-transition-table (- to 0.2.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-transition-table obs-studio (not considered)
    • Depends: obs-transition-table obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-transition-table.html
    • autopkgtest for obs-transition-table/0.2.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• placement (- to 10.0.0-3)
  • Migration status for placement (- to 10.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: placement sphinxcontrib-actdiag (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/placement.html
    • autopkgtest for placement/10.0.0-3: 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
    • 106 days old (needed 2 days)
• r10k (- to 4.0.0-1)
  • Migration status for r10k (- to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r10k/4.0.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r10k.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): umap-learn python-pynndescent (not considered)
    • Depends: umap-learn python-pynndescent (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): umap-learn numba
    • Depends: umap-learn numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umap-learn.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for umap-learn/0.5.4+dfsg-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 106 days old (needed 5 days)
• linuxcnc (- to 2.9.1-2)
  • Migration status for linuxcnc (- to 2.9.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating linuxcnc would introduce bugs in testing: #1055493
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/l/linuxcnc.html
  • Additional info:
    • autopkgtest for linuxcnc/2.9.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • 108 days old (needed 2 days)
• networking-l2gw (- to 1:20.0.0-1)
  • Migration status for networking-l2gw (- to 1:20.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for networking-l2gw/1:20.0.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-l2gw.html
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 108 days old (needed 5 days)
• octave-ltfat (- to 2.6.0+dfsg-6)
  • Migration status for octave-ltfat (- to 2.6.0+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for octave-ltfat/2.6.0+dfsg-6: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-ltfat.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 108 days old (needed 5 days)
• gnupg-pkcs11-scd (- to 0.10.0-3)
  • Migration status for gnupg-pkcs11-scd (- to 0.10.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnupg-pkcs11-scd would introduce bugs in testing: #952735
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnupg-pkcs11-scd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 109 days old (needed 5 days)
• spaghetti (- to 1.7.4-3)
  • Migration status for spaghetti (- to 1.7.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spaghetti would introduce bugs in testing: #1054759
    • Build-Depends(-Arch): spaghetti esda
    • Build-Depends(-Arch): spaghetti libpysal
    • Depends: spaghetti esda
    • Depends: spaghetti libpysal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spaghetti.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 109 days old (needed 5 days)
• pdudaemon (- to 0.0.8.81.gaa63a79-1)
  • Migration status for pdudaemon (- to 0.0.8.81.gaa63a79-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdudaemon would introduce bugs in testing: #1058396, #1060768
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdudaemon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 110 days old (needed 5 days)
• python-django-ca (- to 1.25.0-2)
  • Migration status for python-django-ca (- to 1.25.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-django-ca/1.25.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): python-django-ca celery
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ca.html
    • Reproducible on amd64 - info ♻
    • 110 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
    • Reproducible on armhf - info ♻
    • 110 days old (needed 5 days)
• genomicsdb (- to 1.5.0-2)
  • Migration status for genomicsdb (- to 1.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libgenomicsdb-java/arm64 has unsatisfiable dependency
    • autopkgtest for genomicsdb/1.5.0-2: amd64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genomicsdb.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 111 days old (needed 5 days)
• spopt (- to 0.5.0-4)
  • Migration status for spopt (- to 0.5.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spopt would introduce bugs in testing: #1054780
    • autopkgtest for spopt/0.5.0-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): spopt libpysal
    • Build-Depends(-Arch): spopt mapclassify
    • Build-Depends(-Arch): spopt numba
    • Build-Depends(-Arch): spopt spaghetti
    • Depends: spopt libpysal
    • Depends: spopt spaghetti
  • 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 ♻
    • 111 days old (needed 5 days)
• lintian-brush (- to 0.152)
  • Migration status for lintian-brush (- to 0.152): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lintian-brush would introduce bugs in testing: #1058640, #1061435
    • Build-Depends(-Arch): lintian-brush ognibuild
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lintian-brush.html
    • autopkgtest for lintian-brush/0.152: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 113 days old (needed 2 days)
• netdata (- to 1.43.2-1)
  • Migration status for netdata (- to 1.43.2-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 ♻
    • 114 days old (needed 5 days)
• celery (- to 5.3.4-2)
  • Migration status for celery (- to 5.3.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating celery would introduce bugs in testing: #1056232, #1058317
    • Build-Depends(-Arch): celery python-future
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/celery.html
    • autopkgtest for celery/5.3.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 115 days old (needed 2 days)
• gxneur (- to 0.20.0-2.2)
  • Migration status for gxneur (- to 0.20.0-2.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gxneur xneur (not considered)
    • Depends: gxneur xneur (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gxneur.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 115 days old (needed 5 days)
• rust-imperative (- to 1.0.5-1)
  • Migration status for rust-imperative (- to 1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-imperative-dev/amd64 has unsatisfiable dependency
    • rust-imperative unsatisfiable Build-Depends(-Arch) on amd64: librust-rust-stemmers-1+default-dev (>= 1.2.0-~~)
    • Not built on buildd: arch amd64 binaries uploaded by jelmer
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-imperative.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 115 days old (needed 5 days)
• guerillabackup (- to 0.5.0-1)
  • Migration status for guerillabackup (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guerillabackup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 119 days old (needed 5 days)
• haskell-hledger-web (- to 1.30-1)
  • Migration status for haskell-hledger-web (- to 1.30-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-hledger-web haskell-base64 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hledger-web.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 119 days old (needed 5 days)
• vecgeom (- to 1.2.5+dfsg-1)
  • Migration status for vecgeom (- to 1.2.5+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vecgeom would introduce bugs in testing: #1063044
    • Impossible Depends: vecgeom -> libembree3-3/3.13.5+dfsg-2/amd64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vecgeom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 119 days old (needed 5 days)
• dogecoin (- to 1.14.6-4)
  • Migration status for dogecoin (- to 1.14.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dogecoin would introduce bugs in testing: #1034806, #1059133
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dogecoin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 120 days old (needed 5 days)
• libpsml (- to 2.0.1-1)
  • Migration status for libpsml (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libpsml-dev/amd64 has unsatisfiable dependency
    • libpsml unsatisfiable Build-Depends(-Arch) on amd64: libxmlf90-dev
    • Not built on buildd: arch amd64 binaries uploaded by mbanck
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libp/libpsml.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 120 days old (needed 5 days)
• python-certbot-dns-gandi (- to 1.4.3-2)
  • Migration status for python-certbot-dns-gandi (- to 1.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-certbot-dns-gandi would introduce bugs in testing: #1038920
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-gandi.html
    • autopkgtest for python-certbot-dns-gandi/1.4.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 120 days old (needed 2 days)
• greenbone-feed-sync (- to 23.10.0-1)
  • Migration status for greenbone-feed-sync (- to 23.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sophieb, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): greenbone-feed-sync pontos
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/greenbone-feed-sync.html
    • autopkgtest for greenbone-feed-sync/23.10.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 121 days old (needed 5 days)
• haskell-hoauth2 (- to 2.8.0-1)
  • Migration status for haskell-hoauth2 (- to 2.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-hoauth2 haskell-base64 (not considered)
    • Build-Depends-Indep: haskell-hoauth2 haskell-base64 (not considered)
    • Depends: haskell-hoauth2 haskell-base64 (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hoauth2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 121 days old (needed 5 days)
• orange-spectroscopy (- to 0.6.10-4)
  • Migration status for orange-spectroscopy (- to 0.6.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orange-spectroscopy/0.6.10-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
    • Depends: orange-spectroscopy orange3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange-spectroscopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 121 days old (needed 5 days)
• orange3 (- to 3.35.0+ds1-5)
  • Migration status for orange3 (- to 3.35.0+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orange3/3.35.0+ds1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
    • Depends: orange3 opentsne
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 121 days old (needed 5 days)
• golang-github-gookit-color (- to 1.5.4-2)
  • Migration status for golang-github-gookit-color (- to 1.5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-gookit-color would introduce bugs in testing: #1061077
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gookit-color.html
    • autopkgtest for golang-github-gookit-color/1.5.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 122 days old (needed 2 days)
• haskell-arithmoi (- to 0.12.1.0-2)
  • Migration status for haskell-arithmoi (- to 0.12.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-arithmoi haskell-integer-roots (not considered)
    • Build-Depends-Indep: haskell-arithmoi haskell-integer-roots (not considered)
    • Depends: haskell-arithmoi haskell-integer-roots (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-arithmoi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 122 days old (needed 5 days)
• haskell-cryptol (- to 3.0.0-1)
  • Migration status for haskell-cryptol (- to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-prof
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-cryptol haskell-arithmoi
    • Build-Depends-Indep: haskell-cryptol haskell-arithmoi
    • Depends: haskell-cryptol haskell-arithmoi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cryptol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 122 days old (needed 5 days)
• haskell-dhall (- to 1.41.2-1)
  • Migration status for haskell-dhall (- to 1.41.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-dhall haskell-cborg
    • Build-Depends(-Arch): haskell-dhall haskell-cborg-json
    • Build-Depends(-Arch): haskell-dhall haskell-serialise
    • Build-Depends-Indep: haskell-dhall haskell-cborg
    • Build-Depends-Indep: haskell-dhall haskell-cborg-json
    • Build-Depends-Indep: haskell-dhall haskell-serialise
    • Depends: haskell-dhall haskell-cborg
    • Depends: haskell-dhall haskell-cborg-json
    • Depends: haskell-dhall haskell-serialise
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-dhall.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 122 days old (needed 5 days)
• rust-octocrab (- to 0.31.2-1)
  • Migration status for rust-octocrab (- to 0.31.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-octocrab-dev/amd64 has unsatisfiable dependency
    • librust-octocrab-dev/arm64 has unsatisfiable dependency
    • librust-octocrab-dev/armel has unsatisfiable dependency
    • librust-octocrab-dev/armhf has unsatisfiable dependency
    • librust-octocrab-dev/i386 has unsatisfiable dependency
    • librust-octocrab-dev/mips64el has unsatisfiable dependency
    • librust-octocrab-dev/ppc64el has unsatisfiable dependency
    • librust-octocrab-dev/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): rust-octocrab rust-hyper-timeout
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-octocrab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 122 days old (needed 5 days)
• rust-temp-testdir (- to 0.2.3-1)
  • Migration status for rust-temp-testdir (- to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-temp-testdir/0.2.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-temp-testdir.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 123 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 ♻, 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 ♻
    • 123 days old (needed 5 days)
• canu (- to 2.2+dfsg-5)
  • Migration status for canu (- to 2.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for canu/2.2+dfsg-5: amd64: Pass, arm64: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/canu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 125 days old (needed 5 days)
• rust-tikv-jemalloc-ctl (- to 0.5.4-1)
  • Migration status for rust-tikv-jemalloc-ctl (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-tikv-jemalloc-ctl/0.5.4-1: amd64: Regression or new test ♻, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-tikv-jemalloc-ctl rust-tikv-jemalloc-sys
    • Depends: rust-tikv-jemalloc-ctl rust-tikv-jemalloc-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tikv-jemalloc-ctl.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 126 days old (needed 5 days)
• python-xsdata (- to 23.8-1.1)
  • Migration status for python-xsdata (- to 23.8-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-xsdata python-docformatter (not considered)
    • Depends: python-xsdata python-docformatter (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xsdata.html
    • autopkgtest for python-xsdata/23.8-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 129 days old (needed 2 days)
• rust-xflags (- to 0.3.1-1)
  • Migration status for rust-xflags (- to 0.3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-xflags rust-xflags-macros (not considered)
    • Depends: rust-xflags rust-xflags-macros (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags.html
    • autopkgtest for rust-xflags/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 129 days old (needed 2 days)
• golang-codeberg-gusted-mcaptcha (- to 0.0~git20220723.4f3072e-1)
  • Migration status for golang-codeberg-gusted-mcaptcha (- to 0.0~git20220723.4f3072e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by openarungeek@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-codeberg-gusted-mcaptcha.html
    • autopkgtest for golang-codeberg-gusted-mcaptcha/0.0~git20220723.4f3072e-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 130 days old (needed 2 days)
• golang-github-alecthomas-mango-kong (- to 0.1.0-1)
  • Migration status for golang-github-alecthomas-mango-kong (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sgmoore@kde.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alecthomas-mango-kong.html
    • autopkgtest for golang-github-alecthomas-mango-kong/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 130 days old (needed 2 days)
• golang-github-jedisct1-go-hpke-compact (- to 0.9.2-1)
  • Migration status for golang-github-jedisct1-go-hpke-compact (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jedisct1-go-hpke-compact.html
    • autopkgtest for golang-github-jedisct1-go-hpke-compact/0.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 130 days old (needed 2 days)
• procdump (- to 2.2-1)
  • Migration status for procdump (- to 2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating procdump would introduce bugs in testing: #1064137
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for procdump/2.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/procdump.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 130 days old (needed 5 days)
• ironic (- to 1:23.0.0-4)
  • Migration status for ironic (- to 1:23.0.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: ironic python-amqplib (not considered)
    • Depends: ironic python-amqplib (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ironic.html
    • autopkgtest for ironic/1:23.0.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 131 days old (needed 2 days)
• phppgadmin (- to 7.13.0+dfsg-3)
  • Migration status for phppgadmin (- to 7.13.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phppgadmin would introduce bugs in testing: #1053004
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phppgadmin.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 131 days old (needed 5 days)
• kokkos (- to 3.7.01-2.1)
  • Migration status for kokkos (- to 3.7.01-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kokkos unsatisfiable Build-Depends(-Arch) on s390x: libmemkind-dev
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kokkos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 134 days old (needed 5 days)
• python-vispy (- to 0.14.1-2)
  • Migration status for python-vispy (- to 0.14.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-vispy python-hsluv (not considered)
    • Depends: python-vispy python-hsluv (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-vispy.html
    • autopkgtest for python-vispy/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 ♻, s390x: No tests, superficial or marked flaky ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 134 days old (needed 5 days)
• taurus-pyqtgraph (- to 0.6.2-1)
  • Migration status for taurus-pyqtgraph (- to 0.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): taurus-pyqtgraph taurus (not considered)
    • Depends: taurus-pyqtgraph taurus (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taurus-pyqtgraph.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 134 days old (needed 5 days)
• octavia (- to 13.0.0-2)
  • Migration status for octavia (- to 13.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: octavia sphinxcontrib-nwdiag (not considered)
    • Invalidated by build-dependency (indep)
    • Build-Depends-Indep: octavia sphinxcontrib-actdiag
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octavia.html
    • autopkgtest for octavia/13.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 135 days old (needed 2 days)
• openstack-trove (- to 1:20.0.0-2)
  • Migration status for openstack-trove (- to 1:20.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: openstack-trove python-cassandra-driver (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstack-trove.html
    • autopkgtest for openstack-trove/1:20.0.0-2: 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 ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 135 days old (needed 2 days)
• haskell-integer-roots (- to 1.0.2.0-2)
  • Migration status for haskell-integer-roots (- to 1.0.2.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-integer-roots.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 136 days old (needed 5 days)
• nova (- to 2:28.0.0-2)
  • Migration status for nova (- to 2:28.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nova/2:28.0.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
    • Build-Depends-Indep: nova sphinxcontrib-actdiag
    • Depends: nova python-amqplib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nova.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 136 days old (needed 5 days)
• ironic-python-agent (- to 9.7.0-2)
  • Migration status for ironic-python-agent (- to 9.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ironic-python-agent/9.7.0-2: amd64: Regression or new test ♻, arm64: 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/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
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 137 days old (needed 5 days)
• networking-baremetal (- to 6.2.0-2)
  • Migration status for networking-baremetal (- to 6.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for networking-baremetal/6.2.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-baremetal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 137 days old (needed 5 days)
• x2goserver (- to 4.1.0.6-1.1)
  • Migration status for x2goserver (- to 4.1.0.6-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: x2goserver x2gokdrive (not considered)
    • Invalidated by dependency
    • Depends: x2goserver x2godesktopsharing
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2goserver.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 137 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, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 138 days old (needed 2 days)
• haskell-cborg-json (- to 0.2.5.0-2)
  • Migration status for haskell-cborg-json (- to 0.2.5.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-cborg-json haskell-cborg
    • Build-Depends-Indep: haskell-cborg-json haskell-cborg
    • Depends: haskell-cborg-json haskell-cborg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cborg-json.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 139 days old (needed 5 days)
• haskell-serialise (- to 0.2.6.0-2)
  • Migration status for haskell-serialise (- to 0.2.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-serialise would introduce bugs in testing: #939323
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-serialise haskell-cborg
    • Build-Depends-Indep: haskell-serialise haskell-cborg
    • Depends: haskell-serialise haskell-cborg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-serialise.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 139 days old (needed 5 days)
• pytorch-cuda (- to 2.0.1+dfsg-5)
  • Migration status for pytorch-cuda (- to 2.0.1+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytorch-cuda/2.0.1+dfsg-5: amd64: Regression or new test ♻, ppc64el: Pass
    • Impossible Depends: pytorch-cuda -> libbenchmark1debian/1.8.3-1/amd64
    • Impossible Depends: pytorch-cuda -> libbenchmark1debian/1.8.3-1/ppc64el
    • Impossible Depends: pytorch-cuda -> libdnnl2/2.7.4-2/amd64
    • Build-Depends(-Arch): pytorch-cuda gloo-cuda
    • Depends: pytorch-cuda gloo-cuda
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 139 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
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 140 days old (needed 5 days)
• haskell-cborg (- to 0.2.9.0-1)
  • Migration status for haskell-cborg (- to 0.2.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-cborg would introduce bugs in testing: #1016062
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cborg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 140 days old (needed 5 days)
• networking-bagpipe (- to 19.0.0-1)
  • Migration status for networking-bagpipe (- to 19.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: networking-bagpipe sphinxcontrib-nwdiag (not considered)
    • Invalidated by build-dependency (indep)
    • Build-Depends-Indep: networking-bagpipe networking-bgpvpn
    • Build-Depends-Indep: networking-bagpipe networking-sfc
    • Build-Depends-Indep: networking-bagpipe sphinxcontrib-actdiag
    • Depends: networking-bagpipe networking-bgpvpn
    • Depends: networking-bagpipe networking-sfc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-bagpipe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 141 days old (needed 5 days)
• networking-bgpvpn (- to 19.0.0-1)
  • Migration status for networking-bgpvpn (- to 19.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: networking-bgpvpn networking-bagpipe (not considered)
    • Depends: networking-bgpvpn networking-bagpipe (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-bgpvpn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 141 days old (needed 5 days)
• neutron-dynamic-routing (- to 2:23.0.0-1)
  • Migration status for neutron-dynamic-routing (- to 2:23.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for neutron-dynamic-routing/2:23.0.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neutron-dynamic-routing.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 141 days old (needed 5 days)
• octavia-dashboard (- to 12.0.0-1)
  • Migration status for octavia-dashboard (- to 12.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: octavia-dashboard octavia (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octavia-dashboard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 141 days old (needed 5 days)
• sahara (- to 1:19.0.0-1)
  • Migration status for sahara (- to 1:19.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sahara would introduce bugs in testing: #1058233
    • autopkgtest for sahara/1:19.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sahara.html
    • 141 days old (needed 5 days)
• sahara-plugin-vanilla (- to 10.0.0-1)
  • Migration status for sahara-plugin-vanilla (- to 10.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: sahara-plugin-vanilla sahara (not considered)
    • Depends: sahara-plugin-vanilla sahara (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sahara-plugin-vanilla.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 141 days old (needed 5 days)
• watcher (- to 11.0.0-1)
  • Migration status for watcher (- to 11.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating watcher would introduce bugs in testing: #1058377
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watcher.html
    • 141 days old (needed 5 days)
• rust-rustpython-parser (- to 0.2.0-2)
  • Migration status for rust-rustpython-parser (- 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): rust-rustpython-parser rust-rustpython-ast (not considered)
    • Depends: rust-rustpython-parser rust-rustpython-ast (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustpython-parser.html
    • autopkgtest for rust-rustpython-parser/0.2.0-2: 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
    • 142 days old (needed 2 days)
• ttyd (- to 1.7.4-1)
  • Migration status for ttyd (- to 1.7.4-1): 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 ♻
    • 142 days old (needed 5 days)
• binoculars (- to 0.0.15-1)
  • Migration status for binoculars (- to 0.0.15-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): binoculars pyfai (not considered)
    • Depends: binoculars pyfai (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binoculars.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for binoculars/0.0.15-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 143 days old (needed 2 days)
• rust-axum-core (- to 0.3.4-1)
  • Migration status for rust-axum-core (- to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-axum-core 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 ♻
    • 143 days old (needed 5 days)
• rust-hyper-timeout (- to 0.4.1-1)
  • Migration status for rust-hyper-timeout (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-hyper-timeout/0.4.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hyper-timeout.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
• ghdl (- to 3.0.0+dfsg2-1)
  • Migration status for ghdl (- to 3.0.0+dfsg2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for ghdl/3.0.0+dfsg2-1: amd64: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghdl.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 145 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 unsatisfiable Build-Depends(-Arch) on arm64: libghdl-dev (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on arm64: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on armel: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on mips64el: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on ppc64el: ghdl-mcode (>= 3.0.0)
    • missing build on arm64
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for yosys-plugin-ghdl/0.0~git20230419.5b64ccf-1: amd64: Pass, i386: Pass
    • Build-Depends(-Arch): yosys-plugin-ghdl ghdl
    • Depends: yosys-plugin-ghdl ghdl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yosys-plugin-ghdl.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 146 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 ♻, 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 ♻
    • 147 days old (needed 5 days)
• clblas (- to 2.12-4)
  • Migration status for clblas (- to 2.12-4): 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-4: 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
    • 147 days old (needed 2 days)
• gamescope (- to 3.12.5-1)
  • Migration status for gamescope (- to 3.12.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gamescope would introduce bugs in testing: #1058493
    • Impossible Depends: gamescope -> libwlroots11/0.16.2-3/amd64
    • Impossible Depends: gamescope -> libwlroots11/0.16.2-3/arm64
    • Impossible Depends: gamescope -> libwlroots11/0.16.2-3/armhf
    • Impossible Depends: gamescope -> libwlroots11/0.16.2-3/i386
    • Impossible Depends: gamescope -> libwlroots11/0.16.2-3/mips64el
    • Impossible Depends: gamescope -> libwlroots11/0.16.2-3/ppc64el
    • Impossible Depends: gamescope -> libwlroots11/0.16.2-3/s390x
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 148 days old (needed 5 days)
• gcc-mingw-w64 (25.2 to 26.1)
  • Migration status for gcc-mingw-w64 (25.2 to 26.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Updating gcc-mingw-w64 will fix bugs in testing: #1052220, #1054336
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-mingw-w64.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 151 days old (needed 5 days)
• x2gokdrive (- to 0.0.0.2-1)
  • Migration status for x2gokdrive (- to 0.0.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating x2gokdrive would introduce bugs in testing: #1054800
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2gokdrive.html
    • 151 days old (needed 5 days)
• partman-hfs (- to 11)
  • Migration status for partman-hfs (- to 11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • partman-hfs/amd64 has unsatisfiable dependency
    • partman-hfs/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 152 days old (needed 5 days)
• lxdm (- to 0.5.3-5)
  • Migration status for lxdm (- to 0.5.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lxdm would introduce bugs in testing: #1053089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxdm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 153 days old (needed 5 days)
• python-colorful (- to 0.5.5-1)
  • Migration status for python-colorful (- to 0.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sophieb, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-colorful.html
    • autopkgtest for python-colorful/0.5.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 153 days old (needed 2 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, s390x: Pass
    • Not built on buildd: arch amd64 binaries uploaded by microjoe@microjoe.org
  • 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 ♻
    • 153 days old (needed 5 days)
• skorch (- to 0.15.0-1)
  • Migration status for skorch (- 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): skorch pytorch (not considered)
    • Depends: skorch pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skorch.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for skorch/0.15.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 154 days old (needed 2 days)
• pg-gvm (- to 22.6.2-1)
  • Migration status for pg-gvm (- to 22.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): 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.2-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 ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 156 days old (needed 2 days)
• rust-rsa (- to 0.9.2-2)
  • Migration status for rust-rsa (- to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-rsa would introduce bugs in testing: #1057096
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rsa.html
    • autopkgtest for rust-rsa/0.9.2-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 156 days old (needed 5 days)
• graftcp (- to 0.3.1+ds1-2)
  • Migration status for graftcp (- to 0.3.1+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graftcp would introduce bugs in testing: #981713
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graftcp.html
    • Reproducible on amd64 - info ♻
    • 157 days old (needed 5 days)
• mono-tools (- to 4.2-3.2)
  • Migration status for mono-tools (- to 4.2-3.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: mono-tools cecil (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mono-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 157 days old (needed 5 days)
• pgpcre (- to 0.20190509-6)
  • Migration status for pgpcre (- to 0.20190509-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pgpcre would introduce bugs in testing: #1000001
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgpcre.html
    • autopkgtest for pgpcre/0.20190509-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 157 days old (needed 2 days)
• rust-mozim (- to 0.2.2-1)
  • Migration status for rust-mozim (- to 0.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): rust-mozim rust-etherparse (not considered)
    • Depends: rust-mozim rust-etherparse (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-mozim.html
    • autopkgtest for rust-mozim/0.2.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 157 days old (needed 5 days)
• check-patroni (- to 1.0.0-1)
  • Migration status for check-patroni (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-patroni.html
    • autopkgtest for check-patroni/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 161 days old (needed 2 days)
• obs-ashmanix-countdown (- to 1.3.3-1)
  • Migration status for obs-ashmanix-countdown (- to 1.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-ashmanix-countdown would introduce bugs in testing: #1060938
    • Build-Depends(-Arch): obs-ashmanix-countdown obs-studio
    • Depends: obs-ashmanix-countdown obs-studio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-ashmanix-countdown.html
    • autopkgtest for obs-ashmanix-countdown/1.3.3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 161 days old (needed 5 days)
• rust-etherparse (- to 0.13.0-1)
  • Migration status for rust-etherparse (- to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-etherparse/0.13.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-etherparse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 161 days old (needed 5 days)
• rust-rustpython-common (- to 0.2.0-1)
  • Migration status for rust-rustpython-common (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-rustpython-common/0.2.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustpython-common.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 161 days old (needed 5 days)
• gpac (- to 2.2.1+dfsg1-3)
  • Migration status for gpac (- to 2.2.1+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpac would introduce bugs in testing: #1034732, #1051740, #1051866, #1051955, #1056282, #1059056, #1060409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpac.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 162 days old (needed 5 days)
• obs-color-monitor (- to 0.6.1-1)
  • Migration status for obs-color-monitor (- to 0.6.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-color-monitor obs-studio (not considered)
    • Depends: obs-color-monitor obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-color-monitor.html
    • autopkgtest for obs-color-monitor/0.6.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: 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 ♻
    • 163 days old (needed 5 days)
• gnome-feeds (- to 2.2.0-2)
  • Migration status for gnome-feeds (- to 2.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: gnome-feeds syndication-domination (not considered)
    • Depends: gnome-feeds syndication-domination (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-feeds.html
    • autopkgtest for gnome-feeds/2.2.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 164 days old (needed 5 days)
• ocamldap (- to 2.4.2-5)
  • Migration status for ocamldap (- to 2.4.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocamldap pcre-ocaml (not considered)
    • Depends: ocamldap pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamldap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 164 days old (needed 5 days)
• opentsne (- to 1.0.0-1)
  • Migration status for opentsne (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opentsne would introduce bugs in testing: #1004706, #1056827
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for opentsne/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opentsne.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • 164 days old (needed 5 days)
• icingaweb2-module-nagvis (- to 1.1.1-4)
  • Migration status for icingaweb2-module-nagvis (- to 1.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating icingaweb2-module-nagvis would introduce bugs in testing: #1057075
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/i/icingaweb2-module-nagvis.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 165 days old (needed 5 days)
• obs-advanced-scene-switcher (- to 1.23.1-2)
  • Migration status for obs-advanced-scene-switcher (- to 1.23.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-advanced-scene-switcher obs-studio (not considered)
    • Depends: obs-advanced-scene-switcher obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-advanced-scene-switcher.html
    • autopkgtest for obs-advanced-scene-switcher/1.23.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 165 days old (needed 5 days)
• syndication-domination (- to 1.0-2)
  • Migration status for syndication-domination (- to 1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating syndication-domination would introduce bugs in testing: #1059672
    • autopkgtest for syndication-domination/1.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syndication-domination.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 165 days old (needed 5 days)
• genx (- to 3.6.22-2)
  • Migration status for genx (- to 3.6.22-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-genx/ppc64el has unsatisfiable dependency
    • autopkgtest for genx/3.6.22-2: amd64: Pass
    • Build-Depends(-Arch): genx numba
    • Depends: genx numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genx.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 166 days old (needed 5 days)
• golang-github-jesseduffield-go-git (- to 5.1.2+git20221018.fdd53fe-1)
  • Migration status for golang-github-jesseduffield-go-git (- to 5.1.2+git20221018.fdd53fe-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by openarungeek@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-go-git.html
    • autopkgtest for golang-github-jesseduffield-go-git/5.1.2+git20221018.fdd53fe-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 166 days old (needed 2 days)
• haskell-hsyaml-aeson (- to 0.2.0.1-2)
  • Migration status for haskell-hsyaml-aeson (- to 0.2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-hsyaml-aeson would introduce bugs in testing: #1054961
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): haskell-hsyaml-aeson haskell-hsyaml
    • Build-Depends-Indep: haskell-hsyaml-aeson haskell-hsyaml
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsyaml-aeson.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 166 days old (needed 5 days)
• ocaml-lastfm (- to 0.3.3-4)
  • Migration status for ocaml-lastfm (- to 0.3.3-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocaml-lastfm pcre-ocaml (not considered)
    • Depends: ocaml-lastfm pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-lastfm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 166 days old (needed 5 days)
• python-docformatter (- to 1.7.5-1)
  • Migration status for python-docformatter (- to 1.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-docformatter would introduce bugs in testing: #1056469
    • autopkgtest for python-docformatter/1.7.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-docformatter.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 167 days old (needed 5 days)
• pytorch-ignite (- to 0.4.12-1)
  • Migration status for pytorch-ignite (- to 0.4.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pytorch-ignite pytorch (not considered)
    • Depends: pytorch-ignite pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-ignite.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 167 days old (needed 5 days)
• pytorch-text (- to 0.15.2-1)
  • Migration status for pytorch-text (- to 0.15.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pytorch-text pytorch (not considered)
    • Depends: pytorch-text pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-text.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 167 days old (needed 5 days)
• haskell-base64 (- to 0.4.2.4-3)
  • Migration status for haskell-base64 (- to 0.4.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-base64 would introduce bugs in testing: #1057652
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-base64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 168 days old (needed 5 days)
• meteo-qt (- to 3.3-2)
  • Migration status for meteo-qt (- to 3.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: meteo-qt sip4 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meteo-qt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 168 days old (needed 5 days)
• nomacs (- to 3.17.2282+dfsg-2)
  • Migration status for nomacs (- to 3.17.2282+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nomacs would introduce bugs in testing: #1014124, #974616
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomacs.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 169 days old (needed 5 days)
• python-aiojobs (- to 1.1.0-2)
  • Migration status for python-aiojobs (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiojobs would introduce bugs in testing: #1060944
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiojobs.html
    • autopkgtest for python-aiojobs/1.1.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 169 days old (needed 5 days)
• vuls (- to 0.6.1-5)
  • Migration status for vuls (- to 0.6.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: vuls golang-github-go-redis-redis (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): vuls go-cve-dictionary
    • Build-Depends(-Arch): vuls go-exploitdb
    • Build-Depends(-Arch): vuls gost
    • Build-Depends(-Arch): vuls goval-dictionary
    • Built-Using: vuls go-cve-dictionary
    • Built-Using: vuls go-exploitdb
    • Built-Using: vuls gost
    • Built-Using: vuls goval-dictionary
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vuls.html
    • autopkgtest for vuls/0.6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 169 days old (needed 2 days)
• pytorch-vision (- to 0.15.2-1)
  • Migration status for pytorch-vision (- to 0.15.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytorch-vision would introduce bugs in testing: #1051811
    • autopkgtest for pytorch-vision/0.15.2-1: amd64: Regression or new test ♻, arm64: Pass, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): pytorch-vision pytorch
    • Depends: pytorch-vision pytorch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-vision.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 170 days old (needed 5 days)
• clickhouse (- to 18.16.1+ds-7.4)
  • Migration status for clickhouse (- to 18.16.1+ds-7.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clickhouse would introduce bugs in testing: #1059261
    • Build-Depends(-Arch): clickhouse poco
    • Depends: clickhouse poco
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clickhouse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 171 days old (needed 5 days)
• prometheus-varnish-exporter (- to 1.6.1-2)
  • Migration status for prometheus-varnish-exporter (- to 1.6.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: prometheus-varnish-exporter varnish (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-varnish-exporter.html
    • autopkgtest for prometheus-varnish-exporter/1.6.1-2: 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
    • 171 days old (needed 2 days)
• obs-scene-tree-view (- to 0.1.7-1)
  • Migration status for obs-scene-tree-view (- to 0.1.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-scene-tree-view obs-studio (not considered)
    • Depends: obs-scene-tree-view obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-scene-tree-view.html
    • autopkgtest for obs-scene-tree-view/0.1.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 172 days old (needed 5 days)
• ropgadget (- to 7.4+dfsg-1)
  • Migration status for ropgadget (- to 7.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ropgadget/7.4+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: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ropgadget.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 172 days old (needed 5 days)
• gnome-shell-extension-weather (- to 121-1)
  • Migration status for gnome-shell-extension-weather (- to 121-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-shell-extension-weather would introduce bugs in testing: #1052111
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-weather.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 173 days old (needed 5 days)
• haskell-regex-pcre (- to 0.95.0.0-4)
  • Migration status for haskell-regex-pcre (- to 0.95.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-regex-pcre would introduce bugs in testing: #1000067
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-regex-pcre.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 174 days old (needed 5 days)
• mailman3 (- to 3.3.8-3.1)
  • Migration status for mailman3 (- to 3.3.8-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mailman3 mailman-hyperkitty
    • Depends: mailman3 mailman-suite
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mailman3.html
    • autopkgtest for mailman3/3.3.8-3.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 174 days old (needed 2 days)
• ocaml-http (- to 0.1.6-2)
  • Migration status for ocaml-http (- to 0.1.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocaml-http pcre-ocaml (not considered)
    • Depends: ocaml-http pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-http.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 174 days old (needed 5 days)
• ocamlsdl (- to 0.9.1-4)
  • Migration status for ocamlsdl (- to 0.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocamlsdl would introduce bugs in testing: #1038076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlsdl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 174 days old (needed 5 days)
• rust-rustpython-ast (- to 0.2.0-1)
  • Migration status for rust-rustpython-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:
    • Depends: rust-rustpython-ast rust-rustpython-common (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustpython-ast.html
    • autopkgtest for rust-rustpython-ast/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 174 days old (needed 2 days)
• frr (- to 8.4.4-1.1)
  • Migration status for frr (- to 8.4.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating frr would introduce bugs in testing: #1055852
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frr.html
    • autopkgtest for frr/8.4.4-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 175 days old (needed 2 days)
• trocla (- to 0.5.1-2)
  • Migration status for trocla (- to 0.5.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): trocla ruby-moneta (not considered)
    • Depends: trocla ruby-moneta (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trocla.html
    • autopkgtest for trocla/0.5.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 176 days old (needed 2 days)
• docstring-parser (- to 0.15-3)
  • Migration status for docstring-parser (- to 0.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for docstring-parser/0.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docstring-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 177 days old (needed 5 days)
• gloo-cuda (- to 0.0~git20230117.1090929-2)
  • Migration status for gloo-cuda (- to 0.0~git20230117.1090929-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gloo-cuda would introduce bugs in testing: #1063743
    • Impossible Depends: gloo-cuda -> libhiredis0.14/0.14.1-4/amd64
    • Impossible Depends: gloo-cuda -> libhiredis0.14/0.14.1-4/arm64
    • Impossible Depends: gloo-cuda -> libhiredis0.14/0.14.1-4/ppc64el
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for gloo-cuda/0.0~git20230117.1090929-2: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 177 days old (needed 2 days)
• docbook-defguide (- to 2.0.17+svn9912-3)
  • Migration status for docbook-defguide (- to 2.0.17+svn9912-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating docbook-defguide would introduce bugs in testing: #1031512
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docbook-defguide.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 178 days old (needed 5 days)
• x2goclient (- to 4.1.2.3-1)
  • Migration status for x2goclient (- to 4.1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating x2goclient would introduce bugs in testing: #1042816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2goclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 178 days old (needed 5 days)
• worker (- to 4.12.1-1)
  • Migration status for worker (- to 4.12.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): worker avfs (not considered)
    • Depends: worker avfs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/worker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 179 days old (needed 5 days)
• ibus-anthy (- to 1.5.15-1)
  • Migration status for ibus-anthy (- to 1.5.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ibus-anthy would introduce bugs in testing: #1060953
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-anthy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 180 days old (needed 5 days)
• repetier-host (- to 0.85+dfsg-5)
  • Migration status for repetier-host (- to 0.85+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): repetier-host opentk (not considered)
    • Depends: repetier-host opentk (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/repetier-host.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 180 days old (needed 5 days)
• valijson (- to 1.0+repack-3)
  • Migration status for valijson (- to 1.0+repack-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): valijson poco (not considered)
    • Depends: valijson poco (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valijson.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 180 days old (needed 5 days)
• lookatme (- to 2.5.4-2)
  • Migration status for lookatme (- to 2.5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lookatme would introduce bugs in testing: #1061029
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lookatme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 182 days old (needed 5 days)
• python3.10 (- to 3.10.13-1)
  • Migration status for python3.10 (- to 3.10.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • idle-python3.10/amd64 has unsatisfiable dependency
    • python3.10-full/amd64 has unsatisfiable dependency
    • python3.10-venv/amd64 has unsatisfiable dependency
    • idle-python3.10/arm64 has unsatisfiable dependency
    • python3.10-full/arm64 has unsatisfiable dependency
    • python3.10-venv/arm64 has unsatisfiable dependency
    • python3.10-full/armel has unsatisfiable dependency
    • python3.10-venv/armel has unsatisfiable dependency
    • python3.10-full/armhf has unsatisfiable dependency
    • python3.10-venv/armhf has unsatisfiable dependency
    • python3.10-full/i386 has unsatisfiable dependency
    • python3.10-venv/i386 has unsatisfiable dependency
    • python3.10-full/mips64el has unsatisfiable dependency
    • python3.10-venv/mips64el has unsatisfiable dependency
    • python3.10-full/ppc64el has unsatisfiable dependency
    • python3.10-venv/ppc64el has unsatisfiable dependency
    • python3.10-full/s390x has unsatisfiable dependency
    • python3.10-venv/s390x has unsatisfiable dependency
    • Updating python3.10 would introduce bugs in testing: #1030530, #1031969
    • Build-Depends(-Arch): python3.10 mpdecimal
    • Depends: python3.10 mpdecimal
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python3.10.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch 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
    • 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 ♻
    • 182 days old (needed 5 days)
• bind-dyndb-ldap (- to 11.10-6)
  • Migration status for bind-dyndb-ldap (- to 11.10-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bind9-dyndb-ldap/amd64 has unsatisfiable dependency
    • bind9-dyndb-ldap/arm64 has unsatisfiable dependency
    • bind9-dyndb-ldap/armel has unsatisfiable dependency
    • bind9-dyndb-ldap/armhf has unsatisfiable dependency
    • bind9-dyndb-ldap/i386 has unsatisfiable dependency
    • bind9-dyndb-ldap/mips64el has unsatisfiable dependency
    • bind9-dyndb-ldap/ppc64el has unsatisfiable dependency
    • bind9-dyndb-ldap/s390x has unsatisfiable dependency
    • Updating bind-dyndb-ldap would introduce bugs in testing: #1064294
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bind-dyndb-ldap.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 183 days old (needed 5 days)
• python-kafka (- to 2.0.2-5)
  • Migration status for python-kafka (- to 2.0.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-kafka would introduce bugs in testing: #1058290
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-kafka.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 183 days old (needed 5 days)
• emacs-jedi (- to 0.2.8+git20220410.81c5a42-1)
  • Migration status for emacs-jedi (- to 0.2.8+git20220410.81c5a42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-jedi would introduce bugs in testing: #994171
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-jedi.html
    • autopkgtest for emacs-jedi/0.2.8+git20220410.81c5a42-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 185 days old (needed 2 days)
• gnome-shell-extension-bluetooth-quick-connect (- to 36-2)
  • Migration status for gnome-shell-extension-bluetooth-quick-connect (- to 36-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-shell-extension-bluetooth-quick-connect would introduce bugs in testing: #1052090
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-bluetooth-quick-connect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 186 days old (needed 5 days)
• node-socks-proxy-agent (- to 7.0.0+dfsg+~cs2.0.11-1)
  • Migration status for node-socks-proxy-agent (- to 7.0.0+dfsg+~cs2.0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • node-socks-proxy-agent has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 187 days old (needed 5 days)
• node-lockfile (- to 1.0.4+~1.0.2-3)
  • Migration status for node-lockfile (- to 1.0.4+~1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-lockfile would introduce bugs in testing: #1005940
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-lockfile.html
    • autopkgtest for node-lockfile/1.0.4+~1.0.2-3: 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
    • 188 days old (needed 2 days)
• go-cve-dictionary (- to 0.3.1-5)
  • Migration status for go-cve-dictionary (- to 0.3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Depends: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-cve-dictionary.html
    • autopkgtest for go-cve-dictionary/0.3.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 190 days old (needed 2 days)
• golang-github-jesseduffield-termbox-go (- to 0.0~git20200823.a2289ed-1)
  • Migration status for golang-github-jesseduffield-termbox-go (- to 0.0~git20200823.a2289ed-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-termbox-go would introduce bugs in testing: #1032114
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-termbox-go.html
    • autopkgtest for golang-github-jesseduffield-termbox-go/0.0~git20200823.a2289ed-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 190 days old (needed 2 days)
• gost (- to 0.1.2-2)
  • Migration status for gost (- to 0.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gost golang-github-go-redis-redis (not considered)
    • Built-Using: gost golang-github-go-redis-redis (not considered)
    • Depends: gost golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gost.html
    • autopkgtest for gost/0.1.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 190 days old (needed 2 days)
• goval-dictionary (- to 0.2.0-6)
  • Migration status for goval-dictionary (- to 0.2.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): goval-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: goval-dictionary golang-github-go-redis-redis (not considered)
    • Depends: goval-dictionary golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goval-dictionary.html
    • autopkgtest for goval-dictionary/0.2.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 190 days old (needed 2 days)
• pcre-ocaml (- to 7.5.0-3)
  • Migration status for pcre-ocaml (- to 7.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcre-ocaml would introduce bugs in testing: #1000004
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcre-ocaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 190 days old (needed 5 days)
• tomopy (- to 1.14.1+ds1-1)
  • Migration status for tomopy (- to 1.14.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomopy would introduce bugs in testing: #1032045, #1036684, #1061064
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for tomopy/1.14.1+ds1-1: amd64: Pass, armel: Pass, armhf: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 190 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): go-exploitdb golang-github-go-redis-redis (not considered)
    • Built-Using: go-exploitdb golang-github-go-redis-redis (not considered)
    • Depends: go-exploitdb golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-exploitdb.html
    • autopkgtest for go-exploitdb/0.0~git20181130.7c961e7-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 191 days old (needed 2 days)
• python-discord (- to 2.3.2+dfsg-2)
  • Migration status for python-discord (- to 2.3.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-discord would introduce bugs in testing: #1057608
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-discord.html
    • autopkgtest for python-discord/2.3.2+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 days old (needed 5 days)
• redmine-plugin-local-avatars (- to 1.0.6-1)
  • Migration status for redmine-plugin-local-avatars (- to 1.0.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-local-avatars redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-local-avatars.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 days old (needed 5 days)
• redmine-plugin-pretend (- to 1.0-2)
  • Migration status for redmine-plugin-pretend (- to 1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-pretend redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-pretend.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 days old (needed 5 days)
• heat-cfntools (- to 1.4.2-4)
  • Migration status for heat-cfntools (- to 1.4.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating heat-cfntools would introduce bugs in testing: #1058242
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heat-cfntools.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 192 days old (needed 5 days)
• libengine-gost-openssl (- to 3.0.2-1)
  • Migration status for libengine-gost-openssl (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libengine-gost-openssl would introduce bugs in testing: #1054922
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libengine-gost-openssl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 192 days old (needed 5 days)
• magicgui (- to 0.7.2-3)
  • Migration status for magicgui (- to 0.7.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for magicgui/0.7.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 ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): magicgui docstring-parser
    • Depends: magicgui docstring-parser
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magicgui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 192 days old (needed 5 days)
• xfce4-panel-profiles (- to 1.0.14-1)
  • Migration status for xfce4-panel-profiles (- to 1.0.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfce4-panel-profiles would introduce bugs in testing: #1056704
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-panel-profiles.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 192 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 ♻, 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 ♻
    • 193 days old (needed 5 days)
• libreswan (- to 4.12-1)
  • Migration status for libreswan (- to 4.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libreswan would introduce bugs in testing: #1060981
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libreswan.html
    • autopkgtest for libreswan/4.12-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 196 days old (needed 2 days)
• tomcatjss (- to 8.4.0-2)
  • Migration status for tomcatjss (- to 8.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomcatjss would introduce bugs in testing: #1031816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomcatjss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 196 days old (needed 5 days)
• fanwor (- to 1.16-1)
  • Migration status for fanwor (- to 1.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fanwor would introduce bugs in testing: #1055538
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fanwor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 197 days old (needed 5 days)
• libapache-mod-auth-kerb (- to 5.4-3)
  • Migration status for libapache-mod-auth-kerb (- to 5.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache-mod-auth-kerb would introduce bugs in testing: #976156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-mod-auth-kerb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 197 days old (needed 5 days)
• eln (- to 1.5.2-1)
  • Migration status for eln (- to 1.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • eln unsatisfiable Build-Depends(-Arch) on armel: qt6-webengine-dev
    • eln unsatisfiable Build-Depends(-Arch) on armel: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on armel: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on armel: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qt6-webengine-dev
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qt6-webengine-dev
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qt6-webengine-dev
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qml6-module-qtwebengine
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eln.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
• macs (- to 2.2.9.1-1)
  • Migration status for macs (- to 2.2.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating macs would introduce bugs in testing: #1056813
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/macs.html
    • autopkgtest for macs/2.2.9.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 198 days old (needed 2 days)
• aircrack-ng (- to 1:1.7+git20230807.4bf83f1a-1)
  • Migration status for aircrack-ng (- to 1:1.7+git20230807.4bf83f1a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aircrack-ng would introduce bugs in testing: #1051201
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aircrack-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
• freebsd-buildutils (- to 10.3~svn296373-7.1)
  • Migration status for freebsd-buildutils (- to 10.3~svn296373-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • freebsd-buildutils unsatisfiable Build-Depends(-Arch) on mips64el: gcc-9
    • missing build on mips64el
    • Build-Depends(-Arch): freebsd-buildutils freebsd-glue
    • Build-Depends(-Arch): freebsd-buildutils freebsd-libs
    • Build-Depends(-Arch): freebsd-buildutils gcc-9
    • Depends: freebsd-buildutils freebsd-glue
    • Depends: freebsd-buildutils freebsd-libs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-buildutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
• itop (- to 0.1-4.1)
  • Migration status for itop (- to 0.1-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating itop would introduce bugs in testing: #904206
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/itop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
• nabu (- to 2023.1.1-3)
  • Migration status for nabu (- to 2023.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nabu/2023.1.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 ♻
    • Build-Depends(-Arch): nabu silx
    • Build-Depends(-Arch): nabu tomoscan
    • Depends: nabu silx
    • Depends: nabu tomoscan
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nabu.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 199 days old (needed 5 days)
• freebsd-glue (- to 0.2.22+nmu1)
  • Migration status for freebsd-glue (- to 0.2.22+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • freebsd-glue unsatisfiable Build-Depends(-Arch) on mips64el: gcc-9
    • missing build on mips64el
    • Build-Depends(-Arch): freebsd-glue freebsd-buildutils
    • Build-Depends(-Arch): freebsd-glue gcc-9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-glue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 200 days old (needed 5 days)
• python-pyepics (- to 3.5.1+ds-1)
  • Migration status for python-pyepics (- to 3.5.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyepics would introduce bugs in testing: #1058200
    • Build-Depends(-Arch): python-pyepics epics-base
    • Depends: python-pyepics epics-base
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyepics.html
    • autopkgtest for python-pyepics/3.5.1+ds-1: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 201 days old (needed 2 days)
• chkservice (- to 0.3-1.1)
  • Migration status for chkservice (- to 0.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chkservice would introduce bugs in testing: #988094
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chkservice.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 202 days old (needed 5 days)
• cpupower-gui (- to 0.7.2-2.1)
  • Migration status for cpupower-gui (- to 0.7.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpupower-gui would introduce bugs in testing: #1025555
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpupower-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 202 days old (needed 5 days)
• criu (- to 3.17.1-3)
  • Migration status for criu (- to 3.17.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating criu would introduce bugs in testing: #1054814
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/criu.html
    • 202 days old (needed 5 days)
• oss4 (- to 4.2-build2020-2)
  • Migration status for oss4 (- to 4.2-build2020-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oss4 would introduce bugs in testing: #796636
    • Not built on buildd: arch amd64 binaries uploaded by sthibault
    • Not built on buildd: arch all binaries uploaded by sthibault, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oss4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 202 days old (needed 5 days)
• avfs (- to 1.1.5-1)
  • Migration status for avfs (- to 1.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating avfs would introduce bugs in testing: #1061322
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 203 days old (needed 5 days)
• epics-base (- to 7.0.7+dfsg1-5)
  • Migration status for epics-base (- to 7.0.7+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epics-base would introduce bugs in testing: #1060260
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epics-base.html
    • 203 days old (needed 5 days)
• tomoscan (- to 1.2.2-2)
  • Migration status for tomoscan (- to 1.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tomoscan/1.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 ♻
    • Build-Depends(-Arch): tomoscan silx
    • Depends: tomoscan silx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomoscan.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 204 days old (needed 5 days)
• forensics-extra (- to 2.49)
  • Migration status for forensics-extra (- to 2.49): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: forensics-extra forensics-all (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forensics-extra.html
    • autopkgtest for forensics-extra/2.49: 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
    • 205 days old (needed 2 days)
• newsboat (- to 2.32-3)
  • Migration status for newsboat (- to 2.32-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating newsboat would introduce bugs in testing: #1054680
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/newsboat.html
    • autopkgtest for newsboat/2.32-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 208 days old (needed 2 days)
• gtkwave (- to 3.3.116-1)
  • Migration status for gtkwave (- to 3.3.116-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtkwave would introduce bugs in testing: #1060407
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkwave.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 209 days old (needed 5 days)
• bitsnpicas (- to 2.0+ds-2)
  • Migration status for bitsnpicas (- to 2.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bitsnpicas would introduce bugs in testing: #1041435
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bitsnpicas.html
    • 214 days old (needed 5 days)
• forensics-all (- to 3.47)
  • Migration status for forensics-all (- to 3.47): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: forensics-all shed (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forensics-all.html
    • autopkgtest for forensics-all/3.47: 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
    • 214 days old (needed 2 days)
• haskell-swish (- to 0.10.4.0-1)
  • Migration status for haskell-swish (- to 0.10.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-swish-doc/amd64 has unsatisfiable dependency
    • libghc-swish-doc/arm64 has unsatisfiable dependency
    • libghc-swish-dev/mips64el has unsatisfiable dependency
    • libghc-swish-prof/mips64el has unsatisfiable dependency
    • Updating haskell-swish would introduce bugs in testing: #1058746
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-swish.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 214 days old (needed 5 days)
• mythtv-status (- to 1.1.0-1)
  • Migration status for mythtv-status (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mythtv-status would introduce bugs in testing: #1052282
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mythtv-status.html
    • autopkgtest for mythtv-status/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 216 days old (needed 2 days)
• openjdk-20 (- to 20.0.2+9-1)
  • Migration status for openjdk-20 (- to 20.0.2+9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-20 would introduce bugs in testing: #1031889
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-20.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-20/20.0.2+9-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 217 days old (needed 5 days)
• pyrlp (- to 0.5.1-4)
  • Migration status for pyrlp (- to 0.5.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyrlp would introduce bugs in testing: #1056442
    • autopkgtest for pyrlp/0.5.1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrlp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 217 days old (needed 5 days)
• ctfutils (- to 10.3~svn297264-2.1)
  • Migration status for ctfutils (- to 10.3~svn297264-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ctfutils freebsd-libs (not considered)
    • Depends: ctfutils freebsd-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ctfutils freebsd-buildutils
    • Build-Depends(-Arch): ctfutils freebsd-glue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctfutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 218 days old (needed 5 days)
• python-package-smoke-test (- to 1.0-1)
  • Migration status for python-package-smoke-test (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ben@benfinney.id.au, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-package-smoke-test.html
    • autopkgtest for python-package-smoke-test/1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 218 days old (needed 5 days)
• debian-parl (- to 1.9.31+nmu1)
  • Migration status for debian-parl (- to 1.9.31+nmu1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: debian-parl syncevolution (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-parl.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 219 days old (needed 5 days)
• supertuxkart (- to 1.4+dfsg-3)
  • Migration status for supertuxkart (- to 1.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating supertuxkart would introduce bugs in testing: #1057463
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/supertuxkart.html
    • 222 days old (needed 5 days)
• renderdoc (- to 1.27+dfsg-1)
  • Migration status for renderdoc (- to 1.27+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating renderdoc would introduce bugs in testing: #999924
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 223 days old (needed 5 days)
• rust-packed-simd (- to 0.3.8-1)
  • Migration status for rust-packed-simd (- to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-packed-simd/0.3.8-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-packed-simd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 223 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 ♻
    • 224 days old (needed 5 days)
• gcc-9-cross (- to 29)
  • Migration status for gcc-9-cross (- to 29): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-cross would introduce bugs in testing: #1032217, #994134
    • Build-Depends(-Arch): gcc-9-cross autoconf2.64
    • Build-Depends(-Arch): gcc-9-cross gcc-9
    • Built-Using: gcc-9-cross gcc-9
    • Depends: gcc-9-cross gcc-9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 224 days old (needed 5 days)
• gcc-9-cross-ports (- to 27)
  • Migration status for gcc-9-cross-ports (- to 27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-cross-ports would introduce bugs in testing: #1032216, #994135
    • Build-Depends(-Arch): gcc-9-cross-ports autoconf2.64
    • Build-Depends(-Arch): gcc-9-cross-ports gcc-9
    • Built-Using: gcc-9-cross-ports gcc-9
    • Depends: gcc-9-cross-ports gcc-9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross-ports.html
    • 224 days old (needed 5 days)
• ruby-appraiser-rubocop (- to 1.0.1-2)
  • Migration status for ruby-appraiser-rubocop (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-appraiser-rubocop/amd64 has unsatisfiable dependency
    • ruby-appraiser-rubocop/arm64 has unsatisfiable dependency
    • Updating ruby-appraiser-rubocop would introduce bugs in testing: #1054166
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-appraiser-rubocop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 224 days old (needed 5 days)
• azure-cli (- to 2.50.0-2)
  • Migration status for azure-cli (- to 2.50.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating azure-cli would introduce bugs in testing: #1057393
    • autopkgtest for azure-cli/2.50.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): azure-cli azure-functions-devops-build
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/azure-cli.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 226 days old (needed 5 days)
• gcc-10-cross-mipsen (- to 3+c6)
  • Migration status for gcc-10-cross-mipsen (- to 3+c6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • g++-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • Updating gcc-10-cross-mipsen would introduce bugs in testing: #1032218, #1040624
    • Build-Depends(-Arch): gcc-10-cross-mipsen gcc-10
    • Built-Using: gcc-10-cross-mipsen gcc-10
    • Depends: gcc-10-cross-mipsen gcc-10
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-mipsen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 226 days old (needed 5 days)
• golang-github-hashicorp-terraform-registry-address (- to 0.2.0-1)
  • Migration status for golang-github-hashicorp-terraform-registry-address (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by foka, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-terraform-registry-address.html
    • autopkgtest for golang-github-hashicorp-terraform-registry-address/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 226 days old (needed 2 days)
• baler (- to 1.3.0-1)
  • Migration status for baler (- to 1.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): baler pytorch (not considered)
    • Depends: baler pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/baler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 227 days old (needed 5 days)
• gcc-10-cross-ports (- to 24)
  • Migration status for gcc-10-cross-ports (- to 24): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-10-cross-ports gcc-10 (not considered)
    • Built-Using: gcc-10-cross-ports gcc-10 (not considered)
    • Depends: gcc-10-cross-ports gcc-10 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-ports.html
    • 228 days old (needed 5 days)
• redmine (- to 5.0.4-7)
  • Migration status for redmine (- to 5.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redmine would introduce bugs in testing: #1040927, #1052877, #1055474
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/redmine.html
    • autopkgtest for redmine/5.0.4-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): redmine ruby-html-pipeline
    • Build-Depends(-Arch): redmine ruby-task-list
    • Depends: redmine ruby-html-pipeline
    • Depends: redmine ruby-task-list
  • Additional info:
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• gcc-10-cross (- to 23)
  • Migration status for gcc-10-cross (- to 23): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-10-cross gcc-10 (not considered)
    • Built-Using: gcc-10-cross gcc-10 (not considered)
    • Depends: gcc-10-cross gcc-10 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross.html
    • 229 days old (needed 5 days)
• kanboard (- to 1.2.31+ds2-1)
  • Migration status for kanboard (- to 1.2.31+ds2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kanboard would introduce bugs in testing: #1052638
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kanboard.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for kanboard/1.2.31+ds2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, 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
    • 229 days old (needed 2 days)
• magnum-cluster-api (- to 0.6.0-1)
  • Migration status for magnum-cluster-api (- 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 zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magnum-cluster-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 230 days old (needed 5 days)
• odr-padenc (- to 3.0.0-2)
  • Migration status for odr-padenc (- to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating odr-padenc would introduce bugs in testing: #1033127
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odr-padenc.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 230 days old (needed 5 days)
• ruby-kdl (- to 1.0.3-1)
  • Migration status for ruby-kdl (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-kdl.html
    • autopkgtest for ruby-kdl/1.0.3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 231 days old (needed 5 days)
• openjdk-19 (- to 19.0.2+7-4)
  • Migration status for openjdk-19 (- to 19.0.2+7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-19 would introduce bugs in testing: #1016376, #1042582
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-19.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-19/19.0.2+7-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 232 days old (needed 5 days)
• binutils-msp430 (- to 2.40.50~ti1)
  • Migration status for binutils-msp430 (- to 2.40.50~ti1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-msp430 would introduce bugs in testing: #1042343
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-msp430.html
    • 235 days old (needed 5 days)
• printrun (- to 2.0.1-1)
  • Migration status for printrun (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating printrun would introduce bugs in testing: #1050157
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/printrun.html
    • autopkgtest for printrun/2.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 235 days old (needed 2 days)
• golang-github-traefik-yaegi (- to 0.15.1-2)
  • Migration status for golang-github-traefik-yaegi (- to 0.15.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-traefik-yaegi would introduce bugs in testing: #1052085
    • autopkgtest for golang-github-traefik-yaegi/0.15.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-traefik-yaegi.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 236 days old (needed 5 days)
• markdown-toc-el (- to 0.1.5-3)
  • Migration status for markdown-toc-el (- to 0.1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating markdown-toc-el would introduce bugs in testing: #1036359
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-toc-el.html
    • autopkgtest for markdown-toc-el/0.1.5-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible 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)
• looking-glass (- to 0+b6-1)
  • Migration status for looking-glass (- to 0+b6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): looking-glass obs-studio (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/looking-glass.html
    • Reproducible on amd64 - info ♻
    • 237 days old (needed 5 days)
• obs-gradient-source (- to 0.3.2-1)
  • Migration status for obs-gradient-source (- to 0.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): obs-gradient-source obs-studio (not considered)
    • Depends: obs-gradient-source obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-gradient-source.html
    • autopkgtest for obs-gradient-source/0.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 240 days old (needed 5 days)
• ruby-rack-session (- to 2.0.0-1)
  • Migration status for ruby-rack-session (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rack-session would introduce bugs in testing: #1027350
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-rack-session.html
    • ruby-rack-session unsatisfiable Build-Depends(-Arch) on amd64: ruby-rack (>= 3.0.0~)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 240 days old (needed 5 days)
• ruby-rackup (- to 2.1.0-1)
  • Migration status for ruby-rackup (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rackup would introduce bugs in testing: #1027339
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-rackup.html
    • ruby-rackup unsatisfiable Build-Depends(-Arch) on amd64: ruby-rack (>= 3.0.0~)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 240 days old (needed 5 days)
• brial (- to 1.2.12-1)
  • Migration status for brial (- to 1.2.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for brial/1.2.12-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: brial sagemath
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/brial.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 242 days old (needed 5 days)
• foxtrotgps (- to 1.2.2+bzr332-1)
  • Migration status for foxtrotgps (- to 1.2.2+bzr332-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): foxtrotgps libglade2 (not considered)
    • Depends: foxtrotgps libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foxtrotgps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 244 days old (needed 5 days)
• silx (- to 1.1.2+dfsg-2)
  • Migration status for silx (- to 1.1.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating silx would introduce bugs in testing: #1060318
    • autopkgtest for silx/1.1.2+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Ignored failure, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/silx.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 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, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 247 days old (needed 2 days)
• xserver-xorg-video-qxl (- to 0.1.6-1)
  • Migration status for xserver-xorg-video-qxl (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-qxl would introduce bugs in testing: #1042862
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-qxl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 247 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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ical.html
    • Reproducible on i386 - info ♻
    • 248 days old (needed 5 days)
• golang-github-gonvenience-ytbx (- to 1.4.4-1)
  • Migration status for golang-github-gonvenience-ytbx (- to 1.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by czchen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gonvenience-ytbx.html
    • autopkgtest for golang-github-gonvenience-ytbx/1.4.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 249 days old (needed 2 days)
• octave-database (- to 2.4.4-8)
  • Migration status for octave-database (- to 2.4.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-database would introduce bugs in testing: #1004158
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-database.html
    • autopkgtest for octave-database/2.4.4-8: 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
    • 249 days old (needed 2 days)
• octave-tisean (- to 0.2.3.hg.2021.11.29-1)
  • Migration status for octave-tisean (- to 0.2.3.hg.2021.11.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • octave-tisean/amd64 has unsatisfiable dependency
    • octave-tisean/mips64el has unsatisfiable dependency
    • Updating octave-tisean would introduce bugs in testing: #874116
    • missing build on armel
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/octave-tisean.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • 249 days old (needed 5 days)
• python-pyvmomi (- to 6.7.1-6)
  • Migration status for python-pyvmomi (- to 6.7.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyvmomi would introduce bugs in testing: #1052793
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyvmomi.html
    • 251 days old (needed 5 days)
• liboqs (- to 0.8.0-1)
  • Migration status for liboqs (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liboqs would introduce bugs in testing: #1000303
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liboqs.html
    • 252 days old (needed 5 days)
• webcamoid (- to 9.1.1-1)
  • Migration status for webcamoid (- to 9.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating webcamoid would introduce bugs in testing: #1053808
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webcamoid.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 252 days old (needed 5 days)
• wifite (- to 2.7.0-1)
  • Migration status for wifite (- to 2.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): wifite aircrack-ng (not considered)
    • Depends: wifite aircrack-ng (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wifite.html
    • autopkgtest for wifite/2.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 252 days old (needed 2 days)
• obs-source-clone (- to 0.1.4-1)
  • Migration status for obs-source-clone (- to 0.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-source-clone obs-studio (not considered)
    • Depends: obs-source-clone obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-source-clone.html
    • autopkgtest for obs-source-clone/0.1.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 253 days old (needed 5 days)
• pcb (- to 1:4.3.0-3)
  • Migration status for pcb (- to 1:4.3.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pcb gtkglext (not considered)
    • Depends: pcb gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 253 days old (needed 5 days)
• rust-hdrhistogram (- to 7.5.2-1)
  • Migration status for rust-hdrhistogram (- to 7.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-hdrhistogram would introduce bugs in testing: #1014034
    • autopkgtest for rust-hdrhistogram/7.5.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hdrhistogram.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 253 days old (needed 5 days)
• ruby-jekyll-remote-theme (- to 0.4.3-4)
  • Migration status for ruby-jekyll-remote-theme (- to 0.4.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-remote-theme would introduce bugs in testing: #1031548, #1032541
    • Build-Depends(-Arch): ruby-jekyll-remote-theme ruby-jekyll-github-metadata
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-remote-theme.html
    • autopkgtest for ruby-jekyll-remote-theme/0.4.3-4: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • 254 days old (needed 2 days)
• rust-minijinja (- to 0.34.0-1)
  • Migration status for rust-minijinja (- to 0.34.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-minijinja-dev/amd64 has unsatisfiable dependency
    • librust-minijinja-dev/arm64 has unsatisfiable dependency
    • librust-minijinja-dev/armel has unsatisfiable dependency
    • librust-minijinja-dev/armhf has unsatisfiable dependency
    • librust-minijinja-dev/i386 has unsatisfiable dependency
    • librust-minijinja-dev/mips64el has unsatisfiable dependency
    • librust-minijinja-dev/ppc64el has unsatisfiable dependency
    • librust-minijinja-dev/s390x has unsatisfiable dependency
    • Updating rust-minijinja would introduce bugs in testing: #1051615
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-minijinja.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 254 days old (needed 5 days)
• obs-command-source (- to 0.4.0-4)
  • Migration status for obs-command-source (- to 0.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-command-source obs-studio (not considered)
    • Depends: obs-command-source obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-command-source.html
    • autopkgtest for obs-command-source/0.4.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 255 days old (needed 5 days)
• obs-scene-as-transition (- to 1.1.0+20230419.ce423a3-2)
  • Migration status for obs-scene-as-transition (- to 1.1.0+20230419.ce423a3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-scene-as-transition obs-studio (not considered)
    • Depends: obs-scene-as-transition obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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.0+20230419.ce423a3-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 255 days old (needed 5 days)
• obs-source-copy (- to 0.2.2-7)
  • Migration status for obs-source-copy (- to 0.2.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-source-copy obs-studio (not considered)
    • Depends: obs-source-copy obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-source-copy.html
    • autopkgtest for obs-source-copy/0.2.2-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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 255 days old (needed 5 days)
• obs-vintage-filter (- to 1.0.0-2)
  • Migration status for obs-vintage-filter (- to 1.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-vintage-filter obs-studio (not considered)
    • Depends: obs-vintage-filter obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-vintage-filter.html
    • autopkgtest for obs-vintage-filter/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 ♻, ppc64el: 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 ♻
    • 255 days old (needed 5 days)
• prometheus-frr-exporter (- to 1.2.0-1)
  • Migration status for prometheus-frr-exporter (- to 1.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: prometheus-frr-exporter frr (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-frr-exporter.html
    • autopkgtest for prometheus-frr-exporter/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 255 days old (needed 2 days)
• ruby-ruby-magic-static (- to 0.6.0-2)
  • Migration status for ruby-ruby-magic-static (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-ruby-magic-static would introduce bugs in testing: #1052749
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ruby-magic-static.html
    • autopkgtest for ruby-ruby-magic-static/0.6.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 255 days old (needed 2 days)
• obs-3d-effect (- to 0.0.2-2)
  • Migration status for obs-3d-effect (- to 0.0.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-3d-effect obs-studio (not considered)
    • Depends: obs-3d-effect obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-3d-effect.html
    • autopkgtest for obs-3d-effect/0.0.2-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, ppc64el: 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 ♻
    • 256 days old (needed 5 days)
• php-lcobucci-clock (- to 3.1.0-2)
  • Migration status for php-lcobucci-clock (- to 3.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-lcobucci-clock/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 ♻, s390x: Regression or new test ♻
    • php-lcobucci-clock unsatisfiable Build-Depends(-Arch) on amd64: phpunit (>= 10)
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-lcobucci-clock.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 262 days old (needed 5 days)
• cadabra2 (- to 2.4.3.2-1.1)
  • Migration status for cadabra2 (- to 2.4.3.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cadabra2 would introduce bugs in testing: #1061319
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cadabra2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 271 days old (needed 5 days)
• php-algo26-idna-convert (- to 3.1.0-1)
  • Migration status for php-algo26-idna-convert (- to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-algo26-idna-convert/3.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 ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-algo26-idna-convert php-jakeasmith-http-build-url
    • Depends: php-algo26-idna-convert php-jakeasmith-http-build-url
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-algo26-idna-convert.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 272 days old (needed 5 days)
• php-jakeasmith-http-build-url (- to 1.0.1-1)
  • Migration status for php-jakeasmith-http-build-url (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-jakeasmith-http-build-url.html
    • autopkgtest for php-jakeasmith-http-build-url/1.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 273 days old (needed 2 days)
• php-league-uri (- to 6.8.0-1)
  • Migration status for php-league-uri (- to 6.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): php-league-uri php-league-uri-interfaces
    • Depends: php-league-uri php-league-uri-interfaces
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-league-uri.html
    • autopkgtest for php-league-uri/6.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 275 days old (needed 2 days)
• php-league-uri-interfaces (- to 2.3.0-1)
  • Migration status for php-league-uri-interfaces (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-league-uri-interfaces.html
    • autopkgtest for php-league-uri-interfaces/2.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 275 days old (needed 2 days)
• pyramid-jinja2 (- to 2.7+dfsg-1.3)
  • Migration status for pyramid-jinja2 (- to 2.7+dfsg-1.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyramid-jinja2 python-pyramid (not considered)
    • Depends: pyramid-jinja2 python-pyramid (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyramid-jinja2.html
    • autopkgtest for pyramid-jinja2/2.7+dfsg-1.3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 276 days old (needed 5 days)
• x2gothinclient (- to 1.5.0.1-10)
  • Migration status for x2gothinclient (- to 1.5.0.1-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: x2gothinclient x2goclient (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2gothinclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 280 days old (needed 5 days)
• scikit-fmm (- to 2022.08.15-4)
  • Migration status for scikit-fmm (- to 2022.08.15-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scikit-fmm would introduce bugs in testing: #1059647, #1061001
    • autopkgtest for scikit-fmm/2022.08.15-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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scikit-fmm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 282 days old (needed 5 days)
• ogmrip (- to 1.0.1-4)
  • Migration status for ogmrip (- to 1.0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/o/ogmrip.html
    • Depends: ogmrip gpac
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 284 days old (needed 5 days)
• puppetserver (- to 7.9.5-2)
  • Migration status for puppetserver (- to 7.9.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • puppetserver/amd64 has unsatisfiable dependency
    • puppetserver/arm64 has unsatisfiable dependency
    • Updating puppetserver would introduce bugs in testing: #1042314
    • Build-Depends(-Arch): puppetserver jruby-utils-clojure
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/puppetserver.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on i386 - info ♻
    • 287 days old (needed 5 days)
• ruby-ruby-openai (- to 3.7.0-2)
  • Migration status for ruby-ruby-openai (- to 3.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ruby-openai.html
    • autopkgtest for ruby-ruby-openai/3.7.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 287 days old (needed 5 days)
• sniproxy (- to 0.6.0-2.1)
  • Migration status for sniproxy (- to 0.6.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sniproxy would introduce bugs in testing: #999957
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sniproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 291 days old (needed 5 days)
• libanyevent-riperedis-perl (- to 0.48-1)
  • Migration status for libanyevent-riperedis-perl (- to 0.48-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by az, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libanyevent-riperedis-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 292 days old (needed 5 days)
• matomo-component-ini (- to 3.0.1-1)
  • Migration status for matomo-component-ini (- to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-component-ini.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 292 days old (needed 5 days)
• matomo-component-network (- to 2.0.1-1)
  • Migration status for matomo-component-network (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-component-network.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 292 days old (needed 5 days)
• matomo-device-detector (- to 6.1.1-1)
  • Migration status for matomo-device-detector (- to 6.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
    • Depends: matomo-device-detector php-spyc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-device-detector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 292 days old (needed 5 days)
• matomo-php-tracker (- to 3.1.3-1)
  • Migration status for matomo-php-tracker (- to 3.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-php-tracker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 292 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:
    • Updating regina-normal would introduce bugs in testing: #1037840
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/regina-normal.html
    • autopkgtest for regina-normal/7.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 294 days old (needed 2 days)
• rust-env-logger-0.7 (- to 0.7.1-4)
  • Migration status for rust-env-logger-0.7 (- to 0.7.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-env-logger-0.7 would introduce bugs in testing: #1054156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-env-logger-0.7.html
    • autopkgtest for rust-env-logger-0.7/0.7.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 297 days old (needed 2 days)
• less.php (- to 4.1.0-1)
  • Migration status for less.php (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/less.php.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 300 days old (needed 5 days)
• php-maxmind-web-service-common (- to 0.9.0-1)
  • Migration status for php-maxmind-web-service-common (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-maxmind-web-service-common.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 306 days old (needed 5 days)
• image-factory (- to 1.0.2-1.1)
  • Migration status for image-factory (- to 1.0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating image-factory would introduce bugs in testing: #1060982
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/image-factory.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 309 days old (needed 5 days)
• php-jshrink (- to 1.6.5-1)
  • Migration status for php-jshrink (- to 1.6.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-jshrink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 313 days old (needed 5 days)
• shadowsocks-libev (- to 3.3.5+ds-10)
  • Migration status for shadowsocks-libev (- to 3.3.5+ds-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shadowsocks-libev would introduce bugs in testing: #999965
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shadowsocks-libev.html
    • autopkgtest for shadowsocks-libev/3.3.5+ds-10: 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
    • 314 days old (needed 2 days)
• php-sparkline (- to 2.2.0-1)
  • Migration status for php-sparkline (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sparkline would introduce bugs in testing: #1034403
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sparkline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 317 days old (needed 5 days)
• php-spyc (- to 0.6.3-1)
  • Migration status for php-spyc (- to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-spyc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 317 days old (needed 5 days)
• puppet-module-voxpupuli-kmod (- to 3.2.0-1)
  • Migration status for puppet-module-voxpupuli-kmod (- to 3.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-voxpupuli-kmod.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 319 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ponyorm.html
    • autopkgtest for ponyorm/0.7.16+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 321 days old (needed 2 days)
• libjpeg9 (- to 1:9e-1)
  • Migration status for libjpeg9 (- to 1:9e-1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 333 days old (needed 5 days)
• opentk (- to 1.1.4c+dfsg-2.2)
  • Migration status for opentk (- to 1.1.4c+dfsg-2.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: opentk cecil (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opentk.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 336 days old (needed 5 days)
• gitlab-ci-multi-runner (- to 14.10.1-1)
  • Migration status for gitlab-ci-multi-runner (- to 14.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-ci-multi-runner would introduce bugs in testing: #1033480
    • gitlab-runner/amd64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/arm64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/mips64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/ppc64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/s390x has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • 337 days old (needed 5 days)
• ldaptive (- to 2.1.1+ds-1)
  • Migration status for ldaptive (- to 2.1.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jello, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldaptive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 343 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 ♻, s390x: Regression or new test ♻
    • Depends: searx-admin searx
  • 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 ♻
    • 349 days old (needed 5 days)
• igdiscover (- to 0.11-4)
  • Migration status for igdiscover (- to 0.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating igdiscover would introduce bugs in testing: #1032975
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/igdiscover.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for igdiscover/0.11-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• ganeti (- to 3.0.2-3)
  • Migration status for ganeti (- to 3.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ganeti would introduce bugs in testing: #1042264
    • Build-Depends(-Arch): ganeti haskell-regex-pcre
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganeti.html
    • autopkgtest for ganeti/3.0.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Ignored failure, ppc64el: Pass, s390x: Ignored failure
    • 353 days old (needed 5 days)
• emacs-helm-ag (- to 0.59-2)
  • Migration status for emacs-helm-ag (- to 0.59-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-helm-ag would introduce bugs in testing: #1057557
    • autopkgtest for emacs-helm-ag/0.59-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: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-helm-ag.html
    • Reproducible on i386 - info ♻
    • 358 days old (needed 5 days)
• debian-timeline (- to 46)
  • Migration status for debian-timeline (- to 46): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debian-timeline would introduce bugs in testing: #1032166
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-timeline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 359 days old (needed 5 days)
• pagure (- to 5.11.3+dfsg-2.1)
  • Migration status for pagure (- to 5.11.3+dfsg-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pagure trololio (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): pagure celery
    • Depends: pagure celery
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pagure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 360 days old (needed 5 days)
• python-klein (- to 21.8.0-2)
  • Migration status for python-klein (- to 21.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-klein would introduce bugs in testing: #1052869
    • autopkgtest for python-klein/21.8.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-klein.html
    • Reproducible on i386 - info ♻
    • 360 days old (needed 5 days)
• vart (- to 2.5-4)
  • Migration status for vart (- to 2.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vart would introduce bugs in testing: #1037882
    • Build-Depends(-Arch): vart xir
    • Build-Depends(-Arch): vart xrt
    • Depends: vart xir
    • Depends: vart xrt
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vart.html
    • 360 days old (needed 5 days)
• xrt (- to 202210.2.13.466+dfsg-8)
  • Migration status for xrt (- to 202210.2.13.466+dfsg-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xrt would introduce bugs in testing: #1037903
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrt.html
    • 360 days old (needed 5 days)
• qpid-proton-j (- to 0.34.0-1)
  • Migration status for qpid-proton-j (- to 0.34.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jello, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-proton-j.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 363 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: #1052855
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firmware-microbit-micropython.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 364 days old (needed 5 days)
• gdb-doc (- to 13.1-1)
  • Migration status for gdb-doc (- to 13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gdb-doc would introduce bugs in testing: #1057563
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 364 days old (needed 5 days)
• python-uflash (- to 1.2.4+dfsg-10)
  • Migration status for python-uflash (- to 1.2.4+dfsg-10): 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
    • Build-Depends(-Arch): python-uflash python-nudatus
    • Depends: python-uflash python-nudatus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-uflash.html
    • autopkgtest for python-uflash/1.2.4+dfsg-10: 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
    • 364 days old (needed 2 days)
• vertx-docgen (- to 0.9.4-2)
  • Migration status for vertx-docgen (- to 0.9.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vertx-docgen openjdk-11 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vertx-docgen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 364 days old (needed 5 days)
• zoneminder (- to 1.36.33+dfsg1-1)
  • Migration status for zoneminder (- to 1.36.33+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zoneminder would introduce bugs in testing: #999919
    • Depends: zoneminder libjwt
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zoneminder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 364 days old (needed 5 days)
• kotlin (- to 1.3.31+ds1-1)
  • Migration status for kotlin (- to 1.3.31+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kotlin android-platform-tools-base (not considered)
    • Invalidated by build-dependency
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 365 days old (needed 5 days)
• poliastro (- to 0.17.0-2)
  • Migration status for poliastro (- to 0.17.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for poliastro/0.17.0-2: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): poliastro astroquery
    • Build-Depends(-Arch): poliastro numba
    • Depends: poliastro astroquery
    • Depends: poliastro numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poliastro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 365 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
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/fava.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on i386 - info ♻
    • 366 days old (needed 5 days)
• golang-github-crewjam-saml (- to 0.4.12-2)
  • Migration status for golang-github-crewjam-saml (- to 0.4.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-crewjam-saml would introduce bugs in testing: #1033753, #1033864, #1054223
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-crewjam-saml.html
    • autopkgtest for golang-github-crewjam-saml/0.4.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 366 days old (needed 2 days)
• obs-scene-collection-manager (- to 0.0.8-4)
  • Migration status for obs-scene-collection-manager (- to 0.0.8-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): obs-scene-collection-manager obs-studio (not considered)
    • Depends: obs-scene-collection-manager obs-studio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-scene-collection-manager.html
    • autopkgtest for obs-scene-collection-manager/0.0.8-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 366 days old (needed 5 days)
• 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, 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 ♻
    • 367 days old (needed 5 days)
• quickjs (- to 2021.03.27-1)
  • Migration status for quickjs (- to 2021.03.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quickjs would introduce bugs in testing: #1031074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickjs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 367 days old (needed 5 days)
• oregano (- to 0.84.41+dfsg.1-1.1)
  • Migration status for oregano (- to 0.84.41+dfsg.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oregano would introduce bugs in testing: #1051281
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oregano.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 369 days old (needed 5 days)
• simplescreenrecorder (- to 0.4.4-3)
  • Migration status for simplescreenrecorder (- to 0.4.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simplescreenrecorder would introduce bugs in testing: #1040375
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplescreenrecorder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 370 days old (needed 5 days)
• afnix (- to 3.8.0-1)
  • Migration status for afnix (- to 3.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating afnix would introduce bugs in testing: #1031749, #1037570
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/afnix.html
    • 372 days old (needed 5 days)
• facet-analyser (- to 0.0~git20221121142040.6be10b8+ds1-3)
  • Migration status for facet-analyser (- to 0.0~git20221121142040.6be10b8+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • facet-analyser/amd64 has unsatisfiable dependency
    • Updating facet-analyser would introduce bugs in testing: #1040334
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/facet-analyser.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 373 days old (needed 5 days)
• silver-platter (- to 0.5.6-2)
  • Migration status for silver-platter (- to 0.5.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating silver-platter would introduce bugs in testing: #1058249
    • Build-Depends(-Arch): silver-platter lintian-brush
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/silver-platter.html
    • autopkgtest for silver-platter/0.5.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 373 days old (needed 2 days)
• ognibuild (- to 0.0.18+git20230208.1.9b890a2-1)
  • Migration status for ognibuild (- to 0.0.18+git20230208.1.9b890a2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ognibuild/0.0.18+git20230208.1.9b890a2-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ognibuild.html
    • 376 days old (needed 5 days)
• python-pynndescent (- to 0.5.8-2)
  • Migration status for python-pynndescent (- to 0.5.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pynndescent would introduce bugs in testing: #1057598
    • Build-Depends(-Arch): python-pynndescent numba
    • Depends: python-pynndescent numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pynndescent.html
    • autopkgtest for python-pynndescent/0.5.8-2: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 376 days old (needed 2 days)
• rust-ripasso-cursive (- to 0.6.1-2)
  • Migration status for rust-ripasso-cursive (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ripasso-cursive would introduce bugs in testing: #1056253
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1+deb12u1/amd64
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1+deb12u1/mips64el
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/arm64
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/armel
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/armhf
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/i386
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/ppc64el
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ripasso-cursive.html
    • 377 days old (needed 5 days)
• dogtag-pki (- to 11.2.1-2)
  • Migration status for dogtag-pki (- to 11.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pki-server/amd64 has unsatisfiable dependency
    • pki-server/arm64 has unsatisfiable dependency
    • pki-server/armel has unsatisfiable dependency
    • pki-server/armhf has unsatisfiable dependency
    • pki-server/i386 has unsatisfiable dependency
    • pki-server/mips64el has unsatisfiable dependency
    • pki-server/ppc64el has unsatisfiable dependency
    • pki-server/s390x has unsatisfiable dependency
    • Updating dogtag-pki would introduce bugs in testing: #1054480
    • Build-Depends(-Arch): dogtag-pki tomcatjss
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/dogtag-pki.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 378 days old (needed 5 days)
• php-horde-wicked (- to 2.0.8-9)
  • Migration status for php-horde-wicked (- to 2.0.8-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-wicked php-horde-rpc (not considered)
    • Invalidated by dependency
    • Depends: php-horde-wicked php-horde
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-wicked.html
    • autopkgtest for php-horde-wicked/2.0.8-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 378 days old (needed 2 days)
• pytorch-audio (- to 0.13.1-1)
  • Migration status for pytorch-audio (- to 0.13.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pytorch-audio pytorch (not considered)
    • Depends: pytorch-audio pytorch (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/p/pytorch-audio.html
    • autopkgtest for pytorch-audio/0.13.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 378 days old (needed 2 days)
• invesalius (- to 3.1.99998-4)
  • Migration status for invesalius (- to 3.1.99998-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: invesalius pytorch (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/invesalius.html
    • autopkgtest for invesalius/3.1.99998-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 379 days old (needed 5 days)
• mu-editor (- to 1.0.3+dfsg-6)
  • Migration status for mu-editor (- to 1.0.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): mu-editor python-uflash (not considered)
    • Depends: mu-editor python-uflash (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): mu-editor python-nudatus
    • Depends: mu-editor python-nudatus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mu-editor.html
    • autopkgtest for mu-editor/1.0.3+dfsg-6: 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
    • 379 days old (needed 2 days)
• ruby-jekyll-github-metadata (- to 2.15.0-1)
  • Migration status for ruby-jekyll-github-metadata (- to 2.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-github-metadata would introduce bugs in testing: #1037529, #1059710
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-github-metadata.html
    • autopkgtest for ruby-jekyll-github-metadata/2.15.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 379 days old (needed 2 days)
• bambootracker (- to 0.6.1-1)
  • Migration status for bambootracker (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bambootracker would introduce bugs in testing: #1051573
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bambootracker.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 380 days old (needed 5 days)
• haskell-raaz (- to 0.2.1-2.1)
  • Migration status for haskell-raaz (- to 0.2.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-raaz-dev/amd64 has unsatisfiable dependency
    • libghc-raaz-doc/amd64 has unsatisfiable dependency
    • libghc-raaz-prof/amd64 has unsatisfiable dependency
    • libghc-raaz-dev/arm64 has unsatisfiable dependency
    • libghc-raaz-doc/arm64 has unsatisfiable dependency
    • libghc-raaz-prof/arm64 has unsatisfiable dependency
    • libghc-raaz-dev/armel has unsatisfiable dependency
    • libghc-raaz-prof/armel has unsatisfiable dependency
    • libghc-raaz-dev/armhf has unsatisfiable dependency
    • libghc-raaz-prof/armhf has unsatisfiable dependency
    • libghc-raaz-dev/i386 has unsatisfiable dependency
    • libghc-raaz-prof/i386 has unsatisfiable dependency
    • libghc-raaz-dev/mips64el has unsatisfiable dependency
    • libghc-raaz-prof/mips64el has unsatisfiable dependency
    • libghc-raaz-dev/ppc64el has unsatisfiable dependency
    • libghc-raaz-prof/ppc64el has unsatisfiable dependency
    • libghc-raaz-dev/s390x has unsatisfiable dependency
    • libghc-raaz-prof/s390x has unsatisfiable dependency
    • Updating haskell-raaz would introduce bugs in testing: #1053980, #1054978
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-raaz.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 380 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:
    • Updating sagemath would introduce bugs in testing: #1042683, #1042935, #1050182, #1052051, #1056885
    • Build-Depends(-Arch): sagemath brial
    • Build-Depends(-Arch): sagemath flint-arb
    • Build-Depends(-Arch): sagemath pplpy
    • Depends: sagemath brial
    • Depends: sagemath flint
    • Depends: sagemath flint-arb
    • Depends: sagemath pplpy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagemath.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for sagemath/9.5-6: amd64: Pass, arm64: Pass, i386: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 380 days old (needed 2 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:
    • Updating segyio would introduce bugs in testing: #1055728
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/segyio.html
    • autopkgtest for segyio/1.8.3-1.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 380 days old (needed 2 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
    • Build-Depends(-Arch): hyperspy python-sparse
    • Depends: hyperspy numba
    • Depends: hyperspy python-sparse
  • 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 ♻
    • 381 days old (needed 5 days)
• openems (- to 0.0.35+git20190103.6a75e98+dfsg.1-3.2)
  • Migration status for openems (- to 0.0.35+git20190103.6a75e98+dfsg.1-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openems would introduce bugs in testing: #1054794, #1056826
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openems.html
    • autopkgtest for openems/0.0.35+git20190103.6a75e98+dfsg.1-3.2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 381 days old (needed 5 days)
• ruby-gitlab-markup (- to 1.9.0-1)
  • Migration status for ruby-gitlab-markup (- to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-markup would introduce bugs in testing: #1053838
    • Build-Depends(-Arch): ruby-gitlab-markup ruby-html-pipeline
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-markup.html
    • autopkgtest for ruby-gitlab-markup/1.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 381 days old (needed 2 days)
• ruby-gruff (- to 0.6.0-2)
  • Migration status for ruby-gruff (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gruff would introduce bugs in testing: #1054733
    • autopkgtest for ruby-gruff/0.6.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gruff.html
    • Reproducible on i386 - info ♻
    • 381 days old (needed 5 days)
• python-aioxmpp (- to 0.13.3-1)
  • Migration status for python-aioxmpp (- to 0.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioxmpp would introduce bugs in testing: #1042239
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioxmpp.html
    • Reproducible on i386 - info ♻
    • 382 days old (needed 5 days)
• python-anndata (- to 0.8.0-4)
  • Migration status for python-anndata (- to 0.8.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-anndata would introduce bugs in testing: #1044072
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/python-anndata.html
  • Additional info:
    • autopkgtest for python-anndata/0.8.0-4: 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
    • 383 days old (needed 2 days)
• ubertooth (- to 2018.12.R1-5.1)
  • Migration status for ubertooth (- to 2018.12.R1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ubertooth would introduce bugs in testing: #1054741
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ubertooth.html
    • autopkgtest for ubertooth/2018.12.R1-5.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 383 days old (needed 2 days)
• freesas (- to 0.9.0-6)
  • Migration status for freesas (- to 0.9.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): freesas silx (not considered)
    • Depends: freesas silx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): freesas pyfai
    • Depends: freesas pyfai
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freesas.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 384 days old (needed 5 days)
• haskell-diagrams (- to 1.4.0.1-1)
  • Migration status for haskell-diagrams (- to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-diagrams would introduce bugs in testing: #1057716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-diagrams.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 384 days old (needed 5 days)
• openfpgaloader (- to 0.10.0+git20230202-edea24f-1)
  • Migration status for openfpgaloader (- to 0.10.0+git20230202-edea24f-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openfpgaloader would introduce bugs in testing: #1037802
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openfpgaloader.html
    • Reproducible on i386 - info ♻
    • 384 days old (needed 5 days)
• php-horde-imp (- to 6.2.27-3)
  • Migration status for php-horde-imp (- to 6.2.27-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-imp would introduce bugs in testing: #1038441, #1064391
    • Depends: php-horde-imp php-horde
    • Depends: php-horde-imp php-horde-editor
    • Depends: php-horde-imp php-horde-mail-autoconfig
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imp.html
    • autopkgtest for php-horde-imp/6.2.27-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 384 days old (needed 2 days)
• scmutils (- to 0~20230125+dfsg-1)
  • Migration status for scmutils (- to 0~20230125+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): scmutils mit-scheme (not considered)
    • Depends: scmutils mit-scheme (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scmutils.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 384 days old (needed 5 days)
• swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-3)
  • Migration status for swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swift-im would introduce bugs in testing: #1032724, #1056100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swift-im.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • 384 days old (needed 5 days)
• android-platform-tools-base (- to 2.2.2-4)
  • Migration status for android-platform-tools-base (- to 2.2.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-tools-base would introduce bugs in testing: #1058331
    • Build-Depends(-Arch): android-platform-tools-base android-platform-frameworks-data-binding
    • Build-Depends(-Arch): android-platform-tools-base android-platform-tools-analytics-library
    • Depends: android-platform-tools-base android-platform-frameworks-data-binding
    • Depends: android-platform-tools-base android-platform-tools-analytics-library
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-tools-base.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 385 days old (needed 5 days)
• kotlinx-atomicfu (- to 0.11.12-2)
  • Migration status for kotlinx-atomicfu (- to 0.11.12-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 385 days old (needed 5 days)
• kotlinx-coroutines (- to 1.0.1-2)
  • Migration status for kotlinx-coroutines (- to 1.0.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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 ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 385 days old (needed 5 days)
• polyml (- to 5.7.1-5)
  • Migration status for polyml (- to 5.7.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating polyml would introduce bugs in testing: #1033835
    • autopkgtest for polyml/5.7.1-5: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polyml.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 385 days old (needed 5 days)
• propellor (- to 5.13-3)
  • Migration status for propellor (- to 5.13-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-propellor-dev/amd64 has unsatisfiable dependency
    • libghc-propellor-doc/amd64 has unsatisfiable dependency
    • libghc-propellor-prof/amd64 has unsatisfiable dependency
    • libghc-propellor-dev/arm64 has unsatisfiable dependency
    • libghc-propellor-doc/arm64 has unsatisfiable dependency
    • libghc-propellor-prof/arm64 has unsatisfiable dependency
    • libghc-propellor-dev/armel has unsatisfiable dependency
    • libghc-propellor-prof/armel has unsatisfiable dependency
    • libghc-propellor-dev/armhf has unsatisfiable dependency
    • libghc-propellor-prof/armhf has unsatisfiable dependency
    • libghc-propellor-dev/i386 has unsatisfiable dependency
    • libghc-propellor-prof/i386 has unsatisfiable dependency
    • libghc-propellor-dev/mips64el has unsatisfiable dependency
    • libghc-propellor-prof/mips64el has unsatisfiable dependency
    • libghc-propellor-dev/ppc64el has unsatisfiable dependency
    • libghc-propellor-prof/ppc64el has unsatisfiable dependency
    • libghc-propellor-dev/s390x has unsatisfiable dependency
    • libghc-propellor-prof/s390x has unsatisfiable dependency
    • Updating propellor would introduce bugs in testing: #1053981, #1054640, #1054828
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/propellor.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on i386 - info ♻
    • 385 days old (needed 5 days)
• aiohttp-jinja2 (- to 1.5.1-1)
  • Migration status for aiohttp-jinja2 (- to 1.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiohttp-jinja2 would introduce bugs in testing: #1061008
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiohttp-jinja2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 386 days old (needed 5 days)
• android-platform-frameworks-data-binding (- to 2.2.2-6)
  • Migration status for android-platform-frameworks-data-binding (- to 2.2.2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): android-platform-frameworks-data-binding android-platform-tools-base (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-frameworks-data-binding.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 386 days old (needed 5 days)
• azure-devops-cli-extension (- to 0.26.0-1)
  • Migration status for azure-devops-cli-extension (- to 0.26.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): azure-devops-cli-extension azure-cli (not considered)
    • Depends: azure-devops-cli-extension azure-cli (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/azure-devops-cli-extension.html
    • autopkgtest for azure-devops-cli-extension/0.26.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 387 days old (needed 2 days)
• gnome-photos (- to 43.0-2)
  • Migration status for gnome-photos (- to 43.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-photos would introduce bugs in testing: #1040202, #1040746
    • autopkgtest for gnome-photos/43.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-photos.html
    • Reproducible on i386 - info ♻
    • 387 days old (needed 5 days)
• gradle-kotlin-dsl (- to 0.13.2-5)
  • Migration status for gradle-kotlin-dsl (- to 0.13.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • 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 armhf - info ♻
    • Reproducible on i386 - info ♻
    • 387 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:
    • Updating pyhst2 would introduce bugs in testing: #1036680, #1056840
    • Impossible Depends: pyhst2 -> libcublas11/11.11.3.6~11.8.0-5/amd64
    • Impossible Depends: pyhst2 -> libcudart11.0/11.8.89~11.8.0-5/amd64
    • Impossible Depends: pyhst2 -> libcufft10/11.1.1+~10.9.0.58~11.8.0-5/amd64
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 387 days old (needed 5 days)
• ruby-moneta (- to 1.5.2-1)
  • Migration status for ruby-moneta (- to 1.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-moneta would introduce bugs in testing: #1033316
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-moneta.html
    • autopkgtest for ruby-moneta/1.5.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 388 days old (needed 2 days)
• varnish-vmod-digest (- to 6.4+20220108-1)
  • Migration status for varnish-vmod-digest (- to 6.4+20220108-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): varnish-vmod-digest varnish (not considered)
    • Depends: varnish-vmod-digest varnish (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/v/varnish-vmod-digest.html
    • autopkgtest for varnish-vmod-digest/6.4+20220108-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 388 days old (needed 2 days)
• hyperkitty (- to 1.3.7-1)
  • Migration status for hyperkitty (- to 1.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-django-hyperkitty/amd64 has unsatisfiable dependency
    • python3-django-hyperkitty/arm64 has unsatisfiable dependency
    • Updating hyperkitty would introduce bugs in testing: #1052805
    • hyperkitty unsatisfiable Build-Depends(-Arch) on amd64: python3-django (<< 3:4.2)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/hyperkitty.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 389 days old (needed 5 days)
• openmotor (- to 0.5.0-2)
  • Migration status for openmotor (- 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): openmotor scikit-fmm (not considered)
    • Depends: openmotor scikit-fmm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmotor.html
    • autopkgtest for openmotor/0.5.0-2: 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
    • 389 days old (needed 2 days)
• psi4 (- to 1:1.3.2+dfsg-5)
  • Migration status for psi4 (- to 1:1.3.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for psi4/1:1.3.2+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): psi4 chemps2
    • Depends: psi4 chemps2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psi4.html
    • 389 days old (needed 5 days)
• binutils-m68hc1x (- to 1:3.5.0)
  • Migration status for binutils-m68hc1x (- to 1:3.5.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-m68hc1x would introduce bugs in testing: #1042317
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-m68hc1x.html
    • 390 days old (needed 5 days)
• mikutter (- to 5.0.4+dfsg1-2)
  • Migration status for mikutter (- to 5.0.4+dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mikutter ruby-moneta (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mikutter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 390 days old (needed 5 days)
• mvdsv (- to 0.35-6)
  • Migration status for mvdsv (- to 0.35-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mvdsv would introduce bugs in testing: #1050187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mvdsv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 390 days old (needed 5 days)
• php-horde (- to 5.2.23+debian0-6)
  • Migration status for php-horde (- to 5.2.23+debian0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde php-horde-rpc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 391 days old (needed 5 days)
• ktx (- to 1.42+dfsg-3)
  • Migration status for ktx (- to 1.42+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ktx mvdsv (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 392 days old (needed 5 days)
• magic-wormhole-mailbox-server (- to 0.4.1-2)
  • Migration status for magic-wormhole-mailbox-server (- to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating magic-wormhole-mailbox-server would introduce bugs in testing: #1058173
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magic-wormhole-mailbox-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 392 days old (needed 5 days)
    • Remove hint for (transitive) dependency: magic-wormhole-mailbox-server
• ruby-riddle (- to 2.4.2-3)
  • Migration status for ruby-riddle (- to 2.4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-riddle would introduce bugs in testing: #1033369
    • autopkgtest for ruby-riddle/2.4.2-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ruby-riddle/blocked-on-ci-infra: armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-riddle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 392 days old (needed 5 days)
• php-horde-passwd (- to 5.0.7-9)
  • Migration status for php-horde-passwd (- to 5.0.7-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-passwd php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-passwd.html
    • autopkgtest for php-horde-passwd/5.0.7-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 393 days old (needed 2 days)
• sepp (- to 4.5.1+really4.5.1+dfsg-5)
  • Migration status for sepp (- to 4.5.1+really4.5.1+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sepp/4.5.1+really4.5.1+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻
    • Build-Depends(-Arch): sepp pplacer
    • Depends: sepp pplacer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sepp.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 394 days old (needed 5 days)
• android-sdk-meta (- to 28.0.2+9)
  • Migration status for android-sdk-meta (- to 28.0.2+9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: android-sdk-meta android-platform-build (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-sdk-meta.html
    • autopkgtest for android-sdk-meta/28.0.2+9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 395 days old (needed 2 days)
• eviacam (- to 2.1.4-2.1)
  • Migration status for eviacam (- to 2.1.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eviacam would introduce bugs in testing: #1033052
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eviacam.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• lava (- to 2023.01-2)
  • Migration status for lava (- to 2023.01-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lava would introduce bugs in testing: #1041342
    • autopkgtest for lava/2023.01-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Depends: lava celery
    • Depends: lava djangorestframework-filters
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lava.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• python-pgpy (- to 0.6.0-1)
  • Migration status for python-pgpy (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pgpy would introduce bugs in testing: #1042703
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pgpy.html
    • autopkgtest for python-pgpy/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 395 days old (needed 2 days)
• resampy (- to 0.4.2+ds-3)
  • Migration status for resampy (- to 0.4.2+ds-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): resampy numba (not considered)
    • Depends: resampy numba (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resampy.html
    • autopkgtest for resampy/0.4.2+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 395 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:
    • Piuparts tested OK - 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
    • Reproducible on i386 - info ♻
    • 396 days old (needed 5 days)
• sfepy (- to 2021.4-4)
  • Migration status for sfepy (- to 2021.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sfepy would introduce bugs in testing: #1056887
    • Build-Depends(-Arch): sfepy python-sparse
    • Depends: sfepy python-sparse
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfepy.html
    • autopkgtest for sfepy/2021.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 396 days old (needed 2 days)
• glirc (- to 2.39.0.1-1)
  • Migration status for glirc (- to 2.39.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glirc would introduce bugs in testing: #1054966
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-vty-dev (<< 5.36)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glirc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 397 days old (needed 5 days)
• ruby-github-markup (- to 1.7.0+dfsg-6)
  • Migration status for ruby-github-markup (- to 1.7.0+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-github-markup would introduce bugs in testing: #1053839
    • Build-Depends(-Arch): ruby-github-markup ruby-html-pipeline
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-github-markup.html
    • autopkgtest for ruby-github-markup/1.7.0+dfsg-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 397 days old (needed 2 days)
• darcs (- to 2.16.5-1)
  • Migration status for darcs (- to 2.16.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating darcs would introduce bugs in testing: #1054953
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/darcs.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 398 days old (needed 5 days)
• gtk-sharp3 (- to 2.99.3-4.1)
  • Migration status for gtk-sharp3 (- to 2.99.3-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtk-sharp3 would introduce bugs in testing: #1017897
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-sharp3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 398 days old (needed 5 days)
• pglistener (- to 5.0-2)
  • Migration status for pglistener (- to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pglistener libnss-db (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pglistener.html
    • autopkgtest for pglistener/5.0-2: 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
    • 398 days old (needed 2 days)
• scrcpy (- to 1.25-1)
  • Migration status for scrcpy (- to 1.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scrcpy would introduce bugs in testing: #1050097
    • autopkgtest for scrcpy/1.25-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends-Indep: scrcpy android-framework-23
    • Build-Depends-Indep: scrcpy android-sdk-meta
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrcpy.html
    • 398 days old (needed 5 days)
• clazy (- to 1.11-4)
  • Migration status for clazy (- to 1.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clazy would introduce bugs in testing: #1051858
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clazy.html
    • autopkgtest for clazy/1.11-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 400 days old (needed 2 days)
• relion-cuda (- to 3.1.3-2)
  • Migration status for relion-cuda (- to 3.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating relion-cuda would introduce bugs in testing: #1036681, #1040128
    • Impossible Depends: relion-cuda -> libcufft10/11.1.1+~10.9.0.58~11.8.0-5/amd64
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for relion-cuda/3.1.3-2: amd64: No tests, superficial or marked flaky ♻
    • 400 days old (needed 5 days)
• scm (- to 5f3-4)
  • Migration status for scm (- to 5f3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scm would introduce bugs in testing: #1057602
    • Build-Depends(-Arch): scm slib
    • Depends: scm slib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scm.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 401 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-ultisnips.html
    • autopkgtest for vim-ultisnips/3.2-2: 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
    • 402 days old (needed 2 days)
• cumin (- to 4.2.0-1)
  • Migration status for cumin (- to 4.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cumin would introduce bugs in testing: #1042262
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cumin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 405 days old (needed 5 days)
• varnish (- to 7.1.1-1.1)
  • Migration status for varnish (- to 7.1.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating varnish would introduce bugs in testing: #1054484, #1056156
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/v/varnish.html
  • Additional info:
    • autopkgtest for varnish/7.1.1-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 406 days old (needed 2 days)
• jacal (- to 1c8-1)
  • Migration status for jacal (- to 1c8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: jacal slib (not considered)
    • Invalidated by dependency
    • Depends: jacal scm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jacal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 407 days old (needed 5 days)
• mit-scheme (- to 12.1-3)
  • Migration status for mit-scheme (- to 12.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mit-scheme would introduce bugs in testing: #1057426
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mit-scheme.html
    • 407 days old (needed 5 days)
• php-smbclient (- to 1.0.6-8)
  • Migration status for php-smbclient (- to 1.0.6-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-smbclient would introduce bugs in testing: #1035516
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-smbclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 407 days old (needed 5 days)
• apbs (- to 3.4.1-5)
  • Migration status for apbs (- to 3.4.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apbs would introduce bugs in testing: #1033528
    • autopkgtest for apbs/3.4.1-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for apbs/blocked-on-ci-infra: armel: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apbs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 408 days old (needed 5 days)
• xraylib (- to 4.0.0+dfsg1-3)
  • Migration status for xraylib (- to 4.0.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xraylib would introduce bugs in testing: #1042221
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xraylib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 408 days old (needed 5 days)
• gbrainy (- to 1:2.4.6-1)
  • Migration status for gbrainy (- to 1: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): gbrainy gtk-sharp3 (not considered)
    • Depends: gbrainy gtk-sharp3 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gbrainy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 409 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)
    • 409 days old (needed 5 days)
• libobjcryst (- to 2022.1.4+ds1-2)
  • Migration status for libobjcryst (- to 2022.1.4+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libobjcryst newmat (not considered)
    • Depends: libobjcryst newmat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): libobjcryst cctbx
    • Depends: libobjcryst cctbx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobjcryst.html
    • autopkgtest for libobjcryst/2022.1.4+ds1-2: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 410 days old (needed 2 days)
• pyobjcryst (- to 2.2.5-1)
  • Migration status for pyobjcryst (- to 2.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyobjcryst libobjcryst (not considered)
    • Depends: pyobjcryst libobjcryst (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyobjcryst.html
    • autopkgtest for pyobjcryst/2.2.5-1: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 410 days old (needed 2 days)
• stimfit (- to 0.16.0-1.2)
  • Migration status for stimfit (- to 0.16.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): stimfit sip4 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stimfit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 410 days old (needed 5 days)
• python-clickhouse-driver (- to 0.2.5-1)
  • Migration status for python-clickhouse-driver (- to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-clickhouse-driver would introduce bugs in testing: #1041206
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-clickhouse-driver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 411 days old (needed 5 days)
• php-mailparse (- to 3.1.4+2.1.7~dev20160128-1)
  • Migration status for php-mailparse (- to 3.1.4+2.1.7~dev20160128-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-mailparse would introduce bugs in testing: #999998
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mailparse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• php-mongodb (- to 1.15.0+1.11.1+1.9.2+1.7.5-1)
  • Migration status for php-mongodb (- to 1.15.0+1.11.1+1.9.2+1.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-mongodb would introduce bugs in testing: #999997
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mongodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• closql-el (- to 1.2.1-3)
  • Migration status for closql-el (- to 1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating closql-el would introduce bugs in testing: #1052943
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/closql-el.html
    • autopkgtest for closql-el/1.2.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 413 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)
    • 413 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)
    • 413 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)
    • 413 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)
    • 413 days old (needed 5 days)
• php-horde-sesha (- to 1.0.0~rc3-9)
  • Migration status for php-horde-sesha (- to 1.0.0~rc3-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-sesha php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-sesha.html
    • autopkgtest for php-horde-sesha/1.0.0~rc3-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 413 days old (needed 2 days)
• python-workalendar (- to 17.0.0-1)
  • Migration status for python-workalendar (- to 17.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-workalendar would introduce bugs in testing: #1060939
    • autopkgtest for python-workalendar/17.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-workalendar.html
    • Reproducible on armhf - info ♻
    • 413 days old (needed 5 days)
• tycho (- to 1.6.0-3)
  • Migration status for tycho (- to 1.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libtycho-java/amd64 has unsatisfiable dependency
    • libtycho-java/arm64 has unsatisfiable dependency
    • Updating tycho would introduce bugs in testing: #1031686, #1033428, #1050407
    • tycho unsatisfiable Build-Depends(-Arch) on amd64: libeclipse-osgi-util-java
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tycho.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 413 days old (needed 5 days)
• nuitka (- to 1.3.5+ds-1)
  • Migration status for nuitka (- to 1.3.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nuitka would introduce bugs in testing: #1030440, #1035782
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nuitka.html
    • Reproducible on i386 - info ♻
    • 414 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)
    • 414 days old (needed 5 days)
• php-horde-turba (- to 4.2.29-2)
  • Migration status for php-horde-turba (- to 4.2.29-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-turba would introduce bugs in testing: #1064392
    • Depends: php-horde-turba php-horde
    • Depends: php-horde-turba php-horde-dav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-turba.html
    • autopkgtest for php-horde-turba/4.2.29-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible 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)
• ruby-html-pipeline (- to 2.14.3-1)
  • Migration status for ruby-html-pipeline (- to 2.14.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-html-pipeline would introduce bugs in testing: #1053837
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-html-pipeline.html
    • autopkgtest for ruby-html-pipeline/2.14.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible 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)
• ruby-task-list (- to 2.3.2-2)
  • Migration status for ruby-task-list (- to 2.3.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-task-list ruby-html-pipeline (not considered)
    • Depends: ruby-task-list ruby-html-pipeline (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-task-list.html
    • autopkgtest for ruby-task-list/2.3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible 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)
• php-horde-ingo (- to 3.2.16-9)
  • Migration status for php-horde-ingo (- to 3.2.16-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-ingo php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ingo.html
    • autopkgtest for php-horde-ingo/3.2.16-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible 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)
• tetradraw (- to 2.0.3-10)
  • Migration status for tetradraw (- to 2.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tetradraw would introduce bugs in testing: #1057594
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tetradraw.html
    • 415 days old (needed 5 days)
• php-horde-kronolith (- to 4.2.29-3)
  • Migration status for php-horde-kronolith (- to 4.2.29-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kronolith would introduce bugs in testing: #1054531
    • Depends: php-horde-kronolith php-horde
    • Depends: php-horde-kronolith php-horde-dav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kronolith.html
    • autopkgtest for php-horde-kronolith/4.2.29-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 416 days old (needed 2 days)
• ruby-gh (- to 0.18.0-5)
  • Migration status for ruby-gh (- to 0.18.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-gh/amd64 has unsatisfiable dependency
    • ruby-gh/arm64 has unsatisfiable dependency
    • Updating ruby-gh would introduce bugs in testing: #1025090
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gh.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 416 days old (needed 5 days)
• emacspeak-ss (- to 1.12.1-9)
  • Migration status for emacspeak-ss (- to 1.12.1-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: emacspeak-ss emacspeak (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/emacspeak-ss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• safeclib (- to 3.7.1-2)
  • Migration status for safeclib (- to 3.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating safeclib would introduce bugs in testing: #1042344
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/safeclib.html
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• flask-autoindex (- to 0.6.6-3)
  • Migration status for flask-autoindex (- to 0.6.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-autoindex would introduce bugs in testing: #1058997
    • Build-Depends(-Arch): flask-autoindex python-future
    • Depends: flask-autoindex python-future
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-autoindex.html
    • autopkgtest for flask-autoindex/0.6.6-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 418 days old (needed 5 days)
• golang-github-google-cel-go (- to 0.12.5+ds-1)
  • Migration status for golang-github-google-cel-go (- to 0.12.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-google-cel-go/0.12.5+ds-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-google-cel-go.html
    • 419 days old (needed 5 days)
• openstack-meta-packages (- to 0.34)
  • Migration status for openstack-meta-packages (- to 0.34): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openstack-clients/amd64 has unsatisfiable dependency
    • openstack-clients/arm64 has unsatisfiable dependency
    • Depends: openstack-meta-packages heat
    • Depends: openstack-meta-packages nova
    • Depends: openstack-meta-packages placement
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openstack-meta-packages.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 420 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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-vobject.html
    • Reproducible on i386 - info ♻
    • 420 days old (needed 5 days)
• tiemu (- to 3.04~git20220826.cda2db4+dfsg-2)
  • Migration status for tiemu (- to 3.04~git20220826.cda2db4+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tiemu libglade2 (not considered)
    • Depends: tiemu libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiemu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 420 days old (needed 5 days)
• eclipse-collections (- to 11.0.0.M3-3)
  • Migration status for eclipse-collections (- to 11.0.0.M3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eclipse-collections would introduce bugs in testing: #1031467
    • Build-Depends(-Arch): eclipse-collections tycho
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-collections.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 421 days old (needed 5 days)
• broadcom-sta (- to 6.30.223.271-23)
  • Migration status for broadcom-sta (- to 6.30.223.271-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating broadcom-sta would introduce bugs in testing: #1057447
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 422 days old (needed 5 days)
• kbtin (- to 2.1-2)
  • Migration status for kbtin (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kbtin would introduce bugs in testing: #1061076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kbtin.html
    • autopkgtest for kbtin/2.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 422 days old (needed 2 days)
• i3pystatus (- to 3.35+git20191126.5a8eaf4-2.1)
  • Migration status for i3pystatus (- to 3.35+git20191126.5a8eaf4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating i3pystatus would introduce bugs in testing: #1056410
    • autopkgtest for i3pystatus/3.35+git20191126.5a8eaf4-2.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i3pystatus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 424 days old (needed 5 days)
• php-horde-ansel (- to 3.0.10+debian1-3)
  • Migration status for php-horde-ansel (- to 3.0.10+debian1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-ansel php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ansel.html
    • autopkgtest for php-horde-ansel/3.0.10+debian1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 424 days old (needed 2 days)
• python-omegaconf (- to 2.2.2-2.1)
  • Migration status for python-omegaconf (- to 2.2.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-omegaconf would introduce bugs in testing: #1042251
    • autopkgtest for python-omegaconf/2.2.2-2.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-omegaconf.html
    • 424 days old (needed 5 days)
• python-pyramid (- to 2.0+dfsg-2)
  • Migration status for python-pyramid (- to 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): python-pyramid python-plaster-pastedeploy (not considered)
    • Depends: python-pyramid python-plaster-pastedeploy (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid.html
    • autopkgtest for python-pyramid/2.0+dfsg-2: 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
    • 424 days old (needed 2 days)
• golang-github-bradenhilton-mozillainstallhash (- to 1.0.0-1)
  • Migration status for golang-github-bradenhilton-mozillainstallhash (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): golang-github-bradenhilton-mozillainstallhash golang-github-bradenhilton-cityhash
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bradenhilton-mozillainstallhash.html
    • autopkgtest for golang-github-bradenhilton-mozillainstallhash/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 425 days old (needed 2 days)
• mailscripts (- to 28-1)
  • Migration status for mailscripts (- to 28-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mailscripts python-pgpy (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailscripts.html
    • Reproducible on i386 - info ♻
    • 425 days old (needed 5 days)
• gfm (- to 1.09~git20220826.71eaa92-1)
  • Migration status for gfm (- to 1.09~git20220826.71eaa92-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gfm libglade2 (not considered)
    • Depends: gfm libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 426 days old (needed 5 days)
• libgit-annex-perl (- to 0.008-1)
  • Migration status for libgit-annex-perl (- to 0.008-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libgit-annex-perl/0.008-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgit-annex-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 426 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 ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 426 days old (needed 5 days)
• cpm (- to 0.32-1.5)
  • Migration status for cpm (- to 0.32-1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpm would introduce bugs in testing: #851594
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpm.html
    • Reproducible on i386 - info ♻
    • 427 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 ♻
    • 428 days old (needed 5 days)
• multiplex (- to 0.6.0-1)
  • Migration status for multiplex (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating multiplex would introduce bugs in testing: #1027462
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multiplex.html
    • autopkgtest for multiplex/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 430 days old (needed 2 days)
• troffcvt (- to 1.04+repack1-1)
  • Migration status for troffcvt (- to 1.04+repack1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating troffcvt would introduce bugs in testing: #1059802
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/troffcvt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 433 days old (needed 5 days)
• tpot (- to 0.11.7+dfsg-5)
  • Migration status for tpot (- to 0.11.7+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tpot would introduce bugs in testing: #1027205
    • autopkgtest for tpot/0.11.7+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): tpot pytorch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpot.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 434 days old (needed 5 days)
• prospector (- to 1.1.7-4)
  • Migration status for prospector (- to 1.1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • prospector/amd64 has unsatisfiable dependency
    • prospector/arm64 has unsatisfiable dependency
    • Updating prospector would introduce bugs in testing: #1055672, #947551
    • Build-Depends(-Arch): prospector pylint-celery
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/prospector.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 436 days old (needed 5 days)
• elastalert (- to 0.2.4-3)
  • Migration status for elastalert (- to 0.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating elastalert would introduce bugs in testing: #1061022
    • autopkgtest for elastalert/0.2.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elastalert.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 438 days old (needed 5 days)
• jhbuild (- to 3.38.0-3.1)
  • Migration status for jhbuild (- to 3.38.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jhbuild would introduce bugs in testing: #1054720
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jhbuild.html
    • Reproducible on i386 - info ♻
    • 440 days old (needed 5 days)
• git-remote-hg (- to 1.0.4~ds-1)
  • Migration status for git-remote-hg (- to 1.0.4~ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating git-remote-hg would introduce bugs in testing: #1061742
    • Build-Depends-Indep: git-remote-hg hg-git
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-remote-hg.html
    • autopkgtest for git-remote-hg/1.0.4~ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 442 days old (needed 2 days)
• golang-github-jesseduffield-rollrus (- to 0.0~git20190701.dd028cb-4)
  • Migration status for golang-github-jesseduffield-rollrus (- to 0.0~git20190701.dd028cb-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-rollrus would introduce bugs in testing: #1032112
    • Build-Depends-Indep: golang-github-jesseduffield-rollrus golang-github-jesseduffield-roll
    • Depends: golang-github-jesseduffield-rollrus golang-github-jesseduffield-roll
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-rollrus.html
    • autopkgtest for golang-github-jesseduffield-rollrus/0.0~git20190701.dd028cb-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 442 days old (needed 2 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 442 days old (needed 5 days)
• azure-functions-devops-build (- to 0.0.22-6)
  • Migration status for azure-functions-devops-build (- to 0.0.22-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): azure-functions-devops-build azure-cli (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/azure-functions-devops-build.html
    • autopkgtest for azure-functions-devops-build/0.0.22-6: 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
    • 444 days old (needed 2 days)
• golang-github-bradenhilton-cityhash (- to 1.0.0-1)
  • Migration status for golang-github-bradenhilton-cityhash (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bradenhilton-cityhash.html
    • autopkgtest for golang-github-bradenhilton-cityhash/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 445 days old (needed 2 days)
• node-puppeteer (- to 13.4.1+dfsg-2)
  • Migration status for node-puppeteer (- to 13.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-puppeteer would introduce bugs in testing: #1026868
    • autopkgtest for node-puppeteer/13.4.1+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-puppeteer.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 447 days old (needed 5 days)
• squeak-plugins-scratch (- to 1.4.0.2~svn.r83-3.1)
  • Migration status for squeak-plugins-scratch (- to 1.4.0.2~svn.r83-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squeak-plugins-scratch would introduce bugs in testing: #909352
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squeak-plugins-scratch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 448 days old (needed 5 days)
• golang-github-sethvargo-go-fastly (- to 1.2.1+git20190805.5c6c8bd-3)
  • Migration status for golang-github-sethvargo-go-fastly (- to 1.2.1+git20190805.5c6c8bd-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-sethvargo-go-fastly golang-github-ajg-form (not considered)
    • Depends: golang-github-sethvargo-go-fastly golang-github-ajg-form (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-sethvargo-go-fastly.html
    • autopkgtest for golang-github-sethvargo-go-fastly/1.2.1+git20190805.5c6c8bd-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 450 days old (needed 2 days)
• jupyter-sphinx (- to 0.3.2-2)
  • Migration status for jupyter-sphinx (- to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jupyter-sphinx would introduce bugs in testing: #950598
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-sphinx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 450 days old (needed 5 days)
• libapache-db-perl (- to 0.18-2)
  • Migration status for libapache-db-perl (- to 0.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libapache-db-perl/amd64 has unsatisfiable dependency
    • libapache-db-perl/arm64 has unsatisfiable dependency
    • libapache-db-perl/armel has unsatisfiable dependency
    • libapache-db-perl/armhf has unsatisfiable dependency
    • libapache-db-perl/i386 has unsatisfiable dependency
    • libapache-db-perl/mips64el has unsatisfiable dependency
    • libapache-db-perl/ppc64el has unsatisfiable dependency
    • libapache-db-perl/s390x has unsatisfiable dependency
    • Updating libapache-db-perl would introduce bugs in testing: #1040396
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-db-perl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 450 days old (needed 5 days)
• pyjunitxml (- to 0.7-2)
  • Migration status for pyjunitxml (- to 0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyjunitxml would introduce bugs in testing: #1057356
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyjunitxml.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 450 days old (needed 5 days)
• django-celery-email (- to 3.0.0-2)
  • Migration status for django-celery-email (- to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): django-celery-email celery (not considered)
    • Depends: django-celery-email celery (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-celery-email.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 452 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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djangorestframework-filters.html
    • Reproducible on i386 - info ♻
    • 452 days old (needed 5 days)
• flask-appbuilder (- to 4.1.4+ds-3)
  • Migration status for flask-appbuilder (- to 4.1.4+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-flask-appbuilder/amd64 has unsatisfiable dependency
    • python3-flask-appbuilder/arm64 has unsatisfiable dependency
    • Updating flask-appbuilder would introduce bugs in testing: #1020739, #1036167
    • flask-appbuilder unsatisfiable Build-Depends(-Arch) on amd64: python3-marshmallow-enum
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/flask-appbuilder.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 452 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 452 days old (needed 5 days)
• esnacc (- to 1.8.1-3)
  • Migration status for esnacc (- to 1.8.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating esnacc would introduce bugs in testing: #1058545
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esnacc.html
    • 453 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 ♻
    • 453 days old (needed 5 days)
• pdm (- to 2.2.1+ds1-1)
  • Migration status for pdm (- to 2.2.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pdm/amd64 has unsatisfiable dependency
    • python3-pdm/arm64 has unsatisfiable dependency
    • Updating pdm would introduce bugs in testing: #1043002
    • pdm unsatisfiable Build-Depends(-Arch) on amd64: python3-pep517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 453 days old (needed 5 days)
• perl-doc-html (- to 5.26.0-7)
  • Migration status for perl-doc-html (- to 5.26.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating perl-doc-html would introduce bugs in testing: #907974
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perl-doc-html.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 453 days old (needed 5 days)
• cpptraj (- to 5.1.0+dfsg-3)
  • Migration status for cpptraj (- to 5.1.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpptraj would introduce bugs in testing: #1035833
    • autopkgtest for cpptraj/5.1.0+dfsg-3: 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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpptraj.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 455 days old (needed 5 days)
• pyliblo (- to 0.10.0-5.1)
  • Migration status for pyliblo (- to 0.10.0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyliblo would introduce bugs in testing: #1056839
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyliblo.html
    • autopkgtest for pyliblo/0.10.0-5.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 456 days old (needed 2 days)
• python-webargs (- to 8.0.1-2)
  • Migration status for python-webargs (- to 8.0.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-webargs python-pyramid (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-webargs.html
    • autopkgtest for python-webargs/8.0.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 456 days old (needed 5 days)
• gnome-authenticator (- to 3.32.2+dfsg1-5)
  • Migration status for gnome-authenticator (- to 3.32.2+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-authenticator would introduce bugs in testing: #993849
    • Build-Depends(-Arch): gnome-authenticator libhandy
    • Depends: gnome-authenticator libhandy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-authenticator.html
    • autopkgtest for gnome-authenticator/3.32.2+dfsg1-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 458 days old (needed 5 days)
• golang-github-jesseduffield-go-getter (- to 0.0~git20180822.906e156-5)
  • Migration status for golang-github-jesseduffield-go-getter (- to 0.0~git20180822.906e156-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-go-getter would introduce bugs in testing: #1032107
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-go-getter.html
    • autopkgtest for golang-github-jesseduffield-go-getter/0.0~git20180822.906e156-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 458 days old (needed 2 days)
• golang-github-jesseduffield-roll (- to 0.0~git20190629.695be2e-3)
  • Migration status for golang-github-jesseduffield-roll (- to 0.0~git20190629.695be2e-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-roll would introduce bugs in testing: #1032113
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-roll.html
    • autopkgtest for golang-github-jesseduffield-roll/0.0~git20190629.695be2e-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 458 days old (needed 2 days)
• golang-github-keybase-go-ps (- to 0.0~git20190827.91aafc9-1)
  • Migration status for golang-github-keybase-go-ps (- to 0.0~git20190827.91aafc9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-keybase-go-ps.html
    • autopkgtest for golang-github-keybase-go-ps/0.0~git20190827.91aafc9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 458 days old (needed 2 days)
• golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2)
  • Migration status for golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-leanovate-gopter/0.2.9+git20210201.bbbf00e-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, 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 ♻
    • 458 days old (needed 5 days)
• heudiconv (- to 0.11.6-1)
  • Migration status for heudiconv (- to 0.11.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): heudiconv dcmstack (not considered)
    • Depends: heudiconv dcmstack (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heudiconv.html
    • autopkgtest for heudiconv/0.11.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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
    • 458 days old (needed 2 days)
• ogre-1.9 (- to 1.9.0+dfsg1-14)
  • Migration status for ogre-1.9 (- to 1.9.0+dfsg1-14): 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 ♻
    • 458 days old (needed 5 days)
• zipflinger (- to 7.2.2-2)
  • Migration status for zipflinger (- to 7.2.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): zipflinger android-platform-tools-base (not considered)
    • Depends: zipflinger android-platform-tools-base (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zipflinger.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 458 days old (needed 5 days)
• golang-github-jesseduffield-asciigraph (- to 0.4.1+git20190605.6d88e39-3)
  • Migration status for golang-github-jesseduffield-asciigraph (- to 0.4.1+git20190605.6d88e39-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-asciigraph would introduce bugs in testing: #1032108
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-asciigraph.html
    • autopkgtest for golang-github-jesseduffield-asciigraph/0.4.1+git20190605.6d88e39-3: 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
    • 459 days old (needed 2 days)
• golang-github-jesseduffield-pty (- to 1.1.3+git20191112.07ed706-2)
  • Migration status for golang-github-jesseduffield-pty (- to 1.1.3+git20191112.07ed706-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-pty would introduce bugs in testing: #1032111
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-pty.html
    • autopkgtest for golang-github-jesseduffield-pty/1.1.3+git20191112.07ed706-2: 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
    • 459 days old (needed 2 days)
• golang-github-jesseduffield-yaml (- to 2.2.2+git20190702.b900b7e-3)
  • Migration status for golang-github-jesseduffield-yaml (- to 2.2.2+git20190702.b900b7e-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-yaml would introduce bugs in testing: #1032190
    • autopkgtest for golang-github-jesseduffield-yaml/2.2.2+git20190702.b900b7e-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-yaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 459 days old (needed 5 days)
• golang-github-muesli-combinator (- to 0.3.0-1)
  • Migration status for golang-github-muesli-combinator (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-muesli-combinator.html
    • autopkgtest for golang-github-muesli-combinator/0.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 459 days old (needed 2 days)
• golang-github-twpayne-go-pinentry (- to 0.2.0-1)
  • Migration status for golang-github-twpayne-go-pinentry (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-pinentry.html
    • autopkgtest for golang-github-twpayne-go-pinentry/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 459 days old (needed 2 days)
• golang-github-twpayne-go-shell (- to 0.3.1-1)
  • Migration status for golang-github-twpayne-go-shell (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-shell.html
    • autopkgtest for golang-github-twpayne-go-shell/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 459 days old (needed 2 days)
• golang-github-twpayne-go-vfs (- to 4.1.0-1)
  • Migration status for golang-github-twpayne-go-vfs (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-vfs.html
    • autopkgtest for golang-github-twpayne-go-vfs/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 459 days old (needed 2 days)
• golang-github-twpayne-go-xdg (- to 6.0.0-1)
  • Migration status for golang-github-twpayne-go-xdg (- to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): golang-github-twpayne-go-xdg golang-github-twpayne-go-vfs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-xdg.html
    • autopkgtest for golang-github-twpayne-go-xdg/6.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 459 days old (needed 2 days)
• opensysusers (- to 0.7.3-2)
  • Migration status for opensysusers (- to 0.7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensysusers would introduce bugs in testing: #1055517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensysusers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 459 days old (needed 5 days)
• rust-fxprof-processed-profile (- to 0.4.0-2)
  • Migration status for rust-fxprof-processed-profile (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-fxprof-processed-profile would introduce bugs in testing: #1030997
    • autopkgtest for rust-fxprof-processed-profile/0.4.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fxprof-processed-profile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 459 days old (needed 5 days)
• shush (- to 1.2.3-5.1)
  • Migration status for shush (- to 1.2.3-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shush would introduce bugs in testing: #999964
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shush.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 459 days old (needed 5 days)
• syncmaildir (- to 1.3.0-2)
  • Migration status for syncmaildir (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating syncmaildir would introduce bugs in testing: #1000322
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syncmaildir.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 461 days old (needed 5 days)
• dh-make-golang (- to 0.6.0-2)
  • Migration status for dh-make-golang (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dh-make-golang would introduce bugs in testing: #1043070, #1050523
    • autopkgtest for dh-make-golang/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 ♻, s390x: Regression or new test ♻
    • dh-make-golang/amd64 has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/arm64 has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/armel has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/armhf has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/i386 has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/mips64el has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/ppc64el has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/s390x has unsatisfiable Built-Using on golang-1.19 1.19.8-2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-make-golang.html
    • Reproducible on i386 - info ♻
    • 462 days old (needed 5 days)
• qflow (- to 1.3.17+dfsg.1-3)
  • Migration status for qflow (- to 1.3.17+dfsg.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): qflow opensta (not considered)
    • Depends: qflow opensta (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qflow.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for qflow/1.3.17+dfsg.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 462 days old (needed 2 days)
• tipp (- to 1.0+dfsg-3)
  • Migration status for tipp (- to 1.0+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tipp sepp (not considered)
    • Depends: tipp sepp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tipp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 463 days old (needed 5 days)
• golang-github-github-smimesign (- to 0.2.0+dfsg-1)
  • Migration status for golang-github-github-smimesign (- to 0.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costela, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-github-smimesign.html
    • autopkgtest for golang-github-github-smimesign/0.2.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 464 days old (needed 2 days)
• platformio (- to 4.3.4-3)
  • Migration status for platformio (- to 4.3.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating platformio would introduce bugs in testing: #1053285, #988716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/platformio.html
    • autopkgtest for platformio/4.3.4-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 464 days old (needed 5 days)
• el-get (- to 3.1-2)
  • Migration status for el-get (- to 3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating el-get would introduce bugs in testing: #912364, #916857
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/el-get.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 465 days old (needed 5 days)
• yaramod (- to 3.6.0-1.1)
  • Migration status for yaramod (- to 3.6.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yaramod would introduce bugs in testing: #1037908
    • autopkgtest for yaramod/3.6.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yaramod.html
    • Reproducible on i386 - info ♻
    • 465 days old (needed 5 days)
• sip4 (- to 4.19.25+dfsg-5)
  • Migration status for sip4 (- to 4.19.25+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sip4 would introduce bugs in testing: #1059648
    • autopkgtest for sip4/4.19.25+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sip4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 466 days old (needed 5 days)
• pylint-celery (- to 0.3-7)
  • Migration status for pylint-celery (- to 0.3-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pylint-celery celery (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pylint-celery.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 467 days old (needed 5 days)
• aws-checksums (- to 0.1.13-1)
  • Migration status for aws-checksums (- to 0.1.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libaws-checksums-dev/amd64 has unsatisfiable dependency
    • libaws-checksums1.0.0/amd64 has unsatisfiable dependency
    • Updating aws-checksums would introduce bugs in testing: #1029332, #1050400
    • aws-checksums unsatisfiable Build-Depends(-Arch) on amd64: libaws-c-common-dev
    • Not built on buildd: arch amd64 binaries uploaded by noahm
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/aws-checksums.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 i386 - info ♻
    • 470 days old (needed 5 days)
• fruit (- to 2.1.dfsg-10)
  • Migration status for fruit (- to 2.1.dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fruit would introduce bugs in testing: #1014187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fruit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 470 days old (needed 5 days)
• node-request (- to 2.88.1-6)
  • Migration status for node-request (- to 2.88.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-request would introduce bugs in testing: #956423
    • Build-Depends(-Arch): node-request node-har-validator
    • Depends: node-request node-har-validator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-request.html
    • autopkgtest for node-request/2.88.1-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 470 days old (needed 2 days)
• salt (- to 3004.1+dfsg-2.2)
  • Migration status for salt (- to 3004.1+dfsg-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating salt would introduce bugs in testing: #1013872, #1021317, #1021920, #1022530, #1028421, #1033808, #1051504, #1055179
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): salt pytest-salt-factories
    • Build-Depends(-Arch): salt python-pyvmomi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/salt.html
    • 472 days old (needed 5 days)
• libjpeg6b (- to 1:6b2-3.1)
  • Migration status for libjpeg6b (- to 1:6b2-3.1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
    • Build-Depends(-Arch): libjpeg6b automake1.11
  • 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 ♻
    • 474 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: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-rnp.html
    • Reproducible on armhf - info ♻
    • 474 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 ♻
    • 475 days old (needed 5 days)
• objcryst-fox (- to 2022.1-1)
  • Migration status for objcryst-fox (- to 2022.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): objcryst-fox newmat (not considered)
    • Depends: objcryst-fox newmat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): objcryst-fox cctbx
    • Depends: objcryst-fox cctbx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/objcryst-fox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 476 days old (needed 5 days)
• golang-github-blynn-nex (- to 0.0.0+git.2021.03.30.1a3320dab9-2)
  • Migration status for golang-github-blynn-nex (- to 0.0.0+git.2021.03.30.1a3320dab9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-blynn-nex would introduce bugs in testing: #1022957
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-blynn-nex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 479 days old (needed 5 days)
• pytest-services (- to 2.2.1+ds-3)
  • Migration status for pytest-services (- to 2.2.1+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytest-services/2.2.1+ds-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): pytest-services mysql-8.0
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-services.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 479 days old (needed 5 days)
• python-plaster-pastedeploy (- to 0.5-5)
  • Migration status for python-plaster-pastedeploy (- to 0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-plaster-pastedeploy would introduce bugs in testing: #1052860
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-plaster-pastedeploy.html
    • autopkgtest for python-plaster-pastedeploy/0.5-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 482 days old (needed 2 days)
• python-pyramid-chameleon (- to 0.3-7)
  • Migration status for python-pyramid-chameleon (- to 0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyramid-chameleon would introduce bugs in testing: #1052780, #1056499
    • Build-Depends(-Arch): python-pyramid-chameleon python-pyramid
    • Depends: python-pyramid-chameleon python-pyramid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-chameleon.html
    • autopkgtest for python-pyramid-chameleon/0.3-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 482 days old (needed 2 days)
• golang-github-libvirt-libvirt-go-xml (- to 7.4.0-1)
  • Migration status for golang-github-libvirt-libvirt-go-xml (- to 7.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-libvirt-libvirt-go-xml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 483 days old (needed 5 days)
• libvmod-re2 (- to 2.0.0-2)
  • Migration status for libvmod-re2 (- to 2.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libvmod-re2 varnish (not considered)
    • Depends: libvmod-re2 varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvmod-re2.html
    • autopkgtest for libvmod-re2/2.0.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 487 days old (needed 2 days)
• libvmod-selector (- to 2.6.0-3)
  • Migration status for libvmod-selector (- to 2.6.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libvmod-selector varnish (not considered)
    • Depends: libvmod-selector varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvmod-selector.html
    • autopkgtest for libvmod-selector/2.6.0-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 487 days old (needed 2 days)
• python-semantic-release (- to 7.32.2-1)
  • Migration status for python-semantic-release (- to 7.32.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-semantic-release would introduce bugs in testing: #1056503, #1058357
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-semantic-release.html
    • autopkgtest for python-semantic-release/7.32.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 488 days old (needed 2 days)
• courier-filter-perl (- to 0.200+ds-6)
  • Migration status for courier-filter-perl (- to 0.200+ds-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: courier-filter-perl courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-filter-perl.html
    • autopkgtest for courier-filter-perl/0.200+ds-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 489 days old (needed 5 days)
• flask-mongoengine (- to 1.0.0-1)
  • Migration status for flask-mongoengine (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-mongoengine would introduce bugs in testing: #1061042
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-mongoengine.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 493 days old (needed 5 days)
• autolink (- to 0.10.0-1)
  • Migration status for autolink (- to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autolink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 494 days old (needed 5 days)
• devpi-common (- to 3.2.2-3)
  • Migration status for devpi-common (- to 3.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating devpi-common would introduce bugs in testing: #1030453
    • autopkgtest for devpi-common/3.2.2-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devpi-common.html
    • 494 days old (needed 5 days)
• dradio (- to 3.8-2.1)
  • Migration status for dradio (- to 3.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dradio would introduce bugs in testing: #1057554
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dradio.html
    • Reproducible on i386 - info ♻
    • 494 days old (needed 5 days)
• nwdiag (- to 2.0.0+dfsg-1.1)
  • Migration status for nwdiag (- to 2.0.0+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nwdiag would introduce bugs in testing: #1042235
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nwdiag.html
    • Reproducible on i386 - info ♻
    • 494 days old (needed 5 days)
• python-b2sdk (- to 1.17.3-2)
  • Migration status for python-b2sdk (- to 1.17.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-b2sdk would introduce bugs in testing: #1056458
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-b2sdk.html
    • autopkgtest for python-b2sdk/1.17.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 494 days old (needed 2 days)
• subdownloader (- to 2.1.0-5)
  • Migration status for subdownloader (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating subdownloader would introduce bugs in testing: #1042355
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/subdownloader.html
    • autopkgtest for subdownloader/2.1.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 494 days old (needed 2 days)
• ukui-biometric-manager (- to 1.0.3.1-1)
  • Migration status for ukui-biometric-manager (- to 1.0.3.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: ukui-biometric-manager biometric-authentication (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-biometric-manager.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 494 days old (needed 5 days)
• libextutils-cbuilder-perl (- to 0.280236-2)
  • Migration status for libextutils-cbuilder-perl (- to 0.280236-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libextutils-cbuilder-perl would introduce bugs in testing: #1060712
    • autopkgtest for libextutils-cbuilder-perl/0.280236-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libe/libextutils-cbuilder-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 495 days old (needed 5 days)
• raku (- to 6.d.7)
  • Migration status for raku (- to 6.d.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: raku raku-meta6 (not considered)
    • Invalidated by dependency
    • Depends: raku raku-test-meta
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 495 days old (needed 5 days)
• analizo (- to 1.25.4-2)
  • Migration status for analizo (- to 1.25.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating analizo would introduce bugs in testing: #1051534
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/analizo.html
    • autopkgtest for analizo/1.25.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 496 days old (needed 2 days)
• fsprotect (- to 1.0.7+nmu1)
  • Migration status for fsprotect (- to 1.0.7+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fsprotect would introduce bugs in testing: #1061369
    • Depends: fsprotect aufs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fsprotect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 496 days old (needed 5 days)
• lockdown (- to 0.2+nmu1)
  • Migration status for lockdown (- to 0.2+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lockdown would introduce bugs in testing: #958587
    • lockdown unsatisfiable Build-Depends(-Arch) on amd64: dh-systemd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lockdown.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 ♻
    • 496 days old (needed 5 days)
• mailman-suite (- to 0+20200530-2.1)
  • Migration status for mailman-suite (- to 0+20200530-2.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mailman-suite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 496 days old (needed 5 days)
• matrix-sydent (- to 2.5.1-1.1)
  • Migration status for matrix-sydent (- to 2.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matrix-sydent would introduce bugs in testing: #1029442, #1035844
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/matrix-sydent.html
  • Additional info:
    • autopkgtest for matrix-sydent/2.5.1-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 496 days old (needed 5 days)
• mom (- to 0.6.0-2.1)
  • Migration status for mom (- to 0.6.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mom would introduce bugs in testing: #1014781
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 496 days old (needed 5 days)
• networking-mlnx (- to 1:16.0.0-3.1)
  • Migration status for networking-mlnx (- to 1:16.0.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating networking-mlnx would introduce bugs in testing: #1021924
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-mlnx.html
    • 496 days old (needed 5 days)
• openscap-daemon (- to 0.1.10-3.1)
  • Migration status for openscap-daemon (- to 0.1.10-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openscap-daemon/amd64 has unsatisfiable dependency
    • openscap-daemon/arm64 has unsatisfiable dependency
    • Updating openscap-daemon would introduce bugs in testing: #1035384
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openscap-daemon.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 496 days old (needed 5 days)
• python-ara (- to 1.5.8-1.1)
  • Migration status for python-ara (- to 1.5.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ara would introduce bugs in testing: #1038732
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/python-ara.html
    • Build-Depends-Indep: python-ara python-django-health-check
    • Depends: python-ara python-django-health-check
  • Additional info:
    • 496 days old (needed 5 days)
• libtoxcore (- to 0.2.18-1)
  • Migration status for libtoxcore (- to 0.2.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libtoxcore would introduce bugs in testing: #1053501
    • autopkgtest for libtoxcore/0.2.18-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtoxcore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 499 days old (needed 5 days)
• libvmod-redis (- to 15.1-1)
  • Migration status for libvmod-redis (- to 15.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libvmod-redis varnish (not considered)
    • Depends: libvmod-redis varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvmod-redis.html
    • autopkgtest for libvmod-redis/15.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 499 days old (needed 2 days)
• telegram-cli (- to 1.3.1+git20160323.6547c0b21-3.1)
  • Migration status for telegram-cli (- to 1.3.1+git20160323.6547c0b21-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telegram-cli would introduce bugs in testing: #1018754
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 499 days old (needed 5 days)
• mozillavpn (- to 2.9.0-1)
  • Migration status for mozillavpn (- to 2.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mozillavpn would introduce bugs in testing: #1027506, #1043004
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/mozillavpn.html
    • missing build on mips64el
  • Additional info:
    • 500 days old (needed 5 days)
• bettercap-caplets (- to 0+git20210429-1)
  • Migration status for bettercap-caplets (- to 0+git20210429-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bettercap-caplets/amd64 has unsatisfiable dependency
    • bettercap-caplets/arm64 has unsatisfiable dependency
    • Updating bettercap-caplets would introduce bugs in testing: #1053331
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bettercap-caplets.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 505 days old (needed 5 days)
• python-django-health-check (- to 3.17.0-1)
  • Migration status for python-django-health-check (- to 3.17.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-django-health-check celery (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-health-check.html
    • autopkgtest for python-django-health-check/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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 505 days old (needed 5 days)
• pantalaimon (- to 0.10.5-1)
  • Migration status for pantalaimon (- to 0.10.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pantalaimon would introduce bugs in testing: #1023971
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantalaimon.html
    • autopkgtest for pantalaimon/0.10.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 507 days old (needed 5 days)
• cclive (- to 0.9.3-0.3)
  • Migration status for cclive (- to 0.9.3-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cclive would introduce bugs in testing: #1000076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cclive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 508 days old (needed 5 days)
• rust-matchers (- to 0.1.0-1)
  • Migration status for rust-matchers (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-matchers-dev/amd64 has unsatisfiable dependency
    • librust-matchers-dev/arm64 has unsatisfiable dependency
    • librust-matchers-dev/armel has unsatisfiable dependency
    • librust-matchers-dev/armhf has unsatisfiable dependency
    • librust-matchers-dev/i386 has unsatisfiable dependency
    • librust-matchers-dev/mips64el has unsatisfiable dependency
    • librust-matchers-dev/ppc64el has unsatisfiable dependency
    • librust-matchers-dev/s390x has unsatisfiable dependency
    • Updating rust-matchers would introduce bugs in testing: #1053420, #1054722
    • rust-matchers unsatisfiable Build-Depends(-Arch) on amd64: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on arm64: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on armel: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on armhf: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on i386: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on mips64el: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on ppc64el: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on s390x: librust-regex-automata-0.1+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-matchers.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch 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 ♻
    • Reproducible on i386 - info ♻
    • 508 days old (needed 5 days)
• python-flanker (- to 0.9.14-3)
  • Migration status for python-flanker (- to 0.9.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-flanker would introduce bugs in testing: #1033714
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flanker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 509 days old (needed 5 days)
• dcmstack (- to 0.9-1)
  • Migration status for dcmstack (- to 0.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dcmstack/0.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dcmstack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 511 days old (needed 5 days)
• gpsshogi (- to 0.7.0-3.1)
  • Migration status for gpsshogi (- to 0.7.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): gpsshogi poco (not considered)
    • Depends: gpsshogi poco (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpsshogi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 513 days old (needed 5 days)
• keras (- to 2.3.1+dfsg2-1)
  • Migration status for keras (- to 2.3.1+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-keras/amd64 has unsatisfiable dependency
    • python3-keras/arm64 has unsatisfiable dependency
    • Updating keras would introduce bugs in testing: #1026738
    • keras unsatisfiable Build-Depends(-Arch) on amd64: python3-theano
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/keras.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 518 days old (needed 5 days)
• emacspeak (- to 53.0+dfsg-2)
  • Migration status for emacspeak (- to 53.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacspeak would introduce bugs in testing: #1051402
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/emacspeak.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 521 days old (needed 5 days)
• php-fdomdocument (- to 1.6.7-2)
  • Migration status for php-fdomdocument (- to 1.6.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fdomdocument would introduce bugs in testing: #813866
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fdomdocument.html
    • autopkgtest for php-fdomdocument/1.6.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 521 days old (needed 2 days)
• phpdox (- to 0.12.0-6)
  • Migration status for phpdox (- to 0.12.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phpdox/amd64 has unsatisfiable dependency
    • phpdox/arm64 has unsatisfiable dependency
    • Updating phpdox would introduce bugs in testing: #813861
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/phpdox.html
    • Build-Depends(-Arch): phpdox php-fdomdocument
    • Build-Depends(-Arch): phpdox php-fxsl
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 521 days old (needed 5 days)
• python-icecream (- to 2.1.3-1)
  • Migration status for python-icecream (- to 2.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-icecream would introduce bugs in testing: #1059668
    • autopkgtest for python-icecream/2.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-icecream.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 525 days old (needed 5 days)
• qreator (- to 16.06.1-7.1)
  • Migration status for qreator (- to 16.06.1-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qreator would introduce bugs in testing: #1058246
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qreator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 525 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bing.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 526 days old (needed 5 days)
• sylpheed (- to 3.8.0~beta1-1)
  • Migration status for sylpheed (- to 3.8.0~beta1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sylpheed would introduce bugs in testing: #1036424
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sylpheed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 526 days old (needed 5 days)
• raku-meta6 (- to 0.0.29-1)
  • Migration status for raku-meta6 (- to 0.0.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating raku-meta6 would introduce bugs in testing: #1057611
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-meta6.html
    • 529 days old (needed 5 days)
• raku-test-meta (- to 0.0.17-1)
  • Migration status for raku-test-meta (- to 0.0.17-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-test-meta raku-meta6 (not considered)
    • Depends: raku-test-meta raku-meta6 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-test-meta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 529 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): sagetex sagemath
    • Depends: sagetex sagemath
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagetex.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 530 days old (needed 5 days)
• watchman (- to 4.9.0-7)
  • Migration status for watchman (- to 4.9.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating watchman would introduce bugs in testing: #999930
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watchman.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 530 days old (needed 5 days)
• roger-router (- to 2.4.2-3)
  • Migration status for roger-router (- to 2.4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • roger-router/amd64 has unsatisfiable dependency
    • roger-router/arm64 has unsatisfiable dependency
    • roger-router/armel has unsatisfiable dependency
    • roger-router/armhf has unsatisfiable dependency
    • roger-router/i386 has unsatisfiable dependency
    • roger-router/mips64el has unsatisfiable dependency
    • roger-router/ppc64el has unsatisfiable dependency
    • roger-router/s390x has unsatisfiable dependency
    • Updating roger-router would introduce bugs in testing: #1019303
    • Build-Depends(-Arch): roger-router librm
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/roger-router.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 534 days old (needed 5 days)
• libgovirt (- to 0.3.9-2)
  • Migration status for libgovirt (- to 0.3.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgovirt would introduce bugs in testing: #1030904
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgovirt.html
    • Reproducible on arm64 - info ♻
    • 535 days old (needed 5 days)
• librm (- to 2.2.3-1)
  • Migration status for librm (- to 2.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librm0/amd64 has unsatisfiable dependency
    • librm0/arm64 has unsatisfiable dependency
    • librm0/armel has unsatisfiable dependency
    • librm0/armhf has unsatisfiable dependency
    • librm0/i386 has unsatisfiable dependency
    • librm0/mips64el has unsatisfiable dependency
    • librm0/ppc64el has unsatisfiable dependency
    • librm0/s390x has unsatisfiable dependency
    • Updating librm would introduce bugs in testing: #1022008, #1037392
    • librm unsatisfiable Build-Depends(-Arch) on amd64: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on amd64: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on arm64: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on arm64: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armel: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armel: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armhf: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armhf: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on i386: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on i386: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on mips64el: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on mips64el: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on ppc64el: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on ppc64el: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on s390x: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on s390x: libgssdp-1.2-dev | libgssdp-1.0-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libr/librm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 543 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-subtitles.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 547 days old (needed 5 days)
• mozilla-devscripts (- to 0.54.2+nmu1)
  • Migration status for mozilla-devscripts (- to 0.54.2+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mozilla-devscripts would introduce bugs in testing: #1058698
    • Impossible Build-Depends(-Arch): mozilla-devscripts -> python3-librdf/1.0.17.1+dfsg-4+b2/amd64
    • Impossible Depends: mozilla-devscripts -> python3-librdf/1.0.17.1+dfsg-4+b2/amd64
    • Impossible Depends: mozilla-devscripts -> python3-librdf/1.0.17.1+dfsg-4+b2/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mozilla-devscripts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 549 days old (needed 5 days)
• pandoc-citeproc-preamble (- to 1.7-1)
  • Migration status for pandoc-citeproc-preamble (- to 1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pandoc-citeproc-preamble would introduce bugs in testing: #1054770
    • autopkgtest for pandoc-citeproc-preamble/1.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pandoc-citeproc-preamble.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 550 days old (needed 5 days)
• django-cachalot (- to 2.4.3-2)
  • Migration status for django-cachalot (- to 2.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-django-cachalot/amd64 has unsatisfiable dependency
    • python3-django-cachalot/arm64 has unsatisfiable dependency
    • Updating django-cachalot would introduce bugs in testing: #1055207
    • django-cachalot unsatisfiable Build-Depends(-Arch) on amd64: python3-django (<< 3:3.3~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/django-cachalot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 556 days old (needed 5 days)
• varnish-modules (- to 0.20.0-2)
  • Migration status for varnish-modules (- to 0.20.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): varnish-modules varnish (not considered)
    • Depends: varnish-modules varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/varnish-modules.html
    • autopkgtest for varnish-modules/0.20.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 559 days old (needed 2 days)
• s3ql (- to 3.7.3+dfsg-2)
  • Migration status for s3ql (- to 3.7.3+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): s3ql python-dugong (not considered)
    • Depends: s3ql python-dugong (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): s3ql pyfuse3
    • Depends: s3ql pyfuse3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/s3ql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 561 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
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• haskell-happstack-authenticate (- to 2.6.1-1)
  • Migration status for haskell-happstack-authenticate (- to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-happstack-authenticate-dev/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-doc/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-doc/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/armel has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/armel has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/armhf has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/armhf has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/i386 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/i386 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/mips64el has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/mips64el has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/ppc64el has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/ppc64el has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/s390x has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/s390x has unsatisfiable dependency
    • Updating haskell-happstack-authenticate would introduce bugs in testing: #1054957, #1057719
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-shakespeare-dev (<< 2.1)
    • Build-Depends(-Arch): haskell-happstack-authenticate haskell-userid
    • Build-Depends-Indep: haskell-happstack-authenticate haskell-userid
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-happstack-authenticate.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 563 days old (needed 5 days)
• smlsharp (- to 4.0.0+git20211227.5af5945b-2)
  • Migration status for smlsharp (- to 4.0.0+git20211227.5af5945b-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): smlsharp massivethreads (not considered)
    • Depends: smlsharp massivethreads (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smlsharp.html
    • 568 days old (needed 5 days)
• xir (- to 2.5-1)
  • Migration status for xir (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xir would introduce bugs in testing: #1037901
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xir.html
    • 568 days old (needed 5 days)
• haskell-userid (- to 0.1.3.7-1)
  • Migration status for haskell-userid (- to 0.1.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-userid-dev/amd64 has unsatisfiable dependency
    • libghc-userid-doc/amd64 has unsatisfiable dependency
    • libghc-userid-prof/amd64 has unsatisfiable dependency
    • libghc-userid-dev/arm64 has unsatisfiable dependency
    • libghc-userid-doc/arm64 has unsatisfiable dependency
    • libghc-userid-prof/arm64 has unsatisfiable dependency
    • libghc-userid-dev/armel has unsatisfiable dependency
    • libghc-userid-prof/armel has unsatisfiable dependency
    • libghc-userid-dev/armhf has unsatisfiable dependency
    • libghc-userid-prof/armhf has unsatisfiable dependency
    • libghc-userid-dev/i386 has unsatisfiable dependency
    • libghc-userid-prof/i386 has unsatisfiable dependency
    • libghc-userid-dev/mips64el has unsatisfiable dependency
    • libghc-userid-prof/mips64el has unsatisfiable dependency
    • libghc-userid-dev/ppc64el has unsatisfiable dependency
    • libghc-userid-prof/ppc64el has unsatisfiable dependency
    • libghc-userid-dev/s390x has unsatisfiable dependency
    • libghc-userid-prof/s390x has unsatisfiable dependency
    • Updating haskell-userid would introduce bugs in testing: #1054977, #1057718
    • haskell-userid unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on armel: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on mips64el: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on s390x: libghc-aeson-dev (<< 2.1)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-userid.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 571 days old (needed 5 days)
• ortools (- to 8.2+ds-6)
  • Migration status for ortools (- to 8.2+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libortools8/amd64 has unsatisfiable dependency
    • ortools-samples/amd64 has unsatisfiable dependency
    • python3-ortools/amd64 has unsatisfiable dependency
    • libortools8/arm64 has unsatisfiable dependency
    • ortools-samples/arm64 has unsatisfiable dependency
    • python3-ortools/arm64 has unsatisfiable dependency
    • libortools8/ppc64el has unsatisfiable dependency
    • ortools-samples/ppc64el has unsatisfiable dependency
    • python3-ortools/ppc64el has unsatisfiable dependency
    • Updating ortools would introduce bugs in testing: #1024790, #1040564
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/ortools.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 571 days old (needed 5 days)
• haskell-hindent (- to 5.3.4-1)
  • Migration status for haskell-hindent (- to 5.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hindent-doc/amd64 has unsatisfiable dependency
    • libghc-hindent-doc/arm64 has unsatisfiable dependency
    • libghc-hindent-dev/mips64el has unsatisfiable dependency
    • libghc-hindent-prof/mips64el has unsatisfiable dependency
    • Updating haskell-hindent would introduce bugs in testing: #1053982
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hindent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 572 days old (needed 5 days)
• haskell-hsyaml (- to 0.2.1.1-2)
  • Migration status for haskell-hsyaml (- to 0.2.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsyaml-dev/amd64 has unsatisfiable dependency
    • libghc-hsyaml-doc/amd64 has unsatisfiable dependency
    • libghc-hsyaml-prof/amd64 has unsatisfiable dependency
    • libghc-hsyaml-dev/arm64 has unsatisfiable dependency
    • libghc-hsyaml-doc/arm64 has unsatisfiable dependency
    • libghc-hsyaml-prof/arm64 has unsatisfiable dependency
    • libghc-hsyaml-dev/armel has unsatisfiable dependency
    • libghc-hsyaml-prof/armel has unsatisfiable dependency
    • libghc-hsyaml-dev/armhf has unsatisfiable dependency
    • libghc-hsyaml-prof/armhf has unsatisfiable dependency
    • libghc-hsyaml-dev/i386 has unsatisfiable dependency
    • libghc-hsyaml-prof/i386 has unsatisfiable dependency
    • libghc-hsyaml-dev/mips64el has unsatisfiable dependency
    • libghc-hsyaml-prof/mips64el has unsatisfiable dependency
    • libghc-hsyaml-dev/ppc64el has unsatisfiable dependency
    • libghc-hsyaml-prof/ppc64el has unsatisfiable dependency
    • libghc-hsyaml-dev/s390x has unsatisfiable dependency
    • libghc-hsyaml-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsyaml would introduce bugs in testing: #1054863
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsyaml.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on i386 - info ♻
    • 573 days old (needed 5 days)
• go-mode.el (- to 3:1.6.0-1)
  • Migration status for go-mode.el (- to 3:1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating go-mode.el would introduce bugs in testing: #1052922
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-mode.el.html
    • Reproducible on i386 - info ♻
    • 575 days old (needed 5 days)
• haskell-ircbot (- to 0.6.6.1-1)
  • Migration status for haskell-ircbot (- to 0.6.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-ircbot-dev/amd64 has unsatisfiable dependency
    • libghc-ircbot-doc/amd64 has unsatisfiable dependency
    • libghc-ircbot-prof/amd64 has unsatisfiable dependency
    • libghc-ircbot-dev/arm64 has unsatisfiable dependency
    • libghc-ircbot-doc/arm64 has unsatisfiable dependency
    • libghc-ircbot-prof/arm64 has unsatisfiable dependency
    • libghc-ircbot-dev/armel has unsatisfiable dependency
    • libghc-ircbot-prof/armel has unsatisfiable dependency
    • libghc-ircbot-dev/armhf has unsatisfiable dependency
    • libghc-ircbot-prof/armhf has unsatisfiable dependency
    • libghc-ircbot-dev/i386 has unsatisfiable dependency
    • libghc-ircbot-prof/i386 has unsatisfiable dependency
    • libghc-ircbot-dev/mips64el has unsatisfiable dependency
    • libghc-ircbot-prof/mips64el has unsatisfiable dependency
    • libghc-ircbot-dev/ppc64el has unsatisfiable dependency
    • libghc-ircbot-prof/ppc64el has unsatisfiable dependency
    • libghc-ircbot-dev/s390x has unsatisfiable dependency
    • libghc-ircbot-prof/s390x has unsatisfiable dependency
    • Updating haskell-ircbot would introduce bugs in testing: #1054947, #1057720
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on amd64: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on arm64: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on armel: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on armhf: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on i386: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on mips64el: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on s390x: libghc-optparse-applicative-dev (<< 0.17)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-ircbot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 579 days old (needed 5 days)
• maildrop (- to 2.9.3-2.1)
  • Migration status for maildrop (- to 2.9.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating maildrop would introduce bugs in testing: #1000129
    • Build-Depends(-Arch): maildrop courier-authlib
    • Depends: maildrop courier-authlib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/maildrop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 579 days old (needed 5 days)
• threadscope (- to 0.2.14.1-1)
  • Migration status for threadscope (- to 0.2.14.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating threadscope would introduce bugs in testing: #1054939
    • threadscope unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on armel: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on mips64el: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on s390x: libghc-ghc-events-dev (<< 0.18)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/threadscope.html
    • 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 ♻
    • 579 days old (needed 5 days)
• haskell-reform-hsp (- to 0.2.7.2-2)
  • Migration status for haskell-reform-hsp (- to 0.2.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-reform-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-dev/armel has unsatisfiable dependency
    • libghc-reform-hsp-prof/armel has unsatisfiable dependency
    • libghc-reform-hsp-dev/armhf has unsatisfiable dependency
    • libghc-reform-hsp-prof/armhf has unsatisfiable dependency
    • libghc-reform-hsp-dev/i386 has unsatisfiable dependency
    • libghc-reform-hsp-prof/i386 has unsatisfiable dependency
    • libghc-reform-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-reform-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-reform-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-reform-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-reform-hsp-dev/s390x has unsatisfiable dependency
    • libghc-reform-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-reform-hsp would introduce bugs in testing: #1054865, #1056758
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-reform-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on i386 - info ♻
    • 581 days old (needed 5 days)
• haskell-tidal (- to 1.7.10-1)
  • Migration status for haskell-tidal (- to 1.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-tidal-dev/amd64 has unsatisfiable dependency
    • libghc-tidal-doc/amd64 has unsatisfiable dependency
    • libghc-tidal-prof/amd64 has unsatisfiable dependency
    • libghc-tidal-dev/arm64 has unsatisfiable dependency
    • libghc-tidal-doc/arm64 has unsatisfiable dependency
    • libghc-tidal-prof/arm64 has unsatisfiable dependency
    • libghc-tidal-dev/armel has unsatisfiable dependency
    • libghc-tidal-prof/armel has unsatisfiable dependency
    • libghc-tidal-dev/armhf has unsatisfiable dependency
    • libghc-tidal-prof/armhf has unsatisfiable dependency
    • libghc-tidal-dev/i386 has unsatisfiable dependency
    • libghc-tidal-prof/i386 has unsatisfiable dependency
    • libghc-tidal-dev/mips64el has unsatisfiable dependency
    • libghc-tidal-prof/mips64el has unsatisfiable dependency
    • libghc-tidal-dev/ppc64el has unsatisfiable dependency
    • libghc-tidal-prof/ppc64el has unsatisfiable dependency
    • libghc-tidal-dev/s390x has unsatisfiable dependency
    • libghc-tidal-prof/s390x has unsatisfiable dependency
    • Updating haskell-tidal would introduce bugs in testing: #1054931, #1057722
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on amd64: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on amd64: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on arm64: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on arm64: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armel: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armel: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armhf: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armhf: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on i386: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on i386: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on mips64el: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on mips64el: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on s390x: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on s390x: libghc-primitive-dev (<< 0.8)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-tidal.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 581 days old (needed 5 days)
• ruby-jekyll-coffeescript (- to 1.2.2-3)
  • Migration status for ruby-jekyll-coffeescript (- to 1.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-coffeescript would introduce bugs in testing: #1030873
    • Depends: ruby-jekyll-coffeescript ruby-coffee-script
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-coffeescript.html
    • autopkgtest for ruby-jekyll-coffeescript/1.2.2-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 581 days old (needed 5 days)
• gcc-10-doc (- to 10.4.0-1)
  • Migration status for gcc-10-doc (- to 10.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-10-doc would introduce bugs in testing: #1032733
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 584 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)
    • 584 days old (needed 5 days)
• pyrcb2 (- to 0.6.2-2)
  • Migration status for pyrcb2 (- to 0.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyrcb2 would introduce bugs in testing: #1056441, #1058431
    • autopkgtest for pyrcb2/0.6.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrcb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 586 days old (needed 5 days)
• flint-arb (- to 1:2.23.0-1)
  • Migration status for flint-arb (- to 1:2.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flint-arb would introduce bugs in testing: #1058814
    • Depends: flint-arb flint
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flint-arb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 593 days old (needed 5 days)
• php-fig-link-util (- to 1.2.0-1)
  • Migration status for php-fig-link-util (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fig-link-util would introduce bugs in testing: #947346
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fig-link-util.html
    • autopkgtest for php-fig-link-util/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 593 days old (needed 2 days)
• php-horde-rpc (- to 2.1.9-2)
  • Migration status for php-horde-rpc (- to 2.1.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-rpc php-horde-dav (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 595 days old (needed 5 days)
• apertium-cy-en (- to 0.1.1~r57554-9)
  • Migration status for apertium-cy-en (- to 0.1.1~r57554-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-cy-en would introduce bugs in testing: #1016320
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-cy-en.html
    • autopkgtest for apertium-cy-en/0.1.1~r57554-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 597 days old (needed 2 days)
• apertium-mlt-ara (- to 0.2.0~r62623-3)
  • Migration status for apertium-mlt-ara (- to 0.2.0~r62623-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-mlt-ara would introduce bugs in testing: #1016336
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-mlt-ara.html
    • 598 days old (needed 5 days)
• python-restless (- to 2.2.0-2)
  • Migration status for python-restless (- to 2.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-restless python-pyramid (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-restless.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 600 days old (needed 5 days)
• qtox (- to 1.17.6-0.1)
  • Migration status for qtox (- to 1.17.6-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for qtox/1.17.6-0.1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): qtox libtoxcore
    • Depends: qtox libtoxcore
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 602 days old (needed 5 days)
• astroquery (- to 0.4.6+dfsg-4)
  • Migration status for astroquery (- to 0.4.6+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating astroquery would introduce bugs in testing: #1057543
    • Build-Depends(-Arch): astroquery astropy-helpers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astroquery.html
    • autopkgtest for astroquery/0.4.6+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 604 days old (needed 2 days)
• ippsample (- to 0.0~git20220607.72f89b3-1)
  • Migration status for ippsample (- to 0.0~git20220607.72f89b3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ippsample would introduce bugs in testing: #1042570
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippsample.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 612 days old (needed 5 days)
• kel-agent (- to 0.4.6-2)
  • Migration status for kel-agent (- to 0.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kel-agent would introduce bugs in testing: #1033710
    • autopkgtest for kel-agent/0.4.6-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kel-agent.html
    • 612 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
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 612 days old (needed 5 days)
• python-libguess (- to 1.1-5)
  • Migration status for python-libguess (- to 1.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-libguess libguess (not considered)
    • Depends: python-libguess libguess (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-libguess.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 614 days old (needed 5 days)
• apertium-crh-tur (- to 0.3.0-2)
  • Migration status for apertium-crh-tur (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-crh-tur would introduce bugs in testing: #1016319
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-crh-tur.html
    • 615 days old (needed 5 days)
• pytest-bdd (- to 5.0.0-1)
  • Migration status for pytest-bdd (- to 5.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-bdd would introduce bugs in testing: #1042332
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-bdd.html
    • autopkgtest for pytest-bdd/5.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 616 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, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 619 days old (needed 2 days)
• libdevel-bt-perl (- to 0.06-5)
  • Migration status for libdevel-bt-perl (- to 0.06-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libdevel-bt-perl/amd64 has unsatisfiable dependency
    • libdevel-bt-perl/arm64 has unsatisfiable dependency
    • libdevel-bt-perl/armel has unsatisfiable dependency
    • libdevel-bt-perl/armhf has unsatisfiable dependency
    • libdevel-bt-perl/i386 has unsatisfiable dependency
    • libdevel-bt-perl/mips64el has unsatisfiable dependency
    • libdevel-bt-perl/ppc64el has unsatisfiable dependency
    • libdevel-bt-perl/s390x has unsatisfiable dependency
    • Updating libdevel-bt-perl would introduce bugs in testing: #1022133
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdevel-bt-perl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 619 days old (needed 5 days)
• ruby-eye (- to 0.7-5.1)
  • Migration status for ruby-eye (- to 0.7-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-eye would introduce bugs in testing: #1031479
    • autopkgtest for ruby-eye/0.7-5.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-eye ruby-celluloid-io
    • Depends: ruby-eye ruby-celluloid-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-eye.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 619 days old (needed 5 days)
• autofill-forms (- to 1.1.3-1.1)
  • Migration status for autofill-forms (- to 1.1.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autofill-forms would introduce bugs in testing: #899309
    • Build-Depends(-Arch): autofill-forms mozilla-devscripts
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autofill-forms.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 ♻
    • 620 days old (needed 5 days)
• celery-haystack-ng (- to 0.20.post2-1.1)
  • Migration status for celery-haystack-ng (- to 0.20.post2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating celery-haystack-ng would introduce bugs in testing: #999908
    • Build-Depends(-Arch): celery-haystack-ng celery
    • Depends: celery-haystack-ng celery
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/celery-haystack-ng.html
    • Reproducible on i386 - info ♻
    • 620 days old (needed 5 days)
• celery-progress (- to 0.1.1-1.1)
  • Migration status for celery-progress (- to 0.1.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): celery-progress celery (not considered)
    • Depends: celery-progress celery (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/celery-progress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 620 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 ♻, 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 ♻
    • 622 days old (needed 5 days)
• lmod (- to 8.6.19-1)
  • Migration status for lmod (- to 8.6.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lmod would introduce bugs in testing: #1052807
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lmod.html
    • autopkgtest for lmod/8.6.19-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 626 days old (needed 2 days)
• dynamic-motd (- to 0.04-1)
  • Migration status for dynamic-motd (- to 0.04-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dynamic-motd would introduce bugs in testing: #1029394
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/dynamic-motd.html
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 627 days old (needed 5 days)
• golang-github-bsm-pool (- to 0.8.0-6)
  • Migration status for golang-github-bsm-pool (- to 0.8.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-bsm-pool would introduce bugs in testing: #1017816
    • autopkgtest for golang-github-bsm-pool/0.8.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bsm-pool.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 628 days old (needed 5 days)
• ripe-atlas-sagan (- to 1.2.2-3)
  • Migration status for ripe-atlas-sagan (- to 1.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ripe-atlas-sagan would introduce bugs in testing: #1026529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ripe-atlas-sagan.html
    • 628 days old (needed 5 days)
• wikitrans (- to 1.3-2)
  • Migration status for wikitrans (- to 1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wikitrans would introduce bugs in testing: #1056360
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wikitrans.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 628 days old (needed 5 days)
• python-morris (- to 1.2-3)
  • Migration status for python-morris (- to 1.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-morris would introduce bugs in testing: #1026584
    • autopkgtest for python-morris/1.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-morris.html
    • 629 days old (needed 5 days)
• python-shade (- to 1.30.0-4)
  • Migration status for python-shade (- to 1.30.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-shade would introduce bugs in testing: #1013524
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-shade.html
    • 629 days old (needed 5 days)
• python-amqplib (- to 1.0.2-3)
  • Migration status for python-amqplib (- to 1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-amqplib would introduce bugs in testing: #1054744
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-amqplib.html
    • autopkgtest for python-amqplib/1.0.2-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 630 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 ♻, 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 ♻
    • 631 days old (needed 5 days)
• golang-github-bsm-redeo (- to 2.1.1-5)
  • Migration status for golang-github-bsm-redeo (- to 2.1.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-bsm-redeo golang-github-bsm-pool (not considered)
    • Depends: golang-github-bsm-redeo golang-github-bsm-pool (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bsm-redeo.html
    • autopkgtest for golang-github-bsm-redeo/2.1.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 632 days old (needed 2 days)
• kanboard-cli (- to 0.0.2-3)
  • Migration status for kanboard-cli (- to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kanboard-cli would introduce bugs in testing: #1060954
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kanboard-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 637 days old (needed 5 days)
• flask-testing (- to 0.8.1-2)
  • Migration status for flask-testing (- to 0.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-testing would introduce bugs in testing: #1026543
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-testing.html
    • 638 days old (needed 5 days)
• node-matrix-js-sdk (- to 9.11.0+~cs9.9.16-2)
  • Migration status for node-matrix-js-sdk (- to 9.11.0+~cs9.9.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-matrix-js-sdk would introduce bugs in testing: #1018970, #1021136, #1033621, #958692, #994213
    • Build-Depends(-Arch): node-matrix-js-sdk node-request
    • Depends: node-matrix-js-sdk node-request
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-matrix-js-sdk.html
    • autopkgtest for node-matrix-js-sdk/9.11.0+~cs9.9.16-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 638 days old (needed 5 days)
• python-future (- to 0.18.2-6)
  • Migration status for python-future (- to 0.18.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-future would introduce bugs in testing: #1042244
    • 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/p/python-future.html
    • autopkgtest for python-future/0.18.2-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 638 days old (needed 5 days)
• golang-github-siddontang-goredis (- to 0.0~git20150324.0.760763f-6)
  • Migration status for golang-github-siddontang-goredis (- to 0.0~git20150324.0.760763f-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-siddontang-goredis golang-github-alicebob-miniredis (not considered)
    • Depends: golang-github-siddontang-goredis golang-github-alicebob-miniredis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-siddontang-goredis.html
    • autopkgtest for golang-github-siddontang-goredis/0.0~git20150324.0.760763f-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 639 days old (needed 2 days)
• python-aiohttp-apispec (- to 3.0.0~b2+ds1-2)
  • Migration status for python-aiohttp-apispec (- to 3.0.0~b2+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-aiohttp-apispec python-webargs (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiohttp-apispec.html
    • autopkgtest for python-aiohttp-apispec/3.0.0~b2+ds1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 639 days old (needed 5 days)
• autoconf2.64 (- to 2.64+dfsg-1.1)
  • Migration status for autoconf2.64 (- to 2.64+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autoconf2.64 would introduce bugs in testing: #1039531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autoconf2.64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 643 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 643 days old (needed 5 days)
• provean (- to 1.1.5+ds-2)
  • Migration status for provean (- to 1.1.5+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating provean would introduce bugs in testing: #1042769
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/provean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 646 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
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 652 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
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 652 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
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 652 days old (needed 5 days)
• cider (- to 0.19.0+dfsg-3)
  • Migration status for cider (- to 0.19.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cider would introduce bugs in testing: #1017834
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cider.html
    • autopkgtest for cider/0.19.0+dfsg-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): cider clojure-mode
    • Depends: cider clojure-mode
  • Additional info:
    • Waiting for reproducibility test results on i386 - info ♻
    • 653 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
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 654 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
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 654 days old (needed 5 days)
• mysql-connector-python (- to 8.0.15-3)
  • Migration status for mysql-connector-python (- to 8.0.15-3): 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 660 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
    • Depends: openjdk-11-jre-dcevm openjdk-11
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11-jre-dcevm.html
    • New but not reproducible on amd64 - info ♻
    • 660 days old (needed 5 days)
• pulseaudio-dlna (- to 0.6.4.1-0.1)
  • Migration status for pulseaudio-dlna (- to 0.6.4.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pulseaudio-dlna would introduce bugs in testing: #1016288
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pulseaudio-dlna.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 661 days old (needed 5 days)
• django-macaddress (- to 1.5.0-3)
  • Migration status for django-macaddress (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-macaddress would introduce bugs in testing: #1054372
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-macaddress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 669 days old (needed 5 days)
• bernhard (- to 0.2.6-3)
  • Migration status for bernhard (- to 0.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bernhard would introduce bugs in testing: #1028371
    • autopkgtest for bernhard/0.2.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bernhard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 672 days old (needed 5 days)
• cerealizer (- to 0.8.1-4)
  • Migration status for cerealizer (- to 0.8.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cerealizer would introduce bugs in testing: #1026587
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cerealizer.html
    • 672 days old (needed 5 days)
• pytest-salt-factories (- to 0.907.0-4)
  • Migration status for pytest-salt-factories (- to 0.907.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-salt-factories would introduce bugs in testing: #1009804
    • autopkgtest for pytest-salt-factories/0.907.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-salt-factories.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 678 days old (needed 5 days)
• aiocoap (- to 0.4.3-0.1)
  • Migration status for aiocoap (- to 0.4.3-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiocoap would introduce bugs in testing: #1013528
    • autopkgtest for aiocoap/0.4.3-0.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiocoap.html
    • 679 days old (needed 5 days)
• dap-mode (- to 0.7-3)
  • Migration status for dap-mode (- to 0.7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dap-mode lsp-mode (not considered)
    • Invalidated by dependency
    • Depends: dap-mode lsp-treemacs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dap-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 679 days old (needed 5 days)
• glean-parser (- to 5.1.2-1)
  • Migration status for glean-parser (- to 5.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glean-parser would introduce bugs in testing: #1026750
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glean-parser.html
    • 679 days old (needed 5 days)
• lsp-java (- to 0.20211124-2)
  • Migration status for lsp-java (- to 0.20211124-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lsp-java lsp-mode (not considered)
    • Invalidated by dependency
    • Depends: lsp-java dap-mode
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsp-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 679 days old (needed 5 days)
• lsp-treemacs (- to 0.4-3)
  • Migration status for lsp-treemacs (- to 0.4-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lsp-treemacs lsp-mode (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsp-treemacs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 679 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:
    • autopkgtest for coyote/2022.04.12-1: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coyote.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 680 days old (needed 5 days)
• ntopng (- to 5.2.1+dfsg1-1)
  • Migration status for ntopng (- to 5.2.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ntopng would introduce bugs in testing: #1013302
    • Impossible Depends: ntopng -> libhiredis0.14/0.14.1-4/amd64
    • Impossible Depends: ntopng -> libhiredis0.14/0.14.1-4/arm64
    • Impossible Depends: ntopng -> libhiredis0.14/0.14.1-4/armhf
    • Impossible Depends: ntopng -> libhiredis0.14/0.14.1-4/i386
    • Impossible Depends: ntopng -> libhiredis0.14/0.14.1-4/mips64el
    • Impossible Depends: ntopng -> libhiredis0.14/0.14.1-4/ppc64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntopng.html
    • 680 days old (needed 5 days)
• courier-authlib (- to 0.71.4-1)
  • Migration status for courier-authlib (- to 0.71.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating courier-authlib would introduce bugs in testing: #987009
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-authlib.html
    • autopkgtest for courier-authlib/0.71.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 681 days old (needed 2 days)
• redmine-plugin-custom-css (- to 0.1.7+dfsg-1.1)
  • Migration status for redmine-plugin-custom-css (- to 0.1.7+dfsg-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-custom-css redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-custom-css.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 682 days old (needed 5 days)
• lives (- to 3.0.2-1.2)
  • Migration status for lives (- to 3.0.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lives/amd64 has unsatisfiable dependency
    • lives-plugins/amd64 has unsatisfiable dependency
    • lives/arm64 has unsatisfiable dependency
    • lives-plugins/arm64 has unsatisfiable dependency
    • lives/armel has unsatisfiable dependency
    • lives-plugins/armel has unsatisfiable dependency
    • lives/armhf has unsatisfiable dependency
    • lives-plugins/armhf has unsatisfiable dependency
    • lives/i386 has unsatisfiable dependency
    • lives-plugins/i386 has unsatisfiable dependency
    • lives/mips64el has unsatisfiable dependency
    • lives-plugins/mips64el has unsatisfiable dependency
    • lives/ppc64el has unsatisfiable dependency
    • lives-plugins/ppc64el has unsatisfiable dependency
    • lives/s390x has unsatisfiable dependency
    • lives-plugins/s390x has unsatisfiable dependency
    • Updating lives would introduce bugs in testing: #1013421, #1057362
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lives.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 684 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 ♻
    • 686 days old (needed 5 days)
• i2masschroq (- to 0.4.54-1)
  • Migration status for i2masschroq (- to 0.4.54-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • i2masschroq/amd64 has unsatisfiable dependency
    • i2masschroq/arm64 has unsatisfiable dependency
    • i2masschroq/armel has unsatisfiable dependency
    • i2masschroq/armhf has unsatisfiable dependency
    • i2masschroq/i386 has unsatisfiable dependency
    • i2masschroq/mips64el has unsatisfiable dependency
    • i2masschroq/ppc64el has unsatisfiable dependency
    • i2masschroq/s390x has unsatisfiable dependency
    • Updating i2masschroq would introduce bugs in testing: #1028527
    • Not built on buildd: arch amd64 binaries uploaded by lopippo
    • Not built on buildd: arch all binaries uploaded by lopippo, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/i/i2masschroq.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 693 days old (needed 5 days)
• bully (- to 1.4.00-2)
  • Migration status for bully (- to 1.4.00-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bully aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bully.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 694 days old (needed 5 days)
• xrstools (- to 0.15.0+git20210910+c147919d-3)
  • Migration status for xrstools (- to 0.15.0+git20210910+c147919d-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-xrstools/amd64 has unsatisfiable dependency
    • Updating xrstools would introduce bugs in testing: #1022504, #1056895
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/x/xrstools.html
    • Build-Depends(-Arch): xrstools pytango
    • Build-Depends(-Arch): xrstools silx
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • 697 days old (needed 5 days)
• node-node-forge (- to 1.3.0~dfsg-1)
  • Migration status for node-node-forge (- to 1.3.0~dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-node-forge would introduce bugs in testing: #1002861
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-forge.html
    • autopkgtest for node-node-forge/1.3.0~dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 702 days old (needed 5 days)
• obs-ptz (- to 0.10.4-1)
  • Migration status for obs-ptz (- to 0.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-ptz would introduce bugs in testing: #1022361
    • Build-Depends(-Arch): obs-ptz obs-studio
    • Depends: obs-ptz obs-studio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-ptz.html
    • 702 days old (needed 5 days)
• node-mermaid (- to 8.14.0+~cs11.4.14-1)
  • Migration status for node-mermaid (- to 8.14.0+~cs11.4.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mermaid would introduce bugs in testing: #1001549, #1022630, #1036688
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mermaid.html
    • autopkgtest for node-mermaid/8.14.0+~cs11.4.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 704 days old (needed 2 days)
• biometric-authentication (- to 0.9.71-1)
  • Migration status for biometric-authentication (- to 0.9.71-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): biometric-authentication libfprint (not considered)
    • Depends: biometric-authentication libfprint (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biometric-authentication.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 710 days old (needed 5 days)
• emacsql-sqlite3 (- to 1.0.2+git20220304.1.2113618-1)
  • Migration status for emacsql-sqlite3 (- to 1.0.2+git20220304.1.2113618-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacsql-sqlite3 would introduce bugs in testing: #1052967
    • autopkgtest for emacsql-sqlite3/1.0.2+git20220304.1.2113618-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacsql-sqlite3.html
    • Reproducible on i386 - info ♻
    • 712 days old (needed 5 days)
• qiskit-ibmq-provider (- to 0.4.6-4)
  • Migration status for qiskit-ibmq-provider (- to 0.4.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiskit-ibmq-provider would introduce bugs in testing: #1025181
    • autopkgtest for qiskit-ibmq-provider/0.4.6-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): qiskit-ibmq-provider qiskit-terra
    • Depends: qiskit-ibmq-provider qiskit-terra
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiskit-ibmq-provider.html
    • 712 days old (needed 5 days)
• qiskit-terra (- to 0.12.0-4)
  • Migration status for qiskit-terra (- to 0.12.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiskit-terra would introduce bugs in testing: #1027203, #1056878
    • autopkgtest for qiskit-terra/0.12.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiskit-terra.html
    • 712 days old (needed 5 days)
• rust-weedle (- to 0.12.0-2)
  • Migration status for rust-weedle (- to 0.12.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-weedle-dev/amd64 has unsatisfiable dependency
    • librust-weedle-dev/arm64 has unsatisfiable dependency
    • librust-weedle-dev/armel has unsatisfiable dependency
    • librust-weedle-dev/armhf has unsatisfiable dependency
    • librust-weedle-dev/i386 has unsatisfiable dependency
    • librust-weedle-dev/mips64el has unsatisfiable dependency
    • librust-weedle-dev/ppc64el has unsatisfiable dependency
    • librust-weedle-dev/s390x has unsatisfiable dependency
    • Updating rust-weedle would introduce bugs in testing: #1007026
    • rust-weedle unsatisfiable Build-Depends(-Arch) on amd64: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on arm64: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on armel: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on armhf: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on i386: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on mips64el: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on ppc64el: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on s390x: librust-nom-4+default-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-weedle.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 717 days old (needed 5 days)
• gm-assistant (- to 1.2.4-1)
  • Migration status for gm-assistant (- to 1.2.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gm-assistant poco (not considered)
    • Depends: gm-assistant poco (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gm-assistant.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 722 days old (needed 5 days)
• notcurses (- to 3.0.7+dfsg.1-1)
  • Migration status for notcurses (- to 3.0.7+dfsg.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating notcurses would introduce bugs in testing: #1001661, #1015747
    • autopkgtest for notcurses/3.0.7+dfsg.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notcurses.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 732 days old (needed 5 days)
• thin-provisioning-tools (- to 0.9.0-2)
  • Migration status for thin-provisioning-tools (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating thin-provisioning-tools would introduce bugs in testing: #1041089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thin-provisioning-tools.html
    • Reproducible on i386 - info ♻
    • 734 days old (needed 5 days)
• freeart (- to 3.3.0+ds1-3)
  • Migration status for freeart (- to 3.3.0+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-freeart/amd64 has unsatisfiable dependency
    • python3-freeart/arm64 has unsatisfiable dependency
    • python3-freeart/armel has unsatisfiable dependency
    • python3-freeart/armhf has unsatisfiable dependency
    • python3-freeart/i386 has unsatisfiable dependency
    • python3-freeart/mips64el has unsatisfiable dependency
    • python3-freeart/ppc64el has unsatisfiable dependency
    • Updating freeart would introduce bugs in testing: #1013606, #1056801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/freeart.html
    • Build-Depends(-Arch): freeart silx
  • 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
    • 736 days old (needed 5 days)
• atheme-services (- to 7.2.12-1)
  • Migration status for atheme-services (- to 7.2.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating atheme-services would introduce bugs in testing: #1061308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atheme-services.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 738 days old (needed 5 days)
• gsmartcontrol (- to 1.1.4-1)
  • Migration status for gsmartcontrol (- to 1.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gsmartcontrol would introduce bugs in testing: #1000074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsmartcontrol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 739 days old (needed 5 days)
• scala-mode-el (- to 1:1.1.0-3)
  • Migration status for scala-mode-el (- to 1:1.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scala-mode-el would introduce bugs in testing: #1052917
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala-mode-el.html
    • autopkgtest for scala-mode-el/1:1.1.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 739 days old (needed 2 days)
• node-devtools-protocol (- to 0.0.801017-1)
  • Migration status for node-devtools-protocol (- to 0.0.801017-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by andrius.merkys@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-devtools-protocol.html
    • autopkgtest for node-devtools-protocol/0.0.801017-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 740 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 ♻, s390x: No tests, superficial or marked flaky ♻
    • 740 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
    • Depends: node-grunt-timer node-functional.js
  • 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, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 740 days old (needed 2 days)
• consonance (- to 0.1.5-1)
  • Migration status for consonance (- to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating consonance would introduce bugs in testing: #1058213
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/consonance.html
    • autopkgtest for consonance/0.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 744 days old (needed 2 days)
• guacamole-server (- to 1.3.0-1.1)
  • Migration status for guacamole-server (- to 1.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guacamole-server would introduce bugs in testing: #1005154, #1054082
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guacamole-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 745 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 ♻
    • 747 days old (needed 5 days)
• clamfs (- to 1.2.0-2.1)
  • Migration status for clamfs (- to 1.2.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): clamfs poco (not considered)
    • Depends: clamfs poco (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clamfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• libsynthesis (- to 3.4.0.47.5+syncevolution-1.5.3-1.1)
  • Migration status for libsynthesis (- to 3.4.0.47.5+syncevolution-1.5.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsynthesis would introduce bugs in testing: #1000047
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsynthesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• dioptas (- to 0.5.2-4)
  • Migration status for dioptas (- to 0.5.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dioptas would introduce bugs in testing: #1056798
    • Build-Depends(-Arch): dioptas pyfai
    • Build-Depends(-Arch): dioptas python-future
    • Build-Depends(-Arch): dioptas python-pyepics
    • Depends: dioptas pyfai
    • Depends: dioptas python-future
    • Depends: dioptas python-pyepics
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dioptas.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 ♻
    • 751 days old (needed 5 days)
• tomogui (- to 0.3.1-2)
  • Migration status for tomogui (- to 0.3.1-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 sramacher (please contact debian-release if update is needed)
    • Build-Depends(-Arch): tomogui silx
    • Depends: tomogui silx
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tomogui.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 751 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, 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 ♻
    • 756 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 ♻, 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 ♻
    • 756 days old (needed 5 days)
• mysqmail (- to 0.4.9-10.3)
  • Migration status for mysqmail (- to 0.4.9-10.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mysqmail courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysqmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 757 days old (needed 5 days)
• fwbuilder (- to 5.3.7-5)
  • Migration status for fwbuilder (- to 5.3.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fwbuilder would introduce bugs in testing: #1049951
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fwbuilder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 759 days old (needed 5 days)
• moviepy (- to 1.0.3-2)
  • Migration status for moviepy (- to 1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating moviepy would introduce bugs in testing: #1004642
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moviepy.html
    • 759 days old (needed 5 days)
• shadowsocks-v2ray-plugin (- to 1.3.1-4)
  • Migration status for shadowsocks-v2ray-plugin (- to 1.3.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: shadowsocks-v2ray-plugin shadowsocks-libev (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shadowsocks-v2ray-plugin.html
    • autopkgtest for shadowsocks-v2ray-plugin/1.3.1-4: 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
    • 764 days old (needed 2 days)
• imdbpy (- to 2021.04.18-3)
  • Migration status for imdbpy (- to 2021.04.18-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating imdbpy would introduce bugs in testing: #1017747
    • autopkgtest for imdbpy/2021.04.18-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imdbpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 765 days old (needed 5 days)
• xcb (- to 2.4-8)
  • Migration status for xcb (- to 2.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcb would introduce bugs in testing: #1050607
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 765 days old (needed 5 days)
• libpam-ssh (- to 2.3+ds-6)
  • Migration status for libpam-ssh (- to 2.3+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpam-ssh would introduce bugs in testing: #994992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-ssh.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 770 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, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 772 days old (needed 2 days)
• massivethreads (- to 1.00-4)
  • Migration status for massivethreads (- to 1.00-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating massivethreads would introduce bugs in testing: #1014566
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/massivethreads.html
    • 775 days old (needed 5 days)
• rust-wasm-bindgen-webidl (- to 0.2.75-1)
  • Migration status for rust-wasm-bindgen-webidl (- to 0.2.75-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-wasm-bindgen-webidl-dev/amd64 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/arm64 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/armel has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/armhf has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/i386 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/mips64el has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/ppc64el has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/s390x has unsatisfiable dependency
    • Updating rust-wasm-bindgen-webidl would introduce bugs in testing: #1035417
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on amd64: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on amd64: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on arm64: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on arm64: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armel: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armel: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armhf: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armhf: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on i386: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on i386: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on mips64el: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on mips64el: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on ppc64el: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on ppc64el: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on s390x: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on s390x: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/amd64
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/arm64
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/armel
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/armhf
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/i386
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/mips64el
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/ppc64el
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/s390x
    • Build-Depends(-Arch): rust-wasm-bindgen-webidl rust-weedle
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-wasm-bindgen-webidl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 775 days old (needed 5 days)
• golang-github-go-redis-redis (- to 6.15.0-2)
  • Migration status for golang-github-go-redis-redis (- to 6.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-go-redis-redis would introduce bugs in testing: #985011
    • autopkgtest for golang-github-go-redis-redis/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-redis-redis.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 776 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 778 days old (needed 5 days)
• emacs-lsp-haskell (- to 1.0.20211214-1)
  • Migration status for emacs-lsp-haskell (- to 1.0.20211214-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: emacs-lsp-haskell lsp-mode (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-lsp-haskell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 779 days old (needed 5 days)
• emacs-lsp-ui (- to 8.0.0-1)
  • Migration status for emacs-lsp-ui (- to 8.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: emacs-lsp-ui lsp-mode (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-lsp-ui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 781 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: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-duckpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 781 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: #1050355
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledarray.html
    • 781 days old (needed 5 days)
• mlucas (- to 20.1.1-1)
  • Migration status for mlucas (- to 20.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlucas would introduce bugs in testing: #1013910, #1014547, #1027776
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlucas.html
    • Reproducible on amd64 - info ♻
    • 782 days old (needed 5 days)
• science.js (- to 1.9.3+dfsg-3)
  • Migration status for science.js (- to 1.9.3+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating science.js would introduce bugs in testing: #1058552
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/science.js.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 782 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fxsl.html
    • autopkgtest for php-fxsl/1.1.1-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 783 days old (needed 2 days)
• xtide (- to 2.15.2-1.1)
  • Migration status for xtide (- to 2.15.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xtide would introduce bugs in testing: #1026439
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xtide.html
    • 785 days old (needed 5 days)
• zmodemjs (- to 0.1.10+dfsg-2)
  • Migration status for zmodemjs (- to 0.1.10+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zmodemjs would introduce bugs in testing: #1005454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zmodemjs.html
    • 785 days old (needed 5 days)
• pplacer (- to 1.1~alpha19-6)
  • Migration status for pplacer (- to 1.1~alpha19-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pplacer would introduce bugs in testing: #1024889
    • pplacer unsatisfiable Build-Depends(-Arch) on amd64: libmcl-ocaml-dev
    • pplacer unsatisfiable Build-Depends(-Arch) on arm64: libmcl-ocaml-dev
    • pplacer unsatisfiable Build-Depends(-Arch) on ppc64el: libmcl-ocaml-dev
    • pplacer unsatisfiable Build-Depends(-Arch) on s390x: libmcl-ocaml-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplacer.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 793 days old (needed 5 days)
• kore (- to 4.1.0-6)
  • Migration status for kore (- to 4.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kore would introduce bugs in testing: #1033711
    • autopkgtest for kore/4.1.0-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 796 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:
    • Updating pixmap would introduce bugs in testing: #1054698
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pixmap.html
    • Reproducible on i386 - info ♻
    • 798 days old (needed 5 days)
• mate-optimus (- to 21.04.0-1)
  • Migration status for mate-optimus (- to 21.04.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mate-optimus would introduce bugs in testing: #987819
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-optimus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 days old (needed 5 days)
• libguess (- to 1.2-5)
  • Migration status for libguess (- to 1.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libguess gauche (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libguess.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 808 days old (needed 5 days)
• epigrass (- to 3.0.3+dfsg-2)
  • Migration status for epigrass (- to 3.0.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epigrass would introduce bugs in testing: #995966, #998265
    • autopkgtest for epigrass/3.0.3+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: epigrass numba
    • Depends: epigrass python-epimodels
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epigrass.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 809 days old (needed 5 days)
• radare2 (- to 5.5.0+dfsg-1)
  • Migration status for radare2 (- to 5.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating radare2 would introduce bugs in testing: #1014478, #950372
    • Build-Depends(-Arch): radare2 freebsd-glue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radare2.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 ♻
    • 814 days old (needed 5 days)
• python-llfuse (- to 1.4.1+dfsg-2)
  • Migration status for python-llfuse (- to 1.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-llfuse would introduce bugs in testing: #1056861
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-llfuse.html
    • autopkgtest for python-llfuse/1.4.1+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 818 days old (needed 2 days)
• netopeer2 (- to 2.0.35-1)
  • Migration status for netopeer2 (- to 2.0.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netopeer2 would introduce bugs in testing: #1001796, #1035287, #1060258, #981761
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/n/netopeer2.html
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): netopeer2 sysrepo
    • Depends: netopeer2 sysrepo
  • Additional info:
    • 819 days old (needed 5 days)
• php-sabredav (- to 1.8.12-10)
  • Migration status for php-sabredav (- to 1.8.12-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-sabredav php-sabre-vobject (not considered)
    • Depends: php-sabredav php-sabre-vobject (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabredav.html
    • autopkgtest for php-sabredav/1.8.12-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 819 days old (needed 2 days)
• ruby-diaspora-federation (- to 0.2.7-1)
  • Migration status for ruby-diaspora-federation (- to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-diaspora-federation would introduce bugs in testing: #1006031
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-diaspora-federation.html
    • autopkgtest for ruby-diaspora-federation/0.2.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 819 days old (needed 5 days)
• ruby-diaspora-federation-rails (- to 0.2.7-1)
  • Migration status for ruby-diaspora-federation-rails (- to 0.2.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-diaspora-federation-rails ruby-diaspora-federation (not considered)
    • Depends: ruby-diaspora-federation-rails ruby-diaspora-federation (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-diaspora-federation-rails.html
    • autopkgtest for ruby-diaspora-federation-rails/0.2.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 819 days old (needed 5 days)
• sysrepo (- to 2.0.53-6)
  • Migration status for sysrepo (- to 2.0.53-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sysrepo would introduce bugs in testing: #1037068, #996847
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysrepo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 819 days old (needed 5 days)
• paper-css (- to 0.4.1+ds-1)
  • Migration status for paper-css (- to 0.4.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paper-css.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 823 days old (needed 5 days)
• node-mongodb (- to 3.6.4+~cs11.13.19-2)
  • Migration status for node-mongodb (- to 3.6.4+~cs11.13.19-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mongodb would introduce bugs in testing: #1033817
    • autopkgtest for node-mongodb/3.6.4+~cs11.13.19-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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 ♻
    • 824 days old (needed 5 days)
• python-intbitset (- to 2.3.0-3.2)
  • Migration status for python-intbitset (- to 2.3.0-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-intbitset would introduce bugs in testing: #1042615, #1056860
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-intbitset.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 824 days old (needed 5 days)
• python-rocksdb (- to 0.8.0~rc3-2)
  • Migration status for python-rocksdb (- to 0.8.0~rc3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-rocksdb/amd64 has unsatisfiable dependency
    • python3-rocksdb/arm64 has unsatisfiable dependency
    • python3-rocksdb/i386 has unsatisfiable dependency
    • python3-rocksdb/mips64el has unsatisfiable dependency
    • python3-rocksdb/ppc64el has unsatisfiable dependency
    • python3-rocksdb/s390x has unsatisfiable dependency
    • Updating python-rocksdb would introduce bugs in testing: #1012074, #1056870
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-rocksdb.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 824 days old (needed 5 days)
• jquery-datetimepicker (- to 2.5.20+ds-1)
  • Migration status for jquery-datetimepicker (- to 2.5.20+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-datetimepicker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 825 days old (needed 5 days)
• jquery-sortablejs (- to 1.0.0-1)
  • Migration status for jquery-sortablejs (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-sortablejs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 825 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 ♻
    • 825 days old (needed 5 days)
• syncevolution (- to 2.0.0-3)
  • Migration status for syncevolution (- to 2.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): syncevolution libsynthesis (not considered)
    • Depends: syncevolution libsynthesis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syncevolution.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 825 days old (needed 5 days)
• glogic (- to 2.6-6)
  • Migration status for glogic (- to 2.6-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glogic would introduce bugs in testing: #1058575
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glogic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 828 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:
    • 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 ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): node-solid-keychain node-trust-webcrypto
    • Depends: node-solid-keychain node-trust-webcrypto
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-solid-keychain.html
    • 829 days old (needed 5 days)
• cpl-plugin-xshoo (- to 3.5.3+dfsg-1)
  • Migration status for cpl-plugin-xshoo (- to 3.5.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpl-plugin-xshoo would introduce bugs in testing: #1035786
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-xshoo.html
    • autopkgtest for cpl-plugin-xshoo/3.5.3+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 832 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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-roxml.html
    • Reproducible on i386 - info ♻
    • 833 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 ♻, 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 ♻
    • 839 days old (needed 5 days)
• mbdyn (- to 1.7.3-1)
  • Migration status for mbdyn (- to 1.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mbdyn would introduce bugs in testing: #999554
    • Not built on buildd: arch amd64 binaries uploaded by andrius.merkys@gmail.com
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mbdyn.html
    • 839 days old (needed 5 days)
• python-calendarweek (- to 0.5.0-1)
  • Migration status for python-calendarweek (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calendarweek.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 839 days old (needed 5 days)
• django-dbbackup (- to 3.3.0-1)
  • Migration status for django-dbbackup (- to 3.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-dbbackup.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 842 days old (needed 5 days)
• django-favicon-plus-reloaded (- to 1.1.3-1)
  • Migration status for django-favicon-plus-reloaded (- to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-favicon-plus-reloaded.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 842 days old (needed 5 days)
• django-otp-yubikey (- to 1.0.0.post1-1)
  • Migration status for django-otp-yubikey (- to 1.0.0.post1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-otp-yubikey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 842 days old (needed 5 days)
• django-titofisto (- to 0.1.2.post1-1)
  • Migration status for django-titofisto (- to 0.1.2.post1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-titofisto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 842 days old (needed 5 days)
• django-widget-tweaks (- to 1.4.8-1)
  • Migration status for django-widget-tweaks (- to 1.4.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-widget-tweaks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 842 days old (needed 5 days)
• cpl-plugin-fors (- to 5.5.7+dfsg-2)
  • Migration status for cpl-plugin-fors (- to 5.5.7+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpl-plugin-fors would introduce bugs in testing: #1035696
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-fors.html
    • autopkgtest for cpl-plugin-fors/5.5.7+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 843 days old (needed 5 days)
• pprofile (- to 2.1.0-1)
  • Migration status for pprofile (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pprofile would introduce bugs in testing: #1058191
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pprofile.html
    • autopkgtest for pprofile/2.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 843 days old (needed 2 days)
• python-sshoot (- to 1.4.2-2)
  • Migration status for python-sshoot (- to 1.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-sshoot would introduce bugs in testing: #1013601
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sshoot.html
    • autopkgtest for python-sshoot/1.4.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 844 days old (needed 2 days)
• vast (- to 2021.05.27-8)
  • Migration status for vast (- to 2021.05.27-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vast/amd64 has unsatisfiable dependency
    • vast/arm64 has unsatisfiable dependency
    • vast/ppc64el has unsatisfiable dependency
    • vast/s390x has unsatisfiable dependency
    • Updating vast would introduce bugs in testing: #1001527
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vast.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
    • 845 days old (needed 5 days)
• ganglia (- to 3.7.2-6)
  • Migration status for ganglia (- to 3.7.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ganglia would introduce bugs in testing: #1000041
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia.html
    • autopkgtest for ganglia/3.7.2-6: 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
    • 846 days old (needed 2 days)
• golang-github-gambol99-go-marathon (- to 0.7.1-1)
  • Migration status for golang-github-gambol99-go-marathon (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alois@micard.lu, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gambol99-go-marathon.html
    • autopkgtest for golang-github-gambol99-go-marathon/0.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 847 days old (needed 2 days)
• python-gear (- to 0.5.8-6)
  • Migration status for python-gear (- to 0.5.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-gear would introduce bugs in testing: #1002430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gear.html
    • 848 days old (needed 5 days)
• ruby-github-pages-health-check (- to 1.16.1-3)
  • Migration status for ruby-github-pages-health-check (- to 1.16.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-github-pages-health-check/amd64 has unsatisfiable dependency
    • ruby-github-pages-health-check/arm64 has unsatisfiable dependency
    • Updating ruby-github-pages-health-check would introduce bugs in testing: #1059697
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-github-pages-health-check.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 850 days old (needed 5 days)
• laminar (- to 1.1-1)
  • Migration status for laminar (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating laminar would introduce bugs in testing: #1019455
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/laminar.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 851 days old (needed 5 days)
• toxic (- to 0.11.1-3)
  • Migration status for toxic (- to 0.11.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): toxic libtoxcore (not considered)
    • Depends: toxic libtoxcore (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toxic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 859 days old (needed 5 days)
• grok (- to 1.20110708.1-7)
  • Migration status for grok (- to 1.20110708.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grok would introduce bugs in testing: #1000065
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grok.html
    • autopkgtest for grok/1.20110708.1-7: 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
    • 861 days old (needed 2 days)
• obs-websocket (- to 4.9.0-2)
  • Migration status for obs-websocket (- to 4.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-websocket would introduce bugs in testing: #1006040
    • Build-Depends(-Arch): obs-websocket obs-studio
    • Depends: obs-websocket obs-studio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-websocket.html
    • 861 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:
    • Updating prads would introduce bugs in testing: #999984
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prads.html
    • autopkgtest for prads/0.3.3-7: 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
    • 861 days old (needed 2 days)
• gabedit (- to 2.5.1+ds-1)
  • Migration status for gabedit (- to 2.5.1+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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 armhf - info ♻
    • Reproducible on i386 - info ♻
    • 862 days old (needed 5 days)
• php-webimpress-safe-writer (- to 2.2.0-1)
  • Migration status for php-webimpress-safe-writer (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-webimpress-safe-writer would introduce bugs in testing: #981233
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-webimpress-safe-writer.html
    • autopkgtest for php-webimpress-safe-writer/2.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 863 days old (needed 2 days)
• info-beamer (- to 1.0~pre3+dfsg-0.2)
  • Migration status for info-beamer (- to 1.0~pre3+dfsg-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • info-beamer/amd64 has unsatisfiable dependency
    • info-beamer/arm64 has unsatisfiable dependency
    • info-beamer/armel has unsatisfiable dependency
    • info-beamer/armhf has unsatisfiable dependency
    • info-beamer/i386 has unsatisfiable dependency
    • info-beamer/mips64el has unsatisfiable dependency
    • info-beamer/ppc64el has unsatisfiable dependency
    • info-beamer/s390x has unsatisfiable dependency
    • Updating info-beamer would introduce bugs in testing: #1004823
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/i/info-beamer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 865 days old (needed 5 days)
• trololio (- to 1.0-3)
  • Migration status for trololio (- to 1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trololio would introduce bugs in testing: #1059673
    • autopkgtest for trololio/1.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trololio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 865 days old (needed 5 days)
• sphinx-rst-builder (- to 0.0.3-3)
  • Migration status for sphinx-rst-builder (- to 0.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sphinx-rst-builder would introduce bugs in testing: #1042587
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-rst-builder.html
    • Reproducible on i386 - info ♻
    • 867 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
  • 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
    • 870 days old (needed 5 days)
• nvchecker (- to 2.5-1)
  • Migration status for nvchecker (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nvchecker/2.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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 ♻
    • 872 days old (needed 5 days)
• basemap (- to 1.2.2+dfsg-2)
  • Migration status for basemap (- to 1.2.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mpltoolkits.basemap/amd64 has unsatisfiable dependency
    • python3-mpltoolkits.basemap/arm64 has unsatisfiable dependency
    • python3-mpltoolkits.basemap/armel has unsatisfiable dependency
    • python3-mpltoolkits.basemap/armhf has unsatisfiable dependency
    • python3-mpltoolkits.basemap/i386 has unsatisfiable dependency
    • python3-mpltoolkits.basemap/mips64el has unsatisfiable dependency
    • python3-mpltoolkits.basemap/ppc64el has unsatisfiable dependency
    • python3-mpltoolkits.basemap/s390x has unsatisfiable dependency
    • Updating basemap would introduce bugs in testing: #1009424, #1056789
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/basemap.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
    • 875 days old (needed 5 days)
• ggcov (- to 0.10-4)
  • Migration status for ggcov (- to 0.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ggcov would introduce bugs in testing: #1020263
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ggcov.html
    • 876 days old (needed 5 days)
• vim-scripts (- to 20210124.2)
  • Migration status for vim-scripts (- to 20210124.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vim-scripts would introduce bugs in testing: #1051063
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-scripts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 880 days old (needed 5 days)
• blastem (- to 0.6.3.4-1)
  • Migration status for blastem (- to 0.6.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating blastem would introduce bugs in testing: #1054661
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blastem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 881 days old (needed 5 days)
• node-eslint-plugin-requirejs (- to 4.0.1-1)
  • Migration status for node-eslint-plugin-requirejs (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-eslint-plugin-requirejs would introduce bugs in testing: #1060930
    • autopkgtest for node-eslint-plugin-requirejs/4.0.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-eslint-plugin-requirejs.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 882 days old (needed 5 days)
• ap-utils (- to 1.5-5)
  • Migration status for ap-utils (- to 1.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ap-utils would introduce bugs in testing: #1057542
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ap-utils.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 884 days old (needed 5 days)
• mdk3 (- to 6.0-8)
  • Migration status for mdk3 (- to 6.0-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mdk3 aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdk3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 893 days old (needed 5 days)
• mdk4 (- to 4.2-3)
  • Migration status for mdk4 (- to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mdk4 aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdk4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 893 days old (needed 5 days)
• shotdetect (- to 1.0.86-6)
  • Migration status for shotdetect (- to 1.0.86-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • shotdetect/amd64 has unsatisfiable dependency
    • shotdetect/arm64 has unsatisfiable dependency
    • shotdetect/armel has unsatisfiable dependency
    • shotdetect/armhf has unsatisfiable dependency
    • shotdetect/i386 has unsatisfiable dependency
    • shotdetect/mips64el has unsatisfiable dependency
    • shotdetect/ppc64el has unsatisfiable dependency
    • shotdetect/s390x has unsatisfiable dependency
    • Updating shotdetect would introduce bugs in testing: #1004719
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/shotdetect.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 894 days old (needed 5 days)
• backupchecker (- to 1.7-3)
  • Migration status for backupchecker (- to 1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backupchecker would introduce bugs in testing: #1002409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backupchecker.html
    • 897 days old (needed 5 days)
• snort (- to 2.9.15.1-6)
  • Migration status for snort (- to 2.9.15.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • snort-common-libraries/ppc64el has unsatisfiable dependency
    • Updating snort would introduce bugs in testing: #1019230, #1021276, #1064328, #999956
    • snort unsatisfiable Build-Depends(-Arch) on ppc64el: libluajit-5.1-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snort.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 900 days old (needed 5 days)
• eclipse-tracecompass (- to 7.0.0+repack-1)
  • Migration status for eclipse-tracecompass (- to 7.0.0+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • eclipse-tracecompass/amd64 has unsatisfiable dependency
    • eclipse-tracecompass/arm64 has unsatisfiable dependency
    • Updating eclipse-tracecompass would introduce bugs in testing: #1010983, #1035594
    • eclipse-tracecompass unsatisfiable Build-Depends(-Arch) on amd64: libequinox-p2-ui-sdk-java
    • Build-Depends(-Arch): eclipse-tracecompass eclipse-cdt
    • Build-Depends(-Arch): eclipse-tracecompass eclipse-remote
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/eclipse-tracecompass.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 906 days old (needed 5 days)
• prewikka (- to 5.2.0-2)
  • Migration status for prewikka (- to 5.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prewikka would introduce bugs in testing: #1060985
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prewikka.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 908 days old (needed 5 days)
• gcc-9-doc (- to 9.4.0-1)
  • Migration status for gcc-9-doc (- to 9.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-doc would introduce bugs in testing: #995061
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 913 days old (needed 5 days)
• libglade2 (- to 1:2.6.4-2.4)
  • Migration status for libglade2 (- to 1:2.6.4-2.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libglade2 would introduce bugs in testing: #895517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libglade2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 913 days old (needed 5 days)
• onedrivesdk (- to 1.1.8-3)
  • Migration status for onedrivesdk (- to 1.1.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating onedrivesdk would introduce bugs in testing: #1025016
    • autopkgtest for onedrivesdk/1.1.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onedrivesdk.html
    • 913 days old (needed 5 days)
• morty (- to 0.2.0-3)
  • Migration status for morty (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating morty would introduce bugs in testing: #1052139
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morty.html
    • autopkgtest for morty/0.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 916 days old (needed 2 days)
• purify (- to 2.0.0-6)
  • Migration status for purify (- to 2.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libpurify2.0/amd64 has unsatisfiable dependency
    • purify/amd64 has unsatisfiable dependency
    • libpurify2.0/arm64 has unsatisfiable dependency
    • purify/arm64 has unsatisfiable dependency
    • libpurify2.0/armel has unsatisfiable dependency
    • purify/armel has unsatisfiable dependency
    • libpurify2.0/armhf has unsatisfiable dependency
    • purify/armhf has unsatisfiable dependency
    • libpurify2.0/i386 has unsatisfiable dependency
    • purify/i386 has unsatisfiable dependency
    • libpurify2.0/ppc64el has unsatisfiable dependency
    • purify/ppc64el has unsatisfiable dependency
    • libpurify2.0/s390x has unsatisfiable dependency
    • purify/s390x has unsatisfiable dependency
    • Updating purify would introduce bugs in testing: #1001528
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/purify.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 922 days old (needed 5 days)
• libpam-tacplus (- to 1.3.8-2.1)
  • Migration status for libpam-tacplus (- to 1.3.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpam-tacplus would introduce bugs in testing: #1009966
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-tacplus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 934 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 ♻
    • 950 days old (needed 5 days)
• qiskit-aer (- to 0.4.1-2)
  • Migration status for qiskit-aer (- to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-qiskit-aer/amd64 has unsatisfiable dependency
    • python3-qiskit-aer/arm64 has unsatisfiable dependency
    • python3-qiskit-aer/armhf has unsatisfiable dependency
    • python3-qiskit-aer/i386 has unsatisfiable dependency
    • python3-qiskit-aer/mips64el has unsatisfiable dependency
    • python3-qiskit-aer/ppc64el has unsatisfiable dependency
    • Updating qiskit-aer would introduce bugs in testing: #1027206, #1028896, #1056881
    • Build-Depends(-Arch): qiskit-aer qiskit-terra
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/q/qiskit-aer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 967 days old (needed 5 days)
• squid-deb-proxy (- to 0.8.15+nmu1)
  • Migration status for squid-deb-proxy (- to 0.8.15+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squid-deb-proxy would introduce bugs in testing: #932501, #999646
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squid-deb-proxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 980 days old (needed 5 days)
• mialmpick (- to 0.2.15-2)
  • Migration status for mialmpick (- to 0.2.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mialmpick libglade2 (not considered)
    • Depends: mialmpick libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): mialmpick gtkglext
    • Depends: mialmpick gtkglext
  • 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 ♻
    • 996 days old (needed 5 days)
• whizzytex (- to 1.3.7-1)
  • Migration status for whizzytex (- to 1.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating whizzytex would introduce bugs in testing: #1059088
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whizzytex.html
    • autopkgtest for whizzytex/1.3.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 999 days old (needed 2 days)
• slic3r (- to 1.3.0+dfsg1-5)
  • Migration status for slic3r (- to 1.3.0+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • slic3r/i386 has unsatisfiable dependency
    • Updating slic3r would introduce bugs in testing: #1034848
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r.html
    • uninstallable on arch i386, not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1033 days old (needed 5 days)
• davs2 (- to 1.6-1)
  • Migration status for davs2 (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating davs2 would introduce bugs in testing: #1024722
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/davs2.html
    • New but not reproducible on amd64 - info ♻
    • 1047 days old (needed 5 days)
• xavs2 (- to 1.3-1)
  • Migration status for xavs2 (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xavs2 would introduce bugs in testing: #1024723
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xavs2.html
    • New but not reproducible on amd64 - info ♻
    • 1047 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 ♻, 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 ♻
    • 1051 days old (needed 5 days)
• spdx-licenses (- to 3.8+dfsg-3)
  • Migration status for spdx-licenses (- to 3.8+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spdx-licenses would introduce bugs in testing: #975120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spdx-licenses.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1052 days old (needed 5 days)
• mpdecimal (- to 2.5.1-2)
  • Migration status for mpdecimal (- to 2.5.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mpdecimal would introduce bugs in testing: #1013395
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpdecimal.html
    • 1065 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 ♻
    • 1069 days old (needed 5 days)
• svtplay-dl (- to 3.0-2)
  • Migration status for svtplay-dl (- to 3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating svtplay-dl would introduce bugs in testing: #1061023
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/svtplay-dl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1077 days old (needed 5 days)
• eiskaltdcpp (- to 2.4.2-1)
  • Migration status for eiskaltdcpp (- to 2.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eiskaltdcpp would introduce bugs in testing: #1000100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eiskaltdcpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1087 days old (needed 5 days)
• enigmail (- to 2:2.2.4-0.3)
  • Migration status for enigmail (- to 2:2.2.4-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating enigmail would introduce bugs in testing: #1030186, #975926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enigmail.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • 1088 days old (needed 5 days)
• rust-rust-code-analysis-cli (- to 0.0.19-1)
  • Migration status for rust-rust-code-analysis-cli (- to 0.0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-rust-code-analysis-cli would introduce bugs in testing: #1017649
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-0.7+default-dev
    • Build-Depends(-Arch): rust-rust-code-analysis-cli rust-rust-code-analysis
    • Built-Using: rust-rust-code-analysis-cli rust-rust-code-analysis
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rust-code-analysis-cli.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 ♻
    • 1096 days old (needed 5 days)
• hotspot (- to 1.3.0-2)
  • Migration status for hotspot (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hotspot would introduce bugs in testing: #1025573
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hotspot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1097 days old (needed 5 days)
• libvma (- to 9.2.2-1)
  • Migration status for libvma (- to 9.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libvma would introduce bugs in testing: #1021852
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvma.html
    • 1097 days old (needed 5 days)
• utox (- to 0.18.1-1)
  • Migration status for utox (- to 0.18.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): utox libtoxcore (not considered)
    • Depends: utox libtoxcore (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utox.html
    • autopkgtest for utox/0.18.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1099 days old (needed 2 days)
• fonts-cascadia-code (- to 2102.03-1)
  • Migration status for fonts-cascadia-code (- to 2102.03-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-cascadia-code would introduce bugs in testing: #997317
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-cascadia-code.html
    • 1101 days old (needed 5 days)
• php-facedetect (- to 1.1.0-19-g135c72a-2)
  • Migration status for php-facedetect (- to 1.1.0-19-g135c72a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-facedetect/amd64 has unsatisfiable dependency
    • php-facedetect/arm64 has unsatisfiable dependency
    • php-facedetect/armel has unsatisfiable dependency
    • php-facedetect/armhf has unsatisfiable dependency
    • php-facedetect/i386 has unsatisfiable dependency
    • php-facedetect/mips64el has unsatisfiable dependency
    • php-facedetect/ppc64el has unsatisfiable dependency
    • php-facedetect/s390x has unsatisfiable dependency
    • Updating php-facedetect would introduce bugs in testing: #1020977
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-facedetect.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1103 days old (needed 5 days)
• slib (- to 3b6-3)
  • Migration status for slib (- to 3b6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for slib/3b6-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): slib mit-scheme
    • Build-Depends(-Arch): slib scm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slib.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1103 days old (needed 5 days)
• aiorwlock (- to 1.0.0-0.2)
  • Migration status for aiorwlock (- to 1.0.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiorwlock would introduce bugs in testing: #997106
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiorwlock.html
    • autopkgtest for aiorwlock/1.0.0-0.2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1108 days old (needed 5 days)
• mydumper (- to 0.10.1-1)
  • Migration status for mydumper (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mydumper would introduce bugs in testing: #1000014
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mydumper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1108 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 ♻
    • 1109 days old (needed 5 days)
• zeek (- to 3.2.3+ds2-2)
  • Migration status for zeek (- to 3.2.3+ds2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • zeek/amd64 has unsatisfiable dependency
    • zeek/arm64 has unsatisfiable dependency
    • zeek/armel has unsatisfiable dependency
    • zeek/armhf has unsatisfiable dependency
    • zeek/i386 has unsatisfiable dependency
    • zeek/mips64el has unsatisfiable dependency
    • zeek/ppc64el has unsatisfiable dependency
    • zeek/s390x has unsatisfiable dependency
    • Updating zeek would introduce bugs in testing: #1002760
    • Build-Depends(-Arch): zeek broker
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/z/zeek.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1109 days old (needed 5 days)
• spyder-memory-profiler (- to 0.2.1-1)
  • Migration status for spyder-memory-profiler (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spyder-memory-profiler would introduce bugs in testing: #1035493
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/spyder-memory-profiler.html
    • autopkgtest for spyder-memory-profiler/0.2.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • 1110 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
    • 1111 days old (needed 5 days)
• scmail (- to 1.3-4.1)
  • Migration status for scmail (- to 1.3-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): scmail gauche (not considered)
    • Depends: scmail gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1111 days old (needed 5 days)
• ruby-upr (- to 0.3.0-3)
  • Migration status for ruby-upr (- to 0.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-upr would introduce bugs in testing: #1030689
    • autopkgtest for ruby-upr/0.3.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-upr ruby-moneta
    • Depends: ruby-upr ruby-moneta
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-upr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1112 days old (needed 5 days)
• apertium-kaz-tat (- to 0.2.1-1)
  • Migration status for apertium-kaz-tat (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-kaz-tat would introduce bugs in testing: #1005670
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-kaz-tat.html
    • 1113 days old (needed 5 days)
• apertium-sme-nob (- to 0.6.1+ds.1-2)
  • Migration status for apertium-sme-nob (- to 0.6.1+ds.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-sme-nob would introduce bugs in testing: #1008348
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-sme-nob.html
    • 1113 days old (needed 5 days)
• rust-libnotcurses-sys (- to 2.1.8-1)
  • Migration status for rust-libnotcurses-sys (- to 2.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-libnotcurses-sys would introduce bugs in testing: #985813
    • autopkgtest for rust-libnotcurses-sys/blocked-on-ci-infra: amd64: Regression or new test ♻
    • Build-Depends(-Arch): rust-libnotcurses-sys notcurses
    • Depends: rust-libnotcurses-sys notcurses
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libnotcurses-sys.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 1113 days old (needed 5 days)
• cadvisor (- to 0.38.7+ds1-2)
  • Migration status for cadvisor (- to 0.38.7+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cadvisor would introduce bugs in testing: #1005678, #1027994
    • cadvisor/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/amd64 has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/amd64 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/arm64 has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/arm64 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/armel has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/armel has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/armhf has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/armhf has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/i386 has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/i386 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/mips64el has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/mips64el has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/ppc64el has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/ppc64el has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/s390x has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/s390x has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cadvisor.html
    • autopkgtest for cadvisor/0.38.7+ds1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1114 days old (needed 2 days)
• picprog (- to 1.9.1-5)
  • Migration status for picprog (- to 1.9.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating picprog would introduce bugs in testing: #946039
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picprog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1114 days old (needed 5 days)
• golang-github-alicebob-miniredis (- to 2.2.1-5)
  • Migration status for golang-github-alicebob-miniredis (- to 2.2.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-alicebob-miniredis golang-github-bsm-redeo (not considered)
    • Depends: golang-github-alicebob-miniredis golang-github-bsm-redeo (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alicebob-miniredis.html
    • autopkgtest for golang-github-alicebob-miniredis/2.2.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1115 days old (needed 2 days)
• actdiag (- to 2.0.0+dfsg-1)
  • Migration status for actdiag (- to 2.0.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating actdiag would introduce bugs in testing: #1042159
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/actdiag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1116 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 ♻
    • 1116 days old (needed 5 days)
• sphinxcontrib-actdiag (- to 2.0.0-1)
  • Migration status for sphinxcontrib-actdiag (- 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): sphinxcontrib-actdiag actdiag (not considered)
    • Depends: sphinxcontrib-actdiag actdiag (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-actdiag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1116 days old (needed 5 days)
• sphinxcontrib-nwdiag (- to 2.0.0-1)
  • Migration status for sphinxcontrib-nwdiag (- 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): sphinxcontrib-nwdiag nwdiag (not considered)
    • Depends: sphinxcontrib-nwdiag nwdiag (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-nwdiag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1116 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
    • 1116 days old (needed 5 days)
• backdoor-factory (- to 3.4.2+dfsg-5)
  • Migration status for backdoor-factory (- to 3.4.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backdoor-factory would introduce bugs in testing: #1027037
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backdoor-factory.html
    • autopkgtest for backdoor-factory/3.4.2+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1117 days old (needed 2 days)
• pympler (- to 0.9+dfsg1-2)
  • Migration status for pympler (- to 0.9+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pympler would introduce bugs in testing: #1002173
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pympler.html
    • autopkgtest for pympler/0.9+dfsg1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1119 days old (needed 5 days)
• dfvfs (- to 20201219-1)
  • Migration status for dfvfs (- to 20201219-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dfvfs would introduce bugs in testing: #998527
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dfvfs.html
    • 1121 days old (needed 5 days)
• js2-mode (- to 0~20201220-1)
  • Migration status for js2-mode (- to 0~20201220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating js2-mode would introduce bugs in testing: #1052865
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/js2-mode.html
    • Reproducible on i386 - info ♻
    • 1121 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, 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
    • 1121 days old (needed 2 days)
• emacs-db (- to 0.0.6+git20140421.b3a423f-3)
  • Migration status for emacs-db (- to 0.0.6+git20140421.b3a423f-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): emacs-db emacs-kv (not considered)
    • Depends: emacs-db emacs-kv (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-db.html
    • autopkgtest for emacs-db/0.0.6+git20140421.b3a423f-3: 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
    • 1122 days old (needed 2 days)
• emacs-kv (- to 0.0.19+git20140108.7211484-4)
  • Migration status for emacs-kv (- to 0.0.19+git20140108.7211484-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-kv would introduce bugs in testing: #1052933
    • autopkgtest for emacs-kv/0.0.19+git20140108.7211484-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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-kv.html
    • Reproducible on i386 - info ♻
    • 1122 days old (needed 5 days)
• sagan (- to 1.2.0-1.2)
  • Migration status for sagan (- to 1.2.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sagan would introduce bugs in testing: #999968
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagan.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1122 days old (needed 5 days)
• vg (- to 1.30.0+ds-1)
  • Migration status for vg (- to 1.30.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vg/amd64 has unsatisfiable dependency
    • vg/mips64el has unsatisfiable dependency
    • Updating vg would introduce bugs in testing: #1013061
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • 1122 days old (needed 5 days)
• persp-projectile (- to 1:0.2.0-4)
  • Migration status for persp-projectile (- to 1:0.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating persp-projectile would introduce bugs in testing: #919035
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/persp-projectile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1125 days old (needed 5 days)
• srslte (- to 18.06.1+ds.1-1)
  • Migration status for srslte (- to 18.06.1+ds.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • srsenb/amd64 has unsatisfiable dependency
    • srsepc/amd64 has unsatisfiable dependency
    • srslte-core/amd64 has unsatisfiable dependency
    • srsue/amd64 has unsatisfiable dependency
    • srsenb/arm64 has unsatisfiable dependency
    • srsepc/arm64 has unsatisfiable dependency
    • srslte-core/arm64 has unsatisfiable dependency
    • srsue/arm64 has unsatisfiable dependency
    • srsenb/armel has unsatisfiable dependency
    • srsepc/armel has unsatisfiable dependency
    • srslte-core/armel has unsatisfiable dependency
    • srsue/armel has unsatisfiable dependency
    • srsenb/armhf has unsatisfiable dependency
    • srsepc/armhf has unsatisfiable dependency
    • srslte-core/armhf has unsatisfiable dependency
    • srsue/armhf has unsatisfiable dependency
    • srsenb/i386 has unsatisfiable dependency
    • srsepc/i386 has unsatisfiable dependency
    • srslte-core/i386 has unsatisfiable dependency
    • srsue/i386 has unsatisfiable dependency
    • srsenb/mips64el has unsatisfiable dependency
    • srsepc/mips64el has unsatisfiable dependency
    • srslte-core/mips64el has unsatisfiable dependency
    • srsue/mips64el has unsatisfiable dependency
    • srsenb/ppc64el has unsatisfiable dependency
    • srsepc/ppc64el has unsatisfiable dependency
    • srslte-core/ppc64el has unsatisfiable dependency
    • srsue/ppc64el has unsatisfiable dependency
    • srsenb/s390x has unsatisfiable dependency
    • srsepc/s390x has unsatisfiable dependency
    • srslte-core/s390x has unsatisfiable dependency
    • srsue/s390x has unsatisfiable dependency
    • Updating srslte would introduce bugs in testing: #982113, #993701
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/srslte.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch 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
    • 1125 days old (needed 5 days)
• python-dugong (- to 3.8.1+dfsg-1)
  • Migration status for python-dugong (- to 3.8.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-dugong would introduce bugs in testing: #1002102
    • autopkgtest for python-dugong/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dugong.html
    • 1126 days old (needed 5 days)
• tulip (- to 5.4.0+dfsg-3)
  • Migration status for tulip (- to 5.4.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): tulip sip4 (not considered)
    • Depends: tulip sip4 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tulip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 1130 days old (needed 5 days)
• stylish-haskell (- to 0.12.2.0-1)
  • Migration status for stylish-haskell (- to 0.12.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stylish-haskell would introduce bugs in testing: #1017205
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-strict-dev (<< 0.5)
    • Build-Depends(-Arch): stylish-haskell haskell-hsyaml
    • Build-Depends(-Arch): stylish-haskell haskell-hsyaml-aeson
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stylish-haskell.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1131 days old (needed 5 days)
• trufont (- to 0.6.6+ds-2)
  • Migration status for trufont (- to 0.6.6+ds-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): trufont python-hsluv (not considered)
    • Depends: trufont python-hsluv (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trufont.html
    • autopkgtest for trufont/0.6.6+ds-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1131 days old (needed 5 days)
• golang-github-manyminds-api2go (- to 1.0-RC4-1)
  • Migration status for golang-github-manyminds-api2go (- to 1.0-RC4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-manyminds-api2go would introduce bugs in testing: #1008425
    • autopkgtest for golang-github-manyminds-api2go/1.0-RC4-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-manyminds-api2go.html
    • 1132 days old (needed 5 days)
• gauche-c-wrapper (- to 0.6.1-12)
  • Migration status for gauche-c-wrapper (- to 0.6.1-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gauche-c-wrapper gauche (not considered)
    • Depends: gauche-c-wrapper gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche-c-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1134 days old (needed 5 days)
• khronos-opencl-man (- to 1.0~svn33624-5)
  • Migration status for khronos-opencl-man (- to 1.0~svn33624-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): khronos-opencl-man w3-dtd-mathml (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khronos-opencl-man.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1134 days old (needed 5 days)
• qstopmotion (- to 2.5.2-1)
  • Migration status for qstopmotion (- to 2.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qstopmotion would introduce bugs in testing: #1058520
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qstopmotion.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1134 days old (needed 5 days)
• subvertpy (- to 0.11.0-1)
  • Migration status for subvertpy (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-subvertpy/amd64 has unsatisfiable dependency
    • python3-subvertpy/arm64 has unsatisfiable dependency
    • python3-subvertpy/armel has unsatisfiable dependency
    • python3-subvertpy/armhf has unsatisfiable dependency
    • python3-subvertpy/i386 has unsatisfiable dependency
    • python3-subvertpy/mips64el has unsatisfiable dependency
    • python3-subvertpy/ppc64el has unsatisfiable dependency
    • python3-subvertpy/s390x has unsatisfiable dependency
    • Updating subvertpy would introduce bugs in testing: #1009423
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/subvertpy.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1138 days old (needed 5 days)
• golang-github-ajg-form (- to 1.5+git20160822.523a5da-1.1)
  • Migration status for golang-github-ajg-form (- to 1.5+git20160822.523a5da-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-ajg-form would introduce bugs in testing: #997539
    • autopkgtest for golang-github-ajg-form/1.5+git20160822.523a5da-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ajg-form.html
    • 1139 days old (needed 5 days)
• lsdb (- to 0.11-10.2)
  • Migration status for lsdb (- to 0.11-10.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lsdb would introduce bugs in testing: #965706
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsdb.html
    • 1139 days old (needed 5 days)
• tldjs (- to 2.3.1-1.1)
  • Migration status for tldjs (- to 2.3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tldjs would introduce bugs in testing: #986436
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tldjs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1139 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
    • 1140 days old (needed 5 days)
• jodd (- to 3.8.6-1.1)
  • Migration status for jodd (- to 3.8.6-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jodd would introduce bugs in testing: #961298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jodd.html
    • 1140 days old (needed 5 days)
• xneur (- to 0.20.0-3)
  • Migration status for xneur (- to 0.20.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xneur would introduce bugs in testing: #1037902, #999922
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xneur.html
    • Reproducible on i386 - info ♻
    • 1140 days old (needed 5 days)
• focalinux (- to 2010-09-3.1)
  • Migration status for focalinux (- to 2010-09-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating focalinux would introduce bugs in testing: #1051055
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/focalinux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1141 days old (needed 5 days)
• giblib (- to 1.2.4-13)
  • Migration status for giblib (- to 1.2.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating giblib would introduce bugs in testing: #1018021
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/giblib.html
    • 1141 days old (needed 5 days)
• jquery-simpletreemenu (- to 1.5.0-2.1)
  • Migration status for jquery-simpletreemenu (- to 1.5.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jquery-simpletreemenu would introduce bugs in testing: #979940
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-simpletreemenu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1141 days old (needed 5 days)
• golang-github-filosottile-b2 (- to 0.0~git20170207.b197f7a-1)
  • Migration status for golang-github-filosottile-b2 (- to 0.0~git20170207.b197f7a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-filosottile-b2.html
    • autopkgtest for golang-github-filosottile-b2/0.0~git20170207.b197f7a-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1142 days old (needed 2 days)
• golang-github-gopherjs-jsbuiltin (- to 0.0~git20180426.5009155-1)
  • Migration status for golang-github-gopherjs-jsbuiltin (- to 0.0~git20180426.5009155-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gopherjs-jsbuiltin.html
    • autopkgtest for golang-github-gopherjs-jsbuiltin/0.0~git20180426.5009155-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1142 days old (needed 2 days)
• golang-github-nf-cr2 (- to 0.0~git20180623.4699471-1)
  • Migration status for golang-github-nf-cr2 (- to 0.0~git20180623.4699471-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-nf-cr2.html
    • autopkgtest for golang-github-nf-cr2/0.0~git20180623.4699471-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1142 days old (needed 2 days)
• golang-github-tomnomnom-linkheader (- to 0.1.0+git20180905.02ca582-1)
  • Migration status for golang-github-tomnomnom-linkheader (- to 0.1.0+git20180905.02ca582-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-tomnomnom-linkheader.html
    • autopkgtest for golang-github-tomnomnom-linkheader/0.1.0+git20180905.02ca582-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1142 days old (needed 2 days)
• graypy (- to 2.1.0-1)
  • Migration status for graypy (- to 2.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): graypy python-amqplib (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graypy.html
    • autopkgtest for graypy/2.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1142 days old (needed 2 days)
• jwchat (- to 1.0+dfsg-1.5)
  • Migration status for jwchat (- to 1.0+dfsg-1.5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: jwchat jsjac (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jwchat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1142 days old (needed 5 days)
• ruby-omniauth-bitbucket (- to 0.0.2-1.1)
  • Migration status for ruby-omniauth-bitbucket (- to 0.0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-bitbucket would introduce bugs in testing: #1030812
    • autopkgtest for ruby-omniauth-bitbucket/0.0.2-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-bitbucket.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1142 days old (needed 5 days)
• ripe-atlas-tools (- to 2.3.0-2.1)
  • Migration status for ripe-atlas-tools (- to 2.3.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ripe-atlas-tools would introduce bugs in testing: #997379
    • Build-Depends(-Arch): ripe-atlas-tools ripe-atlas-sagan
    • Depends: ripe-atlas-tools ripe-atlas-sagan
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ripe-atlas-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 1143 days old (needed 5 days)
• automake1.11 (- to 1:1.11.6-6)
  • Migration status for automake1.11 (- to 1:1.11.6-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating automake1.11 would introduce bugs in testing: #1038944
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/automake1.11.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1144 days old (needed 5 days)
• jsjac (- to 1.3.4+dfsg-3)
  • Migration status for jsjac (- to 1.3.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsjac would introduce bugs in testing: #1006027
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsjac.html
    • New but not reproducible on arm64 - info ♻
    • 1144 days old (needed 5 days)
• lua5.1-policy (- to 33+nmu1)
  • Migration status for lua5.1-policy (- to 33+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lua5.1-policy would introduce bugs in testing: #965710
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua5.1-policy.html
    • 1144 days old (needed 5 days)
• php-net-ipv6 (- to 1.3.0b4-1.1)
  • Migration status for php-net-ipv6 (- to 1.3.0b4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-ipv6 would introduce bugs in testing: #1004531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-ipv6.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1144 days old (needed 5 days)
• wiliki (- to 0.6.2-1.1)
  • Migration status for wiliki (- to 0.6.2-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): wiliki gauche (not considered)
    • Depends: wiliki gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wiliki.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1145 days old (needed 5 days)
• android-framework-23 (- to 6.0.1+r72-6)
  • Migration status for android-framework-23 (- to 6.0.1+r72-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-framework-23 would introduce bugs in testing: #1011567
    • Build-Depends(-Arch): android-framework-23 android-platform-build
    • Build-Depends(-Arch): android-framework-23 android-platform-external-doclava
  • 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, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1146 days old (needed 2 days)
• android-platform-build (- to 1:10.0.0+r36-1)
  • Migration status for android-platform-build (- to 1:10.0.0+r36-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-build would introduce bugs in testing: #1042042, #1050437
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-build.html
    • Reproducible on i386 - info ♻
    • 1146 days old (needed 5 days)
• leap-archive-keyring (- to 2017.11.24+nmu1)
  • Migration status for leap-archive-keyring (- to 2017.11.24+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leap-archive-keyring would introduce bugs in testing: #880220
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leap-archive-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1146 days old (needed 5 days)
• monkeysphere (- to 0.43-3.1)
  • Migration status for monkeysphere (- to 0.43-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating monkeysphere would introduce bugs in testing: #1011900
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monkeysphere.html
    • autopkgtest for monkeysphere/0.43-3.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1146 days old (needed 2 days)
• nautilus-scripts-manager (- to 2.0-1.1)
  • Migration status for nautilus-scripts-manager (- to 2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nautilus-scripts-manager would introduce bugs in testing: #1033761
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-scripts-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1146 days old (needed 5 days)
• pafy (- to 0.5.2-2.1)
  • Migration status for pafy (- to 0.5.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pafy would introduce bugs in testing: #1016520
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pafy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1146 days old (needed 5 days)
• pysolfc-cardsets (- to 2.0+dfsg2-2.1)
  • Migration status for pysolfc-cardsets (- to 2.0+dfsg2-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pysolfc-cardsets pysolfc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc-cardsets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1146 days old (needed 5 days)
• resvg (- to 0.8.0-4)
  • Migration status for resvg (- to 0.8.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-resvg-dev/amd64 has unsatisfiable dependency
    • librust-usvg-dev/amd64 has unsatisfiable dependency
    • librust-resvg-dev/arm64 has unsatisfiable dependency
    • librust-usvg-dev/arm64 has unsatisfiable dependency
    • librust-resvg-dev/armhf has unsatisfiable dependency
    • librust-usvg-dev/armhf has unsatisfiable dependency
    • librust-resvg-dev/i386 has unsatisfiable dependency
    • librust-usvg-dev/i386 has unsatisfiable dependency
    • librust-resvg-dev/mips64el has unsatisfiable dependency
    • librust-usvg-dev/mips64el has unsatisfiable dependency
    • librust-resvg-dev/ppc64el has unsatisfiable dependency
    • librust-usvg-dev/ppc64el has unsatisfiable dependency
    • librust-resvg-dev/s390x has unsatisfiable dependency
    • librust-usvg-dev/s390x has unsatisfiable dependency
    • Updating resvg would introduce bugs in testing: #1002188
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-roxmltree-0.7+default-dev
    • Impossible Build-Depends(-Arch): resvg -> patchelf/0.14.3-1+b1/mips64el
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/resvg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1146 days old (needed 5 days)
• w3-dtd-mathml (- to 2.0.0.0-5.1)
  • Migration status for w3-dtd-mathml (- to 2.0.0.0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating w3-dtd-mathml would introduce bugs in testing: #994795
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/w3-dtd-mathml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1146 days old (needed 5 days)
• vlogger (- to 1.3-4.1)
  • Migration status for vlogger (- to 1.3-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vlogger would introduce bugs in testing: #965867
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vlogger.html
    • 1147 days old (needed 5 days)
• libirclib-java (- to 1.10-4)
  • Migration status for libirclib-java (- to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libirclib-java would introduce bugs in testing: #1026625
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libirclib-java.html
    • 1148 days old (needed 5 days)
• zeek-aux (- to 0.45-1)
  • Migration status for zeek-aux (- to 0.45-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zeek-aux would introduce bugs in testing: #985522
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zeek-aux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1149 days old (needed 5 days)
• cecil (- to 0.9.5+dfsg-5.1)
  • Migration status for cecil (- to 0.9.5+dfsg-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cecil would introduce bugs in testing: #1053554
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cecil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1151 days old (needed 5 days)
• asterisk-prompt-de (- to 2.0-1.2)
  • Migration status for asterisk-prompt-de (- to 2.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: asterisk-prompt-de asterisk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-prompt-de.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1154 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:
    • Updating broker would introduce bugs in testing: #1037597
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/broker.html
    • 1154 days old (needed 5 days)
• cycle-quotes (- to 0.1-4)
  • Migration status for cycle-quotes (- to 0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cycle-quotes would introduce bugs in testing: #1020192
    • autopkgtest for cycle-quotes/0.1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cycle-quotes.html
    • 1154 days old (needed 5 days)
• node-node-localstorage (- to 2.1.5-1)
  • Migration status for node-node-localstorage (- to 2.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-node-localstorage would introduce bugs in testing: #1013621
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-localstorage.html
    • autopkgtest for node-node-localstorage/2.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1154 days old (needed 2 days)
• gauche (- to 0.9.10-3)
  • Migration status for gauche (- to 0.9.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gauche would introduce bugs in testing: #1023035
    • Build-Depends(-Arch): gauche slib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1157 days old (needed 5 days)
• pyannotate (- to 1.2.0-2)
  • Migration status for pyannotate (- to 1.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyannotate would introduce bugs in testing: #1058419
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyannotate.html
    • 1157 days old (needed 5 days)
• adabrowse (- to 4.0.3-14)
  • Migration status for adabrowse (- to 4.0.3-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating adabrowse would introduce bugs in testing: #1008980
    • autopkgtest for adabrowse/4.0.3-14: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): adabrowse asis
    • Depends: adabrowse asis
    • Depends: adabrowse gcc-10
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adabrowse.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1160 days old (needed 5 days)
• spyder-reports (- to 0.1.1-4)
  • Migration status for spyder-reports (- to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spyder-reports would introduce bugs in testing: #982647
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/spyder-reports.html
    • autopkgtest for spyder-reports/0.1.1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • 1162 days old (needed 5 days)
• clippoly (- to 0.11-10)
  • Migration status for clippoly (- to 0.11-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clippoly would introduce bugs in testing: #976540
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clippoly.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1165 days old (needed 5 days)
• adacontrol (- to 1.21r6b-7)
  • Migration status for adacontrol (- to 1.21r6b-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • adacontrol/amd64 has unsatisfiable dependency
    • adacontrol/arm64 has unsatisfiable dependency
    • adacontrol/armel has unsatisfiable dependency
    • adacontrol/armhf has unsatisfiable dependency
    • adacontrol/i386 has unsatisfiable dependency
    • adacontrol/mips64el has unsatisfiable dependency
    • adacontrol/ppc64el has unsatisfiable dependency
    • adacontrol/s390x has unsatisfiable dependency
    • Updating adacontrol would introduce bugs in testing: #1008982
    • adacontrol unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • Build-Depends(-Arch): adacontrol asis
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adacontrol.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1166 days old (needed 5 days)
• asis (- to 2019-5)
  • Migration status for asis (- to 2019-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • asis-programs/amd64 has unsatisfiable dependency
    • asis-programs/arm64 has unsatisfiable dependency
    • asis-programs/armel has unsatisfiable dependency
    • asis-programs/armhf has unsatisfiable dependency
    • asis-programs/i386 has unsatisfiable dependency
    • asis-programs/mips64el has unsatisfiable dependency
    • asis-programs/ppc64el has unsatisfiable dependency
    • asis-programs/s390x has unsatisfiable dependency
    • Updating asis would introduce bugs in testing: #1008979
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/asis.html
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlezout8-dev
    • Build-Depends(-Arch): asis gcc-10
    • Depends: asis gcc-10
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1166 days old (needed 5 days)
• libaws (- to 20.2-2)
  • Migration status for libaws (- to 20.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libaws-bin/amd64 has unsatisfiable dependency
    • libaws20-dev/amd64 has unsatisfiable dependency
    • libaws6/amd64 has unsatisfiable dependency
    • libaws-bin/arm64 has unsatisfiable dependency
    • libaws20-dev/arm64 has unsatisfiable dependency
    • libaws6/arm64 has unsatisfiable dependency
    • libaws-bin/armel has unsatisfiable dependency
    • libaws20-dev/armel has unsatisfiable dependency
    • libaws6/armel has unsatisfiable dependency
    • libaws-bin/armhf has unsatisfiable dependency
    • libaws20-dev/armhf has unsatisfiable dependency
    • libaws6/armhf has unsatisfiable dependency
    • libaws-bin/i386 has unsatisfiable dependency
    • libaws20-dev/i386 has unsatisfiable dependency
    • libaws6/i386 has unsatisfiable dependency
    • libaws-bin/mips64el has unsatisfiable dependency
    • libaws20-dev/mips64el has unsatisfiable dependency
    • libaws6/mips64el has unsatisfiable dependency
    • libaws-bin/ppc64el has unsatisfiable dependency
    • libaws20-dev/ppc64el has unsatisfiable dependency
    • libaws6/ppc64el has unsatisfiable dependency
    • libaws-bin/s390x has unsatisfiable dependency
    • libaws20-dev/s390x has unsatisfiable dependency
    • libaws6/s390x has unsatisfiable dependency
    • Updating libaws would introduce bugs in testing: #1008981, #1023114, #997457
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-unicode10-dev (>= 21)
    • Build-Depends(-Arch): libaws asis
    • Build-Depends(-Arch): libaws gcc-10
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/liba/libaws.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1166 days old (needed 5 days)
• libhandy (- to 0.0.13-3)
  • Migration status for libhandy (- to 0.0.13-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libhandy would introduce bugs in testing: #991036
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhandy.html
    • autopkgtest for libhandy/0.0.13-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1168 days old (needed 2 days)
• anki (- to 2.1.15+dfsg-3)
  • Migration status for anki (- to 2.1.15+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating anki would introduce bugs in testing: #1053541, #958853
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/anki.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1171 days old (needed 5 days)
• android-platform-external-libunwind (- to 10.0.0+r36-4)
  • Migration status for android-platform-external-libunwind (- to 10.0.0+r36-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-external-libunwind would introduce bugs in testing: #1060969
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-libunwind.html
    • autopkgtest for android-platform-external-libunwind/10.0.0+r36-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass
    • 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
    • 1172 days old (needed 2 days)
• py-lz4framed (- to 0.14.0-1)
  • Migration status for py-lz4framed (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating py-lz4framed would introduce bugs in testing: #978287
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-lz4framed.html
    • autopkgtest for py-lz4framed/0.14.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1175 days old (needed 5 days)
• leaflet-image (- to 0.4.0~dfsg-3)
  • Migration status for leaflet-image (- to 0.4.0~dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leaflet-image would introduce bugs in testing: #1003260
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leaflet-image.html
    • autopkgtest for leaflet-image/0.4.0~dfsg-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1176 days old (needed 5 days)
• ruby-behance (- to 0.6.1-4)
  • Migration status for ruby-behance (- to 0.6.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-behance would introduce bugs in testing: #1025094
    • autopkgtest for ruby-behance/0.6.1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-behance.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1178 days old (needed 5 days)
• rust-tcmalloc (- to 0.3.0-2)
  • Migration status for rust-tcmalloc (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-tcmalloc would introduce bugs in testing: #981869
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tcmalloc.html
    • autopkgtest for rust-tcmalloc/0.3.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1181 days old (needed 2 days)
• rust-rust-code-analysis (- to 0.0.18-2)
  • Migration status for rust-rust-code-analysis (- to 0.0.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-rust-code-analysis-dev/amd64 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/arm64 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/armel has unsatisfiable dependency
    • librust-rust-code-analysis-dev/armhf has unsatisfiable dependency
    • librust-rust-code-analysis-dev/i386 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/mips64el has unsatisfiable dependency
    • librust-rust-code-analysis-dev/ppc64el has unsatisfiable dependency
    • librust-rust-code-analysis-dev/s390x has unsatisfiable dependency
    • Updating rust-rust-code-analysis would introduce bugs in testing: #1031013
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-tree-sitter-0.17+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-rust-code-analysis.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1183 days old (needed 5 days)
• chibi-scheme (- to 0.9.1-3)
  • Migration status for chibi-scheme (- to 0.9.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chibi-scheme would introduce bugs in testing: #981762
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/chibi-scheme.html
  • Additional info:
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for chibi-scheme/0.9.1-3: amd64: Pass, arm64: Pass, ppc64el: Pass, 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
    • 1184 days old (needed 2 days)
• python-opentracing (- to 2.4.0-1)
  • Migration status for python-opentracing (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-opentracing would introduce bugs in testing: #1026729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-opentracing.html
    • 1186 days old (needed 5 days)
• ibutils (- to 1.5.7+0.2.gbd7e502-3)
  • Migration status for ibutils (- to 1.5.7+0.2.gbd7e502-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ibutils opensm (not considered)
    • Depends: ibutils opensm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1198 days old (needed 5 days)
• qwertone (- to 0.3.0-2)
  • Migration status for qwertone (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qwertone would introduce bugs in testing: #1002148
    • qwertone unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on i386: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qwertone.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1198 days old (needed 5 days)
• libzorpll (- to 7.0.4.0-2)
  • Migration status for libzorpll (- to 7.0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libzorpll-7.0-4/amd64 has unsatisfiable dependency
    • libzorpll-7.0-4/arm64 has unsatisfiable dependency
    • libzorpll-7.0-4/armel has unsatisfiable dependency
    • libzorpll-7.0-4/armhf has unsatisfiable dependency
    • libzorpll-7.0-4/i386 has unsatisfiable dependency
    • libzorpll-7.0-4/mips64el has unsatisfiable dependency
    • libzorpll-7.0-4/ppc64el has unsatisfiable dependency
    • libzorpll-7.0-4/s390x has unsatisfiable dependency
    • Updating libzorpll would introduce bugs in testing: #1006506
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libz/libzorpll.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1214 days old (needed 5 days)
• intel-hdcp (- to 20.3.0-1)
  • Migration status for intel-hdcp (- to 20.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-hdcp would introduce bugs in testing: #1052643
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-hdcp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1216 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 ♻, s390x: Regression or new test ♻
    • Depends: php-horde-mail-autoconfig php-net-dns2
  • 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 ♻
    • 1219 days old (needed 5 days)
• php-horde-mnemo (- to 4.2.14-10)
  • Migration status for php-horde-mnemo (- to 4.2.14-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-mnemo php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mnemo.html
    • autopkgtest for php-horde-mnemo/4.2.14-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1219 days old (needed 2 days)
• php-net-dns2 (- to 1.5.0-1)
  • Migration status for php-net-dns2 (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-dns2 would introduce bugs in testing: #1042457
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-dns2.html
    • autopkgtest for php-net-dns2/1.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1221 days old (needed 2 days)
• rust-mdl (- to 1.0.4-1)
  • Migration status for rust-mdl (- to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-mdl would introduce bugs in testing: #1052952
    • autopkgtest for rust-mdl/1.0.4-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-mdl.html
    • Reproducible on i386 - info ♻
    • 1221 days old (needed 5 days)
• pyqwt3d (- to 0.1.8-6)
  • Migration status for pyqwt3d (- to 0.1.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyqwt3d sip4 (not considered)
    • Depends: pyqwt3d sip4 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyqwt3d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1224 days old (needed 5 days)
• gdis (- to 0.90-6)
  • Migration status for gdis (- to 0.90-6): 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/0.90-6: 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
    • 1228 days old (needed 2 days)
• plm (- to 2.9.2-1)
  • Migration status for plm (- to 2.9.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: plm jruby (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1229 days old (needed 5 days)
• sardana (- to 3.0.3-1)
  • Migration status for sardana (- to 3.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sardana would introduce bugs in testing: #1030905
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/sardana.html
    • Build-Depends-Indep: sardana itango
    • Build-Depends-Indep: sardana pytango
    • Build-Depends-Indep: sardana taurus
    • Depends: sardana itango
    • Depends: sardana pytango
    • Depends: sardana taurus
  • Additional info:
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1233 days old (needed 5 days)
• rust-rspotify (- to 0.7.0-3)
  • Migration status for rust-rspotify (- to 0.7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-rspotify-dev/amd64 has unsatisfiable dependency
    • librust-rspotify-dev/arm64 has unsatisfiable dependency
    • librust-rspotify-dev/armel has unsatisfiable dependency
    • librust-rspotify-dev/armhf has unsatisfiable dependency
    • librust-rspotify-dev/i386 has unsatisfiable dependency
    • librust-rspotify-dev/mips64el has unsatisfiable dependency
    • librust-rspotify-dev/ppc64el has unsatisfiable dependency
    • librust-rspotify-dev/s390x has unsatisfiable dependency
    • Updating rust-rspotify would introduce bugs in testing: #1031072
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-webbrowser-0.5+default-dev
    • Build-Depends(-Arch): rust-rspotify rust-env-logger-0.7
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-rspotify.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1236 days old (needed 5 days)
• xjig (- to 2.4-14.2)
  • Migration status for xjig (- to 2.4-14.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xjig/amd64 has unsatisfiable dependency
    • xjig/arm64 has unsatisfiable dependency
    • xjig/armel has unsatisfiable dependency
    • xjig/armhf has unsatisfiable dependency
    • xjig/i386 has unsatisfiable dependency
    • xjig/mips64el has unsatisfiable dependency
    • xjig/ppc64el has unsatisfiable dependency
    • xjig/s390x has unsatisfiable dependency
    • Updating xjig would introduce bugs in testing: #1014623, #1016403
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/xjig.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1236 days old (needed 5 days)
• php-horde-nag (- to 4.2.19-6)
  • Migration status for php-horde-nag (- to 4.2.19-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-nag would introduce bugs in testing: #1064389
    • Depends: php-horde-nag php-horde
    • Depends: php-horde-nag php-horde-dav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-nag.html
    • autopkgtest for php-horde-nag/4.2.19-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1237 days old (needed 2 days)
• ruby-rails-assets-fine-uploader (- to 5.13.0-2)
  • Migration status for ruby-rails-assets-fine-uploader (- to 5.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-fine-uploader would introduce bugs in testing: #1034027
    • autopkgtest for ruby-rails-assets-fine-uploader/5.13.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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 ♻
    • 1253 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
    • 1266 days old (needed 5 days)
• github-backup (- to 1.20200721-2)
  • Migration status for github-backup (- to 1.20200721-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating github-backup would introduce bugs in testing: #1017298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/github-backup.html
    • 1275 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 ♻, 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 ♻
    • 1277 days old (needed 5 days)
• gnome-video-arcade (- to 0.8.8-5)
  • Migration status for gnome-video-arcade (- to 0.8.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-video-arcade would introduce bugs in testing: #1061694, #1061696
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-video-arcade.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1278 days old (needed 5 days)
• yrmcds (- to 1.1.9-1)
  • Migration status for yrmcds (- to 1.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yrmcds would introduce bugs in testing: #1037907
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yrmcds.html
    • Reproducible on i386 - info ♻
    • 1280 days old (needed 5 days)
• prayer (- to 1.3.5-dfsg1-8)
  • Migration status for prayer (- to 1.3.5-dfsg1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prayer would introduce bugs in testing: #1010066
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prayer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1286 days old (needed 5 days)
• ruby-rails-assets-highlightjs (- to 9.12.0-3)
  • Migration status for ruby-rails-assets-highlightjs (- to 9.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-highlightjs would introduce bugs in testing: #946846
    • autopkgtest for ruby-rails-assets-highlightjs/9.12.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-highlightjs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1287 days old (needed 5 days)
• virtaal (- to 0.7.1+git20191021+ds1-2)
  • Migration status for virtaal (- to 0.7.1+git20191021+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtaal would introduce bugs in testing: #1030008, #1061502
    • autopkgtest for virtaal/0.7.1+git20191021+ds1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • virtaal unsatisfiable Build-Depends(-Arch) on amd64: python3-libproxy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtaal.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1287 days old (needed 5 days)
• fonts-pecita (- to 5.4-2)
  • Migration status for fonts-pecita (- to 5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-pecita would introduce bugs in testing: #975810
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-pecita.html
    • 1288 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tree-style-tab mozilla-devscripts (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tree-style-tab.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1293 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)
    • 1295 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)
    • 1295 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)
    • 1299 days old (needed 5 days)
• opensm (- to 3.3.23-2)
  • Migration status for opensm (- to 3.3.23-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensm would introduce bugs in testing: #1052380
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1302 days old (needed 5 days)
• crazydiskinfo (- to 1.1.0-2)
  • Migration status for crazydiskinfo (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crazydiskinfo would introduce bugs in testing: #997156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crazydiskinfo.html
    • 1309 days old (needed 5 days)
• kwin-effect-xrdesktop (- to 0.15.1-1)
  • Migration status for kwin-effect-xrdesktop (- to 0.15.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kwin-effect-xrdesktop/amd64 has unsatisfiable dependency
    • kwin-effect-xrdesktop/arm64 has unsatisfiable dependency
    • kwin-effect-xrdesktop/armel has unsatisfiable dependency
    • kwin-effect-xrdesktop/armhf has unsatisfiable dependency
    • kwin-effect-xrdesktop/i386 has unsatisfiable dependency
    • kwin-effect-xrdesktop/mips64el has unsatisfiable dependency
    • kwin-effect-xrdesktop/ppc64el has unsatisfiable dependency
    • kwin-effect-xrdesktop/s390x has unsatisfiable dependency
    • Updating kwin-effect-xrdesktop would introduce bugs in testing: #1037382, #993015
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/kwin-effect-xrdesktop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1309 days old (needed 5 days)
• effcee (- to 2019.1-1)
  • Migration status for effcee (- to 2019.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating effcee would introduce bugs in testing: #984048
    • autopkgtest for effcee/2019.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 ♻
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/amd64
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/arm64
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/armel
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/armhf
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/i386
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/mips64el
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/ppc64el
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/effcee.html
    • 1311 days old (needed 5 days)
• bashtop (- to 0.9.25-1)
  • Migration status for bashtop (- to 0.9.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bashtop would introduce bugs in testing: #968381
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bashtop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1312 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 ♻
    • 1315 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 ♻
    • 1316 days old (needed 5 days)
• git-repair (- to 1.20200102-2)
  • Migration status for git-repair (- to 1.20200102-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating git-repair would introduce bugs in testing: #1054816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-repair.html
    • 1317 days old (needed 5 days)
• dune-pdelab (- to 2.7~20200605-2)
  • Migration status for dune-pdelab (- to 2.7~20200605-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libdune-pdelab-dev/amd64 has unsatisfiable dependency
    • libdune-pdelab-dev/arm64 has unsatisfiable dependency
    • libdune-pdelab-dev/armel has unsatisfiable dependency
    • libdune-pdelab-dev/armhf has unsatisfiable dependency
    • libdune-pdelab-dev/i386 has unsatisfiable dependency
    • libdune-pdelab-dev/mips64el has unsatisfiable dependency
    • libdune-pdelab-dev/ppc64el has unsatisfiable dependency
    • libdune-pdelab-dev/s390x has unsatisfiable dependency
    • Updating dune-pdelab would introduce bugs in testing: #1023356, #976499
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/dune-pdelab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1318 days old (needed 5 days)
• openrocket (- to 15.03.6)
  • Migration status for openrocket (- to 15.03.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openrocket would introduce bugs in testing: #984609
    • Depends: openrocket openjdk-8
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1318 days old (needed 5 days)
• php-horde-whups (- to 3.0.12-7)
  • Migration status for php-horde-whups (- to 3.0.12-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-whups php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-whups.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1328 days old (needed 5 days)
• php-horde-gollem (- to 3.0.13-5)
  • Migration status for php-horde-gollem (- to 3.0.13-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-gollem php-horde (not considered)
    • Invalidated by dependency
    • Depends: php-horde-gollem php-horde-editor
  • 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 ♻
    • 1329 days old (needed 5 days)
• php-horde-trean (- to 1.1.10-3)
  • Migration status for php-horde-trean (- to 1.1.10-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-trean php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-trean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1329 days old (needed 5 days)
• php-horde-dav (- to 1.1.4-6)
  • Migration status for php-horde-dav (- to 1.1.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-dav php-sabredav (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-dav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1332 days old (needed 5 days)
• php-horde-editor (- to 2.0.5+debian0-5)
  • Migration status for php-horde-editor (- to 2.0.5+debian0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-editor would introduce bugs in testing: #1042715
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-editor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1332 days old (needed 5 days)
• php-horde-groupware (- to 5.2.22-6)
  • Migration status for php-horde-groupware (- to 5.2.22-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-groupware php-horde (not considered)
    • Invalidated by dependency
    • Depends: php-horde-groupware php-horde-gollem
    • Depends: php-horde-groupware php-horde-kronolith
    • Depends: php-horde-groupware php-horde-mnemo
    • Depends: php-horde-groupware php-horde-nag
    • Depends: php-horde-groupware php-horde-trean
    • Depends: php-horde-groupware php-horde-turba
  • 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 ♻
    • 1332 days old (needed 5 days)
• php-horde-mongo (- to 1.1.0-6)
  • Migration status for php-horde-mongo (- to 1.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mongo would introduce bugs in testing: #820091
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mongo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1332 days old (needed 5 days)
• php-horde-webmail (- to 5.2.22-6)
  • Migration status for php-horde-webmail (- to 5.2.22-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-webmail php-horde (not considered)
    • Invalidated by dependency
    • Depends: php-horde-webmail php-horde-gollem
    • Depends: php-horde-webmail php-horde-imp
    • Depends: php-horde-webmail php-horde-ingo
    • Depends: php-horde-webmail php-horde-kronolith
    • Depends: php-horde-webmail php-horde-mnemo
    • Depends: php-horde-webmail php-horde-nag
    • Depends: php-horde-webmail php-horde-trean
    • Depends: php-horde-webmail php-horde-turba
  • 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 ♻
    • 1332 days old (needed 5 days)
• mkcue (- to 1-7)
  • Migration status for mkcue (- to 1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mkcue would introduce bugs in testing: #984237
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkcue.html
    • 1339 days old (needed 5 days)
• lix (- to 0.9.29-1.1)
  • Migration status for lix (- to 0.9.29-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lix/amd64 has unsatisfiable dependency
    • lix/arm64 has unsatisfiable dependency
    • lix/armhf has unsatisfiable dependency
    • lix/i386 has unsatisfiable dependency
    • Updating lix would introduce bugs in testing: #999750
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lix.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
    • 1351 days old (needed 5 days)
• iptables-converter (- to 0.9.8-1.2)
  • Migration status for iptables-converter (- to 0.9.8-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iptables-converter would introduce bugs in testing: #997602
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iptables-converter.html
    • 1354 days old (needed 5 days)
• breezy-loom (- to 3.0.0+bzr167-1)
  • Migration status for breezy-loom (- to 3.0.0+bzr167-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating breezy-loom would introduce bugs in testing: #988156
    • autopkgtest for breezy-loom/3.0.0+bzr167-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breezy-loom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1363 days old (needed 5 days)
• octave-mpi (- to 3.1.0-1)
  • Migration status for octave-mpi (- to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • octave-mpi/amd64 has unsatisfiable dependency
    • octave-mpi/arm64 has unsatisfiable dependency
    • octave-mpi/armel has unsatisfiable dependency
    • octave-mpi/armhf has unsatisfiable dependency
    • octave-mpi/i386 has unsatisfiable dependency
    • octave-mpi/mips64el has unsatisfiable dependency
    • octave-mpi/ppc64el has unsatisfiable dependency
    • octave-mpi/s390x has unsatisfiable dependency
    • Updating octave-mpi would introduce bugs in testing: #1009133
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/octave-mpi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch 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
    • 1365 days old (needed 5 days)
• astropy-helpers (- to 4.0.1-1)
  • Migration status for astropy-helpers (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating astropy-helpers would introduce bugs in testing: #1058104
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astropy-helpers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1372 days old (needed 5 days)
• fakeroot-ng (- to 0.18-4.1)
  • Migration status for fakeroot-ng (- to 0.18-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fakeroot-ng would introduce bugs in testing: #1016266
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fakeroot-ng.html
    • 1373 days old (needed 5 days)
• telegram-purple (- to 1.4.3-3)
  • Migration status for telegram-purple (- to 1.4.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telegram-purple would introduce bugs in testing: #1011846, #1040074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-purple.html
    • 1376 days old (needed 5 days)
• android-platform-tools-analytics-library (- to 2.2.2-3)
  • Migration status for android-platform-tools-analytics-library (- to 2.2.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): android-platform-tools-analytics-library android-platform-tools-base (not considered)
    • Depends: android-platform-tools-analytics-library android-platform-tools-base (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-tools-analytics-library.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1378 days old (needed 5 days)
• android-sdk-helper (- to 0.2)
  • Migration status for android-sdk-helper (- to 0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: android-sdk-helper android-platform-tools-base (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-sdk-helper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1379 days old (needed 5 days)
• binutils64 (- to 1+c3)
  • Migration status for binutils64 (- to 1+c3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils64 would introduce bugs in testing: #987525, #987526
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1380 days old (needed 5 days)
• cpufrequtils (- to 008-2)
  • Migration status for cpufrequtils (- to 008-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpufrequtils would introduce bugs in testing: #877016
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpufrequtils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1389 days old (needed 5 days)
• sipxtapi (- to 3.3.0~test18+dfsg.1-0.1)
  • Migration status for sipxtapi (- to 3.3.0~test18+dfsg.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsipxtapi/amd64 has unsatisfiable dependency
    • libsipxtapi/arm64 has unsatisfiable dependency
    • libsipxtapi/armel has unsatisfiable dependency
    • libsipxtapi/armhf has unsatisfiable dependency
    • libsipxtapi/i386 has unsatisfiable dependency
    • libsipxtapi/mips64el has unsatisfiable dependency
    • libsipxtapi/ppc64el has unsatisfiable dependency
    • libsipxtapi/s390x has unsatisfiable dependency
    • Updating sipxtapi would introduce bugs in testing: #1058941, #984331, #986494, #999960
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sipxtapi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1391 days old (needed 5 days)
• ruby-jekyll-asciidoc (- to 3.0.0-2)
  • Migration status for ruby-jekyll-asciidoc (- to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-asciidoc would introduce bugs in testing: #1030465
    • autopkgtest for ruby-jekyll-asciidoc/3.0.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-asciidoc.html
    • 1401 days old (needed 5 days)
• rust-librespot-protocol (- to 0.1.0-2)
  • Migration status for rust-librespot-protocol (- to 0.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-librespot-protocol would introduce bugs in testing: #1002238
    • autopkgtest for rust-librespot-protocol/0.1.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-librespot-protocol.html
    • 1402 days old (needed 5 days)
• graphite-api (- to 1.1.3-6)
  • Migration status for graphite-api (- to 1.1.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graphite-api would introduce bugs in testing: #1026609
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graphite-api.html
    • 1403 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)
    • 1412 days old (needed 5 days)
• libkqueue (- to 2.3.1-1)
  • Migration status for libkqueue (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libkqueue/2.3.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻
    • 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/libk/libkqueue.html
    • Reproducible on arm64 - info ♻
    • 1412 days old (needed 5 days)
• ruby-thinking-sphinx (- to 4.1.0-3)
  • Migration status for ruby-thinking-sphinx (- to 4.1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-thinking-sphinx ruby-riddle (not considered)
    • Depends: ruby-thinking-sphinx ruby-riddle (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-thinking-sphinx.html
    • autopkgtest for ruby-thinking-sphinx/4.1.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1412 days old (needed 5 days)
• sdaps (- to 1.9.8-0.1)
  • Migration status for sdaps (- to 1.9.8-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sdaps would introduce bugs in testing: #1001643, #1061159
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdaps.html
    • autopkgtest for sdaps/1.9.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 ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 1412 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
    • 1415 days old (needed 5 days)
• gcc-python-plugin (- to 0.17-6)
  • Migration status for gcc-python-plugin (- to 0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gcc-python3-dbg-plugin/amd64 has unsatisfiable dependency
    • gcc-python3-dbg-plugin/arm64 has unsatisfiable dependency
    • gcc-python3-dbg-plugin/armel has unsatisfiable dependency
    • gcc-python3-dbg-plugin/armhf has unsatisfiable dependency
    • gcc-python3-dbg-plugin/i386 has unsatisfiable dependency
    • gcc-python3-dbg-plugin/mips64el has unsatisfiable dependency
    • gcc-python3-dbg-plugin/ppc64el has unsatisfiable dependency
    • gcc-python3-dbg-plugin/s390x has unsatisfiable dependency
    • Updating gcc-python-plugin would introduce bugs in testing: #1000213, #963999, #978511
    • Build-Depends(-Arch): gcc-python-plugin gcc-10
    • Build-Depends(-Arch): gcc-python-plugin gcc-9
    • Depends: gcc-python-plugin gcc-9
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gcc-python-plugin.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1418 days old (needed 5 days)
• openexr-viewers (- to 2.3.0-1)
  • Migration status for openexr-viewers (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openexr-viewers/amd64 has unsatisfiable dependency
    • openexr-viewers/arm64 has unsatisfiable dependency
    • openexr-viewers/armel has unsatisfiable dependency
    • openexr-viewers/armhf has unsatisfiable dependency
    • openexr-viewers/i386 has unsatisfiable dependency
    • openexr-viewers/mips64el has unsatisfiable dependency
    • openexr-viewers/ppc64el has unsatisfiable dependency
    • openexr-viewers/s390x has unsatisfiable dependency
    • Updating openexr-viewers would introduce bugs in testing: #1017547
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openexr-viewers.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1419 days old (needed 5 days)
• airport-utils (- to 2-8)
  • Migration status for airport-utils (- to 2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating airport-utils would introduce bugs in testing: #414092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/airport-utils.html
    • autopkgtest for airport-utils/2-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1425 days old (needed 2 days)
• gcc-9-cross-mipsen (- to 4+c2)
  • Migration status for gcc-9-cross-mipsen (- to 4+c2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cpp-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • Updating gcc-9-cross-mipsen would introduce bugs in testing: #946352, #963998
    • Build-Depends(-Arch): gcc-9-cross-mipsen autoconf2.64
    • Build-Depends(-Arch): gcc-9-cross-mipsen gcc-9
    • Built-Using: gcc-9-cross-mipsen gcc-9
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gcc-9-cross-mipsen.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 1429 days old (needed 5 days)
• umatrix (- to 1.4.0+dfsg-1)
  • Migration status for umatrix (- to 1.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umatrix would introduce bugs in testing: #976697, #991344
    • Build-Depends(-Arch): umatrix mozilla-devscripts
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umatrix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1433 days old (needed 5 days)
• libneo4j-client (- to 2.2.0-1.1)
  • Migration status for libneo4j-client (- to 2.2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libneo4j-client11/amd64 has unsatisfiable dependency
    • libneo4j-client11/arm64 has unsatisfiable dependency
    • libneo4j-client11/armel has unsatisfiable dependency
    • libneo4j-client11/armhf has unsatisfiable dependency
    • libneo4j-client11/i386 has unsatisfiable dependency
    • libneo4j-client11/mips64el has unsatisfiable dependency
    • libneo4j-client11/ppc64el has unsatisfiable dependency
    • libneo4j-client11/s390x has unsatisfiable dependency
    • Updating libneo4j-client would introduce bugs in testing: #984187
    • Build-Depends(-Arch): libneo4j-client libcypher-parser
    • Depends: libneo4j-client libcypher-parser
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libn/libneo4j-client.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1441 days old (needed 5 days)
• mahimahi (- to 0.98-1.1)
  • Migration status for mahimahi (- to 0.98-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mahimahi/amd64 has unsatisfiable dependency
    • mahimahi/arm64 has unsatisfiable dependency
    • mahimahi/armel has unsatisfiable dependency
    • mahimahi/armhf has unsatisfiable dependency
    • mahimahi/i386 has unsatisfiable dependency
    • mahimahi/mips64el has unsatisfiable dependency
    • mahimahi/ppc64el has unsatisfiable dependency
    • mahimahi/s390x has unsatisfiable dependency
    • Updating mahimahi would introduce bugs in testing: #977684, #984228
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mahimahi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1446 days old (needed 5 days)
• aboot (- to 1.0~pre20200212-1)
  • Migration status for aboot (- to 1.0~pre20200212-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aboot-cross/amd64 has unsatisfiable dependency
    • aboot-cross/arm64 has unsatisfiable dependency
    • aboot-cross/armel has unsatisfiable dependency
    • aboot-cross/armhf has unsatisfiable dependency
    • aboot-cross/i386 has unsatisfiable dependency
    • aboot-cross/mips64el has unsatisfiable dependency
    • aboot-cross/ppc64el has unsatisfiable dependency
    • aboot-cross/s390x has unsatisfiable dependency
    • Updating aboot would introduce bugs in testing: #805988
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/aboot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1448 days old (needed 5 days)
• ruby-jekyll-mentions (- to 1.6.0-1)
  • Migration status for ruby-jekyll-mentions (- to 1.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-mentions ruby-html-pipeline (not considered)
    • Depends: ruby-jekyll-mentions ruby-html-pipeline (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-mentions.html
    • autopkgtest for ruby-jekyll-mentions/1.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1449 days old (needed 2 days)
• win-iconv (- to 0.0.8-4)
  • Migration status for win-iconv (- to 0.0.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating win-iconv would introduce bugs in testing: #921904
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/win-iconv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1449 days old (needed 5 days)
• ruby-rubydns (- to 1.0.3-3)
  • Migration status for ruby-rubydns (- to 1.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rubydns would introduce bugs in testing: #1031468
    • autopkgtest for ruby-rubydns/1.0.3-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-rubydns ruby-celluloid-io
    • Depends: ruby-rubydns ruby-celluloid-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-rubydns.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1456 days old (needed 5 days)
• gnat-gps (- to 19.2-3)
  • Migration status for gnat-gps (- to 19.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnat-gps/amd64 has unsatisfiable dependency
    • gnat-gps/arm64 has unsatisfiable dependency
    • gnat-gps/mips64el has unsatisfiable dependency
    • gnat-gps/ppc64el has unsatisfiable dependency
    • gnat-gps/s390x has unsatisfiable dependency
    • Updating gnat-gps would introduce bugs in testing: #936624, #979146
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-unicode9-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnat-gps.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1458 days old (needed 5 days)
• sassphp (- to 0.7-1)
  • Migration status for sassphp (- to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-sass/amd64 has unsatisfiable dependency
    • php-sass/arm64 has unsatisfiable dependency
    • php-sass/armel has unsatisfiable dependency
    • php-sass/armhf has unsatisfiable dependency
    • php-sass/i386 has unsatisfiable dependency
    • php-sass/mips64el has unsatisfiable dependency
    • php-sass/ppc64el has unsatisfiable dependency
    • php-sass/s390x has unsatisfiable dependency
    • Updating sassphp would introduce bugs in testing: #1035552
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sassphp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1458 days old (needed 5 days)
• mod-gnutls (- to 0.9.0-1.1)
  • Migration status for mod-gnutls (- to 0.9.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mod-gnutls would introduce bugs in testing: #1050670, #942737
    • Build-Depends(-Arch): mod-gnutls monkeysphere
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mod-gnutls.html
    • Reproducible on i386 - info ♻
    • 1460 days old (needed 5 days)
• pysolfc (- to 2.6.4-3)
  • Migration status for pysolfc (- to 2.6.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pysolfc would introduce bugs in testing: #1008708
    • autopkgtest for pysolfc/2.6.4-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc.html
    • 1464 days old (needed 5 days)
• ruby-google-cloud-translate (- to 1.3.0-2)
  • Migration status for ruby-google-cloud-translate (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-google-cloud-translate/amd64 has unsatisfiable dependency
    • ruby-google-cloud-translate/arm64 has unsatisfiable dependency
    • Updating ruby-google-cloud-translate would introduce bugs in testing: #964607
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-google-cloud-translate.html
    • ruby-google-cloud-translate unsatisfiable Build-Depends(-Arch) on amd64: ruby-googleauth (<< 0.10.0)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1474 days old (needed 5 days)
• kcov (- to 38+dfsg-1)
  • Migration status for kcov (- to 38+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kcov would introduce bugs in testing: #964654
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcov.html
    • 1475 days old (needed 5 days)
• fonts-rit-sundar (- to 2.0.0+20170909-2)
  • Migration status for fonts-rit-sundar (- to 2.0.0+20170909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-rit-sundar would introduce bugs in testing: #1033698
    • autopkgtest for fonts-rit-sundar/2.0.0+20170909-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-rit-sundar.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1482 days old (needed 5 days)
• vagrant-bindfs (- to 1.1.6-1)
  • Migration status for vagrant-bindfs (- to 1.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vagrant-bindfs would introduce bugs in testing: #953226
    • autopkgtest for vagrant-bindfs/1.1.6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-bindfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1482 days old (needed 5 days)
• seriousproton (- to 2020.01.15+dfsg-1)
  • Migration status for seriousproton (- to 2020.01.15+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating seriousproton would introduce bugs in testing: #1057114, #997264
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/s390x
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/s390x
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/s390x
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/s390x
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/seriousproton.html
    • 1484 days old (needed 5 days)
• ghemical (- to 3.0.0-5)
  • Migration status for ghemical (- to 3.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ghemical libglade2 (not considered)
    • Depends: ghemical libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ghemical gtkglext
    • Depends: ghemical gtkglext
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghemical.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1492 days old (needed 5 days)
• dafny (- to 2.3.0+dfsg-0.1)
  • Migration status for dafny (- to 2.3.0+dfsg-0.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): dafny boogie (not considered)
    • Depends: dafny boogie (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dafny.html
    • autopkgtest for dafny/2.3.0+dfsg-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1495 days old (needed 2 days)
• dltlyse (- to 1.1-1.1)
  • Migration status for dltlyse (- to 1.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dltlyse would introduce bugs in testing: #966926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dltlyse.html
    • 1497 days old (needed 5 days)
• hilive (- to 2.0a-3)
  • Migration status for hilive (- to 2.0a-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hilive would introduce bugs in testing: #1053499
    • autopkgtest for hilive/2.0a-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: 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 ♻
    • 1499 days old (needed 5 days)
• watson (- to 1.8.0-0.1)
  • Migration status for watson (- to 1.8.0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating watson would introduce bugs in testing: #997487
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watson.html
    • autopkgtest for watson/1.8.0-0.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1508 days old (needed 5 days)
• pyhoca-gui (- to 0.6.1.1-1)
  • Migration status for pyhoca-gui (- to 0.6.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyhoca-gui would introduce bugs in testing: #1054832
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyhoca-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1513 days old (needed 5 days)
• boogie (- to 2.4.1+dfsg-0.1)
  • Migration status for boogie (- to 2.4.1+dfsg-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating boogie would introduce bugs in testing: #1052886
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boogie.html
    • autopkgtest for boogie/2.4.1+dfsg-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1518 days old (needed 2 days)
• dirspec (- to 13.10-1.1)
  • Migration status for dirspec (- to 13.10-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dirspec would introduce bugs in testing: #949937
    • dirspec unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dirspec.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 1523 days old (needed 5 days)
• python-efilter (- to 1.5-2.1)
  • Migration status for python-efilter (- to 1.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-efilter would introduce bugs in testing: #1042316
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-efilter.html
    • Reproducible on i386 - info ♻
    • 1523 days old (needed 5 days)
• opensta (- to 0~20191111gitc018cb2+dfsg-1)
  • Migration status for opensta (- to 0~20191111gitc018cb2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensta would introduce bugs in testing: #1037806
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensta.html
    • Reproducible on i386 - info ♻
    • 1524 days old (needed 5 days)
• pdfrw (- to 0.4-2.1)
  • Migration status for pdfrw (- to 0.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdfrw would introduce bugs in testing: #958362
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfrw.html
    • autopkgtest for pdfrw/0.4-2.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1525 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, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1526 days old (needed 2 days)
• python-ospurge (- to 2.0.0+2019.10.11.git.990287677b-2)
  • Migration status for python-ospurge (- to 2.0.0+2019.10.11.git.990287677b-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ospurge would introduce bugs in testing: #1022392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ospurge.html
    • 1528 days old (needed 5 days)
• simulavr (- to 1.0.0+git20160221.e53413b-2)
  • Migration status for simulavr (- to 1.0.0+git20160221.e53413b-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simulavr would introduce bugs in testing: #975138
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simulavr.html
    • 1528 days old (needed 5 days)
• check-all-the-things (- to 2017.05.20+nmu1)
  • Migration status for check-all-the-things (- to 2017.05.20+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating check-all-the-things would introduce bugs in testing: #862378
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-all-the-things.html
    • 1531 days old (needed 5 days)
• golang-github-ulule-limiter (- to 3.3.3-1)
  • Migration status for golang-github-ulule-limiter (- to 3.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Depends: golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ulule-limiter.html
    • autopkgtest for golang-github-ulule-limiter/3.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1544 days old (needed 2 days)
• thawab (- to 4.1-2)
  • Migration status for thawab (- to 4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating thawab would introduce bugs in testing: #990746
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1558 days old (needed 5 days)
• golang-github-getlantern-errors (- to 0.0~git20190325.abdb3e3-2)
  • Migration status for golang-github-getlantern-errors (- to 0.0~git20190325.abdb3e3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-getlantern-errors/0.0~git20190325.abdb3e3-2: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-getlantern-errors golang-github-getlantern-ops
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-errors.html
    • Reproducible on amd64 - info ♻
    • 1562 days old (needed 5 days)
• ruby-coffee-script (- to 2.4.1-2)
  • Migration status for ruby-coffee-script (- to 2.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-coffee-script would introduce bugs in testing: #1019927
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-coffee-script.html
    • autopkgtest for ruby-coffee-script/2.4.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1565 days old (needed 5 days)
• gr-dab (- to 0.4-2)
  • Migration status for gr-dab (- to 0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gr-dab/amd64 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/amd64 has unsatisfiable dependency
    • gr-dab/arm64 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/arm64 has unsatisfiable dependency
    • gr-dab/armel has unsatisfiable dependency
    • libgnuradio-dab3.8.0/armel has unsatisfiable dependency
    • gr-dab/armhf has unsatisfiable dependency
    • libgnuradio-dab3.8.0/armhf has unsatisfiable dependency
    • gr-dab/i386 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/i386 has unsatisfiable dependency
    • gr-dab/mips64el has unsatisfiable dependency
    • libgnuradio-dab3.8.0/mips64el has unsatisfiable dependency
    • gr-dab/ppc64el has unsatisfiable dependency
    • libgnuradio-dab3.8.0/ppc64el has unsatisfiable dependency
    • gr-dab/s390x has unsatisfiable dependency
    • libgnuradio-dab3.8.0/s390x has unsatisfiable dependency
    • Updating gr-dab would introduce bugs in testing: #1002106, #1031346
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gr-dab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1568 days old (needed 5 days)
• jsunit (- to 0.2.2-2)
  • Migration status for jsunit (- to 0.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsunit would introduce bugs in testing: #974083
    • autopkgtest for jsunit/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsunit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1570 days old (needed 5 days)
• termtris (- to 1.3-1)
  • Migration status for termtris (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating termtris would introduce bugs in testing: #966877
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termtris.html
    • 1575 days old (needed 5 days)
• backup2swift (- to 0.8-1.1)
  • Migration status for backup2swift (- to 0.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backup2swift would introduce bugs in testing: #949942
    • backup2swift unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backup2swift.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1579 days old (needed 5 days)
• gandi-cli (- to 1.5-1)
  • Migration status for gandi-cli (- to 1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gandi-cli would introduce bugs in testing: #922420
    • autopkgtest for gandi-cli/1.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gandi-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1579 days old (needed 5 days)
• aufs (- to 5.2+20190909-1.1)
  • Migration status for aufs (- to 5.2+20190909-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aufs would introduce bugs in testing: #948087
    • aufs unsatisfiable Build-Depends(-Arch) on amd64: linux-kbuild-5.2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aufs.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 ♻
    • 1584 days old (needed 5 days)
• irsim (- to 9.7.104-1)
  • Migration status for irsim (- to 9.7.104-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating irsim would introduce bugs in testing: #997299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/irsim.html
    • 1587 days old (needed 5 days)
• myhdl (- to 0.11-1)
  • Migration status for myhdl (- to 0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating myhdl would introduce bugs in testing: #991212
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/myhdl.html
    • autopkgtest for myhdl/0.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1588 days old (needed 2 days)
• beanbag (- to 1.9.2-1.2)
  • Migration status for beanbag (- to 1.9.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating beanbag would introduce bugs in testing: #977056
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beanbag.html
    • 1589 days old (needed 5 days)
• itango (- to 0.1.7-2)
  • Migration status for itango (- to 0.1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating itango would introduce bugs in testing: #1058165
    • Build-Depends(-Arch): itango pytango
    • Depends: itango pytango
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/itango.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1591 days old (needed 5 days)
• frozen-flask (- to 0.11-3.1)
  • Migration status for frozen-flask (- to 0.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating frozen-flask would introduce bugs in testing: #1009968, #997354
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frozen-flask.html
    • 1593 days old (needed 5 days)
• python-ck (- to 1.9.4-1.1)
  • Migration status for python-ck (- to 1.9.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ck would introduce bugs in testing: #1058260
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ck.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 1594 days old (needed 5 days)
• python-lepl (- to 5.1.3-2.1)
  • Migration status for python-lepl (- to 5.1.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-lepl would introduce bugs in testing: #950059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lepl.html
    • 1594 days old (needed 5 days)
• socket-activate (- to 0.1-2)
  • Migration status for socket-activate (- to 0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating socket-activate would introduce bugs in testing: #922504
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socket-activate.html
    • 1602 days old (needed 5 days)
• haskell98-tutorial (- to 200006-2-3)
  • Migration status for haskell98-tutorial (- to 200006-2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell98-tutorial would introduce bugs in testing: #965577
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell98-tutorial.html
    • 1605 days old (needed 5 days)
• python-pyramid-tm (- to 0.5-1.2)
  • Migration status for python-pyramid-tm (- to 0.5-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-pyramid-tm python-pyramid (not considered)
    • Depends: python-pyramid-tm python-pyramid (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-tm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1610 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
    • Build-Depends(-Arch): python-pyramid-zcml python-pyramid
    • Depends: python-pyramid-zcml python-pyramid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-zcml.html
    • 1610 days old (needed 5 days)
• python-pyramid-multiauth (- to 0.8.0-1.1)
  • Migration status for python-pyramid-multiauth (- to 0.8.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyramid-multiauth would introduce bugs in testing: #997297
    • Build-Depends(-Arch): python-pyramid-multiauth python-pyramid
    • Depends: python-pyramid-multiauth python-pyramid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-multiauth.html
    • 1613 days old (needed 5 days)
• python-ooolib (- to 0.0.22-5)
  • Migration status for python-ooolib (- to 0.0.22-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ooolib would introduce bugs in testing: #965794
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ooolib.html
    • 1621 days old (needed 5 days)
• drmips (- to 2.0.1-2.1)
  • Migration status for drmips (- to 2.0.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating drmips would introduce bugs in testing: #971184
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drmips.html
    • 1625 days old (needed 5 days)
• gigedit (- to 1.1.1-1)
  • Migration status for gigedit (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gigedit/amd64 has unsatisfiable dependency
    • gigedit/arm64 has unsatisfiable dependency
    • gigedit/armel has unsatisfiable dependency
    • gigedit/armhf has unsatisfiable dependency
    • gigedit/i386 has unsatisfiable dependency
    • gigedit/mips64el has unsatisfiable dependency
    • gigedit/ppc64el has unsatisfiable dependency
    • gigedit/s390x has unsatisfiable dependency
    • Updating gigedit would introduce bugs in testing: #997203
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gigedit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1625 days old (needed 5 days)
• crypto-policies (- to 20190816git-1)
  • Migration status for crypto-policies (- to 20190816git-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crypto-policies.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1626 days old (needed 5 days)
• ruby-jekyll-gist (- to 1.5.0-2)
  • Migration status for ruby-jekyll-gist (- to 1.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-gist would introduce bugs in testing: #1059707
    • autopkgtest for ruby-jekyll-gist/1.5.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-gist.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1626 days old (needed 5 days)
• umlet (- to 13.3-1.3)
  • Migration status for umlet (- to 13.3-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umlet would introduce bugs in testing: #965851
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umlet.html
    • 1627 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
    • 1628 days old (needed 5 days)
• python-arrayfire (- to 3.3.20160624-3)
  • Migration status for python-arrayfire (- to 3.3.20160624-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-arrayfire arrayfire (not considered)
    • Depends: python-arrayfire arrayfire (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-arrayfire.html
    • autopkgtest for python-arrayfire/3.3.20160624-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1631 days old (needed 2 days)
• svn-load (- to 1.6-1)
  • Migration status for svn-load (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating svn-load would introduce bugs in testing: #1033526
    • autopkgtest for svn-load/1.6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/svn-load.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1634 days old (needed 5 days)
• golang-github-jesseduffield-gocui (- to 0.3.0+git20190803.ad0cd60-1)
  • Migration status for golang-github-jesseduffield-gocui (- to 0.3.0+git20190803.ad0cd60-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-gocui would introduce bugs in testing: #1032109
    • Build-Depends(-Arch): golang-github-jesseduffield-gocui golang-github-jesseduffield-termbox-go
    • Depends: golang-github-jesseduffield-gocui golang-github-jesseduffield-termbox-go
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-gocui.html
    • autopkgtest for golang-github-jesseduffield-gocui/0.3.0+git20190803.ad0cd60-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1637 days old (needed 2 days)
• hydroffice.bag (- to 0.2.15-3)
  • Migration status for hydroffice.bag (- to 0.2.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hydroffice.bag would introduce bugs in testing: #993003
    • autopkgtest for hydroffice.bag/0.2.15-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hydroffice.bag.html
    • 1641 days old (needed 5 days)
• esniper (- to 2.35.0+git20190805.7930bb4-1)
  • Migration status for esniper (- to 2.35.0+git20190805.7930bb4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating esniper would introduce bugs in testing: #855461
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esniper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1649 days old (needed 5 days)
• simple-obfs (- to 0.0.5-6)
  • Migration status for simple-obfs (- to 0.0.5-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simple-obfs shadowsocks-libev (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simple-obfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1651 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gertty.html
    • autopkgtest for gertty/1.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1655 days old (needed 2 days)
• python-netfilter (- to 0.6.4-2)
  • Migration status for python-netfilter (- to 0.6.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-netfilter would introduce bugs in testing: #1058211
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-netfilter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 1657 days old (needed 5 days)
• rust-pbr (- to 1.0.1-1)
  • Migration status for rust-pbr (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-pbr would introduce bugs in testing: #1053638
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pbr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1659 days old (needed 5 days)
• squirrel3 (- to 3.1-8)
  • Migration status for squirrel3 (- to 3.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squirrel3 would introduce bugs in testing: #1014539, #997441
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squirrel3.html
    • 1667 days old (needed 5 days)
• profitbricks-sdk-python (- to 4.1.3-3)
  • Migration status for profitbricks-sdk-python (- to 4.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating profitbricks-sdk-python would introduce bugs in testing: #1020092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/profitbricks-sdk-python.html
    • 1676 days old (needed 5 days)
• versiontools (- to 1.9.1-4)
  • Migration status for versiontools (- to 1.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating versiontools would introduce bugs in testing: #1054736, #1056537
    • autopkgtest for versiontools/1.9.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/versiontools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1676 days old (needed 5 days)
• nbibtex (- to 0.9.18-13)
  • Migration status for nbibtex (- to 0.9.18-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nbibtex would introduce bugs in testing: #1030454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbibtex.html
    • 1679 days old (needed 5 days)
• hipspy (- to 0.2-3)
  • Migration status for hipspy (- to 0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hipspy would introduce bugs in testing: #1012277
    • autopkgtest for hipspy/0.2-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): hipspy astropy-helpers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hipspy.html
    • 1682 days old (needed 5 days)
• opencollada (- to 0.1.0~20180719.619d942+dfsg0-2)
  • Migration status for opencollada (- to 0.1.0~20180719.619d942+dfsg0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opencollada would introduce bugs in testing: #1000009, #1037799
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencollada.html
    • Reproducible on i386 - info ♻
    • 1691 days old (needed 5 days)
• pluginhook (- to 0~20150216.0~a320158-2.1)
  • Migration status for pluginhook (- to 0~20150216.0~a320158-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pluginhook would introduce bugs in testing: #972915
    • pluginhook/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • pluginhook/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pluginhook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1701 days old (needed 5 days)
• averell (- to 1.2.5-1.1)
  • Migration status for averell (- to 1.2.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): averell erlang-cowboy (not considered)
    • Depends: averell erlang-cowboy (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/averell.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 1737 days old (needed 5 days)
• libapache2-mod-defensible (- to 1.4-3.2)
  • Migration status for libapache2-mod-defensible (- to 1.4-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-defensible would introduce bugs in testing: #965622, #998981
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-defensible.html
    • 1738 days old (needed 5 days)
• megadown (- to 0~20180705+git83c53dd-1.1)
  • Migration status for megadown (- to 0~20180705+git83c53dd-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating megadown would introduce bugs in testing: #1007941, #969885
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/megadown.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1746 days old (needed 5 days)
• golang-github-getlantern-ops (- to 0.0~git20190325.d70cb0d-1)
  • Migration status for golang-github-getlantern-ops (- to 0.0~git20190325.d70cb0d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by micah, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-ops.html
    • autopkgtest for golang-github-getlantern-ops/0.0~git20190325.d70cb0d-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1773 days old (needed 2 days)
• ricochet-im (- to 1.1.4-3)
  • Migration status for ricochet-im (- to 1.1.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ricochet-im would introduce bugs in testing: #992668
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ricochet-im.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1796 days old (needed 5 days)
• x2godesktopsharing (- to 3.2.0.0-2)
  • Migration status for x2godesktopsharing (- to 3.2.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: x2godesktopsharing x2goserver (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2godesktopsharing.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1799 days old (needed 5 days)
• pyfr (- to 1.5.0-3)
  • Migration status for pyfr (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfr would introduce bugs in testing: #997427
    • autopkgtest for pyfr/1.5.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfr.html
    • 1815 days old (needed 5 days)
• aufs-tools (- to 1:4.14+20190211-1)
  • Migration status for aufs-tools (- to 1:4.14+20190211-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aufs-tools would introduce bugs in testing: #943332
    • Build-Depends(-Arch): aufs-tools aufs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aufs-tools.html
    • 1822 days old (needed 5 days)
• libapache2-mod-auth-cas (- to 1.2-1)
  • Migration status for libapache2-mod-auth-cas (- to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-auth-cas would introduce bugs in testing: #1000068
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-auth-cas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1833 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:
    • Updating whitedune would introduce bugs in testing: #1036881
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whitedune.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1836 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
    • 1838 days old (needed 5 days)
• diaspora (- to 0.7.9.0+dfsg-4)
  • Migration status for diaspora (- to 0.7.9.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • diaspora/amd64 has unsatisfiable dependency
    • diaspora/arm64 has unsatisfiable dependency
    • Updating diaspora would introduce bugs in testing: #924109, #974014
    • Not built on buildd: arch all binaries uploaded by praveen, 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/d/diaspora.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 1840 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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-trust-webcrypto.html
    • 1842 days old (needed 5 days)
• sqwebmail-de (- to 6.0.0-1)
  • Migration status for sqwebmail-de (- to 6.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sqwebmail-de courier (not considered)
    • Built-Using: sqwebmail-de courier (not considered)
    • Depends: sqwebmail-de courier (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqwebmail-de.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1852 days old (needed 5 days)
• fonts-alegreya-sans (- to 2.008-1)
  • Migration status for fonts-alegreya-sans (- to 2.008-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-alegreya-sans would introduce bugs in testing: #944499
    • Not built on buildd: arch all binaries uploaded by jeremy@bicha.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-alegreya-sans.html
    • 1861 days old (needed 5 days)
• yorick-full (- to 2.2.04+dfsg1+full)
  • Migration status for yorick-full (- to 2.2.04+dfsg1+full): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: yorick-full yorick-ynfft (not considered)
    • Invalidated by dependency
    • Depends: yorick-full yorick-mira
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-full.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1862 days old (needed 5 days)
• minify-maven-plugin (- to 1.7.4-1.1)
  • Migration status for minify-maven-plugin (- to 1.7.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating minify-maven-plugin would introduce bugs in testing: #1006451
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minify-maven-plugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1866 days old (needed 5 days)
• gozer (- to 0.7.nofont.1-7)
  • Migration status for gozer (- to 0.7.nofont.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gozer giblib (not considered)
    • Depends: gozer giblib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gozer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1867 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)
    • 1867 days old (needed 5 days)
• vibe.d (- to 0.8.4-2)
  • Migration status for vibe.d (- to 0.8.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libvibe-core0/amd64 has unsatisfiable dependency
    • libvibe-crypto0/amd64 has unsatisfiable dependency
    • libvibe-data0/amd64 has unsatisfiable dependency
    • libvibe-http0/amd64 has unsatisfiable dependency
    • libvibe-inet0/amd64 has unsatisfiable dependency
    • libvibe-mail0/amd64 has unsatisfiable dependency
    • libvibe-mongodb0/amd64 has unsatisfiable dependency
    • libvibe-redis0/amd64 has unsatisfiable dependency
    • libvibe-stream0/amd64 has unsatisfiable dependency
    • libvibe-textfilter0/amd64 has unsatisfiable dependency
    • libvibe-tls0/amd64 has unsatisfiable dependency
    • libvibe-utils0/amd64 has unsatisfiable dependency
    • libvibe-web0/amd64 has unsatisfiable dependency
    • libvibe-core0/arm64 has unsatisfiable dependency
    • libvibe-crypto0/arm64 has unsatisfiable dependency
    • libvibe-data0/arm64 has unsatisfiable dependency
    • libvibe-http0/arm64 has unsatisfiable dependency
    • libvibe-inet0/arm64 has unsatisfiable dependency
    • libvibe-mail0/arm64 has unsatisfiable dependency
    • libvibe-mongodb0/arm64 has unsatisfiable dependency
    • libvibe-redis0/arm64 has unsatisfiable dependency
    • libvibe-stream0/arm64 has unsatisfiable dependency
    • libvibe-textfilter0/arm64 has unsatisfiable dependency
    • libvibe-tls0/arm64 has unsatisfiable dependency
    • libvibe-utils0/arm64 has unsatisfiable dependency
    • libvibe-web0/arm64 has unsatisfiable dependency
    • libvibe-core0/armhf has unsatisfiable dependency
    • libvibe-crypto0/armhf has unsatisfiable dependency
    • libvibe-data0/armhf has unsatisfiable dependency
    • libvibe-http0/armhf has unsatisfiable dependency
    • libvibe-inet0/armhf has unsatisfiable dependency
    • libvibe-mail0/armhf has unsatisfiable dependency
    • libvibe-mongodb0/armhf has unsatisfiable dependency
    • libvibe-redis0/armhf has unsatisfiable dependency
    • libvibe-stream0/armhf has unsatisfiable dependency
    • libvibe-textfilter0/armhf has unsatisfiable dependency
    • libvibe-tls0/armhf has unsatisfiable dependency
    • libvibe-utils0/armhf has unsatisfiable dependency
    • libvibe-web0/armhf has unsatisfiable dependency
    • libvibe-core0/i386 has unsatisfiable dependency
    • libvibe-crypto0/i386 has unsatisfiable dependency
    • libvibe-data0/i386 has unsatisfiable dependency
    • libvibe-http0/i386 has unsatisfiable dependency
    • libvibe-inet0/i386 has unsatisfiable dependency
    • libvibe-mail0/i386 has unsatisfiable dependency
    • libvibe-mongodb0/i386 has unsatisfiable dependency
    • libvibe-redis0/i386 has unsatisfiable dependency
    • libvibe-stream0/i386 has unsatisfiable dependency
    • libvibe-textfilter0/i386 has unsatisfiable dependency
    • libvibe-tls0/i386 has unsatisfiable dependency
    • libvibe-utils0/i386 has unsatisfiable dependency
    • libvibe-web0/i386 has unsatisfiable dependency
    • Updating vibe.d would introduce bugs in testing: #941453
    • vibe.d unsatisfiable Build-Depends(-Arch) on amd64: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on arm64: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on armhf: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on i386: libstdx-allocator-dev (>= 2.77.2)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vibe.d.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1868 days old (needed 5 days)
• kpatch (- to 0.6.0-0.2)
  • Migration status for kpatch (- to 0.6.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kpatch would introduce bugs in testing: #1027889, #983648, #991003
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/k/kpatch.html
  • Additional info:
    • 1872 days old (needed 5 days)
• pdfgrep (- to 2.1.2-1)
  • Migration status for pdfgrep (- to 2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdfgrep would introduce bugs in testing: #1000003
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfgrep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1872 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 ♻
    • 1873 days old (needed 5 days)
• xsok (- to 1.02-19)
  • Migration status for xsok (- to 1.02-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xsok would introduce bugs in testing: #1056146
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xsok.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1875 days old (needed 5 days)
• ruby-arel (- to 9.0.0-2)
  • Migration status for ruby-arel (- to 9.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-arel would introduce bugs in testing: #1039034
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-arel.html
    • autopkgtest for ruby-arel/9.0.0-2: 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
    • 1876 days old (needed 2 days)
• resteasy (- to 3.6.2-2)
  • Migration status for resteasy (- to 3.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating resteasy would introduce bugs in testing: #879469
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resteasy.html
    • 1878 days old (needed 5 days)
• mpqc3 (- to 0.0~git20170114-4.1)
  • Migration status for mpqc3 (- to 0.0~git20170114-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mpqc3/amd64 has unsatisfiable dependency
    • mpqc3/arm64 has unsatisfiable dependency
    • mpqc3/armel has unsatisfiable dependency
    • mpqc3/armhf has unsatisfiable dependency
    • mpqc3/i386 has unsatisfiable dependency
    • mpqc3/mips64el has unsatisfiable dependency
    • mpqc3/ppc64el has unsatisfiable dependency
    • Updating mpqc3 would introduce bugs in testing: #946452
    • Build-Depends(-Arch): mpqc3 tiledarray
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mpqc3.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 1894 days old (needed 5 days)
• evqueue-core (- to 2.1-1)
  • Migration status for evqueue-core (- to 2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating evqueue-core would introduce bugs in testing: #1000087, #914801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/evqueue-core.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1928 days old (needed 5 days)
• flightgear-phi (- to 2018.1.1+dfsg1-1.1)
  • Migration status for flightgear-phi (- to 2018.1.1+dfsg1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flightgear-phi would introduce bugs in testing: #979902
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flightgear-phi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1933 days old (needed 5 days)
• mxt-app (- to 1.28-2)
  • Migration status for mxt-app (- to 1.28-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mxt-app would introduce bugs in testing: #952059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mxt-app.html
    • 1936 days old (needed 5 days)
• gauche-gl (- to 0.6-4)
  • Migration status for gauche-gl (- to 0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gauche-gl gauche (not considered)
    • Depends: gauche-gl gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche-gl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1950 days old (needed 5 days)
• swfmill (- to 0.3.6-1)
  • Migration status for swfmill (- to 0.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swfmill would introduce bugs in testing: #1019600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swfmill.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1959 days old (needed 5 days)
• aws-shell (- to 0.2.1-1)
  • Migration status for aws-shell (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aws-shell/amd64 has unsatisfiable dependency
    • aws-shell/arm64 has unsatisfiable dependency
    • Updating aws-shell would introduce bugs in testing: #1050402, #944542
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/aws-shell.html
    • aws-shell unsatisfiable Build-Depends(-Arch) on amd64: awscli (<< 2.0.0)
    • Not built on buildd: arch all binaries uploaded by takaki, a new source-only upload is needed to allow migration
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1967 days old (needed 5 days)
• darcs-monitor (- to 0.4.2-14)
  • Migration status for darcs-monitor (- to 0.4.2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating darcs-monitor would introduce bugs in testing: #1057792
    • Depends: darcs-monitor darcs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/darcs-monitor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1970 days old (needed 5 days)
• dublin-traceroute (- to 0.4.2-2)
  • Migration status for dublin-traceroute (- to 0.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): dublin-traceroute -> libtins4.0/4.0-1+b1/arm64
    • Impossible Build-Depends(-Arch): dublin-traceroute -> libtins4.0/4.0-1+b1/armel
    • Impossible Build-Depends(-Arch): dublin-traceroute -> libtins4.0/4.0-1+b1/armhf
    • Impossible Build-Depends(-Arch): dublin-traceroute -> libtins4.0/4.0-1+b1/i386
    • Impossible Build-Depends(-Arch): dublin-traceroute -> libtins4.0/4.0-1+b1/mips64el
    • Impossible Build-Depends(-Arch): dublin-traceroute -> libtins4.0/4.0-1+b1/ppc64el
    • Impossible Build-Depends(-Arch): dublin-traceroute -> libtins4.0/4.0-1+b1/s390x
    • Impossible Build-Depends(-Arch): dublin-traceroute -> libtins4.0/4.0-1+b2/amd64
    • Impossible Depends: dublin-traceroute -> libtins4.0/4.0-1+b1/arm64
    • Impossible Depends: dublin-traceroute -> libtins4.0/4.0-1+b1/armel
    • Impossible Depends: dublin-traceroute -> libtins4.0/4.0-1+b1/armhf
    • Impossible Depends: dublin-traceroute -> libtins4.0/4.0-1+b1/i386
    • Impossible Depends: dublin-traceroute -> libtins4.0/4.0-1+b1/mips64el
    • Impossible Depends: dublin-traceroute -> libtins4.0/4.0-1+b1/ppc64el
    • Impossible Depends: dublin-traceroute -> libtins4.0/4.0-1+b1/s390x
    • Impossible Depends: dublin-traceroute -> libtins4.0/4.0-1+b2/amd64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dublin-traceroute.html
    • 1974 days old (needed 5 days)
• mozilla-noscript (- to 10.1.9.6-2)
  • Migration status for mozilla-noscript (- to 10.1.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mozilla-noscript would introduce bugs in testing: #922396
    • Build-Depends(-Arch): mozilla-noscript mozilla-devscripts
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mozilla-noscript.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1977 days old (needed 5 days)
• newmat (- to 1.10.4-8)
  • Migration status for newmat (- to 1.10.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating newmat would introduce bugs in testing: #1052790
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/newmat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1979 days old (needed 5 days)
• clearlooks-phenix-theme (- to 7.0.1-3)
  • Migration status for clearlooks-phenix-theme (- to 7.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clearlooks-phenix-theme would introduce bugs in testing: #961834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clearlooks-phenix-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1987 days old (needed 5 days)
• bdfproxy (- to 0.3.9-3)
  • Migration status for bdfproxy (- to 0.3.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bdfproxy would introduce bugs in testing: #1033923
    • autopkgtest for bdfproxy/0.3.9-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: bdfproxy backdoor-factory
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bdfproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 1990 days old (needed 5 days)
• ruby-yaml-db (- to 0.7.0-1)
  • Migration status for ruby-yaml-db (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-yaml-db would introduce bugs in testing: #1019679
    • autopkgtest for ruby-yaml-db/0.7.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-yaml-db.html
    • 2016 days old (needed 5 days)
• lief (- to 0.9.0-1)
  • Migration status for lief (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lief would introduce bugs in testing: #1037752
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lief.html
    • Reproducible on i386 - info ♻
    • 2031 days old (needed 5 days)
• openmx (- to 3.8.5+dfsg1-1)
  • Migration status for openmx (- to 3.8.5+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openmx would introduce bugs in testing: #957639
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmx.html
    • 2034 days old (needed 5 days)
• vowpal-wabbit (- to 8.6.1.dfsg1-1)
  • Migration status for vowpal-wabbit (- to 8.6.1.dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vowpal-wabbit would introduce bugs in testing: #836450, #893031
    • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vowpal-wabbit.html
    • 2036 days old (needed 5 days)
• sus (- to 7.20180621)
  • Migration status for sus (- to 7.20180621): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sus would introduce bugs in testing: #968415
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2072 days old (needed 5 days)
• soundmanager2 (- to 2.97a.20150601+dfsg2-2)
  • Migration status for soundmanager2 (- to 2.97a.20150601+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating soundmanager2 would introduce bugs in testing: #1031482
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soundmanager2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 2075 days old (needed 5 days)
• xqilla (- to 2.3.4-1)
  • Migration status for xqilla (- to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xqilla would introduce bugs in testing: #1040163, #984418
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xqilla.html
    • 2077 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
    • Depends: erlang-cowboy erlang-ranch
  • 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 ♻
    • 2087 days old (needed 5 days)
• tinyjsd (- to 1.2+git1-1)
  • Migration status for tinyjsd (- to 1.2+git1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tinyjsd would introduce bugs in testing: #971774
    • Not built on buildd: arch all binaries uploaded by dkg, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): tinyjsd mozilla-devscripts
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinyjsd.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2088 days old (needed 5 days)
• golang-github-coreos-go-tspi (- to 0.1.1-2)
  • Migration status for golang-github-coreos-go-tspi (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-coreos-go-tspi would introduce bugs in testing: #849665
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-coreos-go-tspi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2139 days old (needed 5 days)
• mldemos (- to 0.5.1+git.1.ee5d11f-4)
  • Migration status for mldemos (- to 0.5.1+git.1.ee5d11f-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mldemos would introduce bugs in testing: #915711, #922585
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mldemos.html
    • 2140 days old (needed 5 days)
• z88 (- to 13.0.0+dfsg2-6)
  • Migration status for z88 (- to 13.0.0+dfsg2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): z88 gtkglext (not considered)
    • Depends: z88 gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/z88.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2142 days old (needed 5 days)
• debbugs (- to 2.6.0)
  • Migration status for debbugs (- to 2.6.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debbugs would introduce bugs in testing: #903413
    • autopkgtest for debbugs/2.6.0: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by don, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debbugs.html
    • 2159 days old (needed 5 days)
• librsl (- to 1.43-1.2)
  • Migration status for librsl (- to 1.43-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating librsl would introduce bugs in testing: #893023
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librsl.html
    • 2209 days old (needed 5 days)
• ignore-me (- to 0.1.2-1)
  • Migration status for ignore-me (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ignore-me would introduce bugs in testing: #912037, #948875
    • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ignore-me.html
    • 2235 days old (needed 5 days)
• boinc-app-eah-brp (- to 0.20170426+dfsg-10)
  • Migration status for boinc-app-eah-brp (- to 0.20170426+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • boinc-app-eah-brp/amd64 has unsatisfiable dependency
    • boinc-app-eah-brp/arm64 has unsatisfiable dependency
    • boinc-app-eah-brp/armel has unsatisfiable dependency
    • boinc-app-eah-brp/armhf has unsatisfiable dependency
    • boinc-app-eah-brp/i386 has unsatisfiable dependency
    • boinc-app-eah-brp/mips64el has unsatisfiable dependency
    • boinc-app-eah-brp/ppc64el has unsatisfiable dependency
    • boinc-app-eah-brp/s390x has unsatisfiable dependency
    • Updating boinc-app-eah-brp would introduce bugs in testing: #887880, #949603
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on amd64: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on arm64: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on armel: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on armhf: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on i386: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on mips64el: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on ppc64el: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on s390x: g++-5 | g++ (<< 6)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/boinc-app-eah-brp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2236 days old (needed 5 days)
• debirf (- to 0.38)
  • Migration status for debirf (- to 0.38): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debirf would introduce bugs in testing: #901779, #969938
    • autopkgtest for debirf/0.38: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debirf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2236 days old (needed 5 days)
• pagetools (- to 0.1-3)
  • Migration status for pagetools (- to 0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pagetools/amd64 has unsatisfiable dependency
    • pagetools/arm64 has unsatisfiable dependency
    • pagetools/armel has unsatisfiable dependency
    • pagetools/armhf has unsatisfiable dependency
    • pagetools/i386 has unsatisfiable dependency
    • pagetools/mips64el has unsatisfiable dependency
    • pagetools/ppc64el has unsatisfiable dependency
    • pagetools/s390x has unsatisfiable dependency
    • Updating pagetools would introduce bugs in testing: #1012690
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pagetools.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2239 days old (needed 5 days)
• debtags (- to 2.1.5)
  • Migration status for debtags (- to 2.1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debtags would introduce bugs in testing: #1058262
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debtags.html
    • Reproducible on i386 - info ♻
    • 2241 days old (needed 5 days)
• khronos-opengl-man4 (- to 1.0~svn33624-1)
  • Migration status for khronos-opengl-man4 (- to 1.0~svn33624-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): khronos-opengl-man4 w3-dtd-mathml (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khronos-opengl-man4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2242 days old (needed 5 days)
• jajuk (- to 1:1.10.9+dfsg2-4)
  • Migration status for jajuk (- to 1:1.10.9+dfsg2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jajuk would introduce bugs in testing: #923330
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jajuk.html
    • 2277 days old (needed 5 days)
• php-enum (- to 2.3.1-1)
  • Migration status for php-enum (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-enum would introduce bugs in testing: #882928
    • autopkgtest for php-enum/2.3.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-enum.html
    • 2292 days old (needed 5 days)
• octicons (- to 4.4.0-2)
  • Migration status for octicons (- to 4.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octicons would introduce bugs in testing: #883107
    • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octicons.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2311 days old (needed 5 days)
• libcypher-parser (- to 0.6.0-1)
  • Migration status for libcypher-parser (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libcypher-parser would introduce bugs in testing: #1012975
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcypher-parser.html
    • 2333 days old (needed 5 days)
• urweb (- to 20170720+dfsg-2)
  • Migration status for urweb (- to 20170720+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liburweb0/ppc64el has unsatisfiable dependency
    • Updating urweb would introduce bugs in testing: #1060107
    • Build-Depends(-Arch): urweb mlton
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urweb.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 2349 days old (needed 5 days)
• opengrm-ngram (- to 1.3.2-3)
  • Migration status for opengrm-ngram (- to 1.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libngram-tools/amd64 has unsatisfiable dependency
    • libngram2/amd64 has unsatisfiable dependency
    • libngram-tools/arm64 has unsatisfiable dependency
    • libngram2/arm64 has unsatisfiable dependency
    • libngram-tools/armel has unsatisfiable dependency
    • libngram2/armel has unsatisfiable dependency
    • libngram-tools/armhf has unsatisfiable dependency
    • libngram2/armhf has unsatisfiable dependency
    • libngram-tools/i386 has unsatisfiable dependency
    • libngram2/i386 has unsatisfiable dependency
    • libngram-tools/mips64el has unsatisfiable dependency
    • libngram2/mips64el has unsatisfiable dependency
    • libngram-tools/ppc64el has unsatisfiable dependency
    • libngram2/ppc64el has unsatisfiable dependency
    • libngram-tools/s390x has unsatisfiable dependency
    • libngram2/s390x has unsatisfiable dependency
    • Updating opengrm-ngram would introduce bugs in testing: #1019172
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/opengrm-ngram.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2361 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 ♻
    • 2379 days old (needed 5 days)
• guidedog (- to 1.3.0-1)
  • Migration status for guidedog (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guidedog would introduce bugs in testing: #1025571
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guidedog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2391 days old (needed 5 days)
• golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1)
  • Migration status for golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-minio-cli would introduce bugs in testing: #869190
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-minio-cli.html
    • 2416 days old (needed 5 days)
• golang-gopkg-mcuadros-go-syslog.v2 (- to 2.2.1-1)
  • Migration status for golang-gopkg-mcuadros-go-syslog.v2 (- to 2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-gopkg-mcuadros-go-syslog.v2 would introduce bugs in testing: #954514
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gopkg-mcuadros-go-syslog.v2.html
    • 2421 days old (needed 5 days)
• ants (- to 2.1.0-5)
  • Migration status for ants (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ants/amd64 has unsatisfiable dependency
    • ants/i386 has unsatisfiable dependency
    • Updating ants would introduce bugs in testing: #872741, #909833
    • ants unsatisfiable Build-Depends(-Arch) on amd64: libinsighttoolkit4-dev (>> 4.7.0~)
    • ants unsatisfiable Build-Depends(-Arch) on i386: libinsighttoolkit4-dev (>> 4.7.0~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/ants.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 2542 days old (needed 5 days)
• yorick-mira (- to 1.1.0+git20170124.3bd1c3~dfsg1-2)
  • Migration status for yorick-mira (- to 1.1.0+git20170124.3bd1c3~dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: yorick-mira yorick-ynfft (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-mira.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2545 days old (needed 5 days)
• irssi-plugin-robustirc (- to 0.6-4)
  • Migration status for irssi-plugin-robustirc (- to 0.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating irssi-plugin-robustirc would introduce bugs in testing: #1015080
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/irssi-plugin-robustirc.html
    • 2558 days old (needed 5 days)
• freebsd-libs (- to 10.3~svn296373-10)
  • Migration status for freebsd-libs (- to 10.3~svn296373-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by steven@pyro.eu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): freebsd-libs freebsd-buildutils
    • Build-Depends(-Arch): freebsd-libs freebsd-glue
    • Depends: freebsd-libs freebsd-glue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 2575 days old (needed 5 days)
• lilyterm (- to 0.9.9.4+git20150208.f600c0-5)
  • Migration status for lilyterm (- to 0.9.9.4+git20150208.f600c0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lilyterm would introduce bugs in testing: #970419
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lilyterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2587 days old (needed 5 days)
• bookkeeper (- to 4.4.0-1)
  • Migration status for bookkeeper (- to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bookkeeper would introduce bugs in testing: #906340
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookkeeper.html
    • 2593 days old (needed 5 days)
• gcc-msp430 (- to 4.6.3~mspgcc-20120406-7.1)
  • Migration status for gcc-msp430 (- to 4.6.3~mspgcc-20120406-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-msp430 would introduce bugs in testing: #965541
    • Build-Depends(-Arch): gcc-msp430 binutils-msp430
    • Depends: gcc-msp430 binutils-msp430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-msp430.html
    • 2596 days old (needed 5 days)
• gdb-msp430 (- to 7.2a~mspgcc-20111205-3.1)
  • Migration status for gdb-msp430 (- to 7.2a~mspgcc-20111205-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gdb-msp430 would introduce bugs in testing: #965545, #999284
    • Build-Depends(-Arch): gdb-msp430 binutils-msp430
    • Depends: gdb-msp430 binutils-msp430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdb-msp430.html
    • 2596 days old (needed 5 days)
• origami (- to 1.2.7+really0.7.4-1.1)
  • Migration status for origami (- to 1.2.7+really0.7.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating origami would introduce bugs in testing: #953144
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/origami.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2596 days old (needed 5 days)
• gli (- to 0.8.2.0+ds1-2)
  • Migration status for gli (- to 0.8.2.0+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gli would introduce bugs in testing: #888933
    • autopkgtest for gli/0.8.2.0+ds1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gli.html
    • 2597 days old (needed 5 days)
• rdup (- to 1.1.15-1)
  • Migration status for rdup (- to 1.1.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rdup/amd64 has unsatisfiable dependency
    • rdup/arm64 has unsatisfiable dependency
    • rdup/armel has unsatisfiable dependency
    • rdup/armhf has unsatisfiable dependency
    • rdup/i386 has unsatisfiable dependency
    • rdup/mips64el has unsatisfiable dependency
    • rdup/ppc64el has unsatisfiable dependency
    • rdup/s390x has unsatisfiable dependency
    • Updating rdup would introduce bugs in testing: #941101, #999975
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rdup.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2601 days old (needed 5 days)
• verilog-mode (- to 20161124.fd230e6-2)
  • Migration status for verilog-mode (- to 20161124.fd230e6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating verilog-mode would introduce bugs in testing: #934977
    • verilog-mode unsatisfiable Build-Depends(-Arch) on amd64: emacs25
    • Not built on buildd: arch all binaries uploaded by spwhitton@spwhitton.name, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilog-mode.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2606 days old (needed 5 days)
• ruby-celluloid-io (- to 0.16.2-5)
  • Migration status for ruby-celluloid-io (- to 0.16.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-celluloid-io would introduce bugs in testing: #1031476
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-celluloid-io.html
    • autopkgtest for ruby-celluloid-io/0.16.2-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Reproducible on i386 - info ♻
    • 2616 days old (needed 5 days)
• ruby-uglifier (- to 2.7.2+dfsg-2)
  • Migration status for ruby-uglifier (- to 2.7.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-uglifier would introduce bugs in testing: #981224
    • autopkgtest for ruby-uglifier/2.7.2+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-uglifier.html
    • 2627 days old (needed 5 days)
• golang-github-tsenart-tb (- to 0.0~git20151208.0.19f4c3d-2)
  • Migration status for golang-github-tsenart-tb (- to 0.0~git20151208.0.19f4c3d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-tsenart-tb would introduce bugs in testing: #964048
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-tsenart-tb.html
    • 2640 days old (needed 5 days)
• powermock (- to 1.6.6-1)
  • Migration status for powermock (- to 1.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating powermock would introduce bugs in testing: #875358
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/powermock.html
    • 2659 days old (needed 5 days)
• kryo-serializers (- to 0.22-3)
  • Migration status for kryo-serializers (- to 0.22-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kryo-serializers would introduce bugs in testing: #875594
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kryo-serializers.html
    • 2704 days old (needed 5 days)
• arrayfire (- to 3.3.2+dfsg1-4)
  • Migration status for arrayfire (- to 3.3.2+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating arrayfire would introduce bugs in testing: #892288, #897707
    • autopkgtest for arrayfire/3.3.2+dfsg1-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): arrayfire clblas
    • Depends: arrayfire clblas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arrayfire.html
    • 2746 days old (needed 5 days)
• ecere-sdk (- to 0.44.15-1)
  • Migration status for ecere-sdk (- to 0.44.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libedasqlite0/amd64 has unsatisfiable dependency
    • libedasqlite0/arm64 has unsatisfiable dependency
    • libedasqlite0/armel has unsatisfiable dependency
    • libedasqlite0/armhf has unsatisfiable dependency
    • libecere0/i386 has unsatisfiable dependency
    • libedasqlite0/i386 has unsatisfiable dependency
    • libedasqlite0/mips64el has unsatisfiable dependency
    • libedasqlite0/ppc64el has unsatisfiable dependency
    • libedasqlite0/s390x has unsatisfiable dependency
    • Updating ecere-sdk would introduce bugs in testing: #898832, #995050
    • Build-Depends(-Arch): ecere-sdk mesa
  • 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
    • 2757 days old (needed 5 days)
• xorp (- to 1.8.6~wip.20160715-2)
  • Migration status for xorp (- to 1.8.6~wip.20160715-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xorp/amd64 has unsatisfiable dependency
    • xorp/i386 has unsatisfiable dependency
    • xorp/ppc64el has unsatisfiable dependency
    • xorp/s390x has unsatisfiable dependency
    • Updating xorp would introduce bugs in testing: #947586, #958600
    • xorp unsatisfiable Build-Depends(-Arch) on amd64: dh-systemd
    • xorp unsatisfiable Build-Depends(-Arch) on i386: dh-systemd
    • xorp unsatisfiable Build-Depends(-Arch) on ppc64el: dh-systemd
    • xorp unsatisfiable Build-Depends(-Arch) on s390x: dh-systemd
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/xorp.html
    • uninstallable on arch amd64, 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 i386 - info ♻
    • 2770 days old (needed 5 days)
• grip (- to 4.2.0-3)
  • Migration status for grip (- to 4.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grip would introduce bugs in testing: #1025825, #953967
    • autopkgtest for grip/4.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 ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grip.html
    • 2789 days old (needed 5 days)
• libretro-mupen64plus (- to 2.0+git20160207+dfsg2-1)
  • Migration status for libretro-mupen64plus (- to 2.0+git20160207+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libretro-mupen64plus would introduce bugs in testing: #935282, #976078
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-mupen64plus.html
    • 2810 days old (needed 5 days)
• glosstex (- to 0.4.dfsg.1-4)
  • Migration status for glosstex (- to 0.4.dfsg.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glosstex would introduce bugs in testing: #1052914
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glosstex.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2814 days old (needed 5 days)
• elektra (- to 0.8.14-5.1)
  • Migration status for elektra (- to 0.8.14-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elektra-tests/amd64 has unsatisfiable dependency
    • libelektra4-python/amd64 has unsatisfiable dependency
    • python3-elektra/amd64 has unsatisfiable dependency
    • elektra-tests/arm64 has unsatisfiable dependency
    • libelektra4-python/arm64 has unsatisfiable dependency
    • python3-elektra/arm64 has unsatisfiable dependency
    • elektra-tests/armel has unsatisfiable dependency
    • libelektra4-python/armel has unsatisfiable dependency
    • python3-elektra/armel has unsatisfiable dependency
    • elektra-tests/armhf has unsatisfiable dependency
    • libelektra4-python/armhf has unsatisfiable dependency
    • python3-elektra/armhf has unsatisfiable dependency
    • elektra-tests/i386 has unsatisfiable dependency
    • libelektra4-python/i386 has unsatisfiable dependency
    • python3-elektra/i386 has unsatisfiable dependency
    • elektra-tests/mips64el has unsatisfiable dependency
    • libelektra4-python/mips64el has unsatisfiable dependency
    • python3-elektra/mips64el has unsatisfiable dependency
    • elektra-tests/ppc64el has unsatisfiable dependency
    • libelektra4-python/ppc64el has unsatisfiable dependency
    • python3-elektra/ppc64el has unsatisfiable dependency
    • elektra-tests/s390x has unsatisfiable dependency
    • libelektra4-python/s390x has unsatisfiable dependency
    • python3-elektra/s390x has unsatisfiable dependency
    • Updating elektra would introduce bugs in testing: #844145, #846200, #851592, #881676, #956949
    • elektra unsatisfiable Build-Depends(-Arch) on amd64: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on arm64: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on armel: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on armhf: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on i386: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on mips64el: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on ppc64el: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on s390x: swig3.0
    • Not built on buildd: arch amd64 binaries uploaded by aeb
    • Not built on buildd: arch all binaries uploaded by aeb, a new source-only upload is needed to allow migration
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/elektra.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2820 days old (needed 5 days)
• php-sabre-xml (- to 1.4.2-1)
  • Migration status for php-sabre-xml (- to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-xml would introduce bugs in testing: #882949
    • autopkgtest for php-sabre-xml/1.4.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-sabre-xml php-sabre-uri
    • Depends: php-sabre-xml php-sabre-uri
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-xml.html
    • 2834 days old (needed 5 days)
• twofish (- to 0.3-5)
  • Migration status for twofish (- to 0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating twofish would introduce bugs in testing: #997617
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/twofish.html
    • 2841 days old (needed 5 days)
• php-sabre-uri (- to 1.1.0-1)
  • Migration status for php-sabre-uri (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-uri would introduce bugs in testing: #882923
    • autopkgtest for php-sabre-uri/1.1.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-uri.html
    • 2897 days old (needed 5 days)
• php-sabre-http (- to 4.2.1-3)
  • Migration status for php-sabre-http (- to 4.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-http would introduce bugs in testing: #882935
    • autopkgtest for php-sabre-http/4.2.1-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-sabre-http php-sabre-event
    • Build-Depends(-Arch): php-sabre-http php-sabre-uri
    • Depends: php-sabre-http php-sabre-event
    • Depends: php-sabre-http php-sabre-uri
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-http.html
    • 2903 days old (needed 5 days)
• php-sabre-event (- to 3.0.0~as2.0.2-2)
  • Migration status for php-sabre-event (- to 3.0.0~as2.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-event would introduce bugs in testing: #882915
    • autopkgtest for php-sabre-event/3.0.0~as2.0.2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-event.html
    • 2911 days old (needed 5 days)
• yorick-ynfft (- to 1.0.3-1)
  • Migration status for yorick-ynfft (- to 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): yorick-ynfft nfft (not considered)
    • Depends: yorick-ynfft nfft (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-ynfft.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 2929 days old (needed 5 days)
• libr3 (- to 1.3.4-1)
  • Migration status for libr3 (- to 1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libr3 would introduce bugs in testing: #1000058
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libr3.html
    • autopkgtest for libr3/1.3.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2937 days old (needed 2 days)
• literki (- to 0.0.0+20100113.git1da40724-1.2)
  • Migration status for literki (- to 0.0.0+20100113.git1da40724-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating literki would introduce bugs in testing: #892344, #899846, #999283
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/literki.html
    • 2944 days old (needed 5 days)
• fsharp (- to 4.0.0.4+dfsg2-2)
  • Migration status for fsharp (- to 4.0.0.4+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fsharp/4.0.0.4+dfsg2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fsharp.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 2996 days old (needed 5 days)
• sipgrep (- to 2.1.0-2)
  • Migration status for sipgrep (- to 2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sipgrep would introduce bugs in testing: #999961
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sipgrep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3037 days old (needed 5 days)
• curlftpfs (- to 0.9.2-9)
  • Migration status for curlftpfs (- to 0.9.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating curlftpfs would introduce bugs in testing: #965476
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curlftpfs.html
    • 3111 days old (needed 5 days)
• bwctl (- to 1.5.4+dfsg1-1)
  • Migration status for bwctl (- to 1.5.4+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bwctl would introduce bugs in testing: #997326
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bwctl.html
    • 3122 days old (needed 5 days)
• yap (- to 6.2.2-6)
  • Migration status for yap (- to 6.2.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yap/i386 has unsatisfiable dependency
    • Updating yap would introduce bugs in testing: #877034, #965915
    • autopkgtest for yap/6.2.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yap.html
    • uninstallable on arch i386, not running autopkgtest there
    • 3145 days old (needed 5 days)
• vncterm (- to 0.9.10-2)
  • Migration status for vncterm (- to 0.9.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vncterm would introduce bugs in testing: #898453
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vncterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3179 days old (needed 5 days)
• qmenu (- to 5.0.2-2)
  • Migration status for qmenu (- to 5.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qmenu would introduce bugs in testing: #997191
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qmenu.html
    • 3220 days old (needed 5 days)
• libapache2-mod-auth-pgsql (- to 2.0.3-6.1)
  • Migration status for libapache2-mod-auth-pgsql (- to 2.0.3-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-auth-pgsql would introduce bugs in testing: #947039
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-auth-pgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3323 days old (needed 5 days)
• libmonitoring-availability-perl (- to 0.46-1)
  • Migration status for libmonitoring-availability-perl (- to 0.46-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libmonitoring-availability-perl would introduce bugs in testing: #839432
    • Not built on buildd: arch all binaries uploaded by formorer, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmonitoring-availability-perl.html
    • Reproducible on i386 - info ♻
    • 3407 days old (needed 5 days)
• pam-pgsql (- to 0.7.3.2-1)
  • Migration status for pam-pgsql (- to 0.7.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pam-pgsql would introduce bugs in testing: #863650
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-pgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3426 days old (needed 5 days)
• tart (- to 3.10-1)
  • Migration status for tart (- to 3.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tart would introduce bugs in testing: #965837
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tart.html
    • 3454 days old (needed 5 days)
• ptex-jtex (- to 1.7+1-15)
  • Migration status for ptex-jtex (- to 1.7+1-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ptex-jtex would introduce bugs in testing: #1003654
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3556 days old (needed 5 days)
• gogglesmm (- to 0.12.7-3)
  • Migration status for gogglesmm (- to 0.12.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gogglesmm would introduce bugs in testing: #1008384
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gogglesmm.html
    • 3580 days old (needed 5 days)
• scheme2c (- to 2012.10.14-1)
  • Migration status for scheme2c (- to 2012.10.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scheme2c would introduce bugs in testing: #778111
    • Not built on buildd: arch amd64 binaries uploaded by bap
    • Not built on buildd: arch all binaries uploaded by bap, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scheme2c.html
    • 3586 days old (needed 5 days)
• libpthread-workqueue (- to 0.9.1-1)
  • Migration status for libpthread-workqueue (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpthread-workqueue would introduce bugs in testing: #835107
    • Not built on buildd: arch amd64 binaries uploaded by rbalint
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpthread-workqueue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3638 days old (needed 5 days)
• couriergrey (- to 0.3.2-5)
  • Migration status for couriergrey (- to 0.3.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: couriergrey courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/couriergrey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3688 days old (needed 5 days)
• reminiscence (- to 0.2.1-2)
  • Migration status for reminiscence (- to 0.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating reminiscence would introduce bugs in testing: #985184
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3776 days old (needed 5 days)
• zeroc-ice-manual (- to 3.5.0-1)
  • Migration status for zeroc-ice-manual (- to 3.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zeroc-ice-manual would introduce bugs in testing: #864472
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3841 days old (needed 5 days)
• mutextrace (- to 0.1.4-1)
  • Migration status for mutextrace (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mutextrace would introduce bugs in testing: #743062
    • Not built on buildd: arch amd64 binaries uploaded by sjr
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mutextrace.html
    • 3944 days old (needed 5 days)
• xmms2-scrobbler (- to 0.4.0-4)
  • Migration status for xmms2-scrobbler (- to 0.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xmms2-scrobbler would introduce bugs in testing: #798099, #919037
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmms2-scrobbler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4007 days old (needed 5 days)
• msp430-libc (- to 20120224-1)
  • Migration status for msp430-libc (- to 20120224-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating msp430-libc would introduce bugs in testing: #965732, #999077
    • Build-Depends(-Arch): msp430-libc binutils-msp430
    • Build-Depends(-Arch): msp430-libc gcc-msp430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/msp430-libc.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • 4296 days old (needed 5 days)
• pxe-kexec (- to 0.2.4-3)
  • Migration status for pxe-kexec (- to 0.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pxe-kexec would introduce bugs in testing: #984300
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pxe-kexec.html
    • 4299 days old (needed 5 days)
• mppenc (- to 1.16-1.1)
  • Migration status for mppenc (- to 1.16-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mppenc would introduce bugs in testing: #965730, #999076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mppenc.html
    • 4327 days old (needed 5 days)
• navi2ch (- to 2.0.0~git20120331-1)
  • Migration status for navi2ch (- to 2.0.0~git20120331-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating navi2ch would introduce bugs in testing: #780480, #952259
    • Not built on buildd: arch all binaries uploaded by knok, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/navi2ch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4328 days old (needed 5 days)
• privbind (- to 1.2-1.1)
  • Migration status for privbind (- to 1.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating privbind would introduce bugs in testing: #965787, #998987
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/privbind.html
    • 4335 days old (needed 5 days)
• nttcp (- to 1.47-13)
  • Migration status for nttcp (- to 1.47-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nttcp would introduce bugs in testing: #1002847
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4345 days old (needed 5 days)
• mixer.app (- to 1.8.0-5)
  • Migration status for mixer.app (- to 1.8.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mixer.app would introduce bugs in testing: #896580
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mixer.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4365 days old (needed 5 days)
• pstack (- to 1.3.1-1)
  • Migration status for pstack (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pstack would introduce bugs in testing: #950168
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pstack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 4522 days old (needed 5 days)
• gems (- to 1.1.1-2)
  • Migration status for gems (- to 1.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gems would introduce bugs in testing: #965548
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gems.html
    • 4527 days old (needed 5 days)
• libinnodb (- to 1.0.6.6750-1)
  • Migration status for libinnodb (- to 1.0.6.6750-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libinnodb would introduce bugs in testing: #952290, #999029
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libinnodb.html
    • 5086 days old (needed 5 days)