Generated: 2019.11.19 12:07:27 +0000

• -binoculars (0.0.4-1 to -)
  • Migration status for -binoculars (0.0.4-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -hfsutils (3.2.6-14 to -)
  • Migration status for -hfsutils (3.2.6-14 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -linux-latest (107 to -)
  • Migration status for -linux-latest (107 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Package not in unstable, will try to remove
• -manpages-es (1.55-10 to -)
  • Migration status for -manpages-es (1.55-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Package not in unstable, will try to remove
• -mod-gnutls (0.9.0-1 to -)
  • Migration status for -mod-gnutls (0.9.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -pyfai (0.18.0+dfsg1-3 to -)
  • Migration status for -pyfai (0.18.0+dfsg1-3 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -python-fabio (0.9.0+dfsg-1 to -)
  • Migration status for -python-fabio (0.9.0+dfsg-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -rust-globset (0.4.4-1 to -)
  • Migration status for -rust-globset (0.4.4-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -rust-md5 (0.3.8-1 to -)
  • Migration status for -rust-md5 (0.3.8-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -rust-memoffset (0.2.1-1 to -)
  • Migration status for -rust-memoffset (0.2.1-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -silx (0.11.0+dfsg-2 to -)
  • Migration status for -silx (0.11.0+dfsg-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• advi/armel (1.10.2-5 to 1.10.2-5)
  • Migration status for advi/armel (1.10.2-5 to 1.10.2-5): Will attempt migration (Any information below is purely informational)
• advi/mips64el (1.10.2-5 to 1.10.2-5)
  • Migration status for advi/mips64el (1.10.2-5 to 1.10.2-5): Will attempt migration (Any information below is purely informational)
• advi/mipsel (1.10.2-5 to 1.10.2-5)
  • Migration status for advi/mipsel (1.10.2-5 to 1.10.2-5): Will attempt migration (Any information below is purely informational)
• alt-ergo/amd64 (2.0.0-5 to 2.0.0-5)
  • Migration status for alt-ergo/amd64 (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• alt-ergo/arm64 (2.0.0-5 to 2.0.0-5)
  • Migration status for alt-ergo/arm64 (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• alt-ergo/armel (2.0.0-5 to 2.0.0-5)
  • Migration status for alt-ergo/armel (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• alt-ergo/i386 (2.0.0-5 to 2.0.0-5)
  • Migration status for alt-ergo/i386 (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• alt-ergo/mips64el (2.0.0-5 to 2.0.0-5)
  • Migration status for alt-ergo/mips64el (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• alt-ergo/mipsel (2.0.0-5 to 2.0.0-5)
  • Migration status for alt-ergo/mipsel (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• alt-ergo/ppc64el (2.0.0-5 to 2.0.0-5)
  • Migration status for alt-ergo/ppc64el (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• alt-ergo/s390x (2.0.0-5 to 2.0.0-5)
  • Migration status for alt-ergo/s390x (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• approx/armel (5.10-2 to 5.10-2)
  • Migration status for approx/armel (5.10-2 to 5.10-2): Will attempt migration (Any information below is purely informational)
• approx/mips64el (5.10-2 to 5.10-2)
  • Migration status for approx/mips64el (5.10-2 to 5.10-2): Will attempt migration (Any information below is purely informational)
• approx/mipsel (5.10-2 to 5.10-2)
  • Migration status for approx/mipsel (5.10-2 to 5.10-2): Will attempt migration (Any information below is purely informational)
• apron/amd64 (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/amd64 (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• apron/arm64 (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/arm64 (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• apron/armel (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/armel (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• apron/armhf (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/armhf (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• apron/i386 (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/i386 (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• apron/mips64el (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/mips64el (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• apron/mipsel (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/mipsel (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• apron/ppc64el (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/ppc64el (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• apron/s390x (0.9.10-9.1 to 0.9.10-9.1)
  • Migration status for apron/s390x (0.9.10-9.1 to 0.9.10-9.1): Will attempt migration (Any information below is purely informational)
• audit/amd64 (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/amd64 (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/amd64 libprelude (not considered)
• audit/arm64 (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/arm64 (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/arm64 libprelude (not considered)
• audit/armel (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/armel (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/armel libprelude (not considered)
• audit/armhf (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/armhf (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/armhf libprelude (not considered)
• audit/i386 (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/i386 (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/i386 libprelude (not considered)
• audit/mips64el (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/mips64el (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/mips64el libprelude (not considered)
• audit/mipsel (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/mipsel (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/mipsel libprelude (not considered)
• audit/ppc64el (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/ppc64el (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/ppc64el libprelude (not considered)
• audit/s390x (1:2.8.5-2 to 1:2.8.5-2)
  • Migration status for audit/s390x (1:2.8.5-2 to 1:2.8.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: audit/s390x libprelude (not considered)
• belenios/armel (1.9+dfsg-1 to 1.9+dfsg-1)
  • Migration status for belenios/armel (1.9+dfsg-1 to 1.9+dfsg-1): Will attempt migration (Any information below is purely informational)
• belenios/mips64el (1.9+dfsg-1 to 1.9+dfsg-1)
  • Migration status for belenios/mips64el (1.9+dfsg-1 to 1.9+dfsg-1): Will attempt migration (Any information below is purely informational)
• belenios/mipsel (1.9+dfsg-1 to 1.9+dfsg-1)
  • Migration status for belenios/mipsel (1.9+dfsg-1 to 1.9+dfsg-1): Will attempt migration (Any information below is purely informational)
• bibtex2html/armel (1.99-3 to 1.99-3)
  • Migration status for bibtex2html/armel (1.99-3 to 1.99-3): Will attempt migration (Any information below is purely informational)
• bibtex2html/mips64el (1.99-3 to 1.99-3)
  • Migration status for bibtex2html/mips64el (1.99-3 to 1.99-3): Will attempt migration (Any information below is purely informational)
• bibtex2html/mipsel (1.99-3 to 1.99-3)
  • Migration status for bibtex2html/mipsel (1.99-3 to 1.99-3): Will attempt migration (Any information below is purely informational)
• bin-prot/amd64 (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/amd64 (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• bin-prot/arm64 (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/arm64 (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• bin-prot/armel (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/armel (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• bin-prot/armhf (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/armhf (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• bin-prot/i386 (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/i386 (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• bin-prot/mips64el (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/mips64el (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• bin-prot/mipsel (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/mipsel (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• bin-prot/ppc64el (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/ppc64el (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• bin-prot/s390x (113.33.03-5 to 113.33.03-5)
  • Migration status for bin-prot/s390x (113.33.03-5 to 113.33.03-5): Will attempt migration (Any information below is purely informational)
• biniou/amd64 (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/amd64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• biniou/arm64 (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/arm64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• biniou/armel (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/armel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• biniou/armhf (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/armhf (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• biniou/i386 (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/i386 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• biniou/mips64el (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/mips64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• biniou/mipsel (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/mipsel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• biniou/ppc64el (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/ppc64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• biniou/s390x (1.2.0-1 to 1.2.0-1)
  • Migration status for biniou/s390x (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• binoculars/amd64 (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/amd64 (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• binoculars/arm64 (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/arm64 (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• binoculars/armel (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/armel (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• binoculars/armhf (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/armhf (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• binoculars/i386 (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/i386 (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• binoculars/mips64el (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/mips64el (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• binoculars/mipsel (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/mipsel (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• binoculars/ppc64el (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/ppc64el (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• binoculars/s390x (0.0.4-1 to 0.0.4-1)
  • Migration status for binoculars/s390x (0.0.4-1 to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• cairo-ocaml/amd64 (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/amd64 (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• cairo-ocaml/arm64 (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/arm64 (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• cairo-ocaml/armel (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/armel (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• cairo-ocaml/armhf (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/armhf (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• cairo-ocaml/i386 (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/i386 (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• cairo-ocaml/mips64el (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/mips64el (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• cairo-ocaml/mipsel (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/mipsel (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• cairo-ocaml/ppc64el (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/ppc64el (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• cairo-ocaml/s390x (1:1.2.0-8 to 1:1.2.0-8)
  • Migration status for cairo-ocaml/s390x (1:1.2.0-8 to 1:1.2.0-8): Will attempt migration (Any information below is purely informational)
• calendar/amd64 (2.04-3 to 2.04-3)
  • Migration status for calendar/amd64 (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• calendar/arm64 (2.04-3 to 2.04-3)
  • Migration status for calendar/arm64 (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• calendar/armel (2.04-3 to 2.04-3)
  • Migration status for calendar/armel (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• calendar/armhf (2.04-3 to 2.04-3)
  • Migration status for calendar/armhf (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• calendar/i386 (2.04-3 to 2.04-3)
  • Migration status for calendar/i386 (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• calendar/mips64el (2.04-3 to 2.04-3)
  • Migration status for calendar/mips64el (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• calendar/mipsel (2.04-3 to 2.04-3)
  • Migration status for calendar/mipsel (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• calendar/ppc64el (2.04-3 to 2.04-3)
  • Migration status for calendar/ppc64el (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• calendar/s390x (2.04-3 to 2.04-3)
  • Migration status for calendar/s390x (2.04-3 to 2.04-3): Will attempt migration (Any information below is purely informational)
• caml2html/amd64 (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/amd64 (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• caml2html/arm64 (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/arm64 (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• caml2html/armel (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/armel (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• caml2html/armhf (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/armhf (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• caml2html/i386 (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/i386 (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• caml2html/mips64el (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/mips64el (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• caml2html/mipsel (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/mipsel (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• caml2html/ppc64el (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/ppc64el (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• caml2html/s390x (1.4.4-2 to 1.4.4-2)
  • Migration status for caml2html/s390x (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• camlbz2/amd64 (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/amd64 (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlbz2/arm64 (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/arm64 (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlbz2/armel (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/armel (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlbz2/armhf (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/armhf (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlbz2/i386 (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/i386 (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlbz2/mips64el (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/mips64el (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlbz2/mipsel (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/mipsel (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlbz2/ppc64el (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/ppc64el (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlbz2/s390x (0.6.0-10 to 0.6.0-10)
  • Migration status for camlbz2/s390x (0.6.0-10 to 0.6.0-10): Will attempt migration (Any information below is purely informational)
• camlidl/amd64 (1.05-16 to 1.05-16)
  • Migration status for camlidl/amd64 (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlidl/arm64 (1.05-16 to 1.05-16)
  • Migration status for camlidl/arm64 (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlidl/armel (1.05-16 to 1.05-16)
  • Migration status for camlidl/armel (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlidl/armhf (1.05-16 to 1.05-16)
  • Migration status for camlidl/armhf (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlidl/i386 (1.05-16 to 1.05-16)
  • Migration status for camlidl/i386 (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlidl/mips64el (1.05-16 to 1.05-16)
  • Migration status for camlidl/mips64el (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlidl/mipsel (1.05-16 to 1.05-16)
  • Migration status for camlidl/mipsel (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlidl/ppc64el (1.05-16 to 1.05-16)
  • Migration status for camlidl/ppc64el (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlidl/s390x (1.05-16 to 1.05-16)
  • Migration status for camlidl/s390x (1.05-16 to 1.05-16): Will attempt migration (Any information below is purely informational)
• camlimages/amd64 (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/amd64 (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camlimages/arm64 (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/arm64 (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camlimages/armel (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/armel (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camlimages/armhf (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/armhf (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camlimages/i386 (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/i386 (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camlimages/mips64el (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/mips64el (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camlimages/mipsel (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/mipsel (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camlimages/ppc64el (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/ppc64el (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camlimages/s390x (1:4.2.6-5 to 1:4.2.6-5)
  • Migration status for camlimages/s390x (1:4.2.6-5 to 1:4.2.6-5): Will attempt migration (Any information below is purely informational)
• camljava/amd64 (0.3-2 to 0.3-2)
  • Migration status for camljava/amd64 (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camljava/arm64 (0.3-2 to 0.3-2)
  • Migration status for camljava/arm64 (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camljava/armel (0.3-2 to 0.3-2)
  • Migration status for camljava/armel (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camljava/armhf (0.3-2 to 0.3-2)
  • Migration status for camljava/armhf (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camljava/i386 (0.3-2 to 0.3-2)
  • Migration status for camljava/i386 (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camljava/mips64el (0.3-2 to 0.3-2)
  • Migration status for camljava/mips64el (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camljava/mipsel (0.3-2 to 0.3-2)
  • Migration status for camljava/mipsel (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camljava/ppc64el (0.3-2 to 0.3-2)
  • Migration status for camljava/ppc64el (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camljava/s390x (0.3-2 to 0.3-2)
  • Migration status for camljava/s390x (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• camlmix/armel (1.3.1-3 to 1.3.1-3)
  • Migration status for camlmix/armel (1.3.1-3 to 1.3.1-3): Will attempt migration (Any information below is purely informational)
• camlmix/mips64el (1.3.1-3 to 1.3.1-3)
  • Migration status for camlmix/mips64el (1.3.1-3 to 1.3.1-3): Will attempt migration (Any information below is purely informational)
• camlmix/mipsel (1.3.1-3 to 1.3.1-3)
  • Migration status for camlmix/mipsel (1.3.1-3 to 1.3.1-3): Will attempt migration (Any information below is purely informational)
• camlp5/amd64 (7.08-2 to 7.08-2)
  • Migration status for camlp5/amd64 (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camlp5/arm64 (7.08-2 to 7.08-2)
  • Migration status for camlp5/arm64 (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camlp5/armel (7.08-2 to 7.08-2)
  • Migration status for camlp5/armel (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camlp5/armhf (7.08-2 to 7.08-2)
  • Migration status for camlp5/armhf (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camlp5/i386 (7.08-2 to 7.08-2)
  • Migration status for camlp5/i386 (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camlp5/mips64el (7.08-2 to 7.08-2)
  • Migration status for camlp5/mips64el (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camlp5/mipsel (7.08-2 to 7.08-2)
  • Migration status for camlp5/mipsel (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camlp5/ppc64el (7.08-2 to 7.08-2)
  • Migration status for camlp5/ppc64el (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camlp5/s390x (7.08-2 to 7.08-2)
  • Migration status for camlp5/s390x (7.08-2 to 7.08-2): Will attempt migration (Any information below is purely informational)
• camltemplate/amd64 (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/amd64 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camltemplate/arm64 (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/arm64 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camltemplate/armel (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/armel (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camltemplate/armhf (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/armhf (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camltemplate/i386 (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/i386 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camltemplate/mips64el (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/mips64el (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camltemplate/mipsel (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/mipsel (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camltemplate/ppc64el (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/ppc64el (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camltemplate/s390x (1.0.2-3 to 1.0.2-3)
  • Migration status for camltemplate/s390x (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• camomile/amd64 (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/amd64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• camomile/arm64 (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/arm64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• camomile/armel (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/armel (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• camomile/armhf (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/armhf (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• camomile/i386 (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/i386 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• camomile/mips64el (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/mips64el (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• camomile/mipsel (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/mipsel (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• camomile/ppc64el (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/ppc64el (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• camomile/s390x (1.0.2-2 to 1.0.2-2)
  • Migration status for camomile/s390x (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• cmdliner/amd64 (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/amd64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cmdliner/arm64 (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/arm64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cmdliner/armel (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/armel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cmdliner/armhf (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/armhf (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cmdliner/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cmdliner/mips64el (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/mips64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cmdliner/mipsel (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/mipsel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cmdliner/ppc64el (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/ppc64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cmdliner/s390x (1.0.4-1 to 1.0.4-1)
  • Migration status for cmdliner/s390x (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• cothreads/amd64 (0.10-5 to 0.10-5)
  • Migration status for cothreads/amd64 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cothreads/arm64 (0.10-5 to 0.10-5)
  • Migration status for cothreads/arm64 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cothreads/armel (0.10-5 to 0.10-5)
  • Migration status for cothreads/armel (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cothreads/armhf (0.10-5 to 0.10-5)
  • Migration status for cothreads/armhf (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cothreads/i386 (0.10-5 to 0.10-5)
  • Migration status for cothreads/i386 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cothreads/mips64el (0.10-5 to 0.10-5)
  • Migration status for cothreads/mips64el (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cothreads/mipsel (0.10-5 to 0.10-5)
  • Migration status for cothreads/mipsel (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cothreads/ppc64el (0.10-5 to 0.10-5)
  • Migration status for cothreads/ppc64el (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cothreads/s390x (0.10-5 to 0.10-5)
  • Migration status for cothreads/s390x (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• cppo/amd64 (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/amd64 (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• cppo/arm64 (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/arm64 (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• cppo/armel (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/armel (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• cppo/armhf (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/armhf (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• cppo/i386 (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/i386 (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• cppo/mips64el (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/mips64el (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• cppo/mipsel (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/mipsel (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• cppo/ppc64el (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/ppc64el (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• cppo/s390x (1.6.6-1 to 1.6.6-1)
  • Migration status for cppo/s390x (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• crac/arm64 (2.5.2+dfsg-2 to 2.5.2+dfsg-2)
  • Migration status for crac/arm64 (2.5.2+dfsg-2 to 2.5.2+dfsg-2): Will attempt migration (Any information below is purely informational)
• crac/mips64el (2.5.2+dfsg-2 to 2.5.2+dfsg-2)
  • Migration status for crac/mips64el (2.5.2+dfsg-2 to 2.5.2+dfsg-2): Will attempt migration (Any information below is purely informational)
• crac/ppc64el (2.5.2+dfsg-2 to 2.5.2+dfsg-2)
  • Migration status for crac/ppc64el (2.5.2+dfsg-2 to 2.5.2+dfsg-2): Will attempt migration (Any information below is purely informational)
• cryptgps/amd64 (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/amd64 (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptgps/arm64 (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/arm64 (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptgps/armel (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/armel (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptgps/armhf (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/armhf (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptgps/i386 (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/i386 (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptgps/mips64el (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/mips64el (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptgps/mipsel (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/mipsel (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptgps/ppc64el (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/ppc64el (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptgps/s390x (0.2.1-11 to 0.2.1-11)
  • Migration status for cryptgps/s390x (0.2.1-11 to 0.2.1-11): Will attempt migration (Any information below is purely informational)
• cryptokit/amd64 (1.13-2 to 1.13-2)
  • Migration status for cryptokit/amd64 (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cryptokit/arm64 (1.13-2 to 1.13-2)
  • Migration status for cryptokit/arm64 (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cryptokit/armel (1.13-2 to 1.13-2)
  • Migration status for cryptokit/armel (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cryptokit/armhf (1.13-2 to 1.13-2)
  • Migration status for cryptokit/armhf (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cryptokit/i386 (1.13-2 to 1.13-2)
  • Migration status for cryptokit/i386 (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cryptokit/mips64el (1.13-2 to 1.13-2)
  • Migration status for cryptokit/mips64el (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cryptokit/mipsel (1.13-2 to 1.13-2)
  • Migration status for cryptokit/mipsel (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cryptokit/ppc64el (1.13-2 to 1.13-2)
  • Migration status for cryptokit/ppc64el (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cryptokit/s390x (1.13-2 to 1.13-2)
  • Migration status for cryptokit/s390x (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• cudf/amd64 (0.7-5 to 0.7-5)
  • Migration status for cudf/amd64 (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• cudf/arm64 (0.7-5 to 0.7-5)
  • Migration status for cudf/arm64 (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• cudf/armel (0.7-5 to 0.7-5)
  • Migration status for cudf/armel (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• cudf/armhf (0.7-5 to 0.7-5)
  • Migration status for cudf/armhf (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• cudf/i386 (0.7-5 to 0.7-5)
  • Migration status for cudf/i386 (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• cudf/mips64el (0.7-5 to 0.7-5)
  • Migration status for cudf/mips64el (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• cudf/mipsel (0.7-5 to 0.7-5)
  • Migration status for cudf/mipsel (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• cudf/ppc64el (0.7-5 to 0.7-5)
  • Migration status for cudf/ppc64el (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• cudf/s390x (0.7-5 to 0.7-5)
  • Migration status for cudf/s390x (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• diet-ng/armhf (1.5.0-1 to 1.5.0-1)
  • Migration status for diet-ng/armhf (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Impossible Depends: diet-ng/armhf -> ldc/armhf
• dochelp/armel (0.1.7 to 0.1.7)
  • Migration status for dochelp/armel (0.1.7 to 0.1.7): Will attempt migration (Any information below is purely informational)
• dochelp/mips64el (0.1.7 to 0.1.7)
  • Migration status for dochelp/mips64el (0.1.7 to 0.1.7): Will attempt migration (Any information below is purely informational)
• dochelp/mipsel (0.1.7 to 0.1.7)
  • Migration status for dochelp/mipsel (0.1.7 to 0.1.7): Will attempt migration (Any information below is purely informational)
• dose3/amd64 (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/amd64 (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• dose3/arm64 (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/arm64 (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• dose3/armel (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/armel (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• dose3/armhf (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/armhf (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• dose3/i386 (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/i386 (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• dose3/mips64el (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/mips64el (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• dose3/mipsel (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/mipsel (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• dose3/ppc64el (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/ppc64el (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• dose3/s390x (5.0.1-14 to 5.0.1-14)
  • Migration status for dose3/s390x (5.0.1-14 to 5.0.1-14): Will attempt migration (Any information below is purely informational)
• easy-format/amd64 (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/amd64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• easy-format/arm64 (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/arm64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• easy-format/armel (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/armel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• easy-format/armhf (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/armhf (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• easy-format/i386 (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/i386 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• easy-format/mips64el (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/mips64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• easy-format/mipsel (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/mipsel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• easy-format/ppc64el (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/ppc64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• easy-format/s390x (1.2.0-1 to 1.2.0-1)
  • Migration status for easy-format/s390x (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• extlib/amd64 (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/amd64 (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• extlib/arm64 (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/arm64 (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• extlib/armel (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/armel (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• extlib/armhf (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/armhf (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• extlib/i386 (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/i386 (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• extlib/mips64el (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/mips64el (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• extlib/mipsel (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/mipsel (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• extlib/ppc64el (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/ppc64el (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• extlib/s390x (1.7.6-1 to 1.7.6-1)
  • Migration status for extlib/s390x (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• facile/amd64 (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/amd64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• facile/arm64 (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/arm64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• facile/armel (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/armel (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• facile/armhf (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/armhf (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• facile/i386 (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/i386 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• facile/mips64el (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/mips64el (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• facile/mipsel (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/mipsel (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• facile/ppc64el (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/ppc64el (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• facile/s390x (1.1.1-1 to 1.1.1-1)
  • Migration status for facile/s390x (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• fieldslib/amd64 (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/amd64 (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• fieldslib/arm64 (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/arm64 (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• fieldslib/armel (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/armel (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• fieldslib/armhf (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/armhf (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• fieldslib/i386 (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/i386 (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• fieldslib/mips64el (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/mips64el (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• fieldslib/mipsel (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/mipsel (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• fieldslib/ppc64el (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/ppc64el (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• fieldslib/s390x (113.33.03-2 to 113.33.03-2)
  • Migration status for fieldslib/s390x (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• findlib/amd64 (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/amd64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• findlib/arm64 (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/arm64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• findlib/armel (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/armel (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• findlib/armhf (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/armhf (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• findlib/i386 (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/i386 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• findlib/mips64el (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/mips64el (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• findlib/mipsel (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/mipsel (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• findlib/ppc64el (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/ppc64el (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• findlib/s390x (1.8.1-1 to 1.8.1-1)
  • Migration status for findlib/s390x (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• freetennis/armel (0.4.8-11 to 0.4.8-11)
  • Migration status for freetennis/armel (0.4.8-11 to 0.4.8-11): Will attempt migration (Any information below is purely informational)
• freetennis/mips64el (0.4.8-11 to 0.4.8-11)
  • Migration status for freetennis/mips64el (0.4.8-11 to 0.4.8-11): Will attempt migration (Any information below is purely informational)
• freetennis/mipsel (0.4.8-11 to 0.4.8-11)
  • Migration status for freetennis/mipsel (0.4.8-11 to 0.4.8-11): Will attempt migration (Any information below is purely informational)
• gd4o/amd64 (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/amd64 (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gd4o/arm64 (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/arm64 (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gd4o/armel (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/armel (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gd4o/armhf (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/armhf (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gd4o/i386 (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/i386 (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gd4o/mips64el (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/mips64el (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gd4o/mipsel (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/mipsel (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gd4o/ppc64el (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/ppc64el (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gd4o/s390x (1.0~alpha5-9 to 1.0~alpha5-9)
  • Migration status for gd4o/s390x (1.0~alpha5-9 to 1.0~alpha5-9): Will attempt migration (Any information below is purely informational)
• gmetadom/amd64 (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/amd64 (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• gmetadom/arm64 (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/arm64 (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• gmetadom/armel (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/armel (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• gmetadom/armhf (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/armhf (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• gmetadom/i386 (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/i386 (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• gmetadom/mips64el (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/mips64el (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• gmetadom/mipsel (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/mipsel (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• gmetadom/ppc64el (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/ppc64el (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• gmetadom/s390x (0.2.6-7 to 0.2.6-7)
  • Migration status for gmetadom/s390x (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• headache/amd64 (1.03-30 to 1.03-30)
  • Migration status for headache/amd64 (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• headache/arm64 (1.03-30 to 1.03-30)
  • Migration status for headache/arm64 (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• headache/armel (1.03-30 to 1.03-30)
  • Migration status for headache/armel (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• headache/armhf (1.03-30 to 1.03-30)
  • Migration status for headache/armhf (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• headache/i386 (1.03-30 to 1.03-30)
  • Migration status for headache/i386 (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• headache/mips64el (1.03-30 to 1.03-30)
  • Migration status for headache/mips64el (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• headache/mipsel (1.03-30 to 1.03-30)
  • Migration status for headache/mipsel (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• headache/ppc64el (1.03-30 to 1.03-30)
  • Migration status for headache/ppc64el (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• headache/s390x (1.03-30 to 1.03-30)
  • Migration status for headache/s390x (1.03-30 to 1.03-30): Will attempt migration (Any information below is purely informational)
• hfsutils/amd64 (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/amd64 (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• hfsutils/arm64 (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/arm64 (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• hfsutils/armel (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/armel (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• hfsutils/armhf (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/armhf (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• hfsutils/i386 (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/i386 (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• hfsutils/mips64el (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/mips64el (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• hfsutils/mipsel (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/mipsel (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• hfsutils/ppc64el (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/ppc64el (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• hfsutils/s390x (3.2.6-14 to 3.2.6-14)
  • Migration status for hfsutils/s390x (3.2.6-14 to 3.2.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• janest-base/amd64 (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/amd64 (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-base/arm64 (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/arm64 (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-base/armel (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/armel (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-base/armhf (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/armhf (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-base/i386 (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/i386 (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-base/mips64el (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/mips64el (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-base/mipsel (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/mipsel (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-base/ppc64el (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/ppc64el (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-base/s390x (0.12.2-2 to 0.12.2-2)
  • Migration status for janest-base/s390x (0.12.2-2 to 0.12.2-2): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/amd64 (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/amd64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/arm64 (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/arm64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/armel (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/armel (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/armhf (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/armhf (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/i386 (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/i386 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/mips64el (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/mips64el (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/mipsel (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/mipsel (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/ppc64el (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/ppc64el (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/s390x (0.12.0-1 to 0.12.0-1)
  • Migration status for janest-ocaml-compiler-libs/s390x (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• js-build-tools/amd64 (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/amd64 (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• js-build-tools/arm64 (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/arm64 (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• js-build-tools/armel (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/armel (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• js-build-tools/armhf (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/armhf (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• js-build-tools/i386 (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/i386 (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• js-build-tools/mips64el (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/mips64el (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• js-build-tools/mipsel (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/mipsel (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• js-build-tools/ppc64el (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/ppc64el (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• js-build-tools/s390x (113.33.04-2 to 113.33.04-2)
  • Migration status for js-build-tools/s390x (113.33.04-2 to 113.33.04-2): Will attempt migration (Any information below is purely informational)
• jsonm/amd64 (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/amd64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• jsonm/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/arm64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• jsonm/armel (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/armel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• jsonm/armhf (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/armhf (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• jsonm/i386 (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/i386 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• jsonm/mips64el (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/mips64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• jsonm/mipsel (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/mipsel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• jsonm/ppc64el (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/ppc64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• jsonm/s390x (1.0.1-2 to 1.0.1-2)
  • Migration status for jsonm/s390x (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• kio-gdrive/amd64 (1.2.7-1 to 1.2.7-1)
  • Migration status for kio-gdrive/amd64 (1.2.7-1 to 1.2.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kio-gdrive/amd64 libkgapi (not considered)
• kio-gdrive/arm64 (1.2.7-1 to 1.2.7-1)
  • Migration status for kio-gdrive/arm64 (1.2.7-1 to 1.2.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kio-gdrive/arm64 libkgapi (not considered)
• kio-gdrive/armhf (1.2.7-1 to 1.2.7-1)
  • Migration status for kio-gdrive/armhf (1.2.7-1 to 1.2.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kio-gdrive/armhf libkgapi (not considered)
• kio-gdrive/i386 (1.2.7-1 to 1.2.7-1)
  • Migration status for kio-gdrive/i386 (1.2.7-1 to 1.2.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kio-gdrive/i386 libkgapi (not considered)
• kio-gdrive/mipsel (1.2.7-1 to 1.2.7-1)
  • Migration status for kio-gdrive/mipsel (1.2.7-1 to 1.2.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kio-gdrive/mipsel libkgapi (not considered)
• kjots/amd64 (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/amd64 (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/amd64 kontactinterface (not considered)
• kjots/arm64 (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/arm64 (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/arm64 kontactinterface (not considered)
• kjots/armel (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/armel (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/armel kontactinterface (not considered)
• kjots/armhf (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/armhf (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/armhf kontactinterface (not considered)
• kjots/i386 (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/i386 (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/i386 kontactinterface (not considered)
• kjots/mips64el (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/mips64el (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/mips64el kontactinterface (not considered)
• kjots/mipsel (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/mipsel (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/mipsel kontactinterface (not considered)
• kjots/ppc64el (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/ppc64el (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/ppc64el kontactinterface (not considered)
• kjots/s390x (4:5.0.2-1 to 4:5.0.2-1)
  • Migration status for kjots/s390x (4:5.0.2-1 to 4:5.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kjots/s390x kontactinterface (not considered)
• kmymoney/amd64 (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/amd64 (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/amd64 kcontacts (not considered)
• kmymoney/arm64 (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/arm64 (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/arm64 kcontacts (not considered)
• kmymoney/armel (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/armel (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/armel kcontacts (not considered)
• kmymoney/armhf (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/armhf (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/armhf kcontacts (not considered)
• kmymoney/i386 (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/i386 (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/i386 kcontacts (not considered)
• kmymoney/mips64el (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/mips64el (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/mips64el kcontacts (not considered)
• kmymoney/mipsel (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/mipsel (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/mipsel kcontacts (not considered)
• kmymoney/ppc64el (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/ppc64el (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/ppc64el kcontacts (not considered)
• kmymoney/s390x (5.0.7-1 to 5.0.7-1)
  • Migration status for kmymoney/s390x (5.0.7-1 to 5.0.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kmymoney/s390x kcontacts (not considered)
• kraft/amd64 (0.82-1 to 0.82-1)
  • Migration status for kraft/amd64 (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/amd64 kcontacts (not considered)
• kraft/arm64 (0.82-1 to 0.82-1)
  • Migration status for kraft/arm64 (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/arm64 kcontacts (not considered)
• kraft/armel (0.82-1 to 0.82-1)
  • Migration status for kraft/armel (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/armel kcontacts (not considered)
• kraft/armhf (0.82-1 to 0.82-1)
  • Migration status for kraft/armhf (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/armhf kcontacts (not considered)
• kraft/i386 (0.82-1 to 0.82-1)
  • Migration status for kraft/i386 (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/i386 kcontacts (not considered)
• kraft/mips64el (0.82-1 to 0.82-1)
  • Migration status for kraft/mips64el (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/mips64el kcontacts (not considered)
• kraft/mipsel (0.82-1 to 0.82-1)
  • Migration status for kraft/mipsel (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/mipsel kcontacts (not considered)
• kraft/ppc64el (0.82-1 to 0.82-1)
  • Migration status for kraft/ppc64el (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/ppc64el kcontacts (not considered)
• kraft/s390x (0.82-1 to 0.82-1)
  • Migration status for kraft/s390x (0.82-1 to 0.82-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: kraft/s390x kcontacts (not considered)
• lablgl/amd64 (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/amd64 (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgl/arm64 (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/arm64 (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgl/armel (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/armel (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgl/armhf (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/armhf (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgl/i386 (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/i386 (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgl/mips64el (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/mips64el (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgl/mipsel (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/mipsel (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgl/ppc64el (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/ppc64el (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgl/s390x (1:1.06-1 to 1:1.06-1)
  • Migration status for lablgl/s390x (1:1.06-1 to 1:1.06-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/amd64 (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/amd64 (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/arm64 (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/arm64 (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/armel (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/armel (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/armhf (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/armhf (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/i386 (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/i386 (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/mips64el (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/mips64el (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/mipsel (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/mipsel (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/ppc64el (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/ppc64el (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk2/s390x (2.18.8+dfsg-1 to 2.18.8+dfsg-1)
  • Migration status for lablgtk2/s390x (2.18.8+dfsg-1 to 2.18.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• lablgtk3/amd64 (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/amd64 (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtk3/arm64 (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/arm64 (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtk3/armel (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/armel (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtk3/armhf (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/armhf (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtk3/i386 (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/i386 (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtk3/mips64el (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/mips64el (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtk3/mipsel (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/mipsel (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtk3/ppc64el (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/ppc64el (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtk3/s390x (3.0~beta6-2 to 3.0~beta6-2)
  • Migration status for lablgtk3/s390x (3.0~beta6-2 to 3.0~beta6-2): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/amd64 (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/amd64 (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/arm64 (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/arm64 (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/armel (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/armel (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/armhf (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/armhf (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/i386 (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/i386 (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/mips64el (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/mips64el (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/mipsel (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/mipsel (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/ppc64el (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/ppc64el (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• lablgtkmathview/s390x (0.7.8-7 to 0.7.8-7)
  • Migration status for lablgtkmathview/s390x (0.7.8-7 to 0.7.8-7): Will attempt migration (Any information below is purely informational)
• laby/armel (0.6.4-3 to 0.6.4-3)
  • Migration status for laby/armel (0.6.4-3 to 0.6.4-3): Will attempt migration (Any information below is purely informational)
• laby/mips64el (0.6.4-3 to 0.6.4-3)
  • Migration status for laby/mips64el (0.6.4-3 to 0.6.4-3): Will attempt migration (Any information below is purely informational)
• laby/mipsel (0.6.4-3 to 0.6.4-3)
  • Migration status for laby/mipsel (0.6.4-3 to 0.6.4-3): Will attempt migration (Any information below is purely informational)
• libguestfs/amd64 (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/amd64 (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libguestfs/arm64 (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/arm64 (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libguestfs/armel (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/armel (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libguestfs/armhf (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/armhf (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libguestfs/i386 (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/i386 (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libguestfs/mips64el (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/mips64el (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libguestfs/mipsel (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/mipsel (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libguestfs/ppc64el (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/ppc64el (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libguestfs/s390x (1:1.40.2-2 to 1:1.40.2-2)
  • Migration status for libguestfs/s390x (1:1.40.2-2 to 1:1.40.2-2): Will attempt migration (Any information below is purely informational)
• libnbd/amd64 (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/amd64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libnbd/arm64 (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/arm64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libnbd/armel (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/armel (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libnbd/armhf (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/armhf (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libnbd/i386 (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/i386 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libnbd/mips64el (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/mips64el (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libnbd/mipsel (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/mipsel (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libnbd/ppc64el (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/ppc64el (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libnbd/s390x (1.0.3-1 to 1.0.3-1)
  • Migration status for libnbd/s390x (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• libvcflib/ppc64el (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for libvcflib/ppc64el (1.0.0+dfsg-2 to 1.0.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: libvcflib/ppc64el libssw (not considered)
• llvm-toolchain-7/amd64 (1:7.0.1-9 to 1:7.0.1-9)
  • Migration status for llvm-toolchain-7/amd64 (1:7.0.1-9 to 1:7.0.1-9): Will attempt migration (Any information below is purely informational)
• llvm-toolchain-7/arm64 (1:7.0.1-9 to 1:7.0.1-9)
  • Migration status for llvm-toolchain-7/arm64 (1:7.0.1-9 to 1:7.0.1-9): Will attempt migration (Any information below is purely informational)
• llvm-toolchain-7/armhf (1:7.0.1-9 to 1:7.0.1-9)
  • Migration status for llvm-toolchain-7/armhf (1:7.0.1-9 to 1:7.0.1-9): Will attempt migration (Any information below is purely informational)
• llvm-toolchain-7/i386 (1:7.0.1-9 to 1:7.0.1-9)
  • Migration status for llvm-toolchain-7/i386 (1:7.0.1-9 to 1:7.0.1-9): Will attempt migration (Any information below is purely informational)
• llvm-toolchain-7/ppc64el (1:7.0.1-9 to 1:7.0.1-9)
  • Migration status for llvm-toolchain-7/ppc64el (1:7.0.1-9 to 1:7.0.1-9): Will attempt migration (Any information below is purely informational)
• llvm-toolchain-7/s390x (1:7.0.1-9 to 1:7.0.1-9)
  • Migration status for llvm-toolchain-7/s390x (1:7.0.1-9 to 1:7.0.1-9): Will attempt migration (Any information below is purely informational)
• mikmatch/amd64 (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/amd64 (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• mikmatch/arm64 (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/arm64 (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• mikmatch/armel (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/armel (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• mikmatch/armhf (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/armhf (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• mikmatch/i386 (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/i386 (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• mikmatch/mips64el (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/mips64el (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• mikmatch/mipsel (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/mipsel (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• mikmatch/ppc64el (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/ppc64el (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• mikmatch/s390x (1.0.8-2 to 1.0.8-2)
  • Migration status for mikmatch/s390x (1.0.8-2 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
• misery/armel (0.2-1.1 to 0.2-1.1)
  • Migration status for misery/armel (0.2-1.1 to 0.2-1.1): Will attempt migration (Any information below is purely informational)
• misery/mips64el (0.2-1.1 to 0.2-1.1)
  • Migration status for misery/mips64el (0.2-1.1 to 0.2-1.1): Will attempt migration (Any information below is purely informational)
• misery/mipsel (0.2-1.1 to 0.2-1.1)
  • Migration status for misery/mipsel (0.2-1.1 to 0.2-1.1): Will attempt migration (Any information below is purely informational)
• mlgmp/amd64 (20021123-20 to 20021123-20)
  • Migration status for mlgmp/amd64 (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlgmp/arm64 (20021123-20 to 20021123-20)
  • Migration status for mlgmp/arm64 (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlgmp/armel (20021123-20 to 20021123-20)
  • Migration status for mlgmp/armel (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlgmp/armhf (20021123-20 to 20021123-20)
  • Migration status for mlgmp/armhf (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlgmp/i386 (20021123-20 to 20021123-20)
  • Migration status for mlgmp/i386 (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlgmp/mips64el (20021123-20 to 20021123-20)
  • Migration status for mlgmp/mips64el (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlgmp/mipsel (20021123-20 to 20021123-20)
  • Migration status for mlgmp/mipsel (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlgmp/ppc64el (20021123-20 to 20021123-20)
  • Migration status for mlgmp/ppc64el (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlgmp/s390x (20021123-20 to 20021123-20)
  • Migration status for mlgmp/s390x (20021123-20 to 20021123-20): Will attempt migration (Any information below is purely informational)
• mlpcap/amd64 (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/amd64 (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mlpcap/arm64 (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/arm64 (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mlpcap/armel (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/armel (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mlpcap/armhf (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/armhf (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mlpcap/i386 (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/i386 (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mlpcap/mips64el (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/mips64el (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mlpcap/mipsel (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/mipsel (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mlpcap/ppc64el (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/ppc64el (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mlpcap/s390x (0.9-17.1 to 0.9-17.1)
  • Migration status for mlpcap/s390x (0.9-17.1 to 0.9-17.1): Will attempt migration (Any information below is purely informational)
• mod-gnutls/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/amd64 (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mod-gnutls/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/arm64 (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mod-gnutls/armel (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/armel (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mod-gnutls/armhf (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/armhf (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mod-gnutls/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/i386 (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mod-gnutls/mips64el (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/mips64el (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mod-gnutls/mipsel (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/mipsel (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mod-gnutls/ppc64el (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/ppc64el (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mod-gnutls/s390x (0.9.0-1 to 0.9.0-1)
  • Migration status for mod-gnutls/s390x (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• mysql-ocaml/amd64 (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/amd64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/arm64 (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/arm64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/armel (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/armel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/armhf (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/armhf (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/i386 (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/i386 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/mips64el (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/mips64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/mipsel (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/mipsel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/ppc64el (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/ppc64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/s390x (1.2.1-1 to 1.2.1-1)
  • Migration status for mysql-ocaml/s390x (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• mz/amd64 (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/amd64 (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/amd64 libcli (not considered)
• mz/arm64 (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/arm64 (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/arm64 libcli (not considered)
• mz/armel (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/armel (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/armel libcli (not considered)
• mz/armhf (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/armhf (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/armhf libcli (not considered)
• mz/i386 (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/i386 (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/i386 libcli (not considered)
• mz/mips64el (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/mips64el (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/mips64el libcli (not considered)
• mz/mipsel (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/mipsel (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/mipsel libcli (not considered)
• mz/ppc64el (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/ppc64el (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/ppc64el libcli (not considered)
• mz/s390x (0.40-1.1 to 0.40-1.1)
  • Migration status for mz/s390x (0.40-1.1 to 0.40-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: mz/s390x libcli (not considered)
• netsniff-ng/amd64 (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/amd64 (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/amd64 libcli (not considered)
• netsniff-ng/arm64 (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/arm64 (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/arm64 libcli (not considered)
• netsniff-ng/armel (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/armel (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/armel libcli (not considered)
• netsniff-ng/armhf (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/armhf (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/armhf libcli (not considered)
• netsniff-ng/i386 (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/i386 (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/i386 libcli (not considered)
• netsniff-ng/mips64el (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/mips64el (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/mips64el libcli (not considered)
• netsniff-ng/mipsel (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/mipsel (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/mipsel libcli (not considered)
• netsniff-ng/ppc64el (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/ppc64el (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/ppc64el libcli (not considered)
• netsniff-ng/s390x (0.6.5-1 to 0.6.5-1)
  • Migration status for netsniff-ng/s390x (0.6.5-1 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: netsniff-ng/s390x libcli (not considered)
• nproc/amd64 (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/amd64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• nproc/arm64 (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/arm64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• nproc/armel (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/armel (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• nproc/armhf (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/armhf (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• nproc/i386 (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/i386 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• nproc/mips64el (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/mips64el (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• nproc/mipsel (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/mipsel (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• nproc/ppc64el (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/ppc64el (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• nproc/s390x (0.5.1-2 to 0.5.1-2)
  • Migration status for nproc/s390x (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• oasis/amd64 (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/amd64 (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• oasis/arm64 (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/arm64 (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• oasis/armel (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/armel (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• oasis/armhf (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/armhf (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• oasis/i386 (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/i386 (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• oasis/mips64el (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/mips64el (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• oasis/mipsel (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/mipsel (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• oasis/ppc64el (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/ppc64el (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• oasis/s390x (0.4.11-1 to 0.4.11-1)
  • Migration status for oasis/s390x (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/amd64 (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/amd64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/arm64 (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/arm64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/armel (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/armel (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/armhf (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/armhf (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/i386 (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/i386 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/mips64el (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/mips64el (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/mipsel (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/mipsel (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/ppc64el (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/ppc64el (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-alsa/s390x (0.2.3-1 to 0.2.3-1)
  • Migration status for ocaml-alsa/s390x (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-ao/amd64 (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/amd64 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ao/arm64 (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/arm64 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ao/armel (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/armel (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ao/armhf (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/armhf (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ao/i386 (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/i386 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ao/mips64el (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/mips64el (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ao/mipsel (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/mipsel (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ao/ppc64el (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/ppc64el (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ao/s390x (0.2.0-2 to 0.2.0-2)
  • Migration status for ocaml-ao/s390x (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-atd/amd64 (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/amd64 (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-atd/arm64 (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/arm64 (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-atd/armel (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/armel (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-atd/armhf (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/armhf (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-atd/i386 (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/i386 (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-atd/mips64el (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/mips64el (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-atd/mipsel (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/mipsel (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-atd/ppc64el (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/ppc64el (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-atd/s390x (2.0.0-3 to 2.0.0-3)
  • Migration status for ocaml-atd/s390x (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-base64/amd64 (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/amd64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-base64/arm64 (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/arm64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-base64/armel (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/armel (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-base64/armhf (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/armhf (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-base64/i386 (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/i386 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-base64/mips64el (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/mips64el (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-base64/mipsel (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/mipsel (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-base64/ppc64el (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/ppc64el (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-base64/s390x (2.0.0-2 to 2.0.0-2)
  • Migration status for ocaml-base64/s390x (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/amd64 (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/amd64 (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/arm64 (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/arm64 (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/armel (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/armel (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/armhf (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/armhf (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/i386 (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/i386 (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/mips64el (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/mips64el (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/mipsel (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/mipsel (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/ppc64el (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/ppc64el (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/s390x (1.3-3 to 1.3-3)
  • Migration status for ocaml-benchmark/s390x (1.3-3 to 1.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/amd64 (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/amd64 (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/arm64 (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/arm64 (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/armel (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/armel (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/armhf (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/armhf (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/i386 (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/i386 (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/mips64el (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/mips64el (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/mipsel (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/mipsel (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/ppc64el (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/ppc64el (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/s390x (2.0.4-4 to 2.0.4-4)
  • Migration status for ocaml-bitstring/s390x (2.0.4-4 to 2.0.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/amd64 (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/amd64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/arm64 (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/arm64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/armel (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/armel (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/armhf (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/armhf (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/i386 (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/i386 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/mips64el (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/mips64el (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/mipsel (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/mipsel (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/ppc64el (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/ppc64el (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/s390x (0.1.4-2 to 0.1.4-2)
  • Migration status for ocaml-bjack/s390x (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/amd64 (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/amd64 (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/arm64 (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/arm64 (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/armel (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/armel (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/armhf (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/armhf (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/i386 (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/i386 (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/mips64el (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/mips64el (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/mipsel (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/mipsel (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/ppc64el (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/ppc64el (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/s390x (0.6.1+dfsg-2 to 0.6.1+dfsg-2)
  • Migration status for ocaml-cairo2/s390x (0.6.1+dfsg-2 to 0.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/mipsel (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/mipsel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/ppc64el (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/ppc64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/s390x (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-charinfo-width/s390x (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/amd64 (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/amd64 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/arm64 (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/arm64 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/armel (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/armel (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/armhf (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/armhf (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/i386 (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/i386 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/mips64el (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/mips64el (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/mipsel (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/mipsel (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/ppc64el (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/ppc64el (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-config-file/s390x (1.2-1 to 1.2-1)
  • Migration status for ocaml-config-file/s390x (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/amd64 (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/amd64 (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/arm64 (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/arm64 (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/armel (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/armel (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/armhf (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/armhf (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/i386 (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/i386 (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/mips64el (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/mips64el (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/mipsel (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/mipsel (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/ppc64el (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/ppc64el (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/s390x (0.6.4-1 to 0.6.4-1)
  • Migration status for ocaml-cry/s390x (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/amd64 (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/amd64 (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/arm64 (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/arm64 (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/armel (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/armel (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/armhf (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/armhf (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/i386 (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/i386 (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/mips64el (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/mips64el (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/mipsel (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/mipsel (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/ppc64el (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/ppc64el (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-csv/s390x (2.2-1 to 2.2-1)
  • Migration status for ocaml-csv/s390x (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/amd64 (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/amd64 (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/arm64 (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/arm64 (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/armel (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/armel (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/armhf (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/armhf (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/i386 (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/i386 (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/mips64el (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/mips64el (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/mipsel (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/mipsel (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/ppc64el (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/ppc64el (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ctypes/s390x (0.15.1-1 to 0.15.1-1)
  • Migration status for ocaml-ctypes/s390x (0.15.1-1 to 0.15.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-curses/amd64 (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/amd64 (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/arm64 (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/arm64 (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/armel (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/armel (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/armhf (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/armhf (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/i386 (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/i386 (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/mips64el (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/mips64el (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/mipsel (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/mipsel (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/ppc64el (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/ppc64el (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/s390x (1.0.3-3 to 1.0.3-3)
  • Migration status for ocaml-curses/s390x (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/amd64 (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/amd64 (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/arm64 (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/arm64 (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/armel (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/armel (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/armhf (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/armhf (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/i386 (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/i386 (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/mips64el (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/mips64el (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/mipsel (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/mipsel (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/ppc64el (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/ppc64el (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/s390x (0.29-3 to 0.29-3)
  • Migration status for ocaml-dbus/s390x (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/amd64 (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/amd64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/arm64 (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/arm64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/armel (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/armel (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/armhf (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/armhf (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/i386 (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/i386 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/mips64el (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/mips64el (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/mipsel (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/mipsel (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/ppc64el (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/ppc64el (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/s390x (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-dssi/s390x (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/amd64 (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/amd64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/arm64 (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/arm64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/armel (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/armel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/armhf (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/armhf (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/i386 (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/i386 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/mips64el (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/mips64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/mipsel (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/mipsel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/ppc64el (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/ppc64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/s390x (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-dtools/s390x (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-dune/amd64 (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/amd64 (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-dune/arm64 (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/arm64 (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-dune/armel (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/armel (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-dune/armhf (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/armhf (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-dune/i386 (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/i386 (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-dune/mips64el (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/mips64el (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-dune/mipsel (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/mipsel (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-dune/ppc64el (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/ppc64el (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-dune/s390x (1.11.0-2 to 1.11.0-2)
  • Migration status for ocaml-dune/s390x (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/amd64 (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/amd64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/arm64 (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/arm64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/armel (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/armel (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/armhf (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/armhf (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/i386 (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/i386 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/mips64el (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/mips64el (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/mipsel (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/mipsel (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/ppc64el (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/ppc64el (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/s390x (0.8.0-1 to 0.8.0-1)
  • Migration status for ocaml-duppy/s390x (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-expat/amd64 (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/amd64 (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-expat/arm64 (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/arm64 (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-expat/armel (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/armel (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-expat/armhf (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/armhf (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-expat/i386 (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/i386 (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-expat/mips64el (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/mips64el (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-expat/mipsel (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/mipsel (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-expat/ppc64el (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/ppc64el (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-expat/s390x (0.9.1+debian1-7 to 0.9.1+debian1-7)
  • Migration status for ocaml-expat/s390x (0.9.1+debian1-7 to 0.9.1+debian1-7): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/amd64 (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/amd64 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/arm64 (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/arm64 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/armel (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/armel (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/armhf (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/armhf (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/i386 (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/i386 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/mips64el (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/mips64el (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/mipsel (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/mipsel (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/ppc64el (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/ppc64el (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-extunix/s390x (0.1.6-1 to 0.1.6-1)
  • Migration status for ocaml-extunix/s390x (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/amd64 (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/amd64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/armel (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/armel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/armhf (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/armhf (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/mips64el (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/mips64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/mipsel (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/mipsel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/ppc64el (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/ppc64el (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/s390x (0.4.0-1 to 0.4.0-1)
  • Migration status for ocaml-faad/s390x (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/amd64 (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/amd64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/arm64 (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/arm64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/armel (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/armel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/armhf (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/armhf (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/i386 (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/i386 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/mips64el (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/mips64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/mipsel (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/mipsel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/ppc64el (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/ppc64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/s390x (0.4.1-1 to 0.4.1-1)
  • Migration status for ocaml-ffmpeg/s390x (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/amd64 (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/amd64 (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/arm64 (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/arm64 (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/armel (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/armel (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/armhf (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/armhf (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/i386 (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/i386 (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/mips64el (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/mips64el (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/mipsel (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/mipsel (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/ppc64el (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/ppc64el (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/s390x (0.5.3-2 to 0.5.3-2)
  • Migration status for ocaml-fileutils/s390x (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/amd64 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/amd64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/arm64 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/arm64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/armel (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/armel (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/armhf (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/armhf (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/i386 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/i386 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/mips64el (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/mips64el (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/mipsel (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/mipsel (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/ppc64el (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/ppc64el (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-flac/s390x (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-flac/s390x (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/amd64 (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/amd64 (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/arm64 (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/arm64 (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/armel (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/armel (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/armhf (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/armhf (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/i386 (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/i386 (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/mips64el (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/mips64el (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/mipsel (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/mipsel (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/ppc64el (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/ppc64el (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/s390x (0.1.0-3 to 0.1.0-3)
  • Migration status for ocaml-frei0r/s390x (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/amd64 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/amd64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/arm64 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/arm64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/armel (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/armel (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/armhf (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/armhf (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/i386 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/i386 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/mips64el (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/mips64el (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/mipsel (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/mipsel (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/ppc64el (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/ppc64el (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-gavl/s390x (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-gavl/s390x (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/amd64 (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/amd64 (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/arm64 (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/arm64 (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/armel (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/armel (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/armhf (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/armhf (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/i386 (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/i386 (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/mips64el (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/mips64el (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/mipsel (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/mipsel (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/ppc64el (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/ppc64el (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/s390x (0.0.20040811-10 to 0.0.20040811-10)
  • Migration status for ocaml-getopt/s390x (0.0.20040811-10 to 0.0.20040811-10): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/amd64 (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/amd64 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/arm64 (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/arm64 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/armel (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/armel (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/armhf (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/armhf (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/i386 (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/i386 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/mips64el (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/mips64el (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/mipsel (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/mipsel (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/ppc64el (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/ppc64el (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gettext/s390x (0.4.1-2 to 0.4.1-2)
  • Migration status for ocaml-gettext/s390x (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/amd64 (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/amd64 (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/arm64 (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/arm64 (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/armel (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/armel (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/armhf (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/armhf (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/i386 (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/i386 (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/mips64el (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/mips64el (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/mipsel (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/mipsel (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/ppc64el (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/ppc64el (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/s390x (0.8.3-4 to 0.8.3-4)
  • Migration status for ocaml-gnuplot/s390x (0.8.3-4 to 0.8.3-4): Will attempt migration (Any information below is purely informational)
• ocaml-http/amd64 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/amd64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-http/arm64 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/arm64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-http/armel (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/armel (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-http/armhf (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/armhf (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-http/i386 (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/i386 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-http/mips64el (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/mips64el (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-http/mipsel (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/mipsel (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-http/ppc64el (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/ppc64el (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-http/s390x (0.1.5-2 to 0.1.5-2)
  • Migration status for ocaml-http/s390x (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/amd64 (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/amd64 (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/arm64 (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/arm64 (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/armel (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/armel (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/armhf (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/armhf (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/i386 (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/i386 (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/mips64el (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/mips64el (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/mipsel (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/mipsel (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/ppc64el (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/ppc64el (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/s390x (1.2-4 to 1.2-4)
  • Migration status for ocaml-inifiles/s390x (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/amd64 (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/amd64 (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/arm64 (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/arm64 (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/armel (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/armel (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/armhf (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/armhf (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/i386 (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/i386 (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/mips64el (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/mips64el (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/mipsel (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/mipsel (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/ppc64el (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/ppc64el (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/s390x (1.0-3 to 1.0-3)
  • Migration status for ocaml-inotify/s390x (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-integers/amd64 (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/amd64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/mipsel (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/mipsel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-integers/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/amd64 (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/amd64 (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/arm64 (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/arm64 (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/armel (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/armel (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/armhf (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/armhf (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/i386 (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/i386 (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/mips64el (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/mips64el (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/mipsel (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/mipsel (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/ppc64el (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/ppc64el (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/s390x (0.1.4-1.1 to 0.1.4-1.1)
  • Migration status for ocaml-ladspa/s390x (0.1.4-1.1 to 0.1.4-1.1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/amd64 (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/amd64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/arm64 (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/arm64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/armel (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/armel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/armhf (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/armhf (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/i386 (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/i386 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/mips64el (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/mips64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/mipsel (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/mipsel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/ppc64el (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/ppc64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lame/s390x (0.3.2-1 to 0.3.2-1)
  • Migration status for ocaml-lame/s390x (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/amd64 (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/amd64 (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/arm64 (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/arm64 (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/armel (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/armel (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/armhf (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/armhf (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/i386 (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/i386 (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/mips64el (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/mips64el (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/mipsel (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/mipsel (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/ppc64el (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/ppc64el (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/s390x (0.3.0-5 to 0.3.0-5)
  • Migration status for ocaml-lastfm/s390x (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/amd64 (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/amd64 (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/arm64 (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/arm64 (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/armel (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/armel (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/armhf (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/armhf (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/i386 (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/i386 (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/mips64el (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/mips64el (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/mipsel (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/mipsel (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/ppc64el (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/ppc64el (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-libvirt/s390x (0.6.1.5-1 to 0.6.1.5-1)
  • Migration status for ocaml-libvirt/s390x (0.6.1.5-1 to 0.6.1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-mad/amd64 (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/amd64 (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-mad/arm64 (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/arm64 (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-mad/armel (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/armel (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-mad/armhf (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/armhf (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-mad/i386 (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/i386 (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-mad/mips64el (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/mips64el (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-mad/mipsel (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/mipsel (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-mad/ppc64el (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/ppc64el (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-mad/s390x (0.4.4-2 to 0.4.4-2)
  • Migration status for ocaml-mad/s390x (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-magic/amd64 (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/amd64 (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-magic/arm64 (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/arm64 (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-magic/armel (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/armel (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-magic/armhf (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/armhf (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-magic/i386 (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/i386 (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-magic/mips64el (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/mips64el (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-magic/mipsel (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/mipsel (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-magic/ppc64el (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/ppc64el (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-magic/s390x (0.7.3-5 to 0.7.3-5)
  • Migration status for ocaml-magic/s390x (0.7.3-5 to 0.7.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/amd64 (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/amd64 (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/arm64 (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/arm64 (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/armel (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/armel (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/armhf (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/armhf (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/i386 (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/i386 (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/mips64el (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/mips64el (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/mipsel (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/mipsel (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/ppc64el (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/ppc64el (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/s390x (1.1+10-2 to 1.1+10-2)
  • Migration status for ocaml-mccs/s390x (1.1+10-2 to 1.1+10-2): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/amd64 (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/amd64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/arm64 (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/arm64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/armel (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/armel (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/armhf (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/armhf (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/i386 (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/i386 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/mips64el (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/mips64el (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/mipsel (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/mipsel (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/ppc64el (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/ppc64el (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-migrate-parsetree/s390x (1.4.0-1 to 1.4.0-1)
  • Migration status for ocaml-migrate-parsetree/s390x (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/mipsel (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/mipsel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/ppc64el (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/ppc64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/s390x (1.1.0-1 to 1.1.0-1)
  • Migration status for ocaml-mmap/s390x (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-obuild/armel (0.1.10-3 to 0.1.10-3)
  • Migration status for ocaml-obuild/armel (0.1.10-3 to 0.1.10-3): Will attempt migration (Any information below is purely informational)
• ocaml-obuild/mips64el (0.1.10-3 to 0.1.10-3)
  • Migration status for ocaml-obuild/mips64el (0.1.10-3 to 0.1.10-3): Will attempt migration (Any information below is purely informational)
• ocaml-obuild/mipsel (0.1.10-3 to 0.1.10-3)
  • Migration status for ocaml-obuild/mipsel (0.1.10-3 to 0.1.10-3): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/amd64 (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/amd64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/arm64 (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/arm64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/armel (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/armel (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/armhf (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/armhf (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/i386 (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/i386 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/mips64el (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/mips64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/mipsel (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/mipsel (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/ppc64el (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/ppc64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/s390x (0.5.2-1 to 0.5.2-1)
  • Migration status for ocaml-ogg/s390x (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/amd64 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/amd64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/arm64 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/arm64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/armel (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/armel (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/armhf (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/armhf (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/i386 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/i386 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/mips64el (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/mips64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/mipsel (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/mipsel (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/ppc64el (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/ppc64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-opus/s390x (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-opus/s390x (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/mipsel (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/mipsel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/s390x (0.2.1-1 to 0.2.1-1)
  • Migration status for ocaml-portaudio/s390x (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/amd64 (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/amd64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/armel (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/armel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/mips64el (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/mips64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/mipsel (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/mipsel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/ppc64el (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/ppc64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/s390x (0.1.2-1 to 0.1.2-1)
  • Migration status for ocaml-pulseaudio/s390x (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-re/amd64 (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/amd64 (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-re/arm64 (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/arm64 (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-re/armel (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/armel (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-re/armhf (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/armhf (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-re/i386 (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/i386 (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-re/mips64el (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/mips64el (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-re/mipsel (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/mipsel (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-re/ppc64el (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/ppc64el (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-re/s390x (1.7.3-2 to 1.7.3-2)
  • Migration status for ocaml-re/s390x (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• ocaml-reins/amd64 (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/amd64 (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-reins/arm64 (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/arm64 (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-reins/armel (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/armel (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-reins/armhf (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/armhf (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-reins/i386 (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/i386 (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-reins/mips64el (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/mips64el (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-reins/mipsel (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/mipsel (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-reins/ppc64el (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/ppc64el (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-reins/s390x (0.1a-9 to 0.1a-9)
  • Migration status for ocaml-reins/s390x (0.1a-9 to 0.1a-9): Will attempt migration (Any information below is purely informational)
• ocaml-result/amd64 (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/amd64 (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-result/arm64 (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/arm64 (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-result/armel (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/armel (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-result/armhf (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/armhf (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-result/i386 (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/i386 (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-result/mips64el (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/mips64el (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-result/mipsel (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/mipsel (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-result/ppc64el (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/ppc64el (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-result/s390x (1.4-2 to 1.4-2)
  • Migration status for ocaml-result/s390x (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/amd64 (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/amd64 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/arm64 (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/arm64 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/armel (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/armel (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/armhf (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/armhf (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/i386 (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/i386 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/mips64el (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/mips64el (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/mipsel (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/mipsel (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/ppc64el (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/ppc64el (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/s390x (0.1.2-2 to 0.1.2-2)
  • Migration status for ocaml-samplerate/s390x (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• ocaml-sha/amd64 (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/amd64 (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/arm64 (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/arm64 (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/armel (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/armel (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/armhf (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/armhf (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/i386 (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/i386 (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/mips64el (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/mips64el (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/mipsel (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/mipsel (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/ppc64el (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/ppc64el (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/s390x (1.11-1 to 1.11-1)
  • Migration status for ocaml-sha/s390x (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/amd64 (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/amd64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/arm64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/armel (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/armel (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/armhf (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/armhf (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/i386 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/mips64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/mipsel (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/mipsel (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/ppc64el (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shine/s390x (0.2.0-1 to 0.2.0-1)
  • Migration status for ocaml-shine/s390x (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/amd64 (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/amd64 (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/arm64 (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/arm64 (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/armel (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/armel (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/armhf (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/armhf (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/i386 (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/i386 (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/mips64el (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/mips64el (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/mipsel (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/mipsel (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/ppc64el (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/ppc64el (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-shout/s390x (0.2.7-1 to 0.2.7-1)
  • Migration status for ocaml-shout/s390x (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/amd64 (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/amd64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/arm64 (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/arm64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/armel (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/armel (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/armhf (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/armhf (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/i386 (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/i386 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/mips64el (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/mips64el (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/mipsel (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/mipsel (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/ppc64el (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/ppc64el (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/s390x (0.1.7-1 to 0.1.7-1)
  • Migration status for ocaml-soundtouch/s390x (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-speex/amd64 (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/amd64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-speex/arm64 (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/arm64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-speex/armel (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/armel (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-speex/armhf (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/armhf (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-speex/i386 (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/i386 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-speex/mips64el (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/mips64el (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-speex/mipsel (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/mipsel (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-speex/ppc64el (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/ppc64el (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-speex/s390x (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-speex/s390x (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/amd64 (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/amd64 (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/arm64 (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/arm64 (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/armel (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/armel (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/armhf (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/armhf (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/i386 (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/i386 (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/mips64el (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/mips64el (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/mipsel (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/mipsel (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/ppc64el (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/ppc64el (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/s390x (4.0.5-2 to 4.0.5-2)
  • Migration status for ocaml-sqlite3/s390x (4.0.5-2 to 4.0.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/amd64 (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/amd64 (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/arm64 (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/arm64 (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/armel (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/armel (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/armhf (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/armhf (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/i386 (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/i386 (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/mips64el (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/mips64el (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/mipsel (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/mipsel (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/ppc64el (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/ppc64el (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/s390x (0.5.9-1 to 0.5.9-1)
  • Migration status for ocaml-ssl/s390x (0.5.9-1 to 0.5.9-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/amd64 (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/amd64 (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/arm64 (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/arm64 (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/armel (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/armel (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/armhf (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/armhf (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/i386 (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/i386 (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/mips64el (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/mips64el (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/mipsel (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/mipsel (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/ppc64el (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/ppc64el (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdcompat/s390x (10-1 to 10-1)
  • Migration status for ocaml-stdcompat/s390x (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/amd64 (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/amd64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/arm64 (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/arm64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/armel (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/armel (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/armhf (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/armhf (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/i386 (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/i386 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/mips64el (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/mips64el (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/mipsel (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/mipsel (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/ppc64el (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/ppc64el (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stdio/s390x (0.12.0-1 to 0.12.0-1)
  • Migration status for ocaml-stdio/s390x (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/amd64 (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/amd64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/arm64 (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/arm64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/armel (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/armel (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/armhf (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/armhf (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/i386 (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/i386 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/mips64el (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/mips64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/mipsel (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/mipsel (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/ppc64el (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/ppc64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/s390x (0.3.1-1 to 0.3.1-1)
  • Migration status for ocaml-taglib/s390x (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-theora/amd64 (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/amd64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-theora/arm64 (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/arm64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-theora/armel (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/armel (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-theora/armhf (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/armhf (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-theora/i386 (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/i386 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-theora/mips64el (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/mips64el (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-theora/mipsel (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/mipsel (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-theora/ppc64el (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/ppc64el (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-theora/s390x (0.3.1-2 to 0.3.1-2)
  • Migration status for ocaml-theora/s390x (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/amd64 (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/amd64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/armel (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/armel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/armhf (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/armhf (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/i386 (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/i386 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/mips64el (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/mips64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/mipsel (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/mipsel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/ppc64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for ocaml-topkg/s390x (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/amd64 (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/amd64 (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/arm64 (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/arm64 (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/armel (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/armel (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/armhf (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/armhf (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/i386 (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/i386 (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/mips64el (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/mips64el (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/mipsel (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/mipsel (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/ppc64el (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/ppc64el (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-visitors/s390x (20190711-2 to 20190711-2)
  • Migration status for ocaml-visitors/s390x (20190711-2 to 20190711-2): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/amd64 (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/amd64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/mipsel (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/mipsel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/s390x (0.1.0-1 to 0.1.0-1)
  • Migration status for ocaml-voaacenc/s390x (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/amd64 (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/amd64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/arm64 (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/arm64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/armel (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/armel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/armhf (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/armhf (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/i386 (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/i386 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/mips64el (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/mips64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/mipsel (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/mipsel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/ppc64el (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/ppc64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/s390x (0.7.1-1 to 0.7.1-1)
  • Migration status for ocaml-vorbis/s390x (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/amd64 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/amd64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/arm64 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/arm64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/armel (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/armel (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/armhf (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/armhf (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/i386 (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/i386 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/mips64el (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/mips64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/mipsel (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/mipsel (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/ppc64el (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/ppc64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/s390x (0.1.3-1 to 0.1.3-1)
  • Migration status for ocaml-xmlplaylist/s390x (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/amd64 (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/amd64 (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/arm64 (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/arm64 (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/armel (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/armel (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/armhf (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/armhf (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/i386 (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/i386 (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/mips64el (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/mips64el (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/mipsel (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/mipsel (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/ppc64el (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/ppc64el (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocaml-zarith/s390x (1.8-1 to 1.8-1)
  • Migration status for ocaml-zarith/s390x (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• ocamlagrep/amd64 (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/amd64 (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlagrep/arm64 (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/arm64 (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlagrep/armel (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/armel (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlagrep/armhf (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/armhf (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlagrep/i386 (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/i386 (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlagrep/mips64el (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/mips64el (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlagrep/mipsel (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/mipsel (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlagrep/ppc64el (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/ppc64el (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlagrep/s390x (1.0-13 to 1.0-13)
  • Migration status for ocamlagrep/s390x (1.0-13 to 1.0-13): Will attempt migration (Any information below is purely informational)
• ocamlbricks/amd64 (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/amd64 (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbricks/arm64 (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/arm64 (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbricks/armel (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/armel (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbricks/armhf (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/armhf (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbricks/i386 (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/i386 (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbricks/mips64el (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/mips64el (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbricks/mipsel (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/mipsel (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbricks/ppc64el (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/ppc64el (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbricks/s390x (0.90+bzr456-2 to 0.90+bzr456-2)
  • Migration status for ocamlbricks/s390x (0.90+bzr456-2 to 0.90+bzr456-2): Will attempt migration (Any information below is purely informational)
• ocamlbuild/amd64 (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/amd64 (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlbuild/arm64 (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/arm64 (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlbuild/armel (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/armel (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlbuild/armhf (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/armhf (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlbuild/i386 (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/i386 (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlbuild/mips64el (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/mips64el (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlbuild/mipsel (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/mipsel (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlbuild/ppc64el (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/ppc64el (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlbuild/s390x (0.14.0-1 to 0.14.0-1)
  • Migration status for ocamlbuild/s390x (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• ocamlcreal/amd64 (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/amd64 (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamlcreal/arm64 (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/arm64 (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamlcreal/armel (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/armel (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamlcreal/armhf (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/armhf (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamlcreal/i386 (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/i386 (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamlcreal/mips64el (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/mips64el (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamlcreal/mipsel (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/mipsel (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamlcreal/ppc64el (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/ppc64el (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamlcreal/s390x (0.7-6 to 0.7-6)
  • Migration status for ocamlcreal/s390x (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• ocamldap/amd64 (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/amd64 (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldap/arm64 (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/arm64 (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldap/armel (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/armel (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldap/armhf (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/armhf (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldap/i386 (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/i386 (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldap/mips64el (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/mips64el (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldap/mipsel (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/mipsel (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldap/ppc64el (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/ppc64el (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldap/s390x (2.1.8-11 to 2.1.8-11)
  • Migration status for ocamldap/s390x (2.1.8-11 to 2.1.8-11): Will attempt migration (Any information below is purely informational)
• ocamldsort/armel (0.16.0-6 to 0.16.0-6)
  • Migration status for ocamldsort/armel (0.16.0-6 to 0.16.0-6): Will attempt migration (Any information below is purely informational)
• ocamldsort/mips64el (0.16.0-6 to 0.16.0-6)
  • Migration status for ocamldsort/mips64el (0.16.0-6 to 0.16.0-6): Will attempt migration (Any information below is purely informational)
• ocamldsort/mipsel (0.16.0-6 to 0.16.0-6)
  • Migration status for ocamldsort/mipsel (0.16.0-6 to 0.16.0-6): Will attempt migration (Any information below is purely informational)
• ocamlgraph/amd64 (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/amd64 (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgraph/arm64 (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/arm64 (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgraph/armel (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/armel (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgraph/armhf (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/armhf (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgraph/i386 (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/i386 (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgraph/mips64el (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/mips64el (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgraph/mipsel (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/mipsel (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgraph/ppc64el (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/ppc64el (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgraph/s390x (1.8.8-1.1 to 1.8.8-1.1)
  • Migration status for ocamlgraph/s390x (1.8.8-1.1 to 1.8.8-1.1): Will attempt migration (Any information below is purely informational)
• ocamlgsl/amd64 (1.19.1-2 to 1.19.1-2)
  • Migration status for ocamlgsl/amd64 (1.19.1-2 to 1.19.1-2): Will attempt migration (Any information below is purely informational)
• ocamlgsl/arm64 (1.19.1-2 to 1.19.1-2)
  • Migration status for ocamlgsl/arm64 (1.19.1-2 to 1.19.1-2): Will attempt migration (Any information below is purely informational)
• ocamlgsl/i386 (1.19.1-2 to 1.19.1-2)
  • Migration status for ocamlgsl/i386 (1.19.1-2 to 1.19.1-2): Will attempt migration (Any information below is purely informational)
• ocamlgsl/mips64el (1.19.1-2 to 1.19.1-2)
  • Migration status for ocamlgsl/mips64el (1.19.1-2 to 1.19.1-2): Will attempt migration (Any information below is purely informational)
• ocamlgsl/ppc64el (1.19.1-2 to 1.19.1-2)
  • Migration status for ocamlgsl/ppc64el (1.19.1-2 to 1.19.1-2): Will attempt migration (Any information below is purely informational)
• ocamlgsl/s390x (1.19.1-2 to 1.19.1-2)
  • Migration status for ocamlgsl/s390x (1.19.1-2 to 1.19.1-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/amd64 (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/amd64 (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/arm64 (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/arm64 (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/armel (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/armel (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/armhf (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/armhf (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/i386 (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/i386 (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/mips64el (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/mips64el (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/mipsel (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/mipsel (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/ppc64el (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/ppc64el (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlmod/s390x (0.0.9-2 to 0.0.9-2)
  • Migration status for ocamlmod/s390x (0.0.9-2 to 0.0.9-2): Will attempt migration (Any information below is purely informational)
• ocamlnet/amd64 (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/amd64 (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/arm64 (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/arm64 (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/armel (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/armel (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/armhf (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/armhf (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/i386 (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/i386 (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/mips64el (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/mips64el (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/mipsel (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/mipsel (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/ppc64el (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/ppc64el (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/s390x (4.1.6-1 to 4.1.6-1)
  • Migration status for ocamlnet/s390x (4.1.6-1 to 4.1.6-1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/amd64 (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/amd64 (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/arm64 (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/arm64 (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/armel (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/armel (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/armhf (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/armhf (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/i386 (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/i386 (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/mips64el (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/mips64el (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/mipsel (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/mipsel (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/ppc64el (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/ppc64el (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlodbc/s390x (2.15-6.1 to 2.15-6.1)
  • Migration status for ocamlodbc/s390x (2.15-6.1 to 2.15-6.1): Will attempt migration (Any information below is purely informational)
• ocamlpam/amd64 (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/amd64 (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlpam/arm64 (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/arm64 (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlpam/armel (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/armel (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlpam/armhf (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/armhf (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlpam/i386 (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/i386 (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlpam/mips64el (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/mips64el (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlpam/mipsel (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/mipsel (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlpam/ppc64el (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/ppc64el (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlpam/s390x (1.1-5 to 1.1-5)
  • Migration status for ocamlpam/s390x (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• ocamlrss/amd64 (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/amd64 (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlrss/arm64 (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/arm64 (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlrss/armel (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/armel (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlrss/armhf (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/armhf (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlrss/i386 (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/i386 (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlrss/mips64el (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/mips64el (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlrss/mipsel (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/mipsel (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlrss/ppc64el (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/ppc64el (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlrss/s390x (2.2.1-3 to 2.2.1-3)
  • Migration status for ocamlrss/s390x (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/amd64 (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/amd64 (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/arm64 (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/arm64 (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/armel (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/armel (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/armhf (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/armhf (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/i386 (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/i386 (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/mips64el (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/mips64el (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/mipsel (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/mipsel (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/ppc64el (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/ppc64el (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocamlsdl/s390x (0.9.1-3 to 0.9.1-3)
  • Migration status for ocamlsdl/s390x (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• ocp-indent/amd64 (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/amd64 (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• ocp-indent/arm64 (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/arm64 (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• ocp-indent/armel (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/armel (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• ocp-indent/armhf (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/armhf (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• ocp-indent/i386 (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/i386 (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• ocp-indent/mips64el (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/mips64el (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• ocp-indent/mipsel (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/mipsel (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• ocp-indent/ppc64el (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/ppc64el (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• ocp-indent/s390x (1.7.0-2 to 1.7.0-2)
  • Migration status for ocp-indent/s390x (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• optcomp/amd64 (1.6-3 to 1.6-3)
  • Migration status for optcomp/amd64 (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• optcomp/arm64 (1.6-3 to 1.6-3)
  • Migration status for optcomp/arm64 (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• optcomp/armel (1.6-3 to 1.6-3)
  • Migration status for optcomp/armel (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• optcomp/armhf (1.6-3 to 1.6-3)
  • Migration status for optcomp/armhf (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• optcomp/i386 (1.6-3 to 1.6-3)
  • Migration status for optcomp/i386 (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• optcomp/mips64el (1.6-3 to 1.6-3)
  • Migration status for optcomp/mips64el (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• optcomp/mipsel (1.6-3 to 1.6-3)
  • Migration status for optcomp/mipsel (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• optcomp/ppc64el (1.6-3 to 1.6-3)
  • Migration status for optcomp/ppc64el (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• optcomp/s390x (1.6-3 to 1.6-3)
  • Migration status for optcomp/s390x (1.6-3 to 1.6-3): Will attempt migration (Any information below is purely informational)
• ounit/amd64 (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/amd64 (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• ounit/arm64 (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/arm64 (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• ounit/armel (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/armel (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• ounit/armhf (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/armhf (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• ounit/i386 (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/i386 (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• ounit/mips64el (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/mips64el (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• ounit/mipsel (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/mipsel (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• ounit/ppc64el (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/ppc64el (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• ounit/s390x (2.0.8-2 to 2.0.8-2)
  • Migration status for ounit/s390x (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• pa-ounit/amd64 (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/amd64 (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pa-ounit/arm64 (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/arm64 (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pa-ounit/armel (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/armel (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pa-ounit/armhf (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/armhf (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pa-ounit/i386 (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/i386 (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pa-ounit/mips64el (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/mips64el (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pa-ounit/mipsel (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/mipsel (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pa-ounit/ppc64el (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/ppc64el (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pa-ounit/s390x (113.00.00-3 to 113.00.00-3)
  • Migration status for pa-ounit/s390x (113.00.00-3 to 113.00.00-3): Will attempt migration (Any information below is purely informational)
• pagodacf/amd64 (0.10-5 to 0.10-5)
  • Migration status for pagodacf/amd64 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• pagodacf/arm64 (0.10-5 to 0.10-5)
  • Migration status for pagodacf/arm64 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• pagodacf/armel (0.10-5 to 0.10-5)
  • Migration status for pagodacf/armel (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• pagodacf/armhf (0.10-5 to 0.10-5)
  • Migration status for pagodacf/armhf (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• pagodacf/i386 (0.10-5 to 0.10-5)
  • Migration status for pagodacf/i386 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• pagodacf/mips64el (0.10-5 to 0.10-5)
  • Migration status for pagodacf/mips64el (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• pagodacf/mipsel (0.10-5 to 0.10-5)
  • Migration status for pagodacf/mipsel (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• pagodacf/ppc64el (0.10-5 to 0.10-5)
  • Migration status for pagodacf/ppc64el (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• pagodacf/s390x (0.10-5 to 0.10-5)
  • Migration status for pagodacf/s390x (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• parmap/amd64 (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/amd64 (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• parmap/arm64 (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/arm64 (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• parmap/armel (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/armel (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• parmap/armhf (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/armhf (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• parmap/i386 (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/i386 (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• parmap/mips64el (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/mips64el (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• parmap/mipsel (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/mipsel (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• parmap/ppc64el (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/ppc64el (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• parmap/s390x (1.0~rc10-3 to 1.0~rc10-3)
  • Migration status for parmap/s390x (1.0~rc10-3 to 1.0~rc10-3): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/amd64 (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/amd64 (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/arm64 (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/arm64 (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/armel (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/armel (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/armhf (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/armhf (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/i386 (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/i386 (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/mips64el (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/mips64el (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/mipsel (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/mipsel (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/ppc64el (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/ppc64el (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• pcre-ocaml/s390x (7.2.3-2 to 7.2.3-2)
  • Migration status for pcre-ocaml/s390x (7.2.3-2 to 7.2.3-2): Will attempt migration (Any information below is purely informational)
• perl4caml/amd64 (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/amd64 (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• perl4caml/arm64 (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/arm64 (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• perl4caml/armel (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/armel (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• perl4caml/armhf (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/armhf (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• perl4caml/i386 (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/i386 (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• perl4caml/mips64el (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/mips64el (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• perl4caml/mipsel (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/mipsel (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• perl4caml/ppc64el (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/ppc64el (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• perl4caml/s390x (0.9.5-5 to 0.9.5-5)
  • Migration status for perl4caml/s390x (0.9.5-5 to 0.9.5-5): Will attempt migration (Any information below is purely informational)
• pgocaml/amd64 (2.3-1 to 2.3-1)
  • Migration status for pgocaml/amd64 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• pgocaml/arm64 (2.3-1 to 2.3-1)
  • Migration status for pgocaml/arm64 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• pgocaml/armel (2.3-1 to 2.3-1)
  • Migration status for pgocaml/armel (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• pgocaml/armhf (2.3-1 to 2.3-1)
  • Migration status for pgocaml/armhf (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• pgocaml/i386 (2.3-1 to 2.3-1)
  • Migration status for pgocaml/i386 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• pgocaml/mips64el (2.3-1 to 2.3-1)
  • Migration status for pgocaml/mips64el (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• pgocaml/mipsel (2.3-1 to 2.3-1)
  • Migration status for pgocaml/mipsel (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• pgocaml/ppc64el (2.3-1 to 2.3-1)
  • Migration status for pgocaml/ppc64el (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• pgocaml/s390x (2.3-1 to 2.3-1)
  • Migration status for pgocaml/s390x (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• planets/armel (0.1.13-20 to 0.1.13-20)
  • Migration status for planets/armel (0.1.13-20 to 0.1.13-20): Will attempt migration (Any information below is purely informational)
• planets/mips64el (0.1.13-20 to 0.1.13-20)
  • Migration status for planets/mips64el (0.1.13-20 to 0.1.13-20): Will attempt migration (Any information below is purely informational)
• planets/mipsel (0.1.13-20 to 0.1.13-20)
  • Migration status for planets/mipsel (0.1.13-20 to 0.1.13-20): Will attempt migration (Any information below is purely informational)
• plplot/amd64 (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/amd64 (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• plplot/arm64 (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/arm64 (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• plplot/armel (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/armel (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• plplot/armhf (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/armhf (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• plplot/i386 (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/i386 (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• plplot/mips64el (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/mips64el (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• plplot/mipsel (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/mipsel (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• plplot/ppc64el (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/ppc64el (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• plplot/s390x (5.15.0+dfsg-4 to 5.15.0+dfsg-4)
  • Migration status for plplot/s390x (5.15.0+dfsg-4 to 5.15.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/amd64 (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/amd64 (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/arm64 (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/arm64 (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/armel (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/armel (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/armhf (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/armhf (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/i386 (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/i386 (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/mips64el (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/mips64el (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/mipsel (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/mipsel (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/ppc64el (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/ppc64el (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• postgresql-ocaml/s390x (4.5.0-1 to 4.5.0-1)
  • Migration status for postgresql-ocaml/s390x (4.5.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/amd64 (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/amd64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/arm64 (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/arm64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/armel (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/armel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/armhf (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/armhf (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/i386 (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/i386 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/mips64el (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/mips64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/mipsel (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/mipsel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/ppc64el (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/ppc64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/s390x (1.2.1-1 to 1.2.1-1)
  • Migration status for ppx-derivers/s390x (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/amd64 (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/amd64 (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/arm64 (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/arm64 (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/armel (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/armel (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/armhf (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/armhf (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/i386 (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/i386 (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/mips64el (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/mips64el (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/mipsel (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/mipsel (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/ppc64el (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/ppc64el (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving-yojson/s390x (3.5.1-2 to 3.5.1-2)
  • Migration status for ppx-deriving-yojson/s390x (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/amd64 (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/amd64 (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/arm64 (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/arm64 (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/armel (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/armel (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/armhf (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/armhf (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/i386 (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/i386 (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/mips64el (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/mips64el (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/mipsel (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/mipsel (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/ppc64el (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/ppc64el (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-deriving/s390x (4.4-2 to 4.4-2)
  • Migration status for ppx-deriving/s390x (4.4-2 to 4.4-2): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/amd64 (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/amd64 (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/arm64 (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/arm64 (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/armel (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/armel (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/armhf (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/armhf (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/i386 (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/i386 (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/mips64el (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/mips64el (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/mipsel (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/mipsel (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/ppc64el (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/ppc64el (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppx-tools-versioned/s390x (5.2.3-1 to 5.2.3-1)
  • Migration status for ppx-tools-versioned/s390x (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/amd64 (1.3-1 to 1.3-1)
  • Migration status for ppxfind/amd64 (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/arm64 (1.3-1 to 1.3-1)
  • Migration status for ppxfind/arm64 (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/armel (1.3-1 to 1.3-1)
  • Migration status for ppxfind/armel (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/armhf (1.3-1 to 1.3-1)
  • Migration status for ppxfind/armhf (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/i386 (1.3-1 to 1.3-1)
  • Migration status for ppxfind/i386 (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/mips64el (1.3-1 to 1.3-1)
  • Migration status for ppxfind/mips64el (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/mipsel (1.3-1 to 1.3-1)
  • Migration status for ppxfind/mipsel (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/ppc64el (1.3-1 to 1.3-1)
  • Migration status for ppxfind/ppc64el (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxfind/s390x (1.3-1 to 1.3-1)
  • Migration status for ppxfind/s390x (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ppxlib/amd64 (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/amd64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• ppxlib/arm64 (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/arm64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• ppxlib/armel (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/armel (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• ppxlib/armhf (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/armhf (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• ppxlib/i386 (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/i386 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• ppxlib/mips64el (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/mips64el (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• ppxlib/mipsel (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/mipsel (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• ppxlib/ppc64el (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/ppc64el (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• ppxlib/s390x (0.8.1-1 to 0.8.1-1)
  • Migration status for ppxlib/s390x (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• pycaml/amd64 (0.82-15 to 0.82-15)
  • Migration status for pycaml/amd64 (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pycaml/arm64 (0.82-15 to 0.82-15)
  • Migration status for pycaml/arm64 (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pycaml/armel (0.82-15 to 0.82-15)
  • Migration status for pycaml/armel (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pycaml/armhf (0.82-15 to 0.82-15)
  • Migration status for pycaml/armhf (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pycaml/i386 (0.82-15 to 0.82-15)
  • Migration status for pycaml/i386 (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pycaml/mips64el (0.82-15 to 0.82-15)
  • Migration status for pycaml/mips64el (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pycaml/mipsel (0.82-15 to 0.82-15)
  • Migration status for pycaml/mipsel (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pycaml/ppc64el (0.82-15 to 0.82-15)
  • Migration status for pycaml/ppc64el (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pycaml/s390x (0.82-15 to 0.82-15)
  • Migration status for pycaml/s390x (0.82-15 to 0.82-15): Will attempt migration (Any information below is purely informational)
• pyfai/amd64 (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/amd64 (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• pyfai/arm64 (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/arm64 (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• pyfai/armel (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/armel (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• pyfai/armhf (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/armhf (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• pyfai/i386 (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/i386 (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• pyfai/mips64el (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/mips64el (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• pyfai/mipsel (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/mipsel (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• pyfai/ppc64el (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/ppc64el (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• pyfai/s390x (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3)
  • Migration status for pyfai/s390x (0.18.0+dfsg1-3 to 0.18.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• python-wsaccel/amd64 (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/amd64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• python-wsaccel/arm64 (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/arm64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• python-wsaccel/armel (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/armel (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• python-wsaccel/armhf (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/armhf (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• python-wsaccel/i386 (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/i386 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• python-wsaccel/mips64el (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/mips64el (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• python-wsaccel/mipsel (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/mipsel (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• python-wsaccel/ppc64el (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/ppc64el (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• python-wsaccel/s390x (0.6.2-2 to 0.6.2-2)
  • Migration status for python-wsaccel/s390x (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• quorum/arm64 (1.1.1-2 to 1.1.1-2)
  • Migration status for quorum/arm64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• quorum/mips64el (1.1.1-2 to 1.1.1-2)
  • Migration status for quorum/mips64el (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• quorum/ppc64el (1.1.1-2 to 1.1.1-2)
  • Migration status for quorum/ppc64el (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• react/amd64 (1.2.0-3 to 1.2.0-3)
  • Migration status for react/amd64 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• react/arm64 (1.2.0-3 to 1.2.0-3)
  • Migration status for react/arm64 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• react/armel (1.2.0-3 to 1.2.0-3)
  • Migration status for react/armel (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• react/armhf (1.2.0-3 to 1.2.0-3)
  • Migration status for react/armhf (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• react/i386 (1.2.0-3 to 1.2.0-3)
  • Migration status for react/i386 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• react/mips64el (1.2.0-3 to 1.2.0-3)
  • Migration status for react/mips64el (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• react/mipsel (1.2.0-3 to 1.2.0-3)
  • Migration status for react/mipsel (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• react/ppc64el (1.2.0-3 to 1.2.0-3)
  • Migration status for react/ppc64el (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• react/s390x (1.2.0-3 to 1.2.0-3)
  • Migration status for react/s390x (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• reactivedata/amd64 (0.1-3 to 0.1-3)
  • Migration status for reactivedata/amd64 (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• reactivedata/arm64 (0.1-3 to 0.1-3)
  • Migration status for reactivedata/arm64 (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• reactivedata/armel (0.1-3 to 0.1-3)
  • Migration status for reactivedata/armel (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• reactivedata/armhf (0.1-3 to 0.1-3)
  • Migration status for reactivedata/armhf (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• reactivedata/i386 (0.1-3 to 0.1-3)
  • Migration status for reactivedata/i386 (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• reactivedata/mips64el (0.1-3 to 0.1-3)
  • Migration status for reactivedata/mips64el (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• reactivedata/mipsel (0.1-3 to 0.1-3)
  • Migration status for reactivedata/mipsel (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• reactivedata/ppc64el (0.1-3 to 0.1-3)
  • Migration status for reactivedata/ppc64el (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• reactivedata/s390x (0.1-3 to 0.1-3)
  • Migration status for reactivedata/s390x (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• rust-globset/amd64 (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/amd64 (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• rust-globset/arm64 (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/arm64 (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• rust-globset/armel (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/armel (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• rust-globset/armhf (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/armhf (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• rust-globset/i386 (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/i386 (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• rust-globset/mips64el (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/mips64el (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• rust-globset/mipsel (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/mipsel (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• rust-globset/ppc64el (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/ppc64el (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• rust-globset/s390x (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-globset/s390x (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• samhain/amd64 (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/amd64 (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/amd64 libprelude (not considered)
• samhain/arm64 (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/arm64 (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/arm64 libprelude (not considered)
• samhain/armel (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/armel (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/armel libprelude (not considered)
• samhain/armhf (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/armhf (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/armhf libprelude (not considered)
• samhain/i386 (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/i386 (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/i386 libprelude (not considered)
• samhain/mips64el (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/mips64el (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/mips64el libprelude (not considered)
• samhain/mipsel (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/mipsel (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/mipsel libprelude (not considered)
• samhain/ppc64el (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/ppc64el (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/ppc64el libprelude (not considered)
• samhain/s390x (4.1.4-2 to 4.1.4-2)
  • Migration status for samhain/s390x (4.1.4-2 to 4.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: samhain/s390x libprelude (not considered)
• silx/amd64 (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/amd64 (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• silx/arm64 (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/arm64 (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• silx/armel (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/armel (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• silx/armhf (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/armhf (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• silx/i386 (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/i386 (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• silx/mips64el (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/mips64el (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• silx/mipsel (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/mipsel (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• silx/ppc64el (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/ppc64el (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• silx/s390x (0.11.0+dfsg-2 to 0.11.0+dfsg-2)
  • Migration status for silx/s390x (0.11.0+dfsg-2 to 0.11.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• suricata/amd64 (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/amd64 (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/amd64 libprelude (not considered)
• suricata/arm64 (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/arm64 (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/arm64 libprelude (not considered)
• suricata/armel (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/armel (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/armel libprelude (not considered)
• suricata/armhf (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/armhf (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/armhf libprelude (not considered)
• suricata/i386 (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/i386 (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/i386 libprelude (not considered)
• suricata/mips64el (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/mips64el (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/mips64el libprelude (not considered)
• suricata/mipsel (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/mipsel (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/mipsel libprelude (not considered)
• suricata/ppc64el (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/ppc64el (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/ppc64el libprelude (not considered)
• suricata/s390x (1:4.1.5-2 to 1:4.1.5-2)
  • Migration status for suricata/s390x (1:4.1.5-2 to 1:4.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: suricata/s390x libprelude (not considered)
• syslog-ocaml/amd64 (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/amd64 (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/arm64 (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/arm64 (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/armel (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/armel (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/armhf (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/armhf (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/i386 (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/i386 (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/mips64el (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/mips64el (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/mipsel (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/mipsel (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/ppc64el (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/ppc64el (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/s390x (1.4-7 to 1.4-7)
  • Migration status for syslog-ocaml/s390x (1.4-7 to 1.4-7): Will attempt migration (Any information below is purely informational)
• type-conv/amd64 (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/amd64 (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• type-conv/arm64 (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/arm64 (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• type-conv/armel (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/armel (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• type-conv/armhf (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/armhf (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• type-conv/i386 (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/i386 (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• type-conv/mips64el (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/mips64el (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• type-conv/mipsel (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/mipsel (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• type-conv/ppc64el (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/ppc64el (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• type-conv/s390x (113.00.02-2 to 113.00.02-2)
  • Migration status for type-conv/s390x (113.00.02-2 to 113.00.02-2): Will attempt migration (Any information below is purely informational)
• typerep/amd64 (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/amd64 (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• typerep/arm64 (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/arm64 (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• typerep/armel (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/armel (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• typerep/armhf (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/armhf (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• typerep/i386 (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/i386 (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• typerep/mips64el (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/mips64el (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• typerep/mipsel (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/mipsel (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• typerep/ppc64el (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/ppc64el (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• typerep/s390x (1:0.12.0-1 to 1:0.12.0-1)
  • Migration status for typerep/s390x (1:0.12.0-1 to 1:0.12.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/amd64 (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/amd64 (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/arm64 (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/arm64 (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/armel (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/armel (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/armhf (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/armhf (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/i386 (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/i386 (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/mips64el (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/mips64el (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/mipsel (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/mipsel (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/ppc64el (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/ppc64el (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/s390x (4.1.0-1 to 4.1.0-1)
  • Migration status for tyxml/s390x (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• ulex/amd64 (1.1-4 to 1.1-4)
  • Migration status for ulex/amd64 (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex/arm64 (1.1-4 to 1.1-4)
  • Migration status for ulex/arm64 (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex/armel (1.1-4 to 1.1-4)
  • Migration status for ulex/armel (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex/armhf (1.1-4 to 1.1-4)
  • Migration status for ulex/armhf (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex/i386 (1.1-4 to 1.1-4)
  • Migration status for ulex/i386 (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex/mips64el (1.1-4 to 1.1-4)
  • Migration status for ulex/mips64el (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex/mipsel (1.1-4 to 1.1-4)
  • Migration status for ulex/mipsel (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex/ppc64el (1.1-4 to 1.1-4)
  • Migration status for ulex/ppc64el (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex/s390x (1.1-4 to 1.1-4)
  • Migration status for ulex/s390x (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• ulex0.8/amd64 (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/amd64 (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• ulex0.8/arm64 (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/arm64 (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• ulex0.8/armel (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/armel (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• ulex0.8/armhf (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/armhf (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• ulex0.8/i386 (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/i386 (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• ulex0.8/mips64el (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/mips64el (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• ulex0.8/mipsel (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/mipsel (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• ulex0.8/ppc64el (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/ppc64el (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• ulex0.8/s390x (0.8-12 to 0.8-12)
  • Migration status for ulex0.8/s390x (0.8-12 to 0.8-12): Will attempt migration (Any information below is purely informational)
• uuidm/amd64 (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/amd64 (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uuidm/arm64 (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/arm64 (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uuidm/armel (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/armel (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uuidm/armhf (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/armhf (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uuidm/i386 (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/i386 (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uuidm/mips64el (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/mips64el (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uuidm/mipsel (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/mipsel (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uuidm/ppc64el (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/ppc64el (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uuidm/s390x (0.9.6-1 to 0.9.6-1)
  • Migration status for uuidm/s390x (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• uutf/amd64 (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/amd64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• uutf/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/arm64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• uutf/armel (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/armel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• uutf/armhf (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/armhf (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• uutf/i386 (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/i386 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• uutf/mips64el (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/mips64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• uutf/mipsel (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/mipsel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• uutf/ppc64el (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/ppc64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• uutf/s390x (1.0.1-2 to 1.0.1-2)
  • Migration status for uutf/s390x (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• variantslib/amd64 (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/amd64 (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• variantslib/arm64 (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/arm64 (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• variantslib/armel (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/armel (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• variantslib/armhf (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/armhf (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• variantslib/i386 (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/i386 (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• variantslib/mips64el (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/mips64el (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• variantslib/mipsel (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/mipsel (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• variantslib/ppc64el (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/ppc64el (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• variantslib/s390x (113.33.03-2 to 113.33.03-2)
  • Migration status for variantslib/s390x (113.33.03-2 to 113.33.03-2): Will attempt migration (Any information below is purely informational)
• xfce4-cpufreq-plugin/ppc64el (1.2.1-1 to 1.2.1-1)
  • Migration status for xfce4-cpufreq-plugin/ppc64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• xml-light/amd64 (2.4-1 to 2.4-1)
  • Migration status for xml-light/amd64 (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xml-light/arm64 (2.4-1 to 2.4-1)
  • Migration status for xml-light/arm64 (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xml-light/armel (2.4-1 to 2.4-1)
  • Migration status for xml-light/armel (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xml-light/armhf (2.4-1 to 2.4-1)
  • Migration status for xml-light/armhf (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xml-light/i386 (2.4-1 to 2.4-1)
  • Migration status for xml-light/i386 (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xml-light/mips64el (2.4-1 to 2.4-1)
  • Migration status for xml-light/mips64el (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xml-light/mipsel (2.4-1 to 2.4-1)
  • Migration status for xml-light/mipsel (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xml-light/ppc64el (2.4-1 to 2.4-1)
  • Migration status for xml-light/ppc64el (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xml-light/s390x (2.4-1 to 2.4-1)
  • Migration status for xml-light/s390x (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• xmlm/amd64 (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/amd64 (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlm/arm64 (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/arm64 (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlm/armel (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/armel (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlm/armhf (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/armhf (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlm/i386 (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/i386 (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlm/mips64el (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/mips64el (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlm/mipsel (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/mipsel (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlm/ppc64el (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/ppc64el (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlm/s390x (1.3.0-2 to 1.3.0-2)
  • Migration status for xmlm/s390x (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/amd64 (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/amd64 (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/arm64 (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/arm64 (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/armel (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/armel (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/armhf (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/armhf (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/i386 (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/i386 (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/mips64el (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/mips64el (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/mipsel (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/mipsel (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/ppc64el (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/ppc64el (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xmlrpc-light/s390x (0.6.1-5 to 0.6.1-5)
  • Migration status for xmlrpc-light/s390x (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• xstr/amd64 (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/amd64 (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• xstr/arm64 (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/arm64 (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• xstr/armel (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/armel (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• xstr/armhf (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/armhf (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• xstr/i386 (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/i386 (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• xstr/mips64el (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/mips64el (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• xstr/mipsel (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/mipsel (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• xstr/ppc64el (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/ppc64el (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• xstr/s390x (0.2.1-23 to 0.2.1-23)
  • Migration status for xstr/s390x (0.2.1-23 to 0.2.1-23): Will attempt migration (Any information below is purely informational)
• yojson/amd64 (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/amd64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• yojson/arm64 (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/arm64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• yojson/armel (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/armel (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• yojson/armhf (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/armhf (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• yojson/i386 (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/i386 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• yojson/mips64el (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/mips64el (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• yojson/mipsel (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/mipsel (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• yojson/ppc64el (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/ppc64el (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• yojson/s390x (1.7.0-1 to 1.7.0-1)
  • Migration status for yojson/s390x (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• z3/amd64 (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/amd64 (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• z3/arm64 (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/arm64 (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• z3/armel (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/armel (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• z3/armhf (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/armhf (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• z3/i386 (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/i386 (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• z3/mips64el (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/mips64el (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• z3/mipsel (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/mipsel (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• z3/ppc64el (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/ppc64el (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• z3/s390x (4.8.6-2 to 4.8.6-2)
  • Migration status for z3/s390x (4.8.6-2 to 4.8.6-2): Will attempt migration (Any information below is purely informational)
• zanshin/amd64 (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/amd64 (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/amd64 akonadi-calendar (not considered)
• zanshin/arm64 (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/arm64 (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/arm64 akonadi-calendar (not considered)
• zanshin/armel (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/armel (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/armel akonadi-calendar (not considered)
• zanshin/armhf (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/armhf (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/armhf akonadi-calendar (not considered)
• zanshin/i386 (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/i386 (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/i386 akonadi-calendar (not considered)
• zanshin/mips64el (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/mips64el (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/mips64el akonadi-calendar (not considered)
• zanshin/mipsel (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/mipsel (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/mipsel akonadi-calendar (not considered)
• zanshin/ppc64el (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/ppc64el (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/ppc64el akonadi-calendar (not considered)
• zanshin/s390x (0.5.0-2 to 0.5.0-2)
  • Migration status for zanshin/s390x (0.5.0-2 to 0.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: zanshin/s390x akonadi-calendar (not considered)
• zed/amd64 (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/amd64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• zed/arm64 (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/arm64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• zed/armel (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/armel (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• zed/armhf (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/armhf (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• zed/i386 (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/i386 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• zed/mips64el (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/mips64el (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• zed/mipsel (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/mipsel (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• zed/ppc64el (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/ppc64el (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• zed/s390x (2.0.3-1 to 2.0.3-1)
  • Migration status for zed/s390x (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• aiopg (0.15.0-1 to 1.0.0-1)
  • Migration status for aiopg (0.15.0-1 to 1.0.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiopg.html
• anbox (0.0~git20191022-1 to 0.0~git20191115-1)
  • Migration status for anbox (0.0~git20191022-1 to 0.0~git20191115-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• babeltrace (1.5.7-1 to 1.5.7-2)
  • Migration status for babeltrace (1.5.7-1 to 1.5.7-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Updating babeltrace fixes old bugs: #944933
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/babeltrace.html
• consul (1.4.4~dfsg1-2 to 1.4.4~dfsg3-5)
  • Migration status for consul (1.4.4~dfsg1-2 to 1.4.4~dfsg3-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/consul.html
• copyq (3.9.2-1 to 3.9.3-1)
  • Migration status for copyq (3.9.2-1 to 3.9.3-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/copyq.html
• crmsh (4.1.0-3 to 4.1.0-4)
  • Migration status for crmsh (4.1.0-3 to 4.1.0-4): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crmsh.html
  • Required age reduced by 3 days because of autopkgtest
• dbus-python (1.2.12-1 to 1.2.12-2)
  • Migration status for dbus-python (1.2.12-1 to 1.2.12-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbus-python.html
  • Required age reduced by 3 days because of autopkgtest
• debci (2.5 to 2.6)
  • Migration status for debci (2.5 to 2.6): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debci.html
  • Required age reduced by 3 days because of autopkgtest
• drbd-utils (9.5.0-1 to 9.11.0-1)
  • Migration status for drbd-utils (9.5.0-1 to 9.11.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drbd-utils.html
• extrepo (- to 0.3)
  • Migration status for extrepo (- to 0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating extrepo introduces new bugs: #945047, #945053
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Too young, only 0 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gfarm2fs (1.2.11-1 to 1.2.13-1)
  • Migration status for gfarm2fs (1.2.11-1 to 1.2.13-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfarm2fs.html
• git-annex (7.20191024-1 to 7.20191114-1)
  • Migration status for git-annex (7.20191024-1 to 7.20191114-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • missing build on mipsel
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-annex.html
  • Required age reduced by 3 days because of autopkgtest
• gladtex (2.3.1-3 to 3.1.0-1)
  • Migration status for gladtex (2.3.1-3 to 3.1.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gladtex.html
• gnome-shell-extension-dash-to-panel (25-1 to 26-1)
  • Migration status for gnome-shell-extension-dash-to-panel (25-1 to 26-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-dash-to-panel.html
• heartbeat (1:3.0.6-9 to 1:3.0.6-10)
  • Migration status for heartbeat (1:3.0.6-9 to 1:3.0.6-10): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heartbeat.html
  • Required age reduced by 3 days because of autopkgtest
• kstars (5:3.3.7-1 to 5:3.3.8-1)
  • Migration status for kstars (5:3.3.7-1 to 5:3.3.8-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kstars.html
• lazy-object-proxy (1.3.1-2 to 1.4.3-1)
  • Migration status for lazy-object-proxy (1.3.1-2 to 1.4.3-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lazy-object-proxy.html
• libchi-driver-memcached-perl (0.15-1 to 0.16-1)
  • Migration status for libchi-driver-memcached-perl (0.15-1 to 0.16-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libchi-driver-memcached-perl.html
  • Required age reduced by 3 days because of autopkgtest
• libconfig-inifiles-perl (3.000001-1 to 3.000002-1)
  • Migration status for libconfig-inifiles-perl (3.000001-1 to 3.000002-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libconfig-inifiles-perl.html
  • Required age reduced by 3 days because of autopkgtest
• libconfig-mvp-slicer-perl (0.302-1 to 0.303-1)
  • Migration status for libconfig-mvp-slicer-perl (0.302-1 to 0.303-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libconfig-mvp-slicer-perl.html
  • Required age reduced by 3 days because of autopkgtest
• libthread-pool (1.0.0-4 to 2.0.1-2)
  • Migration status for libthread-pool (1.0.0-4 to 2.0.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libthread-pool.html
• libva (2.5.0-1 to 2.5.0-2)
  • Migration status for libva (2.5.0-1 to 2.5.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libva.html
• linux (5.2.17-1 to 5.3.9-3)
  • Migration status for linux (5.2.17-1 to 5.3.9-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux.html
• logrotate (3.15.1-1 to 3.15.1-2)
  • Migration status for logrotate (3.15.1-1 to 3.15.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/logrotate.html
  • Required age reduced by 3 days because of autopkgtest
• ltt-control (2.11.0-2 to 2.11.0-3)
  • Migration status for ltt-control (2.11.0-2 to 2.11.0-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Updating ltt-control fixes old bugs: #944938
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ltt-control.html
• nautilus-python (1.2.2-2 to 1.2.3-1)
  • Migration status for nautilus-python (1.2.2-2 to 1.2.3-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-python.html
• node-after (0.8.2-1 to 0.8.2-2)
  • Migration status for node-after (0.8.2-1 to 0.8.2-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-after.html
  • Required age reduced by 3 days because of autopkgtest
• node-asn1.js (5.2.0-1 to 5.2.0-2)
  • Migration status for node-asn1.js (5.2.0-1 to 5.2.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-asn1.js.html
  • Required age reduced by 3 days because of autopkgtest
• node-assertive (3.0.1+ds-1 to 3.1.0+ds-1)
  • Migration status for node-assertive (3.0.1+ds-1 to 3.1.0+ds-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-assertive.html
  • Required age reduced by 3 days because of autopkgtest
• node-ast-util (0.6.0-2 to 0.6.0-3)
  • Migration status for node-ast-util (0.6.0-2 to 0.6.0-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-ast-util.html
  • Required age reduced by 3 days because of autopkgtest
• node-aws4 (1.8.0-1 to 1.8.0-2)
  • Migration status for node-aws4 (1.8.0-1 to 1.8.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-aws4.html
  • Required age reduced by 3 days because of autopkgtest
• node-bn.js (5.0.0-1 to 5.0.0-2)
  • Migration status for node-bn.js (5.0.0-1 to 5.0.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-bn.js.html
  • Required age reduced by 3 days because of autopkgtest
• node-brorand (1.1.0-2 to 1.1.0-3)
  • Migration status for node-brorand (1.1.0-2 to 1.1.0-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-brorand.html
  • Required age reduced by 3 days because of autopkgtest
• node-browser-resolve (1.11.3-1 to 1.11.3-2)
  • Migration status for node-browser-resolve (1.11.3-1 to 1.11.3-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-browser-resolve.html
  • Required age reduced by 3 days because of autopkgtest
• node-coveralls (3.0.6-1 to 3.0.6-3)
  • Migration status for node-coveralls (3.0.6-1 to 3.0.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for node-coveralls/3.0.6-3: amd64: Regression ♻
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-coveralls.html
• node-log-driver (1.2.7+git+20180219+bba1761737-3 to 1.2.7+git+20180219+bba1761737-5)
  • Migration status for node-log-driver (1.2.7+git+20180219+bba1761737-3 to 1.2.7+git+20180219+bba1761737-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for node-log-driver/1.2.7+git+20180219+bba1761737-5: amd64: Regression ♻
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-log-driver.html
• node-lolex (2.2.0-1 to 4.2.0+ds-1)
  • Migration status for node-lolex (2.2.0-1 to 4.2.0+ds-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-lolex.html
  • Required age reduced by 3 days because of autopkgtest
• node-sinon (1.17.6-1 to 7.5.0-1)
  • Migration status for node-sinon (1.17.6-1 to 7.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for node-coveralls/3.0.6-1: amd64: Regression ♻
  • autopkgtest for node-log-driver/1.2.7+git+20180219+bba1761737-3: amd64: Regression ♻
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-sinon.html
• nordugrid-arc (6.3.0-2 to 6.4.0-1)
  • Migration status for nordugrid-arc (6.3.0-2 to 6.4.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nordugrid-arc.html
• ntpsec (1.1.7+dfsg1-2 to 1.1.8+dfsg1-1)
  • Migration status for ntpsec (1.1.7+dfsg1-2 to 1.1.8+dfsg1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntpsec.html
• obs-studio (24.0.3+dfsg1-1 to 24.0.3+dfsg1-2)
  • Migration status for obs-studio (24.0.3+dfsg1-1 to 24.0.3+dfsg1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-studio.html
• opendnssec (1:2.1.3-3 to 1:2.1.4-2)
  • Migration status for opendnssec (1:2.1.3-3 to 1:2.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tjaalton@ubuntu.com
  • Not built on buildd: arch all binaries uploaded by tjaalton@ubuntu.com, a new source-only upload is needed to allow migration
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opendnssec.html
• openstack-pkg-tools (101 to 102)
  • Migration status for openstack-pkg-tools (101 to 102): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstack-pkg-tools.html
• plinth (19.20 to 19.21)
  • Migration status for plinth (19.20 to 19.21): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plinth.html
• plyvel (- to 1.1.0-2)
  • Migration status for plyvel (- to 1.1.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• progress-linux (20190101-8 to 20190101-9)
  • Migration status for progress-linux (20190101-8 to 20190101-9): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/progress-linux.html
• progress-linux-metapackages (- to 20190701-8)
  • Migration status for progress-linux-metapackages (- to 20190701-8): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/progress-linux-metapackages.html
• pyatspi (2.34.0-2 to 2.34.0-5)
  • Migration status for pyatspi (2.34.0-2 to 2.34.0-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyatspi.html
  • Required age reduced by 3 days because of autopkgtest
• pytest-pylint (0.14.1-1 to 0.14.1-2)
  • Migration status for pytest-pylint (0.14.1-1 to 0.14.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-pylint.html
• python-geopandas (0.6.1-1 to 0.6.2-1)
  • Migration status for python-geopandas (0.6.1-1 to 0.6.2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-geopandas.html
• python-m3u8 (0.5.1-1 to 0.5.2-1)
  • Migration status for python-m3u8 (0.5.1-1 to 0.5.2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-m3u8.html
  • Required age reduced by 3 days because of autopkgtest
• python-scipy (1.2.2-7 to 1.2.2-8)
  • Migration status for python-scipy (1.2.2-7 to 1.2.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for gammapy/0.13-1: amd64: Regression ♻
  • autopkgtest for pyfai/0.18.0+dfsg1-3: amd64: Regression ♻
  • missing build on armel
  • missing build on mips64el
  • missing build on mipsel
  • Too young, only 0 of 5 days old
  • Additional info:
  • Updating python-scipy fixes old bugs: #942794
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-scipy.html
• qscintilla2 (2.10.4+dfsg-2.1 to 2.11.2+dfsg-5)
  • Migration status for qscintilla2 (2.10.4+dfsg-2.1 to 2.11.2+dfsg-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 0 of 2 days old
  • Additional info:
  • Updating qscintilla2 fixes old bugs: #875144
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qscintilla2.html
  • Required age reduced by 3 days because of autopkgtest
• r-bioc-genomicalignments (1.22.0-1 to 1.22.1-1)
  • Migration status for r-bioc-genomicalignments (1.22.0-1 to 1.22.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomicalignments.html
  • Required age reduced by 3 days because of autopkgtest
• r-cran-insight (0.6.0-1 to 0.7.0-1)
  • Migration status for r-cran-insight (0.6.0-1 to 0.7.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-insight.html
  • Required age reduced by 3 days because of autopkgtest
• r-cran-rslurm (- to 0.5.0-1)
  • Migration status for r-cran-rslurm (- to 0.5.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rslurm.html
  • Required age reduced by 3 days because of autopkgtest
• segemehl (0.3.4-1 to 0.3.4-2)
  • Migration status for segemehl (0.3.4-1 to 0.3.4-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/segemehl.html
• spades (3.13.0+dfsg2-2 to 3.13.1+dfsg-1)
  • Migration status for spades (3.13.0+dfsg2-2 to 3.13.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for circlator/1.5.6-1: amd64: Regression ♻
  • autopkgtest for spades/3.13.1+dfsg-1: amd64: Regression ♻
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spades.html
• sphinx-astropy (1.1.1-1 to 1.2-1)
  • Migration status for sphinx-astropy (1.1.1-1 to 1.2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 7 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-astropy.html
  • Required age reduced by 3 days because of autopkgtest
• tarlz (0.16-1 to 0.16-2)
  • Migration status for tarlz (0.16-1 to 0.16-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tarlz.html
• tiff (4.1.0-1 to 4.1.0+git191117-1)
  • Migration status for tiff (4.1.0-1 to 4.1.0+git191117-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiff.html
• unicycler (- to 0.4.8+dfsg-1)
  • Migration status for unicycler (- to 0.4.8+dfsg-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unicycler.html
  • Required age reduced by 3 days because of autopkgtest
• vlc (3.0.8-2 to 3.0.8-3)
  • Migration status for vlc (3.0.8-2 to 3.0.8-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vlc.html
  • Required age reduced by 3 days because of autopkgtest
• wine-development (4.19-1 to 4.20-1)
  • Migration status for wine-development (4.19-1 to 4.20-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine-development.html
• xlunzip (0.4-5 to 0.4-6)
  • Migration status for xlunzip (0.4-5 to 0.4-6): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xlunzip.html
• yodl (4.02.01-3 to 4.02.02-1)
  • Migration status for yodl (4.02.01-3 to 4.02.02-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yodl.html
• yp-svipc (0.16-4 to 0.16-5)
  • Migration status for yp-svipc (0.16-4 to 0.16-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yp-svipc.html
• zutils (1.8-4 to 1.8-5)
  • Migration status for zutils (1.8-4 to 1.8-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zutils.html
• asymptote (2.60-1 to 2.60-2)
  • Migration status for asymptote (2.60-1 to 2.60-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asymptote.html
• autofs (5.1.5-2 to 5.1.6-1)
  • Migration status for autofs (5.1.5-2 to 5.1.6-1): Waiting for test results, 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/autofs.html
• awscli (1.16.251-1 to 1.16.283-1)
  • Migration status for awscli (1.16.251-1 to 1.16.283-1): Waiting for test results, 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/awscli.html
  • Required age reduced by 3 days because of autopkgtest
• berkeley-express (1.5.2+dfsg-1 to 1.5.3+dfsg-1)
  • Migration status for berkeley-express (1.5.2+dfsg-1 to 1.5.3+dfsg-1): Waiting for test results, 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/berkeley-express.html
  • Required age reduced by 3 days because of autopkgtest
• black (19.3b0-1 to 19.10b0-1)
  • Migration status for black (19.3b0-1 to 19.10b0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for black/19.10b0-1: amd64: Regression ♻
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/black.html
• burgerspace (1.9.2-3 to 1.9.3-1)
  • Migration status for burgerspace (1.9.2-3 to 1.9.3-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/burgerspace.html
• caveexpress (2.4+git20160609-4 to 2.5-dev2-1)
  • Migration status for caveexpress (2.4+git20160609-4 to 2.5-dev2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caveexpress.html
• ccache (3.7.5-1 to 3.7.6-1)
  • Migration status for ccache (3.7.5-1 to 3.7.6-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccache.html
• cln (1.3.4-5 to 1.3.5-1)
  • Migration status for cln (1.3.4-5 to 1.3.5-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cln.html
• clzip (1.11-5 to 1.11-6)
  • Migration status for clzip (1.11-5 to 1.11-6): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clzip.html
• console-setup (1.193 to 1.194)
  • Migration status for console-setup (1.193 to 1.194): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • uninstallable on arch amd64, autopkgtest delayed there
  • Too young, only 1 of 5 days old
  • Additional info:
  • console-setup-freebsd/amd64 unsatisfiable Depends: vidcontrol
  • console-setup-freebsd/amd64 unsatisfiable Depends: kbdcontrol
  • console-setup-freebsd/i386 unsatisfiable Depends: vidcontrol
  • console-setup-freebsd/i386 unsatisfiable Depends: kbdcontrol
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/console-setup.html
• corsix-th (0.62-2 to 0.63-1)
  • Migration status for corsix-th (0.62-2 to 0.63-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• cross-gcc (230 to 235)
  • Migration status for cross-gcc (230 to 235): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cross-gcc.html
• crun (- to 0.10.6+dfsg-1)
  • Migration status for crun (- to 0.10.6+dfsg-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• cryptmount (5.3.1-1 to 5.3.2-1)
  • Migration status for cryptmount (5.3.1-1 to 5.3.2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cryptmount.html
• cubemap (1.4.2-1 to 1.4.3-1)
  • Migration status for cubemap (1.4.2-1 to 1.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sesse
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cubemap.html
• curry-base (1.1.0-1 to 1.1.1-1)
  • Migration status for curry-base (1.1.0-1 to 1.1.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curry-base.html
• curry-frontend (1.0.4-1 to 1.0.4-2)
  • Migration status for curry-frontend (1.0.4-1 to 1.0.4-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curry-frontend.html
• curry-libs (2.1.0-1 to 2.2.0-1)
  • Migration status for curry-libs (2.1.0-1 to 2.2.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curry-libs.html
• curry-tools (2.1.0-1 to 2.2.0-1)
  • Migration status for curry-tools (2.1.0-1 to 2.2.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curry-tools.html
• fonts-material-design-icons-iconfont (- to 5.0.1-2)
  • Migration status for fonts-material-design-icons-iconfont (- to 5.0.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• fonts-tlwg (1:0.7.1-2 to 1:0.7.1-3)
  • Migration status for fonts-tlwg (1:0.7.1-2 to 1:0.7.1-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-tlwg.html
• georegression (- to 0.20+ds-2)
  • Migration status for georegression (- to 0.20+ds-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gfarm (2.7.11+dfsg-1.1 to 2.7.15+dfsg-1)
  • Migration status for gfarm (2.7.11+dfsg-1.1 to 2.7.15+dfsg-1): Waiting for test results, 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/gfarm.html
• gnumach (2:1.8+git20191029-1 to 2:1.8+git20191117-1)
  • Migration status for gnumach (2:1.8+git20191029-1 to 2:1.8+git20191117-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• golang-github-hashicorp-go-discover (- to 0.0+git20190905.34a6505-2)
  • Migration status for golang-github-hashicorp-go-discover (- to 0.0+git20190905.34a6505-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• golang-github-hetznercloud-hcloud-go (1.15.1-1 to 1.17.0-1)
  • Migration status for golang-github-hetznercloud-hcloud-go (1.15.1-1 to 1.17.0-1): Waiting for test results, 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-hetznercloud-hcloud-go.html
  • Required age reduced by 3 days because of autopkgtest
• golang-github-seccomp-containers-golang (- to 0.3.1-2)
  • Migration status for golang-github-seccomp-containers-golang (- to 0.3.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• googleplay-api (0.4.3-1 to 0.4.3-2)
  • Migration status for googleplay-api (0.4.3-1 to 0.4.3-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/googleplay-api.html
• gtk2-engines-murrine (0.98.2-2 to 0.98.2-3)
  • Migration status for gtk2-engines-murrine (0.98.2-2 to 0.98.2-3): Waiting for test results, 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 gtk2-engines-murrine fixes old bugs: #623783
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk2-engines-murrine.html
• jellyfish (2.3.0-2 to 2.3.0-3)
  • Migration status for jellyfish (2.3.0-2 to 2.3.0-3): Waiting for test results, 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 jellyfish fixes old bugs: #941920
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jellyfish.html
  • Required age reduced by 3 days because of autopkgtest
• jumpnbump-levels (20140925 to 20191111)
  • Migration status for jumpnbump-levels (20140925 to 20191111): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jumpnbump-levels.html
• kicad (5.1.4+dfsg1-2 to 5.1.5+dfsg1-1)
  • Migration status for kicad (5.1.4+dfsg1-2 to 5.1.5+dfsg1-1): Waiting for test results, 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/kicad.html
  • Required age reduced by 3 days because of autopkgtest
• kicad-footprints (5.1.3-1 to 5.1.5-1)
  • Migration status for kicad-footprints (5.1.3-1 to 5.1.5-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad-footprints.html
• kicad-packages3d (5.1.3-1 to 5.1.5-1)
  • Migration status for kicad-packages3d (5.1.3-1 to 5.1.5-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad-packages3d.html
• kicad-symbols (5.1.3-1 to 5.1.5-1)
  • Migration status for kicad-symbols (5.1.3-1 to 5.1.5-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad-symbols.html
• kicad-templates (5.1.3-1 to 5.1.5-1)
  • Migration status for kicad-templates (5.1.3-1 to 5.1.5-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad-templates.html
• kmetronome (1.0.0-3 to 1.0.1-1)
  • Migration status for kmetronome (1.0.0-3 to 1.0.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmetronome.html
• kwartz-client (- to 1.4-1)
  • Migration status for kwartz-client (- to 1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/k/kwartz-client.html
  • Too young, only 1 of 5 days old
• lame (3.100-2 to 3.100-3)
  • Migration status for lame (3.100-2 to 3.100-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lame.html
• ldb (2:2.0.7-3 to 2:2.0.7-4)
  • Migration status for ldb (2:2.0.7-3 to 2:2.0.7-4): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldb.html
• libbio-db-biofetch-perl (- to 1.7.3-2)
  • Migration status for libbio-db-biofetch-perl (- to 1.7.3-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• libbio-db-gff-perl (- to 1.7.3-2)
  • Migration status for libbio-db-gff-perl (- to 1.7.3-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• libbio-db-seqfeature-perl (- to 1.7.3-2)
  • Migration status for libbio-db-seqfeature-perl (- to 1.7.3-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• libbio-searchio-hmmer-perl (- to 1.7.3-2)
  • Migration status for libbio-searchio-hmmer-perl (- to 1.7.3-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• libbio-tools-run-remoteblast-perl (- to 1.7.3-2)
  • Migration status for libbio-tools-run-remoteblast-perl (- to 1.7.3-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• libdata-page-perl (2.02-2 to 2.03-1)
  • Migration status for libdata-page-perl (2.02-2 to 2.03-1): Waiting for test results, 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/libdata-page-perl.html
  • Required age reduced by 3 days because of autopkgtest
• libhtml-tagset-perl (3.20-3 to 3.20-4)
  • Migration status for libhtml-tagset-perl (3.20-3 to 3.20-4): Waiting for test results, 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/libh/libhtml-tagset-perl.html
  • Required age reduced by 3 days because of autopkgtest
• libnet-ssleay-perl (1.88-1 to 1.88-2)
  • Migration status for libnet-ssleay-perl (1.88-1 to 1.88-2): Waiting for test results, 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/libn/libnet-ssleay-perl.html
  • Required age reduced by 3 days because of autopkgtest
• libprelude (4.1.0-4.2 to 5.1.1-4)
  • Migration status for libprelude (4.1.0-4.2 to 5.1.1-4): Waiting for test results, 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 libprelude fixes old bugs: #944580
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libprelude.html
• libpreludedb (- to 5.1.0-3)
  • Migration status for libpreludedb (- to 5.1.0-3): Waiting for test results, 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/libpreludedb.html
• libtap-parser-sourcehandler-pgtap-perl (3.34-2 to 3.35-2)
  • Migration status for libtap-parser-sourcehandler-pgtap-perl (3.34-2 to 3.35-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtap-parser-sourcehandler-pgtap-perl.html
  • Required age reduced by 3 days because of autopkgtest
• localechooser (2.85 to 2.86)
  • Migration status for localechooser (2.85 to 2.86): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• lollypop (1.2.12-1 to 1.2.13-1)
  • Migration status for lollypop (1.2.12-1 to 1.2.13-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lollypop.html
• lunzip (1.11-6 to 1.11-7)
  • Migration status for lunzip (1.11-6 to 1.11-7): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lunzip.html
• lzd (1.1-4 to 1.1-5)
  • Migration status for lzd (1.1-4 to 1.1-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lzd.html
• lzip (1.21-4 to 1.21-5)
  • Migration status for lzip (1.21-4 to 1.21-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lzip.html
• lziprecover (1.21-5 to 1.21-6)
  • Migration status for lziprecover (1.21-5 to 1.21-6): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lziprecover.html
• lzlib (1.11-4 to 1.11-5)
  • Migration status for lzlib (1.11-4 to 1.11-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lzlib.html
• mesa (19.2.3-1 to 19.2.4-1)
  • Migration status for mesa (19.2.3-1 to 19.2.4-1): Waiting for test results, 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/mesa.html
• minetest (5.0.1+repack-2 to 5.1.0+repack-1)
  • Migration status for minetest (5.0.1+repack-2 to 5.1.0+repack-1): Waiting for test results, 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/minetest.html
• mmtf-java (1.0.9-3 to 1.0.9-4)
  • Migration status for mmtf-java (1.0.9-3 to 1.0.9-4): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• mpg123 (1.25.12-1 to 1.25.13-1)
  • Migration status for mpg123 (1.25.12-1 to 1.25.13-1): Waiting for test results, 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/mpg123.html
• mysql-workbench (- to 8.0.18+dfsg-1)
  • Migration status for mysql-workbench (- to 8.0.18+dfsg-1): Waiting for test results, 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/mysql-workbench.html
• nageru (1.9.0-2 to 1.9.1-1)
  • Migration status for nageru (1.9.0-2 to 1.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sesse
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nageru.html
• nextcloud-desktop (2.6.0-1 to 2.6.1-1)
  • Migration status for nextcloud-desktop (2.6.0-1 to 2.6.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nextcloud-desktop.html
• notepadqq (- to 2.0.0~beta1-1)
  • Migration status for notepadqq (- to 2.0.0~beta1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by jonathan@bluemosh.com
  • Too young, only 1 of 7 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• numix-gtk-theme (- to 2.6.7-5)
  • Migration status for numix-gtk-theme (- to 2.6.7-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numix-gtk-theme.html
• numix-icon-theme (0~20180717-1 to 0~20190920-1)
  • Migration status for numix-icon-theme (0~20180717-1 to 0~20190920-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numix-icon-theme.html
• numpy (- to 1:1.17.4-3)
  • Migration status for numpy (- to 1:1.17.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for gammapy/0.13-1: amd64: Regression ♻
  • autopkgtest for pandas/0.23.3+dfsg-8: amd64: Regression ♻
  • autopkgtest for python-scipy/1.2.2-7: amd64: Regression ♻
  • autopkgtest for python-skbio/0.5.5-2: amd64: Regression ♻
  • autopkgtest for skimage/0.14.2-3: amd64: Regression ♻
  • autopkgtest for yt/3.5.1-1: amd64: Regression ♻
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• open-infrastructure-compute-tools (20190811-1 to 20191104-1)
  • Migration status for open-infrastructure-compute-tools (20190811-1 to 20191104-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-infrastructure-compute-tools.html
• openbabel (2.4.1+dfsg-5.1 to 2.4.1+dfsg-6)
  • Migration status for openbabel (2.4.1+dfsg-5.1 to 2.4.1+dfsg-6): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openbabel.html
• openstack-meta-packages (0.26 to 0.27)
  • Migration status for openstack-meta-packages (0.26 to 0.27): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openstack-meta-packages.html
• partman-crypto (104 to 105)
  • Migration status for partman-crypto (104 to 105): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• pdlzip (1.10-5 to 1.10-6)
  • Migration status for pdlzip (1.10-5 to 1.10-6): Waiting for test results, 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/pdlzip.html
• petsc4py (3.11.0-2 to 3.11.0-3)
  • Migration status for petsc4py (3.11.0-2 to 3.11.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 1 of 2 days old
  • Additional info:
  • Updating petsc4py fixes old bugs: #942804
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/petsc4py.html
  • Required age reduced by 3 days because of autopkgtest
• pgbackrest (2.18-1 to 2.19-1)
  • Migration status for pgbackrest (2.18-1 to 2.19-1): Waiting for test results, 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/pgbackrest.html
  • Required age reduced by 3 days because of autopkgtest
• php-elisp (1.22.0-1 to 1.22.1-2)
  • Migration status for php-elisp (1.22.0-1 to 1.22.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-elisp.html
  • Required age reduced by 3 days because of autopkgtest
• pkg-js-tools (0.9.18 to 0.9.19)
  • Migration status for pkg-js-tools (0.9.18 to 0.9.19): Waiting for test results, 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/pkg-js-tools.html
  • Required age reduced by 3 days because of autopkgtest
• pkgsel (0.67 to 0.68)
  • Migration status for pkgsel (0.67 to 0.68): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• plzip (1.8-4 to 1.8-5)
  • Migration status for plzip (1.8-4 to 1.8-5): Waiting for test results, 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/plzip.html
• postgresql-12 (12.0-1 to 12.1-1)
  • Migration status for postgresql-12 (12.0-1 to 12.1-1): Waiting for test results, 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/postgresql-12.html
  • Required age reduced by 3 days because of autopkgtest
• psycopg2 (2.8.3-2 to 2.8.4-1)
  • Migration status for psycopg2 (2.8.3-2 to 2.8.4-1): Waiting for test results, 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/psycopg2.html
  • Required age reduced by 3 days because of autopkgtest
• pycifrw (- to 4.4-2)
  • Migration status for pycifrw (- to 4.4-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• pyfribidi (0.12.0+repack-2 to 0.12.0+repack-3)
  • Migration status for pyfribidi (0.12.0+repack-2 to 0.12.0+repack-3): Waiting for test results, 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 pyfribidi fixes old bugs: #944939
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfribidi.html
  • Required age reduced by 3 days because of autopkgtest
• python-botocore (1.12.241+repack-2 to 1.13.19+repack-1)
  • Migration status for python-botocore (1.12.241+repack-2 to 1.13.19+repack-1): Waiting for test results, 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
• python-crayons (- to 0.3.0-1)
  • Migration status for python-crayons (- to 0.3.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-crypto (2.6.1-12 to 2.6.1-13)
  • Migration status for python-crypto (2.6.1-12 to 2.6.1-13): Waiting for test results, 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-crypto.html
  • Required age reduced by 3 days because of autopkgtest
• python-defaults (2.7.17-1 to 2.7.17-2)
  • Migration status for python-defaults (2.7.17-1 to 2.7.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libxml2/2.9.4+dfsg1-7: amd64: Regression ♻
  • Too young, only 1 of 5 days old
  • Additional info:
  • Updating python-defaults fixes old bugs: #944894
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-defaults.html
• python-dnaio (0.3-2 to 0.4.1-1)
  • Migration status for python-dnaio (0.3-2 to 0.4.1-1): Waiting for test results, 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-dnaio.html
  • Required age reduced by 3 days because of autopkgtest
• python-fuse (2:1.0.0-1 to 2:1.0.0-2)
  • Migration status for python-fuse (2:1.0.0-1 to 2:1.0.0-2): Waiting for test results, 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-fuse fixes old bugs: #944946
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fuse.html
• python-git (3.0.4-1 to 3.0.5-1)
  • Migration status for python-git (3.0.4-1 to 3.0.5-1): Waiting for test results, 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-git.html
• python-mox (0.7.8-2 to 0.7.8-3)
  • Migration status for python-mox (0.7.8-2 to 0.7.8-3): Waiting for test results, 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-mox.html
  • Required age reduced by 3 days because of autopkgtest
• python-popcon (2.0.0 to 2.0.1)
  • Migration status for python-popcon (2.0.0 to 2.0.1): Waiting for test results, 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-popcon.html
• python-portend (- to 2.5-1)
  • Migration status for python-portend (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-project-generator (0.9.15-1 to 0.9.16-1)
  • Migration status for python-project-generator (0.9.15-1 to 0.9.16-1): Waiting for test results, 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-project-generator.html
  • Required age reduced by 3 days because of autopkgtest
• python-pulp (1.6.0+dfsg1-4 to 1.6.0+dfsg1-5)
  • Migration status for python-pulp (1.6.0+dfsg1-4 to 1.6.0+dfsg1-5): Waiting for test results, 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-pulp fixes old bugs: #944160
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pulp.html
• python-pyani (- to 0.2.9-1)
  • Migration status for python-pyani (- to 0.2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-xarray (0.14.0-1 to 0.14.0-2)
  • Migration status for python-xarray (0.14.0-1 to 0.14.0-2): Waiting for test results, 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-xarray fixes old bugs: #944044
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xarray.html
• pytools (2019.1.1-1 to 2019.1.1-2)
  • Migration status for pytools (2019.1.1-1 to 2019.1.1-2): Waiting for test results, 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/pytools.html
• quakespasm (0.93.1+dfsg-1 to 0.93.2+dfsg-1)
  • Migration status for quakespasm (0.93.1+dfsg-1 to 0.93.2+dfsg-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quakespasm.html
• quiterss (0.18.12+dfsg-1 to 0.19.1+dfsg-1)
  • Migration status for quiterss (0.18.12+dfsg-1 to 0.19.1+dfsg-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quiterss.html
• rpl (1.6.1-4 to 1.6.3-1)
  • Migration status for rpl (1.6.1-4 to 1.6.3-1): Waiting for test results, 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/rpl.html
  • Required age reduced by 3 days because of autopkgtest
• ruby-murmurhash3 (- to 0.1.6-1)
  • Migration status for ruby-murmurhash3 (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by srud@openmailbox.org
  • Too young, only 1 of 2 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• rust-percent-encoding (1.0.1-1 to 2.1.0-2)
  • Migration status for rust-percent-encoding (1.0.1-1 to 2.1.0-2): Waiting for test results, 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-percent-encoding.html
  • Required age reduced by 3 days because of autopkgtest
• salt-pylint (2019.6.7-1 to 2019.6.7-2)
  • Migration status for salt-pylint (2019.6.7-1 to 2019.6.7-2): Waiting for test results, 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/salt-pylint.html
• samba (2:4.11.1+dfsg-2 to 2:4.11.1+dfsg-3)
  • Migration status for samba (2:4.11.1+dfsg-2 to 2:4.11.1+dfsg-3): Waiting for test results, 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/samba.html
  • Required age reduced by 3 days because of autopkgtest
• send2trash (1.5.0-1 to 1.5.0-2)
  • Migration status for send2trash (1.5.0-1 to 1.5.0-2): Waiting for test results, 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/send2trash.html
• seqan3 (- to 3.0.0+ds2-2)
  • Migration status for seqan3 (- to 3.0.0+ds2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for seqan3/3.0.0+ds2-2: amd64: Regression ♻
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• simka (- to 1.5.1-2)
  • Migration status for simka (- to 1.5.1-2): 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 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• smarty3 (3.1.33+20180830.1.3a78a21f+selfpack1-1 to 3.1.34+20190228.1.c9f0de05+selfpack1-1)
  • Migration status for smarty3 (3.1.33+20180830.1.3a78a21f+selfpack1-1 to 3.1.34+20190228.1.c9f0de05+selfpack1-1): Waiting for test results, 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/smarty3.html
• source-extractor (- to 2.25.0+ds-2)
  • Migration status for source-extractor (- to 2.25.0+ds-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • autopkgtest for sextractor: amd64: Test in progress
  • Too young, only 1 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• thawab (- to 4.1-2)
  • Migration status for thawab (- to 4.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• toil (3.20.0-1 to 3.21.0-1)
  • Migration status for toil (3.20.0-1 to 3.21.0-1): Waiting for test results, 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/toil.html
  • Required age reduced by 3 days because of autopkgtest
• trustedqsl (2.4.7-2 to 2.5.1-1)
  • Migration status for trustedqsl (2.4.7-2 to 2.5.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trustedqsl.html
• undertow (2.0.27-1 to 2.0.28-1)
  • Migration status for undertow (2.0.27-1 to 2.0.28-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/undertow.html
• unibilium (2.0.0-4 to 2.0.0-5)
  • Migration status for unibilium (2.0.0-4 to 2.0.0-5): Waiting for test results, 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/u/unibilium.html
  • Required age reduced by 3 days because of autopkgtest
• usbtop (0.2-1 to 1.0+dfsg-1)
  • Migration status for usbtop (0.2-1 to 1.0+dfsg-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/usbtop.html
• vitrage-dashboard (- to 2.0.0-1)
  • Migration status for vitrage-dashboard (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by arbet.michal@gmail.com, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• vtkplotter (- to 2019.1.2-3)
  • Migration status for vtkplotter (- to 2019.1.2-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• wah-plugins (0.1.0-4 to 0.1.0-5)
  • Migration status for wah-plugins (0.1.0-4 to 0.1.0-5): Waiting for test results, 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/w/wah-plugins.html
• wavbreaker (0.11-1 to 0.11-2)
  • Migration status for wavbreaker (0.11-1 to 0.11-2): Waiting for test results, 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/w/wavbreaker.html
• whois (5.5.2 to 5.5.3)
  • Migration status for whois (5.5.2 to 5.5.3): Waiting for test results, 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/w/whois.html
• arandr (- to 0.1.10-1)
  • Migration status for arandr (- to 0.1.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by rhonda, 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/a/arandr.html
• armagetronad (0.2.8.3.4-2 to 0.2.8.3.4-3)
  • Migration status for armagetronad (0.2.8.3.4-2 to 0.2.8.3.4-3): Waiting for test results, 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/armagetronad.html
• cctools (7.0.9-3 to 7.0.9-5)
  • Migration status for cctools (7.0.9-3 to 7.0.9-5): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cctools.html
• chemical-structures (2.2.dfsg.0-13 to 2.2.dfsg.0-15)
  • Migration status for chemical-structures (2.2.dfsg.0-13 to 2.2.dfsg.0-15): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chemical-structures.html
• clonezilla (3.27.16-3 to 3.35.2-1)
  • Migration status for clonezilla (3.27.16-3 to 3.35.2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clonezilla.html
• cvxopt (1.1.9+dfsg-3 to 1.2.3+dfsg-2)
  • Migration status for cvxopt (1.1.9+dfsg-3 to 1.2.3+dfsg-2): Waiting for test results, 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 cvxopt fixes old bugs: #933281
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvxopt.html
• duplicity (0.8.05-2 to 0.8.07-1)
  • Migration status for duplicity (0.8.05-2 to 0.8.07-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 mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/duplicity.html
• erofs-utils (- to 1.0-3)
  • Migration status for erofs-utils (- to 1.0-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• exim4 (4.92.3-1 to 4.93~RC3-1)
  • Migration status for exim4 (4.92.3-1 to 4.93~RC3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating exim4 introduces new bugs: #944481
  • Too young, only 2 of 7 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/exim4.html
  • Required age reduced by 3 days because of autopkgtest
• fasm (1.73.17-1 to 1.73.18-1)
  • Migration status for fasm (1.73.17-1 to 1.73.18-1): Waiting for test results, 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/fasm.html
• flatzebra (0.1.6-5 to 0.1.7-1)
  • Migration status for flatzebra (0.1.6-5 to 0.1.7-1): Waiting for test results, 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/flatzebra.html
• fontforge (1:20170731~dfsg-2 to 1:20190801~dfsg-2)
  • Migration status for fontforge (1:20170731~dfsg-2 to 1:20190801~dfsg-2): Waiting for test results, 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/fontforge.html
• fonts-bajaderka (- to 1.0-1)
  • Migration status for fonts-bajaderka (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by kilobyte, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• fonts-breip (1:0.5.1-2 to 1:0.5.1-3)
  • Migration status for fonts-breip (1:0.5.1-2 to 1:0.5.1-3): Waiting for test results, 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/fonts-breip.html
• fonts-ipaexfont (00401-1 to 00401-2)
  • Migration status for fonts-ipaexfont (00401-1 to 00401-2): Waiting for test results, 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/fonts-ipaexfont.html
• fonts-ricty-diminished (4.1.1-2 to 4.1.1-3)
  • Migration status for fonts-ricty-diminished (4.1.1-2 to 4.1.1-3): Waiting for test results, 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/fonts-ricty-diminished.html
• freeplane (1.7.9-1 to 1.7.10-1)
  • Migration status for freeplane (1.7.9-1 to 1.7.10-1): Waiting for test results, 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/freeplane.html
• g15daemon (- to 1.9.5.3-10)
  • Migration status for g15daemon (- to 1.9.5.3-10): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• git-mestrelion-tools (2018.10-1 to 2019.10-1)
  • Migration status for git-mestrelion-tools (2018.10-1 to 2019.10-1): Waiting for test results, 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/git-mestrelion-tools.html
• hivex (1.3.18-1 to 1.3.18-2)
  • Migration status for hivex (1.3.18-1 to 1.3.18-2): Waiting for test results, 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/hivex.html
• https-everywhere (2019.6.27-2 to 2019.11.7-1)
  • Migration status for https-everywhere (2019.6.27-2 to 2019.11.7-1): Waiting for test results, 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/https-everywhere.html
• ipdb (0.11-1 to 0.12.2-1)
  • Migration status for ipdb (0.11-1 to 0.12.2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipdb.html
• libg15 (- to 1.3.0~svn324-1)
  • Migration status for libg15 (- to 1.3.0~svn324-1): Waiting for test results, 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/libg15.html
• libt3highlight (0.4.8-1 to 0.4.9-1)
  • Migration status for libt3highlight (0.4.8-1 to 0.4.9-1): Waiting for test results, 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/libt/libt3highlight.html
• libtest-diaginc-perl (- to 0.008-2)
  • Migration status for libtest-diaginc-perl (- to 0.008-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• lincredits (0.7+nmu1 to 0.8)
  • Migration status for lincredits (0.7+nmu1 to 0.8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by lawrencc, 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/l/lincredits.html
• manpages-de (2.15-1 to 2.16-1)
  • Migration status for manpages-de (2.15-1 to 2.16-1): Waiting for test results, 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/manpages-de.html
• omgifol (- to 0.4.0-2)
  • Migration status for omgifol (- to 0.4.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• opencpn (- to 4.8.8+dfsg.2-1)
  • Migration status for opencpn (- to 4.8.8+dfsg.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • opencpn-plugins/i386 unsatisfiable Depends: opencpn (>= 4.8.6~20180801.8d20a06+dfsg.1)
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Impossible Depends: opencpn -> wxwidgets3.0/amd64
• palabos (1.5~r1+repack1-4 to 1.5~r1+repack1-5)
  • Migration status for palabos (1.5~r1+repack1-4 to 1.5~r1+repack1-5): Waiting for test results, 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/palabos.html
• peruse (- to 1.2+dfsg+20191117-1)
  • Migration status for peruse (- to 1.2+dfsg+20191117-1): Waiting for test results, 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/peruse.html
• piper (- to 0.3-1)
  • Migration status for piper (- to 0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by steve@sk2.org, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• pygrace (0.5-2 to 0.6-2)
  • Migration status for pygrace (0.5-2 to 0.6-2): Waiting for test results, 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/pygrace.html
• pymeeus (- to 0.3.6-2)
  • Migration status for pymeeus (- to 0.3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by anarcat@koumbit.org, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• pyrsistent (0.15.4-3 to 0.15.5-1)
  • Migration status for pyrsistent (0.15.4-3 to 0.15.5-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 mipsel
  • missing build on ppc64el
  • missing build on s390x
  • 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)
• pyside2 (5.11.2-3 to 5.13.2-1)
  • Migration status for pyside2 (5.11.2-3 to 5.13.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for freecad/0.18.4+dfsg1-1: amd64: Regression ♻
  • pyside2 unsatisfiable Build-Depends(-Arch) on mips64el: libqt5datavisualization5-dev
  • pyside2 unsatisfiable Build-Depends(-Arch) on mipsel: libqt5datavisualization5-dev
  • Not built on buildd: arch amd64 binaries uploaded by hertzog
  • Not built on buildd: arch all binaries uploaded by hertzog, a new source-only upload is needed to allow migration
  • missing build on arm64
  • missing build on armel
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyside2.html
• python-debianbts (2.8.2 to 3.0.2)
  • Migration status for python-debianbts (2.8.2 to 3.0.2): Waiting for test results, 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-debianbts.html
• python-pygit2 (0.27.4-2 to 0.28.2-2)
  • Migration status for python-pygit2 (0.27.4-2 to 0.28.2-2): Waiting for test results, 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 python-pygit2 fixes old bugs: #931698
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pygit2.html
• python-vulndb (0.1.1-1 to 0.1.3-2)
  • Migration status for python-vulndb (0.1.1-1 to 0.1.3-2): Waiting for test results, 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-vulndb.html
• pywws (18.10.1-1 to 19.7.1-1)
  • Migration status for pywws (18.10.1-1 to 19.7.1-1): Waiting for test results, 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/pywws.html
• qpdf (9.0.1-1 to 9.1.0-1)
  • Migration status for qpdf (9.0.1-1 to 9.1.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpdf.html
• qutip (- to 4.4.1-2)
  • Migration status for qutip (- to 4.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for qutip/4.4.1-2: amd64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by dparsons
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• r-cran-rcppeigen (0.3.3.5.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen (0.3.3.5.0-1 to 0.3.3.7.0-1): Waiting for test results, 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/r-cran-rcppeigen.html
• resfinder (- to 3.2-1)
  • Migration status for resfinder (- to 3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for resfinder/3.2-1: amd64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• resfinder-db (- to 0.0+git20191001.149209d-1)
  • Migration status for resfinder-db (- to 0.0+git20191001.149209d-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
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• ruby-i18n-data (- to 0.10.0-1)
  • Migration status for ruby-i18n-data (- 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 srud@openmailbox.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 2 days old (needed 2 days)
• rust-ansi-term (0.11.0-1 to 0.12.1-1)
  • Migration status for rust-ansi-term (0.11.0-1 to 0.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-lscolors/0.5.0-2: amd64: Regression ♻
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ansi-term.html
• rust-bincode (1.0.1-1 to 1.2.0-1)
  • Migration status for rust-bincode (1.0.1-1 to 1.2.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bincode.html
• rust-exa (- to 0.9.0-1)
  • Migration status for rust-exa (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-exa/0.9.0-1: amd64: Regression ♻
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-exa.html
• rust-getrandom (0.1.6-1 to 0.1.13-3)
  • Migration status for rust-getrandom (0.1.6-1 to 0.1.13-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/rust-getrandom.html
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • uninstallable on arch amd64, autopkgtest delayed there
  • Too young, only 2 of 5 days old
  • Additional info:
  • librust-getrandom+compiler-builtins-dev/amd64 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+compiler-builtins-dev/arm64 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+compiler-builtins-dev/armel unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+compiler-builtins-dev/armhf unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+compiler-builtins-dev/i386 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+compiler-builtins-dev/mips64el unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+compiler-builtins-dev/mipsel unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+compiler-builtins-dev/ppc64el unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+compiler-builtins-dev/s390x unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/amd64 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/arm64 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/armel unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/armhf unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/i386 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/mips64el unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/mipsel unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/ppc64el unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
  • librust-getrandom+rustc-dep-of-std-dev/s390x unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev
• rust-git2 (0.7.5-1 to 0.10.1-1)
  • Migration status for rust-git2 (0.7.5-1 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-git2/0.10.1-1: amd64: Regression ♻
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-git2.html
• rust-lazy-static (1.3.0-1 to 1.4.0-1)
  • Migration status for rust-lazy-static (1.3.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-tokio-threadpool/0.1.16-1: amd64: Regression ♻
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lazy-static.html
• schism (2:20190805-1 to 2:20190805-2)
  • Migration status for schism (2:20190805-1 to 2:20190805-2): Waiting for test results, 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/schism.html
• sysfsutils (2.1.0+repack-5 to 2.1.0+repack-6)
  • Migration status for sysfsutils (2.1.0+repack-5 to 2.1.0+repack-6): Waiting for test results, 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/sysfsutils.html
• tevent (0.10.1-3 to 0.10.1-4)
  • Migration status for tevent (0.10.1-3 to 0.10.1-4): Waiting for test results, 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/tevent.html
• texstudio (2.12.14+debian-1 to 2.12.16+debian-1)
  • Migration status for texstudio (2.12.14+debian-1 to 2.12.16+debian-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tom@cryptography.ch
  • Not built on buildd: arch all binaries uploaded by tom@cryptography.ch, 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/t/texstudio.html
• toxic (- to 0.8.3-1)
  • Migration status for toxic (- to 0.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kilobyte
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• tutka (1.1.3-1 to 1.1.3-2)
  • Migration status for tutka (1.1.3-1 to 1.1.3-2): Waiting for test results, 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/tutka.html
• wesnoth-1.14 (1:1.14.7-1 to 1:1.14.9-1)
  • Migration status for wesnoth-1.14 (1:1.14.7-1 to 1:1.14.9-1): Waiting for test results, 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/w/wesnoth-1.14.html
• wxglade (0.8.3-2 to 0.9.4-1)
  • Migration status for wxglade (0.8.3-2 to 0.9.4-1): Waiting for test results, 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/w/wxglade.html
• yoshimi (1.6.0-1 to 1.6.0.2-1)
  • Migration status for yoshimi (1.6.0-1 to 1.6.0.2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yoshimi.html
• zabbix (1:4.0.11+dfsg-1 to 1:4.0.14+dfsg-1)
  • Migration status for zabbix (1:4.0.11+dfsg-1 to 1:4.0.14+dfsg-1): Waiting for test results, 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/z/zabbix.html
• aglfn (1.7-3 to 1.7+git20191031.4036a9c-1)
  • Migration status for aglfn (1.7-3 to 1.7+git20191031.4036a9c-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aglfn.html
• arch-install-scripts (22-1 to 23-1)
  • Migration status for arch-install-scripts (22-1 to 23-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arch-install-scripts.html
• astromatic (1.1 to 1.2)
  • Migration status for astromatic (1.1 to 1.2): Waiting for test results, 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/a/astromatic.html
• astrometry.net (0.78+dfsg-2 to 0.78+dfsg-3)
  • Migration status for astrometry.net (0.78+dfsg-2 to 0.78+dfsg-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 7 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astrometry.net.html
  • Required age reduced by 3 days because of autopkgtest
• bookletimposer (0.2-5 to 0.3~beta1-1)
  • Migration status for bookletimposer (0.2-5 to 0.3~beta1-1): Waiting for test results, 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/bookletimposer.html
• branca (- to 0.3.1-4)
  • Migration status for branca (- to 0.3.1-4): Waiting for test results, 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)
• calligra (1:3.1.0+dfsg-5 to 1:3.1.0+dfsg-6)
  • Migration status for calligra (1:3.1.0+dfsg-5 to 1:3.1.0+dfsg-6): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Updating calligra fixes old bugs: #944853
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calligra.html
• calligraplan (1:3.1.0-3 to 1:3.2.0-1)
  • Migration status for calligraplan (1:3.1.0-3 to 1:3.2.0-1): Waiting for test results, 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/calligraplan.html
• car (3.0-4-1 to 3.0-5-1)
  • Migration status for car (3.0-4-1 to 3.0-5-1): Waiting for test results, 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/car.html
• connectome-workbench (1.3.2-1 to 1.4.1-4)
  • Migration status for connectome-workbench (1.3.2-1 to 1.4.1-4): Waiting for test results, 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/connectome-workbench.html
• debian-installer (20190702+deb10u1 to 20190702+deb10u2)
  • Migration status for debian-installer (20190702+deb10u1 to 20190702+deb10u2): Waiting for test results, 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/debian-installer.html
• debian-installer-netboot-images (20190702+deb10u1 to 20190702+deb10u2)
  • Migration status for debian-installer-netboot-images (20190702+deb10u1 to 20190702+deb10u2): Waiting for test results, 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/debian-installer-netboot-images.html
• debian-security-support (2019.11.01 to 2019.11.16)
  • Migration status for debian-security-support (2019.11.01 to 2019.11.16): Waiting for test results, 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/debian-security-support.html
• deepin-terminal (3.2.1.1+ds1-1 to 5.0.0+ds1-1)
  • Migration status for deepin-terminal (3.2.1.1+ds1-1 to 5.0.0+ds1-1): Waiting for test results, 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/deepin-terminal.html
• effects (4.1.3-1 to 4.1.4-1)
  • Migration status for effects (4.1.3-1 to 4.1.4-1): Waiting for test results, 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/effects.html
• fcitx (1:4.2.9.6-6 to 1:4.2.9.7-1)
  • Migration status for fcitx (1:4.2.9.6-6 to 1:4.2.9.7-1): Waiting for test results, 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/fcitx.html
• flawfinder (1.31-1 to 2.0.10-0.1)
  • Migration status for flawfinder (1.31-1 to 2.0.10-0.1): Waiting for test results, 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/flawfinder.html
• fonts-sil-mingzat (- to 1.000-2)
  • Migration status for fonts-sil-mingzat (- to 1.000-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by fabian@greffrath.com, a new source-only upload is needed to allow migration
  • Too young, only 3 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• git-quick-stats (- to 2.0.11-1)
  • Migration status for git-quick-stats (- to 2.0.11-1): Waiting for test results, 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)
• gnuradio (3.8.0.0-5 to 3.8.0.0-6)
  • Migration status for gnuradio (3.8.0.0-5 to 3.8.0.0-6): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Updating gnuradio fixes old bugs: #943965
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnuradio.html
• gr-fosphor (3.8~1.278b66e-2 to 3.8~1.278b66e-3)
  • Migration status for gr-fosphor (3.8~1.278b66e-2 to 3.8~1.278b66e-3): Waiting for test results, 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/gr-fosphor.html
• iwd (0.23-1 to 1.1-1)
  • Migration status for iwd (0.23-1 to 1.1-1): Waiting for test results, 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/iwd.html
• libcgns (3.3.0-6 to 3.3.0-7)
  • Migration status for libcgns (3.3.0-6 to 3.3.0-7): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Updating libcgns fixes old bugs: #944127
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcgns.html
• libiio (0.18-1 to 0.18-2)
  • Migration status for libiio (0.18-1 to 0.18-2): Waiting for test results, 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/libi/libiio.html
• libkolabxml (1.1.6-4 to 1.1.6-5)
  • Migration status for libkolabxml (1.1.6-4 to 1.1.6-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 3 of 5 days old
  • Additional info:
  • Updating libkolabxml fixes old bugs: #925748
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkolabxml.html
• libseccomp (2.4.1-2 to 2.4.2-2)
  • Migration status for libseccomp (2.4.1-2 to 2.4.2-2): Waiting for test results, 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/libs/libseccomp.html
• libt3config (0.2.11-1 to 1.0.0-1)
  • Migration status for libt3config (0.2.11-1 to 1.0.0-1): Waiting for test results, 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/libt/libt3config.html
• mailscripts (0.13-1 to 0.14-1)
  • Migration status for mailscripts (0.13-1 to 0.14-1): Waiting for test results, 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/mailscripts.html
• mingw-w64 (6.0.0-4 to 7.0.0-2)
  • Migration status for mingw-w64 (6.0.0-4 to 7.0.0-2): Waiting for test results, 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/mingw-w64.html
• msitools (0.99-2 to 0.100-1)
  • Migration status for msitools (0.99-2 to 0.100-1): Waiting for test results, 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/msitools.html
• nosexcover (1.0.11-1.1 to 1.0.11-1.2)
  • Migration status for nosexcover (1.0.11-1.1 to 1.0.11-1.2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Updating nosexcover fixes old bugs: #906083, #937159
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nosexcover.html
• nvidia-graphics-drivers (430.50-2 to 430.64-1)
  • Migration status for nvidia-graphics-drivers (430.50-2 to 430.64-1): Waiting for test results, 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)
• nvidia-settings (430.50-1 to 430.64-1)
  • Migration status for nvidia-settings (430.50-1 to 430.64-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • nvidia-settings/ppc64el unsatisfiable Depends: nvidia-tesla-alternative
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvidia-settings.html
• odil (0.10.0-7 to 0.10.0-9)
  • Migration status for odil (0.10.0-7 to 0.10.0-9): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odil.html
• packmol (- to 18.169-2)
  • Migration status for packmol (- to 18.169-2): Waiting for test results, 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)
• php-monolog (1.25.1-1 to 1.25.2-1)
  • Migration status for php-monolog (1.25.1-1 to 1.25.2-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-monolog.html
• php7.3 (7.3.10-1 to 7.3.11-1~deb10u1)
  • Migration status for php7.3 (7.3.10-1 to 7.3.11-1~deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by carnil
  • Additional info:
  • Updating php7.3 fixes old bugs: #943468
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php7.3.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
  • Impossible Depends: php7.3 -> net-snmp/amd64
  • Impossible Depends: php7.3 -> net-snmp/arm64
  • Impossible Depends: php7.3 -> net-snmp/armel
  • Impossible Depends: php7.3 -> net-snmp/armhf
  • Impossible Depends: php7.3 -> net-snmp/i386
  • Impossible Depends: php7.3 -> net-snmp/mips64el
  • Impossible Depends: php7.3 -> net-snmp/mipsel
  • Impossible Depends: php7.3 -> net-snmp/ppc64el
  • Impossible Depends: php7.3 -> net-snmp/s390x
• phpmyadmin-shapefile (- to 2.1-3)
  • Migration status for phpmyadmin-shapefile (- to 2.1-3): Waiting for test results, 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)
• phpmyadmin-sql-parser (- to 4.3.2-3)
  • Migration status for phpmyadmin-sql-parser (- to 4.3.2-3): Waiting for test results, 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)
• prelude-correlator (4.1.1-2 to 5.1.0+ds-2)
  • Migration status for prelude-correlator (4.1.1-2 to 5.1.0+ds-2): Waiting for test results, 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/prelude-correlator.html
• prelude-lml (- to 5.1.0-2)
  • Migration status for prelude-lml (- to 5.1.0-2): Waiting for test results, 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/prelude-lml.html
• prelude-lml-rules (4.1.0-1 to 5.1.0-2)
  • Migration status for prelude-lml-rules (4.1.0-1 to 5.1.0-2): Waiting for test results, 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/prelude-lml-rules.html
• prelude-manager (- to 5.1.0-2)
  • Migration status for prelude-manager (- to 5.1.0-2): Waiting for test results, 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/prelude-manager.html
• prewikka (- to 5.1.1-1)
  • Migration status for prewikka (- to 5.1.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • uninstallable on arch amd64, autopkgtest delayed there
  • Too young, only 3 of 5 days old
  • Additional info:
  • prewikka/amd64 unsatisfiable Depends: python3-lark-parser
  • prewikka/i386 unsatisfiable Depends: python3-lark-parser
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prewikka.html
• propellor (5.9.1-1 to 5.10.1-1)
  • Migration status for propellor (5.9.1-1 to 5.10.1-1): Waiting for test results, 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/propellor.html
• pycairo (1.16.2-1 to 1.16.2-2)
  • Migration status for pycairo (1.16.2-1 to 1.16.2-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Updating pycairo fixes old bugs: #942666
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycairo.html
• python-kaptan (0.5.10-1 to 0.5.10-1.1)
  • Migration status for python-kaptan (0.5.10-1 to 0.5.10-1.1): Waiting for test results, 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-kaptan.html
• python-lesscpy (0.13.0+ds-1 to 0.13.0+ds-2)
  • Migration status for python-lesscpy (0.13.0+ds-1 to 0.13.0+ds-2): Waiting for test results, 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-lesscpy.html
• python-libtmux (0.8.0-1 to 0.8.0-1.1)
  • Migration status for python-libtmux (0.8.0-1 to 0.8.0-1.1): Waiting for test results, 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-libtmux.html
• r-cran-rmarkdown (1.15+dfsg-1 to 1.17+dfsg-1)
  • Migration status for r-cran-rmarkdown (1.15+dfsg-1 to 1.17+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for r-cran-rmarkdown/1.17+dfsg-1: amd64: Regression ♻
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rmarkdown.html
• rust-aes-soft (- to 0.3.3-1)
  • Migration status for rust-aes-soft (- to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rust-aes-soft unsatisfiable Build-Depends(-Arch) on amd64: librust-block-cipher-trait-0.6+default-dev
  • Not built on buildd: arch amd64 binaries uploaded by bugzilla@tut.by
  • uninstallable on arch amd64, autopkgtest delayed there
  • Too young, only 3 of 5 days old
  • Additional info:
  • librust-aes-soft-dev/amd64 unsatisfiable Depends: librust-block-cipher-trait-0.6+default-dev
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• rust-alsa-sys (- to 0.2.0-1)
  • Migration status for rust-alsa-sys (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bugzilla@tut.by
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• rust-libsodium-sys (- to 0.2.5-1)
  • Migration status for rust-libsodium-sys (- to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-libsodium-sys/0.2.5-1: amd64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Too young, only 3 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• rust-memoffset (0.2.1-1 to 0.5.3-1)
  • Migration status for rust-memoffset (0.2.1-1 to 0.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
  • Additional info:
  • Updating rust-memoffset fixes old bugs: #936025
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-memoffset.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• rust-signal-hook-registry (- to 1.1.1-1)
  • Migration status for rust-signal-hook-registry (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Too young, only 3 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• rust-universal-hash (- to 0.3.0-1)
  • Migration status for rust-universal-hash (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bugzilla@tut.by
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• s390-dasd (0.0.64 to 0.0.65)
  • Migration status for s390-dasd (0.0.64 to 0.0.65): Waiting for test results, 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)
• sardana (3.0.0a+3.f4f89e+dfsg-2 to 3.0.2a0+34.9f6895-1)
  • Migration status for sardana (3.0.0a+3.f4f89e+dfsg-2 to 3.0.2a0+34.9f6895-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sardana.html
• sight (- to 19.0.0-1)
  • Migration status for sight (- to 19.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Too young, only 3 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Impossible Depends: sight -> gdcm/amd64
  • Impossible Depends: sight -> insighttoolkit4/amd64
  • Impossible Depends: sight -> vtk7/amd64
  • Impossible Build-Depends(-Arch): sight -> vtk7/amd64
• snek (1.1-1.1 to 1.2-2)
  • Migration status for snek (1.1-1.1 to 1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • snek unsatisfiable Build-Depends(-Arch) on amd64: picolibc-arm-none-eabi (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on amd64: picolibc-riscv64-unknown-elf (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on armel: picolibc-arm-none-eabi (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on armel: picolibc-riscv64-unknown-elf (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on armhf: picolibc-arm-none-eabi (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on armhf: picolibc-riscv64-unknown-elf (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on i386: picolibc-arm-none-eabi (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on i386: picolibc-riscv64-unknown-elf (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on mips64el: picolibc-arm-none-eabi (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on mips64el: picolibc-riscv64-unknown-elf (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on mipsel: picolibc-arm-none-eabi (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on mipsel: picolibc-riscv64-unknown-elf (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on ppc64el: picolibc-arm-none-eabi (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on ppc64el: picolibc-riscv64-unknown-elf (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on s390x: picolibc-arm-none-eabi (>= 1.1)
  • snek unsatisfiable Build-Depends(-Arch) on s390x: picolibc-riscv64-unknown-elf (>= 1.1)
  • missing build on amd64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snek.html
• sshfs-fuse (2.10+repack-2 to 3.6.0+repack-1)
  • Migration status for sshfs-fuse (2.10+repack-2 to 3.6.0+repack-1): Waiting for test results, 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/sshfs-fuse.html
• suitesparse (1:5.4.0+dfsg-1 to 1:5.6.0+dfsg-2)
  • Migration status for suitesparse (1:5.4.0+dfsg-1 to 1:5.6.0+dfsg-2): Waiting for test results, 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/suitesparse.html
• taurus-pyqtgraph (- to 0.3.1-2)
  • Migration status for taurus-pyqtgraph (- to 0.3.1-2): Waiting for test results, 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)
• tlf (1.3.2-1 to 1.4.0-1)
  • Migration status for tlf (1.3.2-1 to 1.4.0-1): Waiting for test results, 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/tlf.html
• uprightdiff (- to 1.3.0-3)
  • Migration status for uprightdiff (- to 1.3.0-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uprightdiff.html
• uwsgi-apparmor (- to 0.0.0+git.2014.09.15.7d6d7bd7eb-2)
  • Migration status for uwsgi-apparmor (- to 0.0.0+git.2014.09.15.7d6d7bd7eb-2): Waiting for test results, 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)
• zope.i18nmessageid (4.0.3-2 to 5.0.0-1)
  • Migration status for zope.i18nmessageid (4.0.3-2 to 5.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for zope.i18nmessageid/5.0.0-1: amd64: Regression ♻
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zope.i18nmessageid.html
• akonadi (4:18.08.3-7 to 4:18.08.3-11)
  • Migration status for akonadi (4:18.08.3-7 to 4:18.08.3-11): Waiting for test results, 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/akonadi.html
• akonadi-calendar (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for akonadi-calendar (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/akonadi-calendar.html
• akonadi-calendar-tools (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for akonadi-calendar-tools (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/akonadi-calendar-tools.html
• akonadi-contacts (4:18.08.3-1 to 4:18.08.3-4)
  • Migration status for akonadi-contacts (4:18.08.3-1 to 4:18.08.3-4): Waiting for test results, 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/akonadi-contacts.html
• akonadi-import-wizard (4:18.08.3-1 to 4:18.08.3-4)
  • Migration status for akonadi-import-wizard (4:18.08.3-1 to 4:18.08.3-4): Waiting for test results, 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/akonadi-import-wizard.html
• akonadi-mime (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for akonadi-mime (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/akonadi-mime.html
• akonadi-notes (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for akonadi-notes (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/akonadi-notes.html
• akonadi-search (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for akonadi-search (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/akonadi-search.html
• akonadiconsole (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for akonadiconsole (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/akonadiconsole.html
• akregator (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for akregator (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/akregator.html
• apt-cacher-ng (3.2-3 to 3.3-2)
  • Migration status for apt-cacher-ng (3.2-3 to 3.3-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • missing build on mipsel
  • Too young, only 4 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-cacher-ng.html
• csv-mode (1.9-2 to 1.10-1)
  • Migration status for csv-mode (1.9-2 to 1.10-1): Waiting for test results, 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/csv-mode.html
• cyrus-imapd (3.0.11-1 to 3.0.12-1)
  • Migration status for cyrus-imapd (3.0.11-1 to 3.0.12-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • autopkgtest for cyrus-imapd: amd64: Test in progress
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cyrus-imapd.html
• dislocker (0.7.1-4 to 0.7.1-5)
  • Migration status for dislocker (0.7.1-4 to 0.7.1-5): Waiting for test results, 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/dislocker.html
• drascula (1.0+ds3-1 to 1.0+ds4-1)
  • Migration status for drascula (1.0+ds3-1 to 1.0+ds4-1): Waiting for test results, 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/drascula.html
• easymock (4.0.2-1 to 4.1-1)
  • Migration status for easymock (4.0.2-1 to 4.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/easymock.html
• elogind (241.3-1+debian1 to 241.3-1+debian2)
  • Migration status for elogind (241.3-1+debian1 to 241.3-1+debian2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elogind.html
• erlang-idna (- to 6.0.0-2)
  • Migration status for erlang-idna (- to 6.0.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• erlang-p1-acme (- to 1.0.2-2)
  • Migration status for erlang-p1-acme (- to 1.0.2-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• erlang-unicode-util-compat (- to 0.5.0-2)
  • Migration status for erlang-unicode-util-compat (- to 0.5.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gnudatalanguage (0.9.9-11 to 0.9.9-12)
  • Migration status for gnudatalanguage (0.9.9-11 to 0.9.9-12): Waiting for test results, 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/g/gnudatalanguage.html
  • Required age reduced by 3 days because of autopkgtest
• grantlee-editor (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for grantlee-editor (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/grantlee-editor.html
• hijra (- to 0.4.1-2)
  • Migration status for hijra (- to 0.4.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • uninstallable on arch amd64, autopkgtest delayed there
  • Too young, only 4 of 5 days old
  • Additional info:
  • gnome-shell-extension-hijra/amd64 unsatisfiable Depends: gnome-shell (<< 3.31)
  • gnome-shell-extension-hijra/i386 unsatisfiable Depends: gnome-shell (<< 3.31)
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• imapfilter (1:2.6.13-1 to 1:2.6.15-1)
  • Migration status for imapfilter (1:2.6.13-1 to 1:2.6.15-1): Waiting for test results, 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/imapfilter.html
• kaddressbook (4:18.08.3-3 to 4:18.08.3-5)
  • Migration status for kaddressbook (4:18.08.3-3 to 4:18.08.3-5): Waiting for test results, 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/kaddressbook.html
• kalarm (4:18.08.3-1 to 4:18.08.3-4)
  • Migration status for kalarm (4:18.08.3-1 to 4:18.08.3-4): Waiting for test results, 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/kalarm.html
• kalarmcal (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for kalarmcal (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/kalarmcal.html
• kblog (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for kblog (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/kblog.html
• kcalcore (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for kcalcore (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/kcalcore.html
• kcalutils (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for kcalutils (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/kcalutils.html
• kcontacts (4:18.08.3-1 to 4:18.08.3-4)
  • Migration status for kcontacts (4:18.08.3-1 to 4:18.08.3-4): Waiting for test results, 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/kcontacts.html
• kdav (18.08.3-2 to 18.08.3-4)
  • Migration status for kdav (18.08.3-2 to 18.08.3-4): Waiting for test results, 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/kdav.html
• kdepim-addons (18.08.3-2 to 18.08.3-4)
  • Migration status for kdepim-addons (18.08.3-2 to 18.08.3-4): Waiting for test results, 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/kdepim-addons.html
• kdepim-runtime (4:18.08.3-4 to 4:18.08.3-6)
  • Migration status for kdepim-runtime (4:18.08.3-4 to 4:18.08.3-6): Waiting for test results, 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/kdepim-runtime.html
• keyringer (0.5.3-1 to 0.5.5-1)
  • Migration status for keyringer (0.5.3-1 to 0.5.5-1): Waiting for test results, 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/keyringer.html
• kf5-kdepim-apps-libs (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for kf5-kdepim-apps-libs (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/kf5-kdepim-apps-libs.html
• kf5-messagelib (4:18.08.3-2 to 4:18.08.3-5)
  • Migration status for kf5-messagelib (4:18.08.3-2 to 4:18.08.3-5): Waiting for test results, 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/kf5-messagelib.html
• kgpg (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for kgpg (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/kgpg.html
• kidentitymanagement (18.08.3-2 to 18.08.3-4)
  • Migration status for kidentitymanagement (18.08.3-2 to 18.08.3-4): Waiting for test results, 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/kidentitymanagement.html
• kimap (18.08.3-1 to 18.08.3-3)
  • Migration status for kimap (18.08.3-1 to 18.08.3-3): Waiting for test results, 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/kimap.html
• kitinerary (18.08.3-2 to 18.08.3-4)
  • Migration status for kitinerary (18.08.3-2 to 18.08.3-4): Waiting for test results, 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/kitinerary.html
• kldap (18.08.3-1 to 18.08.3-3)
  • Migration status for kldap (18.08.3-1 to 18.08.3-3): Waiting for test results, 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/kldap.html
• kleopatra (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for kleopatra (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/kleopatra.html
• kmail (4:18.08.3-1 to 4:18.08.3-4)
  • Migration status for kmail (4:18.08.3-1 to 4:18.08.3-4): Waiting for test results, 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/kmail.html
• kmail-account-wizard (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for kmail-account-wizard (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/kmail-account-wizard.html
• kmailtransport (18.08.3-2 to 18.08.3-4)
  • Migration status for kmailtransport (18.08.3-2 to 18.08.3-4): Waiting for test results, 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/kmailtransport.html
• kmbox (18.08.3-1 to 18.08.3-3)
  • Migration status for kmbox (18.08.3-1 to 18.08.3-3): Waiting for test results, 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/kmbox.html
• kmime (18.08.3-1 to 18.08.3-3)
  • Migration status for kmime (18.08.3-1 to 18.08.3-3): Waiting for test results, 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/kmime.html
• knotes (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for knotes (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/knotes.html
• kontact (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for kontact (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/kontact.html
• kontactinterface (18.08.3-1 to 18.08.3-3)
  • Migration status for kontactinterface (18.08.3-1 to 18.08.3-3): Waiting for test results, 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/kontactinterface.html
• korganizer (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for korganizer (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/korganizer.html
• kpimtextedit (18.08.3-1 to 18.08.3-3)
  • Migration status for kpimtextedit (18.08.3-1 to 18.08.3-3): Waiting for test results, 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/kpimtextedit.html
• kpkpass (18.08.3-2 to 18.08.3-4)
  • Migration status for kpkpass (18.08.3-2 to 18.08.3-4): Waiting for test results, 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/kpkpass.html
• ksh (2020.0.0-1 to 2020.0.0-2)
  • Migration status for ksh (2020.0.0-1 to 2020.0.0-2): Waiting for test results, 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/ksh.html
• ksmtp (18.08.3-1 to 18.08.3-3)
  • Migration status for ksmtp (18.08.3-1 to 18.08.3-3): Waiting for test results, 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/ksmtp.html
• ktnef (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for ktnef (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/ktnef.html
• libdata-compare-perl (1.26-1 to 1.27-1)
  • Migration status for libdata-compare-perl (1.26-1 to 1.27-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Invalidated by build-dependency (indep)
  • Build-Depends-Indep: libdata-compare-perl libclone-perl (not considered)
  • Depends: libdata-compare-perl libclone-perl (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdata-compare-perl.html
  • Required age reduced by 3 days because of autopkgtest
  • 4 days old (needed 2 days)
• libglu (9.0.0-2.1 to 9.0.1-1)
  • Migration status for libglu (9.0.0-2.1 to 9.0.1-1): Waiting for test results, 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 libglu fixes old bugs: #944753
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libglu.html
• libkf5calendarsupport (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for libkf5calendarsupport (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/libk/libkf5calendarsupport.html
• libkf5eventviews (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for libkf5eventviews (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/libk/libkf5eventviews.html
• libkf5grantleetheme (18.08.3-1 to 18.08.3-3)
  • Migration status for libkf5grantleetheme (18.08.3-1 to 18.08.3-3): Waiting for test results, 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/libk/libkf5grantleetheme.html
• libkf5gravatar (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for libkf5gravatar (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/libk/libkf5gravatar.html
• libkf5incidenceeditor (18.08.3-3 to 18.08.3-5)
  • Migration status for libkf5incidenceeditor (18.08.3-3 to 18.08.3-5): Waiting for test results, 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/libk/libkf5incidenceeditor.html
• libkf5ksieve (4:18.08.3-2 to 4:18.08.3-5)
  • Migration status for libkf5ksieve (4:18.08.3-2 to 4:18.08.3-5): Waiting for test results, 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/libk/libkf5ksieve.html
• libkf5libkdepim (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for libkf5libkdepim (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/libk/libkf5libkdepim.html
• libkf5libkleo (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for libkf5libkleo (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/libk/libkf5libkleo.html
• libkf5mailcommon (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for libkf5mailcommon (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/libk/libkf5mailcommon.html
• libkf5mailimporter (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for libkf5mailimporter (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/libk/libkf5mailimporter.html
• libkf5pimcommon (4:18.08.3-2 to 4:18.08.3-4)
  • Migration status for libkf5pimcommon (4:18.08.3-2 to 4:18.08.3-4): Waiting for test results, 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/libk/libkf5pimcommon.html
• libkgapi (18.08.3-2 to 18.08.3-4)
  • Migration status for libkgapi (18.08.3-2 to 18.08.3-4): Waiting for test results, 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/libk/libkgapi.html
• libteam (1.28-1 to 1.29-1)
  • Migration status for libteam (1.28-1 to 1.29-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libteam.html
• mbox-importer (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for mbox-importer (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mbox-importer.html
• mcomix (- to 1.2.1mcomix3+git20190616-2)
  • Migration status for mcomix (- to 1.2.1mcomix3+git20190616-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mcomix.html
• mpdtoys (- to 0.25.0)
  • Migration status for mpdtoys (- to 0.25.0): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpdtoys.html
• neomutt (20180716+dfsg.1-1.2 to 20191111+dfsg.1-1)
  • Migration status for neomutt (20180716+dfsg.1-1.2 to 20191111+dfsg.1-1): Waiting for test results, 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/neomutt.html
• neovim (0.3.8-1 to 0.4.3-2)
  • Migration status for neovim (0.3.8-1 to 0.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python-neovim/0.3.0-1: amd64: Regression ♻
  • missing build on mipsel
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neovim.html
• nlopt (2.6.1-5 to 2.6.1-6)
  • Migration status for nlopt (2.6.1-5 to 2.6.1-6): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • 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/n/nlopt.html
• node-mongodb (3.3.2+~3.2.7-1 to 3.3.4+~3.2.7-1)
  • Migration status for node-mongodb (3.3.2+~3.2.7-1 to 3.3.4+~3.2.7-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mongodb.html
• nvidia-graphics-drivers-legacy-390xx (390.129-2 to 390.132-1)
  • Migration status for nvidia-graphics-drivers-legacy-390xx (390.129-2 to 390.132-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• nvidia-persistenced (430.50-1 to 430.64-1)
  • Migration status for nvidia-persistenced (430.50-1 to 430.64-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • nvidia-persistenced/ppc64el unsatisfiable Depends: libnvidia-tesla-cfg1
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• owslib (0.18.0-2 to 0.19.0-1)
  • Migration status for owslib (0.18.0-2 to 0.19.0-1): Waiting for test results, 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/owslib.html
• pim-data-exporter (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for pim-data-exporter (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/pim-data-exporter.html
• pim-sieve-editor (4:18.08.3-1 to 4:18.08.3-3)
  • Migration status for pim-sieve-editor (4:18.08.3-1 to 4:18.08.3-3): Waiting for test results, 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/pim-sieve-editor.html
• pm-utils (1.4.1-18 to 1.4.1-19)
  • Migration status for pm-utils (1.4.1-18 to 1.4.1-19): Waiting for test results, 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/pm-utils.html
• primus-vk (- to 1.3-2)
  • Migration status for primus-vk (- to 1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by luca.boccassi@gmail.com
  • Not built on buildd: arch all binaries uploaded by luca.boccassi@gmail.com, a new source-only upload is needed to allow migration
  • Too young, only 4 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• pyjunitxml (0.6-1.3 to 0.6-2)
  • Migration status for pyjunitxml (0.6-1.3 to 0.6-2): Waiting for test results, 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/pyjunitxml.html
• python-pybedtools (0.8.0-1 to 0.8.0-3)
  • Migration status for python-pybedtools (0.8.0-1 to 0.8.0-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • pybedtools-bin/i386 unsatisfiable Depends: python3-pybedtools
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pybedtools.html
• python3-defaults (3.7.5-1 to 3.7.5-3)
  • Migration status for python3-defaults (3.7.5-1 to 3.7.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for beets/1.4.7-2: amd64: Regression ♻
  • autopkgtest for biomaj3/3.1.14-1: amd64: Regression ♻
  • autopkgtest for biomaj3-core/3.0.19-1: amd64: Regression ♻
  • autopkgtest for biomaj3-user/3.0.10-1: amd64: Regression ♻
  • autopkgtest for bottleneck/1.2.1+ds1-2: amd64: Regression ♻
  • autopkgtest for cairosvg/2.4.2-1: amd64: Regression ♻
  • autopkgtest for chardet/3.0.4-4: amd64: Regression ♻
  • autopkgtest for citeproc-py/0.3.0-3: amd64: Regression ♻
  • autopkgtest for csvkit/1.0.2-1: amd64: Regression ♻
  • autopkgtest for cvxopt/1.1.9+dfsg-3: amd64: Regression ♻
  • autopkgtest for cyvcf2/0.10.8-1: amd64: Regression ♻
  • autopkgtest for dask/1.0.0+dfsg-2: amd64: Regression ♻
  • autopkgtest for dh-python/4.20191017: amd64: Regression ♻
  • autopkgtest for diffoscope/130: amd64: Regression ♻
  • autopkgtest for distro-info/0.22: amd64: Regression ♻
  • autopkgtest for glymur/0.8.18+ds-1: amd64: Regression ♻
  • autopkgtest for gpyfft/0.7.0-2: amd64: Regression ♻
  • autopkgtest for gudhi/3.0.0+dfsg-3: amd64: Regression ♻
  • autopkgtest for gyoto/1.4.3-1: amd64: Regression ♻
  • autopkgtest for h5py/2.10.0-2: amd64: Regression ♻
  • autopkgtest for hovercraft/2.6-5: amd64: Regression ♻
  • autopkgtest for hyperkitty/1.3.0-1: amd64: Regression ♻
  • autopkgtest for jupyter-client/5.3.4-1: amd64: Regression ♻
  • autopkgtest for libgpuarray/0.7.6-4: amd64: Regression ♻
  • autopkgtest for librecaptcha/0.6.2-1: amd64: Regression ♻
  • autopkgtest for matplotlib/3.0.2-2: amd64: Regression ♻
  • autopkgtest for med-fichier/4.0.0+repack-8: amd64: Regression ♻
  • autopkgtest for numexpr/2.7.0-1: amd64: Regression ♻
  • autopkgtest for openslide-python/1.1.1-4: amd64: Regression ♻
  • autopkgtest for pandas/0.23.3+dfsg-8: amd64: Regression ♻
  • autopkgtest for patsy/0.5.0+git13-g54dcf7b-1: amd64: Regression ♻
  • autopkgtest for psycopg2/2.8.3-2: amd64: Regression ♻
  • autopkgtest for pyatspi/2.34.0-2: amd64: Regression ♻
  • autopkgtest for pybigwig/0.3.12-1: amd64: Regression ♻
  • autopkgtest for pycxx/7.0.3-3: amd64: Regression ♻
  • autopkgtest for pydecorate/0.2.1-1: amd64: Regression ♻
  • autopkgtest for pyepr/1.0.0-1: amd64: Regression ♻
  • autopkgtest for pyfai/0.18.0+dfsg1-3: amd64: Regression ♻
  • autopkgtest for pyfftw/0.11.1-3: amd64: Regression ♻
  • autopkgtest for pygame/1.9.4.post1+dfsg-3: amd64: Regression ♻
  • autopkgtest for pyinsane/2.0.13-1: amd64: Regression ♻
  • autopkgtest for pykdtree/1.3.1-4: amd64: Regression ♻
  • autopkgtest for pylibtiff/0.4.2-6: amd64: Regression ♻
  • autopkgtest for pymca/5.5.3+dfsg-1: amd64: Regression ♻
  • autopkgtest for pymssql/2.1.4+dfsg-2: amd64: Regression ♻
  • autopkgtest for pynfft/1.3.2-2: amd64: Regression ♻
  • autopkgtest for pyorbital/1.5.0-4: amd64: Regression ♻
  • autopkgtest for pyqt5webengine/5.12.1-4: amd64: Regression ♻
  • autopkgtest for pyresample/1.13.2-1: amd64: Regression ♻
  • autopkgtest for pystemmer/1.3.0+dfsg-2: amd64: Regression ♻
  • autopkgtest for pytables/3.5.2-3: amd64: Regression ♻
  • autopkgtest for pytest-astropy/0.5.0-1: amd64: Regression ♻
  • autopkgtest for python-aalib/0.3.2-4: amd64: Regression ♻
  • autopkgtest for python-agate/1.6.0-3: amd64: Regression ♻
  • autopkgtest for python-agate-excel/0.2.1-3: amd64: Regression ♻
  • autopkgtest for python-airr/1.2.1-2: amd64: Regression ♻
  • autopkgtest for python-apt/1.8.4: amd64: Regression ♻
  • autopkgtest for python-argon2/18.3.0-2: amd64: Regression ♻
  • autopkgtest for python-ase/3.18.1-1: amd64: Regression ♻
  • autopkgtest for python-bayespy/0.5.18-2: amd64: Regression ♻
  • autopkgtest for python-biopython/1.73+dfsg-1: amd64: Regression ♻
  • autopkgtest for python-blosc/1.7.0+ds1-2: amd64: Regression ♻
  • autopkgtest for python-bumps/0.7.13-1: amd64: Regression ♻
  • autopkgtest for python-caldav/0.6.1+repack1-1: amd64: Regression ♻
  • autopkgtest for python-cryptography/2.6.1-4: amd64: Regression ♻
  • autopkgtest for python-csb/1.2.5+dfsg-5: amd64: Regression ♻
  • autopkgtest for python-datrie/0.7.1-3: amd64: Regression ♻
  • autopkgtest for python-djvulibre/0.8.4-1: amd64: Regression ♻
  • autopkgtest for python-dtcwt/0.12.0-2: amd64: Regression ♻
  • autopkgtest for python-fabio/0.9.0+dfsg-1: amd64: Regression ♻
  • autopkgtest for python-fakeredis/1.0.5-1: amd64: Regression ♻
  • autopkgtest for python-feather-format/0.3.1+dfsg1-2: amd64: Regression ♻
  • autopkgtest for python-fisx/1.1.7-2: amd64: Regression ♻
  • autopkgtest for python-geotiepoints/1.1.8-2: amd64: Regression ♻
  • autopkgtest for python-gimmik/2.1-1: amd64: Regression ♻
  • autopkgtest for python-graphviz/0.8.4-2: amd64: Regression ♻
  • autopkgtest for python-h5netcdf/0.7.1-1: amd64: Regression ♻
  • autopkgtest for python-hdf4/0.10.1-2: amd64: Regression ♻
  • autopkgtest for python-httptools/0.0.11-1.1: amd64: Regression ♻
  • autopkgtest for python-hypothesis/3.71.11-1: amd64: Regression ♻
  • autopkgtest for python-imageio/2.4.1-3: amd64: Regression ♻
  • autopkgtest for python-jellyfish/0.6.1-1: amd64: Regression ♻
  • autopkgtest for python-jsonrpc/1.12.1-1: amd64: Regression ♻
  • autopkgtest for python-leather/0.3.3-1: amd64: Regression ♻
  • autopkgtest for python-libdiscid/1.1-1: amd64: Regression ♻
  • autopkgtest for python-line-profiler/2.1-2: amd64: Regression ♻
  • autopkgtest for python-ltfatpy/1.0.16-3: amd64: Regression ♻
  • autopkgtest for python-lti/0.9.4-1: amd64: Regression ♻
  • autopkgtest for python-lupa/1.6+dfsg-4: amd64: Regression ♻
  • autopkgtest for python-matplotlib-venn/0.11.5-6: amd64: Regression ♻
  • autopkgtest for python-mechanicalsoup/0.10.0-3: amd64: Regression ♻
  • autopkgtest for python-meshio/3.2.6-1: amd64: Regression ♻
  • autopkgtest for python-mplexporter/0.0.1+20140921-4: amd64: Regression ♻
  • autopkgtest for python-msgpack-numpy/0.4.4-1: amd64: Regression ♻
  • autopkgtest for python-murmurhash/1.0.1-2: amd64: Regression ♻
  • autopkgtest for python-nacl/1.3.0-2: amd64: Regression ♻
  • autopkgtest for python-numpy/1:1.16.5-1: amd64: Regression ♻
  • autopkgtest for python-parsel/1.5.2-1: amd64: Regression ♻
  • autopkgtest for python-pcl/0.3.0~rc1+dfsg-7: amd64: Regression ♻
  • autopkgtest for python-periodictable/1.5.1-2: amd64: Regression ♻
  • autopkgtest for python-pomegranate/0.11.1+dfsg2-1: amd64: Regression ♻
  • autopkgtest for python-prov/1.5.2-2: amd64: Regression ♻
  • autopkgtest for python-pulp/1.6.0+dfsg1-4: amd64: Regression ♻
  • autopkgtest for python-pygit2/0.27.4-2: amd64: Regression ♻
  • autopkgtest for python-pymeasure/0.5-1: amd64: Regression ♻
  • autopkgtest for python-quantities/0.12.3-2: amd64: Regression ♻
  • autopkgtest for python-redis/3.3.11-1: amd64: Regression ♻
  • autopkgtest for python-scipy/1.2.2-7: amd64: Regression ♻
  • autopkgtest for python-scrapy/1.7.3-1: amd64: Regression ♻
  • autopkgtest for python-scrapy-djangoitem/1.1.1-4: amd64: Regression ♻
  • autopkgtest for python-sfml/2.2~git20150611.196c88+dfsg-5: amd64: Regression ♻
  • autopkgtest for python-sparse/0.2.0-1: amd64: Regression ♻
  • autopkgtest for python-spectra/0.0.11-1: amd64: Regression ♻
  • autopkgtest for python-tesserocr/2.4.0-4: amd64: Regression ♻
  • autopkgtest for python-tornado/6.0.3+really5.1.1-1: amd64: Regression ♻
  • autopkgtest for python-treetime/0.6.2-1: amd64: Regression ♻
  • autopkgtest for python-uinput/0.11.2-2: amd64: Regression ♻
  • autopkgtest for python-ulmo/0.8.5+dfsg1-1: amd64: Regression ♻
  • autopkgtest for python-vispy/0.6.1-2: amd64: Regression ♻
  • autopkgtest for pyzmq/17.1.2-3: amd64: Regression ♻
  • autopkgtest for qscintilla2/2.10.4+dfsg-2.1: amd64: Regression ♻
  • autopkgtest for sasmodels/1.0.0-2: amd64: Regression ♻
  • autopkgtest for sasview/5.0.1-1: amd64: Regression ♻
  • autopkgtest for satpy/0.16.1-3: amd64: Regression ♻
  • autopkgtest for scoop/0.7.1.1-4: amd64: Regression ♻
  • autopkgtest for seaborn/0.9.0-2: amd64: Regression ♻
  • autopkgtest for segyio/1.8.3-1: amd64: Regression ♻
  • autopkgtest for silx/0.11.0+dfsg-2: amd64: Regression ♻
  • autopkgtest for skimage/0.14.2-3: amd64: Regression ♻
  • autopkgtest for spyder-unittest/0.3.0-1: amd64: Regression ♻
  • autopkgtest for statsmodels/0.9.0-6: amd64: Regression ♻
  • autopkgtest for tagpy/2013.1-7: amd64: Regression ♻
  • autopkgtest for translate-toolkit/2.4.0-2: amd64: Regression ♻
  • autopkgtest for txzmq/0.8.0-2: amd64: Regression ♻
  • autopkgtest for uvloop/0.11.3+ds1-2: amd64: Regression ♻
  • autopkgtest for watson/1.6.0-6: amd64: Regression ♻
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3-defaults.html
• q2templates (- to 2019.10.0+dfsg-1)
  • Migration status for q2templates (- to 2019.10.0+dfsg-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
  • Too young, only 4 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• r-cran-testthat (2.2.1-1 to 2.3.0-1)
  • Migration status for r-cran-testthat (2.2.1-1 to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for r-cran-pdftools/2.3-1: amd64: Regression ♻
  • autopkgtest for r-cran-processx/3.4.1-1: amd64: Regression ♻
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-testthat.html
• rust-libgit2-sys (0.7.11-1 to 0.9.1-2)
  • Migration status for rust-libgit2-sys (0.7.11-1 to 0.9.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libgit2-sys.html
• rust-object (0.11.0-1 to 0.12.0-1)
  • Migration status for rust-object (0.11.0-1 to 0.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-object/0.12.0-1: amd64: Regression ♻
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-object.html
• ssreflect (1.9.0+dfsg-1 to 1.9.0+dfsg-2)
  • Migration status for ssreflect (1.9.0+dfsg-1 to 1.9.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssreflect.html
  • Required age reduced by 3 days because of autopkgtest
  • 4 days old (needed 2 days)
• staticsite (1.0-1 to 1.1-1)
  • Migration status for staticsite (1.0-1 to 1.1-1): Waiting for test results, 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/staticsite.html
• umoci (0.4.4+dfsg-1 to 0.4.4+dfsg-5)
  • Migration status for umoci (0.4.4+dfsg-1 to 0.4.4+dfsg-5): Waiting for test results, 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/umoci.html
• vip-manager (- to 0.6+ds-3)
  • Migration status for vip-manager (- to 0.6+ds-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• volk (2.0.0-2 to 2.0.0-3)
  • Migration status for volk (2.0.0-2 to 2.0.0-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/volk.html
• watchman (- to 4.9.0-2)
  • Migration status for watchman (- to 4.9.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 4 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• broccoli-python (0.62-1 to 0.63-1)
  • Migration status for broccoli-python (0.62-1 to 0.63-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bengen
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/broccoli-python.html
  • 5 days old (needed 5 days)
• camlpdf (2.2.1-1 to 2.3-2)
  • Migration status for camlpdf (2.2.1-1 to 2.3-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Updating camlpdf fixes old bugs: #944276
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camlpdf.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• campania (- to 2.009-2)
  • Migration status for campania (- to 2.009-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 5 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• clamfs (- to 1.1.0-1)
  • Migration status for clamfs (- to 1.1.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clamfs.html
  • 5 days old (needed 5 days)
• ddogleg (- to 0.17+ds-2)
  • Migration status for ddogleg (- to 0.17+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): ddogleg junit5 (not considered)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• ejabberd (19.08-2 to 19.09.1-1)
  • Migration status for ejabberd (19.08-2 to 19.09.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): ejabberd erlang-unicode-util-compat (not considered)
  • Depends: ejabberd erlang-unicode-util-compat (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ejabberd.html
  • 5 days old (needed 5 days)
• ejabberd-contrib (0.2019.08.19~dfsg0-3 to 0.2019.11.10~dfsg0-1)
  • Migration status for ejabberd-contrib (0.2019.08.19~dfsg0-3 to 0.2019.11.10~dfsg0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): ejabberd-contrib ejabberd (not considered)
  • Depends: ejabberd-contrib ejabberd (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ejabberd-contrib.html
  • 5 days old (needed 5 days)
• erlang-p1-xmpp (1.4.0-1 to 1.4.2-1)
  • Migration status for erlang-p1-xmpp (1.4.0-1 to 1.4.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): erlang-p1-xmpp erlang-unicode-util-compat (not considered)
  • Depends: erlang-p1-xmpp erlang-unicode-util-compat (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-xmpp.html
  • 5 days old (needed 5 days)
• fst (- to 0.115.0-1)
  • Migration status for fst (- to 0.115.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fst introduces new bugs: #944791
  • Not built on buildd: arch all binaries uploaded by zmoelnig@umlaeute.mur.at, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• gnome-shell-extension-arc-menu (- to 38.3-dev-1)
  • Migration status for gnome-shell-extension-arc-menu (- to 38.3-dev-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• gnumed-client (- to 1.7.8+dfsg-1)
  • Migration status for gnumed-client (- to 1.7.8+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnumed-client introduces new bugs: #936630
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnumed-client.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
  • Impossible Depends: gnumed-client -> python-gnuplot/amd64
  • Impossible Depends: gnumed-client -> python-gnuplot/arm64
  • Impossible Depends: gnumed-client -> python-gnuplot/armel
  • Impossible Depends: gnumed-client -> python-gnuplot/armhf
  • Impossible Depends: gnumed-client -> python-gnuplot/i386
  • Impossible Depends: gnumed-client -> python-gnuplot/mips64el
  • Impossible Depends: gnumed-client -> python-gnuplot/mipsel
  • Impossible Depends: gnumed-client -> python-gnuplot/ppc64el
  • Impossible Depends: gnumed-client -> python-gnuplot/s390x
• golang-github-fsouza-go-dockerclient (1.2.1-2 to 1.6.0-1)
  • Migration status for golang-github-fsouza-go-dockerclient (1.2.1-2 to 1.6.0-1): Waiting for test results, 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-fsouza-go-dockerclient.html
  • Additional info:
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): golang-github-getlantern-errors golang-github-getlantern-ops (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-errors.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• golang-github-getlantern-hidden (- to 0.0~git20190325.f02dbb0-2)
  • Migration status for golang-github-getlantern-hidden (- to 0.0~git20190325.f02dbb0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-github-getlantern-hidden introduces new bugs: #927251
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-hidden.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• gplaycli (3.25+ds-1 to 3.26+dfsg-1)
  • Migration status for gplaycli (3.25+ds-1 to 3.26+dfsg-1): Waiting for test results, 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/g/gplaycli.html
• inkscape-survex-export (- to 1.0-1)
  • Migration status for inkscape-survex-export (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by wookey, a new source-only upload is needed to allow migration
  • Too young, only 5 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• lightbox2.js (- to 2.11.1+dfsg-1)
  • Migration status for lightbox2.js (- to 2.11.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by x.guimard@free.fr, a new source-only upload is needed to allow migration
  • Too young, only 5 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• linux-signed-i386 (5.2.17+1 to 5.3.9+2)
  • Migration status for linux-signed-i386 (5.2.17+1 to 5.3.9+2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • linux-signed-i386 unsatisfiable Build-Depends(-Arch) on i386: linux-support-5.3.0-2 (= 5.3.9-2)
  • linux-signed-i386 unsatisfiable Build-Depends(-Arch) on i386: linux-image-5.3.0-2-686-unsigned (= 5.3.9-2) [i386]
  • linux-signed-i386 unsatisfiable Build-Depends(-Arch) on i386: linux-image-5.3.0-2-686-pae-unsigned (= 5.3.9-2) [i386]
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• node-yargs (10.0.3-2 to 15.0.0-1)
  • Migration status for node-yargs (10.0.3-2 to 15.0.0-1): Waiting for test results, 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/n/node-yargs.html
  • Additional info:
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• octave-nan (3.1.4-5 to 3.4.3-1)
  • Migration status for octave-nan (3.1.4-5 to 3.4.3-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on mipsel
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-nan.html
  • 5 days old (needed 5 days)
• phylonium (- to 1.1-1)
  • Migration status for phylonium (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• pysimplesoap (1.16.2-1 to 1.16.2-2)
  • Migration status for pysimplesoap (1.16.2-1 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysimplesoap.html
  • 5 days old (needed 5 days)
• python-bleach (3.1.0-1 to 3.1.0-2)
  • Migration status for python-bleach (3.1.0-1 to 3.1.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bleach.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• python-django-channels (2.3.0-1 to 2.3.1-1)
  • Migration status for python-django-channels (2.3.0-1 to 2.3.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 5 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-channels.html
• python-dmsh (- to 0.1.3-1)
  • Migration status for python-dmsh (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python-dmsh/0.1.3-1: amd64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by dparsons, a new source-only upload is needed to allow migration
  • Too young, only 5 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-periphery (- to 2.0.0-1)
  • Migration status for python-periphery (- to 2.0.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 5 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-periphery.html
• python-pybadges (- to 2.2.1-1)
  • Migration status for python-pybadges (- to 2.2.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 5 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pybadges.html
• python-tempora (- to 1.14.1-1)
  • Migration status for python-tempora (- to 1.14.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• python-testfixtures (4.14.3-3 to 6.10.1-1)
  • Migration status for python-testfixtures (4.14.3-3 to 6.10.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): python-testfixtures python-sybil (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-testfixtures.html
  • 5 days old (needed 5 days)
• qcelemental (- to 0.5.0+dfsg-1)
  • Migration status for qcelemental (- to 0.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mbanck, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• r-cran-tidyr (0.8.3-1 to 1.0.0-1)
  • Migration status for r-cran-tidyr (0.8.3-1 to 1.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): r-cran-tidyr r-cran-tibble (not considered)
  • Depends: r-cran-tidyr r-cran-tibble (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tidyr.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• ruby-rqrcode-core (- to 0.1.0-1)
  • Migration status for ruby-rqrcode-core (- 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 praveen, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• rust-barrel (- to 0.6.2-1)
  • Migration status for rust-barrel (- to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • librust-barrel+diesel-dev/amd64 unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+diesel-dev/arm64 unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+diesel-dev/armel unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+diesel-dev/armhf unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+diesel-dev/i386 unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+diesel-dev/mips64el unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+diesel-dev/mipsel unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+diesel-dev/ppc64el unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+diesel-dev/s390x unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/amd64 unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/arm64 unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/armel unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/armhf unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/i386 unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/mips64el unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/mipsel unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/ppc64el unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • librust-barrel+tempdir-dev/s390x unsatisfiable Depends: librust-tempdir-0.3+default-dev (>= 0.3.4-~~)
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• rust-box-drawing (- to 0.1.2-1)
  • Migration status for rust-box-drawing (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by nicoo
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• rust-crossterm-winapi (- to 0.3.0-1)
  • Migration status for rust-crossterm-winapi (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• rust-migrations-macros (- to 1.4.1-1)
  • Migration status for rust-migrations-macros (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• rust-parity-wasm (0.35.5-1 to 0.38.0-1)
  • Migration status for rust-parity-wasm (0.35.5-1 to 0.38.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-parity-wasm/0.38.0-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-parity-wasm.html
  • 5 days old (needed 5 days)
• rust-prettytable-rs (- to 0.8.0-1)
  • Migration status for rust-prettytable-rs (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bugzilla@tut.by
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• rust-radix-trie (- to 0.1.5-1)
  • Migration status for rust-radix-trie (- to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• rust-sct (- to 0.6.0-1)
  • Migration status for rust-sct (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• rust-section-testing (- to 0.0.4-1)
  • Migration status for rust-section-testing (- to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• rust-webpki (- to 0.21.0-1)
  • Migration status for rust-webpki (- to 0.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 5 days old (needed 5 days)
• singularity-container (3.1.1+ds-1 to 3.5.0+ds1-1)
  • Migration status for singularity-container (3.1.1+ds-1 to 3.5.0+ds1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on ppc64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singularity-container.html
  • 5 days old (needed 5 days)
• sysbench (- to 1.0.18+ds-1)
  • Migration status for sysbench (- to 1.0.18+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): sysbench ck (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysbench.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• utop (- to 2.4.2-1)
  • Migration status for utop (- to 2.4.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utop.html
  • 5 days old (needed 5 days)
• cds-healpix-java (- to 0.25.1+ds-2)
  • Migration status for cds-healpix-java (- to 0.25.1+ds-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 6 of 7 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• cmake (3.13.4-1 to 3.15.4-1)
  • Migration status for cmake (3.13.4-1 to 3.15.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for oce/0.18.2-3: amd64: Regression ♻
  • autopkgtest for wslay/1.1.0-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmake.html
  • 6 days old (needed 5 days)
• coyote (2019.02.25-1 to 2019.08.19-1)
  • Migration status for coyote (2019.02.25-1 to 2019.08.19-1): Waiting for test results, 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/c/coyote.html
  • Required age reduced by 3 days because of autopkgtest
• extsmail (2.2-4 to 2.3-1)
  • Migration status for extsmail (2.2-4 to 2.3-1): Waiting for test results, 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/e/extsmail.html
  • Required age reduced by 3 days because of autopkgtest
• gnome-shell-extension-show-ip (8-3 to 8-4)
  • Migration status for gnome-shell-extension-show-ip (8-3 to 8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnome-shell-extension-show-ip introduces new bugs: #944993
  • Too young, only 6 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-show-ip.html
• gscan2pdf (2.5.7-1 to 2.6.1-1)
  • Migration status for gscan2pdf (2.5.7-1 to 2.6.1-1): Waiting for test results, 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/gscan2pdf.html
  • Required age reduced by 3 days because of autopkgtest
• ibus (1.5.19-4+deb10u1 to 1.5.21-2)
  • Migration status for ibus (1.5.19-4+deb10u1 to 1.5.21-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Updating ibus fixes old bugs: #940634
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus.html
  • Required age reduced by 3 days because of autopkgtest
  • Required age is not allowed to drop below 2 days
  • 6 days old (needed 2 days)
• idlastro (2019.08.01+dfsg-1 to 2019.10.30+dfsg-1)
  • Migration status for idlastro (2019.08.01+dfsg-1 to 2019.10.30+dfsg-1): Waiting for test results, 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/i/idlastro.html
  • Required age reduced by 3 days because of autopkgtest
• lambda-term (- to 2.0.2-1)
  • Migration status for lambda-term (- to 2.0.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lambda-term.html
  • 6 days old (needed 5 days)
• libbio-graphics-perl (- to 2.40-4)
  • Migration status for libbio-graphics-perl (- to 2.40-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libbio-graphics-perl/2.40-4: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbio-graphics-perl.html
  • 6 days old (needed 5 days)
• libclone-perl (0.41-1 to 0.43-1)
  • Migration status for libclone-perl (0.41-1 to 0.43-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libclone-perl unsatisfiable Build-Depends(-Arch) on s390x: libb-cow-perl
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libclone-perl.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• libinputsynth (0.12.1-1 to 0.13.1-1)
  • Migration status for libinputsynth (0.12.1-1 to 0.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ajqlee
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libinputsynth.html
  • 6 days old (needed 5 days)
• libvterm (0~bzr718-1 to 0.1.2-2)
  • Migration status for libvterm (0~bzr718-1 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvterm.html
  • 6 days old (needed 5 days)
• linux-signed-amd64 (5.2.17+1 to 5.3.9+2)
  • Migration status for linux-signed-amd64 (5.2.17+1 to 5.3.9+2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • linux-signed-amd64 unsatisfiable Build-Depends(-Arch) on amd64: linux-support-5.3.0-2 (= 5.3.9-2)
  • linux-signed-amd64 unsatisfiable Build-Depends(-Arch) on amd64: linux-image-5.3.0-2-amd64-unsigned (= 5.3.9-2) [amd64]
  • linux-signed-amd64 unsatisfiable Build-Depends(-Arch) on amd64: linux-image-5.3.0-2-cloud-amd64-unsigned (= 5.3.9-2) [amd64]
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-signed-amd64.html
  • 6 days old (needed 5 days)
• llvm-toolchain-8 (1:8.0.1-3 to 1:8.0.1-4)
  • Migration status for llvm-toolchain-8 (1:8.0.1-3 to 1:8.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating llvm-toolchain-8 introduces new bugs: #944844
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Updating llvm-toolchain-8 fixes old bugs: #943920
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-8.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• mistune (0.8.4-1 to 0.8.4-2)
  • Migration status for mistune (0.8.4-1 to 0.8.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mistune.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• nbconvert (5.6.0-1 to 5.6.0-2)
  • Migration status for nbconvert (5.6.0-1 to 5.6.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbconvert.html
  • 6 days old (needed 5 days)
• nbformat (4.4.0-2 to 4.4.0-3)
  • Migration status for nbformat (4.4.0-2 to 4.4.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbformat.html
  • 6 days old (needed 5 days)
• ocplib-simplex (0.4-1 to 0.4-2)
  • Migration status for ocplib-simplex (0.4-1 to 0.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocplib-simplex.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• pyaxmlparser (0.3.21-1 to 0.3.24-1)
  • Migration status for pyaxmlparser (0.3.21-1 to 0.3.24-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 6 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyaxmlparser.html
• pytest-astropy (0.5.0-1 to 0.6.0-1)
  • Migration status for pytest-astropy (0.5.0-1 to 0.6.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 6 of 7 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-astropy.html
  • Required age reduced by 3 days because of autopkgtest
• pytest-astropy-header (- to 0.1.1-2)
  • Migration status for pytest-astropy-header (- to 0.1.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 6 of 7 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• python-numpy (1:1.16.5-1 to 1:1.16.5-2)
  • Migration status for python-numpy (1:1.16.5-1 to 1:1.16.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for pandas/0.23.3+dfsg-8: amd64: Regression ♻
  • autopkgtest for python-numpy/1:1.16.5-2: amd64: Regression ♻
  • autopkgtest for python-scipy/1.2.2-7: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-numpy.html
  • 6 days old (needed 5 days)
• python-pypubsub (- to 4.0.3-2)
  • Migration status for python-pypubsub (- to 4.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python-pypubsub/4.0.3-2: amd64: Regression ♻
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 6 days old (needed 5 days)
• python-sybil (- to 1.2.0-1)
  • Migration status for python-sybil (- to 1.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): python-sybil pytest (not considered)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 6 days old (needed 5 days)
• python-telegram-bot (- to 12.2.0-2)
  • Migration status for python-telegram-bot (- to 12.2.0-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 6 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• r-cran-openmx (- to 2.14.11-1)
  • Migration status for r-cran-openmx (- to 2.14.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for r-cran-openmx/2.14.11-1: amd64: Regression ♻
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 6 days old (needed 5 days)
• racon (- to 1.4.10-1)
  • Migration status for racon (- to 1.4.10-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): racon libthread-pool (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/racon.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• runescape (0.5-1 to 0.6-2)
  • Migration status for runescape (0.5-1 to 0.6-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 6 days old (needed 5 days)
• rust-cmake (0.1.40-1 to 0.1.42-1)
  • Migration status for rust-cmake (0.1.40-1 to 0.1.42-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-cmake rust-cc (not considered)
  • Depends: rust-cmake rust-cc (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cmake.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• rust-libc (0.2.62-1 to 0.2.65-1)
  • Migration status for rust-libc (0.2.62-1 to 0.2.65-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-libc/0.2.65-1: amd64: Regression ♻
  • autopkgtest for rust-tempfile/3.0.8-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libc.html
  • 6 days old (needed 5 days)
• sqlmap (1.3.11-2 to 1.3.11-3)
  • Migration status for sqlmap (1.3.11-2 to 1.3.11-3): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 6 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlmap.html
• testpath (0.4.2+dfsg-1 to 0.4.2+dfsg-2)
  • Migration status for testpath (0.4.2+dfsg-1 to 0.4.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for testpath/0.4.2+dfsg-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/testpath.html
  • 6 days old (needed 5 days)
• tpm2-tools (3.1.3-2 to 4.0.1-1)
  • Migration status for tpm2-tools (3.1.3-2 to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for tpm2-tools/4.0.1-1: amd64: Regression ♻
  • tpm2-tools unsatisfiable Build-Depends(-Arch) on s390x: libtss2-dev (>= 2.3.0)
  • missing build on s390x
  • Too young, only 6 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-tools.html
• tpm2-tss (2.1.0-4 to 2.3.1-2)
  • Migration status for tpm2-tss (2.1.0-4 to 2.3.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on s390x
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Too young, only 6 of 10 days old
  • Additional info:
  • Updating tpm2-tss fixes old bugs: #943938
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-tss.html
• acpi-override (- to 0.1)
  • Migration status for acpi-override (- to 0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by cascardo, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• aiomysql (- to 0.0.20-1)
  • Migration status for aiomysql (- to 0.0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ruben.undheim@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• asciitree (- to 0.3.3-1)
  • Migration status for asciitree (- to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by gladky.anton@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• ben (0.8.3 to 0.9.0)
  • Migration status for ben (0.8.3 to 0.9.0): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/ben.html
  • 7 days old (needed 5 days)
• biomaj3-download (3.0.19-1 to 3.1.0-1)
  • Migration status for biomaj3-download (3.0.19-1 to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for biomaj3/3.1.14-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biomaj3-download.html
  • 7 days old (needed 5 days)
• bitwise (- to 0.40-1)
  • Migration status for bitwise (- to 0.40-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by jonathan@bluemosh.com
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• cpupower-gui (- to 0.7.0-1)
  • Migration status for cpupower-gui (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kilobyte
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• docker.io (18.09.9+dfsg1-5 to 19.03.4+dfsg2-2)
  • Migration status for docker.io (18.09.9+dfsg1-5 to 19.03.4+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for golang-github-containers-image/4.0.1-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docker.io.html
  • 7 days old (needed 5 days)
• dropwatch (- to 1.5.1-1)
  • Migration status for dropwatch (- to 1.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by onlyjob@member.fsf.org
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• dtmf2num (- to 0.1.1-1)
  • Migration status for dtmf2num (- to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kilobyte
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• eviacam (- to 2.1.4-1)
  • Migration status for eviacam (- to 2.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating eviacam introduces new bugs: #915708, #922578
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eviacam.html
  • 7 days old (needed 5 days)
• fontparts (- to 0.8.7-2)
  • Migration status for fontparts (- to 0.8.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for fontparts/0.8.7-2: amd64: Regression ♻
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• freeboard (- to 1.1.0+dfsg.1-2)
  • Migration status for freeboard (- to 1.1.0+dfsg.1-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 7 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gau2grid (- to 2.0.4-1)
  • Migration status for gau2grid (- to 2.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gau2grid introduces new bugs: #942242
  • Not built on buildd: arch amd64 binaries uploaded by mbanck
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gau2grid.html
  • 7 days old (needed 5 days)
• golang-github-gofrs-uuid (- to 3.2.0-1)
  • Migration status for golang-github-gofrs-uuid (- 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 onlyjob@member.fsf.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• golang-github-ovh-go-ovh (- to 0.0~git20181109.ba5adb4-4)
  • Migration status for golang-github-ovh-go-ovh (- to 0.0~git20181109.ba5adb4-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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ovh-go-ovh.html
  • 7 days old (needed 5 days)
• golang-github-zclconf-go-cty (- to 1.1.0-1)
  • Migration status for golang-github-zclconf-go-cty (- 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 onlyjob@member.fsf.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• ima-evm-utils (- to 1.1-1)
  • Migration status for ima-evm-utils (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by wart
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• libbio-db-ace-perl (- to 1.7.3-1)
  • Migration status for libbio-db-ace-perl (- to 1.7.3-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 7 days)
• libcxx-serial (- to 1.2.1-1.1)
  • Migration status for libcxx-serial (- to 1.2.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libcxx-serial introduces new bugs: #921697
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcxx-serial.html
  • 7 days old (needed 5 days)
• linux-signed-arm64 (5.2.17+1 to 5.3.9+1)
  • Migration status for linux-signed-arm64 (5.2.17+1 to 5.3.9+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • linux-signed-arm64 unsatisfiable Build-Depends(-Arch) on arm64: linux-support-5.3.0-2 (= 5.3.9-1)
  • linux-signed-arm64 unsatisfiable Build-Depends(-Arch) on arm64: linux-image-5.3.0-2-arm64-unsigned (= 5.3.9-1) [arm64]
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• ltsp (5.18.12-3 to 19.11-1)
  • Migration status for ltsp (5.18.12-3 to 19.11-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 mipsel
  • missing build on ppc64el
  • missing build on s390x
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ltsp.html
  • 7 days old (needed 5 days)
• lwt-log (- to 1.1.1-1)
  • Migration status for lwt-log (- to 1.1.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• mlpost (0.8.1-8 to 0.8.2-1)
  • Migration status for mlpost (0.8.1-8 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlpost.html
  • 7 days old (needed 5 days)
• ocaml-batteries (2.6.0-1 to 2.10.0-1)
  • Migration status for ocaml-batteries (2.6.0-1 to 2.10.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-batteries.html
  • 7 days old (needed 5 days)
• ocaml-sedlex (2.1-1 to 2.1-3)
  • Migration status for ocaml-sedlex (2.1-1 to 2.1-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-sedlex.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• panicparse (- to 1.3.0-2)
  • Migration status for panicparse (- to 1.3.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• patsy (0.5.0+git13-g54dcf7b-1 to 0.5.1-0.2)
  • Migration status for patsy (0.5.0+git13-g54dcf7b-1 to 0.5.1-0.2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/patsy.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• plaso (20190131-1 to 20190131-2)
  • Migration status for plaso (20190131-1 to 20190131-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • 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/p/plaso.html
  • 7 days old (needed 5 days)
• postfix-mta-sts-resolver (- to 0.6.0-1)
  • Migration status for postfix-mta-sts-resolver (- 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 kroeckx, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• potool (0.17-1 to 0.18-1)
  • Migration status for potool (0.17-1 to 0.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by porridge
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/potool.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• prometheus-ipmi-exporter (- to 1.0.0+ds-1)
  • Migration status for prometheus-ipmi-exporter (- to 1.0.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bdrung
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• pyrundeck (- to 0.9.7-1)
  • Migration status for pyrundeck (- to 0.9.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by bdrung, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• python-aioamqp (0.12.0-1 to 0.13.0-1)
  • Migration status for python-aioamqp (0.12.0-1 to 0.13.0-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 7 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioamqp.html
• python-asgiref (3.2.2-1 to 3.2.3-1)
  • Migration status for python-asgiref (3.2.2-1 to 3.2.3-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 7 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-asgiref.html
• python-channels-redis (2.3.3-1 to 2.4.1-1)
  • Migration status for python-channels-redis (2.3.3-1 to 2.4.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 7 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-channels-redis.html
• python-jaraco.functools (- to 2.0-2)
  • Migration status for python-jaraco.functools (- to 2.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• python-ospurge (- to 2.0.0+2019.10.11.git.990287677b-1)
  • Migration status for python-ospurge (- to 2.0.0+2019.10.11.git.990287677b-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• python-sop (- to 0.2.0-1)
  • Migration status for python-sop (- 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 dkg, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• q2-demux (- to 2019.4.1-1)
  • Migration status for q2-demux (- to 2019.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for q2-demux/2019.4.1-1: amd64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
  • q2-demux/i386 unsatisfiable Depends: python3-skbio
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• qflow (1.3.17+dfsg.1-1 to 1.3.17+dfsg.1-2)
  • Migration status for qflow (1.3.17+dfsg.1-1 to 1.3.17+dfsg.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): qflow opensta (not considered)
  • Depends: qflow opensta (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qflow.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 7 days)
• r-cran-rsample (- to 0.0.5-2)
  • Migration status for r-cran-rsample (- to 0.0.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): r-cran-rsample r-cran-furrr (not considered)
  • Depends: r-cran-rsample r-cran-furrr (not considered)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-uwot (- to 0.1.4-1)
  • Migration status for r-cran-uwot (- to 0.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): r-cran-uwot r-cran-dqrng (not considered)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• rust-ammonia (- to 3.0.0-1)
  • Migration status for rust-ammonia (- to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• rust-crypto-mac (- to 0.7.0-1)
  • Migration status for rust-crypto-mac (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• rust-expat-sys (- to 2.1.6-1)
  • Migration status for rust-expat-sys (- to 2.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bugzilla@tut.by
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• rust-gstreamer-base (- to 0.14.4-1)
  • Migration status for rust-gstreamer-base (- to 0.14.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-gstreamer-base/0.14.4-1: amd64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by slomo
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• rust-gstreamer-base-sys (- to 0.8.0-1)
  • Migration status for rust-gstreamer-base-sys (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by slomo
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• rust-parse-arg (- to 0.1.4-1)
  • Migration status for rust-parse-arg (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• rust-rfc822-sanitizer (- to 0.3.3-1)
  • Migration status for rust-rfc822-sanitizer (- to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• rust-selectors (- to 0.21.0-1)
  • Migration status for rust-selectors (- to 0.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-selectors/0.21.0-1: amd64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• rust-sequoia-openpgp (- to 0.11.0-1)
  • Migration status for rust-sequoia-openpgp (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by dkg
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• six (1.12.0-2 to 1.13.0-1)
  • Migration status for six (1.12.0-2 to 1.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python-mox/0.7.8-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/six.html
  • 7 days old (needed 5 days)
• spamoracle (1.4-16 to 1.6-1)
  • Migration status for spamoracle (1.4-16 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Updating spamoracle fixes old bugs: #944235
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spamoracle.html
  • 7 days old (needed 5 days)
• splash (2.9.0-2 to 2.9.1-1)
  • Migration status for splash (2.9.0-2 to 2.9.1-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 7 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/splash.html
• tnseq-transit (2.5.2-1 to 3.0.1-1)
  • Migration status for tnseq-transit (2.5.2-1 to 3.0.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): tnseq-transit python-pypubsub (not considered)
  • Depends: tnseq-transit python-pypubsub (not considered)
  • Additional info:
  • Updating tnseq-transit fixes old bugs: #938674
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tnseq-transit.html
  • 7 days old (needed 5 days)
• tpm-udev (- to 0.2)
  • Migration status for tpm-udev (- to 0.2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 7 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• xhk (- to 1.1-1)
  • Migration status for xhk (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bartm
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 7 days old (needed 5 days)
• ansimarkup (- to 1.4.0-1)
  • Migration status for ansimarkup (- to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by mckinstry
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• azure-cosmos-python (- to 2.3.3-1)
  • Migration status for azure-cosmos-python (- to 2.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by luca.boccassi@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• bzr-loom (- to 2.2.0+brz)
  • Migration status for bzr-loom (- to 2.2.0+brz): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by jelmer, a new source-only upload is needed to allow migration
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • bzr-loom/amd64 unsatisfiable Depends: brz-loom
  • bzr-loom/i386 unsatisfiable Depends: brz-loom
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• compyle (- to 0.6~dev0~20190922.gitaa5a50d-1)
  • Migration status for compyle (- to 0.6~dev0~20190922.gitaa5a50d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by gladky.anton@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• cpu-x (- to 3.2.4-1)
  • Migration status for cpu-x (- to 3.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by mike.gabriel@das-netzwerkteam.de
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• endlessh (- to 1.0-1)
  • Migration status for endlessh (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by nicoo
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• errbot (- to 6.1.1+ds-1)
  • Migration status for errbot (- to 6.1.1+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on arm64
  • missing build on mips64el
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• fbset (2.1-30 to 2.1-31)
  • Migration status for fbset (2.1-30 to 2.1-31): Waiting for test results, 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/f/fbset.html
• filesaver.js (- to 2.0.2-1)
  • Migration status for filesaver.js (- to 2.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by nik@naturalnet.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• flask-jwt-simple (- to 0.0.3-1)
  • Migration status for flask-jwt-simple (- to 0.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for flask-jwt-simple/0.0.3-1: amd64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• git-revise (- to 0.4.2-1)
  • Migration status for git-revise (- to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by anarcat@koumbit.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• gitbatch (- to 0.5.0-1)
  • Migration status for gitbatch (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • gitbatch/amd64 has unsatisfiable Built-Using on golang-1.12 1.12.9-2
  • Not built on buildd: arch amd64 binaries uploaded by ssgelm@gmail.com
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• glulxe (- to 0.5.4-1)
  • Migration status for glulxe (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • glulxe unsatisfiable Build-Depends(-Arch) on amd64: libglktermw-dev (>= 1.0.4-2)
  • Not built on buildd: arch amd64 binaries uploaded by jgoerzen
  • Too young, only 8 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• golang-github-containers-buildah (- to 1.10.1-3)
  • Migration status for golang-github-containers-buildah (- to 1.10.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for golang-github-containers-buildah/1.10.1-3: amd64: Regression ♻
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• golang-github-miekg-mmark (1.3.6+dfsg-1 to 1.3.6+dfsg-2)
  • Migration status for golang-github-miekg-mmark (1.3.6+dfsg-1 to 1.3.6+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mmark/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mmark/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mmark/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mmark/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mmark/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mmark/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mmark/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mmark/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mmark/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-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 mipsel
  • missing build on ppc64el
  • missing build on s390x
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-miekg-mmark.html
  • 8 days old (needed 5 days)
• hoteldruid (2.3.2-1 to 3.0.0-1)
  • Migration status for hoteldruid (2.3.2-1 to 3.0.0-1): Waiting for test results, 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/h/hoteldruid.html
• hw-probe (- to 1.4-1)
  • Migration status for hw-probe (- to 1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mathieu.malaterre@gmail.com, a new source-only upload is needed to allow migration
  • Too young, only 8 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• intellij-java-compatibility (- to 1.0.1-1)
  • Migration status for intellij-java-compatibility (- 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 ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• jengelman-shadow (- to 4.0.3-1)
  • Migration status for jengelman-shadow (- to 4.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by seamlikok@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• junit5 (- to 5.3.2-1)
  • Migration status for junit5 (- to 5.3.2-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• jupyter-sphinx (- to 0.1.4-1)
  • Migration status for jupyter-sphinx (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by picca, a new source-only upload is needed to allow migration
  • Too young, only 8 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• kcollectd (- to 0.10.2-1)
  • Migration status for kcollectd (- to 0.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bugs@sandroknauss.de
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• kirigami-gallery (- to 19.04.3-1)
  • Migration status for kirigami-gallery (- to 19.04.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by perezmeyer@gmail.com
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• knitpy (- to 0.1.1~git20180430-1)
  • Migration status for knitpy (- to 0.1.1~git20180430-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by miriam, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• libdc1394 (- to 2.2.6-1)
  • Migration status for libdc1394 (- to 2.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by guus
  • Not built on buildd: arch all binaries uploaded by guus, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• libinsane (- to 1.0.1-1)
  • Migration status for libinsane (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kilobyte
  • Not built on buildd: arch all binaries uploaded by kilobyte, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• libkainjow-mustache (- to 3.2.1+ds-1)
  • Migration status for libkainjow-mustache (- to 3.2.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by legoktm@riseup.net
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• libpicocontainer1-java (- to 1.3-1)
  • Migration status for libpicocontainer1-java (- to 1.3-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• libslirp (- to 4.0.0-1)
  • Migration status for libslirp (- to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by mjt
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• localslackirc (1.4-1 to 1.5-1)
  • Migration status for localslackirc (1.4-1 to 1.5-1): Waiting for test results, 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/l/localslackirc.html
• lwt (2.7.1-7 to 4.3.0-2)
  • Migration status for lwt (2.7.1-7 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lwt.html
  • 8 days old (needed 5 days)
• medialibrary (- to 0.6.0-1)
  • Migration status for medialibrary (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by s.ramacher@gmail.com
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• namecheap (- to 0.0.3-2)
  • Migration status for namecheap (- to 0.0.3-2): 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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• networkx (- to 2.4-2)
  • Migration status for networkx (- to 2.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for androguard/3.3.5-1: amd64: Regression ♻
  • autopkgtest for hyperkitty/1.3.0-1: amd64: Regression ♻
  • autopkgtest for skimage/0.14.2-3: amd64: Regression ♻
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• ocaml-gen (0.5-1 to 0.5.2-2)
  • Migration status for ocaml-gen (0.5-1 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-gen.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• openkim-models (- to 20190331-1)
  • Migration status for openkim-models (- to 20190331-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • openkim-models unsatisfiable Build-Depends(-Arch) on amd64: libkim-api-dev
  • Not built on buildd: arch amd64 binaries uploaded by gladky.anton@gmail.com
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • openkim-models/amd64 unsatisfiable Depends: libkim-api2 (>= 2.1.0)
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• opensta (- to 0~20191010git56851ed+dfsg-1)
  • Migration status for opensta (- to 0~20191010git56851ed+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ruben.undheim@gmail.com
  • Too young, only 8 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• pandas (0.23.3+dfsg-8 to 0.25.3+dfsg-4)
  • Migration status for pandas (0.23.3+dfsg-8 to 0.25.3+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for dask/1.0.0+dfsg-2: amd64: Regression ♻
  • autopkgtest for python-feather-format/0.3.1+dfsg1-2: amd64: Regression ♻
  • autopkgtest for python-skbio/0.5.5-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pandas.html
  • 8 days old (needed 5 days)
• phpmyadmin (- to 4:4.9.1+dfsg1-2)
  • Migration status for phpmyadmin (- to 4:4.9.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for phpmyadmin/4:4.9.1+dfsg1-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpmyadmin.html
  • 8 days old (needed 5 days)
• protobuf2 (- to 2.6.1-3)
  • Migration status for protobuf2 (- to 2.6.1-3): 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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• pulseaudio-qt (- to 1.1.0-1)
  • Migration status for pulseaudio-qt (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by perezmeyer@gmail.com
  • Not built on buildd: arch all binaries uploaded by perezmeyer@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• pymupdf (- to 1.14.16-1)
  • Migration status for pymupdf (- to 1.14.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by josch
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• python-aiosqlite (- to 0.10.0-1)
  • Migration status for python-aiosqlite (- 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 kroeckx, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• python-deeptoolsintervals (- to 0.1.9-1)
  • Migration status for python-deeptoolsintervals (- to 0.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by moeller
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• python-flask-jwt-extended (- to 3.21.0-1)
  • Migration status for python-flask-jwt-extended (- to 3.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• python-flask-seeder (- to 0.1~a2-1)
  • Migration status for python-flask-seeder (- to 0.1~a2-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• python-gntp (- to 1.0.3-1)
  • Migration status for python-gntp (- 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 jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• python-ldapdomaindump (- to 0.9.1-1)
  • Migration status for python-ldapdomaindump (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by hertzog, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• python-networkx (2.2-1 to 2.2-5)
  • Migration status for python-networkx (2.2-1 to 2.2-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Updating python-networkx fixes old bugs: #932679, #933581
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-networkx.html
  • 8 days old (needed 5 days)
• python-pamqp (- to 2.3.0-1)
  • Migration status for python-pamqp (- 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 fladi, a new source-only upload is needed to allow migration
  • Too young, only 8 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-pynetstring (- to 0.2-1)
  • Migration status for python-pynetstring (- to 0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by kroeckx, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• python-pyperform (- to 1.86-1)
  • Migration status for python-pyperform (- to 1.86-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• q2-feature-classifier (- to 2019.4.0-1)
  • Migration status for q2-feature-classifier (- to 2019.4.0-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:
  • q2-feature-classifier/i386 unsatisfiable Depends: python3-skbio
  • q2-feature-classifier/i386 unsatisfiable Depends: vsearch
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• q2-feature-table (- to 2019.4.0+dfsg-1)
  • Migration status for q2-feature-table (- to 2019.4.0+dfsg-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:
  • q2-feature-table/i386 unsatisfiable Depends: python3-skbio
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• q2-quality-filter (- to 2019.4.0-1)
  • Migration status for q2-quality-filter (- to 2019.4.0-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• qlcplus (- to 4.12.2-1)
  • Migration status for qlcplus (- to 4.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by perezmeyer@gmail.com
  • Not built on buildd: arch all binaries uploaded by perezmeyer@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• qosmic (- to 1.6.0-1)
  • Migration status for qosmic (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by jonathan@bluemosh.com
  • Too young, only 8 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• r-cran-bdgraph (- to 2.61-1)
  • Migration status for r-cran-bdgraph (- to 2.61-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-dqrng (- to 0.2.1+dfsg-1)
  • Migration status for r-cran-dqrng (- to 0.2.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for r-cran-dqrng/0.2.1+dfsg-1: amd64: Regression ♻
  • r-cran-dqrng unsatisfiable Build-Depends(-Arch) on amd64: r-cran-sitmo (>= 2.0.0)
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• r-cran-pcapp (- to 1.9-73-1)
  • Migration status for r-cran-pcapp (- to 1.9-73-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by moeller
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-rockchalk (- to 1.8.144+dfsg-1)
  • Migration status for r-cran-rockchalk (- to 1.8.144+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • r-cran-rockchalk unsatisfiable Build-Depends(-Arch) on amd64: r-cran-kutils
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • r-cran-rockchalk/amd64 unsatisfiable Depends: r-cran-kutils
  • r-cran-rockchalk/i386 unsatisfiable Depends: r-cran-kutils
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• rasterview (- to 1.7.1-1)
  • Migration status for rasterview (- to 1.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by odyx
  • Too young, only 8 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• rust-array-init (- to 0.1.0-1)
  • Migration status for rust-array-init (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by slomo
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• rust-byte-slice-cast (- to 0.3.2-1)
  • Migration status for rust-byte-slice-cast (- to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by slomo
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• rust-cc (1.0.37-1 to 1.0.46-1)
  • Migration status for rust-cc (1.0.37-1 to 1.0.46-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cc.html
  • 8 days old (needed 5 days)
• rust-gstreamer (- to 0.14.5-1)
  • Migration status for rust-gstreamer (- to 0.14.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by slomo
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • librust-gstreamer+futures-dev/amd64 unsatisfiable Depends: librust-futures-core-preview-0.3+default-dev
  • librust-gstreamer+futures-dev/arm64 unsatisfiable Depends: librust-futures-core-preview-0.3+default-dev
  • librust-gstreamer+futures-dev/armel unsatisfiable Depends: librust-futures-core-preview-0.3+default-dev
  • librust-gstreamer+futures-dev/armhf unsatisfiable Depends: librust-futures-core-preview-0.3+default-dev
  • librust-gstreamer+futures-dev/i386 unsatisfiable Depends: librust-futures-core-preview-0.3+default-dev
  • librust-gstreamer+futures-dev/mips64el unsatisfiable Depends: librust-futures-core-preview-0.3+default-dev
  • librust-gstreamer+futures-dev/ppc64el unsatisfiable Depends: librust-futures-core-preview-0.3+default-dev
  • librust-gstreamer+futures-dev/s390x unsatisfiable Depends: librust-futures-core-preview-0.3+default-dev
  • librust-gstreamer+paste-dev/amd64 unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+paste-dev/arm64 unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+paste-dev/armel unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+paste-dev/armhf unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+paste-dev/i386 unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+paste-dev/mips64el unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+paste-dev/ppc64el unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+paste-dev/s390x unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+ser-de-dev/amd64 unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+ser-de-dev/arm64 unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+ser-de-dev/armel unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+ser-de-dev/armhf unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+ser-de-dev/i386 unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+ser-de-dev/mips64el unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+ser-de-dev/ppc64el unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+ser-de-dev/s390x unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+serde-bytes-dev/amd64 unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+serde-bytes-dev/arm64 unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+serde-bytes-dev/armel unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+serde-bytes-dev/armhf unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+serde-bytes-dev/i386 unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+serde-bytes-dev/mips64el unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+serde-bytes-dev/ppc64el unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+serde-bytes-dev/s390x unsatisfiable Depends: librust-serde-bytes-0.11+default-dev
  • librust-gstreamer+subclassing-dev/amd64 unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+subclassing-dev/arm64 unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+subclassing-dev/armel unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+subclassing-dev/armhf unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+subclassing-dev/i386 unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+subclassing-dev/mips64el unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+subclassing-dev/ppc64el unsatisfiable Depends: librust-paste-0.1+default-dev
  • librust-gstreamer+subclassing-dev/s390x unsatisfiable Depends: librust-paste-0.1+default-dev
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• rust-gstreamer-sys (- to 0.8.0-1)
  • Migration status for rust-gstreamer-sys (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by slomo
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• rust-hexyl (0.5.1-1 to 0.6.0-2)
  • Migration status for rust-hexyl (0.5.1-1 to 0.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-hexyl rust-ansi-term (not considered)
  • Depends: rust-hexyl rust-ansi-term (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hexyl.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• rust-timerfd (1.0.0-1 to 1.0.0-2)
  • Migration status for rust-timerfd (1.0.0-1 to 1.0.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-timerfd.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• rust-tokio-sync (- to 0.1.7-1)
  • Migration status for rust-tokio-sync (- to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• rust-try-from (- to 0.3.2-1)
  • Migration status for rust-try-from (- to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-try-from/0.3.2-1: amd64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• sagemath (- to 8.9-2)
  • Migration status for sagemath (- to 8.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sagemath introduces new bugs: #920147, #944648
  • sagemath unsatisfiable Build-Depends(-Arch) on armhf: liblinbox-dev (>= 1.6.3)
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagemath.html
  • 8 days old (needed 5 days)
• seriousproton (- to 2019.05.21+dfsg-1)
  • Migration status for seriousproton (- to 2019.05.21+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by nicoo
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• skewer (- to 0.2.2-1)
  • Migration status for skewer (- to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by moeller
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• statsmodels (0.9.0-6 to 0.10.1-5)
  • Migration status for statsmodels (0.9.0-6 to 0.10.1-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/statsmodels.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• stopmotion (0.8.4-3 to 0.8.5-1)
  • Migration status for stopmotion (0.8.4-3 to 0.8.5-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stopmotion.html
  • 8 days old (needed 5 days)
• systune (0.5.8 to 0.5.9)
  • Migration status for systune (0.5.8 to 0.5.9): Waiting for test results, 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/s/systune.html
• thunderbird (1:60.9.0-1 to 1:68.2.2-1)
  • Migration status for thunderbird (1:60.9.0-1 to 1:68.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating thunderbird introduces new bugs: #944715
  • Additional info:
  • Updating thunderbird fixes old bugs: #925841
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thunderbird.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• trololio (- to 1.0-1)
  • Migration status for trololio (- to 1.0-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• tuareg-mode (1:2.1.0-2 to 1:2.1.0-3)
  • Migration status for tuareg-mode (1:2.1.0-2 to 1:2.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by treinen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tuareg-mode.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• vdjtools (- to 1.2.1+git20190311-1)
  • Migration status for vdjtools (- to 1.2.1+git20190311-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for vdjtools/1.2.1+git20190311-1: amd64: Regression ♻
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• watcher-dashboard (- to 2.0.0-2)
  • Migration status for watcher-dashboard (- to 2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by arbet.michal@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 8 days old (needed 5 days)
• canu (1.8+dfsg-2 to 1.9+dfsg-1)
  • Migration status for canu (1.8+dfsg-2 to 1.9+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/canu.html
  • 9 days old (needed 5 days)
• cupt (2.10.3 to 2.10.4)
  • Migration status for cupt (2.10.3 to 2.10.4): Waiting for test results, 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/c/cupt.html
• django-prometheus (- to 1.1.0-1)
  • Migration status for django-prometheus (- 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 fladi, a new source-only upload is needed to allow migration
  • Too young, only 9 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• enigmail (2:2.0.12+ds1-1 to 2:2.1.3+ds1-4)
  • Migration status for enigmail (2:2.0.12+ds1-1 to 2:2.1.3+ds1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: enigmail thunderbird (not considered)
  • Additional info:
  • Updating enigmail fixes old bugs: #933832
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enigmail.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• gcc-snapshot (- to 1:20191110-1)
  • Migration status for gcc-snapshot (- to 1:20191110-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gcc-snapshot introduces new bugs: #321449, #651291
  • missing build on amd64
  • missing build on i386
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-snapshot.html
  • 9 days old (needed 5 days)
• gimp (2.10.12-1 to 2.10.14-1)
  • Migration status for gimp (2.10.12-1 to 2.10.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • gimp unsatisfiable Build-Depends(-Arch) on amd64: libgegl-dev (>= 0.4.18)
  • gimp unsatisfiable Build-Depends(-Arch) on arm64: libgegl-dev (>= 0.4.18)
  • gimp unsatisfiable Build-Depends(-Arch) on armel: libgegl-dev (>= 0.4.18)
  • gimp unsatisfiable Build-Depends(-Arch) on armhf: libgegl-dev (>= 0.4.18)
  • gimp unsatisfiable Build-Depends(-Arch) on mips64el: libgegl-dev (>= 0.4.18)
  • gimp unsatisfiable Build-Depends(-Arch) on mipsel: libgegl-dev (>= 0.4.18)
  • gimp unsatisfiable Build-Depends(-Arch) on s390x: libgegl-dev (>= 0.4.18)
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • missing build on s390x
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • gimp/i386 unsatisfiable Depends: gimp-data (>= 2.10.14)
  • gimp/ppc64el unsatisfiable Depends: gimp-data (>= 2.10.14)
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gimp.html
  • 9 days old (needed 5 days)
• ginac (1.7.8-1 to 1.7.8-2)
  • Migration status for ginac (1.7.8-1 to 1.7.8-2): Waiting for test results, 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/g/ginac.html
• golang-github-apparentlymart-go-textseg (- to 1.0.0-1)
  • Migration status for golang-github-apparentlymart-go-textseg (- 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 onlyjob@member.fsf.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• golang-github-rs-cors (- to 1.7.0-1)
  • Migration status for golang-github-rs-cors (- to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by onlyjob@member.fsf.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• golang-github-toqueteos-webbrowser (- to 1.2.0+git20190725.dc97d39-1)
  • Migration status for golang-github-toqueteos-webbrowser (- to 1.2.0+git20190725.dc97d39-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by iwamatsu, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• haskell-genvalidity-containers (- to 0.5.1.1-1)
  • Migration status for haskell-genvalidity-containers (- to 0.5.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by schizo
  • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
  • Too young, only 9 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• haskell-gi-cairo-render (- to 0.0.1-1)
  • Migration status for haskell-gi-cairo-render (- to 0.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by schizo
  • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
  • Too young, only 9 of 10 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• haskell-git-lfs (- to 1.1.0-1)
  • Migration status for haskell-git-lfs (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by spwhitton@spwhitton.name
  • Not built on buildd: arch all binaries uploaded by spwhitton@spwhitton.name, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 9 days old (needed 5 days)
• haskell-http-client-restricted (- to 0.0.1-1)
  • Migration status for haskell-http-client-restricted (- to 0.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by spwhitton@spwhitton.name
  • Not built on buildd: arch all binaries uploaded by spwhitton@spwhitton.name, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 9 days old (needed 5 days)
• isbg (- to 2.1.5-1)
  • Migration status for isbg (- to 2.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 9 days old (needed 5 days)
• kernel-wedge (2.99 to 2.100)
  • Migration status for kernel-wedge (2.99 to 2.100): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kernel-wedge/2.100: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kernel-wedge.html
  • 9 days old (needed 5 days)
• libdrm (2.4.99-1 to 2.4.100-3)
  • Migration status for libdrm (2.4.99-1 to 2.4.100-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libdrm introduces new bugs: #944752
  • Not built on buildd: arch amd64 binaries uploaded by tjaalton@ubuntu.com
  • Not built on buildd: arch all binaries uploaded by tjaalton@ubuntu.com, a new source-only upload is needed to allow migration
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdrm.html
  • 9 days old (needed 5 days)
• ocaml-ptmap (2.0.4-2 to 2.0.4-3)
  • Migration status for ocaml-ptmap (2.0.4-2 to 2.0.4-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-ptmap.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• ocaml-rope (0.6.2-1 to 0.6.2-2)
  • Migration status for ocaml-rope (0.6.2-1 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-rope.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• pgcluu (- to 2.9-1)
  • Migration status for pgcluu (- to 2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by myon, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• php-netscape-bookmark-parser (- to 2.1.0-1)
  • Migration status for php-netscape-bookmark-parser (- to 2.1.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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• php-pcov (- to 1.0.6-1)
  • Migration status for php-pcov (- to 1.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ondrej
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 9 days old (needed 5 days)
• php-psr (- to 0.7.0-1)
  • Migration status for php-psr (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ondrej
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 9 days old (needed 5 days)
• r-cran-proc (- to 1.15.3-2)
  • Migration status for r-cran-proc (- to 1.15.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for r-cran-proc/1.15.3-2: amd64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by moeller
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 9 days old (needed 5 days)
• r-cran-regsem (- to 1.3.9+dfsg-1)
  • Migration status for r-cran-regsem (- to 1.3.9+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-rpf (- to 0.62+dfsg-1)
  • Migration status for r-cran-rpf (- to 0.62+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-semplot (- to 1.1.2-1)
  • Migration status for r-cran-semplot (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for r-cran-semplot/1.1.2-1: amd64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 9 days old (needed 5 days)
• r-cran-splines2 (- to 0.2.8-1)
  • Migration status for r-cran-splines2 (- to 0.2.8-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• ruby-jekyll-remote-theme (- to 0.4.1-1)
  • Migration status for ruby-jekyll-remote-theme (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for ruby-jekyll-remote-theme/0.4.1-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-remote-theme.html
  • 9 days old (needed 5 days)
• rust-buffered-reader (0.7.0-2 to 0.11.0-1)
  • Migration status for rust-buffered-reader (0.7.0-2 to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-buffered-reader/0.11.0-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-buffered-reader.html
  • 9 days old (needed 5 days)
• rust-rand-os (0.1.1-2 to 0.2.2-1)
  • Migration status for rust-rand-os (0.1.1-2 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rand-os.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• rust-rdrand (0.4.0-1 to 0.6.0-1)
  • Migration status for rust-rdrand (0.4.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-rand-os/0.1.1-2: amd64: Regression ♻
  • autopkgtest for rust-rdrand/0.6.0-1: amd64: Regression ♻
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rdrand.html
  • 9 days old (needed 5 days)
• rust-sysinfo (0.9.5-2 to 0.9.6-1)
  • Migration status for rust-sysinfo (0.9.5-2 to 0.9.6-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sysinfo.html
  • 9 days old (needed 5 days)
• testinfra (- to 3.2.0-1)
  • Migration status for testinfra (- 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 seb, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 9 days old (needed 5 days)
• visp (- to 3.2.0-1)
  • Migration status for visp (- to 3.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating visp introduces new bugs: #944548
  • Not built on buildd: arch amd64 binaries uploaded by olivier.sallou@irisa.fr
  • Not built on buildd: arch all binaries uploaded by olivier.sallou@irisa.fr, a new source-only upload is needed to allow migration
  • missing build on armel
  • missing build on armhf
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • libvisp-detection3.2/amd64 unsatisfiable Depends: libdmtx0a (>= 0.7.0)
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/visp.html
  • 9 days old (needed 5 days)
• bcbio (1.1.2-3 to 1.1.7-1)
  • Migration status for bcbio (1.1.2-3 to 1.1.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): bcbio tophat-recondition (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bcbio.html
  • 10 days old (needed 5 days)
• chromium (- to 78.0.3904.97-1)
  • Migration status for chromium (- to 78.0.3904.97-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating chromium introduces new bugs: #944627
  • missing build on armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chromium.html
  • 10 days old (needed 5 days)
• coq (8.9.1-1 to 8.9.1-2)
  • Migration status for coq (8.9.1-1 to 8.9.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq.html
  • 10 days old (needed 5 days)
• firefox (- to 70.0.1-1)
  • Migration status for firefox (- to 70.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating firefox introduces new bugs: #817954, #871947, #888423, #909286, #915582
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox.html
  • 10 days old (needed 5 days)
• gegl (0.4.16-2 to 0.4.18-1)
  • Migration status for gegl (0.4.16-2 to 0.4.18-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 mips64el
  • missing build on mipsel
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gegl.html
  • 10 days old (needed 5 days)
• hurd (- to 1:0.9.git20191029-3)
  • Migration status for hurd (- to 1:0.9.git20191029-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hurd introduces new bugs: #650080, #838244, #943307
  • hurd unsatisfiable Build-Depends(-Arch) on amd64: mig (>= 1.4-3~)
  • hurd unsatisfiable Build-Depends(-Arch) on amd64: gnumach-dev (>= 2:1.8+git20170102-1~)
  • hurd unsatisfiable Build-Depends(-Arch) on amd64: libc0.3-dev (>= 2.17-94~)
  • 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
  • 10 days old (needed 5 days)
• morbig (0.9.1-3 to 0.10.4-2)
  • Migration status for morbig (0.9.1-3 to 0.10.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morbig.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• morsmall (0.1-1 to 0.3.0-1)
  • Migration status for morsmall (0.1-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morsmall.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• node-media-typer (0.3.0-3 to 1.1.0-1)
  • Migration status for node-media-typer (0.3.0-3 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for node-type-is/1.6.16-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-media-typer.html
  • 10 days old (needed 5 days)
• ocaml-gstreamer (0.2.0-2 to 0.3.0-2)
  • Migration status for ocaml-gstreamer (0.2.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-gstreamer.html
  • 10 days old (needed 5 days)
• ocaml-lo (0.1.0-1 to 0.1.2-1)
  • Migration status for ocaml-lo (0.1.0-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-lo.html
  • 10 days old (needed 5 days)
• ocaml-mm (0.4.1-2 to 0.5.0-1)
  • Migration status for ocaml-mm (0.4.1-2 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-mm.html
  • 10 days old (needed 5 days)
• ocaml-qcheck (0.9-2 to 0.11-1)
  • Migration status for ocaml-qcheck (0.9-2 to 0.11-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-qcheck.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• ocamlify (0.0.2-6 to 0.0.2-7)
  • Migration status for ocamlify (0.0.2-6 to 0.0.2-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlify.html
  • 10 days old (needed 5 days)
• php-constant-time (- to 2.3.0-1)
  • Migration status for php-constant-time (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-constant-time introduces new bugs: #892587
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-constant-time.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• python-bx (0.8.2-1 to 0.8.5-1)
  • Migration status for python-bx (0.8.2-1 to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-bx introduces new bugs: #944409
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bx.html
  • 10 days old (needed 5 days)
• roary (3.12.0+dfsg-2 to 3.13.0+dfsg-1)
  • Migration status for roary (3.12.0+dfsg-2 to 3.13.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): roary bioperl (not considered)
  • Depends: roary bioperl (not considered)
  • Additional info:
  • roary/i386 unsatisfiable Depends: bedtools
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/roary.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• ruby-zip (1.2.2-1 to 2.0.0-1)
  • Migration status for ruby-zip (1.2.2-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-zip.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• rust-clang-sys (0.27.0-1 to 0.28.1-2)
  • Migration status for rust-clang-sys (0.27.0-1 to 0.28.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-clang-sys.html
  • 10 days old (needed 5 days)
• rust-fallible-iterator (0.1.6-1 to 0.2.0-1)
  • Migration status for rust-fallible-iterator (0.1.6-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-fallible-iterator/0.2.0-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fallible-iterator.html
  • 10 days old (needed 5 days)
• rust-gumdrop-derive (0.6.0-1 to 0.7.0-1)
  • Migration status for rust-gumdrop-derive (0.6.0-1 to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bugzilla@tut.by
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gumdrop-derive.html
  • 10 days old (needed 5 days)
• rust-num-bigint (0.2.0-1 to 0.2.3-1)
  • Migration status for rust-num-bigint (0.2.0-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rust-num-bigint unsatisfiable Build-Depends(-Arch) on i386: librust-num-traits-0.2+std-dev (>= 0.2.7-~~)
  • rust-num-bigint unsatisfiable Build-Depends(-Arch) on i386: librust-num-traits-0.2-dev (>= 0.2.7-~~)
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • missing build on i386
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • librust-num-bigint+quickcheck-macros-dev/amd64 unsatisfiable Depends: librust-quickcheck-macros-0.8-dev
  • librust-num-bigint+quickcheck-macros-dev/arm64 unsatisfiable Depends: librust-quickcheck-macros-0.8-dev
  • librust-num-bigint+quickcheck-macros-dev/armel unsatisfiable Depends: librust-quickcheck-macros-0.8-dev
  • librust-num-bigint+quickcheck-macros-dev/armhf unsatisfiable Depends: librust-quickcheck-macros-0.8-dev
  • librust-num-bigint+quickcheck-macros-dev/mips64el unsatisfiable Depends: librust-quickcheck-macros-0.8-dev
  • librust-num-bigint+quickcheck-macros-dev/mipsel unsatisfiable Depends: librust-quickcheck-macros-0.8-dev
  • librust-num-bigint+quickcheck-macros-dev/ppc64el unsatisfiable Depends: librust-quickcheck-macros-0.8-dev
  • librust-num-bigint+quickcheck-macros-dev/s390x unsatisfiable Depends: librust-quickcheck-macros-0.8-dev
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-num-bigint.html
  • 10 days old (needed 5 days)
• rust-proc-macro2 (0.4.30-1 to 1.0.6-1)
  • Migration status for rust-proc-macro2 (0.4.30-1 to 1.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-quote/0.6.13-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-macro2.html
  • 10 days old (needed 5 days)
• rust-ring (- to 0.16.9-2)
  • Migration status for rust-ring (- to 0.16.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bugzilla@tut.by
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ring.html
  • 10 days old (needed 5 days)
• rust-syn (0.15.39-1 to 1.0.8-1)
  • Migration status for rust-syn (0.15.39-1 to 1.0.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-syn rust-proc-macro2 (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-syn.html
  • 10 days old (needed 5 days)
• transgui (5.17.0+dfsg-1 to 5.18.0+dfsg-1)
  • Migration status for transgui (5.17.0+dfsg-1 to 5.18.0+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/transgui.html
  • 10 days old (needed 5 days)
• xstrp4 (1.8.2-1 to 1.8.2-2)
  • Migration status for xstrp4 (1.8.2-1 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xstrp4.html
  • 10 days old (needed 5 days)
• camlzip (1.08-1 to 1.09-2)
  • Migration status for camlzip (1.08-1 to 1.09-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camlzip.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• logswan (2.0.4-1 to 2.1.1-1)
  • Migration status for logswan (2.0.4-1 to 2.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
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/logswan.html
  • 11 days old (needed 5 days)
• ocaml (4.05.0-12 to 4.08.1-4)
  • Migration status for ocaml (4.05.0-12 to 4.08.1-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Updating ocaml fixes old bugs: #944126
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml.html
  • 11 days old (needed 5 days)
• ocplib-endian (- to 1.0-1)
  • Migration status for ocplib-endian (- to 1.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 11 days old (needed 5 days)
• pslib (0.4.5-3.1 to 0.4.7-1)
  • Migration status for pslib (0.4.5-3.1 to 0.4.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by steinm
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pslib.html
  • 11 days old (needed 10 days)
• rust-lalrpop (- to 0.17.2-1)
  • Migration status for rust-lalrpop (- to 0.17.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by dkg
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 11 days old (needed 5 days)
• rust-nettle (- to 5.0.3-1)
  • Migration status for rust-nettle (- to 5.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by dkg
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• rust-rand-pcg (0.1.1-1 to 0.2.1-1)
  • Migration status for rust-rand-pcg (0.1.1-1 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/r/rust-rand-pcg.html
  • 11 days old (needed 5 days)
• rust-serde-derive (1.0.98-1 to 1.0.102-1)
  • Migration status for rust-serde-derive (1.0.98-1 to 1.0.102-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-serde-derive rust-proc-macro2 (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde-derive.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• twisted (18.9.0-3 to 18.9.0-5)
  • Migration status for twisted (18.9.0-3 to 18.9.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating twisted introduces new bugs: #943963
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/twisted.html
  • 11 days old (needed 5 days)
• biobambam2 (- to 2.0.147+dfsg-1)
  • Migration status for biobambam2 (- to 2.0.147+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating biobambam2 introduces new bugs: #933937
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biobambam2.html
  • 12 days old (needed 5 days)
• hevea (2.32-2 to 2.32-3)
  • Migration status for hevea (2.32-2 to 2.32-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hevea.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• libmaus2 (- to 2.0.684-1)
  • Migration status for libmaus2 (- to 2.0.684-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libmaus2 introduces new bugs: #934619
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmaus2.html
  • 12 days old (needed 5 days)
• nomad (- to 0.10.1+dfsg1-2)
  • Migration status for nomad (- to 0.10.1+dfsg1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomad.html
  • 12 days old (needed 5 days)
• ocaml-sexplib0 (0.12.0-1 to 0.12.0-2)
  • Migration status for ocaml-sexplib0 (0.12.0-1 to 0.12.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-sexplib0.html
  • 12 days old (needed 5 days)
• orpie (1.5.2-2 to 1.5.2-4)
  • Migration status for orpie (1.5.2-2 to 1.5.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by steinm
  • Additional info:
  • Updating orpie fixes old bugs: #939963
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orpie.html
  • 12 days old (needed 5 days)
• polygen (1.0.6.ds2-18 to 1.0.6.ds2-19)
  • Migration status for polygen (1.0.6.ds2-18 to 1.0.6.ds2-19): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polygen.html
  • 12 days old (needed 5 days)
• prokka (- to 1.14.0+dfsg-1)
  • Migration status for prokka (- to 1.14.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/prokka.html
  • autopkgtest for prokka/1.14.0+dfsg-1: amd64: Regression ♻
  • Additional info:
  • 12 days old (needed 5 days)
• tophide (1.0.4-1 to 1.0.4-2)
  • Migration status for tophide (1.0.4-1 to 1.0.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tophide.html
  • 12 days old (needed 5 days)
• bedtools (2.27.1+dfsg-4 to 2.29.0+dfsg-1)
  • Migration status for bedtools (2.27.1+dfsg-4 to 2.29.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 armhf
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bedtools.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• cups (2.3.0-6 to 2.3.0-7)
  • Migration status for cups (2.3.0-6 to 2.3.0-7): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cups.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• golang-github-dchest-uniuri (- to 0.0~git20160212.8902c56-1)
  • Migration status for golang-github-dchest-uniuri (- to 0.0~git20160212.8902c56-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• golang-github-joyent-gocommon (- to 0.0~git20161202.b787089-1)
  • Migration status for golang-github-joyent-gocommon (- to 0.0~git20161202.b787089-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• golang-github-mattetti-filebuffer (- to 0.0~git20171024.3a1e8e5-1)
  • Migration status for golang-github-mattetti-filebuffer (- to 0.0~git20171024.3a1e8e5-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• golang-github-pearkes-dnsimple (- to 0.0~git20161003.0adf7d0-1)
  • Migration status for golang-github-pearkes-dnsimple (- to 0.0~git20161003.0adf7d0-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• golang-github-soniah-dnsmadeeasy (- to 1.1+git20150117.5578a8c-1)
  • Migration status for golang-github-soniah-dnsmadeeasy (- to 1.1+git20150117.5578a8c-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• golang-github-zorkian-go-datadog-api (- to 2.22.0+git20190822.e9c4097-1)
  • Migration status for golang-github-zorkian-go-datadog-api (- to 2.22.0+git20190822.e9c4097-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• kannel (1.4.5-3 to 1.4.5-5)
  • Migration status for kannel (1.4.5-3 to 1.4.5-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on ppc64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kannel.html
  • 13 days old (needed 5 days)
• nautilus-admin (1.1.9-2 to 1.1.9-3)
  • Migration status for nautilus-admin (1.1.9-2 to 1.1.9-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: nautilus-admin nautilus-python (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-admin.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• nautilus-hide (0.2.3-7 to 0.2.3-8)
  • Migration status for nautilus-hide (0.2.3-7 to 0.2.3-8): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: nautilus-hide nautilus-python (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-hide.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• pcb-rnd (2.1.3-2 to 2.1.4-2)
  • Migration status for pcb-rnd (2.1.3-2 to 2.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pcb-rnd introduces new bugs: #943955
  • missing build on arm64
  • missing build on i386
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcb-rnd.html
  • 13 days old (needed 5 days)
• rygel (0.36.2-4 to 0.38.2-3)
  • Migration status for rygel (0.36.2-4 to 0.38.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rygel unsatisfiable Build-Depends(-Arch) on amd64: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on amd64: libgupnp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on arm64: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on arm64: libgupnp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on armel: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on armel: libgupnp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on armhf: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on armhf: libgupnp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on i386: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on i386: libgupnp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on mips64el: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on mips64el: libgupnp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on mipsel: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on mipsel: libgupnp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on ppc64el: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on ppc64el: libgupnp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on s390x: libgssdp-1.2-dev (>= 1.1.0)
  • rygel unsatisfiable Build-Depends(-Arch) on s390x: libgupnp-1.2-dev (>= 1.1.0)
  • 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 mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rygel.html
  • 13 days old (needed 5 days)
• bpftrace (- to 0.9.2-2)
  • Migration status for bpftrace (- to 0.9.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpftrace.html
  • 14 days old (needed 5 days)
• camlp4 (4.05+2-1 to 4.08+1-1)
  • Migration status for camlp4 (4.05+2-1 to 4.08+1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camlp4.html
  • 14 days old (needed 5 days)
• docker-registry (2.7.1~ds1-2 to 2.7.1~ds1-3)
  • Migration status for docker-registry (2.7.1~ds1-2 to 2.7.1~ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for golang-github-containers-image/4.0.1-2: amd64: Regression ♻
  • docker-registry/mips64el has unsatisfiable Built-Using on golang-1.12 1.12.10-1
  • docker-registry/mipsel has unsatisfiable Built-Using on golang-1.12 1.12.10-1
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docker-registry.html
  • 14 days old (needed 5 days)
• gnome-music (3.32.2-1 to 3.34.1-1)
  • Migration status for gnome-music (3.32.2-1 to 3.34.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • gnome-music unsatisfiable Build-Depends(-Arch) on arm64: libtracker-sparql-2.0-dev (>= 2.2.0)
  • gnome-music unsatisfiable Build-Depends(-Arch) on armel: libtracker-sparql-2.0-dev (>= 2.2.0)
  • gnome-music unsatisfiable Build-Depends(-Arch) on armhf: libtracker-sparql-2.0-dev (>= 2.2.0)
  • gnome-music unsatisfiable Build-Depends(-Arch) on mips64el: libtracker-sparql-2.0-dev (>= 2.2.0)
  • gnome-music unsatisfiable Build-Depends(-Arch) on mipsel: libtracker-sparql-2.0-dev (>= 2.2.0)
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-music.html
  • 14 days old (needed 5 days)
• hlins (0.39-25 to 0.39-26)
  • Migration status for hlins (0.39-25 to 0.39-26): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hlins.html
  • Required age reduced by 3 days because of autopkgtest
  • 14 days old (needed 2 days)
• iwyu (8.0-1 to 8.0-2)
  • Migration status for iwyu (8.0-1 to 8.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iwyu.html
  • 14 days old (needed 5 days)
• labltk (8.06.2+dfsg-1 to 8.06.6+dfsg-1)
  • Migration status for labltk (8.06.2+dfsg-1 to 8.06.6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labltk.html
  • 14 days old (needed 5 days)
• ledit (2.04-3 to 2.04-4)
  • Migration status for ledit (2.04-3 to 2.04-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ledit.html
  • 14 days old (needed 5 days)
• ocaml-num (- to 1.2-2)
  • Migration status for ocaml-num (- to 1.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 14 days old (needed 5 days)
• ocaml-tools (20120103-5 to 20120103-6)
  • Migration status for ocaml-tools (20120103-5 to 20120103-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-tools.html
  • 14 days old (needed 5 days)
• ocamlwc (0.3-15 to 0.3-16)
  • Migration status for ocamlwc (0.3-15 to 0.3-16): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlwc.html
  • Required age reduced by 3 days because of autopkgtest
  • 14 days old (needed 2 days)
• ocamlweb (1.41-2 to 1.41-3)
  • Migration status for ocamlweb (1.41-2 to 1.41-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlweb.html
  • Required age reduced by 3 days because of autopkgtest
  • 14 days old (needed 2 days)
• ppx-tools (5.0+4.05.0-1 to 5.3+4.08.0-1)
  • Migration status for ppx-tools (5.0+4.05.0-1 to 5.3+4.08.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ppx-tools.html
  • 14 days old (needed 5 days)
• python-django (1:1.11.23-1~deb10u1 to 2:2.2.7-1)
  • Migration status for python-django (1:1.11.23-1~deb10u1 to 2:2.2.7-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django.html
  • 14 days old (needed 5 days)
• rust-darling-macro (- to 0.10.2-1)
  • Migration status for rust-darling-macro (- to 0.10.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-darling-macro rust-syn (not considered)
  • Depends: rust-darling-macro rust-syn (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-darling-macro.html
  • Required age reduced by 3 days because of autopkgtest
  • 14 days old (needed 2 days)
• rust-goblin (0.0.19-1 to 0.1.0-1)
  • Migration status for rust-goblin (0.0.19-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-goblin/0.1.0-1: amd64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by bugzilla@tut.by
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-goblin.html
  • 14 days old (needed 5 days)
• rust-scroll (0.9.2-1 to 0.10.1-1)
  • Migration status for rust-scroll (0.9.2-1 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-scroll/0.10.1-1: amd64: Regression ♻
  • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-scroll.html
  • Additional info:
  • 14 days old (needed 5 days)
• rust-stdweb-internal-macros (0.2.5-1 to 0.2.9-1)
  • Migration status for rust-stdweb-internal-macros (0.2.5-1 to 0.2.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-stdweb-internal-macros rust-proc-macro2 (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-stdweb-internal-macros.html
  • Required age reduced by 3 days because of autopkgtest
  • 14 days old (needed 2 days)
• cupp (0.0+20160624.git07f9b8-1 to 0.0+20190501.git986658-3)
  • Migration status for cupp (0.0+20160624.git07f9b8-1 to 0.0+20190501.git986658-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cupp.html
  • 15 days old (needed 5 days)
• frr (6.0.2-2 to 7.2-1)
  • Migration status for frr (6.0.2-2 to 7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating frr introduces new bugs: #944392
  • missing build on mipsel
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frr.html
  • Required age reduced by 3 days because of autopkgtest
  • 15 days old (needed 2 days)
• golang-github-boj-redistore (- to 1.2+git20180917.cd5dcc7-1)
  • Migration status for golang-github-boj-redistore (- to 1.2+git20180917.cd5dcc7-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 15 days old (needed 2 days)
• golang-github-jackc-fake (- to 0.0~git20150926.812a484-1)
  • Migration status for golang-github-jackc-fake (- to 0.0~git20150926.812a484-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 15 days old (needed 2 days)
• golang-github-nrdcg-goinwx (- to 0.6.1-1)
  • Migration status for golang-github-nrdcg-goinwx (- to 0.6.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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 15 days old (needed 2 days)
• golang-github-vultr-govultr (- to 0.1.4+git20190904.cb344cc-1)
  • Migration status for golang-github-vultr-govultr (- to 0.1.4+git20190904.cb344cc-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 15 days old (needed 2 days)
• haskell-hoauth2 (1.7.2-5 to 1.8.7-1)
  • Migration status for haskell-hoauth2 (1.7.2-5 to 1.8.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hoauth2.html
  • 15 days old (needed 5 days)
• haskell-yesod-auth-oauth2 (0.5.2.0-3 to 0.6.1.1-1)
  • Migration status for haskell-yesod-auth-oauth2 (0.5.2.0-3 to 0.6.1.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-yesod-auth-oauth2.html
  • 15 days old (needed 5 days)
• pillow (6.2.0-1 to 6.2.1-2)
  • Migration status for pillow (6.2.0-1 to 6.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for last-align/984-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pillow.html
  • 15 days old (needed 5 days)
• python-easydev (0.9.37-1 to 0.9.38-2)
  • Migration status for python-easydev (0.9.37-1 to 0.9.38-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Updating python-easydev fixes old bugs: #937720
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-easydev.html
  • 15 days old (needed 5 days)
• rust-jemalloc-sys (- to 0.3.2-2)
  • Migration status for rust-jemalloc-sys (- to 0.3.2-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 15 days old (needed 2 days)
• rust-process-viewer (0.2.0-1 to 0.2.6-1)
  • Migration status for rust-process-viewer (0.2.0-1 to 0.2.6-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/rust-process-viewer.html
  • 15 days old (needed 5 days)
• tryton-proteus (5.0.3-2 to 5.0.5-1)
  • Migration status for tryton-proteus (5.0.3-2 to 5.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for tryton-modules-account-fr/5.0.1-2: amd64: Regression ♻
  • autopkgtest for tryton-modules-purchase-request/5.0.2-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tryton-proteus.html
  • 15 days old (needed 5 days)
• why3 (1.2.1-1 to 1.2.1-2)
  • Migration status for why3 (1.2.1-1 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/why3.html
  • Required age reduced by 3 days because of autopkgtest
  • 15 days old (needed 2 days)
• xfsprogs (5.0.0-1 to 5.2.1-1)
  • Migration status for xfsprogs (5.0.0-1 to 5.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by nathans
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfsprogs.html
  • 15 days old (needed 10 days)
• cclib (1.6.1-1 to 1.6.2-1)
  • Migration status for cclib (1.6.1-1 to 1.6.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cclib.html
  • 16 days old (needed 5 days)
• fortran-language-server (- to 1.10.2-1)
  • Migration status for fortran-language-server (- to 1.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by hle, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 16 days old (needed 2 days)
• perl6-tap-harness (- to 0.20190121-1)
  • Migration status for perl6-tap-harness (- to 0.20190121-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: perl6-tap-harness rakudo (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perl6-tap-harness.html
  • 16 days old (needed 5 days)
• pyspread (- to 1.1.3-5)
  • Migration status for pyspread (- to 1.1.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pyspread introduces new bugs: #937544
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyspread.html
  • 16 days old (needed 5 days)
• rust-arc-swap (0.3.11-2 to 0.4.3-1)
  • Migration status for rust-arc-swap (0.3.11-2 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-arc-swap.html
  • 16 days old (needed 5 days)
• rust-backtrace-sys (0.1.28-1 to 0.1.32-1)
  • Migration status for rust-backtrace-sys (0.1.28-1 to 0.1.32-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • librust-backtrace-sys+compiler-builtins-dev/amd64 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+compiler-builtins-dev/arm64 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+compiler-builtins-dev/armel unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+compiler-builtins-dev/armhf unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+compiler-builtins-dev/i386 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+compiler-builtins-dev/mips64el unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+compiler-builtins-dev/mipsel unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+compiler-builtins-dev/ppc64el unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+compiler-builtins-dev/s390x unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/amd64 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/arm64 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/armel unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/armhf unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/i386 unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/mips64el unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/mipsel unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/ppc64el unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • librust-backtrace-sys+rustc-dep-of-std-dev/s390x unsatisfiable Depends: librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~)
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-backtrace-sys.html
  • 16 days old (needed 5 days)
• rust-unicode-segmentation (1.2.1-1 to 1.5.0-1)
  • Migration status for rust-unicode-segmentation (1.2.1-1 to 1.5.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/r/rust-unicode-segmentation.html
  • 16 days old (needed 5 days)
• websocket-client (0.53.0-1 to 0.53.0-2)
  • Migration status for websocket-client (0.53.0-1 to 0.53.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/websocket-client.html
  • 16 days old (needed 5 days)
• cryptsetup (2:2.2.1-1 to 2:2.2.2-1)
  • Migration status for cryptsetup (2:2.2.1-1 to 2:2.2.2-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/c/cryptsetup.html
  • 17 days old (needed 5 days)
• jupyter-notebook (5.7.8-1 to 6.0.0-1)
  • Migration status for jupyter-notebook (5.7.8-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Updating jupyter-notebook fixes old bugs: #936775
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-notebook.html
  • 17 days old (needed 5 days)
• menhir (20190626-6 to 20190924-1)
  • Migration status for menhir (20190626-6 to 20190924-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/menhir.html
  • Required age reduced by 3 days because of autopkgtest
  • 17 days old (needed 2 days)
• rust-combine (- to 3.8.1-1)
  • Migration status for rust-combine (- to 3.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-combine introduces new bugs: #935866
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • librust-combine+combine-regex-1-dev/amd64 unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+combine-regex-1-dev/arm64 unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+combine-regex-1-dev/armel unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+combine-regex-1-dev/armhf unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+combine-regex-1-dev/i386 unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+combine-regex-1-dev/mips64el unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+combine-regex-1-dev/mipsel unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+combine-regex-1-dev/ppc64el unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+combine-regex-1-dev/s390x unsatisfiable Depends: librust-combine-regex-1-1+default-dev
  • librust-combine+doc-dev/amd64 unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+doc-dev/arm64 unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+doc-dev/armel unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+doc-dev/armhf unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+doc-dev/i386 unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+doc-dev/mips64el unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+doc-dev/mipsel unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+doc-dev/ppc64el unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+doc-dev/s390x unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/amd64 unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/arm64 unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/armel unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/armhf unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/i386 unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/mips64el unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/mipsel unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/ppc64el unsatisfiable Depends: librust-regex-0.2+default-dev
  • librust-combine+regex-dev/s390x unsatisfiable Depends: librust-regex-0.2+default-dev
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-combine.html
  • 17 days old (needed 5 days)
• rust-ctor (0.1.9-2 to 0.1.12-1)
  • Migration status for rust-ctor (0.1.9-2 to 0.1.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-ctor rust-syn (not considered)
  • Depends: rust-ctor rust-syn (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ctor.html
  • 17 days old (needed 5 days)
• rust-darling-core (- to 0.10.2-1)
  • Migration status for rust-darling-core (- to 0.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-darling-core/0.10.2-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-darling-core.html
  • 17 days old (needed 5 days)
• strip-nondeterminism (1.6.1-1 to 1.6.2-1)
  • Migration status for strip-nondeterminism (1.6.1-1 to 1.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for strip-nondeterminism/1.6.2-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/strip-nondeterminism.html
  • 17 days old (needed 5 days)
• trilinos (12.12.1-8 to 12.14.1-1)
  • Migration status for trilinos (12.12.1-8 to 12.14.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating trilinos introduces new bugs: #944486, #944688
  • autopkgtest for deal.ii/9.1.1-6: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trilinos.html
  • 17 days old (needed 5 days)
• acl2 (- to 8.1dfsg-4)
  • Migration status for acl2 (- to 8.1dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on ppc64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acl2.html
  • 18 days old (needed 5 days)
• apertium-anaphora (- to 0.0.2-1)
  • Migration status for apertium-anaphora (- to 0.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kartik
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 18 days old (needed 10 days)
• apertium-lex-tools (0.2.1-1 to 0.2.3-1)
  • Migration status for apertium-lex-tools (0.2.1-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kartik
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-lex-tools.html
  • 18 days old (needed 10 days)
• apertium-recursive (- to 0.0.1-1)
  • Migration status for apertium-recursive (- to 0.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kartik
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 18 days old (needed 10 days)
• cg3 (1.1.7-1 to 1.3.1-1)
  • Migration status for cg3 (1.1.7-1 to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kartik
  • Not built on buildd: arch all binaries uploaded by kartik, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cg3.html
  • 18 days old (needed 10 days)
• cloudpickle (1.2.1-1 to 1.2.1-2)
  • Migration status for cloudpickle (1.2.1-1 to 1.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by diane@ghic.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cloudpickle.html
  • Required age reduced by 3 days because of autopkgtest
  • 18 days old (needed 2 days)
• llvm-toolchain-9 (1:9-1 to 1:9.0.0-3)
  • Migration status for llvm-toolchain-9 (1:9-1 to 1:9.0.0-3): Will attempt migration due to a hint (Any information below is purely informational)
  • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/l/llvm-toolchain-9.html
  • Additional info:
  • Ignoring piuparts issue as requested by elbrus
  • Required age reduced by 3 days because of autopkgtest
  • 18 days old (needed 2 days)
• rust-chrono (0.4.7-1 to 0.4.9-2)
  • Migration status for rust-chrono (0.4.7-1 to 0.4.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-chrono rust-js-sys (not considered)
  • Additional info:
  • Updating rust-chrono fixes old bugs: #943868
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-chrono.html
  • 18 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:
  • Not built on buildd: arch amd64 binaries uploaded by kengyu@lexical.tw
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 18 days old (needed 5 days)
• vdr-plugin-fritzbox (- to 1.5.3-9)
  • Migration status for vdr-plugin-fritzbox (- to 1.5.3-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): vdr-plugin-fritzbox libcommoncpp2 (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-fritzbox.html
  • 18 days old (needed 5 days)
• grilo-plugins (0.3.9-1 to 0.3.10-1)
  • Migration status for grilo-plugins (0.3.9-1 to 0.3.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • grilo-plugins unsatisfiable Build-Depends(-Arch) on arm64: libtracker-sparql-2.0-dev (>= 2.3.0)
  • grilo-plugins unsatisfiable Build-Depends(-Arch) on armel: libtracker-sparql-2.0-dev (>= 2.3.0)
  • grilo-plugins unsatisfiable Build-Depends(-Arch) on armhf: libtracker-sparql-2.0-dev (>= 2.3.0)
  • grilo-plugins unsatisfiable Build-Depends(-Arch) on mips64el: libtracker-sparql-2.0-dev (>= 2.3.0)
  • grilo-plugins unsatisfiable Build-Depends(-Arch) on mipsel: libtracker-sparql-2.0-dev (>= 2.3.0)
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grilo-plugins.html
  • 19 days old (needed 5 days)
• libdata-url-java (- to 1.0.1-1)
  • Migration status for libdata-url-java (- 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 tmancill, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 19 days old (needed 5 days)
• pgbouncer (1.11.0-1 to 1.12.0-1)
  • Migration status for pgbouncer (1.11.0-1 to 1.12.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
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgbouncer.html
  • Required age reduced by 3 days because of autopkgtest
  • 19 days old (needed 2 days)
• ansilove (4.0.3-1 to 4.0.4-1)
  • Migration status for ansilove (4.0.3-1 to 4.0.4-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ansilove.html
  • 20 days old (needed 5 days)
• libmoo-perl (2.003004-2 to 2.003006-1)
  • Migration status for libmoo-perl (2.003004-2 to 2.003006-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libobject-remote-perl/0.004000-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmoo-perl.html
  • 20 days old (needed 5 days)
• otb (- to 7.0.0+dfsg-1)
  • Migration status for otb (- to 7.0.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/otb.html
  • 20 days old (needed 5 days)
  • Impossible Depends: otb -> insighttoolkit4/amd64
  • Impossible Depends: otb -> insighttoolkit4/i386
• python-cutadapt (2.4-2 to 2.6-1)
  • Migration status for python-cutadapt (2.4-2 to 2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by moeller, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by moeller
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cutadapt.html
  • 20 days old (needed 5 days)
• rclone (1.47.0+ex1-7 to 1.49.5-3)
  • Migration status for rclone (1.47.0+ex1-7 to 1.49.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rclone/mipsel has unsatisfiable Built-Using on golang-1.12 1.12.9-2
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rclone.html
  • 20 days old (needed 5 days)
• rust-data-encoding-macro-internal (0.1.7-2 to 0.1.7-3)
  • Migration status for rust-data-encoding-macro-internal (0.1.7-2 to 0.1.7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-data-encoding-macro-internal rust-syn (not considered)
  • Depends: rust-data-encoding-macro-internal rust-syn (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-data-encoding-macro-internal.html
  • Required age reduced by 3 days because of autopkgtest
  • 20 days old (needed 2 days)
• rust-nitrokey (0.3.4-1 to 0.3.4-2)
  • Migration status for rust-nitrokey (0.3.4-1 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nitrokey.html
  • 20 days old (needed 5 days)
• rust-scroll-derive (0.9.5-1 to 0.10.1-2)
  • Migration status for rust-scroll-derive (0.9.5-1 to 0.10.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-scroll-derive rust-proc-macro2 (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-scroll-derive.html
  • Required age reduced by 3 days because of autopkgtest
  • 20 days old (needed 2 days)
• rust-stdweb-derive (0.5.1-1 to 0.5.3-1)
  • Migration status for rust-stdweb-derive (0.5.1-1 to 0.5.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-stdweb-derive rust-proc-macro2 (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-stdweb-derive.html
  • Required age reduced by 3 days because of autopkgtest
  • 20 days old (needed 2 days)
• apertium-separable (0.3.2-1 to 0.3.3-1)
  • Migration status for apertium-separable (0.3.2-1 to 0.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): apertium-separable apertium (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-separable.html
  • 21 days old (needed 10 days)
• dmarc-cat (0.9.2-4 to 0.12.0-1)
  • Migration status for dmarc-cat (0.9.2-4 to 0.12.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by built-using
  • Built-Using: dmarc-cat golang-github-keltia-archive (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dmarc-cat.html
  • 21 days old (needed 5 days)
• julia (1.0.4+dfsg-1 to 1.2.0+dfsg-1)
  • Migration status for julia (1.0.4+dfsg-1 to 1.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating julia introduces new bugs: #928131
  • missing build on arm64
  • missing build on armhf
  • Additional info:
  • Updating julia fixes old bugs: #931693
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/julia.html
  • Required age reduced by 3 days because of autopkgtest
  • 21 days old (needed 2 days)
• python-intbitset (- to 2.3.0-3.1)
  • Migration status for python-intbitset (- to 2.3.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-intbitset introduces new bugs: #917829
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-intbitset.html
  • 21 days old (needed 5 days)
• rust-crossbeam (0.3.2-2 to 0.7.2-2)
  • Migration status for rust-crossbeam (0.3.2-2 to 0.7.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-crossbeam rust-crossbeam-epoch (not considered)
  • Depends: rust-crossbeam rust-crossbeam-epoch (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-crossbeam.html
  • 21 days old (needed 5 days)
• rust-crossbeam-epoch (0.7.1-1 to 0.7.2-2)
  • Migration status for rust-crossbeam-epoch (0.7.1-1 to 0.7.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-crossbeam-epoch rust-memoffset (not considered)
  • Depends: rust-crossbeam-epoch rust-memoffset (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-crossbeam-epoch.html
  • 21 days old (needed 5 days)
• rust-derive-new (0.5.6-1 to 0.5.8-1)
  • Migration status for rust-derive-new (0.5.6-1 to 0.5.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-derive-new rust-proc-macro2 (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-derive-new.html
  • 21 days old (needed 5 days)
• rust-jobserver (0.1.14-1 to 0.1.17-2)
  • Migration status for rust-jobserver (0.1.14-1 to 0.1.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-jobserver rust-getrandom (not considered)
  • Depends: rust-jobserver rust-getrandom (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-jobserver.html
  • 21 days old (needed 5 days)
• rust-log (0.4.6-1 to 0.4.8-2)
  • Migration status for rust-log (0.4.6-1 to 0.4.8-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • librust-log+kv-unstable-sval-dev/amd64 unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+kv-unstable-sval-dev/arm64 unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+kv-unstable-sval-dev/armel unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+kv-unstable-sval-dev/armhf unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+kv-unstable-sval-dev/i386 unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+kv-unstable-sval-dev/mips64el unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+kv-unstable-sval-dev/mipsel unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+kv-unstable-sval-dev/ppc64el unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+kv-unstable-sval-dev/s390x unsatisfiable Depends: librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/amd64 unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/arm64 unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/armel unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/armhf unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/i386 unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/mips64el unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/mipsel unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/ppc64el unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • librust-log+sval-dev/s390x unsatisfiable Depends: librust-sval-0.4-dev (>= 0.4.2-~~)
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-log.html
  • 21 days old (needed 5 days)
• rust-num-derive (0.2.5-1 to 0.3.0-1)
  • Migration status for rust-num-derive (0.2.5-1 to 0.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-num-derive rust-proc-macro2 (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-derive.html
  • 21 days old (needed 5 days)
• rust-uuid (0.7.1-1 to 0.8.1-1)
  • Migration status for rust-uuid (0.7.1-1 to 0.8.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: rust-uuid rust-md5 (not considered)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-uuid.html
  • 21 days old (needed 5 days)
• rust-which (2.0.1-1 to 3.0.0-2)
  • Migration status for rust-which (2.0.1-1 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-which.html
  • 21 days old (needed 5 days)
• rust-winapi (0.3.6-1 to 0.3.8-1)
  • Migration status for rust-winapi (0.3.6-1 to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-tempfile/3.0.8-1: amd64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-winapi.html
  • 21 days old (needed 5 days)
• zeitgeist (1.0.1-1 to 1.0.2-2)
  • Migration status for zeitgeist (1.0.1-1 to 1.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating zeitgeist introduces new bugs: #943994
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zeitgeist.html
  • 21 days old (needed 5 days)
• apertium (3.5.2-1 to 3.6.1-1)
  • Migration status for apertium (3.5.2-1 to 3.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by kartik
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium.html
  • 22 days old (needed 10 days)
• apertium-eval-translator (- to 1.2.1-1)
  • Migration status for apertium-eval-translator (- 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 kartik, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 22 days old (needed 10 days)
• austin (0.7.0-1 to 1.0.0-1)
  • Migration status for austin (0.7.0-1 to 1.0.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/austin.html
  • 22 days old (needed 5 days)
• autofdo (0.18-2 to 0.19-2)
  • Migration status for autofdo (0.18-2 to 0.19-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autofdo.html
  • 22 days old (needed 5 days)
• debsecan (0.4.19+nmu1 to 0.4.20)
  • Migration status for debsecan (0.4.19+nmu1 to 0.4.20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by fw, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debsecan.html
  • 22 days old (needed 10 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 introduces new bugs: #922420
  • autopkgtest for gandi-cli/1.5-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gandi-cli.html
  • 22 days old (needed 5 days)
• golang-github-keltia-archive (0.3.3-1 to 0.7.0-1)
  • Migration status for golang-github-keltia-archive (0.3.3-1 to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for golang-github-keltia-archive/0.7.0-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-keltia-archive.html
  • 22 days old (needed 5 days)
• libssw (1.1-2 to 1.1-3)
  • Migration status for libssw (1.1-2 to 1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by satta@tetrinetsucht.de
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libssw.html
  • Required age reduced by 3 days because of autopkgtest
  • 22 days old (needed 2 days)
• newsboat (2.13-2 to 2.16.1-1)
  • Migration status for newsboat (2.13-2 to 2.16.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
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/newsboat.html
  • 22 days old (needed 10 days)
• openafs (1.8.4~pre1-1 to 1.8.5-1)
  • Migration status for openafs (1.8.4~pre1-1 to 1.8.5-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openafs.html
  • 22 days old (needed 2 days)
• python-cheroot (7.0.0+ds-1 to 8.2.1+ds-2)
  • Migration status for python-cheroot (7.0.0+ds-1 to 8.2.1+ds-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cheroot.html
  • Required age reduced by 3 days because of autopkgtest
  • 22 days old (needed 2 days)
• python-oauthlib (2.1.0-2 to 3.1.0-1)
  • Migration status for python-oauthlib (2.1.0-2 to 3.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Build-Depends(-Arch): python-oauthlib pytest (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-oauthlib.html
  • Required age reduced by 3 days because of autopkgtest
  • 22 days old (needed 2 days)
• r-cran-devtools (2.0.1-1 to 2.2.1-1)
  • Migration status for r-cran-devtools (2.0.1-1 to 2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for r-cran-devtools/2.2.1-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-devtools.html
  • 22 days old (needed 5 days)
• rust-env-proxy (0.3.1-1 to 0.4.0-1)
  • Migration status for rust-env-proxy (0.3.1-1 to 0.4.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-env-proxy rust-url (not considered)
  • Depends: rust-env-proxy rust-url (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-env-proxy.html
  • 22 days old (needed 5 days)
• rust-getopts (0.2.19-1 to 0.2.21-1)
  • Migration status for rust-getopts (0.2.19-1 to 0.2.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • librust-getopts+rustc-dep-of-std-dev/amd64 unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/amd64 unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+rustc-dep-of-std-dev/arm64 unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/arm64 unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+rustc-dep-of-std-dev/armel unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/armel unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+rustc-dep-of-std-dev/armhf unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/armhf unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+rustc-dep-of-std-dev/i386 unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/i386 unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+rustc-dep-of-std-dev/mips64el unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/mips64el unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+rustc-dep-of-std-dev/mipsel unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/mipsel unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+rustc-dep-of-std-dev/ppc64el unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/ppc64el unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+rustc-dep-of-std-dev/s390x unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+rustc-dep-of-std-dev/s390x unsatisfiable Depends: librust-unicode-width-0.1+rustc-dep-of-std-dev (>= 0.1.5-~~)
  • librust-getopts+std-dev/amd64 unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+std-dev/arm64 unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+std-dev/armel unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+std-dev/armhf unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+std-dev/i386 unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+std-dev/mips64el unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+std-dev/mipsel unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+std-dev/ppc64el unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • librust-getopts+std-dev/s390x unsatisfiable Depends: librust-rustc-std-workspace-std-1+default-dev
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-getopts.html
  • 22 days old (needed 5 days)
• rust-proptest (0.8.7-1 to 0.9.4-3)
  • Migration status for rust-proptest (0.8.7-1 to 0.9.4-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proptest.html
  • 22 days old (needed 5 days)
• sphinxcontrib-youtube (- to 1.0-1.1)
  • Migration status for sphinxcontrib-youtube (- to 1.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sphinxcontrib-youtube introduces new bugs: #896348, #943690
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-youtube.html
  • 22 days old (needed 5 days)
• tasksel (3.55 to 3.56)
  • Migration status for tasksel (3.55 to 3.56): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by nicoo, a new source-only upload is needed to allow migration
  • Additional info:
  • Updating tasksel fixes old bugs: #942270
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tasksel.html
  • 22 days old (needed 2 days)
• urwid-satext (0.7.0.a2-1 to 0.8.0~hg143.144bdf877d21-1)
  • Migration status for urwid-satext (0.7.0.a2-1 to 0.8.0~hg143.144bdf877d21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by debacle, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urwid-satext.html
  • 22 days old (needed 5 days)
• python-setuptools (41.2.0-1 to 41.4.0-1)
  • Migration status for python-setuptools (41.2.0-1 to 41.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for pep8/1.7.1-6: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-setuptools.html
  • 23 days old (needed 5 days)
• lava (- to 2019.10-1)
  • Migration status for lava (- to 2019.10-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: lava lava-coordinator (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lava.html
  • Required age reduced by 3 days because of autopkgtest
  • 24 days old (needed 2 days)
• perl6-zef (- to 0.8.0-1)
  • Migration status for perl6-zef (- to 0.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: perl6-zef rakudo (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perl6-zef.html
  • 24 days old (needed 5 days)
• rasdaemon (0.6.0-1.2 to 0.6.4-2)
  • Migration status for rasdaemon (0.6.0-1.2 to 0.6.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ahs3
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rasdaemon.html
  • 25 days old (needed 5 days)
• sopel (- to 6.6.9-1)
  • Migration status for sopel (- to 6.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sopel introduces new bugs: #943405
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sopel.html
  • 25 days old (needed 5 days)
• tracker (2.1.8-2 to 2.3.1-1)
  • Migration status for tracker (2.1.8-2 to 2.3.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tracker.html
  • Required age reduced by 3 days because of autopkgtest
  • 25 days old (needed 2 days)
• tracker-miners (2.1.6-1 to 2.3.1-1)
  • Migration status for tracker-miners (2.1.6-1 to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • tracker-miners unsatisfiable Build-Depends(-Arch) on arm64: libtracker-miner-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on arm64: libtracker-sparql-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on arm64: tracker (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on armel: libtracker-miner-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on armel: libtracker-sparql-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on armel: tracker (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on armhf: libtracker-miner-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on armhf: libtracker-sparql-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on armhf: tracker (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on mips64el: libtracker-miner-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on mips64el: libtracker-sparql-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on mips64el: tracker (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on mipsel: libtracker-miner-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on mipsel: libtracker-sparql-2.0-dev (>= 2.2.0)
  • tracker-miners unsatisfiable Build-Depends(-Arch) on mipsel: tracker (>= 2.2.0)
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tracker-miners.html
  • 25 days old (needed 5 days)
• acpica-unix (20190509-1 to 20190703-1)
  • Migration status for acpica-unix (20190509-1 to 20190703-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ahs3
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acpica-unix.html
  • 26 days old (needed 5 days)
• rust-bindgen (0.47.0-1 to 0.51.1-2)
  • Migration status for rust-bindgen (0.47.0-1 to 0.51.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-bindgen/0.51.1-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bindgen.html
  • 26 days old (needed 5 days)
• rust-nettle-sys (- to 2.0.4-1)
  • Migration status for rust-nettle-sys (- to 2.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-nettle-sys/2.0.4-1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nettle-sys.html
  • 26 days old (needed 5 days)
• shellia (5.4.1 to 5.5)
  • Migration status for shellia (5.4.1 to 5.5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shellia.html
  • 26 days old (needed 5 days)
• gitlab-ci-multi-runner (12.3.0+dfsg-1 to 12.4.0+dfsg-1)
  • Migration status for gitlab-ci-multi-runner (12.3.0+dfsg-1 to 12.4.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by built-using
  • Built-Using: gitlab-ci-multi-runner docker.io (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
  • 27 days old (needed 5 days)
• nova (2:19.0.2-4 to 2:20.0.0-2)
  • Migration status for nova (2:19.0.2-4 to 2:20.0.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nova.html
  • 27 days old (needed 5 days)
• nss (2:3.45-1 to 2:3.47-1)
  • Migration status for nss (2:3.45-1 to 2:3.47-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nss.html
  • 27 days old (needed 5 days)
• python-pykka (1.2.1-4 to 2.0.0-3)
  • Migration status for python-pykka (1.2.1-4 to 2.0.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pykka.html
  • 27 days old (needed 5 days)
  • Impossible Build-Depends(-Arch): python-pykka -> python-eventlet/amd64
• browserpass (2.0.22-2 to 3.4.1-1)
  • Migration status for browserpass (2.0.22-2 to 3.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating browserpass introduces new bugs: #944657
  • webext-browserpass/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • webext-browserpass/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/browserpass.html
  • 28 days old (needed 5 days)
• gcr (3.33.4-2 to 3.34.0-1)
  • Migration status for gcr (3.33.4-2 to 3.34.0-1): Waiting for test results, 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/gcr.html
  • Additional info:
  • 28 days old (needed 5 days)
• klavaro (3.03-2 to 3.09-2)
  • Migration status for klavaro (3.03-2 to 3.09-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bartm
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/klavaro.html
  • 28 days old (needed 5 days)
• python-cbor (1.0.0-1 to 1.0.0-1.1)
  • Migration status for python-cbor (1.0.0-1 to 1.0.0-1.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cbor.html
  • 28 days old (needed 5 days)
• python-scales (- to 1.0.9-2.1)
  • Migration status for python-scales (- to 1.0.9-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-scales introduces new bugs: #942352
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-scales.html
  • 28 days old (needed 5 days)
• tslib (1.20-1 to 1.21-1)
  • Migration status for tslib (1.20-1 to 1.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by martink@posteo.de
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tslib.html
  • 28 days old (needed 10 days)
• yapsy (1.12.0-1 to 1.12.0-1.1)
  • Migration status for yapsy (1.12.0-1 to 1.12.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for biomaj3/3.1.14-1: amd64: Regression ♻
  • autopkgtest for yapsy/1.12.0-1.1: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yapsy.html
  • 28 days old (needed 5 days)
• libsoxr (0.1.3-1 to 0.1.3-2)
  • Migration status for libsoxr (0.1.3-1 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libsoxr introduces new bugs: #944017
  • autopkgtest for libsoxr/0.1.3-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsoxr.html
  • 29 days old (needed 5 days)
• pytest (3.10.1-2 to 4.6.6-1)
  • Migration status for pytest (3.10.1-2 to 4.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for dask/1.0.0+dfsg-2: amd64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest.html
  • 29 days old (needed 5 days)
• celery-batches (- to 0.2-1)
  • Migration status for celery-batches (- to 0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating celery-batches introduces new bugs: #942647
  • Not built on buildd: arch amd64 binaries uploaded by debacle
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 30 days old (needed 5 days)
• golang-github-openshift-imagebuilder (- to 1.1.0-2)
  • Migration status for golang-github-openshift-imagebuilder (- to 1.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by built-using
  • Built-Using: golang-github-openshift-imagebuilder docker.io (not considered)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 30 days old (needed 2 days)
• openjdk-13 (13.0.1+9-1 to 13.0.1+9-2)
  • Migration status for openjdk-13 (13.0.1+9-1 to 13.0.1+9-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-13.html
  • 30 days old (needed 5 days)
• perl6-readline (- to 0.1.5-1)
  • Migration status for perl6-readline (- to 0.1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: perl6-readline rakudo (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perl6-readline.html
  • 31 days old (needed 5 days)
• php-horde-javascriptminify-jsmin (1.0.2-5 to 1.0.2-6)
  • Migration status for php-horde-javascriptminify-jsmin (1.0.2-5 to 1.0.2-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 31 days old (needed 5 days)
• php-horde-mongo (- to 1.1.0-4)
  • Migration status for php-horde-mongo (- to 1.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-horde-mongo introduces new bugs: #820091
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mongo.html
  • 31 days old (needed 5 days)
• php-horde-text-filter-jsmin (1.0.2-5 to 1.0.2-6)
  • Migration status for php-horde-text-filter-jsmin (1.0.2-5 to 1.0.2-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 31 days old (needed 5 days)
• python-fabio (0.9.0+dfsg-1 to 0.9.0+dfsg-2)
  • Migration status for python-fabio (0.9.0+dfsg-1 to 0.9.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
  • Updating python-fabio introduces new bugs: #942887
  • autopkgtest for python-fabio/0.9.0+dfsg-2: amd64: Regression ♻
  • Additional info:
  • Updating python-fabio fixes old bugs: #937745
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fabio.html
  • 31 days old (needed 5 days)
• rust-futures (0.1.28-2 to 0.1.29-1)
  • Migration status for rust-futures (0.1.28-2 to 0.1.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-tokio-threadpool/0.1.16-1: amd64: Regression ♻
  • missing build on arm64
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-futures.html
  • 31 days old (needed 5 days)
• vagrant-librarian-puppet (- to 0.9.2-1)
  • Migration status for vagrant-librarian-puppet (- 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 georg, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 31 days old (needed 2 days)
• cadvisor (- to 0.34.0+dfsg-1)
  • Migration status for cadvisor (- to 0.34.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by built-using
  • Built-Using: cadvisor rkt (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cadvisor.html
  • Required age reduced by 3 days because of autopkgtest
  • 32 days old (needed 2 days)
• cross-toolchain-base-mipsen (- to 8)
  • Migration status for cross-toolchain-base-mipsen (- to 8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cross-toolchain-base-mipsen introduces new bugs: #942565
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cross-toolchain-base-mipsen.html
  • 32 days old (needed 5 days)
• kexec-tools (1:2.0.18-1 to 1:2.0.20-1)
  • Migration status for kexec-tools (1:2.0.18-1 to 1:2.0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kexec-tools introduces new bugs: #942617
  • Not built on buildd: arch amd64 binaries uploaded by khalid
  • missing build on i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kexec-tools.html
  • 32 days old (needed 5 days)
• openjdk-8 (- to 8u232-b09-1)
  • Migration status for openjdk-8 (- to 8u232-b09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openjdk-8 introduces new bugs: #929650
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-8.html
  • 32 days old (needed 5 days)
• rakudo (- to 2019.07.1-8)
  • Migration status for rakudo (- to 2019.07.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rakudo unsatisfiable Build-Depends(-Arch) on mipsel: nqp (>= 2019.07)
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rakudo.html
  • 32 days old (needed 5 days)
• rkt (- to 1.30.0+dfsg1-8)
  • Migration status for rkt (- to 1.30.0+dfsg1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rkt introduces new bugs: #929781
  • rkt/arm64 has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • rkt/ppc64el has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • missing build on arm64
  • missing build on ppc64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rkt.html
  • 32 days old (needed 5 days)
• bro (- to 2.6.4+ds1-2)
  • Migration status for bro (- to 2.6.4+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating bro introduces new bugs: #939078
  • bro unsatisfiable Build-Depends(-Arch) on armel: libbroker-dev
  • bro unsatisfiable Build-Depends(-Arch) on armhf: libbroker-dev
  • bro unsatisfiable Build-Depends(-Arch) on s390x: libbroker-dev
  • missing build on armel
  • missing build on armhf
  • missing build on s390x
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bro.html
  • 33 days old (needed 5 days)
• gcc-defaults-mipsen (- to 1.186.1)
  • Migration status for gcc-defaults-mipsen (- to 1.186.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: gcc-defaults-mipsen gcc-9-cross-mipsen (not considered)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-defaults-mipsen.html
  • 33 days old (needed 5 days)
• openjdk-14 (- to 14~19-1)
  • Migration status for openjdk-14 (- to 14~19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openjdk-14 introduces new bugs: #942783
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • autopkgtest for openjdk-14/14~19-1: amd64: Ignored failure
  • 33 days old (needed 5 days)
• r-cran-caic4 (- to 0.8-1)
  • Migration status for r-cran-caic4 (- to 0.8-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• r-cran-d3network (- to 0.5.2.1-1)
  • Migration status for r-cran-d3network (- to 0.5.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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• r-cran-furrr (- to 0.1.0-1)
  • Migration status for r-cran-furrr (- 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 tille, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• r-cran-ggm (- to 2.3-1)
  • Migration status for r-cran-ggm (- to 2.3-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• r-cran-gparotation (- to 2014.11-1-1)
  • Migration status for r-cran-gparotation (- to 2014.11-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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• r-cran-lisreltor (- to 0.1.4-1)
  • Migration status for r-cran-lisreltor (- to 0.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
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• r-cran-nfactors (- to 2.3.3.1-1)
  • Migration status for r-cran-nfactors (- to 2.3.3.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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 7 days)
• r-cran-propclust (- to 1.4-6-1)
  • Migration status for r-cran-propclust (- to 1.4-6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Build-Depends(-Arch): r-cran-propclust r-cran-dynamictreecut (not considered)
  • Depends: r-cran-propclust r-cran-dynamictreecut (not considered)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• r-cran-qgraph (- to 1.6.3-1)
  • Migration status for r-cran-qgraph (- to 1.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• rust-web-sys (- to 0.3.28-1.1)
  • Migration status for rust-web-sys (- to 0.3.28-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-web-sys introduces new bugs: #942487
  • uninstallable on arch amd64, autopkgtest delayed there
  • Additional info:
  • librust-web-sys+env-logger-dev/amd64 unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • librust-web-sys+env-logger-dev/arm64 unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • librust-web-sys+env-logger-dev/armel unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • librust-web-sys+env-logger-dev/armhf unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • librust-web-sys+env-logger-dev/i386 unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • librust-web-sys+env-logger-dev/mips64el unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • librust-web-sys+env-logger-dev/mipsel unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • librust-web-sys+env-logger-dev/ppc64el unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • librust-web-sys+env-logger-dev/s390x unsatisfiable Depends: librust-env-logger-0.7+default-dev
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 33 days old (needed 5 days)
• virtualbox (- to 6.0.14-dfsg-1)
  • Migration status for virtualbox (- to 6.0.14-dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating virtualbox introduces new bugs: #794466, #943569
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 33 days old (needed 5 days)
• virtualbox-ext-pack (- to 6.0.14-1)
  • Migration status for virtualbox-ext-pack (- to 6.0.14-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Invalidated by dependency
  • Depends: virtualbox-ext-pack virtualbox (not considered)
  • Additional info:
  • virtualbox-ext-pack/i386 unsatisfiable Depends: virtualbox (>= 6.0.14-dfsg-0~) | virtualbox-6.0
  • virtualbox-ext-pack/i386 unsatisfiable Depends: virtualbox (<< 6.0.14-dfsg-z) | virtualbox-6.0
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 33 days old (needed 5 days)
• libpillowfight (0.2.4-2 to 0.3.0-1)
  • Migration status for libpillowfight (0.2.4-2 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by moeller
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpillowfight.html
  • 34 days old (needed 5 days)
• oscar (- to 1.1.0-testing-3-1)
  • Migration status for oscar (- to 1.1.0-testing-3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by sergiodj@sergiodj.net
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 34 days old (needed 5 days)
• python-exif (2.2.0-2 to 2.2.0-4)
  • Migration status for python-exif (2.2.0-2 to 2.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by takaki, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-exif.html
  • 34 days old (needed 5 days)
• python-packaging (19.1-2 to 19.2-1)
  • Migration status for python-packaging (19.1-2 to 19.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-packaging.html
  • 34 days old (needed 5 days)
• kaptive (- to 0.6.0-1)
  • Migration status for kaptive (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • I