Generated: 2020.05.28 14:06:04 +0000

• -approx (5.10-2 to -)
  • Migration status for -approx (5.10-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -gtksourceview2 (2.10.5-3 to -)
  • Migration status for -gtksourceview2 (2.10.5-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
• -lablgtk2 (2.18.8+dfsg-1 to -)
  • Migration status for -lablgtk2 (2.18.8+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
• -libasr (1.0.2-2 to -)
  • Migration status for -libasr (1.0.2-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Package not in unstable, will try to remove
• -llvm-toolchain-6.0 (1:6.0.1-14.1 to -)
  • Migration status for -llvm-toolchain-6.0 (1:6.0.1-14.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Package not in unstable, will try to remove
• -node-hoek (8.5.0+~4.2.1+~3.3.1-1 to -)
  • Migration status for -node-hoek (8.5.0+~4.2.1+~3.3.1-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -ocamlnet (4.1.6-1 to -)
  • Migration status for -ocamlnet (4.1.6-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -openstack-cluster-installer (28 to -)
  • Migration status for -openstack-cluster-installer (28 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -openstack-meta-packages (0.28 to -)
  • Migration status for -openstack-meta-packages (0.28 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Removal request by auto-removals
  • Package is broken, will try to remove
• -php7.3 (7.3.15-3 to -)
  • Migration status for -php7.3 (7.3.15-3 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Package not in unstable, will try to remove
• -xserver-xorg-input-void (1:1.4.1-1 to -)
  • Migration status for -xserver-xorg-input-void (1:1.4.1-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Package not in unstable, will try to remove
• acepack/amd64 (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/amd64 (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/amd64 r-base
• acepack/arm64 (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/arm64 (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/arm64 r-base
• acepack/armel (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/armel (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/armel r-base
• acepack/armhf (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/armhf (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/armhf r-base
• acepack/i386 (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/i386 (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/i386 r-base
• acepack/mips64el (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/mips64el (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/mips64el r-base
• acepack/mipsel (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/mipsel (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/mipsel r-base
• acepack/ppc64el (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/ppc64el (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/ppc64el r-base
• acepack/s390x (1.4.1-2 to 1.4.1-2)
  • Migration status for acepack/s390x (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: acepack/s390x r-base
• apache-log4j1.2_pu (1.2.17-9 to 1.2.17-8+deb10u1)
  • Migration status for apache-log4j1.2_pu (1.2.17-9 to 1.2.17-8+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: apache-log4j1.2 is newer in the target suite (1.2.17-9 1.2.17-8+deb10u1)
• approx/amd64 (5.10-2 to 5.10-2)
  • Migration status for approx/amd64 (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• approx/arm64 (5.10-2 to 5.10-2)
  • Migration status for approx/arm64 (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• approx/armel (5.10-2 to 5.10-2)
  • Migration status for approx/armel (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• approx/armhf (5.10-2 to 5.10-2)
  • Migration status for approx/armhf (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• approx/i386 (5.10-2 to 5.10-2)
  • Migration status for approx/i386 (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• approx/mips64el (5.10-2 to 5.10-2)
  • Migration status for approx/mips64el (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• approx/mipsel (5.10-2 to 5.10-2)
  • Migration status for approx/mipsel (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• approx/ppc64el (5.10-2 to 5.10-2)
  • Migration status for approx/ppc64el (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• approx/s390x (5.10-2 to 5.10-2)
  • Migration status for approx/s390x (5.10-2 to 5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• apt_pu (2.1.5 to 1.8.2.1)
  • Migration status for apt_pu (2.1.5 to 1.8.2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: apt is newer in the target suite (2.1.5 1.8.2.1)
• bind9_pu (1:9.16.2-3 to 1:9.11.5.P4+dfsg-5.1+deb10u1)
  • Migration status for bind9_pu (1:9.16.2-3 to 1:9.11.5.P4+dfsg-5.1+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: bind9 is newer in the target suite (1:9.16.2-3 1:9.11.5.P4+dfsg-5.1+deb10u1)
• borgbackup_pu (1.1.11-5 to 1.1.9-2+deb10u1)
  • Migration status for borgbackup_pu (1.1.11-5 to 1.1.9-2+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: borgbackup is newer in the target suite (1.1.11-5 1.1.9-2+deb10u1)
• btfs/amd64 (2.20-1 to 2.20-1)
  • Migration status for btfs/amd64 (2.20-1 to 2.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: btfs/amd64 libtorrent-rasterbar (not considered)
  • Invalidated by dependency
• btfs/arm64 (2.20-1 to 2.20-1)
  • Migration status for btfs/arm64 (2.20-1 to 2.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: btfs/arm64 libtorrent-rasterbar (not considered)
  • Invalidated by dependency
• btfs/armhf (2.20-1 to 2.20-1)
  • Migration status for btfs/armhf (2.20-1 to 2.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: btfs/armhf libtorrent-rasterbar (not considered)
  • Invalidated by dependency
• btfs/i386 (2.20-1 to 2.20-1)
  • Migration status for btfs/i386 (2.20-1 to 2.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: btfs/i386 libtorrent-rasterbar (not considered)
  • Invalidated by dependency
• btfs/mips64el (2.20-1 to 2.20-1)
  • Migration status for btfs/mips64el (2.20-1 to 2.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: btfs/mips64el libtorrent-rasterbar (not considered)
  • Invalidated by dependency
• btfs/ppc64el (2.20-1 to 2.20-1)
  • Migration status for btfs/ppc64el (2.20-1 to 2.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: btfs/ppc64el libtorrent-rasterbar (not considered)
  • Invalidated by dependency
• btfs/s390x (2.20-1 to 2.20-1)
  • Migration status for btfs/s390x (2.20-1 to 2.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: btfs/s390x libtorrent-rasterbar (not considered)
  • Invalidated by dependency
• bundler_pu (2.1.4-1 to 1.17.3-3+deb10u1)
  • Migration status for bundler_pu (2.1.4-1 to 1.17.3-3+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: bundler is newer in the target suite (2.1.4-1 1.17.3-3+deb10u1)
• cairodevice/amd64 (2.28-1 to 2.28-1)
  • Migration status for cairodevice/amd64 (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/amd64 r-base
• cairodevice/arm64 (2.28-1 to 2.28-1)
  • Migration status for cairodevice/arm64 (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/arm64 r-base
• cairodevice/armel (2.28-1 to 2.28-1)
  • Migration status for cairodevice/armel (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/armel r-base
• cairodevice/armhf (2.28-1 to 2.28-1)
  • Migration status for cairodevice/armhf (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/armhf r-base
• cairodevice/i386 (2.28-1 to 2.28-1)
  • Migration status for cairodevice/i386 (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/i386 r-base
• cairodevice/mips64el (2.28-1 to 2.28-1)
  • Migration status for cairodevice/mips64el (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/mips64el r-base
• cairodevice/mipsel (2.28-1 to 2.28-1)
  • Migration status for cairodevice/mipsel (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/mipsel r-base
• cairodevice/ppc64el (2.28-1 to 2.28-1)
  • Migration status for cairodevice/ppc64el (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/ppc64el r-base
• cairodevice/s390x (2.28-1 to 2.28-1)
  • Migration status for cairodevice/s390x (2.28-1 to 2.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: cairodevice/s390x r-base
• chron/amd64 (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/amd64 (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/amd64 r-base
• chron/arm64 (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/arm64 (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/arm64 r-base
• chron/armel (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/armel (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/armel r-base
• chron/armhf (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/armhf (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/armhf r-base
• chron/i386 (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/i386 (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/i386 r-base
• chron/mips64el (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/mips64el (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/mips64el r-base
• chron/mipsel (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/mipsel (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/mipsel r-base
• chron/ppc64el (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/ppc64el (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/ppc64el r-base
• chron/s390x (2.3-55-1 to 2.3-55-1)
  • Migration status for chron/s390x (2.3-55-1 to 2.3-55-1): Will attempt migration (Any information below is purely informational)
  • Depends: chron/s390x r-base
• cluster/amd64 (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/amd64 (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/amd64 r-base
• cluster/arm64 (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/arm64 (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/arm64 r-base
• cluster/armel (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/armel (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/armel r-base
• cluster/armhf (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/armhf (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/armhf r-base
• cluster/i386 (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/i386 (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/i386 r-base
• cluster/mips64el (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/mips64el (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/mips64el r-base
• cluster/mipsel (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/mipsel (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/mipsel r-base
• cluster/ppc64el (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/ppc64el (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/ppc64el r-base
• cluster/s390x (2.1.0-2 to 2.1.0-2)
  • Migration status for cluster/s390x (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: cluster/s390x r-base
• confget_pu (2.3.4-1 to 2.2.0-4+deb10u1)
  • Migration status for confget_pu (2.3.4-1 to 2.2.0-4+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: confget is newer in the target suite (2.3.4-1 2.2.0-4+deb10u1)
• dart/amd64 (6.9.2-2 to 6.9.2-2)
  • Migration status for dart/amd64 (6.9.2-2 to 6.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dart/amd64 openscenegraph (not considered)
  • Invalidated by dependency
• dart/arm64 (6.9.2-2 to 6.9.2-2)
  • Migration status for dart/arm64 (6.9.2-2 to 6.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dart/arm64 openscenegraph (not considered)
  • Invalidated by dependency
• dart/armel (6.9.2-2 to 6.9.2-2)
  • Migration status for dart/armel (6.9.2-2 to 6.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dart/armel openscenegraph (not considered)
  • Invalidated by dependency
• dart/armhf (6.9.2-2 to 6.9.2-2)
  • Migration status for dart/armhf (6.9.2-2 to 6.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dart/armhf openscenegraph (not considered)
  • Invalidated by dependency
• dart/i386 (6.9.2-2 to 6.9.2-2)
  • Migration status for dart/i386 (6.9.2-2 to 6.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dart/i386 openscenegraph (not considered)
  • Invalidated by dependency
• dart/mips64el (6.9.2-2 to 6.9.2-2)
  • Migration status for dart/mips64el (6.9.2-2 to 6.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dart/mips64el openscenegraph (not considered)
  • Invalidated by dependency
• dart/mipsel (6.9.2-2 to 6.9.2-2)
  • Migration status for dart/mipsel (6.9.2-2 to 6.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dart/mipsel openscenegraph (not considered)
  • Invalidated by dependency
• dart/ppc64el (6.9.2-2 to 6.9.2-2)
  • Migration status for dart/ppc64el (6.9.2-2 to 6.9.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dart/ppc64el openscenegraph (not considered)
  • Invalidated by dependency
• date/amd64 (1.2.39-1 to 1.2.39-1)
  • Migration status for date/amd64 (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/amd64 r-base
• date/arm64 (1.2.39-1 to 1.2.39-1)
  • Migration status for date/arm64 (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/arm64 r-base
• date/armel (1.2.39-1 to 1.2.39-1)
  • Migration status for date/armel (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/armel r-base
• date/armhf (1.2.39-1 to 1.2.39-1)
  • Migration status for date/armhf (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/armhf r-base
• date/i386 (1.2.39-1 to 1.2.39-1)
  • Migration status for date/i386 (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/i386 r-base
• date/mips64el (1.2.39-1 to 1.2.39-1)
  • Migration status for date/mips64el (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/mips64el r-base
• date/mipsel (1.2.39-1 to 1.2.39-1)
  • Migration status for date/mipsel (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/mipsel r-base
• date/ppc64el (1.2.39-1 to 1.2.39-1)
  • Migration status for date/ppc64el (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/ppc64el r-base
• date/s390x (1.2.39-1 to 1.2.39-1)
  • Migration status for date/s390x (1.2.39-1 to 1.2.39-1): Will attempt migration (Any information below is purely informational)
  • Depends: date/s390x r-base
• digikam/amd64 (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3)
  • Migration status for digikam/amd64 (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: digikam/amd64 kio (not considered)
  • Invalidated by dependency
  • Depends: digikam/amd64 akonadi-contacts
  • Depends: digikam/amd64 kcalcore
• digikam/arm64 (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3)
  • Migration status for digikam/arm64 (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: digikam/arm64 kio (not considered)
  • Invalidated by dependency
  • Depends: digikam/arm64 akonadi-contacts
  • Depends: digikam/arm64 kcalcore
• digikam/armel (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3)
  • Migration status for digikam/armel (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: digikam/armel kio (not considered)
  • Invalidated by dependency
  • Depends: digikam/armel akonadi-contacts
  • Depends: digikam/armel kcalcore
• digikam/armhf (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3)
  • Migration status for digikam/armhf (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: digikam/armhf kio (not considered)
  • Invalidated by dependency
  • Depends: digikam/armhf akonadi-contacts
  • Depends: digikam/armhf kcalcore
• digikam/i386 (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3)
  • Migration status for digikam/i386 (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: digikam/i386 kio (not considered)
  • Invalidated by dependency
  • Depends: digikam/i386 akonadi-contacts
  • Depends: digikam/i386 kcalcore
• digikam/ppc64el (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3)
  • Migration status for digikam/ppc64el (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: digikam/ppc64el kio (not considered)
  • Invalidated by dependency
  • Depends: digikam/ppc64el akonadi-contacts
  • Depends: digikam/ppc64el kcalcore
• digikam/s390x (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3)
  • Migration status for digikam/s390x (4:6.4.0+dfsg-3 to 4:6.4.0+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: digikam/s390x kio (not considered)
  • Invalidated by dependency
  • Depends: digikam/s390x akonadi-contacts
  • Depends: digikam/s390x kcalcore
• dovecot_pu (- to 1:2.3.4.1-5+deb10u2)
  • Migration status for dovecot_pu (- to 1:2.3.4.1-5+deb10u2): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
  • NEEDS APPROVAL BY RM
• dpdk_pu (19.11.2-1 to 18.11.6-1~deb10u2)
  • Migration status for dpdk_pu (19.11.2-1 to 18.11.6-1~deb10u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: dpdk is newer in the target suite (19.11.2-1 18.11.6-1~deb10u2)
• exim4_pu (4.93-16 to 4.92-8+deb10u4)
  • Migration status for exim4_pu (4.93-16 to 4.92-8+deb10u4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: exim4 is newer in the target suite (4.93-16 4.92-8+deb10u4)
• fasianoptions/amd64 (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/amd64 (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/amd64 r-base
• fasianoptions/arm64 (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/arm64 (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/arm64 r-base
• fasianoptions/armel (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/armel (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/armel r-base
• fasianoptions/armhf (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/armhf (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/armhf r-base
• fasianoptions/i386 (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/i386 (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/i386 r-base
• fasianoptions/mips64el (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/mips64el (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/mips64el r-base
• fasianoptions/mipsel (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/mipsel (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/mipsel r-base
• fasianoptions/ppc64el (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/ppc64el (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/ppc64el r-base
• fasianoptions/s390x (3042.82-1 to 3042.82-1)
  • Migration status for fasianoptions/s390x (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fasianoptions/s390x r-base
• fassets/amd64 (3042.84-1 to 3042.84-1)
  • Migration status for fassets/amd64 (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/amd64 r-base
• fassets/arm64 (3042.84-1 to 3042.84-1)
  • Migration status for fassets/arm64 (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/arm64 r-base
• fassets/armel (3042.84-1 to 3042.84-1)
  • Migration status for fassets/armel (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/armel r-base
• fassets/armhf (3042.84-1 to 3042.84-1)
  • Migration status for fassets/armhf (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/armhf r-base
• fassets/i386 (3042.84-1 to 3042.84-1)
  • Migration status for fassets/i386 (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/i386 r-base
• fassets/mips64el (3042.84-1 to 3042.84-1)
  • Migration status for fassets/mips64el (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/mips64el r-base
• fassets/mipsel (3042.84-1 to 3042.84-1)
  • Migration status for fassets/mipsel (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/mipsel r-base
• fassets/ppc64el (3042.84-1 to 3042.84-1)
  • Migration status for fassets/ppc64el (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/ppc64el r-base
• fassets/s390x (3042.84-1 to 3042.84-1)
  • Migration status for fassets/s390x (3042.84-1 to 3042.84-1): Will attempt migration (Any information below is purely informational)
  • Depends: fassets/s390x r-base
• fastnetmon/amd64 (1.1.4-1 to 1.1.4-1)
  • Migration status for fastnetmon/amd64 (1.1.4-1 to 1.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: fastnetmon/amd64 ndpi (not considered)
  • Invalidated by dependency
• fastnetmon/armel (1.1.4-1 to 1.1.4-1)
  • Migration status for fastnetmon/armel (1.1.4-1 to 1.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: fastnetmon/armel ndpi (not considered)
  • Invalidated by dependency
• fastnetmon/mips64el (1.1.4-1 to 1.1.4-1)
  • Migration status for fastnetmon/mips64el (1.1.4-1 to 1.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: fastnetmon/mips64el ndpi (not considered)
  • Invalidated by dependency
• fastnetmon/mipsel (1.1.4-1 to 1.1.4-1)
  • Migration status for fastnetmon/mipsel (1.1.4-1 to 1.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: fastnetmon/mipsel ndpi (not considered)
  • Invalidated by dependency
• fbasics/amd64 (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/amd64 (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/amd64 r-base
• fbasics/arm64 (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/arm64 (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/arm64 r-base
• fbasics/armel (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/armel (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/armel r-base
• fbasics/armhf (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/armhf (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/armhf r-base
• fbasics/i386 (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/i386 (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/i386 r-base
• fbasics/mips64el (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/mips64el (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/mips64el r-base
• fbasics/mipsel (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/mipsel (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/mipsel r-base
• fbasics/ppc64el (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/ppc64el (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/ppc64el r-base
• fbasics/s390x (3042.89.1-1 to 3042.89.1-1)
  • Migration status for fbasics/s390x (3042.89.1-1 to 3042.89.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fbasics/s390x r-base
• fcopulae/amd64 (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/amd64 (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/amd64 r-base
• fcopulae/arm64 (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/arm64 (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/arm64 r-base
• fcopulae/armel (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/armel (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/armel r-base
• fcopulae/armhf (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/armhf (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/armhf r-base
• fcopulae/i386 (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/i386 (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/i386 r-base
• fcopulae/mips64el (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/mips64el (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/mips64el r-base
• fcopulae/mipsel (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/mipsel (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/mipsel r-base
• fcopulae/ppc64el (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/ppc64el (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/ppc64el r-base
• fcopulae/s390x (3042.82.1-1 to 3042.82.1-1)
  • Migration status for fcopulae/s390x (3042.82.1-1 to 3042.82.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fcopulae/s390x r-base
• fgarch/amd64 (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/amd64 (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/amd64 r-base
• fgarch/arm64 (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/arm64 (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/arm64 r-base
• fgarch/armel (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/armel (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/armel r-base
• fgarch/armhf (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/armhf (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/armhf r-base
• fgarch/i386 (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/i386 (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/i386 r-base
• fgarch/mips64el (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/mips64el (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/mips64el r-base
• fgarch/mipsel (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/mipsel (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/mipsel r-base
• fgarch/ppc64el (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/ppc64el (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/ppc64el r-base
• fgarch/s390x (3042.83.2-1 to 3042.83.2-1)
  • Migration status for fgarch/s390x (3042.83.2-1 to 3042.83.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: fgarch/s390x r-base
• firefox-esr_pu (68.8.0esr-1 to 68.8.0esr-1~deb10u1)
  • Migration status for firefox-esr_pu (68.8.0esr-1 to 68.8.0esr-1~deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: firefox-esr is newer in the target suite (68.8.0esr-1 68.8.0esr-1~deb10u1)
• fnonlinear/amd64 (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/amd64 (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/amd64 r-base
• fnonlinear/arm64 (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/arm64 (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/arm64 r-base
• fnonlinear/armel (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/armel (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/armel r-base
• fnonlinear/armhf (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/armhf (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/armhf r-base
• fnonlinear/i386 (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/i386 (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/i386 r-base
• fnonlinear/mips64el (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/mips64el (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/mips64el r-base
• fnonlinear/mipsel (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/mipsel (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/mipsel r-base
• fnonlinear/ppc64el (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/ppc64el (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/ppc64el r-base
• fnonlinear/s390x (3042.79-1 to 3042.79-1)
  • Migration status for fnonlinear/s390x (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: fnonlinear/s390x r-base
• foptions/amd64 (3042.86-1 to 3042.86-1)
  • Migration status for foptions/amd64 (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/amd64 r-base
• foptions/arm64 (3042.86-1 to 3042.86-1)
  • Migration status for foptions/arm64 (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/arm64 r-base
• foptions/armel (3042.86-1 to 3042.86-1)
  • Migration status for foptions/armel (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/armel r-base
• foptions/armhf (3042.86-1 to 3042.86-1)
  • Migration status for foptions/armhf (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/armhf r-base
• foptions/i386 (3042.86-1 to 3042.86-1)
  • Migration status for foptions/i386 (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/i386 r-base
• foptions/mips64el (3042.86-1 to 3042.86-1)
  • Migration status for foptions/mips64el (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/mips64el r-base
• foptions/mipsel (3042.86-1 to 3042.86-1)
  • Migration status for foptions/mipsel (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/mipsel r-base
• foptions/ppc64el (3042.86-1 to 3042.86-1)
  • Migration status for foptions/ppc64el (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/ppc64el r-base
• foptions/s390x (3042.86-1 to 3042.86-1)
  • Migration status for foptions/s390x (3042.86-1 to 3042.86-1): Will attempt migration (Any information below is purely informational)
  • Depends: foptions/s390x r-base
• fportfolio/amd64 (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/amd64 (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/amd64 r-base
• fportfolio/arm64 (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/arm64 (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/arm64 r-base
• fportfolio/armel (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/armel (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/armel r-base
• fportfolio/armhf (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/armhf (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/armhf r-base
• fportfolio/i386 (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/i386 (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/i386 r-base
• fportfolio/mips64el (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/mips64el (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/mips64el r-base
• fportfolio/mipsel (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/mipsel (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/mipsel r-base
• fportfolio/ppc64el (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/ppc64el (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/ppc64el r-base
• fportfolio/s390x (3042.83.1-1 to 3042.83.1-1)
  • Migration status for fportfolio/s390x (3042.83.1-1 to 3042.83.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: fportfolio/s390x r-base
• fregression/amd64 (3042.82-1 to 3042.82-1)
  • Migration status for fregression/amd64 (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/amd64 r-base
• fregression/arm64 (3042.82-1 to 3042.82-1)
  • Migration status for fregression/arm64 (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/arm64 r-base
• fregression/armel (3042.82-1 to 3042.82-1)
  • Migration status for fregression/armel (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/armel r-base
• fregression/armhf (3042.82-1 to 3042.82-1)
  • Migration status for fregression/armhf (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/armhf r-base
• fregression/i386 (3042.82-1 to 3042.82-1)
  • Migration status for fregression/i386 (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/i386 r-base
• fregression/mips64el (3042.82-1 to 3042.82-1)
  • Migration status for fregression/mips64el (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/mips64el r-base
• fregression/mipsel (3042.82-1 to 3042.82-1)
  • Migration status for fregression/mipsel (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/mipsel r-base
• fregression/ppc64el (3042.82-1 to 3042.82-1)
  • Migration status for fregression/ppc64el (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/ppc64el r-base
• fregression/s390x (3042.82-1 to 3042.82-1)
  • Migration status for fregression/s390x (3042.82-1 to 3042.82-1): Will attempt migration (Any information below is purely informational)
  • Depends: fregression/s390x r-base
• funitroots/amd64 (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/amd64 (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/amd64 r-base
• funitroots/arm64 (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/arm64 (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/arm64 r-base
• funitroots/armel (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/armel (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/armel r-base
• funitroots/armhf (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/armhf (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/armhf r-base
• funitroots/i386 (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/i386 (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/i386 r-base
• funitroots/mips64el (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/mips64el (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/mips64el r-base
• funitroots/mipsel (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/mipsel (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/mipsel r-base
• funitroots/ppc64el (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/ppc64el (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/ppc64el r-base
• funitroots/s390x (3042.79-1 to 3042.79-1)
  • Migration status for funitroots/s390x (3042.79-1 to 3042.79-1): Will attempt migration (Any information below is purely informational)
  • Depends: funitroots/s390x r-base
• graphicsmagick_pu (1.4+really1.3.35-1 to 1.4+really1.3.35-1~deb10u1)
  • Migration status for graphicsmagick_pu (1.4+really1.3.35-1 to 1.4+really1.3.35-1~deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: graphicsmagick is newer in the target suite (1.4+really1.3.35-1 1.4+really1.3.35-1~deb10u1)
• gtksourceview2/amd64 (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/amd64 (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtksourceview2/arm64 (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/arm64 (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtksourceview2/armel (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/armel (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtksourceview2/armhf (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/armhf (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtksourceview2/i386 (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/i386 (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtksourceview2/mips64el (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/mips64el (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtksourceview2/mipsel (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/mipsel (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtksourceview2/ppc64el (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/ppc64el (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtksourceview2/s390x (2.10.5-3 to 2.10.5-3)
  • Migration status for gtksourceview2/s390x (2.10.5-3 to 2.10.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• gtools/amd64 (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/amd64 (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/amd64 r-base
• gtools/arm64 (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/arm64 (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/arm64 r-base
• gtools/armel (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/armel (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/armel r-base
• gtools/armhf (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/armhf (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/armhf r-base
• gtools/i386 (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/i386 (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/i386 r-base
• gtools/mips64el (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/mips64el (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/mips64el r-base
• gtools/mipsel (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/mipsel (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/mipsel r-base
• gtools/ppc64el (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/ppc64el (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/ppc64el r-base
• gtools/s390x (3.8.2-1 to 3.8.2-1)
  • Migration status for gtools/s390x (3.8.2-1 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: gtools/s390x r-base
• hmisc/amd64 (4.4-0-1 to 4.4-0-1)
  • Migration status for hmisc/amd64 (4.4-0-1 to 4.4-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: hmisc/amd64 r-base
• hmisc/arm64 (4.4-0-1 to 4.4-0-1)
  • Migration status for hmisc/arm64 (4.4-0-1 to 4.4-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: hmisc/arm64 r-base
• hmisc/armhf (4.4-0-1 to 4.4-0-1)
  • Migration status for hmisc/armhf (4.4-0-1 to 4.4-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: hmisc/armhf r-base
• hmisc/i386 (4.4-0-1 to 4.4-0-1)
  • Migration status for hmisc/i386 (4.4-0-1 to 4.4-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: hmisc/i386 r-base
• hmisc/mips64el (4.4-0-1 to 4.4-0-1)
  • Migration status for hmisc/mips64el (4.4-0-1 to 4.4-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: hmisc/mips64el r-base
• hmisc/mipsel (4.4-0-1 to 4.4-0-1)
  • Migration status for hmisc/mipsel (4.4-0-1 to 4.4-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: hmisc/mipsel r-base
• hmisc/ppc64el (4.4-0-1 to 4.4-0-1)
  • Migration status for hmisc/ppc64el (4.4-0-1 to 4.4-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: hmisc/ppc64el r-base
• hmisc/s390x (4.4-0-1 to 4.4-0-1)
  • Migration status for hmisc/s390x (4.4-0-1 to 4.4-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: hmisc/s390x r-base
• ifcplusplus/amd64 (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/amd64 (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/amd64 openscenegraph (not considered)
  • Invalidated by dependency
• ifcplusplus/arm64 (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/arm64 (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/arm64 openscenegraph (not considered)
  • Invalidated by dependency
• ifcplusplus/armel (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/armel (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/armel openscenegraph (not considered)
  • Invalidated by dependency
• ifcplusplus/armhf (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/armhf (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/armhf openscenegraph (not considered)
  • Invalidated by dependency
• ifcplusplus/i386 (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/i386 (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/i386 openscenegraph (not considered)
  • Invalidated by dependency
• ifcplusplus/mips64el (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/mips64el (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/mips64el openscenegraph (not considered)
  • Invalidated by dependency
• ifcplusplus/mipsel (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/mipsel (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/mipsel openscenegraph (not considered)
  • Invalidated by dependency
• ifcplusplus/ppc64el (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/ppc64el (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/ppc64el openscenegraph (not considered)
  • Invalidated by dependency
• ifcplusplus/s390x (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2)
  • Migration status for ifcplusplus/s390x (0~git20190402.13744d5+dfsg-2 to 0~git20190402.13744d5+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ifcplusplus/s390x openscenegraph (not considered)
  • Invalidated by dependency
• kernsmooth/amd64 (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/amd64 (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/amd64 r-base
• kernsmooth/arm64 (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/arm64 (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/arm64 r-base
• kernsmooth/armel (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/armel (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/armel r-base
• kernsmooth/armhf (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/armhf (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/armhf r-base
• kernsmooth/i386 (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/i386 (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/i386 r-base
• kernsmooth/mips64el (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/mips64el (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/mips64el r-base
• kernsmooth/mipsel (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/mipsel (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/mipsel r-base
• kernsmooth/ppc64el (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/ppc64el (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/ppc64el r-base
• kernsmooth/s390x (2.23-17-1 to 2.23-17-1)
  • Migration status for kernsmooth/s390x (2.23-17-1 to 2.23-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: kernsmooth/s390x r-base
• keystone_pu (2:17.0.0-1 to 2:14.2.0-0+deb10u1)
  • Migration status for keystone_pu (2:17.0.0-1 to 2:14.2.0-0+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: keystone is newer in the target suite (2:17.0.0-1 2:14.2.0-0+deb10u1)
• kgpg/amd64 (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/amd64 (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/amd64 kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/amd64 akonadi
  • Depends: kgpg/amd64 akonadi-contacts
• kgpg/arm64 (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/arm64 (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/arm64 kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/arm64 akonadi
  • Depends: kgpg/arm64 akonadi-contacts
• kgpg/armel (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/armel (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/armel kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/armel akonadi
  • Depends: kgpg/armel akonadi-contacts
• kgpg/armhf (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/armhf (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/armhf kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/armhf akonadi
  • Depends: kgpg/armhf akonadi-contacts
• kgpg/i386 (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/i386 (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/i386 kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/i386 akonadi
  • Depends: kgpg/i386 akonadi-contacts
• kgpg/mips64el (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/mips64el (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/mips64el kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/mips64el akonadi
  • Depends: kgpg/mips64el akonadi-contacts
• kgpg/mipsel (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/mipsel (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/mipsel kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/mipsel akonadi
  • Depends: kgpg/mipsel akonadi-contacts
• kgpg/ppc64el (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/ppc64el (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/ppc64el kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/ppc64el akonadi
  • Depends: kgpg/ppc64el akonadi-contacts
• kgpg/s390x (4:20.04.0-1 to 4:20.04.0-1)
  • Migration status for kgpg/s390x (4:20.04.0-1 to 4:20.04.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kgpg/s390x kio (not considered)
  • Invalidated by dependency
  • Depends: kgpg/s390x akonadi
  • Depends: kgpg/s390x akonadi-contacts
• 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:
  • Depends: kio-gdrive/amd64 kio (not considered)
  • Invalidated by dependency
  • Depends: kio-gdrive/amd64 libkgapi
• 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:
  • Depends: kio-gdrive/arm64 kio (not considered)
  • Invalidated by dependency
  • Depends: kio-gdrive/arm64 libkgapi
• 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:
  • Depends: kio-gdrive/armhf kio (not considered)
  • Invalidated by dependency
  • Depends: kio-gdrive/armhf libkgapi
• 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:
  • Depends: kio-gdrive/i386 kio (not considered)
  • Invalidated by dependency
  • Depends: kio-gdrive/i386 libkgapi
• 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:
  • Depends: kio-gdrive/mipsel kio (not considered)
  • Invalidated by dependency
  • Depends: kio-gdrive/mipsel libkgapi
• kjots/amd64 (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/amd64 (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/amd64 kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/amd64 akonadi
  • Depends: kjots/amd64 akonadi-notes
  • Depends: kjots/amd64 kmime
  • Depends: kjots/amd64 kontactinterface
  • Depends: kjots/amd64 kpimtextedit
• kjots/arm64 (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/arm64 (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/arm64 kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/arm64 akonadi
  • Depends: kjots/arm64 akonadi-notes
  • Depends: kjots/arm64 kmime
  • Depends: kjots/arm64 kontactinterface
  • Depends: kjots/arm64 kpimtextedit
• kjots/armel (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/armel (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/armel kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/armel akonadi
  • Depends: kjots/armel akonadi-notes
  • Depends: kjots/armel kmime
  • Depends: kjots/armel kontactinterface
  • Depends: kjots/armel kpimtextedit
• kjots/armhf (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/armhf (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/armhf kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/armhf akonadi
  • Depends: kjots/armhf akonadi-notes
  • Depends: kjots/armhf kmime
  • Depends: kjots/armhf kontactinterface
  • Depends: kjots/armhf kpimtextedit
• kjots/i386 (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/i386 (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/i386 kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/i386 akonadi
  • Depends: kjots/i386 akonadi-notes
  • Depends: kjots/i386 kmime
  • Depends: kjots/i386 kontactinterface
  • Depends: kjots/i386 kpimtextedit
• kjots/mips64el (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/mips64el (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/mips64el kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/mips64el akonadi
  • Depends: kjots/mips64el akonadi-notes
  • Depends: kjots/mips64el kmime
  • Depends: kjots/mips64el kontactinterface
  • Depends: kjots/mips64el kpimtextedit
• kjots/mipsel (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/mipsel (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/mipsel kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/mipsel akonadi
  • Depends: kjots/mipsel akonadi-notes
  • Depends: kjots/mipsel kmime
  • Depends: kjots/mipsel kontactinterface
  • Depends: kjots/mipsel kpimtextedit
• kjots/ppc64el (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/ppc64el (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/ppc64el kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/ppc64el akonadi
  • Depends: kjots/ppc64el akonadi-notes
  • Depends: kjots/ppc64el kmime
  • Depends: kjots/ppc64el kontactinterface
  • Depends: kjots/ppc64el kpimtextedit
• kjots/s390x (4:5.0.2-2 to 4:5.0.2-2)
  • Migration status for kjots/s390x (4:5.0.2-2 to 4:5.0.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kjots/s390x kio (not considered)
  • Invalidated by dependency
  • Depends: kjots/s390x akonadi
  • Depends: kjots/s390x akonadi-notes
  • Depends: kjots/s390x kmime
  • Depends: kjots/s390x kontactinterface
  • Depends: kjots/s390x kpimtextedit
• kmymoney/amd64 (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/amd64 (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/amd64 kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/amd64 akonadi
  • Depends: kmymoney/amd64 kidentitymanagement
• kmymoney/arm64 (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/arm64 (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/arm64 kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/arm64 akonadi
  • Depends: kmymoney/arm64 kidentitymanagement
• kmymoney/armel (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/armel (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/armel kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/armel akonadi
  • Depends: kmymoney/armel kidentitymanagement
• kmymoney/armhf (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/armhf (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/armhf kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/armhf akonadi
  • Depends: kmymoney/armhf kidentitymanagement
• kmymoney/i386 (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/i386 (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/i386 kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/i386 akonadi
  • Depends: kmymoney/i386 kidentitymanagement
• kmymoney/mips64el (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/mips64el (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/mips64el kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/mips64el akonadi
  • Depends: kmymoney/mips64el kidentitymanagement
• kmymoney/mipsel (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/mipsel (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/mipsel kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/mipsel akonadi
  • Depends: kmymoney/mipsel kidentitymanagement
• kmymoney/ppc64el (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/ppc64el (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/ppc64el kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/ppc64el akonadi
  • Depends: kmymoney/ppc64el kidentitymanagement
• kmymoney/s390x (5.0.8-1 to 5.0.8-1)
  • Migration status for kmymoney/s390x (5.0.8-1 to 5.0.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kmymoney/s390x kio (not considered)
  • Invalidated by dependency
  • Depends: kmymoney/s390x akonadi
  • Depends: kmymoney/s390x kidentitymanagement
• kraft/amd64 (0.90-2 to 0.90-2)
  • Migration status for kraft/amd64 (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/amd64 akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/amd64 akonadi-contacts
• kraft/arm64 (0.90-2 to 0.90-2)
  • Migration status for kraft/arm64 (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/arm64 akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/arm64 akonadi-contacts
• kraft/armel (0.90-2 to 0.90-2)
  • Migration status for kraft/armel (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/armel akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/armel akonadi-contacts
• kraft/armhf (0.90-2 to 0.90-2)
  • Migration status for kraft/armhf (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/armhf akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/armhf akonadi-contacts
• kraft/i386 (0.90-2 to 0.90-2)
  • Migration status for kraft/i386 (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/i386 akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/i386 akonadi-contacts
• kraft/mips64el (0.90-2 to 0.90-2)
  • Migration status for kraft/mips64el (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/mips64el akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/mips64el akonadi-contacts
• kraft/mipsel (0.90-2 to 0.90-2)
  • Migration status for kraft/mipsel (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/mipsel akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/mipsel akonadi-contacts
• kraft/ppc64el (0.90-2 to 0.90-2)
  • Migration status for kraft/ppc64el (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/ppc64el akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/ppc64el akonadi-contacts
• kraft/s390x (0.90-2 to 0.90-2)
  • Migration status for kraft/s390x (0.90-2 to 0.90-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: kraft/s390x akonadi (not considered)
  • Invalidated by dependency
  • Depends: kraft/s390x akonadi-contacts
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• lattice/amd64 (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/amd64 (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/amd64 r-base
• lattice/arm64 (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/arm64 (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/arm64 r-base
• lattice/armel (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/armel (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/armel r-base
• lattice/armhf (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/armhf (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/armhf r-base
• lattice/i386 (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/i386 (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/i386 r-base
• lattice/mips64el (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/mips64el (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/mips64el r-base
• lattice/mipsel (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/mipsel (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/mipsel r-base
• lattice/ppc64el (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/ppc64el (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/ppc64el r-base
• lattice/s390x (0.20-41-1 to 0.20-41-1)
  • Migration status for lattice/s390x (0.20-41-1 to 0.20-41-1): Will attempt migration (Any information below is purely informational)
  • Depends: lattice/s390x r-base
• lemonldap-ng_pu (2.0.8+ds1-2 to 2.0.2+ds-7+deb10u4)
  • Migration status for lemonldap-ng_pu (2.0.8+ds1-2 to 2.0.2+ds-7+deb10u4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: lemonldap-ng is newer in the target suite (2.0.8+ds1-2 2.0.2+ds-7+deb10u4)
• libguestfs/amd64 (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/amd64 (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/amd64 yara (not considered)
  • Invalidated by dependency
• libguestfs/arm64 (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/arm64 (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/arm64 yara (not considered)
  • Invalidated by dependency
• libguestfs/armel (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/armel (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/armel yara (not considered)
  • Invalidated by dependency
• libguestfs/armhf (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/armhf (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/armhf yara (not considered)
  • Invalidated by dependency
• libguestfs/i386 (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/i386 (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/i386 yara (not considered)
  • Invalidated by dependency
• libguestfs/mips64el (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/mips64el (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/mips64el yara (not considered)
  • Invalidated by dependency
• libguestfs/mipsel (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/mipsel (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/mipsel yara (not considered)
  • Invalidated by dependency
• libguestfs/ppc64el (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/ppc64el (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/ppc64el yara (not considered)
  • Invalidated by dependency
• libguestfs/s390x (1:1.42.0-1 to 1:1.42.0-1)
  • Migration status for libguestfs/s390x (1:1.42.0-1 to 1:1.42.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libguestfs/s390x yara (not considered)
  • Invalidated by dependency
• libreswan_pu (3.29-2 to 3.27-6+deb10u1)
  • Migration status for libreswan_pu (3.29-2 to 3.27-6+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: libreswan is newer in the target suite (3.29-2 3.27-6+deb10u1)
• libyang_pu (0.16.105-3 to 0.16.105-1+deb10u1)
  • Migration status for libyang_pu (0.16.105-3 to 0.16.105-1+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: libyang is newer in the target suite (0.16.105-3 0.16.105-1+deb10u1)
• littler/amd64 (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/amd64 (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/amd64 r-base
• littler/arm64 (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/arm64 (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/arm64 r-base
• littler/armel (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/armel (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/armel r-base
• littler/armhf (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/armhf (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/armhf r-base
• littler/i386 (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/i386 (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/i386 r-base
• littler/mips64el (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/mips64el (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/mips64el r-base
• littler/mipsel (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/mipsel (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/mipsel r-base
• littler/ppc64el (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/ppc64el (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/ppc64el r-base
• littler/s390x (0.3.9-1 to 0.3.9-1)
  • Migration status for littler/s390x (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: littler/s390x r-base
• lme4/amd64 (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/amd64 (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/amd64 r-base
• lme4/arm64 (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/arm64 (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/arm64 r-base
• lme4/armel (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/armel (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/armel r-base
• lme4/armhf (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/armhf (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/armhf r-base
• lme4/i386 (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/i386 (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/i386 r-base
• lme4/mips64el (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/mips64el (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/mips64el r-base
• lme4/mipsel (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/mipsel (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/mipsel r-base
• lme4/ppc64el (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/ppc64el (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/ppc64el r-base
• lme4/s390x (1.1-23-1 to 1.1-23-1)
  • Migration status for lme4/s390x (1.1-23-1 to 1.1-23-1): Will attempt migration (Any information below is purely informational)
  • Depends: lme4/s390x r-base
• lmtest/amd64 (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/amd64 (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/amd64 r-base
• lmtest/arm64 (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/arm64 (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/arm64 r-base
• lmtest/armel (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/armel (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/armel r-base
• lmtest/armhf (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/armhf (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/armhf r-base
• lmtest/i386 (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/i386 (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/i386 r-base
• lmtest/mips64el (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/mips64el (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/mips64el r-base
• lmtest/mipsel (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/mipsel (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/mipsel r-base
• lmtest/ppc64el (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/ppc64el (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/ppc64el r-base
• lmtest/s390x (0.9.37-2 to 0.9.37-2)
  • Migration status for lmtest/s390x (0.9.37-2 to 0.9.37-2): Will attempt migration (Any information below is purely informational)
  • Depends: lmtest/s390x r-base
• mgcv/amd64 (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/amd64 (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/amd64 r-base
• mgcv/arm64 (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/arm64 (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/arm64 r-base
• mgcv/armel (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/armel (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/armel r-base
• mgcv/armhf (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/armhf (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/armhf r-base
• mgcv/i386 (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/i386 (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/i386 r-base
• mgcv/mips64el (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/mips64el (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/mips64el r-base
• mgcv/mipsel (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/mipsel (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/mipsel r-base
• mgcv/ppc64el (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/ppc64el (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/ppc64el r-base
• mgcv/s390x (1.8-31-1 to 1.8-31-1)
  • Migration status for mgcv/s390x (1.8-31-1 to 1.8-31-1): Will attempt migration (Any information below is purely informational)
  • Depends: mgcv/s390x r-base
• mnormt/amd64 (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/amd64 (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/amd64 r-base
• mnormt/arm64 (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/arm64 (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/arm64 r-base
• mnormt/armel (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/armel (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/armel r-base
• mnormt/armhf (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/armhf (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/armhf r-base
• mnormt/i386 (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/i386 (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/i386 r-base
• mnormt/mips64el (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/mips64el (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/mips64el r-base
• mnormt/mipsel (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/mipsel (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/mipsel r-base
• mnormt/ppc64el (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/ppc64el (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/ppc64el r-base
• mnormt/s390x (1.5-7-1 to 1.5-7-1)
  • Migration status for mnormt/s390x (1.5-7-1 to 1.5-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: mnormt/s390x r-base
• mvtnorm/amd64 (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/amd64 (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/amd64 r-base
• mvtnorm/arm64 (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/arm64 (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/arm64 r-base
• mvtnorm/armel (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/armel (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/armel r-base
• mvtnorm/armhf (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/armhf (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/armhf r-base
• mvtnorm/i386 (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/i386 (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/i386 r-base
• mvtnorm/mips64el (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/mips64el (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/mips64el r-base
• mvtnorm/mipsel (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/mipsel (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/mipsel r-base
• mvtnorm/ppc64el (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/ppc64el (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/ppc64el r-base
• mvtnorm/s390x (1.1-0-1 to 1.1-0-1)
  • Migration status for mvtnorm/s390x (1.1-0-1 to 1.1-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: mvtnorm/s390x r-base
• nlme/amd64 (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/amd64 (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/amd64 r-base
• nlme/arm64 (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/arm64 (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/arm64 r-base
• nlme/armel (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/armel (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/armel r-base
• nlme/armhf (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/armhf (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/armhf r-base
• nlme/i386 (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/i386 (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/i386 r-base
• nlme/mips64el (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/mips64el (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/mips64el r-base
• nlme/mipsel (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/mipsel (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/mipsel r-base
• nlme/ppc64el (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/ppc64el (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/ppc64el r-base
• nlme/s390x (3.1.147-1 to 3.1.147-1)
  • Migration status for nlme/s390x (3.1.147-1 to 3.1.147-1): Will attempt migration (Any information below is purely informational)
  • Depends: nlme/s390x r-base
• node-dot-prop_pu (5.2.0-1 to 4.1.1-1+deb10u2)
  • Migration status for node-dot-prop_pu (5.2.0-1 to 4.1.1-1+deb10u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: node-dot-prop is newer in the target suite (5.2.0-1 4.1.1-1+deb10u2)
• node-handlebars_pu (3:4.7.2-3 to 3:4.1.0-1+deb10u1)
  • Migration status for node-handlebars_pu (3:4.7.2-3 to 3:4.1.0-1+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: node-handlebars is newer in the target suite (3:4.7.2-3 3:4.1.0-1+deb10u1)
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
• osgearth/amd64 (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/amd64 (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/amd64 openscenegraph (not considered)
  • Invalidated by dependency
• osgearth/arm64 (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/arm64 (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/arm64 openscenegraph (not considered)
  • Invalidated by dependency
• osgearth/armel (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/armel (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/armel openscenegraph (not considered)
  • Invalidated by dependency
• osgearth/armhf (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/armhf (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/armhf openscenegraph (not considered)
  • Invalidated by dependency
• osgearth/i386 (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/i386 (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/i386 openscenegraph (not considered)
  • Invalidated by dependency
• osgearth/mips64el (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/mips64el (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/mips64el openscenegraph (not considered)
  • Invalidated by dependency
• osgearth/mipsel (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/mipsel (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/mipsel openscenegraph (not considered)
  • Invalidated by dependency
• osgearth/ppc64el (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/ppc64el (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/ppc64el openscenegraph (not considered)
  • Invalidated by dependency
• osgearth/s390x (2.10.2+dfsg-2 to 2.10.2+dfsg-2)
  • Migration status for osgearth/s390x (2.10.2+dfsg-2 to 2.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: osgearth/s390x openscenegraph (not considered)
  • Invalidated by dependency
• pdfchain_pu (1:0.4.4.2-2 to 1:0.4.4.2-1+deb10u1)
  • Migration status for pdfchain_pu (1:0.4.4.2-2 to 1:0.4.4.2-1+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: pdfchain is newer in the target suite (1:0.4.4.2-2 1:0.4.4.2-1+deb10u1)
• pdns-recursor_pu (4.3.1-1 to 4.1.11-1+deb10u1)
  • Migration status for pdns-recursor_pu (4.3.1-1 to 4.1.11-1+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: pdns-recursor is newer in the target suite (4.3.1-1 4.1.11-1+deb10u1)
• qdirstat_pu (1.6.1-1 to 1.5-1+deb10u1)
  • Migration status for qdirstat_pu (1.6.1-1 to 1.5-1+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: qdirstat is newer in the target suite (1.6.1-1 1.5-1+deb10u1)
• quadprog/amd64 (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/amd64 (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/amd64 r-base
• quadprog/arm64 (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/arm64 (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/arm64 r-base
• quadprog/armel (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/armel (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/armel r-base
• quadprog/armhf (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/armhf (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/armhf r-base
• quadprog/i386 (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/i386 (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/i386 r-base
• quadprog/mips64el (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/mips64el (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/mips64el r-base
• quadprog/mipsel (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/mipsel (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/mipsel r-base
• quadprog/ppc64el (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/ppc64el (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/ppc64el r-base
• quadprog/s390x (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/s390x (1.5-8-1 to 1.5-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: quadprog/s390x r-base
• r-cran-actuar/amd64 (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/amd64 (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/amd64 r-base
• r-cran-actuar/arm64 (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/arm64 (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/arm64 r-base
• r-cran-actuar/armel (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/armel (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/armel r-base
• r-cran-actuar/armhf (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/armhf (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/armhf r-base
• r-cran-actuar/i386 (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/i386 (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/i386 r-base
• r-cran-actuar/mips64el (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/mips64el (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/mips64el r-base
• r-cran-actuar/mipsel (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/mipsel (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/mipsel r-base
• r-cran-actuar/ppc64el (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/ppc64el (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/ppc64el r-base
• r-cran-actuar/s390x (2.3-3-1 to 2.3-3-1)
  • Migration status for r-cran-actuar/s390x (2.3-3-1 to 2.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-actuar/s390x r-base
• r-cran-ade4/amd64 (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/amd64 (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/amd64 r-base
• r-cran-ade4/arm64 (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/arm64 (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/arm64 r-base
• r-cran-ade4/armel (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/armel (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/armel r-base
• r-cran-ade4/armhf (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/armhf (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/armhf r-base
• r-cran-ade4/i386 (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/i386 (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/i386 r-base
• r-cran-ade4/mips64el (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/mips64el (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/mips64el r-base
• r-cran-ade4/mipsel (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/mipsel (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/mipsel r-base
• r-cran-ade4/ppc64el (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/ppc64el (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/ppc64el r-base
• r-cran-ade4/s390x (1.7-15-1 to 1.7-15-1)
  • Migration status for r-cran-ade4/s390x (1.7-15-1 to 1.7-15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ade4/s390x r-base
• r-cran-adephylo/amd64 (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/amd64 (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/amd64 r-base
• r-cran-adephylo/arm64 (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/arm64 (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/arm64 r-base
• r-cran-adephylo/armel (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/armel (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/armel r-base
• r-cran-adephylo/armhf (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/armhf (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/armhf r-base
• r-cran-adephylo/i386 (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/i386 (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/i386 r-base
• r-cran-adephylo/mips64el (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/mips64el (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/mips64el r-base
• r-cran-adephylo/mipsel (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/mipsel (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/mipsel r-base
• r-cran-adephylo/ppc64el (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/ppc64el (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/ppc64el r-base
• r-cran-adephylo/s390x (1.1-11-3 to 1.1-11-3)
  • Migration status for r-cran-adephylo/s390x (1.1-11-3 to 1.1-11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adephylo/s390x r-base
• r-cran-amap/amd64 (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/amd64 (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/amd64 r-base
• r-cran-amap/arm64 (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/arm64 (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/arm64 r-base
• r-cran-amap/armel (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/armel (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/armel r-base
• r-cran-amap/armhf (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/armhf (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/armhf r-base
• r-cran-amap/i386 (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/i386 (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/i386 r-base
• r-cran-amap/mips64el (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/mips64el (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/mips64el r-base
• r-cran-amap/mipsel (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/mipsel (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/mipsel r-base
• r-cran-amap/ppc64el (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/ppc64el (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/ppc64el r-base
• r-cran-amap/s390x (0.8-18-2 to 0.8-18-2)
  • Migration status for r-cran-amap/s390x (0.8-18-2 to 0.8-18-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amap/s390x r-base
• r-cran-amelia/amd64 (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/amd64 (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/amd64 r-base
• r-cran-amelia/arm64 (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/arm64 (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/arm64 r-base
• r-cran-amelia/armel (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/armel (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/armel r-base
• r-cran-amelia/armhf (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/armhf (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/armhf r-base
• r-cran-amelia/i386 (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/i386 (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/i386 r-base
• r-cran-amelia/mips64el (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/mips64el (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/mips64el r-base
• r-cran-amelia/mipsel (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/mipsel (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/mipsel r-base
• r-cran-amelia/ppc64el (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/ppc64el (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/ppc64el r-base
• r-cran-amelia/s390x (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-amelia/s390x (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amelia/s390x r-base
• r-cran-amore/amd64 (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/amd64 (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/amd64 r-base
• r-cran-amore/arm64 (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/arm64 (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/arm64 r-base
• r-cran-amore/armel (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/armel (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/armel r-base
• r-cran-amore/armhf (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/armhf (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/armhf r-base
• r-cran-amore/i386 (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/i386 (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/i386 r-base
• r-cran-amore/mips64el (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/mips64el (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/mips64el r-base
• r-cran-amore/mipsel (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/mipsel (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/mipsel r-base
• r-cran-amore/ppc64el (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/ppc64el (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/ppc64el r-base
• r-cran-amore/s390x (0.2-16-1 to 0.2-16-1)
  • Migration status for r-cran-amore/s390x (0.2-16-1 to 0.2-16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-amore/s390x r-base
• r-cran-apcluster/amd64 (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/amd64 (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/amd64 r-base
• r-cran-apcluster/arm64 (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/arm64 (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/arm64 r-base
• r-cran-apcluster/armel (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/armel (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/armel r-base
• r-cran-apcluster/armhf (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/armhf (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/armhf r-base
• r-cran-apcluster/i386 (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/i386 (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/i386 r-base
• r-cran-apcluster/mips64el (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/mips64el (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/mips64el r-base
• r-cran-apcluster/mipsel (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/mipsel (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/mipsel r-base
• r-cran-apcluster/ppc64el (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/ppc64el (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/ppc64el r-base
• r-cran-apcluster/s390x (1.4.8-1 to 1.4.8-1)
  • Migration status for r-cran-apcluster/s390x (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-apcluster/s390x r-base
• r-cran-ape/amd64 (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/amd64 (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/amd64 r-base
• r-cran-ape/arm64 (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/arm64 (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/arm64 r-base
• r-cran-ape/armel (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/armel (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/armel r-base
• r-cran-ape/armhf (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/armhf (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/armhf r-base
• r-cran-ape/i386 (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/i386 (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/i386 r-base
• r-cran-ape/mips64el (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/mips64el (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/mips64el r-base
• r-cran-ape/mipsel (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/mipsel (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/mipsel r-base
• r-cran-ape/ppc64el (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/ppc64el (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/ppc64el r-base
• r-cran-ape/s390x (5.3-1 to 5.3-1)
  • Migration status for r-cran-ape/s390x (5.3-1 to 5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ape/s390x r-base
• r-cran-askpass/amd64 (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/amd64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/amd64 r-base
• r-cran-askpass/arm64 (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/arm64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/arm64 r-base
• r-cran-askpass/armel (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/armel (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/armel r-base
• r-cran-askpass/armhf (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/armhf (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/armhf r-base
• r-cran-askpass/i386 (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/i386 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/i386 r-base
• r-cran-askpass/mips64el (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/mips64el (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/mips64el r-base
• r-cran-askpass/mipsel (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/mipsel (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/mipsel r-base
• r-cran-askpass/ppc64el (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/ppc64el (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/ppc64el r-base
• r-cran-askpass/s390x (1.1-1 to 1.1-1)
  • Migration status for r-cran-askpass/s390x (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-askpass/s390x r-base
• r-cran-base64enc/amd64 (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/amd64 (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/amd64 r-base
• r-cran-base64enc/arm64 (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/arm64 (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/arm64 r-base
• r-cran-base64enc/armel (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/armel (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/armel r-base
• r-cran-base64enc/armhf (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/armhf (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/armhf r-base
• r-cran-base64enc/i386 (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/i386 (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/i386 r-base
• r-cran-base64enc/mips64el (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/mips64el (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/mips64el r-base
• r-cran-base64enc/mipsel (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/mipsel (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/mipsel r-base
• r-cran-base64enc/ppc64el (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/ppc64el (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/ppc64el r-base
• r-cran-base64enc/s390x (0.1-3-2 to 0.1-3-2)
  • Migration status for r-cran-base64enc/s390x (0.1-3-2 to 0.1-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64enc/s390x r-base
• r-cran-base64url/amd64 (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/amd64 (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/amd64 r-base
• r-cran-base64url/arm64 (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/arm64 (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/arm64 r-base
• r-cran-base64url/armel (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/armel (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/armel r-base
• r-cran-base64url/armhf (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/armhf (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/armhf r-base
• r-cran-base64url/i386 (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/i386 (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/i386 r-base
• r-cran-base64url/mips64el (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/mips64el (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/mips64el r-base
• r-cran-base64url/mipsel (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/mipsel (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/mipsel r-base
• r-cran-base64url/ppc64el (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/ppc64el (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/ppc64el r-base
• r-cran-base64url/s390x (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/s390x (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-base64url/s390x r-base
• r-cran-batchtools/amd64 (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/amd64 (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/amd64 r-base
• r-cran-batchtools/arm64 (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/arm64 (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/arm64 r-base
• r-cran-batchtools/armel (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/armel (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/armel r-base
• r-cran-batchtools/armhf (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/armhf (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/armhf r-base
• r-cran-batchtools/i386 (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/i386 (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/i386 r-base
• r-cran-batchtools/mips64el (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/mips64el (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/mips64el r-base
• r-cran-batchtools/mipsel (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/mipsel (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/mipsel r-base
• r-cran-batchtools/ppc64el (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/ppc64el (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/ppc64el r-base
• r-cran-batchtools/s390x (0.9.13-1 to 0.9.13-1)
  • Migration status for r-cran-batchtools/s390x (0.9.13-1 to 0.9.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchtools/s390x r-base
• r-cran-bayesfactor/amd64 (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/amd64 (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/amd64 r-base
• r-cran-bayesfactor/arm64 (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/arm64 (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/arm64 r-base
• r-cran-bayesfactor/armel (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/armel (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/armel r-base
• r-cran-bayesfactor/armhf (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/armhf (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/armhf r-base
• r-cran-bayesfactor/i386 (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/i386 (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/i386 r-base
• r-cran-bayesfactor/mips64el (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/mips64el (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/mips64el r-base
• r-cran-bayesfactor/mipsel (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/mipsel (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/mipsel r-base
• r-cran-bayesfactor/ppc64el (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/ppc64el (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/ppc64el r-base
• r-cran-bayesfactor/s390x (0.9.12-4.2-1 to 0.9.12-4.2-1)
  • Migration status for r-cran-bayesfactor/s390x (0.9.12-4.2-1 to 0.9.12-4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfactor/s390x r-base
• r-cran-bayesfm/amd64 (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/amd64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/amd64 r-base
• r-cran-bayesfm/arm64 (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/arm64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/arm64 r-base
• r-cran-bayesfm/armel (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/armel (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/armel r-base
• r-cran-bayesfm/armhf (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/armhf (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/armhf r-base
• r-cran-bayesfm/i386 (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/i386 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/i386 r-base
• r-cran-bayesfm/mips64el (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/mips64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/mips64el r-base
• r-cran-bayesfm/mipsel (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/mipsel (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/mipsel r-base
• r-cran-bayesfm/ppc64el (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/ppc64el (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/ppc64el r-base
• r-cran-bayesfm/s390x (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-bayesfm/s390x (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesfm/s390x r-base
• r-cran-bayesm/amd64 (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/amd64 (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/amd64 r-base
• r-cran-bayesm/arm64 (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/arm64 (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/arm64 r-base
• r-cran-bayesm/armel (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/armel (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/armel r-base
• r-cran-bayesm/armhf (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/armhf (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/armhf r-base
• r-cran-bayesm/i386 (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/i386 (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/i386 r-base
• r-cran-bayesm/mips64el (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/mips64el (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/mips64el r-base
• r-cran-bayesm/mipsel (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/mipsel (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/mipsel r-base
• r-cran-bayesm/ppc64el (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/ppc64el (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/ppc64el r-base
• r-cran-bayesm/s390x (3.1-4+dfsg-1 to 3.1-4+dfsg-1)
  • Migration status for r-cran-bayesm/s390x (3.1-4+dfsg-1 to 3.1-4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesm/s390x r-base
• r-cran-bbmisc/amd64 (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/amd64 (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/amd64 r-base
• r-cran-bbmisc/arm64 (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/arm64 (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/arm64 r-base
• r-cran-bbmisc/armel (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/armel (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/armel r-base
• r-cran-bbmisc/armhf (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/armhf (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/armhf r-base
• r-cran-bbmisc/i386 (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/i386 (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/i386 r-base
• r-cran-bbmisc/mips64el (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/mips64el (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/mips64el r-base
• r-cran-bbmisc/mipsel (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/mipsel (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/mipsel r-base
• r-cran-bbmisc/ppc64el (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/ppc64el (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/ppc64el r-base
• r-cran-bbmisc/s390x (1.11-3 to 1.11-3)
  • Migration status for r-cran-bbmisc/s390x (1.11-3 to 1.11-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmisc/s390x r-base
• r-cran-bdgraph/amd64 (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/amd64 (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/amd64 r-base
• r-cran-bdgraph/arm64 (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/arm64 (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/arm64 r-base
• r-cran-bdgraph/armel (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/armel (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/armel r-base
• r-cran-bdgraph/armhf (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/armhf (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/armhf r-base
• r-cran-bdgraph/i386 (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/i386 (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/i386 r-base
• r-cran-bdgraph/mips64el (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/mips64el (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/mips64el r-base
• r-cran-bdgraph/mipsel (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/mipsel (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/mipsel r-base
• r-cran-bdgraph/ppc64el (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/ppc64el (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/ppc64el r-base
• r-cran-bdgraph/s390x (2.62-1 to 2.62-1)
  • Migration status for r-cran-bdgraph/s390x (2.62-1 to 2.62-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdgraph/s390x r-base
• r-cran-bdsmatrix/amd64 (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/amd64 (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/amd64 r-base
• r-cran-bdsmatrix/arm64 (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/arm64 (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/arm64 r-base
• r-cran-bdsmatrix/armel (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/armel (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/armel r-base
• r-cran-bdsmatrix/armhf (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/armhf (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/armhf r-base
• r-cran-bdsmatrix/i386 (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/i386 (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/i386 r-base
• r-cran-bdsmatrix/mips64el (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/mips64el (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/mips64el r-base
• r-cran-bdsmatrix/mipsel (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/mipsel (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/mipsel r-base
• r-cran-bdsmatrix/ppc64el (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/ppc64el (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/ppc64el r-base
• r-cran-bdsmatrix/s390x (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-bdsmatrix/s390x (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bdsmatrix/s390x r-base
• r-cran-biasedurn/amd64 (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/amd64 (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/amd64 r-base
• r-cran-biasedurn/arm64 (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/arm64 (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/arm64 r-base
• r-cran-biasedurn/armel (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/armel (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/armel r-base
• r-cran-biasedurn/armhf (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/armhf (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/armhf r-base
• r-cran-biasedurn/i386 (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/i386 (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/i386 r-base
• r-cran-biasedurn/mips64el (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/mips64el (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/mips64el r-base
• r-cran-biasedurn/mipsel (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/mipsel (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/mipsel r-base
• r-cran-biasedurn/ppc64el (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/ppc64el (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/ppc64el r-base
• r-cran-biasedurn/s390x (1.07-3 to 1.07-3)
  • Migration status for r-cran-biasedurn/s390x (1.07-3 to 1.07-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biasedurn/s390x r-base
• r-cran-bibtex/amd64 (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/amd64 (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/amd64 r-base
• r-cran-bibtex/arm64 (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/arm64 (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/arm64 r-base
• r-cran-bibtex/armel (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/armel (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/armel r-base
• r-cran-bibtex/armhf (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/armhf (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/armhf r-base
• r-cran-bibtex/i386 (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/i386 (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/i386 r-base
• r-cran-bibtex/mips64el (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/mips64el (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/mips64el r-base
• r-cran-bibtex/mipsel (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/mipsel (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/mipsel r-base
• r-cran-bibtex/ppc64el (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/ppc64el (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/ppc64el r-base
• r-cran-bibtex/s390x (0.4.2.2-1 to 0.4.2.2-1)
  • Migration status for r-cran-bibtex/s390x (0.4.2.2-1 to 0.4.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bibtex/s390x r-base
• r-cran-bigmemory/amd64 (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/amd64 (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/amd64 r-base
• r-cran-bigmemory/arm64 (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/arm64 (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/arm64 r-base
• r-cran-bigmemory/armel (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/armel (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/armel r-base
• r-cran-bigmemory/armhf (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/armhf (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/armhf r-base
• r-cran-bigmemory/i386 (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/i386 (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/i386 r-base
• r-cran-bigmemory/mips64el (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/mips64el (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/mips64el r-base
• r-cran-bigmemory/mipsel (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/mipsel (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/mipsel r-base
• r-cran-bigmemory/ppc64el (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/ppc64el (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/ppc64el r-base
• r-cran-bigmemory/s390x (4.5.36-1 to 4.5.36-1)
  • Migration status for r-cran-bigmemory/s390x (4.5.36-1 to 4.5.36-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory/s390x r-base
• r-cran-bindrcpp/amd64 (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/amd64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/amd64 r-base
• r-cran-bindrcpp/arm64 (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/arm64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/arm64 r-base
• r-cran-bindrcpp/armel (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/armel (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/armel r-base
• r-cran-bindrcpp/armhf (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/armhf (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/armhf r-base
• r-cran-bindrcpp/i386 (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/i386 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/i386 r-base
• r-cran-bindrcpp/mips64el (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/mips64el (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/mips64el r-base
• r-cran-bindrcpp/mipsel (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/mipsel (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/mipsel r-base
• r-cran-bindrcpp/ppc64el (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/ppc64el (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/ppc64el r-base
• r-cran-bindrcpp/s390x (0.2.2-2 to 0.2.2-2)
  • Migration status for r-cran-bindrcpp/s390x (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindrcpp/s390x r-base
• r-cran-bio3d/amd64 (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/amd64 (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/amd64 r-base
• r-cran-bio3d/arm64 (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/arm64 (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/arm64 r-base
• r-cran-bio3d/armel (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/armel (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/armel r-base
• r-cran-bio3d/armhf (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/armhf (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/armhf r-base
• r-cran-bio3d/i386 (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/i386 (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/i386 r-base
• r-cran-bio3d/mips64el (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/mips64el (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/mips64el r-base
• r-cran-bio3d/mipsel (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/mipsel (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/mipsel r-base
• r-cran-bio3d/ppc64el (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/ppc64el (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/ppc64el r-base
• r-cran-bio3d/s390x (2.4-1-1 to 2.4-1-1)
  • Migration status for r-cran-bio3d/s390x (2.4-1-1 to 2.4-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bio3d/s390x r-base
• r-cran-bit/amd64 (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/amd64 (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/amd64 r-base
• r-cran-bit/arm64 (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/arm64 (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/arm64 r-base
• r-cran-bit/armel (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/armel (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/armel r-base
• r-cran-bit/armhf (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/armhf (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/armhf r-base
• r-cran-bit/i386 (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/i386 (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/i386 r-base
• r-cran-bit/mips64el (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/mips64el (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/mips64el r-base
• r-cran-bit/mipsel (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/mipsel (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/mipsel r-base
• r-cran-bit/ppc64el (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/ppc64el (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/ppc64el r-base
• r-cran-bit/s390x (1.1-15.2-1 to 1.1-15.2-1)
  • Migration status for r-cran-bit/s390x (1.1-15.2-1 to 1.1-15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit/s390x r-base
• r-cran-bit64/amd64 (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/amd64 (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/amd64 r-base
• r-cran-bit64/arm64 (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/arm64 (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/arm64 r-base
• r-cran-bit64/armel (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/armel (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/armel r-base
• r-cran-bit64/armhf (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/armhf (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/armhf r-base
• r-cran-bit64/i386 (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/i386 (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/i386 r-base
• r-cran-bit64/mips64el (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/mips64el (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/mips64el r-base
• r-cran-bit64/mipsel (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/mipsel (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/mipsel r-base
• r-cran-bit64/ppc64el (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/ppc64el (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/ppc64el r-base
• r-cran-bit64/s390x (0.9-7-3 to 0.9-7-3)
  • Migration status for r-cran-bit64/s390x (0.9-7-3 to 0.9-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bit64/s390x r-base
• r-cran-bitops/amd64 (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/amd64 (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/amd64 r-base
• r-cran-bitops/arm64 (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/arm64 (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/arm64 r-base
• r-cran-bitops/armel (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/armel (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/armel r-base
• r-cran-bitops/armhf (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/armhf (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/armhf r-base
• r-cran-bitops/i386 (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/i386 (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/i386 r-base
• r-cran-bitops/mips64el (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/mips64el (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/mips64el r-base
• r-cran-bitops/mipsel (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/mipsel (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/mipsel r-base
• r-cran-bitops/ppc64el (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/ppc64el (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/ppc64el r-base
• r-cran-bitops/s390x (1.0-6-4 to 1.0-6-4)
  • Migration status for r-cran-bitops/s390x (1.0-6-4 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bitops/s390x r-base
• r-cran-biwt/amd64 (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/amd64 (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/amd64 r-base
• r-cran-biwt/arm64 (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/arm64 (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/arm64 r-base
• r-cran-biwt/armel (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/armel (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/armel r-base
• r-cran-biwt/armhf (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/armhf (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/armhf r-base
• r-cran-biwt/i386 (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/i386 (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/i386 r-base
• r-cran-biwt/mips64el (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/mips64el (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/mips64el r-base
• r-cran-biwt/mipsel (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/mipsel (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/mipsel r-base
• r-cran-biwt/ppc64el (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/ppc64el (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/ppc64el r-base
• r-cran-biwt/s390x (1.0-2 to 1.0-2)
  • Migration status for r-cran-biwt/s390x (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biwt/s390x r-base
• r-cran-blockmodeling/amd64 (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/amd64 (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/amd64 r-base
• r-cran-blockmodeling/arm64 (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/arm64 (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/arm64 r-base
• r-cran-blockmodeling/armel (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/armel (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/armel r-base
• r-cran-blockmodeling/armhf (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/armhf (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/armhf r-base
• r-cran-blockmodeling/i386 (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/i386 (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/i386 r-base
• r-cran-blockmodeling/mips64el (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/mips64el (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/mips64el r-base
• r-cran-blockmodeling/mipsel (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/mipsel (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/mipsel r-base
• r-cran-blockmodeling/ppc64el (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/ppc64el (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/ppc64el r-base
• r-cran-blockmodeling/s390x (0.3.6-1 to 0.3.6-1)
  • Migration status for r-cran-blockmodeling/s390x (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blockmodeling/s390x r-base
• r-cran-boolnet/amd64 (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/amd64 (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/amd64 r-base
• r-cran-boolnet/arm64 (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/arm64 (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/arm64 r-base
• r-cran-boolnet/armel (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/armel (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/armel r-base
• r-cran-boolnet/armhf (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/armhf (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/armhf r-base
• r-cran-boolnet/i386 (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/i386 (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/i386 r-base
• r-cran-boolnet/mips64el (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/mips64el (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/mips64el r-base
• r-cran-boolnet/mipsel (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/mipsel (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/mipsel r-base
• r-cran-boolnet/ppc64el (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/ppc64el (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/ppc64el r-base
• r-cran-boolnet/s390x (2.1.5-2 to 2.1.5-2)
  • Migration status for r-cran-boolnet/s390x (2.1.5-2 to 2.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-boolnet/s390x r-base
• r-cran-brglm/amd64 (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/amd64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/amd64 r-base
• r-cran-brglm/arm64 (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/arm64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/arm64 r-base
• r-cran-brglm/armel (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/armel (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/armel r-base
• r-cran-brglm/armhf (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/armhf (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/armhf r-base
• r-cran-brglm/i386 (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/i386 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/i386 r-base
• r-cran-brglm/mips64el (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/mips64el (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/mips64el r-base
• r-cran-brglm/mipsel (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/mipsel (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/mipsel r-base
• r-cran-brglm/ppc64el (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/ppc64el (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/ppc64el r-base
• r-cran-brglm/s390x (0.6.2-1 to 0.6.2-1)
  • Migration status for r-cran-brglm/s390x (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brglm/s390x r-base
• r-cran-cairo/amd64 (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/amd64 (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/amd64 r-base
• r-cran-cairo/arm64 (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/arm64 (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/arm64 r-base
• r-cran-cairo/armel (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/armel (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/armel r-base
• r-cran-cairo/armhf (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/armhf (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/armhf r-base
• r-cran-cairo/i386 (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/i386 (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/i386 r-base
• r-cran-cairo/mips64el (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/mips64el (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/mips64el r-base
• r-cran-cairo/mipsel (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/mipsel (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/mipsel r-base
• r-cran-cairo/ppc64el (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/ppc64el (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/ppc64el r-base
• r-cran-cairo/s390x (1.5-12-1 to 1.5-12-1)
  • Migration status for r-cran-cairo/s390x (1.5-12-1 to 1.5-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cairo/s390x r-base
• r-cran-caret/amd64 (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/amd64 (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/amd64 r-base
• r-cran-caret/arm64 (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/arm64 (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/arm64 r-base
• r-cran-caret/armel (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/armel (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/armel r-base
• r-cran-caret/armhf (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/armhf (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/armhf r-base
• r-cran-caret/i386 (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/i386 (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/i386 r-base
• r-cran-caret/mips64el (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/mips64el (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/mips64el r-base
• r-cran-caret/mipsel (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/mipsel (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/mipsel r-base
• r-cran-caret/ppc64el (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/ppc64el (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/ppc64el r-base
• r-cran-caret/s390x (6.0-86+dfsg-1 to 6.0-86+dfsg-1)
  • Migration status for r-cran-caret/s390x (6.0-86+dfsg-1 to 6.0-86+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caret/s390x r-base
• r-cran-catools/amd64 (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/amd64 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/amd64 r-base
• r-cran-catools/arm64 (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/arm64 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/arm64 r-base
• r-cran-catools/armel (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/armel (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/armel r-base
• r-cran-catools/armhf (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/armhf (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/armhf r-base
• r-cran-catools/i386 (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/i386 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/i386 r-base
• r-cran-catools/mips64el (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/mips64el (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/mips64el r-base
• r-cran-catools/mipsel (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/mipsel (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/mipsel r-base
• r-cran-catools/ppc64el (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/ppc64el (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/ppc64el r-base
• r-cran-catools/s390x (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-catools/s390x (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-catools/s390x r-base
• r-cran-checkmate/amd64 (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/amd64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/amd64 r-base
• r-cran-checkmate/arm64 (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/arm64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/arm64 r-base
• r-cran-checkmate/armel (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/armel (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/armel r-base
• r-cran-checkmate/armhf (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/armhf (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/armhf r-base
• r-cran-checkmate/i386 (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/i386 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/i386 r-base
• r-cran-checkmate/mips64el (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/mips64el (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/mips64el r-base
• r-cran-checkmate/mipsel (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/mipsel (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/mipsel r-base
• r-cran-checkmate/ppc64el (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/ppc64el (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/ppc64el r-base
• r-cran-checkmate/s390x (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-checkmate/s390x (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-checkmate/s390x r-base
• r-cran-class/amd64 (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/amd64 (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/amd64 r-base
• r-cran-class/arm64 (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/arm64 (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/arm64 r-base
• r-cran-class/armel (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/armel (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/armel r-base
• r-cran-class/armhf (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/armhf (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/armhf r-base
• r-cran-class/i386 (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/i386 (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/i386 r-base
• r-cran-class/mips64el (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/mips64el (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/mips64el r-base
• r-cran-class/mipsel (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/mipsel (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/mipsel r-base
• r-cran-class/ppc64el (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/ppc64el (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/ppc64el r-base
• r-cran-class/s390x (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-class/s390x (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-class/s390x r-base
• r-cran-classint/amd64 (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/amd64 (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/amd64 r-base
• r-cran-classint/arm64 (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/arm64 (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/arm64 r-base
• r-cran-classint/armel (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/armel (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/armel r-base
• r-cran-classint/armhf (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/armhf (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/armhf r-base
• r-cran-classint/i386 (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/i386 (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/i386 r-base
• r-cran-classint/mips64el (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/mips64el (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/mips64el r-base
• r-cran-classint/mipsel (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/mipsel (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/mipsel r-base
• r-cran-classint/ppc64el (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/ppc64el (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/ppc64el r-base
• r-cran-classint/s390x (0.4-3-1 to 0.4-3-1)
  • Migration status for r-cran-classint/s390x (0.4-3-1 to 0.4-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-classint/s390x r-base
• r-cran-clue/amd64 (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/amd64 (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/amd64 r-base
• r-cran-clue/arm64 (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/arm64 (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/arm64 r-base
• r-cran-clue/armel (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/armel (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/armel r-base
• r-cran-clue/armhf (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/armhf (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/armhf r-base
• r-cran-clue/i386 (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/i386 (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/i386 r-base
• r-cran-clue/mips64el (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/mips64el (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/mips64el r-base
• r-cran-clue/mipsel (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/mipsel (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/mipsel r-base
• r-cran-clue/ppc64el (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/ppc64el (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/ppc64el r-base
• r-cran-clue/s390x (0.3-57-1 to 0.3-57-1)
  • Migration status for r-cran-clue/s390x (0.3-57-1 to 0.3-57-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clue/s390x r-base
• r-cran-cmprsk/amd64 (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/amd64 (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/amd64 r-base
• r-cran-cmprsk/arm64 (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/arm64 (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/arm64 r-base
• r-cran-cmprsk/armel (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/armel (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/armel r-base
• r-cran-cmprsk/armhf (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/armhf (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/armhf r-base
• r-cran-cmprsk/i386 (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/i386 (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/i386 r-base
• r-cran-cmprsk/mips64el (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/mips64el (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/mips64el r-base
• r-cran-cmprsk/mipsel (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/mipsel (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/mipsel r-base
• r-cran-cmprsk/ppc64el (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/ppc64el (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/ppc64el r-base
• r-cran-cmprsk/s390x (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-cmprsk/s390x (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cmprsk/s390x r-base
• r-cran-coin/amd64 (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/amd64 (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/amd64 r-base
• r-cran-coin/arm64 (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/arm64 (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/arm64 r-base
• r-cran-coin/armel (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/armel (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/armel r-base
• r-cran-coin/armhf (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/armhf (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/armhf r-base
• r-cran-coin/i386 (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/i386 (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/i386 r-base
• r-cran-coin/mips64el (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/mips64el (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/mips64el r-base
• r-cran-coin/mipsel (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/mipsel (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/mipsel r-base
• r-cran-coin/ppc64el (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/ppc64el (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/ppc64el r-base
• r-cran-coin/s390x (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-coin/s390x (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coin/s390x r-base
• r-cran-colorspace/amd64 (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/amd64 (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/amd64 r-base
• r-cran-colorspace/arm64 (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/arm64 (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/arm64 r-base
• r-cran-colorspace/armel (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/armel (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/armel r-base
• r-cran-colorspace/armhf (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/armhf (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/armhf r-base
• r-cran-colorspace/i386 (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/i386 (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/i386 r-base
• r-cran-colorspace/mips64el (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/mips64el (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/mips64el r-base
• r-cran-colorspace/mipsel (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/mipsel (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/mipsel r-base
• r-cran-colorspace/ppc64el (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/ppc64el (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/ppc64el r-base
• r-cran-colorspace/s390x (1.4-1+dfsg-1 to 1.4-1+dfsg-1)
  • Migration status for r-cran-colorspace/s390x (1.4-1+dfsg-1 to 1.4-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colorspace/s390x r-base
• r-cran-commonmark/amd64 (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/amd64 (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/amd64 r-base
• r-cran-commonmark/arm64 (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/arm64 (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/arm64 r-base
• r-cran-commonmark/armel (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/armel (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/armel r-base
• r-cran-commonmark/armhf (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/armhf (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/armhf r-base
• r-cran-commonmark/i386 (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/i386 (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/i386 r-base
• r-cran-commonmark/mips64el (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/mips64el (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/mips64el r-base
• r-cran-commonmark/mipsel (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/mipsel (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/mipsel r-base
• r-cran-commonmark/ppc64el (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/ppc64el (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/ppc64el r-base
• r-cran-commonmark/s390x (1.7-1 to 1.7-1)
  • Migration status for r-cran-commonmark/s390x (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-commonmark/s390x r-base
• r-cran-contfrac/amd64 (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/amd64 (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/amd64 r-base
• r-cran-contfrac/arm64 (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/arm64 (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/arm64 r-base
• r-cran-contfrac/armel (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/armel (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/armel r-base
• r-cran-contfrac/armhf (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/armhf (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/armhf r-base
• r-cran-contfrac/i386 (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/i386 (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/i386 r-base
• r-cran-contfrac/mips64el (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/mips64el (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/mips64el r-base
• r-cran-contfrac/mipsel (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/mipsel (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/mipsel r-base
• r-cran-contfrac/ppc64el (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/ppc64el (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/ppc64el r-base
• r-cran-contfrac/s390x (1.1-12-1 to 1.1-12-1)
  • Migration status for r-cran-contfrac/s390x (1.1-12-1 to 1.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-contfrac/s390x r-base
• r-cran-covr/amd64 (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/amd64 (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/amd64 r-base
• r-cran-covr/arm64 (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/arm64 (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/arm64 r-base
• r-cran-covr/armel (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/armel (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/armel r-base
• r-cran-covr/armhf (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/armhf (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/armhf r-base
• r-cran-covr/i386 (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/i386 (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/i386 r-base
• r-cran-covr/mips64el (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/mips64el (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/mips64el r-base
• r-cran-covr/mipsel (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/mipsel (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/mipsel r-base
• r-cran-covr/ppc64el (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/ppc64el (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/ppc64el r-base
• r-cran-covr/s390x (3.5.0+dfsg-1 to 3.5.0+dfsg-1)
  • Migration status for r-cran-covr/s390x (3.5.0+dfsg-1 to 3.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covr/s390x r-base
• r-cran-cubature/amd64 (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/amd64 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/amd64 r-base
• r-cran-cubature/arm64 (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/arm64 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/arm64 r-base
• r-cran-cubature/armel (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/armel (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/armel r-base
• r-cran-cubature/armhf (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/armhf (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/armhf r-base
• r-cran-cubature/i386 (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/i386 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/i386 r-base
• r-cran-cubature/mips64el (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/mips64el (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/mips64el r-base
• r-cran-cubature/mipsel (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/mipsel (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/mipsel r-base
• r-cran-cubature/ppc64el (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/ppc64el (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/ppc64el r-base
• r-cran-cubature/s390x (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-cubature/s390x (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cubature/s390x r-base
• r-cran-curl/amd64 (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/amd64 (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/amd64 r-base
• r-cran-curl/arm64 (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/arm64 (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/arm64 r-base
• r-cran-curl/armel (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/armel (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/armel r-base
• r-cran-curl/armhf (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/armhf (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/armhf r-base
• r-cran-curl/i386 (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/i386 (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/i386 r-base
• r-cran-curl/mips64el (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/mips64el (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/mips64el r-base
• r-cran-curl/mipsel (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/mipsel (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/mipsel r-base
• r-cran-curl/ppc64el (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/ppc64el (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/ppc64el r-base
• r-cran-curl/s390x (4.3+dfsg-1 to 4.3+dfsg-1)
  • Migration status for r-cran-curl/s390x (4.3+dfsg-1 to 4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-curl/s390x r-base
• r-cran-data.table/amd64 (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/amd64 (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/amd64 r-base
• r-cran-data.table/arm64 (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/arm64 (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/arm64 r-base
• r-cran-data.table/armel (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/armel (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/armel r-base
• r-cran-data.table/armhf (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/armhf (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/armhf r-base
• r-cran-data.table/i386 (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/i386 (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/i386 r-base
• r-cran-data.table/mips64el (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/mips64el (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/mips64el r-base
• r-cran-data.table/mipsel (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/mipsel (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/mipsel r-base
• r-cran-data.table/ppc64el (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/ppc64el (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/ppc64el r-base
• r-cran-data.table/s390x (1.12.8+dfsg-1 to 1.12.8+dfsg-1)
  • Migration status for r-cran-data.table/s390x (1.12.8+dfsg-1 to 1.12.8+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-data.table/s390x r-base
• r-cran-ddalpha/amd64 (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/amd64 (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/amd64 r-base
• r-cran-ddalpha/arm64 (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/arm64 (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/arm64 r-base
• r-cran-ddalpha/armel (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/armel (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/armel r-base
• r-cran-ddalpha/armhf (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/armhf (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/armhf r-base
• r-cran-ddalpha/i386 (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/i386 (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/i386 r-base
• r-cran-ddalpha/mips64el (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/mips64el (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/mips64el r-base
• r-cran-ddalpha/mipsel (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/mipsel (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/mipsel r-base
• r-cran-ddalpha/ppc64el (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/ppc64el (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/ppc64el r-base
• r-cran-ddalpha/s390x (1.3.11-1 to 1.3.11-1)
  • Migration status for r-cran-ddalpha/s390x (1.3.11-1 to 1.3.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ddalpha/s390x r-base
• r-cran-deal/amd64 (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/amd64 (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/amd64 r-base
• r-cran-deal/arm64 (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/arm64 (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/arm64 r-base
• r-cran-deal/armel (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/armel (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/armel r-base
• r-cran-deal/armhf (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/armhf (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/armhf r-base
• r-cran-deal/i386 (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/i386 (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/i386 r-base
• r-cran-deal/mips64el (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/mips64el (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/mips64el r-base
• r-cran-deal/mipsel (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/mipsel (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/mipsel r-base
• r-cran-deal/ppc64el (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/ppc64el (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/ppc64el r-base
• r-cran-deal/s390x (1:1.2-39-1 to 1:1.2-39-1)
  • Migration status for r-cran-deal/s390x (1:1.2-39-1 to 1:1.2-39-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deal/s390x r-base
• r-cran-deldir/amd64 (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/amd64 (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/amd64 r-base
• r-cran-deldir/arm64 (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/arm64 (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/arm64 r-base
• r-cran-deldir/armel (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/armel (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/armel r-base
• r-cran-deldir/armhf (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/armhf (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/armhf r-base
• r-cran-deldir/i386 (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/i386 (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/i386 r-base
• r-cran-deldir/mips64el (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/mips64el (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/mips64el r-base
• r-cran-deldir/mipsel (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/mipsel (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/mipsel r-base
• r-cran-deldir/ppc64el (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/ppc64el (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/ppc64el r-base
• r-cran-deldir/s390x (0.1-25-1 to 0.1-25-1)
  • Migration status for r-cran-deldir/s390x (0.1-25-1 to 0.1-25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deldir/s390x r-base
• r-cran-deoptim/amd64 (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/amd64 (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/amd64 r-base
• r-cran-deoptim/arm64 (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/arm64 (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/arm64 r-base
• r-cran-deoptim/armel (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/armel (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/armel r-base
• r-cran-deoptim/armhf (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/armhf (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/armhf r-base
• r-cran-deoptim/i386 (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/i386 (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/i386 r-base
• r-cran-deoptim/mips64el (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/mips64el (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/mips64el r-base
• r-cran-deoptim/mipsel (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/mipsel (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/mipsel r-base
• r-cran-deoptim/ppc64el (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/ppc64el (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/ppc64el r-base
• r-cran-deoptim/s390x (2.2-5-1 to 2.2-5-1)
  • Migration status for r-cran-deoptim/s390x (2.2-5-1 to 2.2-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptim/s390x r-base
• r-cran-deoptimr/amd64 (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/amd64 (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/amd64 r-base
• r-cran-deoptimr/arm64 (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/arm64 (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/arm64 r-base
• r-cran-deoptimr/armel (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/armel (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/armel r-base
• r-cran-deoptimr/armhf (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/armhf (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/armhf r-base
• r-cran-deoptimr/i386 (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/i386 (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/i386 r-base
• r-cran-deoptimr/mips64el (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/mips64el (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/mips64el r-base
• r-cran-deoptimr/mipsel (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/mipsel (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/mipsel r-base
• r-cran-deoptimr/ppc64el (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/ppc64el (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/ppc64el r-base
• r-cran-deoptimr/s390x (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-deoptimr/s390x (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-deoptimr/s390x r-base
• r-cran-desolve/amd64 (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/amd64 (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/amd64 r-base
• r-cran-desolve/arm64 (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/arm64 (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/arm64 r-base
• r-cran-desolve/armel (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/armel (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/armel r-base
• r-cran-desolve/armhf (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/armhf (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/armhf r-base
• r-cran-desolve/i386 (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/i386 (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/i386 r-base
• r-cran-desolve/mips64el (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/mips64el (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/mips64el r-base
• r-cran-desolve/mipsel (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/mipsel (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/mipsel r-base
• r-cran-desolve/ppc64el (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/ppc64el (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/ppc64el r-base
• r-cran-desolve/s390x (1.28-1 to 1.28-1)
  • Migration status for r-cran-desolve/s390x (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desolve/s390x r-base
• r-cran-digest/amd64 (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/amd64 (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/amd64 r-base
• r-cran-digest/arm64 (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/arm64 (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/arm64 r-base
• r-cran-digest/armel (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/armel (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/armel r-base
• r-cran-digest/armhf (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/armhf (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/armhf r-base
• r-cran-digest/i386 (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/i386 (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/i386 r-base
• r-cran-digest/mips64el (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/mips64el (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/mips64el r-base
• r-cran-digest/mipsel (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/mipsel (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/mipsel r-base
• r-cran-digest/ppc64el (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/ppc64el (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/ppc64el r-base
• r-cran-digest/s390x (0.6.25-1 to 0.6.25-1)
  • Migration status for r-cran-digest/s390x (0.6.25-1 to 0.6.25-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-digest/s390x r-base
• r-cran-dimred/amd64 (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/amd64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/amd64 r-base
• r-cran-dimred/arm64 (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/arm64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/arm64 r-base
• r-cran-dimred/armel (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/armel (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/armel r-base
• r-cran-dimred/armhf (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/armhf (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/armhf r-base
• r-cran-dimred/i386 (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/i386 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/i386 r-base
• r-cran-dimred/mips64el (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/mips64el (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/mips64el r-base
• r-cran-dimred/mipsel (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/mipsel (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/mipsel r-base
• r-cran-dimred/ppc64el (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/ppc64el (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/ppc64el r-base
• r-cran-dimred/s390x (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-dimred/s390x (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dimred/s390x r-base
• r-cran-diptest/amd64 (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/amd64 (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/amd64 r-base
• r-cran-diptest/arm64 (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/arm64 (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/arm64 r-base
• r-cran-diptest/armel (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/armel (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/armel r-base
• r-cran-diptest/armhf (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/armhf (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/armhf r-base
• r-cran-diptest/i386 (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/i386 (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/i386 r-base
• r-cran-diptest/mips64el (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/mips64el (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/mips64el r-base
• r-cran-diptest/mipsel (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/mipsel (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/mipsel r-base
• r-cran-diptest/ppc64el (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/ppc64el (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/ppc64el r-base
• r-cran-diptest/s390x (0.75-7-1 to 0.75-7-1)
  • Migration status for r-cran-diptest/s390x (0.75-7-1 to 0.75-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diptest/s390x r-base
• r-cran-distory/amd64 (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/amd64 (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/amd64 r-base
• r-cran-distory/arm64 (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/arm64 (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/arm64 r-base
• r-cran-distory/armel (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/armel (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/armel r-base
• r-cran-distory/armhf (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/armhf (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/armhf r-base
• r-cran-distory/i386 (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/i386 (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/i386 r-base
• r-cran-distory/mips64el (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/mips64el (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/mips64el r-base
• r-cran-distory/mipsel (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/mipsel (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/mipsel r-base
• r-cran-distory/ppc64el (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/ppc64el (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/ppc64el r-base
• r-cran-distory/s390x (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/s390x (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-distory/s390x r-base
• r-cran-dosefinding/amd64 (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/amd64 (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/amd64 r-base
• r-cran-dosefinding/arm64 (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/arm64 (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/arm64 r-base
• r-cran-dosefinding/armel (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/armel (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/armel r-base
• r-cran-dosefinding/armhf (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/armhf (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/armhf r-base
• r-cran-dosefinding/i386 (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/i386 (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/i386 r-base
• r-cran-dosefinding/mips64el (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/mips64el (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/mips64el r-base
• r-cran-dosefinding/mipsel (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/mipsel (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/mipsel r-base
• r-cran-dosefinding/ppc64el (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/ppc64el (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/ppc64el r-base
• r-cran-dosefinding/s390x (0.9-17-1 to 0.9-17-1)
  • Migration status for r-cran-dosefinding/s390x (0.9-17-1 to 0.9-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dosefinding/s390x r-base
• r-cran-dotcall64/amd64 (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/amd64 (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/amd64 r-base
• r-cran-dotcall64/arm64 (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/arm64 (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/arm64 r-base
• r-cran-dotcall64/armel (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/armel (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/armel r-base
• r-cran-dotcall64/armhf (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/armhf (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/armhf r-base
• r-cran-dotcall64/i386 (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/i386 (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/i386 r-base
• r-cran-dotcall64/mips64el (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/mips64el (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/mips64el r-base
• r-cran-dotcall64/mipsel (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/mipsel (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/mipsel r-base
• r-cran-dotcall64/ppc64el (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/ppc64el (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/ppc64el r-base
• r-cran-dotcall64/s390x (1.0-0-1 to 1.0-0-1)
  • Migration status for r-cran-dotcall64/s390x (1.0-0-1 to 1.0-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dotcall64/s390x r-base
• r-cran-dplyr/amd64 (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/amd64 (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/amd64 r-base
• r-cran-dplyr/arm64 (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/arm64 (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/arm64 r-base
• r-cran-dplyr/armel (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/armel (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/armel r-base
• r-cran-dplyr/armhf (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/armhf (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/armhf r-base
• r-cran-dplyr/i386 (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/i386 (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/i386 r-base
• r-cran-dplyr/mips64el (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/mips64el (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/mips64el r-base
• r-cran-dplyr/mipsel (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/mipsel (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/mipsel r-base
• r-cran-dplyr/ppc64el (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/ppc64el (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/ppc64el r-base
• r-cran-dplyr/s390x (0.8.5-1 to 0.8.5-1)
  • Migration status for r-cran-dplyr/s390x (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dplyr/s390x r-base
• r-cran-dqrng/amd64 (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/amd64 (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/amd64 r-base
• r-cran-dqrng/arm64 (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/arm64 (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/arm64 r-base
• r-cran-dqrng/armel (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/armel (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/armel r-base
• r-cran-dqrng/armhf (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/armhf (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/armhf r-base
• r-cran-dqrng/i386 (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/i386 (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/i386 r-base
• r-cran-dqrng/mips64el (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/mips64el (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/mips64el r-base
• r-cran-dqrng/mipsel (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/mipsel (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/mipsel r-base
• r-cran-dqrng/ppc64el (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/ppc64el (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/ppc64el r-base
• r-cran-dqrng/s390x (0.2.1+dfsg-4 to 0.2.1+dfsg-4)
  • Migration status for r-cran-dqrng/s390x (0.2.1+dfsg-4 to 0.2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dqrng/s390x r-base
• r-cran-e1071/amd64 (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/amd64 (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/amd64 r-base
• r-cran-e1071/arm64 (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/arm64 (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/arm64 r-base
• r-cran-e1071/armel (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/armel (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/armel r-base
• r-cran-e1071/armhf (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/armhf (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/armhf r-base
• r-cran-e1071/i386 (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/i386 (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/i386 r-base
• r-cran-e1071/mips64el (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/mips64el (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/mips64el r-base
• r-cran-e1071/mipsel (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/mipsel (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/mipsel r-base
• r-cran-e1071/ppc64el (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/ppc64el (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/ppc64el r-base
• r-cran-e1071/s390x (1.7-3-1 to 1.7-3-1)
  • Migration status for r-cran-e1071/s390x (1.7-3-1 to 1.7-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-e1071/s390x r-base
• r-cran-eaf/amd64 (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/amd64 (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/amd64 r-base
• r-cran-eaf/arm64 (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/arm64 (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/arm64 r-base
• r-cran-eaf/armel (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/armel (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/armel r-base
• r-cran-eaf/armhf (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/armhf (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/armhf r-base
• r-cran-eaf/i386 (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/i386 (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/i386 r-base
• r-cran-eaf/mips64el (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/mips64el (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/mips64el r-base
• r-cran-eaf/mipsel (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/mipsel (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/mipsel r-base
• r-cran-eaf/ppc64el (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/ppc64el (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/ppc64el r-base
• r-cran-eaf/s390x (1.9-1-1 to 1.9-1-1)
  • Migration status for r-cran-eaf/s390x (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eaf/s390x r-base
• r-cran-earth/amd64 (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/amd64 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/amd64 r-base
• r-cran-earth/arm64 (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/arm64 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/arm64 r-base
• r-cran-earth/armel (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/armel (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/armel r-base
• r-cran-earth/armhf (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/armhf (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/armhf r-base
• r-cran-earth/i386 (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/i386 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/i386 r-base
• r-cran-earth/mips64el (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/mips64el (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/mips64el r-base
• r-cran-earth/mipsel (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/mipsel (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/mipsel r-base
• r-cran-earth/ppc64el (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/ppc64el (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/ppc64el r-base
• r-cran-earth/s390x (5.1.2-1 to 5.1.2-1)
  • Migration status for r-cran-earth/s390x (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-earth/s390x r-base
• r-cran-eco/amd64 (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/amd64 (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/amd64 r-base
• r-cran-eco/arm64 (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/arm64 (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/arm64 r-base
• r-cran-eco/armel (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/armel (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/armel r-base
• r-cran-eco/armhf (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/armhf (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/armhf r-base
• r-cran-eco/i386 (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/i386 (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/i386 r-base
• r-cran-eco/mips64el (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/mips64el (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/mips64el r-base
• r-cran-eco/mipsel (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/mipsel (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/mipsel r-base
• r-cran-eco/ppc64el (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/ppc64el (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/ppc64el r-base
• r-cran-eco/s390x (4.0-1-2 to 4.0-1-2)
  • Migration status for r-cran-eco/s390x (4.0-1-2 to 4.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eco/s390x r-base
• r-cran-ecodist/amd64 (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/amd64 (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/amd64 r-base
• r-cran-ecodist/arm64 (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/arm64 (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/arm64 r-base
• r-cran-ecodist/armel (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/armel (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/armel r-base
• r-cran-ecodist/armhf (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/armhf (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/armhf r-base
• r-cran-ecodist/i386 (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/i386 (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/i386 r-base
• r-cran-ecodist/mips64el (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/mips64el (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/mips64el r-base
• r-cran-ecodist/mipsel (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/mipsel (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/mipsel r-base
• r-cran-ecodist/ppc64el (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/ppc64el (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/ppc64el r-base
• r-cran-ecodist/s390x (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-ecodist/s390x (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ecodist/s390x r-base
• r-cran-eipack/amd64 (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/amd64 (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/amd64 r-base
• r-cran-eipack/arm64 (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/arm64 (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/arm64 r-base
• r-cran-eipack/armel (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/armel (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/armel r-base
• r-cran-eipack/armhf (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/armhf (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/armhf r-base
• r-cran-eipack/i386 (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/i386 (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/i386 r-base
• r-cran-eipack/mips64el (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/mips64el (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/mips64el r-base
• r-cran-eipack/mipsel (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/mipsel (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/mipsel r-base
• r-cran-eipack/ppc64el (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/ppc64el (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/ppc64el r-base
• r-cran-eipack/s390x (0.2-1-1 to 0.2-1-1)
  • Migration status for r-cran-eipack/s390x (0.2-1-1 to 0.2-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-eipack/s390x r-base
• r-cran-emoa/amd64 (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/amd64 (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/amd64 r-base
• r-cran-emoa/arm64 (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/arm64 (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/arm64 r-base
• r-cran-emoa/armel (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/armel (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/armel r-base
• r-cran-emoa/armhf (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/armhf (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/armhf r-base
• r-cran-emoa/i386 (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/i386 (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/i386 r-base
• r-cran-emoa/mips64el (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/mips64el (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/mips64el r-base
• r-cran-emoa/mipsel (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/mipsel (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/mipsel r-base
• r-cran-emoa/ppc64el (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/ppc64el (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/ppc64el r-base
• r-cran-emoa/s390x (0.5-0.1-1 to 0.5-0.1-1)
  • Migration status for r-cran-emoa/s390x (0.5-0.1-1 to 0.5-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-emoa/s390x r-base
• r-cran-energy/amd64 (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/amd64 (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/amd64 r-base
• r-cran-energy/arm64 (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/arm64 (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/arm64 r-base
• r-cran-energy/armel (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/armel (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/armel r-base
• r-cran-energy/armhf (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/armhf (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/armhf r-base
• r-cran-energy/i386 (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/i386 (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/i386 r-base
• r-cran-energy/mips64el (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/mips64el (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/mips64el r-base
• r-cran-energy/mipsel (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/mipsel (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/mipsel r-base
• r-cran-energy/ppc64el (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/ppc64el (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/ppc64el r-base
• r-cran-energy/s390x (1.7-7-1 to 1.7-7-1)
  • Migration status for r-cran-energy/s390x (1.7-7-1 to 1.7-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-energy/s390x r-base
• r-cran-epi/amd64 (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/amd64 (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/amd64 r-base
• r-cran-epi/arm64 (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/arm64 (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/arm64 r-base
• r-cran-epi/armel (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/armel (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/armel r-base
• r-cran-epi/armhf (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/armhf (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/armhf r-base
• r-cran-epi/i386 (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/i386 (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/i386 r-base
• r-cran-epi/mips64el (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/mips64el (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/mips64el r-base
• r-cran-epi/mipsel (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/mipsel (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/mipsel r-base
• r-cran-epi/ppc64el (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/ppc64el (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/ppc64el r-base
• r-cran-epi/s390x (2.40-1 to 2.40-1)
  • Migration status for r-cran-epi/s390x (2.40-1 to 2.40-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epi/s390x r-base
• r-cran-erm/amd64 (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/amd64 (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/amd64 r-base
• r-cran-erm/arm64 (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/arm64 (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/arm64 r-base
• r-cran-erm/armel (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/armel (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/armel r-base
• r-cran-erm/armhf (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/armhf (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/armhf r-base
• r-cran-erm/i386 (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/i386 (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/i386 r-base
• r-cran-erm/mips64el (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/mips64el (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/mips64el r-base
• r-cran-erm/mipsel (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/mipsel (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/mipsel r-base
• r-cran-erm/ppc64el (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/ppc64el (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/ppc64el r-base
• r-cran-erm/s390x (1.0-1-1 to 1.0-1-1)
  • Migration status for r-cran-erm/s390x (1.0-1-1 to 1.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-erm/s390x r-base
• r-cran-evd/amd64 (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/amd64 (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/amd64 r-base
• r-cran-evd/arm64 (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/arm64 (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/arm64 r-base
• r-cran-evd/armel (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/armel (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/armel r-base
• r-cran-evd/armhf (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/armhf (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/armhf r-base
• r-cran-evd/i386 (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/i386 (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/i386 r-base
• r-cran-evd/mips64el (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/mips64el (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/mips64el r-base
• r-cran-evd/mipsel (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/mipsel (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/mipsel r-base
• r-cran-evd/ppc64el (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/ppc64el (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/ppc64el r-base
• r-cran-evd/s390x (2.3-3-2 to 2.3-3-2)
  • Migration status for r-cran-evd/s390x (2.3-3-2 to 2.3-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evd/s390x r-base
• r-cran-exactranktests/amd64 (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/amd64 (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/amd64 r-base
• r-cran-exactranktests/arm64 (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/arm64 (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/arm64 r-base
• r-cran-exactranktests/armel (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/armel (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/armel r-base
• r-cran-exactranktests/armhf (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/armhf (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/armhf r-base
• r-cran-exactranktests/i386 (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/i386 (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/i386 r-base
• r-cran-exactranktests/mips64el (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/mips64el (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/mips64el r-base
• r-cran-exactranktests/mipsel (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/mipsel (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/mipsel r-base
• r-cran-exactranktests/ppc64el (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/ppc64el (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/ppc64el r-base
• r-cran-exactranktests/s390x (0.8-31-2 to 0.8-31-2)
  • Migration status for r-cran-exactranktests/s390x (0.8-31-2 to 0.8-31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-exactranktests/s390x r-base
• r-cran-expint/amd64 (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/amd64 (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/amd64 r-base
• r-cran-expint/arm64 (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/arm64 (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/arm64 r-base
• r-cran-expint/armel (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/armel (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/armel r-base
• r-cran-expint/armhf (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/armhf (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/armhf r-base
• r-cran-expint/i386 (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/i386 (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/i386 r-base
• r-cran-expint/mips64el (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/mips64el (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/mips64el r-base
• r-cran-expint/mipsel (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/mipsel (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/mipsel r-base
• r-cran-expint/ppc64el (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/ppc64el (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/ppc64el r-base
• r-cran-expint/s390x (0.1-6-1 to 0.1-6-1)
  • Migration status for r-cran-expint/s390x (0.1-6-1 to 0.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expint/s390x r-base
• r-cran-expm/amd64 (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/amd64 (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/amd64 r-base
• r-cran-expm/arm64 (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/arm64 (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/arm64 r-base
• r-cran-expm/armel (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/armel (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/armel r-base
• r-cran-expm/armhf (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/armhf (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/armhf r-base
• r-cran-expm/i386 (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/i386 (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/i386 r-base
• r-cran-expm/mips64el (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/mips64el (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/mips64el r-base
• r-cran-expm/mipsel (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/mipsel (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/mipsel r-base
• r-cran-expm/ppc64el (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/ppc64el (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/ppc64el r-base
• r-cran-expm/s390x (0.999-4-1 to 0.999-4-1)
  • Migration status for r-cran-expm/s390x (0.999-4-1 to 0.999-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-expm/s390x r-base
• r-cran-extradistr/amd64 (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/amd64 (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/amd64 r-base
• r-cran-extradistr/arm64 (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/arm64 (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/arm64 r-base
• r-cran-extradistr/armel (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/armel (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/armel r-base
• r-cran-extradistr/armhf (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/armhf (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/armhf r-base
• r-cran-extradistr/i386 (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/i386 (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/i386 r-base
• r-cran-extradistr/mips64el (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/mips64el (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/mips64el r-base
• r-cran-extradistr/mipsel (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/mipsel (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/mipsel r-base
• r-cran-extradistr/ppc64el (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/ppc64el (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/ppc64el r-base
• r-cran-extradistr/s390x (1.8.11-1 to 1.8.11-1)
  • Migration status for r-cran-extradistr/s390x (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-extradistr/s390x r-base
• r-cran-fansi/amd64 (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/amd64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/amd64 r-base
• r-cran-fansi/arm64 (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/arm64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/arm64 r-base
• r-cran-fansi/armel (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/armel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/armel r-base
• r-cran-fansi/armhf (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/armhf (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/armhf r-base
• r-cran-fansi/i386 (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/i386 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/i386 r-base
• r-cran-fansi/mips64el (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/mips64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/mips64el r-base
• r-cran-fansi/mipsel (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/mipsel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/mipsel r-base
• r-cran-fansi/ppc64el (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/ppc64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/ppc64el r-base
• r-cran-fansi/s390x (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-fansi/s390x (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fansi/s390x r-base
• r-cran-farver/amd64 (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/amd64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/amd64 r-base
• r-cran-farver/arm64 (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/arm64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/arm64 r-base
• r-cran-farver/armel (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/armel (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/armel r-base
• r-cran-farver/armhf (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/armhf (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/armhf r-base
• r-cran-farver/i386 (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/i386 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/i386 r-base
• r-cran-farver/mips64el (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/mips64el (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/mips64el r-base
• r-cran-farver/mipsel (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/mipsel (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/mipsel r-base
• r-cran-farver/ppc64el (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/ppc64el (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/ppc64el r-base
• r-cran-farver/s390x (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-farver/s390x (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-farver/s390x r-base
• r-cran-fastcluster/amd64 (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/amd64 (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/amd64 r-base
• r-cran-fastcluster/arm64 (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/arm64 (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/arm64 r-base
• r-cran-fastcluster/armel (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/armel (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/armel r-base
• r-cran-fastcluster/armhf (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/armhf (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/armhf r-base
• r-cran-fastcluster/i386 (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/i386 (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/i386 r-base
• r-cran-fastcluster/mips64el (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/mips64el (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/mips64el r-base
• r-cran-fastcluster/mipsel (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/mipsel (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/mipsel r-base
• r-cran-fastcluster/ppc64el (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/ppc64el (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/ppc64el r-base
• r-cran-fastcluster/s390x (1.1.25-3 to 1.1.25-3)
  • Migration status for r-cran-fastcluster/s390x (1.1.25-3 to 1.1.25-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastcluster/s390x r-base
• r-cran-fastica/amd64 (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/amd64 (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/amd64 r-base
• r-cran-fastica/arm64 (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/arm64 (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/arm64 r-base
• r-cran-fastica/armel (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/armel (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/armel r-base
• r-cran-fastica/armhf (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/armhf (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/armhf r-base
• r-cran-fastica/i386 (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/i386 (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/i386 r-base
• r-cran-fastica/mips64el (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/mips64el (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/mips64el r-base
• r-cran-fastica/mipsel (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/mipsel (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/mipsel r-base
• r-cran-fastica/ppc64el (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/ppc64el (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/ppc64el r-base
• r-cran-fastica/s390x (1.2-2-2 to 1.2-2-2)
  • Migration status for r-cran-fastica/s390x (1.2-2-2 to 1.2-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastica/s390x r-base
• r-cran-fastmap/amd64 (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/amd64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/amd64 r-base
• r-cran-fastmap/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/arm64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/arm64 r-base
• r-cran-fastmap/armel (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/armel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/armel r-base
• r-cran-fastmap/armhf (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/armhf (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/armhf r-base
• r-cran-fastmap/i386 (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/i386 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/i386 r-base
• r-cran-fastmap/mips64el (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/mips64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/mips64el r-base
• r-cran-fastmap/mipsel (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/mipsel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/mipsel r-base
• r-cran-fastmap/ppc64el (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/ppc64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/ppc64el r-base
• r-cran-fastmap/s390x (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-fastmap/s390x (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmap/s390x r-base
• r-cran-fastmatch/amd64 (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/amd64 (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/amd64 r-base
• r-cran-fastmatch/arm64 (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/arm64 (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/arm64 r-base
• r-cran-fastmatch/armel (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/armel (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/armel r-base
• r-cran-fastmatch/armhf (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/armhf (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/armhf r-base
• r-cran-fastmatch/i386 (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/i386 (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/i386 r-base
• r-cran-fastmatch/mips64el (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/mips64el (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/mips64el r-base
• r-cran-fastmatch/mipsel (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/mipsel (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/mipsel r-base
• r-cran-fastmatch/ppc64el (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/ppc64el (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/ppc64el r-base
• r-cran-fastmatch/s390x (1.1-0-2 to 1.1-0-2)
  • Migration status for r-cran-fastmatch/s390x (1.1-0-2 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fastmatch/s390x r-base
• r-cran-fdrtool/amd64 (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/amd64 (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/amd64 r-base
• r-cran-fdrtool/arm64 (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/arm64 (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/arm64 r-base
• r-cran-fdrtool/armel (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/armel (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/armel r-base
• r-cran-fdrtool/armhf (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/armhf (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/armhf r-base
• r-cran-fdrtool/i386 (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/i386 (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/i386 r-base
• r-cran-fdrtool/mips64el (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/mips64el (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/mips64el r-base
• r-cran-fdrtool/mipsel (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/mipsel (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/mipsel r-base
• r-cran-fdrtool/ppc64el (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/ppc64el (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/ppc64el r-base
• r-cran-fdrtool/s390x (1.2.15-1 to 1.2.15-1)
  • Migration status for r-cran-fdrtool/s390x (1.2.15-1 to 1.2.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fdrtool/s390x r-base
• r-cran-fields/amd64 (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/amd64 (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/amd64 r-base
• r-cran-fields/arm64 (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/arm64 (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/arm64 r-base
• r-cran-fields/armel (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/armel (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/armel r-base
• r-cran-fields/armhf (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/armhf (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/armhf r-base
• r-cran-fields/i386 (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/i386 (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/i386 r-base
• r-cran-fields/mips64el (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/mips64el (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/mips64el r-base
• r-cran-fields/mipsel (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/mipsel (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/mipsel r-base
• r-cran-fields/ppc64el (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/ppc64el (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/ppc64el r-base
• r-cran-fields/s390x (10.3-1 to 10.3-1)
  • Migration status for r-cran-fields/s390x (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fields/s390x r-base
• r-cran-filehash/amd64 (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/amd64 (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/amd64 r-base
• r-cran-filehash/arm64 (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/arm64 (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/arm64 r-base
• r-cran-filehash/armel (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/armel (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/armel r-base
• r-cran-filehash/armhf (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/armhf (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/armhf r-base
• r-cran-filehash/i386 (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/i386 (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/i386 r-base
• r-cran-filehash/mips64el (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/mips64el (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/mips64el r-base
• r-cran-filehash/mipsel (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/mipsel (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/mipsel r-base
• r-cran-filehash/ppc64el (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/ppc64el (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/ppc64el r-base
• r-cran-filehash/s390x (2.4-2-2 to 2.4-2-2)
  • Migration status for r-cran-filehash/s390x (2.4-2-2 to 2.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-filehash/s390x r-base
• r-cran-fingerprint/amd64 (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/amd64 (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/amd64 r-base
• r-cran-fingerprint/arm64 (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/arm64 (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/arm64 r-base
• r-cran-fingerprint/armel (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/armel (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/armel r-base
• r-cran-fingerprint/armhf (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/armhf (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/armhf r-base
• r-cran-fingerprint/i386 (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/i386 (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/i386 r-base
• r-cran-fingerprint/mips64el (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/mips64el (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/mips64el r-base
• r-cran-fingerprint/mipsel (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/mipsel (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/mipsel r-base
• r-cran-fingerprint/ppc64el (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/ppc64el (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/ppc64el r-base
• r-cran-fingerprint/s390x (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/s390x (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fingerprint/s390x r-base
• r-cran-flashclust/amd64 (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/amd64 (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/amd64 r-base
• r-cran-flashclust/arm64 (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/arm64 (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/arm64 r-base
• r-cran-flashclust/armel (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/armel (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/armel r-base
• r-cran-flashclust/armhf (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/armhf (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/armhf r-base
• r-cran-flashclust/i386 (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/i386 (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/i386 r-base
• r-cran-flashclust/mips64el (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/mips64el (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/mips64el r-base
• r-cran-flashclust/mipsel (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/mipsel (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/mipsel r-base
• r-cran-flashclust/ppc64el (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/ppc64el (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/ppc64el r-base
• r-cran-flashclust/s390x (1.01-2-2 to 1.01-2-2)
  • Migration status for r-cran-flashclust/s390x (1.01-2-2 to 1.01-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flashclust/s390x r-base
• r-cran-fnn/amd64 (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/amd64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/amd64 r-base
• r-cran-fnn/arm64 (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/arm64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/arm64 r-base
• r-cran-fnn/armel (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/armel (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/armel r-base
• r-cran-fnn/armhf (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/armhf (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/armhf r-base
• r-cran-fnn/i386 (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/i386 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/i386 r-base
• r-cran-fnn/mips64el (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/mips64el (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/mips64el r-base
• r-cran-fnn/mipsel (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/mipsel (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/mipsel r-base
• r-cran-fnn/ppc64el (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/ppc64el (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/ppc64el r-base
• r-cran-fnn/s390x (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-fnn/s390x (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fnn/s390x r-base
• r-cran-forecast/amd64 (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/amd64 (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/amd64 r-base
• r-cran-forecast/arm64 (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/arm64 (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/arm64 r-base
• r-cran-forecast/armel (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/armel (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/armel r-base
• r-cran-forecast/armhf (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/armhf (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/armhf r-base
• r-cran-forecast/i386 (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/i386 (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/i386 r-base
• r-cran-forecast/mips64el (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/mips64el (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/mips64el r-base
• r-cran-forecast/mipsel (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/mipsel (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/mipsel r-base
• r-cran-forecast/ppc64el (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/ppc64el (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/ppc64el r-base
• r-cran-forecast/s390x (8.12-1 to 8.12-1)
  • Migration status for r-cran-forecast/s390x (8.12-1 to 8.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-forecast/s390x r-base
• r-cran-fracdiff/amd64 (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/amd64 (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/amd64 r-base
• r-cran-fracdiff/arm64 (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/arm64 (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/arm64 r-base
• r-cran-fracdiff/armel (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/armel (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/armel r-base
• r-cran-fracdiff/armhf (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/armhf (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/armhf r-base
• r-cran-fracdiff/i386 (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/i386 (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/i386 r-base
• r-cran-fracdiff/mips64el (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/mips64el (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/mips64el r-base
• r-cran-fracdiff/mipsel (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/mipsel (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/mipsel r-base
• r-cran-fracdiff/ppc64el (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/ppc64el (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/ppc64el r-base
• r-cran-fracdiff/s390x (1.5-1-1 to 1.5-1-1)
  • Migration status for r-cran-fracdiff/s390x (1.5-1-1 to 1.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fracdiff/s390x r-base
• r-cran-freetypeharfbuzz/amd64 (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/amd64 (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/amd64 r-base
• r-cran-freetypeharfbuzz/arm64 (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/arm64 (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/arm64 r-base
• r-cran-freetypeharfbuzz/armel (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/armel (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/armel r-base
• r-cran-freetypeharfbuzz/armhf (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/armhf (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/armhf r-base
• r-cran-freetypeharfbuzz/i386 (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/i386 (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/i386 r-base
• r-cran-freetypeharfbuzz/mips64el (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/mips64el (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/mips64el r-base
• r-cran-freetypeharfbuzz/mipsel (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/mipsel (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/mipsel r-base
• r-cran-freetypeharfbuzz/ppc64el (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/ppc64el (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/ppc64el r-base
• r-cran-freetypeharfbuzz/s390x (0.2.5+dfsg-2 to 0.2.5+dfsg-2)
  • Migration status for r-cran-freetypeharfbuzz/s390x (0.2.5+dfsg-2 to 0.2.5+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-freetypeharfbuzz/s390x r-base
• r-cran-fs/amd64 (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/amd64 (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/amd64 r-base
• r-cran-fs/arm64 (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/arm64 (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/arm64 r-base
• r-cran-fs/armel (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/armel (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/armel r-base
• r-cran-fs/armhf (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/armhf (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/armhf r-base
• r-cran-fs/i386 (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/i386 (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/i386 r-base
• r-cran-fs/mips64el (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/mips64el (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/mips64el r-base
• r-cran-fs/mipsel (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/mipsel (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/mipsel r-base
• r-cran-fs/ppc64el (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/ppc64el (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/ppc64el r-base
• r-cran-fs/s390x (1.4.1+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-fs/s390x (1.4.1+dfsg-1 to 1.4.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fs/s390x r-base
• r-cran-fts/amd64 (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/amd64 (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/amd64 r-base
• r-cran-fts/arm64 (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/arm64 (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/arm64 r-base
• r-cran-fts/armel (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/armel (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/armel r-base
• r-cran-fts/armhf (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/armhf (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/armhf r-base
• r-cran-fts/i386 (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/i386 (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/i386 r-base
• r-cran-fts/mips64el (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/mips64el (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/mips64el r-base
• r-cran-fts/mipsel (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/mipsel (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/mipsel r-base
• r-cran-fts/ppc64el (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/ppc64el (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/ppc64el r-base
• r-cran-fts/s390x (0.9.9.2-1 to 0.9.9.2-1)
  • Migration status for r-cran-fts/s390x (0.9.9.2-1 to 0.9.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fts/s390x r-base
• r-cran-gam/amd64 (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/amd64 (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/amd64 r-base
• r-cran-gam/arm64 (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/arm64 (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/arm64 r-base
• r-cran-gam/armel (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/armel (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/armel r-base
• r-cran-gam/armhf (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/armhf (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/armhf r-base
• r-cran-gam/i386 (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/i386 (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/i386 r-base
• r-cran-gam/mips64el (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/mips64el (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/mips64el r-base
• r-cran-gam/mipsel (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/mipsel (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/mipsel r-base
• r-cran-gam/ppc64el (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/ppc64el (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/ppc64el r-base
• r-cran-gam/s390x (1.16.1-1 to 1.16.1-1)
  • Migration status for r-cran-gam/s390x (1.16.1-1 to 1.16.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gam/s390x r-base
• r-cran-gbm/amd64 (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/amd64 (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/amd64 r-base
• r-cran-gbm/arm64 (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/arm64 (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/arm64 r-base
• r-cran-gbm/armel (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/armel (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/armel r-base
• r-cran-gbm/armhf (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/armhf (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/armhf r-base
• r-cran-gbm/i386 (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/i386 (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/i386 r-base
• r-cran-gbm/mips64el (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/mips64el (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/mips64el r-base
• r-cran-gbm/mipsel (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/mipsel (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/mipsel r-base
• r-cran-gbm/ppc64el (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/ppc64el (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/ppc64el r-base
• r-cran-gbm/s390x (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-gbm/s390x (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbm/s390x r-base
• r-cran-gbrd/amd64 (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/amd64 (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/amd64 r-base
• r-cran-gbrd/arm64 (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/arm64 (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/arm64 r-base
• r-cran-gbrd/armel (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/armel (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/armel r-base
• r-cran-gbrd/armhf (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/armhf (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/armhf r-base
• r-cran-gbrd/i386 (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/i386 (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/i386 r-base
• r-cran-gbrd/mips64el (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/mips64el (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/mips64el r-base
• r-cran-gbrd/mipsel (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/mipsel (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/mipsel r-base
• r-cran-gbrd/ppc64el (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/ppc64el (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/ppc64el r-base
• r-cran-gbrd/s390x (0.4-11-1 to 0.4-11-1)
  • Migration status for r-cran-gbrd/s390x (0.4-11-1 to 0.4-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gbrd/s390x r-base
• r-cran-gdtools/amd64 (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/amd64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/amd64 r-base
• r-cran-gdtools/arm64 (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/arm64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/arm64 r-base
• r-cran-gdtools/armel (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/armel (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/armel r-base
• r-cran-gdtools/armhf (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/armhf (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/armhf r-base
• r-cran-gdtools/i386 (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/i386 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/i386 r-base
• r-cran-gdtools/mips64el (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/mips64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/mips64el r-base
• r-cran-gdtools/mipsel (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/mipsel (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/mipsel r-base
• r-cran-gdtools/ppc64el (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/ppc64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/ppc64el r-base
• r-cran-gdtools/s390x (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-gdtools/s390x (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gdtools/s390x r-base
• r-cran-gee/amd64 (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/amd64 (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/amd64 r-base
• r-cran-gee/arm64 (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/arm64 (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/arm64 r-base
• r-cran-gee/armel (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/armel (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/armel r-base
• r-cran-gee/armhf (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/armhf (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/armhf r-base
• r-cran-gee/i386 (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/i386 (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/i386 r-base
• r-cran-gee/mips64el (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/mips64el (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/mips64el r-base
• r-cran-gee/mipsel (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/mipsel (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/mipsel r-base
• r-cran-gee/ppc64el (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/ppc64el (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/ppc64el r-base
• r-cran-gee/s390x (4.13-20-1 to 4.13-20-1)
  • Migration status for r-cran-gee/s390x (4.13-20-1 to 4.13-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gee/s390x r-base
• r-cran-geepack/amd64 (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/amd64 (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/amd64 r-base
• r-cran-geepack/arm64 (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/arm64 (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/arm64 r-base
• r-cran-geepack/armel (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/armel (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/armel r-base
• r-cran-geepack/armhf (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/armhf (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/armhf r-base
• r-cran-geepack/i386 (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/i386 (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/i386 r-base
• r-cran-geepack/mips64el (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/mips64el (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/mips64el r-base
• r-cran-geepack/mipsel (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/mipsel (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/mipsel r-base
• r-cran-geepack/ppc64el (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/ppc64el (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/ppc64el r-base
• r-cran-geepack/s390x (1.3-1-1 to 1.3-1-1)
  • Migration status for r-cran-geepack/s390x (1.3-1-1 to 1.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geepack/s390x r-base
• r-cran-genabel/amd64 (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/amd64 (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/amd64 r-base
• r-cran-genabel/arm64 (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/arm64 (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/arm64 r-base
• r-cran-genabel/armel (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/armel (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/armel r-base
• r-cran-genabel/armhf (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/armhf (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/armhf r-base
• r-cran-genabel/i386 (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/i386 (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/i386 r-base
• r-cran-genabel/mips64el (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/mips64el (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/mips64el r-base
• r-cran-genabel/mipsel (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/mipsel (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/mipsel r-base
• r-cran-genabel/ppc64el (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/ppc64el (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/ppc64el r-base
• r-cran-genabel/s390x (1.8-0-3 to 1.8-0-3)
  • Migration status for r-cran-genabel/s390x (1.8-0-3 to 1.8-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel/s390x r-base
• r-cran-geometry/amd64 (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/amd64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/amd64 r-base
• r-cran-geometry/arm64 (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/arm64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/arm64 r-base
• r-cran-geometry/armel (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/armel (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/armel r-base
• r-cran-geometry/armhf (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/armhf (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/armhf r-base
• r-cran-geometry/i386 (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/i386 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/i386 r-base
• r-cran-geometry/mips64el (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/mips64el (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/mips64el r-base
• r-cran-geometry/mipsel (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/mipsel (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/mipsel r-base
• r-cran-geometry/ppc64el (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/ppc64el (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/ppc64el r-base
• r-cran-geometry/s390x (0.4.5-1 to 0.4.5-1)
  • Migration status for r-cran-geometry/s390x (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geometry/s390x r-base
• r-cran-geosphere/amd64 (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/amd64 (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/amd64 r-base
• r-cran-geosphere/arm64 (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/arm64 (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/arm64 r-base
• r-cran-geosphere/armel (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/armel (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/armel r-base
• r-cran-geosphere/armhf (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/armhf (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/armhf r-base
• r-cran-geosphere/i386 (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/i386 (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/i386 r-base
• r-cran-geosphere/mips64el (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/mips64el (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/mips64el r-base
• r-cran-geosphere/mipsel (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/mipsel (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/mipsel r-base
• r-cran-geosphere/ppc64el (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/ppc64el (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/ppc64el r-base
• r-cran-geosphere/s390x (1.5-10-1 to 1.5-10-1)
  • Migration status for r-cran-geosphere/s390x (1.5-10-1 to 1.5-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-geosphere/s390x r-base
• r-cran-ggforce/amd64 (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/amd64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/amd64 r-base
• r-cran-ggforce/arm64 (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/arm64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/arm64 r-base
• r-cran-ggforce/armel (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/armel (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/armel r-base
• r-cran-ggforce/armhf (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/armhf (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/armhf r-base
• r-cran-ggforce/i386 (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/i386 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/i386 r-base
• r-cran-ggforce/mips64el (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/mips64el (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/mips64el r-base
• r-cran-ggforce/mipsel (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/mipsel (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/mipsel r-base
• r-cran-ggforce/ppc64el (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/ppc64el (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/ppc64el r-base
• r-cran-ggforce/s390x (0.3.1-2 to 0.3.1-2)
  • Migration status for r-cran-ggforce/s390x (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggforce/s390x r-base
• r-cran-ggrepel/amd64 (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/amd64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/amd64 r-base
• r-cran-ggrepel/arm64 (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/arm64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/arm64 r-base
• r-cran-ggrepel/armel (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/armel (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/armel r-base
• r-cran-ggrepel/armhf (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/armhf (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/armhf r-base
• r-cran-ggrepel/i386 (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/i386 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/i386 r-base
• r-cran-ggrepel/mips64el (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/mips64el (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/mips64el r-base
• r-cran-ggrepel/mipsel (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/mipsel (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/mipsel r-base
• r-cran-ggrepel/ppc64el (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/ppc64el (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/ppc64el r-base
• r-cran-ggrepel/s390x (0.8.2-1 to 0.8.2-1)
  • Migration status for r-cran-ggrepel/s390x (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggrepel/s390x r-base
• r-cran-git2r/amd64 (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/amd64 (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/amd64 r-base
• r-cran-git2r/arm64 (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/arm64 (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/arm64 r-base
• r-cran-git2r/armel (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/armel (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/armel r-base
• r-cran-git2r/armhf (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/armhf (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/armhf r-base
• r-cran-git2r/i386 (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/i386 (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/i386 r-base
• r-cran-git2r/mips64el (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/mips64el (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/mips64el r-base
• r-cran-git2r/mipsel (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/mipsel (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/mipsel r-base
• r-cran-git2r/ppc64el (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/ppc64el (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/ppc64el r-base
• r-cran-git2r/s390x (0.27.1-1 to 0.27.1-1)
  • Migration status for r-cran-git2r/s390x (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-git2r/s390x r-base
• r-cran-glasso/amd64 (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/amd64 (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/amd64 r-base
• r-cran-glasso/arm64 (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/arm64 (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/arm64 r-base
• r-cran-glasso/armel (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/armel (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/armel r-base
• r-cran-glasso/armhf (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/armhf (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/armhf r-base
• r-cran-glasso/i386 (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/i386 (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/i386 r-base
• r-cran-glasso/mips64el (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/mips64el (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/mips64el r-base
• r-cran-glasso/mipsel (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/mipsel (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/mipsel r-base
• r-cran-glasso/ppc64el (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/ppc64el (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/ppc64el r-base
• r-cran-glasso/s390x (1.11-1 to 1.11-1)
  • Migration status for r-cran-glasso/s390x (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glasso/s390x r-base
• r-cran-glmmtmb/amd64 (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/amd64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/amd64 r-base
• r-cran-glmmtmb/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/arm64 r-base
• r-cran-glmmtmb/armel (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/armel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/armel r-base
• r-cran-glmmtmb/armhf (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/armhf (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/armhf r-base
• r-cran-glmmtmb/i386 (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/i386 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/i386 r-base
• r-cran-glmmtmb/mips64el (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/mips64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/mips64el r-base
• r-cran-glmmtmb/mipsel (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/mipsel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/mipsel r-base
• r-cran-glmmtmb/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/ppc64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/ppc64el r-base
• r-cran-glmmtmb/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-glmmtmb/s390x (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmmtmb/s390x r-base
• r-cran-gmm/amd64 (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/amd64 (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/amd64 r-base
• r-cran-gmm/arm64 (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/arm64 (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/arm64 r-base
• r-cran-gmm/armel (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/armel (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/armel r-base
• r-cran-gmm/armhf (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/armhf (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/armhf r-base
• r-cran-gmm/i386 (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/i386 (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/i386 r-base
• r-cran-gmm/mips64el (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/mips64el (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/mips64el r-base
• r-cran-gmm/mipsel (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/mipsel (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/mipsel r-base
• r-cran-gmm/ppc64el (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/ppc64el (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/ppc64el r-base
• r-cran-gmm/s390x (1.6-4-1 to 1.6-4-1)
  • Migration status for r-cran-gmm/s390x (1.6-4-1 to 1.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmm/s390x r-base
• r-cran-gnm/amd64 (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/amd64 (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/amd64 r-base
• r-cran-gnm/arm64 (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/arm64 (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/arm64 r-base
• r-cran-gnm/armel (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/armel (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/armel r-base
• r-cran-gnm/armhf (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/armhf (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/armhf r-base
• r-cran-gnm/i386 (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/i386 (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/i386 r-base
• r-cran-gnm/mips64el (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/mips64el (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/mips64el r-base
• r-cran-gnm/mipsel (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/mipsel (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/mipsel r-base
• r-cran-gnm/ppc64el (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/ppc64el (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/ppc64el r-base
• r-cran-gnm/s390x (1.1-1-2 to 1.1-1-2)
  • Migration status for r-cran-gnm/s390x (1.1-1-2 to 1.1-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gnm/s390x r-base
• r-cran-goftest/amd64 (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/amd64 (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/amd64 r-base
• r-cran-goftest/arm64 (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/arm64 (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/arm64 r-base
• r-cran-goftest/armel (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/armel (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/armel r-base
• r-cran-goftest/armhf (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/armhf (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/armhf r-base
• r-cran-goftest/i386 (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/i386 (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/i386 r-base
• r-cran-goftest/mips64el (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/mips64el (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/mips64el r-base
• r-cran-goftest/mipsel (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/mipsel (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/mipsel r-base
• r-cran-goftest/ppc64el (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/ppc64el (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/ppc64el r-base
• r-cran-goftest/s390x (1.2-2-1 to 1.2-2-1)
  • Migration status for r-cran-goftest/s390x (1.2-2-1 to 1.2-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-goftest/s390x r-base
• r-cran-gower/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/amd64 r-base
• r-cran-gower/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/arm64 r-base
• r-cran-gower/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/armel r-base
• r-cran-gower/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/armhf r-base
• r-cran-gower/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/i386 r-base
• r-cran-gower/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/mips64el r-base
• r-cran-gower/mipsel (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/mipsel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/mipsel r-base
• r-cran-gower/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/ppc64el r-base
• r-cran-gower/s390x (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-gower/s390x (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gower/s390x r-base
• r-cran-graphlayouts/amd64 (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/amd64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/amd64 r-base
• r-cran-graphlayouts/arm64 (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/arm64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/arm64 r-base
• r-cran-graphlayouts/armel (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/armel (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/armel r-base
• r-cran-graphlayouts/armhf (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/armhf (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/armhf r-base
• r-cran-graphlayouts/i386 (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/i386 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/i386 r-base
• r-cran-graphlayouts/mips64el (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/mips64el (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/mips64el r-base
• r-cran-graphlayouts/mipsel (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/mipsel (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/mipsel r-base
• r-cran-graphlayouts/ppc64el (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/ppc64el (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/ppc64el r-base
• r-cran-graphlayouts/s390x (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-graphlayouts/s390x (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-graphlayouts/s390x r-base
• r-cran-gsl/amd64 (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/amd64 (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/amd64 r-base
• r-cran-gsl/arm64 (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/arm64 (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/arm64 r-base
• r-cran-gsl/armel (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/armel (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/armel r-base
• r-cran-gsl/armhf (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/armhf (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/armhf r-base
• r-cran-gsl/i386 (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/i386 (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/i386 r-base
• r-cran-gsl/mips64el (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/mips64el (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/mips64el r-base
• r-cran-gsl/mipsel (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/mipsel (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/mipsel r-base
• r-cran-gsl/ppc64el (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/ppc64el (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/ppc64el r-base
• r-cran-gsl/s390x (2.1-6-1 to 2.1-6-1)
  • Migration status for r-cran-gsl/s390x (2.1-6-1 to 2.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsl/s390x r-base
• r-cran-haplo.stats/amd64 (1.7.9-4 to 1.7.9-4)
  • Migration status for r-cran-haplo.stats/amd64 (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haplo.stats/amd64 r-base
• r-cran-haplo.stats/arm64 (1.7.9-4 to 1.7.9-4)
  • Migration status for r-cran-haplo.stats/arm64 (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haplo.stats/arm64 r-base
• r-cran-haplo.stats/armhf (1.7.9-4 to 1.7.9-4)
  • Migration status for r-cran-haplo.stats/armhf (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haplo.stats/armhf r-base
• r-cran-haplo.stats/i386 (1.7.9-4 to 1.7.9-4)
  • Migration status for r-cran-haplo.stats/i386 (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haplo.stats/i386 r-base
• r-cran-haplo.stats/mips64el (1.7.9-4 to 1.7.9-4)
  • Migration status for r-cran-haplo.stats/mips64el (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haplo.stats/mips64el r-base
• r-cran-haplo.stats/mipsel (1.7.9-4 to 1.7.9-4)
  • Migration status for r-cran-haplo.stats/mipsel (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haplo.stats/mipsel r-base
• r-cran-haplo.stats/ppc64el (1.7.9-4 to 1.7.9-4)
  • Migration status for r-cran-haplo.stats/ppc64el (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haplo.stats/ppc64el r-base
• r-cran-haplo.stats/s390x (1.7.9-4 to 1.7.9-4)
  • Migration status for r-cran-haplo.stats/s390x (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haplo.stats/s390x r-base
• r-cran-haven/amd64 (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/amd64 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/amd64 r-base
• r-cran-haven/arm64 (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/arm64 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/arm64 r-base
• r-cran-haven/armel (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/armel (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/armel r-base
• r-cran-haven/armhf (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/armhf (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/armhf r-base
• r-cran-haven/i386 (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/i386 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/i386 r-base
• r-cran-haven/mips64el (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/mips64el (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/mips64el r-base
• r-cran-haven/mipsel (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/mipsel (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/mipsel r-base
• r-cran-haven/ppc64el (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/ppc64el (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/ppc64el r-base
• r-cran-haven/s390x (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-haven/s390x (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-haven/s390x r-base
• r-cran-hdf5/amd64 (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/amd64 (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/amd64 r-base
• r-cran-hdf5/arm64 (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/arm64 (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/arm64 r-base
• r-cran-hdf5/armel (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/armel (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/armel r-base
• r-cran-hdf5/armhf (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/armhf (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/armhf r-base
• r-cran-hdf5/i386 (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/i386 (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/i386 r-base
• r-cran-hdf5/mips64el (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/mips64el (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/mips64el r-base
• r-cran-hdf5/mipsel (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/mipsel (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/mipsel r-base
• r-cran-hdf5/ppc64el (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/ppc64el (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/ppc64el r-base
• r-cran-hdf5/s390x (1.6.10-4.1 to 1.6.10-4.1)
  • Migration status for r-cran-hdf5/s390x (1.6.10-4.1 to 1.6.10-4.1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hdf5/s390x r-base
• r-cran-hexbin/amd64 (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/amd64 (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/amd64 r-base
• r-cran-hexbin/arm64 (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/arm64 (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/arm64 r-base
• r-cran-hexbin/armel (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/armel (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/armel r-base
• r-cran-hexbin/armhf (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/armhf (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/armhf r-base
• r-cran-hexbin/i386 (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/i386 (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/i386 r-base
• r-cran-hexbin/mips64el (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/mips64el (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/mips64el r-base
• r-cran-hexbin/mipsel (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/mipsel (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/mipsel r-base
• r-cran-hexbin/ppc64el (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/ppc64el (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/ppc64el r-base
• r-cran-hexbin/s390x (1.28.1-1 to 1.28.1-1)
  • Migration status for r-cran-hexbin/s390x (1.28.1-1 to 1.28.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hexbin/s390x r-base
• r-cran-huge/amd64 (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/amd64 (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/amd64 r-base
• r-cran-huge/arm64 (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/arm64 (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/arm64 r-base
• r-cran-huge/armel (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/armel (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/armel r-base
• r-cran-huge/armhf (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/armhf (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/armhf r-base
• r-cran-huge/i386 (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/i386 (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/i386 r-base
• r-cran-huge/mips64el (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/mips64el (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/mips64el r-base
• r-cran-huge/mipsel (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/mipsel (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/mipsel r-base
• r-cran-huge/ppc64el (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/ppc64el (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/ppc64el r-base
• r-cran-huge/s390x (1.3.4.1-1 to 1.3.4.1-1)
  • Migration status for r-cran-huge/s390x (1.3.4.1-1 to 1.3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-huge/s390x r-base
• r-cran-igraph/amd64 (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/amd64 (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/amd64 r-base
• r-cran-igraph/arm64 (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/arm64 (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/arm64 r-base
• r-cran-igraph/armel (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/armel (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/armel r-base
• r-cran-igraph/armhf (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/armhf (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/armhf r-base
• r-cran-igraph/i386 (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/i386 (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/i386 r-base
• r-cran-igraph/mips64el (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/mips64el (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/mips64el r-base
• r-cran-igraph/mipsel (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/mipsel (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/mipsel r-base
• r-cran-igraph/ppc64el (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/ppc64el (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/ppc64el r-base
• r-cran-igraph/s390x (1.2.5-1 to 1.2.5-1)
  • Migration status for r-cran-igraph/s390x (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-igraph/s390x r-base
• r-cran-int64/amd64 (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/amd64 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/amd64 r-base
• r-cran-int64/arm64 (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/arm64 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/arm64 r-base
• r-cran-int64/armel (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/armel (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/armel r-base
• r-cran-int64/armhf (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/armhf (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/armhf r-base
• r-cran-int64/i386 (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/i386 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/i386 r-base
• r-cran-int64/mips64el (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/mips64el (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/mips64el r-base
• r-cran-int64/mipsel (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/mipsel (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/mipsel r-base
• r-cran-int64/ppc64el (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/ppc64el (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/ppc64el r-base
• r-cran-int64/s390x (1.1.2-4 to 1.1.2-4)
  • Migration status for r-cran-int64/s390x (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-int64/s390x r-base
• r-cran-interp/amd64 (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/amd64 (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/amd64 r-base
• r-cran-interp/arm64 (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/arm64 (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/arm64 r-base
• r-cran-interp/armel (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/armel (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/armel r-base
• r-cran-interp/armhf (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/armhf (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/armhf r-base
• r-cran-interp/i386 (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/i386 (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/i386 r-base
• r-cran-interp/mips64el (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/mips64el (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/mips64el r-base
• r-cran-interp/mipsel (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/mipsel (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/mipsel r-base
• r-cran-interp/ppc64el (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/ppc64el (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/ppc64el r-base
• r-cran-interp/s390x (1.0-33-1 to 1.0-33-1)
  • Migration status for r-cran-interp/s390x (1.0-33-1 to 1.0-33-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-interp/s390x r-base
• r-cran-intervals/amd64 (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/amd64 (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/amd64 r-base
• r-cran-intervals/arm64 (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/arm64 (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/arm64 r-base
• r-cran-intervals/armel (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/armel (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/armel r-base
• r-cran-intervals/armhf (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/armhf (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/armhf r-base
• r-cran-intervals/i386 (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/i386 (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/i386 r-base
• r-cran-intervals/mips64el (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/mips64el (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/mips64el r-base
• r-cran-intervals/mipsel (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/mipsel (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/mipsel r-base
• r-cran-intervals/ppc64el (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/ppc64el (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/ppc64el r-base
• r-cran-intervals/s390x (0.15.2-1 to 0.15.2-1)
  • Migration status for r-cran-intervals/s390x (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-intervals/s390x r-base
• r-cran-ipred/amd64 (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/amd64 (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/amd64 r-base
• r-cran-ipred/arm64 (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/arm64 (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/arm64 r-base
• r-cran-ipred/armel (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/armel (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/armel r-base
• r-cran-ipred/armhf (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/armhf (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/armhf r-base
• r-cran-ipred/i386 (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/i386 (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/i386 r-base
• r-cran-ipred/mips64el (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/mips64el (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/mips64el r-base
• r-cran-ipred/mipsel (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/mipsel (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/mipsel r-base
• r-cran-ipred/ppc64el (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/ppc64el (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/ppc64el r-base
• r-cran-ipred/s390x (0.9-9-1 to 0.9-9-1)
  • Migration status for r-cran-ipred/s390x (0.9-9-1 to 0.9-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ipred/s390x r-base
• r-cran-irace/amd64 (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/amd64 (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/amd64 r-base
• r-cran-irace/arm64 (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/arm64 (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/arm64 r-base
• r-cran-irace/armel (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/armel (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/armel r-base
• r-cran-irace/armhf (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/armhf (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/armhf r-base
• r-cran-irace/i386 (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/i386 (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/i386 r-base
• r-cran-irace/mips64el (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/mips64el (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/mips64el r-base
• r-cran-irace/mipsel (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/mipsel (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/mipsel r-base
• r-cran-irace/ppc64el (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/ppc64el (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/ppc64el r-base
• r-cran-irace/s390x (3.4.1-1 to 3.4.1-1)
  • Migration status for r-cran-irace/s390x (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irace/s390x r-base
• r-cran-irlba/amd64 (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/amd64 (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/amd64 r-base
• r-cran-irlba/arm64 (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/arm64 (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/arm64 r-base
• r-cran-irlba/armel (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/armel (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/armel r-base
• r-cran-irlba/armhf (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/armhf (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/armhf r-base
• r-cran-irlba/i386 (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/i386 (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/i386 r-base
• r-cran-irlba/mips64el (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/mips64el (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/mips64el r-base
• r-cran-irlba/mipsel (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/mipsel (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/mipsel r-base
• r-cran-irlba/ppc64el (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/ppc64el (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/ppc64el r-base
• r-cran-irlba/s390x (2.3.3-1 to 2.3.3-1)
  • Migration status for r-cran-irlba/s390x (2.3.3-1 to 2.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irlba/s390x r-base
• r-cran-iso/amd64 (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/amd64 (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/amd64 r-base
• r-cran-iso/arm64 (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/arm64 (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/arm64 r-base
• r-cran-iso/armel (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/armel (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/armel r-base
• r-cran-iso/armhf (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/armhf (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/armhf r-base
• r-cran-iso/i386 (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/i386 (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/i386 r-base
• r-cran-iso/mips64el (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/mips64el (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/mips64el r-base
• r-cran-iso/mipsel (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/mipsel (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/mipsel r-base
• r-cran-iso/ppc64el (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/ppc64el (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/ppc64el r-base
• r-cran-iso/s390x (0.0-18-1 to 0.0-18-1)
  • Migration status for r-cran-iso/s390x (0.0-18-1 to 0.0-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-iso/s390x r-base
• r-cran-isoband/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/amd64 r-base
• r-cran-isoband/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/arm64 r-base
• r-cran-isoband/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/armel r-base
• r-cran-isoband/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/armhf r-base
• r-cran-isoband/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/i386 r-base
• r-cran-isoband/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/mips64el r-base
• r-cran-isoband/mipsel (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/mipsel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/mipsel r-base
• r-cran-isoband/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/ppc64el r-base
• r-cran-isoband/s390x (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-isoband/s390x (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoband/s390x r-base
• r-cran-jpeg/amd64 (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/amd64 (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/amd64 r-base
• r-cran-jpeg/arm64 (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/arm64 (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/arm64 r-base
• r-cran-jpeg/armel (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/armel (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/armel r-base
• r-cran-jpeg/armhf (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/armhf (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/armhf r-base
• r-cran-jpeg/i386 (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/i386 (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/i386 r-base
• r-cran-jpeg/mips64el (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/mips64el (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/mips64el r-base
• r-cran-jpeg/mipsel (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/mipsel (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/mipsel r-base
• r-cran-jpeg/ppc64el (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/ppc64el (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/ppc64el r-base
• r-cran-jpeg/s390x (0.1-8.1-1 to 0.1-8.1-1)
  • Migration status for r-cran-jpeg/s390x (0.1-8.1-1 to 0.1-8.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jpeg/s390x r-base
• r-cran-jsonlite/amd64 (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/amd64 (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/amd64 r-base
• r-cran-jsonlite/arm64 (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/arm64 (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/arm64 r-base
• r-cran-jsonlite/armel (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/armel (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/armel r-base
• r-cran-jsonlite/armhf (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/armhf (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/armhf r-base
• r-cran-jsonlite/i386 (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/i386 (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/i386 r-base
• r-cran-jsonlite/mips64el (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/mips64el (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/mips64el r-base
• r-cran-jsonlite/mipsel (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/mipsel (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/mipsel r-base
• r-cran-jsonlite/ppc64el (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/ppc64el (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/ppc64el r-base
• r-cran-jsonlite/s390x (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for r-cran-jsonlite/s390x (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonlite/s390x r-base
• r-cran-kernlab/amd64 (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/amd64 (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/amd64 r-base
• r-cran-kernlab/arm64 (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/arm64 (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/arm64 r-base
• r-cran-kernlab/armel (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/armel (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/armel r-base
• r-cran-kernlab/armhf (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/armhf (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/armhf r-base
• r-cran-kernlab/i386 (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/i386 (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/i386 r-base
• r-cran-kernlab/mips64el (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/mips64el (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/mips64el r-base
• r-cran-kernlab/mipsel (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/mipsel (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/mipsel r-base
• r-cran-kernlab/ppc64el (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/ppc64el (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/ppc64el r-base
• r-cran-kernlab/s390x (0.9-29-1 to 0.9-29-1)
  • Migration status for r-cran-kernlab/s390x (0.9-29-1 to 0.9-29-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kernlab/s390x r-base
• r-cran-km.ci/amd64 (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/amd64 (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/amd64 r-base
• r-cran-km.ci/arm64 (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/arm64 (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/arm64 r-base
• r-cran-km.ci/armel (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/armel (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/armel r-base
• r-cran-km.ci/armhf (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/armhf (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/armhf r-base
• r-cran-km.ci/i386 (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/i386 (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/i386 r-base
• r-cran-km.ci/mips64el (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/mips64el (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/mips64el r-base
• r-cran-km.ci/mipsel (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/mipsel (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/mipsel r-base
• r-cran-km.ci/ppc64el (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/ppc64el (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/ppc64el r-base
• r-cran-km.ci/s390x (0.5-2-2 to 0.5-2-2)
  • Migration status for r-cran-km.ci/s390x (0.5-2-2 to 0.5-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-km.ci/s390x r-base
• r-cran-kmsurv/amd64 (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/amd64 (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/amd64 r-base
• r-cran-kmsurv/arm64 (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/arm64 (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/arm64 r-base
• r-cran-kmsurv/armel (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/armel (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/armel r-base
• r-cran-kmsurv/armhf (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/armhf (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/armhf r-base
• r-cran-kmsurv/i386 (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/i386 (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/i386 r-base
• r-cran-kmsurv/mips64el (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/mips64el (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/mips64el r-base
• r-cran-kmsurv/mipsel (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/mipsel (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/mipsel r-base
• r-cran-kmsurv/ppc64el (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/ppc64el (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/ppc64el r-base
• r-cran-kmsurv/s390x (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/s390x (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kmsurv/s390x r-base
• r-cran-ks/amd64 (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/amd64 (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/amd64 r-base
• r-cran-ks/arm64 (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/arm64 (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/arm64 r-base
• r-cran-ks/armel (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/armel (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/armel r-base
• r-cran-ks/armhf (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/armhf (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/armhf r-base
• r-cran-ks/i386 (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/i386 (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/i386 r-base
• r-cran-ks/mips64el (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/mips64el (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/mips64el r-base
• r-cran-ks/mipsel (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/mipsel (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/mipsel r-base
• r-cran-ks/ppc64el (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/ppc64el (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/ppc64el r-base
• r-cran-ks/s390x (1.11.7-1 to 1.11.7-1)
  • Migration status for r-cran-ks/s390x (1.11.7-1 to 1.11.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ks/s390x r-base
• r-cran-lasso2/amd64 (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/amd64 (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/amd64 r-base
• r-cran-lasso2/arm64 (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/arm64 (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/arm64 r-base
• r-cran-lasso2/armel (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/armel (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/armel r-base
• r-cran-lasso2/armhf (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/armhf (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/armhf r-base
• r-cran-lasso2/i386 (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/i386 (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/i386 r-base
• r-cran-lasso2/mips64el (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/mips64el (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/mips64el r-base
• r-cran-lasso2/mipsel (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/mipsel (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/mipsel r-base
• r-cran-lasso2/ppc64el (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/ppc64el (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/ppc64el r-base
• r-cran-lasso2/s390x (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-lasso2/s390x (1.2-20-1 to 1.2-20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lasso2/s390x r-base
• r-cran-later/amd64 (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/amd64 (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/amd64 r-base
• r-cran-later/arm64 (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/arm64 (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/arm64 r-base
• r-cran-later/armel (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/armel (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/armel r-base
• r-cran-later/armhf (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/armhf (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/armhf r-base
• r-cran-later/i386 (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/i386 (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/i386 r-base
• r-cran-later/mips64el (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/mips64el (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/mips64el r-base
• r-cran-later/mipsel (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/mipsel (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/mipsel r-base
• r-cran-later/ppc64el (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/ppc64el (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/ppc64el r-base
• r-cran-later/s390x (1.0.0+dfsg-2 to 1.0.0+dfsg-2)
  • Migration status for r-cran-later/s390x (1.0.0+dfsg-2 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-later/s390x r-base
• r-cran-lavasearch2/amd64 (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/amd64 (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/amd64 r-base
• r-cran-lavasearch2/arm64 (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/arm64 (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/arm64 r-base
• r-cran-lavasearch2/armel (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/armel (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/armel r-base
• r-cran-lavasearch2/armhf (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/armhf (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/armhf r-base
• r-cran-lavasearch2/i386 (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/i386 (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/i386 r-base
• r-cran-lavasearch2/mips64el (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/mips64el (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/mips64el r-base
• r-cran-lavasearch2/mipsel (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/mipsel (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/mipsel r-base
• r-cran-lavasearch2/ppc64el (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/ppc64el (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/ppc64el r-base
• r-cran-lavasearch2/s390x (1.5.5+dfsg-1 to 1.5.5+dfsg-1)
  • Migration status for r-cran-lavasearch2/s390x (1.5.5+dfsg-1 to 1.5.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavasearch2/s390x r-base
• r-cran-lazyeval/amd64 (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/amd64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/amd64 r-base
• r-cran-lazyeval/arm64 (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/arm64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/arm64 r-base
• r-cran-lazyeval/armel (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/armel (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/armel r-base
• r-cran-lazyeval/armhf (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/armhf (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/armhf r-base
• r-cran-lazyeval/i386 (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/i386 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/i386 r-base
• r-cran-lazyeval/mips64el (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/mips64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/mips64el r-base
• r-cran-lazyeval/mipsel (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/mipsel (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/mipsel r-base
• r-cran-lazyeval/ppc64el (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/ppc64el (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/ppc64el r-base
• r-cran-lazyeval/s390x (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/s390x (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lazyeval/s390x r-base
• r-cran-leaps/amd64 (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/amd64 (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/amd64 r-base
• r-cran-leaps/arm64 (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/arm64 (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/arm64 r-base
• r-cran-leaps/armel (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/armel (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/armel r-base
• r-cran-leaps/armhf (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/armhf (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/armhf r-base
• r-cran-leaps/i386 (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/i386 (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/i386 r-base
• r-cran-leaps/mips64el (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/mips64el (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/mips64el r-base
• r-cran-leaps/mipsel (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/mipsel (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/mipsel r-base
• r-cran-leaps/ppc64el (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/ppc64el (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/ppc64el r-base
• r-cran-leaps/s390x (3.1-1 to 3.1-1)
  • Migration status for r-cran-leaps/s390x (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leaps/s390x r-base
• r-cran-lexrankr/amd64 (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/amd64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/amd64 r-base
• r-cran-lexrankr/arm64 (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/arm64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/arm64 r-base
• r-cran-lexrankr/armel (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/armel (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/armel r-base
• r-cran-lexrankr/armhf (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/armhf (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/armhf r-base
• r-cran-lexrankr/i386 (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/i386 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/i386 r-base
• r-cran-lexrankr/mips64el (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/mips64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/mips64el r-base
• r-cran-lexrankr/mipsel (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/mipsel (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/mipsel r-base
• r-cran-lexrankr/ppc64el (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/ppc64el (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/ppc64el r-base
• r-cran-lexrankr/s390x (0.5.2-1 to 0.5.2-1)
  • Migration status for r-cran-lexrankr/s390x (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lexrankr/s390x r-base
• r-cran-lhs/amd64 (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/amd64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/amd64 r-base
• r-cran-lhs/arm64 (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/arm64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/arm64 r-base
• r-cran-lhs/armel (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/armel (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/armel r-base
• r-cran-lhs/armhf (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/armhf (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/armhf r-base
• r-cran-lhs/i386 (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/i386 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/i386 r-base
• r-cran-lhs/mips64el (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/mips64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/mips64el r-base
• r-cran-lhs/mipsel (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/mipsel (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/mipsel r-base
• r-cran-lhs/ppc64el (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/ppc64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/ppc64el r-base
• r-cran-lhs/s390x (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-lhs/s390x (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lhs/s390x r-base
• r-cran-libcoin/amd64 (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/amd64 (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/amd64 r-base
• r-cran-libcoin/arm64 (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/arm64 (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/arm64 r-base
• r-cran-libcoin/armel (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/armel (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/armel r-base
• r-cran-libcoin/armhf (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/armhf (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/armhf r-base
• r-cran-libcoin/i386 (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/i386 (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/i386 r-base
• r-cran-libcoin/mips64el (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/mips64el (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/mips64el r-base
• r-cran-libcoin/mipsel (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/mipsel (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/mipsel r-base
• r-cran-libcoin/ppc64el (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/ppc64el (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/ppc64el r-base
• r-cran-libcoin/s390x (1.0-5-1 to 1.0-5-1)
  • Migration status for r-cran-libcoin/s390x (1.0-5-1 to 1.0-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-libcoin/s390x r-base
• r-cran-linprog/amd64 (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/amd64 (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/amd64 r-base
• r-cran-linprog/arm64 (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/arm64 (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/arm64 r-base
• r-cran-linprog/armel (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/armel (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/armel r-base
• r-cran-linprog/armhf (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/armhf (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/armhf r-base
• r-cran-linprog/i386 (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/i386 (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/i386 r-base
• r-cran-linprog/mips64el (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/mips64el (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/mips64el r-base
• r-cran-linprog/mipsel (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/mipsel (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/mipsel r-base
• r-cran-linprog/ppc64el (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/ppc64el (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/ppc64el r-base
• r-cran-linprog/s390x (0.9-2-1 to 0.9-2-1)
  • Migration status for r-cran-linprog/s390x (0.9-2-1 to 0.9-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-linprog/s390x r-base
• r-cran-locfit/amd64 (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/amd64 (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/amd64 r-base
• r-cran-locfit/arm64 (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/arm64 (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/arm64 r-base
• r-cran-locfit/armel (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/armel (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/armel r-base
• r-cran-locfit/armhf (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/armhf (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/armhf r-base
• r-cran-locfit/i386 (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/i386 (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/i386 r-base
• r-cran-locfit/mips64el (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/mips64el (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/mips64el r-base
• r-cran-locfit/mipsel (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/mipsel (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/mipsel r-base
• r-cran-locfit/ppc64el (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/ppc64el (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/ppc64el r-base
• r-cran-locfit/s390x (1.5-9.4-2 to 1.5-9.4-2)
  • Migration status for r-cran-locfit/s390x (1.5-9.4-2 to 1.5-9.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-locfit/s390x r-base
• r-cran-logspline/amd64 (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/amd64 (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/amd64 r-base
• r-cran-logspline/arm64 (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/arm64 (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/arm64 r-base
• r-cran-logspline/armel (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/armel (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/armel r-base
• r-cran-logspline/armhf (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/armhf (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/armhf r-base
• r-cran-logspline/i386 (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/i386 (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/i386 r-base
• r-cran-logspline/mips64el (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/mips64el (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/mips64el r-base
• r-cran-logspline/mipsel (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/mipsel (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/mipsel r-base
• r-cran-logspline/ppc64el (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/ppc64el (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/ppc64el r-base
• r-cran-logspline/s390x (2.1.16-1 to 2.1.16-1)
  • Migration status for r-cran-logspline/s390x (2.1.16-1 to 2.1.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logspline/s390x r-base
• r-cran-lpsolve/amd64 (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/amd64 (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/amd64 r-base
• r-cran-lpsolve/arm64 (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/arm64 (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/arm64 r-base
• r-cran-lpsolve/armel (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/armel (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/armel r-base
• r-cran-lpsolve/armhf (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/armhf (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/armhf r-base
• r-cran-lpsolve/i386 (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/i386 (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/i386 r-base
• r-cran-lpsolve/mips64el (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/mips64el (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/mips64el r-base
• r-cran-lpsolve/mipsel (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/mipsel (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/mipsel r-base
• r-cran-lpsolve/ppc64el (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/ppc64el (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/ppc64el r-base
• r-cran-lpsolve/s390x (5.6.15-1 to 5.6.15-1)
  • Migration status for r-cran-lpsolve/s390x (5.6.15-1 to 5.6.15-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lpsolve/s390x r-base
• r-cran-lsei/amd64 (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/amd64 (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/amd64 r-base
• r-cran-lsei/arm64 (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/arm64 (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/arm64 r-base
• r-cran-lsei/armel (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/armel (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/armel r-base
• r-cran-lsei/armhf (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/armhf (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/armhf r-base
• r-cran-lsei/i386 (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/i386 (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/i386 r-base
• r-cran-lsei/mips64el (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/mips64el (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/mips64el r-base
• r-cran-lsei/mipsel (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/mipsel (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/mipsel r-base
• r-cran-lsei/ppc64el (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/ppc64el (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/ppc64el r-base
• r-cran-lsei/s390x (1.2-0.1-1 to 1.2-0.1-1)
  • Migration status for r-cran-lsei/s390x (1.2-0.1-1 to 1.2-0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsei/s390x r-base
• r-cran-lubridate/amd64 (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/amd64 (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/amd64 r-base
• r-cran-lubridate/arm64 (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/arm64 (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/arm64 r-base
• r-cran-lubridate/armel (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/armel (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/armel r-base
• r-cran-lubridate/armhf (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/armhf (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/armhf r-base
• r-cran-lubridate/i386 (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/i386 (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/i386 r-base
• r-cran-lubridate/mips64el (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/mips64el (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/mips64el r-base
• r-cran-lubridate/mipsel (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/mipsel (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/mipsel r-base
• r-cran-lubridate/ppc64el (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/ppc64el (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/ppc64el r-base
• r-cran-lubridate/s390x (1.7.8-1 to 1.7.8-1)
  • Migration status for r-cran-lubridate/s390x (1.7.8-1 to 1.7.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lubridate/s390x r-base
• r-cran-luminescence/amd64 (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/amd64 (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/amd64 r-base
• r-cran-luminescence/arm64 (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/arm64 (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/arm64 r-base
• r-cran-luminescence/armel (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/armel (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/armel r-base
• r-cran-luminescence/armhf (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/armhf (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/armhf r-base
• r-cran-luminescence/i386 (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/i386 (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/i386 r-base
• r-cran-luminescence/mips64el (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/mips64el (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/mips64el r-base
• r-cran-luminescence/mipsel (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/mipsel (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/mipsel r-base
• r-cran-luminescence/ppc64el (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/ppc64el (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/ppc64el r-base
• r-cran-luminescence/s390x (0.9.7-1 to 0.9.7-1)
  • Migration status for r-cran-luminescence/s390x (0.9.7-1 to 0.9.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-luminescence/s390x r-base
• r-cran-magick/amd64 (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/amd64 (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/amd64 r-base
• r-cran-magick/arm64 (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/arm64 (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/arm64 r-base
• r-cran-magick/armel (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/armel (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/armel r-base
• r-cran-magick/armhf (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/armhf (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/armhf r-base
• r-cran-magick/i386 (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/i386 (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/i386 r-base
• r-cran-magick/mips64el (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/mips64el (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/mips64el r-base
• r-cran-magick/mipsel (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/mipsel (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/mipsel r-base
• r-cran-magick/ppc64el (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/ppc64el (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/ppc64el r-base
• r-cran-magick/s390x (2.3+dfsg-1 to 2.3+dfsg-1)
  • Migration status for r-cran-magick/s390x (2.3+dfsg-1 to 2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magick/s390x r-base
• r-cran-maldiquant/amd64 (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/amd64 (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/amd64 r-base
• r-cran-maldiquant/arm64 (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/arm64 (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/arm64 r-base
• r-cran-maldiquant/armel (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/armel (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/armel r-base
• r-cran-maldiquant/armhf (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/armhf (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/armhf r-base
• r-cran-maldiquant/i386 (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/i386 (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/i386 r-base
• r-cran-maldiquant/mips64el (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/mips64el (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/mips64el r-base
• r-cran-maldiquant/mipsel (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/mipsel (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/mipsel r-base
• r-cran-maldiquant/ppc64el (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/ppc64el (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/ppc64el r-base
• r-cran-maldiquant/s390x (1.19.3-1 to 1.19.3-1)
  • Migration status for r-cran-maldiquant/s390x (1.19.3-1 to 1.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquant/s390x r-base
• r-cran-mapdata/amd64 (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/amd64 (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/amd64 r-base
• r-cran-mapdata/arm64 (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/arm64 (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/arm64 r-base
• r-cran-mapdata/armel (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/armel (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/armel r-base
• r-cran-mapdata/armhf (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/armhf (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/armhf r-base
• r-cran-mapdata/i386 (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/i386 (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/i386 r-base
• r-cran-mapdata/mips64el (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/mips64el (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/mips64el r-base
• r-cran-mapdata/mipsel (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/mipsel (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/mipsel r-base
• r-cran-mapdata/ppc64el (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/ppc64el (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/ppc64el r-base
• r-cran-mapdata/s390x (2.3.0-2 to 2.3.0-2)
  • Migration status for r-cran-mapdata/s390x (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapdata/s390x r-base
• r-cran-mapproj/amd64 (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/amd64 (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/amd64 r-base
• r-cran-mapproj/arm64 (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/arm64 (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/arm64 r-base
• r-cran-mapproj/armel (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/armel (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/armel r-base
• r-cran-mapproj/armhf (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/armhf (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/armhf r-base
• r-cran-mapproj/i386 (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/i386 (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/i386 r-base
• r-cran-mapproj/mips64el (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/mips64el (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/mips64el r-base
• r-cran-mapproj/mipsel (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/mipsel (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/mipsel r-base
• r-cran-mapproj/ppc64el (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/ppc64el (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/ppc64el r-base
• r-cran-mapproj/s390x (1.2.7-1 to 1.2.7-1)
  • Migration status for r-cran-mapproj/s390x (1.2.7-1 to 1.2.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mapproj/s390x r-base
• r-cran-maps/amd64 (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/amd64 (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/amd64 r-base
• r-cran-maps/arm64 (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/arm64 (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/arm64 r-base
• r-cran-maps/armel (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/armel (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/armel r-base
• r-cran-maps/armhf (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/armhf (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/armhf r-base
• r-cran-maps/i386 (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/i386 (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/i386 r-base
• r-cran-maps/mips64el (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/mips64el (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/mips64el r-base
• r-cran-maps/mipsel (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/mipsel (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/mipsel r-base
• r-cran-maps/ppc64el (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/ppc64el (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/ppc64el r-base
• r-cran-maps/s390x (3.3.0-2 to 3.3.0-2)
  • Migration status for r-cran-maps/s390x (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maps/s390x r-base
• r-cran-markdown/amd64 (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/amd64 (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/amd64 r-base
• r-cran-markdown/arm64 (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/arm64 (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/arm64 r-base
• r-cran-markdown/armel (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/armel (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/armel r-base
• r-cran-markdown/armhf (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/armhf (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/armhf r-base
• r-cran-markdown/i386 (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/i386 (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/i386 r-base
• r-cran-markdown/mips64el (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/mips64el (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/mips64el r-base
• r-cran-markdown/mipsel (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/mipsel (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/mipsel r-base
• r-cran-markdown/ppc64el (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/ppc64el (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/ppc64el r-base
• r-cran-markdown/s390x (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-markdown/s390x (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-markdown/s390x r-base
• r-cran-mass/amd64 (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/amd64 (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/amd64 r-base
• r-cran-mass/arm64 (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/arm64 (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/arm64 r-base
• r-cran-mass/armel (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/armel (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/armel r-base
• r-cran-mass/armhf (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/armhf (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/armhf r-base
• r-cran-mass/i386 (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/i386 (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/i386 r-base
• r-cran-mass/mips64el (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/mips64el (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/mips64el r-base
• r-cran-mass/mipsel (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/mipsel (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/mipsel r-base
• r-cran-mass/ppc64el (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/ppc64el (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/ppc64el r-base
• r-cran-mass/s390x (7.3-51.6-1 to 7.3-51.6-1)
  • Migration status for r-cran-mass/s390x (7.3-51.6-1 to 7.3-51.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mass/s390x r-base
• r-cran-matching/amd64 (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/amd64 (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/amd64 r-base
• r-cran-matching/arm64 (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/arm64 (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/arm64 r-base
• r-cran-matching/armel (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/armel (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/armel r-base
• r-cran-matching/armhf (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/armhf (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/armhf r-base
• r-cran-matching/i386 (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/i386 (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/i386 r-base
• r-cran-matching/mips64el (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/mips64el (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/mips64el r-base
• r-cran-matching/mipsel (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/mipsel (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/mipsel r-base
• r-cran-matching/ppc64el (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/ppc64el (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/ppc64el r-base
• r-cran-matching/s390x (4.9-7-1 to 4.9-7-1)
  • Migration status for r-cran-matching/s390x (4.9-7-1 to 4.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matching/s390x r-base
• r-cran-matrixstats/amd64 (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/amd64 (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/amd64 r-base
• r-cran-matrixstats/arm64 (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/arm64 (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/arm64 r-base
• r-cran-matrixstats/armel (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/armel (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/armel r-base
• r-cran-matrixstats/armhf (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/armhf (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/armhf r-base
• r-cran-matrixstats/i386 (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/i386 (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/i386 r-base
• r-cran-matrixstats/mips64el (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/mips64el (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/mips64el r-base
• r-cran-matrixstats/mipsel (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/mipsel (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/mipsel r-base
• r-cran-matrixstats/ppc64el (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/ppc64el (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/ppc64el r-base
• r-cran-matrixstats/s390x (0.56.0-1 to 0.56.0-1)
  • Migration status for r-cran-matrixstats/s390x (0.56.0-1 to 0.56.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixstats/s390x r-base
• r-cran-maxstat/amd64 (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/amd64 (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/amd64 r-base
• r-cran-maxstat/arm64 (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/arm64 (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/arm64 r-base
• r-cran-maxstat/armel (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/armel (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/armel r-base
• r-cran-maxstat/armhf (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/armhf (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/armhf r-base
• r-cran-maxstat/i386 (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/i386 (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/i386 r-base
• r-cran-maxstat/mips64el (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/mips64el (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/mips64el r-base
• r-cran-maxstat/mipsel (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/mipsel (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/mipsel r-base
• r-cran-maxstat/ppc64el (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/ppc64el (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/ppc64el r-base
• r-cran-maxstat/s390x (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/s390x (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxstat/s390x r-base
• r-cran-mclust/amd64 (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/amd64 (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/amd64 r-base
• r-cran-mclust/arm64 (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/arm64 (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/arm64 r-base
• r-cran-mclust/armel (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/armel (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/armel r-base
• r-cran-mclust/armhf (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/armhf (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/armhf r-base
• r-cran-mclust/i386 (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/i386 (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/i386 r-base
• r-cran-mclust/mips64el (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/mips64el (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/mips64el r-base
• r-cran-mclust/mipsel (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/mipsel (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/mipsel r-base
• r-cran-mclust/ppc64el (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/ppc64el (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/ppc64el r-base
• r-cran-mclust/s390x (5.4.6-1 to 5.4.6-1)
  • Migration status for r-cran-mclust/s390x (5.4.6-1 to 5.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mclust/s390x r-base
• r-cran-mcmc/amd64 (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/amd64 (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/amd64 r-base
• r-cran-mcmc/arm64 (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/arm64 (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/arm64 r-base
• r-cran-mcmc/armel (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/armel (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/armel r-base
• r-cran-mcmc/armhf (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/armhf (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/armhf r-base
• r-cran-mcmc/i386 (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/i386 (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/i386 r-base
• r-cran-mcmc/mips64el (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/mips64el (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/mips64el r-base
• r-cran-mcmc/mipsel (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/mipsel (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/mipsel r-base
• r-cran-mcmc/ppc64el (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/ppc64el (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/ppc64el r-base
• r-cran-mcmc/s390x (0.9-7-1 to 0.9-7-1)
  • Migration status for r-cran-mcmc/s390x (0.9-7-1 to 0.9-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmc/s390x r-base
• r-cran-mcmcpack/amd64 (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/amd64 (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/amd64 r-base
• r-cran-mcmcpack/arm64 (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/arm64 (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/arm64 r-base
• r-cran-mcmcpack/armel (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/armel (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/armel r-base
• r-cran-mcmcpack/armhf (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/armhf (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/armhf r-base
• r-cran-mcmcpack/i386 (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/i386 (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/i386 r-base
• r-cran-mcmcpack/mips64el (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/mips64el (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/mips64el r-base
• r-cran-mcmcpack/mipsel (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/mipsel (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/mipsel r-base
• r-cran-mcmcpack/ppc64el (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/ppc64el (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/ppc64el r-base
• r-cran-mcmcpack/s390x (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-mcmcpack/s390x (1.4-7-1 to 1.4-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mcmcpack/s390x r-base
• r-cran-mda/amd64 (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/amd64 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/amd64 r-base
• r-cran-mda/arm64 (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/arm64 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/arm64 r-base
• r-cran-mda/armel (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/armel (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/armel r-base
• r-cran-mda/armhf (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/armhf (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/armhf r-base
• r-cran-mda/i386 (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/i386 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/i386 r-base
• r-cran-mda/mips64el (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/mips64el (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/mips64el r-base
• r-cran-mda/mipsel (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/mipsel (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/mipsel r-base
• r-cran-mda/ppc64el (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/ppc64el (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/ppc64el r-base
• r-cran-mda/s390x (0.5-1 to 0.5-1)
  • Migration status for r-cran-mda/s390x (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mda/s390x r-base
• r-cran-medadherence/amd64 (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/amd64 (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/amd64 r-base
• r-cran-medadherence/arm64 (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/arm64 (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/arm64 r-base
• r-cran-medadherence/armel (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/armel (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/armel r-base
• r-cran-medadherence/armhf (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/armhf (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/armhf r-base
• r-cran-medadherence/i386 (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/i386 (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/i386 r-base
• r-cran-medadherence/mips64el (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/mips64el (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/mips64el r-base
• r-cran-medadherence/mipsel (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/mipsel (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/mipsel r-base
• r-cran-medadherence/ppc64el (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/ppc64el (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/ppc64el r-base
• r-cran-medadherence/s390x (1.03-5 to 1.03-5)
  • Migration status for r-cran-medadherence/s390x (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-medadherence/s390x r-base
• r-cran-metamix/amd64 (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/amd64 (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/amd64 r-base
• r-cran-metamix/arm64 (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/arm64 (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/arm64 r-base
• r-cran-metamix/armel (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/armel (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/armel r-base
• r-cran-metamix/armhf (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/armhf (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/armhf r-base
• r-cran-metamix/i386 (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/i386 (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/i386 r-base
• r-cran-metamix/mips64el (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/mips64el (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/mips64el r-base
• r-cran-metamix/mipsel (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/mipsel (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/mipsel r-base
• r-cran-metamix/ppc64el (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/ppc64el (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/ppc64el r-base
• r-cran-metamix/s390x (0.3-2 to 0.3-2)
  • Migration status for r-cran-metamix/s390x (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metamix/s390x r-base
• r-cran-mets/amd64 (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/amd64 (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/amd64 r-base
• r-cran-mets/arm64 (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/arm64 (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/arm64 r-base
• r-cran-mets/armel (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/armel (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/armel r-base
• r-cran-mets/armhf (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/armhf (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/armhf r-base
• r-cran-mets/i386 (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/i386 (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/i386 r-base
• r-cran-mets/mips64el (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/mips64el (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/mips64el r-base
• r-cran-mets/mipsel (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/mipsel (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/mipsel r-base
• r-cran-mets/ppc64el (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/ppc64el (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/ppc64el r-base
• r-cran-mets/s390x (1.2.7.1-1 to 1.2.7.1-1)
  • Migration status for r-cran-mets/s390x (1.2.7.1-1 to 1.2.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mets/s390x r-base
• r-cran-mime/amd64 (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/amd64 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/amd64 r-base
• r-cran-mime/arm64 (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/arm64 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/arm64 r-base
• r-cran-mime/armel (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/armel (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/armel r-base
• r-cran-mime/armhf (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/armhf (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/armhf r-base
• r-cran-mime/i386 (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/i386 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/i386 r-base
• r-cran-mime/mips64el (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/mips64el (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/mips64el r-base
• r-cran-mime/mipsel (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/mipsel (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/mipsel r-base
• r-cran-mime/ppc64el (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/ppc64el (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/ppc64el r-base
• r-cran-mime/s390x (0.9-1 to 0.9-1)
  • Migration status for r-cran-mime/s390x (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mime/s390x r-base
• r-cran-minerva/amd64 (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/amd64 (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/amd64 r-base
• r-cran-minerva/arm64 (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/arm64 (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/arm64 r-base
• r-cran-minerva/armel (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/armel (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/armel r-base
• r-cran-minerva/armhf (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/armhf (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/armhf r-base
• r-cran-minerva/i386 (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/i386 (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/i386 r-base
• r-cran-minerva/mips64el (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/mips64el (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/mips64el r-base
• r-cran-minerva/mipsel (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/mipsel (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/mipsel r-base
• r-cran-minerva/ppc64el (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/ppc64el (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/ppc64el r-base
• r-cran-minerva/s390x (1.5.8-2 to 1.5.8-2)
  • Migration status for r-cran-minerva/s390x (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minerva/s390x r-base
• r-cran-minpack.lm/amd64 (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/amd64 (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/amd64 r-base
• r-cran-minpack.lm/arm64 (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/arm64 (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/arm64 r-base
• r-cran-minpack.lm/armel (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/armel (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/armel r-base
• r-cran-minpack.lm/armhf (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/armhf (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/armhf r-base
• r-cran-minpack.lm/i386 (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/i386 (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/i386 r-base
• r-cran-minpack.lm/mips64el (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/mips64el (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/mips64el r-base
• r-cran-minpack.lm/mipsel (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/mipsel (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/mipsel r-base
• r-cran-minpack.lm/ppc64el (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/ppc64el (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/ppc64el r-base
• r-cran-minpack.lm/s390x (1.2-1-4 to 1.2-1-4)
  • Migration status for r-cran-minpack.lm/s390x (1.2-1-4 to 1.2-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minpack.lm/s390x r-base
• r-cran-minqa/amd64 (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/amd64 (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/amd64 r-base
• r-cran-minqa/arm64 (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/arm64 (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/arm64 r-base
• r-cran-minqa/armel (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/armel (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/armel r-base
• r-cran-minqa/armhf (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/armhf (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/armhf r-base
• r-cran-minqa/i386 (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/i386 (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/i386 r-base
• r-cran-minqa/mips64el (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/mips64el (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/mips64el r-base
• r-cran-minqa/mipsel (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/mipsel (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/mipsel r-base
• r-cran-minqa/ppc64el (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/ppc64el (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/ppc64el r-base
• r-cran-minqa/s390x (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-minqa/s390x (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-minqa/s390x r-base
• r-cran-mixtools/amd64 (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/amd64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/amd64 r-base
• r-cran-mixtools/arm64 (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/arm64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/arm64 r-base
• r-cran-mixtools/armel (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/armel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/armel r-base
• r-cran-mixtools/armhf (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/armhf (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/armhf r-base
• r-cran-mixtools/i386 (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/i386 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/i386 r-base
• r-cran-mixtools/mips64el (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/mips64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/mips64el r-base
• r-cran-mixtools/mipsel (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/mipsel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/mipsel r-base
• r-cran-mixtools/ppc64el (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/ppc64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/ppc64el r-base
• r-cran-mixtools/s390x (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-mixtools/s390x (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mixtools/s390x r-base
• r-cran-mlbench/amd64 (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/amd64 (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/amd64 r-base
• r-cran-mlbench/arm64 (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/arm64 (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/arm64 r-base
• r-cran-mlbench/armel (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/armel (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/armel r-base
• r-cran-mlbench/armhf (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/armhf (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/armhf r-base
• r-cran-mlbench/i386 (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/i386 (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/i386 r-base
• r-cran-mlbench/mips64el (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/mips64el (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/mips64el r-base
• r-cran-mlbench/mipsel (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/mipsel (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/mipsel r-base
• r-cran-mlbench/ppc64el (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/ppc64el (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/ppc64el r-base
• r-cran-mlbench/s390x (2.1-1-3 to 2.1-1-3)
  • Migration status for r-cran-mlbench/s390x (2.1-1-3 to 2.1-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlbench/s390x r-base
• r-cran-mlr/amd64 (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/amd64 (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/amd64 r-base
• r-cran-mlr/arm64 (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/arm64 (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/arm64 r-base
• r-cran-mlr/armel (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/armel (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/armel r-base
• r-cran-mlr/armhf (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/armhf (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/armhf r-base
• r-cran-mlr/i386 (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/i386 (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/i386 r-base
• r-cran-mlr/mips64el (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/mips64el (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/mips64el r-base
• r-cran-mlr/mipsel (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/mipsel (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/mipsel r-base
• r-cran-mlr/ppc64el (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/ppc64el (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/ppc64el r-base
• r-cran-mlr/s390x (2.17.1+dfsg-1 to 2.17.1+dfsg-1)
  • Migration status for r-cran-mlr/s390x (2.17.1+dfsg-1 to 2.17.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlr/s390x r-base
• r-cran-mnp/amd64 (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/amd64 (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/amd64 r-base
• r-cran-mnp/arm64 (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/arm64 (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/arm64 r-base
• r-cran-mnp/armel (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/armel (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/armel r-base
• r-cran-mnp/armhf (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/armhf (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/armhf r-base
• r-cran-mnp/i386 (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/i386 (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/i386 r-base
• r-cran-mnp/mips64el (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/mips64el (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/mips64el r-base
• r-cran-mnp/mipsel (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/mipsel (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/mipsel r-base
• r-cran-mnp/ppc64el (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/ppc64el (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/ppc64el r-base
• r-cran-mnp/s390x (3.1-0-2 to 3.1-0-2)
  • Migration status for r-cran-mnp/s390x (3.1-0-2 to 3.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mnp/s390x r-base
• r-cran-modelmetrics/amd64 (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/amd64 (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/amd64 r-base
• r-cran-modelmetrics/arm64 (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/arm64 (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/arm64 r-base
• r-cran-modelmetrics/armel (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/armel (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/armel r-base
• r-cran-modelmetrics/armhf (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/armhf (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/armhf r-base
• r-cran-modelmetrics/i386 (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/i386 (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/i386 r-base
• r-cran-modelmetrics/mips64el (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/mips64el (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/mips64el r-base
• r-cran-modelmetrics/mipsel (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/mipsel (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/mipsel r-base
• r-cran-modelmetrics/ppc64el (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/ppc64el (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/ppc64el r-base
• r-cran-modelmetrics/s390x (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/s390x (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelmetrics/s390x r-base
• r-cran-msm/amd64 (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/amd64 (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/amd64 r-base
• r-cran-msm/arm64 (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/arm64 (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/arm64 r-base
• r-cran-msm/armel (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/armel (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/armel r-base
• r-cran-msm/armhf (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/armhf (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/armhf r-base
• r-cran-msm/i386 (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/i386 (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/i386 r-base
• r-cran-msm/mips64el (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/mips64el (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/mips64el r-base
• r-cran-msm/mipsel (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/mipsel (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/mipsel r-base
• r-cran-msm/ppc64el (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/ppc64el (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/ppc64el r-base
• r-cran-msm/s390x (1.6.8-1 to 1.6.8-1)
  • Migration status for r-cran-msm/s390x (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-msm/s390x r-base
• r-cran-multicool/amd64 (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/amd64 (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/amd64 r-base
• r-cran-multicool/arm64 (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/arm64 (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/arm64 r-base
• r-cran-multicool/armel (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/armel (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/armel r-base
• r-cran-multicool/armhf (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/armhf (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/armhf r-base
• r-cran-multicool/i386 (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/i386 (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/i386 r-base
• r-cran-multicool/mips64el (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/mips64el (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/mips64el r-base
• r-cran-multicool/mipsel (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/mipsel (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/mipsel r-base
• r-cran-multicool/ppc64el (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/ppc64el (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/ppc64el r-base
• r-cran-multicool/s390x (0.1-11-2 to 0.1-11-2)
  • Migration status for r-cran-multicool/s390x (0.1-11-2 to 0.1-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicool/s390x r-base
• r-cran-multicore/amd64 (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/amd64 (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/amd64 r-base
• r-cran-multicore/arm64 (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/arm64 (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/arm64 r-base
• r-cran-multicore/armel (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/armel (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/armel r-base
• r-cran-multicore/armhf (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/armhf (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/armhf r-base
• r-cran-multicore/i386 (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/i386 (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/i386 r-base
• r-cran-multicore/mips64el (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/mips64el (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/mips64el r-base
• r-cran-multicore/mipsel (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/mipsel (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/mipsel r-base
• r-cran-multicore/ppc64el (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/ppc64el (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/ppc64el r-base
• r-cran-multicore/s390x (0.2-1 to 0.2-1)
  • Migration status for r-cran-multicore/s390x (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multicore/s390x r-base
• r-cran-mvnfast/amd64 (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/amd64 (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/amd64 r-base
• r-cran-mvnfast/arm64 (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/arm64 (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/arm64 r-base
• r-cran-mvnfast/armel (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/armel (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/armel r-base
• r-cran-mvnfast/armhf (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/armhf (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/armhf r-base
• r-cran-mvnfast/i386 (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/i386 (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/i386 r-base
• r-cran-mvnfast/mips64el (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/mips64el (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/mips64el r-base
• r-cran-mvnfast/mipsel (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/mipsel (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/mipsel r-base
• r-cran-mvnfast/ppc64el (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/ppc64el (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/ppc64el r-base
• r-cran-mvnfast/s390x (0.2.5+dfsg-1 to 0.2.5+dfsg-1)
  • Migration status for r-cran-mvnfast/s390x (0.2.5+dfsg-1 to 0.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnfast/s390x r-base
• r-cran-mvnormtest/amd64 (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/amd64 (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/amd64 r-base
• r-cran-mvnormtest/arm64 (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/arm64 (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/arm64 r-base
• r-cran-mvnormtest/armel (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/armel (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/armel r-base
• r-cran-mvnormtest/armhf (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/armhf (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/armhf r-base
• r-cran-mvnormtest/i386 (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/i386 (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/i386 r-base
• r-cran-mvnormtest/mips64el (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/mips64el (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/mips64el r-base
• r-cran-mvnormtest/mipsel (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/mipsel (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/mipsel r-base
• r-cran-mvnormtest/ppc64el (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/ppc64el (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/ppc64el r-base
• r-cran-mvnormtest/s390x (0.1-9-1 to 0.1-9-1)
  • Migration status for r-cran-mvnormtest/s390x (0.1-9-1 to 0.1-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mvnormtest/s390x r-base
• r-cran-ncdf4/amd64 (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/amd64 (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/amd64 r-base
• r-cran-ncdf4/arm64 (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/arm64 (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/arm64 r-base
• r-cran-ncdf4/armel (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/armel (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/armel r-base
• r-cran-ncdf4/armhf (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/armhf (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/armhf r-base
• r-cran-ncdf4/i386 (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/i386 (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/i386 r-base
• r-cran-ncdf4/mips64el (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/mips64el (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/mips64el r-base
• r-cran-ncdf4/mipsel (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/mipsel (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/mipsel r-base
• r-cran-ncdf4/ppc64el (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/ppc64el (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/ppc64el r-base
• r-cran-ncdf4/s390x (1.17-1 to 1.17-1)
  • Migration status for r-cran-ncdf4/s390x (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdf4/s390x r-base
• r-cran-nleqslv/amd64 (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/amd64 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/amd64 r-base
• r-cran-nleqslv/arm64 (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/arm64 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/arm64 r-base
• r-cran-nleqslv/armel (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/armel (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/armel r-base
• r-cran-nleqslv/armhf (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/armhf (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/armhf r-base
• r-cran-nleqslv/i386 (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/i386 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/i386 r-base
• r-cran-nleqslv/mips64el (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/mips64el (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/mips64el r-base
• r-cran-nleqslv/mipsel (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/mipsel (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/mipsel r-base
• r-cran-nleqslv/ppc64el (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/ppc64el (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/ppc64el r-base
• r-cran-nleqslv/s390x (3.3.2-1 to 3.3.2-1)
  • Migration status for r-cran-nleqslv/s390x (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nleqslv/s390x r-base
• r-cran-nloptr/amd64 (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/amd64 (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/amd64 r-base
• r-cran-nloptr/arm64 (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/arm64 (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/arm64 r-base
• r-cran-nloptr/armel (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/armel (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/armel r-base
• r-cran-nloptr/armhf (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/armhf (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/armhf r-base
• r-cran-nloptr/i386 (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/i386 (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/i386 r-base
• r-cran-nloptr/mips64el (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/mips64el (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/mips64el r-base
• r-cran-nloptr/mipsel (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/mipsel (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/mipsel r-base
• r-cran-nloptr/ppc64el (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/ppc64el (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/ppc64el r-base
• r-cran-nloptr/s390x (1.2.2.1-1 to 1.2.2.1-1)
  • Migration status for r-cran-nloptr/s390x (1.2.2.1-1 to 1.2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nloptr/s390x r-base
• r-cran-nmf/amd64 (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/amd64 (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/amd64 r-base
• r-cran-nmf/arm64 (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/arm64 (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/arm64 r-base
• r-cran-nmf/armel (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/armel (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/armel r-base
• r-cran-nmf/armhf (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/armhf (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/armhf r-base
• r-cran-nmf/i386 (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/i386 (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/i386 r-base
• r-cran-nmf/mips64el (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/mips64el (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/mips64el r-base
• r-cran-nmf/mipsel (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/mipsel (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/mipsel r-base
• r-cran-nmf/ppc64el (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/ppc64el (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/ppc64el r-base
• r-cran-nmf/s390x (0.22.0-1 to 0.22.0-1)
  • Migration status for r-cran-nmf/s390x (0.22.0-1 to 0.22.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nmf/s390x r-base
• r-cran-nnet/amd64 (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/amd64 (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/amd64 r-base
• r-cran-nnet/arm64 (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/arm64 (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/arm64 r-base
• r-cran-nnet/armel (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/armel (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/armel r-base
• r-cran-nnet/armhf (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/armhf (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/armhf r-base
• r-cran-nnet/i386 (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/i386 (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/i386 r-base
• r-cran-nnet/mips64el (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/mips64el (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/mips64el r-base
• r-cran-nnet/mipsel (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/mipsel (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/mipsel r-base
• r-cran-nnet/ppc64el (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/ppc64el (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/ppc64el r-base
• r-cran-nnet/s390x (7.3-14-1 to 7.3-14-1)
  • Migration status for r-cran-nnet/s390x (7.3-14-1 to 7.3-14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnet/s390x r-base
• r-cran-nnls/amd64 (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/amd64 (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/amd64 r-base
• r-cran-nnls/arm64 (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/arm64 (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/arm64 r-base
• r-cran-nnls/armel (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/armel (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/armel r-base
• r-cran-nnls/armhf (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/armhf (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/armhf r-base
• r-cran-nnls/i386 (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/i386 (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/i386 r-base
• r-cran-nnls/mips64el (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/mips64el (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/mips64el r-base
• r-cran-nnls/mipsel (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/mipsel (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/mipsel r-base
• r-cran-nnls/ppc64el (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/ppc64el (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/ppc64el r-base
• r-cran-nnls/s390x (1.4-3 to 1.4-3)
  • Migration status for r-cran-nnls/s390x (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nnls/s390x r-base
• r-cran-openmx/amd64 (2.17.3-1 to 2.17.3-1)
  • Migration status for r-cran-openmx/amd64 (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openmx/amd64 r-base
• r-cran-openmx/arm64 (2.17.3-1 to 2.17.3-1)
  • Migration status for r-cran-openmx/arm64 (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openmx/arm64 r-base
• r-cran-openmx/armhf (2.17.3-1 to 2.17.3-1)
  • Migration status for r-cran-openmx/armhf (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openmx/armhf r-base
• r-cran-openmx/i386 (2.17.3-1 to 2.17.3-1)
  • Migration status for r-cran-openmx/i386 (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openmx/i386 r-base
• r-cran-openmx/ppc64el (2.17.3-1 to 2.17.3-1)
  • Migration status for r-cran-openmx/ppc64el (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openmx/ppc64el r-base
• r-cran-openmx/s390x (2.17.3-1 to 2.17.3-1)
  • Migration status for r-cran-openmx/s390x (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openmx/s390x r-base
• r-cran-openssl/amd64 (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/amd64 (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/amd64 r-base
• r-cran-openssl/arm64 (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/arm64 (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/arm64 r-base
• r-cran-openssl/armel (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/armel (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/armel r-base
• r-cran-openssl/armhf (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/armhf (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/armhf r-base
• r-cran-openssl/i386 (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/i386 (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/i386 r-base
• r-cran-openssl/mips64el (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/mips64el (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/mips64el r-base
• r-cran-openssl/mipsel (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/mipsel (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/mipsel r-base
• r-cran-openssl/ppc64el (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/ppc64el (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/ppc64el r-base
• r-cran-openssl/s390x (1.4.1+dfsg-2 to 1.4.1+dfsg-2)
  • Migration status for r-cran-openssl/s390x (1.4.1+dfsg-2 to 1.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openssl/s390x r-base
• r-cran-openxlsx/amd64 (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/amd64 (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/amd64 r-base
• r-cran-openxlsx/arm64 (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/arm64 (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/arm64 r-base
• r-cran-openxlsx/armel (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/armel (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/armel r-base
• r-cran-openxlsx/armhf (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/armhf (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/armhf r-base
• r-cran-openxlsx/i386 (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/i386 (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/i386 r-base
• r-cran-openxlsx/mips64el (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/mips64el (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/mips64el r-base
• r-cran-openxlsx/mipsel (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/mipsel (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/mipsel r-base
• r-cran-openxlsx/ppc64el (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/ppc64el (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/ppc64el r-base
• r-cran-openxlsx/s390x (4.1.5-1 to 4.1.5-1)
  • Migration status for r-cran-openxlsx/s390x (4.1.5-1 to 4.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-openxlsx/s390x r-base
• r-cran-ordinal/amd64 (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/amd64 (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/amd64 r-base
• r-cran-ordinal/arm64 (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/arm64 (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/arm64 r-base
• r-cran-ordinal/armel (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/armel (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/armel r-base
• r-cran-ordinal/armhf (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/armhf (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/armhf r-base
• r-cran-ordinal/i386 (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/i386 (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/i386 r-base
• r-cran-ordinal/mips64el (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/mips64el (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/mips64el r-base
• r-cran-ordinal/mipsel (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/mipsel (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/mipsel r-base
• r-cran-ordinal/ppc64el (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/ppc64el (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/ppc64el r-base
• r-cran-ordinal/s390x (2019.12-10-1 to 2019.12-10-1)
  • Migration status for r-cran-ordinal/s390x (2019.12-10-1 to 2019.12-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ordinal/s390x r-base
• r-cran-pan/amd64 (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/amd64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/amd64 r-base
• r-cran-pan/arm64 (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/arm64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/arm64 r-base
• r-cran-pan/armel (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/armel (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/armel r-base
• r-cran-pan/armhf (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/armhf (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/armhf r-base
• r-cran-pan/i386 (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/i386 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/i386 r-base
• r-cran-pan/mips64el (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/mips64el (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/mips64el r-base
• r-cran-pan/mipsel (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/mipsel (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/mipsel r-base
• r-cran-pan/ppc64el (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/ppc64el (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/ppc64el r-base
• r-cran-pan/s390x (1.6-1 to 1.6-1)
  • Migration status for r-cran-pan/s390x (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pan/s390x r-base
• r-cran-paramhelpers/amd64 (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/amd64 (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/amd64 r-base
• r-cran-paramhelpers/arm64 (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/arm64 (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/arm64 r-base
• r-cran-paramhelpers/armel (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/armel (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/armel r-base
• r-cran-paramhelpers/armhf (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/armhf (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/armhf r-base
• r-cran-paramhelpers/i386 (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/i386 (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/i386 r-base
• r-cran-paramhelpers/mips64el (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/mips64el (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/mips64el r-base
• r-cran-paramhelpers/mipsel (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/mipsel (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/mipsel r-base
• r-cran-paramhelpers/ppc64el (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/ppc64el (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/ppc64el r-base
• r-cran-paramhelpers/s390x (1.14-1 to 1.14-1)
  • Migration status for r-cran-paramhelpers/s390x (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-paramhelpers/s390x r-base
• r-cran-parmigene/amd64 (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/amd64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/amd64 r-base
• r-cran-parmigene/arm64 (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/arm64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/arm64 r-base
• r-cran-parmigene/armel (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/armel (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/armel r-base
• r-cran-parmigene/armhf (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/armhf (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/armhf r-base
• r-cran-parmigene/i386 (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/i386 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/i386 r-base
• r-cran-parmigene/mips64el (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/mips64el (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/mips64el r-base
• r-cran-parmigene/mipsel (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/mipsel (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/mipsel r-base
• r-cran-parmigene/ppc64el (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/ppc64el (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/ppc64el r-base
• r-cran-parmigene/s390x (1.0.2-2 to 1.0.2-2)
  • Migration status for r-cran-parmigene/s390x (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parmigene/s390x r-base
• r-cran-party/amd64 (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/amd64 (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/amd64 r-base
• r-cran-party/arm64 (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/arm64 (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/arm64 r-base
• r-cran-party/armel (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/armel (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/armel r-base
• r-cran-party/armhf (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/armhf (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/armhf r-base
• r-cran-party/i386 (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/i386 (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/i386 r-base
• r-cran-party/mips64el (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/mips64el (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/mips64el r-base
• r-cran-party/mipsel (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/mipsel (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/mipsel r-base
• r-cran-party/ppc64el (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/ppc64el (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/ppc64el r-base
• r-cran-party/s390x (1.3-4-1 to 1.3-4-1)
  • Migration status for r-cran-party/s390x (1.3-4-1 to 1.3-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-party/s390x r-base
• r-cran-partykit/amd64 (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/amd64 (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/amd64 r-base
• r-cran-partykit/arm64 (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/arm64 (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/arm64 r-base
• r-cran-partykit/armel (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/armel (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/armel r-base
• r-cran-partykit/armhf (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/armhf (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/armhf r-base
• r-cran-partykit/i386 (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/i386 (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/i386 r-base
• r-cran-partykit/mips64el (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/mips64el (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/mips64el r-base
• r-cran-partykit/mipsel (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/mipsel (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/mipsel r-base
• r-cran-partykit/ppc64el (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/ppc64el (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/ppc64el r-base
• r-cran-partykit/s390x (1.2-7-1 to 1.2-7-1)
  • Migration status for r-cran-partykit/s390x (1.2-7-1 to 1.2-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-partykit/s390x r-base
• r-cran-pbdzmq/amd64 (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/amd64 (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/amd64 r-base
• r-cran-pbdzmq/arm64 (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/arm64 (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/arm64 r-base
• r-cran-pbdzmq/armel (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/armel (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/armel r-base
• r-cran-pbdzmq/armhf (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/armhf (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/armhf r-base
• r-cran-pbdzmq/i386 (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/i386 (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/i386 r-base
• r-cran-pbdzmq/mips64el (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/mips64el (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/mips64el r-base
• r-cran-pbdzmq/mipsel (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/mipsel (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/mipsel r-base
• r-cran-pbdzmq/ppc64el (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/ppc64el (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/ppc64el r-base
• r-cran-pbdzmq/s390x (0.3.3+dfsg-1 to 0.3.3+dfsg-1)
  • Migration status for r-cran-pbdzmq/s390x (0.3.3+dfsg-1 to 0.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbdzmq/s390x r-base
• r-cran-pbivnorm/amd64 (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/amd64 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/amd64 r-base
• r-cran-pbivnorm/arm64 (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/arm64 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/arm64 r-base
• r-cran-pbivnorm/armel (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/armel (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/armel r-base
• r-cran-pbivnorm/armhf (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/armhf (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/armhf r-base
• r-cran-pbivnorm/i386 (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/i386 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/i386 r-base
• r-cran-pbivnorm/mips64el (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/mips64el (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/mips64el r-base
• r-cran-pbivnorm/mipsel (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/mipsel (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/mipsel r-base
• r-cran-pbivnorm/ppc64el (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/ppc64el (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/ppc64el r-base
• r-cran-pbivnorm/s390x (0.6.0-3 to 0.6.0-3)
  • Migration status for r-cran-pbivnorm/s390x (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbivnorm/s390x r-base
• r-cran-pbmcapply/amd64 (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/amd64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/amd64 r-base
• r-cran-pbmcapply/arm64 (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/arm64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/arm64 r-base
• r-cran-pbmcapply/armel (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/armel (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/armel r-base
• r-cran-pbmcapply/armhf (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/armhf (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/armhf r-base
• r-cran-pbmcapply/i386 (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/i386 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/i386 r-base
• r-cran-pbmcapply/mips64el (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/mips64el (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/mips64el r-base
• r-cran-pbmcapply/mipsel (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/mipsel (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/mipsel r-base
• r-cran-pbmcapply/ppc64el (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/ppc64el (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/ppc64el r-base
• r-cran-pbmcapply/s390x (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-pbmcapply/s390x (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbmcapply/s390x r-base
• r-cran-pcapp/amd64 (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/amd64 (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/amd64 r-base
• r-cran-pcapp/arm64 (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/arm64 (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/arm64 r-base
• r-cran-pcapp/armel (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/armel (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/armel r-base
• r-cran-pcapp/armhf (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/armhf (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/armhf r-base
• r-cran-pcapp/i386 (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/i386 (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/i386 r-base
• r-cran-pcapp/mips64el (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/mips64el (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/mips64el r-base
• r-cran-pcapp/mipsel (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/mipsel (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/mipsel r-base
• r-cran-pcapp/ppc64el (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/ppc64el (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/ppc64el r-base
• r-cran-pcapp/s390x (1.9-73-2 to 1.9-73-2)
  • Migration status for r-cran-pcapp/s390x (1.9-73-2 to 1.9-73-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcapp/s390x r-base
• r-cran-pcict/amd64 (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/amd64 (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/amd64 r-base
• r-cran-pcict/arm64 (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/arm64 (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/arm64 r-base
• r-cran-pcict/armel (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/armel (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/armel r-base
• r-cran-pcict/armhf (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/armhf (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/armhf r-base
• r-cran-pcict/i386 (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/i386 (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/i386 r-base
• r-cran-pcict/mips64el (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/mips64el (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/mips64el r-base
• r-cran-pcict/mipsel (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/mipsel (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/mipsel r-base
• r-cran-pcict/ppc64el (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/ppc64el (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/ppc64el r-base
• r-cran-pcict/s390x (0.5-4.1-1 to 0.5-4.1-1)
  • Migration status for r-cran-pcict/s390x (0.5-4.1-1 to 0.5-4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pcict/s390x r-base
• r-cran-pdftools/amd64 (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/amd64 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/amd64 r-base
• r-cran-pdftools/arm64 (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/arm64 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/arm64 r-base
• r-cran-pdftools/armel (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/armel (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/armel r-base
• r-cran-pdftools/armhf (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/armhf (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/armhf r-base
• r-cran-pdftools/i386 (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/i386 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/i386 r-base
• r-cran-pdftools/mips64el (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/mips64el (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/mips64el r-base
• r-cran-pdftools/mipsel (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/mipsel (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/mipsel r-base
• r-cran-pdftools/ppc64el (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/ppc64el (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/ppc64el r-base
• r-cran-pdftools/s390x (2.3-1 to 2.3-1)
  • Migration status for r-cran-pdftools/s390x (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pdftools/s390x r-base
• r-cran-phangorn/amd64 (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/amd64 (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/amd64 r-base
• r-cran-phangorn/arm64 (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/arm64 (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/arm64 r-base
• r-cran-phangorn/armel (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/armel (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/armel r-base
• r-cran-phangorn/armhf (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/armhf (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/armhf r-base
• r-cran-phangorn/i386 (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/i386 (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/i386 r-base
• r-cran-phangorn/mips64el (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/mips64el (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/mips64el r-base
• r-cran-phangorn/mipsel (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/mipsel (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/mipsel r-base
• r-cran-phangorn/ppc64el (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/ppc64el (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/ppc64el r-base
• r-cran-phangorn/s390x (2.5.5-1 to 2.5.5-1)
  • Migration status for r-cran-phangorn/s390x (2.5.5-1 to 2.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phangorn/s390x r-base
• r-cran-phylobase/amd64 (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/amd64 (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/amd64 r-base
• r-cran-phylobase/arm64 (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/arm64 (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/arm64 r-base
• r-cran-phylobase/armel (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/armel (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/armel r-base
• r-cran-phylobase/armhf (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/armhf (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/armhf r-base
• r-cran-phylobase/i386 (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/i386 (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/i386 r-base
• r-cran-phylobase/mips64el (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/mips64el (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/mips64el r-base
• r-cran-phylobase/mipsel (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/mipsel (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/mipsel r-base
• r-cran-phylobase/ppc64el (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/ppc64el (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/ppc64el r-base
• r-cran-phylobase/s390x (0.8.10-1 to 0.8.10-1)
  • Migration status for r-cran-phylobase/s390x (0.8.10-1 to 0.8.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phylobase/s390x r-base
• r-cran-pixmap/amd64 (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/amd64 (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/amd64 r-base
• r-cran-pixmap/arm64 (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/arm64 (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/arm64 r-base
• r-cran-pixmap/armel (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/armel (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/armel r-base
• r-cran-pixmap/armhf (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/armhf (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/armhf r-base
• r-cran-pixmap/i386 (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/i386 (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/i386 r-base
• r-cran-pixmap/mips64el (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/mips64el (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/mips64el r-base
• r-cran-pixmap/mipsel (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/mipsel (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/mipsel r-base
• r-cran-pixmap/ppc64el (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/ppc64el (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/ppc64el r-base
• r-cran-pixmap/s390x (0.4-11-2 to 0.4-11-2)
  • Migration status for r-cran-pixmap/s390x (0.4-11-2 to 0.4-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pixmap/s390x r-base
• r-cran-pki/amd64 (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/amd64 (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/amd64 r-base
• r-cran-pki/arm64 (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/arm64 (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/arm64 r-base
• r-cran-pki/armel (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/armel (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/armel r-base
• r-cran-pki/armhf (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/armhf (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/armhf r-base
• r-cran-pki/i386 (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/i386 (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/i386 r-base
• r-cran-pki/mips64el (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/mips64el (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/mips64el r-base
• r-cran-pki/mipsel (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/mipsel (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/mipsel r-base
• r-cran-pki/ppc64el (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/ppc64el (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/ppc64el r-base
• r-cran-pki/s390x (0.1-7-1 to 0.1-7-1)
  • Migration status for r-cran-pki/s390x (0.1-7-1 to 0.1-7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pki/s390x r-base
• r-cran-png/amd64 (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/amd64 (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/amd64 r-base
• r-cran-png/arm64 (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/arm64 (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/arm64 r-base
• r-cran-png/armel (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/armel (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/armel r-base
• r-cran-png/armhf (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/armhf (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/armhf r-base
• r-cran-png/i386 (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/i386 (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/i386 r-base
• r-cran-png/mips64el (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/mips64el (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/mips64el r-base
• r-cran-png/mipsel (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/mipsel (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/mipsel r-base
• r-cran-png/ppc64el (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/ppc64el (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/ppc64el r-base
• r-cran-png/s390x (0.1-7-3 to 0.1-7-3)
  • Migration status for r-cran-png/s390x (0.1-7-3 to 0.1-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-png/s390x r-base
• r-cran-polyclip/amd64 (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/amd64 (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/amd64 r-base
• r-cran-polyclip/arm64 (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/arm64 (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/arm64 r-base
• r-cran-polyclip/armel (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/armel (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/armel r-base
• r-cran-polyclip/armhf (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/armhf (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/armhf r-base
• r-cran-polyclip/i386 (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/i386 (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/i386 r-base
• r-cran-polyclip/mips64el (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/mips64el (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/mips64el r-base
• r-cran-polyclip/mipsel (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/mipsel (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/mipsel r-base
• r-cran-polyclip/ppc64el (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/ppc64el (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/ppc64el r-base
• r-cran-polyclip/s390x (1.10-0-1 to 1.10-0-1)
  • Migration status for r-cran-polyclip/s390x (1.10-0-1 to 1.10-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polyclip/s390x r-base
• r-cran-polycub/amd64 (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/amd64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/amd64 r-base
• r-cran-polycub/arm64 (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/arm64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/arm64 r-base
• r-cran-polycub/armel (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/armel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/armel r-base
• r-cran-polycub/armhf (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/armhf (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/armhf r-base
• r-cran-polycub/i386 (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/i386 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/i386 r-base
• r-cran-polycub/mips64el (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/mips64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/mips64el r-base
• r-cran-polycub/mipsel (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/mipsel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/mipsel r-base
• r-cran-polycub/ppc64el (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/ppc64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/ppc64el r-base
• r-cran-polycub/s390x (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-polycub/s390x (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycub/s390x r-base
• r-cran-princurve/amd64 (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/amd64 (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/amd64 r-base
• r-cran-princurve/arm64 (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/arm64 (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/arm64 r-base
• r-cran-princurve/armel (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/armel (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/armel r-base
• r-cran-princurve/armhf (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/armhf (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/armhf r-base
• r-cran-princurve/i386 (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/i386 (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/i386 r-base
• r-cran-princurve/mips64el (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/mips64el (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/mips64el r-base
• r-cran-princurve/mipsel (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/mipsel (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/mipsel r-base
• r-cran-princurve/ppc64el (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/ppc64el (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/ppc64el r-base
• r-cran-princurve/s390x (2.1.4-1 to 2.1.4-1)
  • Migration status for r-cran-princurve/s390x (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-princurve/s390x r-base
• r-cran-proc/amd64 (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/amd64 (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/amd64 r-base
• r-cran-proc/arm64 (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/arm64 (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/arm64 r-base
• r-cran-proc/armel (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/armel (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/armel r-base
• r-cran-proc/armhf (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/armhf (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/armhf r-base
• r-cran-proc/i386 (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/i386 (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/i386 r-base
• r-cran-proc/mips64el (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/mips64el (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/mips64el r-base
• r-cran-proc/mipsel (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/mipsel (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/mipsel r-base
• r-cran-proc/ppc64el (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/ppc64el (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/ppc64el r-base
• r-cran-proc/s390x (1.16.2-2 to 1.16.2-2)
  • Migration status for r-cran-proc/s390x (1.16.2-2 to 1.16.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proc/s390x r-base
• r-cran-processx/amd64 (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/amd64 (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/amd64 r-base
• r-cran-processx/arm64 (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/arm64 (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/arm64 r-base
• r-cran-processx/armel (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/armel (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/armel r-base
• r-cran-processx/armhf (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/armhf (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/armhf r-base
• r-cran-processx/i386 (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/i386 (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/i386 r-base
• r-cran-processx/mips64el (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/mips64el (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/mips64el r-base
• r-cran-processx/mipsel (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/mipsel (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/mipsel r-base
• r-cran-processx/ppc64el (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/ppc64el (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/ppc64el r-base
• r-cran-processx/s390x (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-processx/s390x (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-processx/s390x r-base
• r-cran-prodlim/amd64 (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/amd64 (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/amd64 r-base
• r-cran-prodlim/arm64 (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/arm64 (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/arm64 r-base
• r-cran-prodlim/armel (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/armel (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/armel r-base
• r-cran-prodlim/armhf (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/armhf (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/armhf r-base
• r-cran-prodlim/i386 (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/i386 (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/i386 r-base
• r-cran-prodlim/mips64el (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/mips64el (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/mips64el r-base
• r-cran-prodlim/mipsel (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/mipsel (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/mipsel r-base
• r-cran-prodlim/ppc64el (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/ppc64el (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/ppc64el r-base
• r-cran-prodlim/s390x (2019.11.13-1 to 2019.11.13-1)
  • Migration status for r-cran-prodlim/s390x (2019.11.13-1 to 2019.11.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prodlim/s390x r-base
• r-cran-projpred/amd64 (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/amd64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/amd64 r-base
• r-cran-projpred/arm64 (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/arm64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/arm64 r-base
• r-cran-projpred/armel (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/armel (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/armel r-base
• r-cran-projpred/armhf (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/armhf (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/armhf r-base
• r-cran-projpred/i386 (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/i386 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/i386 r-base
• r-cran-projpred/mips64el (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/mips64el (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/mips64el r-base
• r-cran-projpred/mipsel (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/mipsel (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/mipsel r-base
• r-cran-projpred/ppc64el (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/ppc64el (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/ppc64el r-base
• r-cran-projpred/s390x (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-projpred/s390x (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-projpred/s390x r-base
• r-cran-promises/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/amd64 r-base
• r-cran-promises/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/arm64 r-base
• r-cran-promises/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/armel r-base
• r-cran-promises/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/armhf r-base
• r-cran-promises/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/i386 r-base
• r-cran-promises/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/mips64el r-base
• r-cran-promises/mipsel (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/mipsel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/mipsel r-base
• r-cran-promises/ppc64el (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/ppc64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/ppc64el r-base
• r-cran-promises/s390x (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-promises/s390x (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-promises/s390x r-base
• r-cran-propclust/amd64 (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/amd64 (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/amd64 r-base
• r-cran-propclust/arm64 (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/arm64 (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/arm64 r-base
• r-cran-propclust/armel (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/armel (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/armel r-base
• r-cran-propclust/armhf (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/armhf (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/armhf r-base
• r-cran-propclust/i386 (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/i386 (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/i386 r-base
• r-cran-propclust/mips64el (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/mips64el (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/mips64el r-base
• r-cran-propclust/mipsel (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/mipsel (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/mipsel r-base
• r-cran-propclust/ppc64el (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/ppc64el (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/ppc64el r-base
• r-cran-propclust/s390x (1.4-6-1 to 1.4-6-1)
  • Migration status for r-cran-propclust/s390x (1.4-6-1 to 1.4-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-propclust/s390x r-base
• r-cran-ps/amd64 (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/amd64 (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/amd64 r-base
• r-cran-ps/arm64 (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/arm64 (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/arm64 r-base
• r-cran-ps/armel (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/armel (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/armel r-base
• r-cran-ps/armhf (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/armhf (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/armhf r-base
• r-cran-ps/i386 (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/i386 (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/i386 r-base
• r-cran-ps/mips64el (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/mips64el (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/mips64el r-base
• r-cran-ps/mipsel (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/mipsel (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/mipsel r-base
• r-cran-ps/ppc64el (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/ppc64el (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/ppc64el r-base
• r-cran-ps/s390x (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-ps/s390x (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ps/s390x r-base
• r-cran-pscl/amd64 (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/amd64 (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/amd64 r-base
• r-cran-pscl/arm64 (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/arm64 (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/arm64 r-base
• r-cran-pscl/armel (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/armel (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/armel r-base
• r-cran-pscl/armhf (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/armhf (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/armhf r-base
• r-cran-pscl/i386 (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/i386 (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/i386 r-base
• r-cran-pscl/mips64el (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/mips64el (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/mips64el r-base
• r-cran-pscl/mipsel (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/mipsel (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/mipsel r-base
• r-cran-pscl/ppc64el (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/ppc64el (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/ppc64el r-base
• r-cran-pscl/s390x (1.5.5-1 to 1.5.5-1)
  • Migration status for r-cran-pscl/s390x (1.5.5-1 to 1.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscl/s390x r-base
• r-cran-psychometric/amd64 (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/amd64 (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/amd64 r-base
• r-cran-psychometric/arm64 (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/arm64 (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/arm64 r-base
• r-cran-psychometric/armel (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/armel (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/armel r-base
• r-cran-psychometric/armhf (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/armhf (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/armhf r-base
• r-cran-psychometric/i386 (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/i386 (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/i386 r-base
• r-cran-psychometric/mips64el (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/mips64el (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/mips64el r-base
• r-cran-psychometric/mipsel (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/mipsel (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/mipsel r-base
• r-cran-psychometric/ppc64el (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/ppc64el (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/ppc64el r-base
• r-cran-psychometric/s390x (2.2-1 to 2.2-1)
  • Migration status for r-cran-psychometric/s390x (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychometric/s390x r-base
• r-cran-psychotools/amd64 (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/amd64 (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/amd64 r-base
• r-cran-psychotools/arm64 (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/arm64 (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/arm64 r-base
• r-cran-psychotools/armel (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/armel (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/armel r-base
• r-cran-psychotools/armhf (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/armhf (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/armhf r-base
• r-cran-psychotools/i386 (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/i386 (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/i386 r-base
• r-cran-psychotools/mips64el (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/mips64el (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/mips64el r-base
• r-cran-psychotools/mipsel (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/mipsel (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/mipsel r-base
• r-cran-psychotools/ppc64el (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/ppc64el (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/ppc64el r-base
• r-cran-psychotools/s390x (0.5-1-1 to 0.5-1-1)
  • Migration status for r-cran-psychotools/s390x (0.5-1-1 to 0.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotools/s390x r-base
• r-cran-purrr/amd64 (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/amd64 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/amd64 r-base
• r-cran-purrr/arm64 (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/arm64 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/arm64 r-base
• r-cran-purrr/armel (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/armel (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/armel r-base
• r-cran-purrr/armhf (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/armhf (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/armhf r-base
• r-cran-purrr/i386 (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/i386 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/i386 r-base
• r-cran-purrr/mips64el (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/mips64el (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/mips64el r-base
• r-cran-purrr/mipsel (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/mipsel (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/mipsel r-base
• r-cran-purrr/ppc64el (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/ppc64el (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/ppc64el r-base
• r-cran-purrr/s390x (0.3.4-1 to 0.3.4-1)
  • Migration status for r-cran-purrr/s390x (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrr/s390x r-base
• r-cran-purrrlyr/amd64 (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/amd64 (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/amd64 r-base
• r-cran-purrrlyr/arm64 (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/arm64 (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/arm64 r-base
• r-cran-purrrlyr/armel (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/armel (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/armel r-base
• r-cran-purrrlyr/armhf (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/armhf (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/armhf r-base
• r-cran-purrrlyr/i386 (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/i386 (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/i386 r-base
• r-cran-purrrlyr/mips64el (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/mips64el (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/mips64el r-base
• r-cran-purrrlyr/mipsel (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/mipsel (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/mipsel r-base
• r-cran-purrrlyr/ppc64el (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/ppc64el (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/ppc64el r-base
• r-cran-purrrlyr/s390x (0.0.6-1 to 0.0.6-1)
  • Migration status for r-cran-purrrlyr/s390x (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrlyr/s390x r-base
• r-cran-qap/amd64 (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/amd64 (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/amd64 r-base
• r-cran-qap/arm64 (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/arm64 (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/arm64 r-base
• r-cran-qap/armel (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/armel (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/armel r-base
• r-cran-qap/armhf (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/armhf (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/armhf r-base
• r-cran-qap/i386 (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/i386 (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/i386 r-base
• r-cran-qap/mips64el (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/mips64el (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/mips64el r-base
• r-cran-qap/mipsel (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/mipsel (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/mipsel r-base
• r-cran-qap/ppc64el (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/ppc64el (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/ppc64el r-base
• r-cran-qap/s390x (0.1-1-1 to 0.1-1-1)
  • Migration status for r-cran-qap/s390x (0.1-1-1 to 0.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qap/s390x r-base
• r-cran-qgraph/amd64 (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-qgraph/amd64 (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qgraph/amd64 r-base
• r-cran-qgraph/arm64 (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-qgraph/arm64 (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qgraph/arm64 r-base
• r-cran-qgraph/armhf (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-qgraph/armhf (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qgraph/armhf r-base
• r-cran-qgraph/i386 (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-qgraph/i386 (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qgraph/i386 r-base
• r-cran-qgraph/mips64el (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-qgraph/mips64el (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qgraph/mips64el r-base
• r-cran-qgraph/mipsel (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-qgraph/mipsel (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qgraph/mipsel r-base
• r-cran-qgraph/ppc64el (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-qgraph/ppc64el (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qgraph/ppc64el r-base
• r-cran-qgraph/s390x (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-qgraph/s390x (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qgraph/s390x r-base
• r-cran-qpdf/amd64 (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/amd64 (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/amd64 r-base
• r-cran-qpdf/arm64 (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/arm64 (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/arm64 r-base
• r-cran-qpdf/armel (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/armel (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/armel r-base
• r-cran-qpdf/armhf (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/armhf (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/armhf r-base
• r-cran-qpdf/i386 (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/i386 (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/i386 r-base
• r-cran-qpdf/mips64el (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/mips64el (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/mips64el r-base
• r-cran-qpdf/mipsel (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/mipsel (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/mipsel r-base
• r-cran-qpdf/ppc64el (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/ppc64el (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/ppc64el r-base
• r-cran-qpdf/s390x (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for r-cran-qpdf/s390x (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qpdf/s390x r-base
• r-cran-qtl/amd64 (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/amd64 (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/amd64 r-base
• r-cran-qtl/arm64 (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/arm64 (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/arm64 r-base
• r-cran-qtl/armel (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/armel (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/armel r-base
• r-cran-qtl/armhf (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/armhf (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/armhf r-base
• r-cran-qtl/i386 (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/i386 (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/i386 r-base
• r-cran-qtl/mips64el (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/mips64el (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/mips64el r-base
• r-cran-qtl/mipsel (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/mipsel (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/mipsel r-base
• r-cran-qtl/ppc64el (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/ppc64el (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/ppc64el r-base
• r-cran-qtl/s390x (1.46-2-1 to 1.46-2-1)
  • Migration status for r-cran-qtl/s390x (1.46-2-1 to 1.46-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qtl/s390x r-base
• r-cran-quantreg/amd64 (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/amd64 (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/amd64 r-base
• r-cran-quantreg/arm64 (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/arm64 (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/arm64 r-base
• r-cran-quantreg/armel (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/armel (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/armel r-base
• r-cran-quantreg/armhf (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/armhf (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/armhf r-base
• r-cran-quantreg/i386 (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/i386 (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/i386 r-base
• r-cran-quantreg/mips64el (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/mips64el (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/mips64el r-base
• r-cran-quantreg/mipsel (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/mipsel (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/mipsel r-base
• r-cran-quantreg/ppc64el (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/ppc64el (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/ppc64el r-base
• r-cran-quantreg/s390x (5.55-1 to 5.55-1)
  • Migration status for r-cran-quantreg/s390x (5.55-1 to 5.55-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-quantreg/s390x r-base
• r-cran-randomfields/amd64 (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/amd64 (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/amd64 r-base
• r-cran-randomfields/arm64 (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/arm64 (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/arm64 r-base
• r-cran-randomfields/armel (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/armel (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/armel r-base
• r-cran-randomfields/armhf (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/armhf (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/armhf r-base
• r-cran-randomfields/i386 (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/i386 (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/i386 r-base
• r-cran-randomfields/mips64el (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/mips64el (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/mips64el r-base
• r-cran-randomfields/mipsel (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/mipsel (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/mipsel r-base
• r-cran-randomfields/ppc64el (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/ppc64el (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/ppc64el r-base
• r-cran-randomfields/s390x (3.3.8-1 to 3.3.8-1)
  • Migration status for r-cran-randomfields/s390x (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfields/s390x r-base
• r-cran-randomfieldsutils/amd64 (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/amd64 (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/amd64 r-base
• r-cran-randomfieldsutils/arm64 (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/arm64 (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/arm64 r-base
• r-cran-randomfieldsutils/armel (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/armel (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/armel r-base
• r-cran-randomfieldsutils/armhf (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/armhf (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/armhf r-base
• r-cran-randomfieldsutils/i386 (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/i386 (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/i386 r-base
• r-cran-randomfieldsutils/mips64el (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/mips64el (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/mips64el r-base
• r-cran-randomfieldsutils/mipsel (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/mipsel (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/mipsel r-base
• r-cran-randomfieldsutils/ppc64el (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/ppc64el (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/ppc64el r-base
• r-cran-randomfieldsutils/s390x (0.5.3-1 to 0.5.3-1)
  • Migration status for r-cran-randomfieldsutils/s390x (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomfieldsutils/s390x r-base
• r-cran-randomforest/amd64 (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/amd64 (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/amd64 r-base
• r-cran-randomforest/arm64 (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/arm64 (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/arm64 r-base
• r-cran-randomforest/armel (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/armel (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/armel r-base
• r-cran-randomforest/armhf (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/armhf (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/armhf r-base
• r-cran-randomforest/i386 (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/i386 (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/i386 r-base
• r-cran-randomforest/mips64el (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/mips64el (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/mips64el r-base
• r-cran-randomforest/mipsel (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/mipsel (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/mipsel r-base
• r-cran-randomforest/ppc64el (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/ppc64el (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/ppc64el r-base
• r-cran-randomforest/s390x (4.6-14-2 to 4.6-14-2)
  • Migration status for r-cran-randomforest/s390x (4.6-14-2 to 4.6-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomforest/s390x r-base
• r-cran-randomglm/amd64 (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/amd64 (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/amd64 r-base
• r-cran-randomglm/arm64 (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/arm64 (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/arm64 r-base
• r-cran-randomglm/armel (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/armel (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/armel r-base
• r-cran-randomglm/armhf (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/armhf (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/armhf r-base
• r-cran-randomglm/i386 (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/i386 (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/i386 r-base
• r-cran-randomglm/mips64el (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/mips64el (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/mips64el r-base
• r-cran-randomglm/mipsel (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/mipsel (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/mipsel r-base
• r-cran-randomglm/ppc64el (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/ppc64el (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/ppc64el r-base
• r-cran-randomglm/s390x (1.02-1-1 to 1.02-1-1)
  • Migration status for r-cran-randomglm/s390x (1.02-1-1 to 1.02-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-randomglm/s390x r-base
• r-cran-ranger/amd64 (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/amd64 (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/amd64 r-base
• r-cran-ranger/arm64 (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/arm64 (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/arm64 r-base
• r-cran-ranger/armel (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/armel (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/armel r-base
• r-cran-ranger/armhf (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/armhf (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/armhf r-base
• r-cran-ranger/i386 (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/i386 (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/i386 r-base
• r-cran-ranger/mips64el (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/mips64el (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/mips64el r-base
• r-cran-ranger/mipsel (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/mipsel (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/mipsel r-base
• r-cran-ranger/ppc64el (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/ppc64el (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/ppc64el r-base
• r-cran-ranger/s390x (0.12.1-3 to 0.12.1-3)
  • Migration status for r-cran-ranger/s390x (0.12.1-3 to 0.12.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ranger/s390x r-base
• r-cran-rann/amd64 (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/amd64 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/amd64 r-base
• r-cran-rann/arm64 (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/arm64 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/arm64 r-base
• r-cran-rann/armel (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/armel (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/armel r-base
• r-cran-rann/armhf (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/armhf (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/armhf r-base
• r-cran-rann/i386 (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/i386 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/i386 r-base
• r-cran-rann/mips64el (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/mips64el (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/mips64el r-base
• r-cran-rann/mipsel (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/mipsel (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/mipsel r-base
• r-cran-rann/ppc64el (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/ppc64el (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/ppc64el r-base
• r-cran-rann/s390x (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/s390x (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rann/s390x r-base
• r-cran-rappdirs/amd64 (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/amd64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/amd64 r-base
• r-cran-rappdirs/arm64 (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/arm64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/arm64 r-base
• r-cran-rappdirs/armel (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/armel (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/armel r-base
• r-cran-rappdirs/armhf (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/armhf (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/armhf r-base
• r-cran-rappdirs/i386 (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/i386 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/i386 r-base
• r-cran-rappdirs/mips64el (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/mips64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/mips64el r-base
• r-cran-rappdirs/mipsel (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/mipsel (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/mipsel r-base
• r-cran-rappdirs/ppc64el (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/ppc64el (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/ppc64el r-base
• r-cran-rappdirs/s390x (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-rappdirs/s390x (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rappdirs/s390x r-base
• r-cran-raschsampler/amd64 (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/amd64 (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/amd64 r-base
• r-cran-raschsampler/arm64 (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/arm64 (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/arm64 r-base
• r-cran-raschsampler/armel (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/armel (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/armel r-base
• r-cran-raschsampler/armhf (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/armhf (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/armhf r-base
• r-cran-raschsampler/i386 (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/i386 (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/i386 r-base
• r-cran-raschsampler/mips64el (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/mips64el (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/mips64el r-base
• r-cran-raschsampler/mipsel (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/mipsel (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/mipsel r-base
• r-cran-raschsampler/ppc64el (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/ppc64el (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/ppc64el r-base
• r-cran-raschsampler/s390x (0.8-8-2 to 0.8-8-2)
  • Migration status for r-cran-raschsampler/s390x (0.8-8-2 to 0.8-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raschsampler/s390x r-base
• r-cran-rcppannoy/amd64 (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/amd64 (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/amd64 r-base
• r-cran-rcppannoy/arm64 (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/arm64 (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/arm64 r-base
• r-cran-rcppannoy/armel (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/armel (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/armel r-base
• r-cran-rcppannoy/armhf (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/armhf (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/armhf r-base
• r-cran-rcppannoy/i386 (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/i386 (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/i386 r-base
• r-cran-rcppannoy/mips64el (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/mips64el (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/mips64el r-base
• r-cran-rcppannoy/mipsel (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/mipsel (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/mipsel r-base
• r-cran-rcppannoy/ppc64el (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/ppc64el (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/ppc64el r-base
• r-cran-rcppannoy/s390x (0.0.16-2 to 0.0.16-2)
  • Migration status for r-cran-rcppannoy/s390x (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppannoy/s390x r-base
• r-cran-rcppeigen/amd64 (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/amd64 (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/amd64 r-base
• r-cran-rcppeigen/arm64 (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/arm64 (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/arm64 r-base
• r-cran-rcppeigen/armel (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/armel (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/armel r-base
• r-cran-rcppeigen/armhf (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/armhf (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/armhf r-base
• r-cran-rcppeigen/i386 (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/i386 (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/i386 r-base
• r-cran-rcppeigen/mips64el (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/mips64el (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/mips64el r-base
• r-cran-rcppeigen/mipsel (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/mipsel (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/mipsel r-base
• r-cran-rcppeigen/ppc64el (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/ppc64el (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/ppc64el r-base
• r-cran-rcppeigen/s390x (0.3.3.7.0-1 to 0.3.3.7.0-1)
  • Migration status for r-cran-rcppeigen/s390x (0.3.3.7.0-1 to 0.3.3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppeigen/s390x r-base
• r-cran-rcppgsl/amd64 (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/amd64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/amd64 r-base
• r-cran-rcppgsl/arm64 (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/arm64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/arm64 r-base
• r-cran-rcppgsl/armel (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/armel (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/armel r-base
• r-cran-rcppgsl/armhf (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/armhf (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/armhf r-base
• r-cran-rcppgsl/i386 (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/i386 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/i386 r-base
• r-cran-rcppgsl/mips64el (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/mips64el (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/mips64el r-base
• r-cran-rcppgsl/mipsel (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/mipsel (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/mipsel r-base
• r-cran-rcppgsl/ppc64el (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/ppc64el (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/ppc64el r-base
• r-cran-rcppgsl/s390x (0.3.7-1 to 0.3.7-1)
  • Migration status for r-cran-rcppgsl/s390x (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppgsl/s390x r-base
• r-cran-rcppparallel/amd64 (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/amd64 (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/amd64 r-base
• r-cran-rcppparallel/arm64 (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/arm64 (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/arm64 r-base
• r-cran-rcppparallel/armel (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/armel (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/armel r-base
• r-cran-rcppparallel/armhf (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/armhf (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/armhf r-base
• r-cran-rcppparallel/i386 (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/i386 (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/i386 r-base
• r-cran-rcppparallel/mips64el (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/mips64el (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/mips64el r-base
• r-cran-rcppparallel/mipsel (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/mipsel (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/mipsel r-base
• r-cran-rcppparallel/ppc64el (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/ppc64el (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/ppc64el r-base
• r-cran-rcppparallel/s390x (5.0.1+dfsg-1 to 5.0.1+dfsg-1)
  • Migration status for r-cran-rcppparallel/s390x (5.0.1+dfsg-1 to 5.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppparallel/s390x r-base
• r-cran-rcpproll/amd64 (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/amd64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/amd64 r-base
• r-cran-rcpproll/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/arm64 r-base
• r-cran-rcpproll/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/armel r-base
• r-cran-rcpproll/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/armhf r-base
• r-cran-rcpproll/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/i386 r-base
• r-cran-rcpproll/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/mips64el r-base
• r-cran-rcpproll/mipsel (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/mipsel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/mipsel r-base
• r-cran-rcpproll/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/ppc64el r-base
• r-cran-rcpproll/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-rcpproll/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcpproll/s390x r-base
• r-cran-rcurl/amd64 (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/amd64 (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/amd64 r-base
• r-cran-rcurl/arm64 (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/arm64 (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/arm64 r-base
• r-cran-rcurl/armel (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/armel (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/armel r-base
• r-cran-rcurl/armhf (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/armhf (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/armhf r-base
• r-cran-rcurl/i386 (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/i386 (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/i386 r-base
• r-cran-rcurl/mips64el (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/mips64el (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/mips64el r-base
• r-cran-rcurl/mipsel (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/mipsel (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/mipsel r-base
• r-cran-rcurl/ppc64el (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/ppc64el (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/ppc64el r-base
• r-cran-rcurl/s390x (1.98-1.2-1 to 1.98-1.2-1)
  • Migration status for r-cran-rcurl/s390x (1.98-1.2-1 to 1.98-1.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcurl/s390x r-base
• r-cran-readr/amd64 (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/amd64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/amd64 r-base
• r-cran-readr/arm64 (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/arm64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/arm64 r-base
• r-cran-readr/armel (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/armel (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/armel r-base
• r-cran-readr/armhf (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/armhf (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/armhf r-base
• r-cran-readr/i386 (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/i386 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/i386 r-base
• r-cran-readr/mips64el (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/mips64el (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/mips64el r-base
• r-cran-readr/mipsel (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/mipsel (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/mipsel r-base
• r-cran-readr/ppc64el (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/ppc64el (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/ppc64el r-base
• r-cran-readr/s390x (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-readr/s390x (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readr/s390x r-base
• r-cran-readstata13/amd64 (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/amd64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/amd64 r-base
• r-cran-readstata13/arm64 (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/arm64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/arm64 r-base
• r-cran-readstata13/armel (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/armel (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/armel r-base
• r-cran-readstata13/armhf (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/armhf (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/armhf r-base
• r-cran-readstata13/i386 (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/i386 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/i386 r-base
• r-cran-readstata13/mips64el (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/mips64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/mips64el r-base
• r-cran-readstata13/mipsel (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/mipsel (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/mipsel r-base
• r-cran-readstata13/ppc64el (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/ppc64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/ppc64el r-base
• r-cran-readstata13/s390x (0.9.2-1 to 0.9.2-1)
  • Migration status for r-cran-readstata13/s390x (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readstata13/s390x r-base
• r-cran-readxl/amd64 (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/amd64 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/amd64 r-base
• r-cran-readxl/arm64 (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/arm64 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/arm64 r-base
• r-cran-readxl/armel (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/armel (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/armel r-base
• r-cran-readxl/armhf (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/armhf (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/armhf r-base
• r-cran-readxl/i386 (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/i386 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/i386 r-base
• r-cran-readxl/mips64el (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/mips64el (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/mips64el r-base
• r-cran-readxl/mipsel (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/mipsel (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/mipsel r-base
• r-cran-readxl/ppc64el (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/ppc64el (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/ppc64el r-base
• r-cran-readxl/s390x (1.3.1-2 to 1.3.1-2)
  • Migration status for r-cran-readxl/s390x (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readxl/s390x r-base
• r-cran-redland/amd64 (1.0.17-11-1 to 1.0.17-11-1)
  • Migration status for r-cran-redland/amd64 (1.0.17-11-1 to 1.0.17-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-redland/amd64 r-base
• r-cran-redland/arm64 (1.0.17-11-1 to 1.0.17-11-1)
  • Migration status for r-cran-redland/arm64 (1.0.17-11-1 to 1.0.17-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-redland/arm64 r-base
• r-cran-redland/armhf (1.0.17-11-1 to 1.0.17-11-1)
  • Migration status for r-cran-redland/armhf (1.0.17-11-1 to 1.0.17-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-redland/armhf r-base
• r-cran-redland/i386 (1.0.17-11-1 to 1.0.17-11-1)
  • Migration status for r-cran-redland/i386 (1.0.17-11-1 to 1.0.17-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-redland/i386 r-base
• r-cran-redland/mips64el (1.0.17-11-1 to 1.0.17-11-1)
  • Migration status for r-cran-redland/mips64el (1.0.17-11-1 to 1.0.17-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-redland/mips64el r-base
• r-cran-redland/mipsel (1.0.17-11-1 to 1.0.17-11-1)
  • Migration status for r-cran-redland/mipsel (1.0.17-11-1 to 1.0.17-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-redland/mipsel r-base
• r-cran-redland/ppc64el (1.0.17-11-1 to 1.0.17-11-1)
  • Migration status for r-cran-redland/ppc64el (1.0.17-11-1 to 1.0.17-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-redland/ppc64el r-base
• r-cran-redland/s390x (1.0.17-11-1 to 1.0.17-11-1)
  • Migration status for r-cran-redland/s390x (1.0.17-11-1 to 1.0.17-11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-redland/s390x r-base
• r-cran-regsem/amd64 (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/amd64 (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/amd64 r-base
• r-cran-regsem/arm64 (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/arm64 (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/arm64 r-base
• r-cran-regsem/armel (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/armel (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/armel r-base
• r-cran-regsem/armhf (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/armhf (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/armhf r-base
• r-cran-regsem/i386 (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/i386 (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/i386 r-base
• r-cran-regsem/mips64el (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/mips64el (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/mips64el r-base
• r-cran-regsem/mipsel (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/mipsel (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/mipsel r-base
• r-cran-regsem/ppc64el (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/ppc64el (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/ppc64el r-base
• r-cran-regsem/s390x (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for r-cran-regsem/s390x (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-regsem/s390x r-base
• r-cran-relsurv/amd64 (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/amd64 (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/amd64 r-base
• r-cran-relsurv/arm64 (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/arm64 (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/arm64 r-base
• r-cran-relsurv/armel (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/armel (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/armel r-base
• r-cran-relsurv/armhf (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/armhf (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/armhf r-base
• r-cran-relsurv/i386 (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/i386 (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/i386 r-base
• r-cran-relsurv/mips64el (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/mips64el (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/mips64el r-base
• r-cran-relsurv/mipsel (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/mipsel (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/mipsel r-base
• r-cran-relsurv/ppc64el (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/ppc64el (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/ppc64el r-base
• r-cran-relsurv/s390x (2.2-3-1 to 2.2-3-1)
  • Migration status for r-cran-relsurv/s390x (2.2-3-1 to 2.2-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-relsurv/s390x r-base
• r-cran-reticulate/amd64 (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/amd64 (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/amd64 r-base
• r-cran-reticulate/arm64 (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/arm64 (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/arm64 r-base
• r-cran-reticulate/armel (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/armel (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/armel r-base
• r-cran-reticulate/armhf (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/armhf (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/armhf r-base
• r-cran-reticulate/i386 (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/i386 (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/i386 r-base
• r-cran-reticulate/mips64el (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/mips64el (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/mips64el r-base
• r-cran-reticulate/mipsel (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/mipsel (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/mipsel r-base
• r-cran-reticulate/ppc64el (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/ppc64el (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/ppc64el r-base
• r-cran-reticulate/s390x (1.15+dfsg-1 to 1.15+dfsg-1)
  • Migration status for r-cran-reticulate/s390x (1.15+dfsg-1 to 1.15+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reticulate/s390x r-base
• r-cran-rgdal/amd64 (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/amd64 (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/amd64 r-base
• r-cran-rgdal/arm64 (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/arm64 (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/arm64 r-base
• r-cran-rgdal/armel (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/armel (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/armel r-base
• r-cran-rgdal/armhf (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/armhf (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/armhf r-base
• r-cran-rgdal/i386 (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/i386 (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/i386 r-base
• r-cran-rgdal/mips64el (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/mips64el (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/mips64el r-base
• r-cran-rgdal/mipsel (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/mipsel (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/mipsel r-base
• r-cran-rgdal/ppc64el (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/ppc64el (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/ppc64el r-base
• r-cran-rgdal/s390x (1.4-8-1 to 1.4-8-1)
  • Migration status for r-cran-rgdal/s390x (1.4-8-1 to 1.4-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgdal/s390x r-base
• r-cran-rgenoud/amd64 (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/amd64 (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/amd64 r-base
• r-cran-rgenoud/arm64 (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/arm64 (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/arm64 r-base
• r-cran-rgenoud/armel (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/armel (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/armel r-base
• r-cran-rgenoud/armhf (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/armhf (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/armhf r-base
• r-cran-rgenoud/i386 (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/i386 (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/i386 r-base
• r-cran-rgenoud/mips64el (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/mips64el (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/mips64el r-base
• r-cran-rgenoud/mipsel (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/mipsel (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/mipsel r-base
• r-cran-rgenoud/ppc64el (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/ppc64el (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/ppc64el r-base
• r-cran-rgenoud/s390x (5.8-3.0-1 to 5.8-3.0-1)
  • Migration status for r-cran-rgenoud/s390x (5.8-3.0-1 to 5.8-3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rgenoud/s390x r-base
• r-cran-rinside/amd64 (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/amd64 (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/amd64 r-base
• r-cran-rinside/arm64 (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/arm64 (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/arm64 r-base
• r-cran-rinside/armel (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/armel (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/armel r-base
• r-cran-rinside/armhf (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/armhf (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/armhf r-base
• r-cran-rinside/i386 (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/i386 (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/i386 r-base
• r-cran-rinside/mips64el (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/mips64el (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/mips64el r-base
• r-cran-rinside/mipsel (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/mipsel (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/mipsel r-base
• r-cran-rinside/ppc64el (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/ppc64el (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/ppc64el r-base
• r-cran-rinside/s390x (0.2.16-1 to 0.2.16-1)
  • Migration status for r-cran-rinside/s390x (0.2.16-1 to 0.2.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rinside/s390x r-base
• r-cran-rjags/amd64 (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/amd64 (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/amd64 r-base
• r-cran-rjags/arm64 (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/arm64 (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/arm64 r-base
• r-cran-rjags/armel (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/armel (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/armel r-base
• r-cran-rjags/armhf (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/armhf (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/armhf r-base
• r-cran-rjags/i386 (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/i386 (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/i386 r-base
• r-cran-rjags/mips64el (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/mips64el (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/mips64el r-base
• r-cran-rjags/mipsel (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/mipsel (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/mipsel r-base
• r-cran-rjags/ppc64el (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/ppc64el (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/ppc64el r-base
• r-cran-rjags/s390x (1:4-10-1 to 1:4-10-1)
  • Migration status for r-cran-rjags/s390x (1:4-10-1 to 1:4-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjags/s390x r-base
• r-cran-rjson/amd64 (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/amd64 (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/amd64 r-base
• r-cran-rjson/arm64 (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/arm64 (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/arm64 r-base
• r-cran-rjson/armel (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/armel (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/armel r-base
• r-cran-rjson/armhf (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/armhf (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/armhf r-base
• r-cran-rjson/i386 (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/i386 (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/i386 r-base
• r-cran-rjson/mips64el (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/mips64el (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/mips64el r-base
• r-cran-rjson/mipsel (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/mipsel (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/mipsel r-base
• r-cran-rjson/ppc64el (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/ppc64el (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/ppc64el r-base
• r-cran-rjson/s390x (0.2.20-1 to 0.2.20-1)
  • Migration status for r-cran-rjson/s390x (0.2.20-1 to 0.2.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rjson/s390x r-base
• r-cran-rlang/amd64 (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/amd64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/amd64 r-base
• r-cran-rlang/arm64 (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/arm64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/arm64 r-base
• r-cran-rlang/armel (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/armel (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/armel r-base
• r-cran-rlang/armhf (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/armhf (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/armhf r-base
• r-cran-rlang/i386 (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/i386 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/i386 r-base
• r-cran-rlang/mips64el (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/mips64el (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/mips64el r-base
• r-cran-rlang/mipsel (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/mipsel (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/mipsel r-base
• r-cran-rlang/ppc64el (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/ppc64el (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/ppc64el r-base
• r-cran-rlang/s390x (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-rlang/s390x (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlang/s390x r-base
• r-cran-rlrsim/amd64 (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/amd64 (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/amd64 r-base
• r-cran-rlrsim/arm64 (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/arm64 (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/arm64 r-base
• r-cran-rlrsim/armel (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/armel (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/armel r-base
• r-cran-rlrsim/armhf (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/armhf (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/armhf r-base
• r-cran-rlrsim/i386 (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/i386 (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/i386 r-base
• r-cran-rlrsim/mips64el (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/mips64el (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/mips64el r-base
• r-cran-rlrsim/mipsel (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/mipsel (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/mipsel r-base
• r-cran-rlrsim/ppc64el (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/ppc64el (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/ppc64el r-base
• r-cran-rlrsim/s390x (3.1-6-1 to 3.1-6-1)
  • Migration status for r-cran-rlrsim/s390x (3.1-6-1 to 3.1-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlrsim/s390x r-base
• r-cran-rms/amd64 (5.1-4-1 to 5.1-4-1)
  • Migration status for r-cran-rms/amd64 (5.1-4-1 to 5.1-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rms/amd64 r-base
• r-cran-rms/arm64 (5.1-4-1 to 5.1-4-1)
  • Migration status for r-cran-rms/arm64 (5.1-4-1 to 5.1-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rms/arm64 r-base
• r-cran-rms/armhf (5.1-4-1 to 5.1-4-1)
  • Migration status for r-cran-rms/armhf (5.1-4-1 to 5.1-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rms/armhf r-base
• r-cran-rms/i386 (5.1-4-1 to 5.1-4-1)
  • Migration status for r-cran-rms/i386 (5.1-4-1 to 5.1-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rms/i386 r-base
• r-cran-rms/mips64el (5.1-4-1 to 5.1-4-1)
  • Migration status for r-cran-rms/mips64el (5.1-4-1 to 5.1-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rms/mips64el r-base
• r-cran-rms/mipsel (5.1-4-1 to 5.1-4-1)
  • Migration status for r-cran-rms/mipsel (5.1-4-1 to 5.1-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rms/mipsel r-base
• r-cran-rms/ppc64el (5.1-4-1 to 5.1-4-1)
  • Migration status for r-cran-rms/ppc64el (5.1-4-1 to 5.1-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rms/ppc64el r-base
• r-cran-rms/s390x (5.1-4-1 to 5.1-4-1)
  • Migration status for r-cran-rms/s390x (5.1-4-1 to 5.1-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rms/s390x r-base
• r-cran-rncl/amd64 (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/amd64 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/amd64 r-base
• r-cran-rncl/arm64 (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/arm64 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/arm64 r-base
• r-cran-rncl/armel (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/armel (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/armel r-base
• r-cran-rncl/armhf (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/armhf (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/armhf r-base
• r-cran-rncl/i386 (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/i386 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/i386 r-base
• r-cran-rncl/mips64el (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/mips64el (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/mips64el r-base
• r-cran-rncl/mipsel (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/mipsel (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/mipsel r-base
• r-cran-rncl/ppc64el (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/ppc64el (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/ppc64el r-base
• r-cran-rncl/s390x (0.8.4-1 to 0.8.4-1)
  • Migration status for r-cran-rncl/s390x (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rncl/s390x r-base
• r-cran-rnetcdf/amd64 (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/amd64 (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/amd64 r-base
• r-cran-rnetcdf/arm64 (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/arm64 (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/arm64 r-base
• r-cran-rnetcdf/armel (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/armel (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/armel r-base
• r-cran-rnetcdf/armhf (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/armhf (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/armhf r-base
• r-cran-rnetcdf/i386 (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/i386 (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/i386 r-base
• r-cran-rnetcdf/mips64el (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/mips64el (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/mips64el r-base
• r-cran-rnetcdf/mipsel (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/mipsel (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/mipsel r-base
• r-cran-rnetcdf/ppc64el (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/ppc64el (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/ppc64el r-base
• r-cran-rnetcdf/s390x (2.3-1-1 to 2.3-1-1)
  • Migration status for r-cran-rnetcdf/s390x (2.3-1-1 to 2.3-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnetcdf/s390x r-base
• r-cran-rniftilib/amd64 (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/amd64 (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/amd64 r-base
• r-cran-rniftilib/arm64 (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/arm64 (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/arm64 r-base
• r-cran-rniftilib/armel (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/armel (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/armel r-base
• r-cran-rniftilib/armhf (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/armhf (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/armhf r-base
• r-cran-rniftilib/i386 (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/i386 (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/i386 r-base
• r-cran-rniftilib/mips64el (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/mips64el (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/mips64el r-base
• r-cran-rniftilib/mipsel (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/mipsel (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/mipsel r-base
• r-cran-rniftilib/ppc64el (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/ppc64el (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/ppc64el r-base
• r-cran-rniftilib/s390x (0.0-35.r79-5 to 0.0-35.r79-5)
  • Migration status for r-cran-rniftilib/s390x (0.0-35.r79-5 to 0.0-35.r79-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rniftilib/s390x r-base
• r-cran-robust/amd64 (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/amd64 (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/amd64 r-base
• r-cran-robust/arm64 (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/arm64 (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/arm64 r-base
• r-cran-robust/armel (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/armel (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/armel r-base
• r-cran-robust/armhf (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/armhf (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/armhf r-base
• r-cran-robust/i386 (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/i386 (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/i386 r-base
• r-cran-robust/mips64el (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/mips64el (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/mips64el r-base
• r-cran-robust/mipsel (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/mipsel (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/mipsel r-base
• r-cran-robust/ppc64el (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/ppc64el (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/ppc64el r-base
• r-cran-robust/s390x (0.5-0.0-1 to 0.5-0.0-1)
  • Migration status for r-cran-robust/s390x (0.5-0.0-1 to 0.5-0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robust/s390x r-base
• r-cran-rook/amd64 (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/amd64 (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/amd64 r-base
• r-cran-rook/arm64 (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/arm64 (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/arm64 r-base
• r-cran-rook/armel (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/armel (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/armel r-base
• r-cran-rook/armhf (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/armhf (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/armhf r-base
• r-cran-rook/i386 (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/i386 (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/i386 r-base
• r-cran-rook/mips64el (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/mips64el (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/mips64el r-base
• r-cran-rook/mipsel (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/mipsel (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/mipsel r-base
• r-cran-rook/ppc64el (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/ppc64el (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/ppc64el r-base
• r-cran-rook/s390x (1.1-1+dfsg-2 to 1.1-1+dfsg-2)
  • Migration status for r-cran-rook/s390x (1.1-1+dfsg-2 to 1.1-1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rook/s390x r-base
• r-cran-rpact/amd64 (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/amd64 (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/amd64 r-base
• r-cran-rpact/arm64 (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/arm64 (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/arm64 r-base
• r-cran-rpact/armel (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/armel (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/armel r-base
• r-cran-rpact/armhf (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/armhf (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/armhf r-base
• r-cran-rpact/i386 (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/i386 (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/i386 r-base
• r-cran-rpact/mips64el (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/mips64el (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/mips64el r-base
• r-cran-rpact/mipsel (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/mipsel (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/mipsel r-base
• r-cran-rpact/ppc64el (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/ppc64el (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/ppc64el r-base
• r-cran-rpact/s390x (2.0.6-1 to 2.0.6-1)
  • Migration status for r-cran-rpact/s390x (2.0.6-1 to 2.0.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpact/s390x r-base
• r-cran-rpf/amd64 (1.0.4+dfsg-1 to 1.0.4+dfsg-1)
  • Migration status for r-cran-rpf/amd64 (1.0.4+dfsg-1 to 1.0.4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpf/amd64 r-base
• r-cran-rpf/arm64 (1.0.4+dfsg-1 to 1.0.4+dfsg-1)
  • Migration status for r-cran-rpf/arm64 (1.0.4+dfsg-1 to 1.0.4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpf/arm64 r-base
• r-cran-rpf/armel (1.0.4+dfsg-1 to 1.0.4+dfsg-1)
  • Migration status for r-cran-rpf/armel (1.0.4+dfsg-1 to 1.0.4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpf/armel r-base
• r-cran-rpf/armhf (1.0.4+dfsg-1 to 1.0.4+dfsg-1)
  • Migration status for r-cran-rpf/armhf (1.0.4+dfsg-1 to 1.0.4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpf/armhf r-base
• r-cran-rpf/i386 (1.0.4+dfsg-1 to 1.0.4+dfsg-1)
  • Migration status for r-cran-rpf/i386 (1.0.4+dfsg-1 to 1.0.4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpf/i386 r-base
• r-cran-rpf/ppc64el (1.0.4+dfsg-1 to 1.0.4+dfsg-1)
  • Migration status for r-cran-rpf/ppc64el (1.0.4+dfsg-1 to 1.0.4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpf/ppc64el r-base
• r-cran-rpf/s390x (1.0.4+dfsg-1 to 1.0.4+dfsg-1)
  • Migration status for r-cran-rpf/s390x (1.0.4+dfsg-1 to 1.0.4+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpf/s390x r-base
• r-cran-rpostgresql/amd64 (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/amd64 (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/amd64 r-base
• r-cran-rpostgresql/arm64 (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/arm64 (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/arm64 r-base
• r-cran-rpostgresql/armel (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/armel (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/armel r-base
• r-cran-rpostgresql/armhf (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/armhf (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/armhf r-base
• r-cran-rpostgresql/i386 (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/i386 (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/i386 r-base
• r-cran-rpostgresql/mips64el (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/mips64el (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/mips64el r-base
• r-cran-rpostgresql/mipsel (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/mipsel (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/mipsel r-base
• r-cran-rpostgresql/ppc64el (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/ppc64el (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/ppc64el r-base
• r-cran-rpostgresql/s390x (0.6-2+dfsg-2 to 0.6-2+dfsg-2)
  • Migration status for r-cran-rpostgresql/s390x (0.6-2+dfsg-2 to 0.6-2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rpostgresql/s390x r-base
• r-cran-rprotobuf/amd64 (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/amd64 (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/amd64 r-base
• r-cran-rprotobuf/arm64 (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/arm64 (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/arm64 r-base
• r-cran-rprotobuf/armel (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/armel (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/armel r-base
• r-cran-rprotobuf/armhf (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/armhf (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/armhf r-base
• r-cran-rprotobuf/i386 (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/i386 (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/i386 r-base
• r-cran-rprotobuf/mips64el (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/mips64el (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/mips64el r-base
• r-cran-rprotobuf/mipsel (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/mipsel (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/mipsel r-base
• r-cran-rprotobuf/ppc64el (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/ppc64el (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/ppc64el r-base
• r-cran-rprotobuf/s390x (0.4.17-1 to 0.4.17-1)
  • Migration status for r-cran-rprotobuf/s390x (0.4.17-1 to 0.4.17-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprotobuf/s390x r-base
• r-cran-rrcov/amd64 (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/amd64 (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/amd64 r-base
• r-cran-rrcov/arm64 (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/arm64 (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/arm64 r-base
• r-cran-rrcov/armel (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/armel (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/armel r-base
• r-cran-rrcov/armhf (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/armhf (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/armhf r-base
• r-cran-rrcov/i386 (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/i386 (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/i386 r-base
• r-cran-rrcov/mips64el (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/mips64el (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/mips64el r-base
• r-cran-rrcov/mipsel (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/mipsel (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/mipsel r-base
• r-cran-rrcov/ppc64el (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/ppc64el (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/ppc64el r-base
• r-cran-rrcov/s390x (1.5-2-1 to 1.5-2-1)
  • Migration status for r-cran-rrcov/s390x (1.5-2-1 to 1.5-2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rrcov/s390x r-base
• r-cran-rsclient/amd64 (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/amd64 (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/amd64 r-base
• r-cran-rsclient/arm64 (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/arm64 (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/arm64 r-base
• r-cran-rsclient/armel (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/armel (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/armel r-base
• r-cran-rsclient/armhf (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/armhf (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/armhf r-base
• r-cran-rsclient/i386 (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/i386 (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/i386 r-base
• r-cran-rsclient/mips64el (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/mips64el (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/mips64el r-base
• r-cran-rsclient/mipsel (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/mipsel (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/mipsel r-base
• r-cran-rsclient/ppc64el (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/ppc64el (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/ppc64el r-base
• r-cran-rsclient/s390x (0.7-3-2 to 0.7-3-2)
  • Migration status for r-cran-rsclient/s390x (0.7-3-2 to 0.7-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsclient/s390x r-base
• r-cran-rsgcc/amd64 (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/amd64 (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/amd64 r-base
• r-cran-rsgcc/arm64 (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/arm64 (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/arm64 r-base
• r-cran-rsgcc/armel (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/armel (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/armel r-base
• r-cran-rsgcc/armhf (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/armhf (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/armhf r-base
• r-cran-rsgcc/i386 (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/i386 (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/i386 r-base
• r-cran-rsgcc/mips64el (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/mips64el (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/mips64el r-base
• r-cran-rsgcc/mipsel (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/mipsel (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/mipsel r-base
• r-cran-rsgcc/ppc64el (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/ppc64el (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/ppc64el r-base
• r-cran-rsgcc/s390x (1.0.6-2 to 1.0.6-2)
  • Migration status for r-cran-rsgcc/s390x (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsgcc/s390x r-base
• r-cran-rspectra/amd64 (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/amd64 (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/amd64 r-base
• r-cran-rspectra/arm64 (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/arm64 (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/arm64 r-base
• r-cran-rspectra/armel (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/armel (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/armel r-base
• r-cran-rspectra/armhf (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/armhf (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/armhf r-base
• r-cran-rspectra/i386 (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/i386 (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/i386 r-base
• r-cran-rspectra/mips64el (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/mips64el (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/mips64el r-base
• r-cran-rspectra/mipsel (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/mipsel (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/mipsel r-base
• r-cran-rspectra/ppc64el (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/ppc64el (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/ppc64el r-base
• r-cran-rspectra/s390x (0.16-0-1 to 0.16-0-1)
  • Migration status for r-cran-rspectra/s390x (0.16-0-1 to 0.16-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rspectra/s390x r-base
• r-cran-rsqlite/amd64 (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/amd64 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/amd64 r-base
• r-cran-rsqlite/arm64 (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/arm64 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/arm64 r-base
• r-cran-rsqlite/armel (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/armel (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/armel r-base
• r-cran-rsqlite/armhf (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/armhf (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/armhf r-base
• r-cran-rsqlite/i386 (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/i386 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/i386 r-base
• r-cran-rsqlite/mips64el (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/mips64el (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/mips64el r-base
• r-cran-rsqlite/mipsel (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/mipsel (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/mipsel r-base
• r-cran-rsqlite/ppc64el (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/ppc64el (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/ppc64el r-base
• r-cran-rsqlite/s390x (2.2.0-1 to 2.2.0-1)
  • Migration status for r-cran-rsqlite/s390x (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsqlite/s390x r-base
• r-cran-rstan/amd64 (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstan/amd64 (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstan/amd64 r-base
• r-cran-rstan/arm64 (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstan/arm64 (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstan/arm64 r-base
• r-cran-rstan/armel (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstan/armel (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstan/armel r-base
• r-cran-rstan/armhf (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstan/armhf (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstan/armhf r-base
• r-cran-rstan/i386 (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstan/i386 (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstan/i386 r-base
• r-cran-rstan/mips64el (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstan/mips64el (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstan/mips64el r-base
• r-cran-rstan/ppc64el (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstan/ppc64el (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstan/ppc64el r-base
• r-cran-rstan/s390x (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstan/s390x (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstan/s390x r-base
• r-cran-rstanarm/amd64 (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstanarm/amd64 (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstanarm/amd64 r-base
• r-cran-rstanarm/arm64 (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstanarm/arm64 (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstanarm/arm64 r-base
• r-cran-rstanarm/armhf (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstanarm/armhf (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstanarm/armhf r-base
• r-cran-rstanarm/i386 (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstanarm/i386 (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstanarm/i386 r-base
• r-cran-rstanarm/mips64el (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstanarm/mips64el (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstanarm/mips64el r-base
• r-cran-rstanarm/ppc64el (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstanarm/ppc64el (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstanarm/ppc64el r-base
• r-cran-rstanarm/s390x (2.19.3-1 to 2.19.3-1)
  • Migration status for r-cran-rstanarm/s390x (2.19.3-1 to 2.19.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstanarm/s390x r-base
• r-cran-rtsne/amd64 (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/amd64 (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/amd64 r-base
• r-cran-rtsne/arm64 (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/arm64 (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/arm64 r-base
• r-cran-rtsne/armel (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/armel (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/armel r-base
• r-cran-rtsne/armhf (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/armhf (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/armhf r-base
• r-cran-rtsne/i386 (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/i386 (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/i386 r-base
• r-cran-rtsne/mips64el (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/mips64el (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/mips64el r-base
• r-cran-rtsne/mipsel (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/mipsel (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/mipsel r-base
• r-cran-rtsne/ppc64el (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/ppc64el (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/ppc64el r-base
• r-cran-rtsne/s390x (0.15-2 to 0.15-2)
  • Migration status for r-cran-rtsne/s390x (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rtsne/s390x r-base
• r-cran-rwave/amd64 (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/amd64 (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/amd64 r-base
• r-cran-rwave/arm64 (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/arm64 (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/arm64 r-base
• r-cran-rwave/armel (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/armel (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/armel r-base
• r-cran-rwave/armhf (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/armhf (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/armhf r-base
• r-cran-rwave/i386 (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/i386 (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/i386 r-base
• r-cran-rwave/mips64el (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/mips64el (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/mips64el r-base
• r-cran-rwave/mipsel (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/mipsel (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/mipsel r-base
• r-cran-rwave/ppc64el (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/ppc64el (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/ppc64el r-base
• r-cran-rwave/s390x (2.4-8-2 to 2.4-8-2)
  • Migration status for r-cran-rwave/s390x (2.4-8-2 to 2.4-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwave/s390x r-base
• r-cran-rwiener/amd64 (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/amd64 (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/amd64 r-base
• r-cran-rwiener/arm64 (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/arm64 (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/arm64 r-base
• r-cran-rwiener/armel (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/armel (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/armel r-base
• r-cran-rwiener/armhf (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/armhf (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/armhf r-base
• r-cran-rwiener/i386 (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/i386 (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/i386 r-base
• r-cran-rwiener/mips64el (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/mips64el (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/mips64el r-base
• r-cran-rwiener/mipsel (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/mipsel (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/mipsel r-base
• r-cran-rwiener/ppc64el (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/ppc64el (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/ppc64el r-base
• r-cran-rwiener/s390x (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/s390x (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rwiener/s390x r-base
• r-cran-samr/amd64 (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/amd64 (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/amd64 r-base
• r-cran-samr/arm64 (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/arm64 (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/arm64 r-base
• r-cran-samr/armel (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/armel (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/armel r-base
• r-cran-samr/armhf (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/armhf (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/armhf r-base
• r-cran-samr/i386 (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/i386 (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/i386 r-base
• r-cran-samr/mips64el (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/mips64el (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/mips64el r-base
• r-cran-samr/mipsel (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/mipsel (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/mipsel r-base
• r-cran-samr/ppc64el (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/ppc64el (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/ppc64el r-base
• r-cran-samr/s390x (3.0-1 to 3.0-1)
  • Migration status for r-cran-samr/s390x (3.0-1 to 3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-samr/s390x r-base
• r-cran-satellite/amd64 (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/amd64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/amd64 r-base
• r-cran-satellite/arm64 (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/arm64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/arm64 r-base
• r-cran-satellite/armel (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/armel (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/armel r-base
• r-cran-satellite/armhf (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/armhf (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/armhf r-base
• r-cran-satellite/i386 (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/i386 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/i386 r-base
• r-cran-satellite/mips64el (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/mips64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/mips64el r-base
• r-cran-satellite/mipsel (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/mipsel (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/mipsel r-base
• r-cran-satellite/ppc64el (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/ppc64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/ppc64el r-base
• r-cran-satellite/s390x (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-satellite/s390x (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-satellite/s390x r-base
• r-cran-sctransform/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/amd64 r-base
• r-cran-sctransform/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/arm64 r-base
• r-cran-sctransform/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/armel r-base
• r-cran-sctransform/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/armhf r-base
• r-cran-sctransform/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/i386 r-base
• r-cran-sctransform/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/mips64el r-base
• r-cran-sctransform/mipsel (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/mipsel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/mipsel r-base
• r-cran-sctransform/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/ppc64el r-base
• r-cran-sctransform/s390x (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-sctransform/s390x (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sctransform/s390x r-base
• r-cran-sdmtools/amd64 (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/amd64 (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/amd64 r-base
• r-cran-sdmtools/arm64 (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/arm64 (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/arm64 r-base
• r-cran-sdmtools/armel (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/armel (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/armel r-base
• r-cran-sdmtools/armhf (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/armhf (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/armhf r-base
• r-cran-sdmtools/i386 (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/i386 (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/i386 r-base
• r-cran-sdmtools/mips64el (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/mips64el (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/mips64el r-base
• r-cran-sdmtools/mipsel (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/mipsel (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/mipsel r-base
• r-cran-sdmtools/ppc64el (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/ppc64el (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/ppc64el r-base
• r-cran-sdmtools/s390x (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/s390x (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sdmtools/s390x r-base
• r-cran-seqinr/amd64 (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/amd64 (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/amd64 r-base
• r-cran-seqinr/arm64 (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/arm64 (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/arm64 r-base
• r-cran-seqinr/armel (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/armel (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/armel r-base
• r-cran-seqinr/armhf (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/armhf (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/armhf r-base
• r-cran-seqinr/i386 (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/i386 (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/i386 r-base
• r-cran-seqinr/mips64el (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/mips64el (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/mips64el r-base
• r-cran-seqinr/mipsel (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/mipsel (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/mipsel r-base
• r-cran-seqinr/ppc64el (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/ppc64el (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/ppc64el r-base
• r-cran-seqinr/s390x (3.6-1-1 to 3.6-1-1)
  • Migration status for r-cran-seqinr/s390x (3.6-1-1 to 3.6-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seqinr/s390x r-base
• r-cran-seriation/amd64 (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/amd64 (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/amd64 r-base
• r-cran-seriation/arm64 (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/arm64 (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/arm64 r-base
• r-cran-seriation/armel (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/armel (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/armel r-base
• r-cran-seriation/armhf (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/armhf (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/armhf r-base
• r-cran-seriation/i386 (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/i386 (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/i386 r-base
• r-cran-seriation/mips64el (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/mips64el (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/mips64el r-base
• r-cran-seriation/mipsel (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/mipsel (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/mipsel r-base
• r-cran-seriation/ppc64el (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/ppc64el (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/ppc64el r-base
• r-cran-seriation/s390x (1.2-8-1 to 1.2-8-1)
  • Migration status for r-cran-seriation/s390x (1.2-8-1 to 1.2-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seriation/s390x r-base
• r-cran-seurat/amd64 (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/amd64 (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/amd64 r-base
• r-cran-seurat/arm64 (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/arm64 (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/arm64 r-base
• r-cran-seurat/armel (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/armel (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/armel r-base
• r-cran-seurat/armhf (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/armhf (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/armhf r-base
• r-cran-seurat/i386 (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/i386 (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/i386 r-base
• r-cran-seurat/mips64el (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/mips64el (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/mips64el r-base
• r-cran-seurat/mipsel (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/mipsel (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/mipsel r-base
• r-cran-seurat/ppc64el (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/ppc64el (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/ppc64el r-base
• r-cran-seurat/s390x (3.1.5-1 to 3.1.5-1)
  • Migration status for r-cran-seurat/s390x (3.1.5-1 to 3.1.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seurat/s390x r-base
• r-cran-sf/amd64 (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/amd64 (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/amd64 r-base
• r-cran-sf/arm64 (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/arm64 (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/arm64 r-base
• r-cran-sf/armel (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/armel (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/armel r-base
• r-cran-sf/armhf (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/armhf (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/armhf r-base
• r-cran-sf/i386 (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/i386 (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/i386 r-base
• r-cran-sf/mips64el (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/mips64el (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/mips64el r-base
• r-cran-sf/mipsel (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/mipsel (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/mipsel r-base
• r-cran-sf/ppc64el (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/ppc64el (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/ppc64el r-base
• r-cran-sf/s390x (0.9-3+dfsg-1 to 0.9-3+dfsg-1)
  • Migration status for r-cran-sf/s390x (0.9-3+dfsg-1 to 0.9-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sf/s390x r-base
• r-cran-sitmo/amd64 (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/amd64 (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/amd64 r-base
• r-cran-sitmo/arm64 (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/arm64 (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/arm64 r-base
• r-cran-sitmo/armel (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/armel (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/armel r-base
• r-cran-sitmo/armhf (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/armhf (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/armhf r-base
• r-cran-sitmo/i386 (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/i386 (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/i386 r-base
• r-cran-sitmo/mips64el (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/mips64el (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/mips64el r-base
• r-cran-sitmo/mipsel (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/mipsel (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/mipsel r-base
• r-cran-sitmo/ppc64el (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/ppc64el (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/ppc64el r-base
• r-cran-sitmo/s390x (2.0.1-2 to 2.0.1-2)
  • Migration status for r-cran-sitmo/s390x (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sitmo/s390x r-base
• r-cran-slam/amd64 (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/amd64 (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/amd64 r-base
• r-cran-slam/arm64 (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/arm64 (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/arm64 r-base
• r-cran-slam/armel (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/armel (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/armel r-base
• r-cran-slam/armhf (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/armhf (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/armhf r-base
• r-cran-slam/i386 (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/i386 (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/i386 r-base
• r-cran-slam/mips64el (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/mips64el (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/mips64el r-base
• r-cran-slam/mipsel (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/mipsel (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/mipsel r-base
• r-cran-slam/ppc64el (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/ppc64el (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/ppc64el r-base
• r-cran-slam/s390x (0.1-47-2 to 0.1-47-2)
  • Migration status for r-cran-slam/s390x (0.1-47-2 to 0.1-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-slam/s390x r-base
• r-cran-snowballc/amd64 (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/amd64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/amd64 r-base
• r-cran-snowballc/arm64 (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/arm64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/arm64 r-base
• r-cran-snowballc/armel (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/armel (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/armel r-base
• r-cran-snowballc/armhf (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/armhf (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/armhf r-base
• r-cran-snowballc/i386 (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/i386 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/i386 r-base
• r-cran-snowballc/mips64el (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/mips64el (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/mips64el r-base
• r-cran-snowballc/mipsel (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/mipsel (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/mipsel r-base
• r-cran-snowballc/ppc64el (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/ppc64el (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/ppc64el r-base
• r-cran-snowballc/s390x (0.7.0-1 to 0.7.0-1)
  • Migration status for r-cran-snowballc/s390x (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowballc/s390x r-base
• r-cran-sodium/amd64 (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/amd64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/amd64 r-base
• r-cran-sodium/arm64 (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/arm64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/arm64 r-base
• r-cran-sodium/armel (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/armel (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/armel r-base
• r-cran-sodium/armhf (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/armhf (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/armhf r-base
• r-cran-sodium/i386 (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/i386 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/i386 r-base
• r-cran-sodium/mips64el (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/mips64el (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/mips64el r-base
• r-cran-sodium/mipsel (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/mipsel (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/mipsel r-base
• r-cran-sodium/ppc64el (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/ppc64el (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/ppc64el r-base
• r-cran-sodium/s390x (1.1-1 to 1.1-1)
  • Migration status for r-cran-sodium/s390x (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sodium/s390x r-base
• r-cran-sourcetools/amd64 (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/amd64 (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/amd64 r-base
• r-cran-sourcetools/arm64 (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/arm64 (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/arm64 r-base
• r-cran-sourcetools/armel (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/armel (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/armel r-base
• r-cran-sourcetools/armhf (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/armhf (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/armhf r-base
• r-cran-sourcetools/i386 (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/i386 (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/i386 r-base
• r-cran-sourcetools/mips64el (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/mips64el (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/mips64el r-base
• r-cran-sourcetools/mipsel (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/mipsel (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/mipsel r-base
• r-cran-sourcetools/ppc64el (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/ppc64el (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/ppc64el r-base
• r-cran-sourcetools/s390x (0.1.7-2 to 0.1.7-2)
  • Migration status for r-cran-sourcetools/s390x (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sourcetools/s390x r-base
• r-cran-spam/amd64 (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/amd64 (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/amd64 r-base
• r-cran-spam/arm64 (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/arm64 (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/arm64 r-base
• r-cran-spam/armel (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/armel (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/armel r-base
• r-cran-spam/armhf (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/armhf (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/armhf r-base
• r-cran-spam/i386 (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/i386 (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/i386 r-base
• r-cran-spam/mips64el (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/mips64el (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/mips64el r-base
• r-cran-spam/mipsel (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/mipsel (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/mipsel r-base
• r-cran-spam/ppc64el (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/ppc64el (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/ppc64el r-base
• r-cran-spam/s390x (2.5-1-1 to 2.5-1-1)
  • Migration status for r-cran-spam/s390x (2.5-1-1 to 2.5-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spam/s390x r-base
• r-cran-sparsem/amd64 (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/amd64 (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/amd64 r-base
• r-cran-sparsem/arm64 (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/arm64 (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/arm64 r-base
• r-cran-sparsem/armel (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/armel (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/armel r-base
• r-cran-sparsem/armhf (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/armhf (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/armhf r-base
• r-cran-sparsem/i386 (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/i386 (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/i386 r-base
• r-cran-sparsem/mips64el (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/mips64el (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/mips64el r-base
• r-cran-sparsem/mipsel (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/mipsel (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/mipsel r-base
• r-cran-sparsem/ppc64el (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/ppc64el (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/ppc64el r-base
• r-cran-sparsem/s390x (1.78-1 to 1.78-1)
  • Migration status for r-cran-sparsem/s390x (1.78-1 to 1.78-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sparsem/s390x r-base
• r-cran-spatial/amd64 (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/amd64 (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/amd64 r-base
• r-cran-spatial/arm64 (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/arm64 (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/arm64 r-base
• r-cran-spatial/armel (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/armel (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/armel r-base
• r-cran-spatial/armhf (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/armhf (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/armhf r-base
• r-cran-spatial/i386 (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/i386 (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/i386 r-base
• r-cran-spatial/mips64el (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/mips64el (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/mips64el r-base
• r-cran-spatial/mipsel (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/mipsel (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/mipsel r-base
• r-cran-spatial/ppc64el (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/ppc64el (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/ppc64el r-base
• r-cran-spatial/s390x (7.3-12-1 to 7.3-12-1)
  • Migration status for r-cran-spatial/s390x (7.3-12-1 to 7.3-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatial/s390x r-base
• r-cran-spatialreg/amd64 (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/amd64 (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/amd64 r-base
• r-cran-spatialreg/arm64 (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/arm64 (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/arm64 r-base
• r-cran-spatialreg/armel (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/armel (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/armel r-base
• r-cran-spatialreg/armhf (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/armhf (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/armhf r-base
• r-cran-spatialreg/i386 (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/i386 (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/i386 r-base
• r-cran-spatialreg/mips64el (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/mips64el (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/mips64el r-base
• r-cran-spatialreg/mipsel (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/mipsel (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/mipsel r-base
• r-cran-spatialreg/ppc64el (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/ppc64el (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/ppc64el r-base
• r-cran-spatialreg/s390x (1.1-5+dfsg-1 to 1.1-5+dfsg-1)
  • Migration status for r-cran-spatialreg/s390x (1.1-5+dfsg-1 to 1.1-5+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatialreg/s390x r-base
• r-cran-spatstat.utils/amd64 (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/amd64 (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/amd64 r-base
• r-cran-spatstat.utils/arm64 (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/arm64 (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/arm64 r-base
• r-cran-spatstat.utils/armel (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/armel (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/armel r-base
• r-cran-spatstat.utils/armhf (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/armhf (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/armhf r-base
• r-cran-spatstat.utils/i386 (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/i386 (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/i386 r-base
• r-cran-spatstat.utils/mips64el (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/mips64el (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/mips64el r-base
• r-cran-spatstat.utils/mipsel (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/mipsel (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/mipsel r-base
• r-cran-spatstat.utils/ppc64el (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/ppc64el (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/ppc64el r-base
• r-cran-spatstat.utils/s390x (1.17-0-1 to 1.17-0-1)
  • Migration status for r-cran-spatstat.utils/s390x (1.17-0-1 to 1.17-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.utils/s390x r-base
• r-cran-spdep/amd64 (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/amd64 (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/amd64 r-base
• r-cran-spdep/arm64 (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/arm64 (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/arm64 r-base
• r-cran-spdep/armel (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/armel (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/armel r-base
• r-cran-spdep/armhf (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/armhf (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/armhf r-base
• r-cran-spdep/i386 (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/i386 (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/i386 r-base
• r-cran-spdep/mips64el (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/mips64el (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/mips64el r-base
• r-cran-spdep/mipsel (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/mipsel (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/mipsel r-base
• r-cran-spdep/ppc64el (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/ppc64el (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/ppc64el r-base
• r-cran-spdep/s390x (1.1-3+dfsg-1 to 1.1-3+dfsg-1)
  • Migration status for r-cran-spdep/s390x (1.1-3+dfsg-1 to 1.1-3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdep/s390x r-base
• r-cran-spp/amd64 (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/amd64 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/amd64 r-base
• r-cran-spp/arm64 (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/arm64 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/arm64 r-base
• r-cran-spp/armel (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/armel (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/armel r-base
• r-cran-spp/armhf (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/armhf (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/armhf r-base
• r-cran-spp/i386 (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/i386 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/i386 r-base
• r-cran-spp/mips64el (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/mips64el (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/mips64el r-base
• r-cran-spp/mipsel (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/mipsel (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/mipsel r-base
• r-cran-spp/ppc64el (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/ppc64el (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/ppc64el r-base
• r-cran-spp/s390x (1.16.0-1 to 1.16.0-1)
  • Migration status for r-cran-spp/s390x (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spp/s390x r-base
• r-cran-stanheaders/amd64 (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/amd64 (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/amd64 r-base
• r-cran-stanheaders/arm64 (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/arm64 (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/arm64 r-base
• r-cran-stanheaders/armel (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/armel (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/armel r-base
• r-cran-stanheaders/armhf (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/armhf (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/armhf r-base
• r-cran-stanheaders/i386 (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/i386 (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/i386 r-base
• r-cran-stanheaders/mips64el (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/mips64el (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/mips64el r-base
• r-cran-stanheaders/mipsel (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/mipsel (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/mipsel r-base
• r-cran-stanheaders/ppc64el (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/ppc64el (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/ppc64el r-base
• r-cran-stanheaders/s390x (2.21.0-1-1 to 2.21.0-1-1)
  • Migration status for r-cran-stanheaders/s390x (2.21.0-1-1 to 2.21.0-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stanheaders/s390x r-base
• r-cran-statmod/amd64 (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/amd64 (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/amd64 r-base
• r-cran-statmod/arm64 (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/arm64 (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/arm64 r-base
• r-cran-statmod/armel (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/armel (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/armel r-base
• r-cran-statmod/armhf (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/armhf (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/armhf r-base
• r-cran-statmod/i386 (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/i386 (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/i386 r-base
• r-cran-statmod/mips64el (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/mips64el (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/mips64el r-base
• r-cran-statmod/mipsel (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/mipsel (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/mipsel r-base
• r-cran-statmod/ppc64el (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/ppc64el (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/ppc64el r-base
• r-cran-statmod/s390x (1.4.34-1 to 1.4.34-1)
  • Migration status for r-cran-statmod/s390x (1.4.34-1 to 1.4.34-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-statmod/s390x r-base
• r-cran-stringdist/amd64 (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/amd64 (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/amd64 r-base
• r-cran-stringdist/arm64 (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/arm64 (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/arm64 r-base
• r-cran-stringdist/armel (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/armel (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/armel r-base
• r-cran-stringdist/armhf (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/armhf (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/armhf r-base
• r-cran-stringdist/i386 (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/i386 (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/i386 r-base
• r-cran-stringdist/mips64el (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/mips64el (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/mips64el r-base
• r-cran-stringdist/mipsel (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/mipsel (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/mipsel r-base
• r-cran-stringdist/ppc64el (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/ppc64el (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/ppc64el r-base
• r-cran-stringdist/s390x (0.9.5.5-1 to 0.9.5.5-1)
  • Migration status for r-cran-stringdist/s390x (0.9.5.5-1 to 0.9.5.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringdist/s390x r-base
• r-cran-stringi/amd64 (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/amd64 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/amd64 r-base
• r-cran-stringi/arm64 (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/arm64 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/arm64 r-base
• r-cran-stringi/armel (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/armel (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/armel r-base
• r-cran-stringi/armhf (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/armhf (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/armhf r-base
• r-cran-stringi/i386 (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/i386 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/i386 r-base
• r-cran-stringi/mips64el (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/mips64el (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/mips64el r-base
• r-cran-stringi/mipsel (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/mipsel (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/mipsel r-base
• r-cran-stringi/ppc64el (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/ppc64el (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/ppc64el r-base
• r-cran-stringi/s390x (1.4.6-1 to 1.4.6-1)
  • Migration status for r-cran-stringi/s390x (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringi/s390x r-base
• r-cran-surveillance/amd64 (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/amd64 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/amd64 r-base
• r-cran-surveillance/arm64 (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/arm64 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/arm64 r-base
• r-cran-surveillance/armel (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/armel (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/armel r-base
• r-cran-surveillance/armhf (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/armhf (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/armhf r-base
• r-cran-surveillance/i386 (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/i386 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/i386 r-base
• r-cran-surveillance/mips64el (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/mips64el (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/mips64el r-base
• r-cran-surveillance/mipsel (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/mipsel (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/mipsel r-base
• r-cran-surveillance/ppc64el (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/ppc64el (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/ppc64el r-base
• r-cran-surveillance/s390x (1.18.0-1 to 1.18.0-1)
  • Migration status for r-cran-surveillance/s390x (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-surveillance/s390x r-base
• r-cran-sys/amd64 (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/amd64 (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/amd64 r-base
• r-cran-sys/arm64 (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/arm64 (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/arm64 r-base
• r-cran-sys/armel (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/armel (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/armel r-base
• r-cran-sys/armhf (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/armhf (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/armhf r-base
• r-cran-sys/i386 (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/i386 (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/i386 r-base
• r-cran-sys/mips64el (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/mips64el (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/mips64el r-base
• r-cran-sys/mipsel (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/mipsel (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/mipsel r-base
• r-cran-sys/ppc64el (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/ppc64el (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/ppc64el r-base
• r-cran-sys/s390x (3.3-1 to 3.3-1)
  • Migration status for r-cran-sys/s390x (3.3-1 to 3.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sys/s390x r-base
• r-cran-tcr/amd64 (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/amd64 (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/amd64 r-base
• r-cran-tcr/arm64 (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/arm64 (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/arm64 r-base
• r-cran-tcr/armel (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/armel (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/armel r-base
• r-cran-tcr/armhf (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/armhf (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/armhf r-base
• r-cran-tcr/i386 (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/i386 (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/i386 r-base
• r-cran-tcr/mips64el (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/mips64el (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/mips64el r-base
• r-cran-tcr/mipsel (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/mipsel (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/mipsel r-base
• r-cran-tcr/ppc64el (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/ppc64el (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/ppc64el r-base
• r-cran-tcr/s390x (2.2.4.1-1 to 2.2.4.1-1)
  • Migration status for r-cran-tcr/s390x (2.2.4.1-1 to 2.2.4.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tcr/s390x r-base
• r-cran-tfmpvalue/amd64 (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/amd64 (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/amd64 r-base
• r-cran-tfmpvalue/arm64 (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/arm64 (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/arm64 r-base
• r-cran-tfmpvalue/armel (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/armel (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/armel r-base
• r-cran-tfmpvalue/armhf (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/armhf (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/armhf r-base
• r-cran-tfmpvalue/i386 (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/i386 (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/i386 r-base
• r-cran-tfmpvalue/mips64el (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/mips64el (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/mips64el r-base
• r-cran-tfmpvalue/mipsel (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/mipsel (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/mipsel r-base
• r-cran-tfmpvalue/ppc64el (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/ppc64el (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/ppc64el r-base
• r-cran-tfmpvalue/s390x (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-tfmpvalue/s390x (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfmpvalue/s390x r-base
• r-cran-tgp/amd64 (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/amd64 (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/amd64 r-base
• r-cran-tgp/arm64 (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/arm64 (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/arm64 r-base
• r-cran-tgp/armel (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/armel (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/armel r-base
• r-cran-tgp/armhf (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/armhf (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/armhf r-base
• r-cran-tgp/i386 (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/i386 (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/i386 r-base
• r-cran-tgp/mips64el (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/mips64el (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/mips64el r-base
• r-cran-tgp/mipsel (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/mipsel (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/mipsel r-base
• r-cran-tgp/ppc64el (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/ppc64el (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/ppc64el r-base
• r-cran-tgp/s390x (2.4-14-4 to 2.4-14-4)
  • Migration status for r-cran-tgp/s390x (2.4-14-4 to 2.4-14-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tgp/s390x r-base
• r-cran-tibble/amd64 (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/amd64 (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/amd64 r-base
• r-cran-tibble/arm64 (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/arm64 (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/arm64 r-base
• r-cran-tibble/armel (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/armel (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/armel r-base
• r-cran-tibble/armhf (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/armhf (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/armhf r-base
• r-cran-tibble/i386 (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/i386 (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/i386 r-base
• r-cran-tibble/mips64el (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/mips64el (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/mips64el r-base
• r-cran-tibble/mipsel (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/mipsel (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/mipsel r-base
• r-cran-tibble/ppc64el (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/ppc64el (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/ppc64el r-base
• r-cran-tibble/s390x (3.0.1-1 to 3.0.1-1)
  • Migration status for r-cran-tibble/s390x (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tibble/s390x r-base
• r-cran-tidyr/amd64 (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/amd64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/amd64 r-base
• r-cran-tidyr/arm64 (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/arm64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/arm64 r-base
• r-cran-tidyr/armel (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/armel (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/armel r-base
• r-cran-tidyr/armhf (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/armhf (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/armhf r-base
• r-cran-tidyr/i386 (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/i386 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/i386 r-base
• r-cran-tidyr/mips64el (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/mips64el (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/mips64el r-base
• r-cran-tidyr/mipsel (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/mipsel (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/mipsel r-base
• r-cran-tidyr/ppc64el (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/ppc64el (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/ppc64el r-base
• r-cran-tidyr/s390x (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-tidyr/s390x (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyr/s390x r-base
• r-cran-tiff/amd64 (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/amd64 (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/amd64 r-base
• r-cran-tiff/arm64 (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/arm64 (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/arm64 r-base
• r-cran-tiff/armel (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/armel (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/armel r-base
• r-cran-tiff/armhf (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/armhf (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/armhf r-base
• r-cran-tiff/i386 (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/i386 (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/i386 r-base
• r-cran-tiff/mips64el (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/mips64el (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/mips64el r-base
• r-cran-tiff/mipsel (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/mipsel (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/mipsel r-base
• r-cran-tiff/ppc64el (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/ppc64el (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/ppc64el r-base
• r-cran-tiff/s390x (0.1-5-1 to 0.1-5-1)
  • Migration status for r-cran-tiff/s390x (0.1-5-1 to 0.1-5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tiff/s390x r-base
• r-cran-tikzdevice/amd64 (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/amd64 (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/amd64 r-base
• r-cran-tikzdevice/arm64 (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/arm64 (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/arm64 r-base
• r-cran-tikzdevice/armel (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/armel (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/armel r-base
• r-cran-tikzdevice/armhf (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/armhf (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/armhf r-base
• r-cran-tikzdevice/i386 (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/i386 (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/i386 r-base
• r-cran-tikzdevice/mips64el (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/mips64el (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/mips64el r-base
• r-cran-tikzdevice/mipsel (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/mipsel (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/mipsel r-base
• r-cran-tikzdevice/ppc64el (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/ppc64el (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/ppc64el r-base
• r-cran-tikzdevice/s390x (0.12.3-1 to 0.12.3-1)
  • Migration status for r-cran-tikzdevice/s390x (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tikzdevice/s390x r-base
• r-cran-timedate/amd64 (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/amd64 (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/amd64 r-base
• r-cran-timedate/arm64 (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/arm64 (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/arm64 r-base
• r-cran-timedate/armel (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/armel (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/armel r-base
• r-cran-timedate/armhf (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/armhf (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/armhf r-base
• r-cran-timedate/i386 (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/i386 (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/i386 r-base
• r-cran-timedate/mips64el (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/mips64el (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/mips64el r-base
• r-cran-timedate/mipsel (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/mipsel (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/mipsel r-base
• r-cran-timedate/ppc64el (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/ppc64el (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/ppc64el r-base
• r-cran-timedate/s390x (3043.102-1 to 3043.102-1)
  • Migration status for r-cran-timedate/s390x (3043.102-1 to 3043.102-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timedate/s390x r-base
• r-cran-timereg/amd64 (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/amd64 (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/amd64 r-base
• r-cran-timereg/arm64 (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/arm64 (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/arm64 r-base
• r-cran-timereg/armel (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/armel (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/armel r-base
• r-cran-timereg/armhf (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/armhf (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/armhf r-base
• r-cran-timereg/i386 (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/i386 (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/i386 r-base
• r-cran-timereg/mips64el (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/mips64el (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/mips64el r-base
• r-cran-timereg/mipsel (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/mipsel (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/mipsel r-base
• r-cran-timereg/ppc64el (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/ppc64el (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/ppc64el r-base
• r-cran-timereg/s390x (1.9.4-1 to 1.9.4-1)
  • Migration status for r-cran-timereg/s390x (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-timereg/s390x r-base
• r-cran-tm/amd64 (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/amd64 (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/amd64 r-base
• r-cran-tm/arm64 (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/arm64 (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/arm64 r-base
• r-cran-tm/armel (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/armel (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/armel r-base
• r-cran-tm/armhf (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/armhf (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/armhf r-base
• r-cran-tm/i386 (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/i386 (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/i386 r-base
• r-cran-tm/mips64el (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/mips64el (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/mips64el r-base
• r-cran-tm/mipsel (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/mipsel (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/mipsel r-base
• r-cran-tm/ppc64el (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/ppc64el (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/ppc64el r-base
• r-cran-tm/s390x (0.7-7-2 to 0.7-7-2)
  • Migration status for r-cran-tm/s390x (0.7-7-2 to 0.7-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tm/s390x r-base
• r-cran-tmb/amd64 (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/amd64 (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/amd64 r-base
• r-cran-tmb/arm64 (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/arm64 (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/arm64 r-base
• r-cran-tmb/armel (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/armel (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/armel r-base
• r-cran-tmb/armhf (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/armhf (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/armhf r-base
• r-cran-tmb/i386 (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/i386 (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/i386 r-base
• r-cran-tmb/mips64el (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/mips64el (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/mips64el r-base
• r-cran-tmb/mipsel (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/mipsel (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/mipsel r-base
• r-cran-tmb/ppc64el (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/ppc64el (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/ppc64el r-base
• r-cran-tmb/s390x (1.7.16-1 to 1.7.16-1)
  • Migration status for r-cran-tmb/s390x (1.7.16-1 to 1.7.16-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmb/s390x r-base
• r-cran-tmvtnorm/amd64 (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/amd64 (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/amd64 r-base
• r-cran-tmvtnorm/arm64 (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/arm64 (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/arm64 r-base
• r-cran-tmvtnorm/armel (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/armel (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/armel r-base
• r-cran-tmvtnorm/armhf (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/armhf (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/armhf r-base
• r-cran-tmvtnorm/i386 (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/i386 (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/i386 r-base
• r-cran-tmvtnorm/mips64el (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/mips64el (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/mips64el r-base
• r-cran-tmvtnorm/mipsel (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/mipsel (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/mipsel r-base
• r-cran-tmvtnorm/ppc64el (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/ppc64el (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/ppc64el r-base
• r-cran-tmvtnorm/s390x (1.4-10-3 to 1.4-10-3)
  • Migration status for r-cran-tmvtnorm/s390x (1.4-10-3 to 1.4-10-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tmvtnorm/s390x r-base
• r-cran-transformr/amd64 (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/amd64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/amd64 r-base
• r-cran-transformr/arm64 (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/arm64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/arm64 r-base
• r-cran-transformr/armel (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/armel (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/armel r-base
• r-cran-transformr/armhf (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/armhf (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/armhf r-base
• r-cran-transformr/i386 (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/i386 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/i386 r-base
• r-cran-transformr/mips64el (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/mips64el (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/mips64el r-base
• r-cran-transformr/mipsel (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/mipsel (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/mipsel r-base
• r-cran-transformr/ppc64el (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/ppc64el (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/ppc64el r-base
• r-cran-transformr/s390x (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-transformr/s390x (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-transformr/s390x r-base
• r-cran-treespace/amd64 (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1)
  • Migration status for r-cran-treespace/amd64 (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treespace/amd64 r-base
• r-cran-treespace/arm64 (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1)
  • Migration status for r-cran-treespace/arm64 (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treespace/arm64 r-base
• r-cran-treespace/armhf (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1)
  • Migration status for r-cran-treespace/armhf (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treespace/armhf r-base
• r-cran-treespace/i386 (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1)
  • Migration status for r-cran-treespace/i386 (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treespace/i386 r-base
• r-cran-treespace/mips64el (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1)
  • Migration status for r-cran-treespace/mips64el (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treespace/mips64el r-base
• r-cran-treespace/mipsel (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1)
  • Migration status for r-cran-treespace/mipsel (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treespace/mipsel r-base
• r-cran-treespace/ppc64el (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1)
  • Migration status for r-cran-treespace/ppc64el (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treespace/ppc64el r-base
• r-cran-treespace/s390x (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1)
  • Migration status for r-cran-treespace/s390x (1.1.3.2+dfsg-1 to 1.1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treespace/s390x r-base
• r-cran-triebeard/amd64 (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/amd64 (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/amd64 r-base
• r-cran-triebeard/arm64 (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/arm64 (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/arm64 r-base
• r-cran-triebeard/armel (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/armel (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/armel r-base
• r-cran-triebeard/armhf (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/armhf (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/armhf r-base
• r-cran-triebeard/i386 (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/i386 (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/i386 r-base
• r-cran-triebeard/mips64el (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/mips64el (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/mips64el r-base
• r-cran-triebeard/mipsel (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/mipsel (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/mipsel r-base
• r-cran-triebeard/ppc64el (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/ppc64el (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/ppc64el r-base
• r-cran-triebeard/s390x (0.3.0-3 to 0.3.0-3)
  • Migration status for r-cran-triebeard/s390x (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-triebeard/s390x r-base
• r-cran-truncnorm/amd64 (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/amd64 (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/amd64 r-base
• r-cran-truncnorm/arm64 (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/arm64 (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/arm64 r-base
• r-cran-truncnorm/armel (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/armel (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/armel r-base
• r-cran-truncnorm/armhf (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/armhf (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/armhf r-base
• r-cran-truncnorm/i386 (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/i386 (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/i386 r-base
• r-cran-truncnorm/mips64el (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/mips64el (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/mips64el r-base
• r-cran-truncnorm/mipsel (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/mipsel (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/mipsel r-base
• r-cran-truncnorm/ppc64el (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/ppc64el (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/ppc64el r-base
• r-cran-truncnorm/s390x (1.0-8-2 to 1.0-8-2)
  • Migration status for r-cran-truncnorm/s390x (1.0-8-2 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncnorm/s390x r-base
• r-cran-tsp/amd64 (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/amd64 (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/amd64 r-base
• r-cran-tsp/arm64 (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/arm64 (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/arm64 r-base
• r-cran-tsp/armel (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/armel (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/armel r-base
• r-cran-tsp/armhf (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/armhf (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/armhf r-base
• r-cran-tsp/i386 (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/i386 (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/i386 r-base
• r-cran-tsp/mips64el (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/mips64el (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/mips64el r-base
• r-cran-tsp/mipsel (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/mipsel (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/mipsel r-base
• r-cran-tsp/ppc64el (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/ppc64el (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/ppc64el r-base
• r-cran-tsp/s390x (1.1-10-1 to 1.1-10-1)
  • Migration status for r-cran-tsp/s390x (1.1-10-1 to 1.1-10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsp/s390x r-base
• r-cran-ttr/amd64 (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/amd64 (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/amd64 r-base
• r-cran-ttr/arm64 (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/arm64 (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/arm64 r-base
• r-cran-ttr/armel (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/armel (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/armel r-base
• r-cran-ttr/armhf (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/armhf (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/armhf r-base
• r-cran-ttr/i386 (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/i386 (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/i386 r-base
• r-cran-ttr/mips64el (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/mips64el (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/mips64el r-base
• r-cran-ttr/mipsel (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/mipsel (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/mipsel r-base
• r-cran-ttr/ppc64el (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/ppc64el (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/ppc64el r-base
• r-cran-ttr/s390x (0.23-6-2 to 0.23-6-2)
  • Migration status for r-cran-ttr/s390x (0.23-6-2 to 0.23-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ttr/s390x r-base
• r-cran-tweenr/amd64 (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/amd64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/amd64 r-base
• r-cran-tweenr/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/arm64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/arm64 r-base
• r-cran-tweenr/armel (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/armel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/armel r-base
• r-cran-tweenr/armhf (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/armhf (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/armhf r-base
• r-cran-tweenr/i386 (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/i386 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/i386 r-base
• r-cran-tweenr/mips64el (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/mips64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/mips64el r-base
• r-cran-tweenr/mipsel (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/mipsel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/mipsel r-base
• r-cran-tweenr/ppc64el (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/ppc64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/ppc64el r-base
• r-cran-tweenr/s390x (1.0.1-2 to 1.0.1-2)
  • Migration status for r-cran-tweenr/s390x (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tweenr/s390x r-base
• r-cran-ucminf/amd64 (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/amd64 (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/amd64 r-base
• r-cran-ucminf/arm64 (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/arm64 (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/arm64 r-base
• r-cran-ucminf/armel (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/armel (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/armel r-base
• r-cran-ucminf/armhf (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/armhf (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/armhf r-base
• r-cran-ucminf/i386 (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/i386 (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/i386 r-base
• r-cran-ucminf/mips64el (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/mips64el (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/mips64el r-base
• r-cran-ucminf/mipsel (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/mipsel (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/mipsel r-base
• r-cran-ucminf/ppc64el (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/ppc64el (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/ppc64el r-base
• r-cran-ucminf/s390x (1.1-4-2 to 1.1-4-2)
  • Migration status for r-cran-ucminf/s390x (1.1-4-2 to 1.1-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ucminf/s390x r-base
• r-cran-udunits2/amd64 (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/amd64 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/amd64 r-base
• r-cran-udunits2/arm64 (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/arm64 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/arm64 r-base
• r-cran-udunits2/armel (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/armel (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/armel r-base
• r-cran-udunits2/armhf (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/armhf (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/armhf r-base
• r-cran-udunits2/i386 (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/i386 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/i386 r-base
• r-cran-udunits2/mips64el (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/mips64el (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/mips64el r-base
• r-cran-udunits2/mipsel (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/mipsel (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/mipsel r-base
• r-cran-udunits2/ppc64el (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/ppc64el (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/ppc64el r-base
• r-cran-udunits2/s390x (0.13-1 to 0.13-1)
  • Migration status for r-cran-udunits2/s390x (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-udunits2/s390x r-base
• r-cran-units/amd64 (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/amd64 (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/amd64 r-base
• r-cran-units/arm64 (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/arm64 (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/arm64 r-base
• r-cran-units/armel (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/armel (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/armel r-base
• r-cran-units/armhf (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/armhf (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/armhf r-base
• r-cran-units/i386 (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/i386 (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/i386 r-base
• r-cran-units/mips64el (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/mips64el (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/mips64el r-base
• r-cran-units/mipsel (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/mipsel (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/mipsel r-base
• r-cran-units/ppc64el (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/ppc64el (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/ppc64el r-base
• r-cran-units/s390x (0.6-6-1 to 0.6-6-1)
  • Migration status for r-cran-units/s390x (0.6-6-1 to 0.6-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-units/s390x r-base
• r-cran-urltools/amd64 (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/amd64 (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/amd64 r-base
• r-cran-urltools/arm64 (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/arm64 (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/arm64 r-base
• r-cran-urltools/armel (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/armel (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/armel r-base
• r-cran-urltools/armhf (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/armhf (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/armhf r-base
• r-cran-urltools/i386 (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/i386 (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/i386 r-base
• r-cran-urltools/mips64el (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/mips64el (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/mips64el r-base
• r-cran-urltools/mipsel (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/mipsel (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/mipsel r-base
• r-cran-urltools/ppc64el (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/ppc64el (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/ppc64el r-base
• r-cran-urltools/s390x (1.7.3+dfsg-1 to 1.7.3+dfsg-1)
  • Migration status for r-cran-urltools/s390x (1.7.3+dfsg-1 to 1.7.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-urltools/s390x r-base
• r-cran-utf8/amd64 (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/amd64 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/amd64 r-base
• r-cran-utf8/arm64 (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/arm64 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/arm64 r-base
• r-cran-utf8/armel (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/armel (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/armel r-base
• r-cran-utf8/armhf (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/armhf (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/armhf r-base
• r-cran-utf8/i386 (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/i386 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/i386 r-base
• r-cran-utf8/mips64el (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/mips64el (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/mips64el r-base
• r-cran-utf8/mipsel (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/mipsel (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/mipsel r-base
• r-cran-utf8/ppc64el (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/ppc64el (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/ppc64el r-base
• r-cran-utf8/s390x (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-utf8/s390x (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-utf8/s390x r-base
• r-cran-uuid/amd64 (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/amd64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/amd64 r-base
• r-cran-uuid/arm64 (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/arm64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/arm64 r-base
• r-cran-uuid/armel (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/armel (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/armel r-base
• r-cran-uuid/armhf (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/armhf (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/armhf r-base
• r-cran-uuid/i386 (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/i386 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/i386 r-base
• r-cran-uuid/mips64el (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/mips64el (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/mips64el r-base
• r-cran-uuid/mipsel (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/mipsel (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/mipsel r-base
• r-cran-uuid/ppc64el (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/ppc64el (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/ppc64el r-base
• r-cran-uuid/s390x (0.1.4-1 to 0.1.4-1)
  • Migration status for r-cran-uuid/s390x (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uuid/s390x r-base
• r-cran-uwot/amd64 (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/amd64 (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/amd64 r-base
• r-cran-uwot/arm64 (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/arm64 (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/arm64 r-base
• r-cran-uwot/armel (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/armel (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/armel r-base
• r-cran-uwot/armhf (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/armhf (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/armhf r-base
• r-cran-uwot/i386 (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/i386 (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/i386 r-base
• r-cran-uwot/mips64el (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/mips64el (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/mips64el r-base
• r-cran-uwot/mipsel (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/mipsel (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/mipsel r-base
• r-cran-uwot/ppc64el (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/ppc64el (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/ppc64el r-base
• r-cran-uwot/s390x (0.1.8-1 to 0.1.8-1)
  • Migration status for r-cran-uwot/s390x (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uwot/s390x r-base
• r-cran-v8/amd64 (3.0.2+dfsg-1 to 3.0.2+dfsg-1)
  • Migration status for r-cran-v8/amd64 (3.0.2+dfsg-1 to 3.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-v8/amd64 r-base
• r-cran-v8/arm64 (3.0.2+dfsg-1 to 3.0.2+dfsg-1)
  • Migration status for r-cran-v8/arm64 (3.0.2+dfsg-1 to 3.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-v8/arm64 r-base
• r-cran-v8/armhf (3.0.2+dfsg-1 to 3.0.2+dfsg-1)
  • Migration status for r-cran-v8/armhf (3.0.2+dfsg-1 to 3.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-v8/armhf r-base
• r-cran-v8/i386 (3.0.2+dfsg-1 to 3.0.2+dfsg-1)
  • Migration status for r-cran-v8/i386 (3.0.2+dfsg-1 to 3.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-v8/i386 r-base
• r-cran-v8/mips64el (3.0.2+dfsg-1 to 3.0.2+dfsg-1)
  • Migration status for r-cran-v8/mips64el (3.0.2+dfsg-1 to 3.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-v8/mips64el r-base
• r-cran-v8/mipsel (3.0.2+dfsg-1 to 3.0.2+dfsg-1)
  • Migration status for r-cran-v8/mipsel (3.0.2+dfsg-1 to 3.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-v8/mipsel r-base
• r-cran-v8/ppc64el (3.0.2+dfsg-1 to 3.0.2+dfsg-1)
  • Migration status for r-cran-v8/ppc64el (3.0.2+dfsg-1 to 3.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-v8/ppc64el r-base
• r-cran-v8/s390x (3.0.2+dfsg-1 to 3.0.2+dfsg-1)
  • Migration status for r-cran-v8/s390x (3.0.2+dfsg-1 to 3.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-v8/s390x r-base
• r-cran-vdiffr/amd64 (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for r-cran-vdiffr/amd64 (0.3.1+dfsg-3 to 0.3.1+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vdiffr/amd64 r-base
• r-cran-vdiffr/arm64 (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for r-cran-vdiffr/arm64 (0.3.1+dfsg-3 to 0.3.1+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vdiffr/arm64 r-base
• r-cran-vdiffr/armhf (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for r-cran-vdiffr/armhf (0.3.1+dfsg-3 to 0.3.1+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vdiffr/armhf r-base
• r-cran-vdiffr/i386 (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for r-cran-vdiffr/i386 (0.3.1+dfsg-3 to 0.3.1+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vdiffr/i386 r-base
• r-cran-vdiffr/mips64el (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for r-cran-vdiffr/mips64el (0.3.1+dfsg-3 to 0.3.1+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vdiffr/mips64el r-base
• r-cran-vdiffr/mipsel (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for r-cran-vdiffr/mipsel (0.3.1+dfsg-3 to 0.3.1+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vdiffr/mipsel r-base
• r-cran-vdiffr/ppc64el (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for r-cran-vdiffr/ppc64el (0.3.1+dfsg-3 to 0.3.1+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vdiffr/ppc64el r-base
• r-cran-vdiffr/s390x (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for r-cran-vdiffr/s390x (0.3.1+dfsg-3 to 0.3.1+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vdiffr/s390x r-base
• r-cran-vegan/amd64 (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/amd64 (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/amd64 r-base
• r-cran-vegan/arm64 (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/arm64 (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/arm64 r-base
• r-cran-vegan/armel (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/armel (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/armel r-base
• r-cran-vegan/armhf (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/armhf (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/armhf r-base
• r-cran-vegan/i386 (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/i386 (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/i386 r-base
• r-cran-vegan/mips64el (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/mips64el (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/mips64el r-base
• r-cran-vegan/mipsel (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/mipsel (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/mipsel r-base
• r-cran-vegan/ppc64el (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/ppc64el (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/ppc64el r-base
• r-cran-vegan/s390x (2.5-6+dfsg-1 to 2.5-6+dfsg-1)
  • Migration status for r-cran-vegan/s390x (2.5-6+dfsg-1 to 2.5-6+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vegan/s390x r-base
• r-cran-vgam/amd64 (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/amd64 (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/amd64 r-base
• r-cran-vgam/arm64 (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/arm64 (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/arm64 r-base
• r-cran-vgam/armel (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/armel (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/armel r-base
• r-cran-vgam/armhf (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/armhf (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/armhf r-base
• r-cran-vgam/i386 (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/i386 (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/i386 r-base
• r-cran-vgam/mips64el (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/mips64el (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/mips64el r-base
• r-cran-vgam/mipsel (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/mipsel (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/mipsel r-base
• r-cran-vgam/ppc64el (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/ppc64el (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/ppc64el r-base
• r-cran-vgam/s390x (1.1-3-1 to 1.1-3-1)
  • Migration status for r-cran-vgam/s390x (1.1-3-1 to 1.1-3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vgam/s390x r-base
• r-cran-waveslim/amd64 (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/amd64 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/amd64 r-base
• r-cran-waveslim/arm64 (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/arm64 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/arm64 r-base
• r-cran-waveslim/armel (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/armel (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/armel r-base
• r-cran-waveslim/armhf (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/armhf (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/armhf r-base
• r-cran-waveslim/i386 (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/i386 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/i386 r-base
• r-cran-waveslim/mips64el (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/mips64el (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/mips64el r-base
• r-cran-waveslim/mipsel (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/mipsel (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/mipsel r-base
• r-cran-waveslim/ppc64el (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/ppc64el (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/ppc64el r-base
• r-cran-waveslim/s390x (1.8.2-1 to 1.8.2-1)
  • Migration status for r-cran-waveslim/s390x (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-waveslim/s390x r-base
• r-cran-wavethresh/amd64 (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/amd64 (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/amd64 r-base
• r-cran-wavethresh/arm64 (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/arm64 (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/arm64 r-base
• r-cran-wavethresh/armel (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/armel (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/armel r-base
• r-cran-wavethresh/armhf (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/armhf (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/armhf r-base
• r-cran-wavethresh/i386 (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/i386 (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/i386 r-base
• r-cran-wavethresh/mips64el (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/mips64el (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/mips64el r-base
• r-cran-wavethresh/mipsel (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/mipsel (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/mipsel r-base
• r-cran-wavethresh/ppc64el (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/ppc64el (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/ppc64el r-base
• r-cran-wavethresh/s390x (4.6.8-2 to 4.6.8-2)
  • Migration status for r-cran-wavethresh/s390x (4.6.8-2 to 4.6.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wavethresh/s390x r-base
• r-cran-webgestaltr/amd64 (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/amd64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/amd64 r-base
• r-cran-webgestaltr/arm64 (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/arm64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/arm64 r-base
• r-cran-webgestaltr/armel (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/armel (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/armel r-base
• r-cran-webgestaltr/armhf (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/armhf (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/armhf r-base
• r-cran-webgestaltr/i386 (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/i386 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/i386 r-base
• r-cran-webgestaltr/mips64el (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/mips64el (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/mips64el r-base
• r-cran-webgestaltr/mipsel (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/mipsel (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/mipsel r-base
• r-cran-webgestaltr/ppc64el (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/ppc64el (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/ppc64el r-base
• r-cran-webgestaltr/s390x (0.4.3-1 to 0.4.3-1)
  • Migration status for r-cran-webgestaltr/s390x (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webgestaltr/s390x r-base
• r-cran-webutils/amd64 (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/amd64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/amd64 r-base
• r-cran-webutils/arm64 (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/arm64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/arm64 r-base
• r-cran-webutils/armel (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/armel (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/armel r-base
• r-cran-webutils/armhf (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/armhf (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/armhf r-base
• r-cran-webutils/i386 (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/i386 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/i386 r-base
• r-cran-webutils/mips64el (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/mips64el (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/mips64el r-base
• r-cran-webutils/mipsel (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/mipsel (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/mipsel r-base
• r-cran-webutils/ppc64el (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/ppc64el (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/ppc64el r-base
• r-cran-webutils/s390x (1.1-1 to 1.1-1)
  • Migration status for r-cran-webutils/s390x (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webutils/s390x r-base
• r-cran-wgcna/amd64 (1.69-1 to 1.69-1)
  • Migration status for r-cran-wgcna/amd64 (1.69-1 to 1.69-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wgcna/amd64 r-base
• r-cran-wgcna/arm64 (1.69-1 to 1.69-1)
  • Migration status for r-cran-wgcna/arm64 (1.69-1 to 1.69-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wgcna/arm64 r-base
• r-cran-wgcna/armhf (1.69-1 to 1.69-1)
  • Migration status for r-cran-wgcna/armhf (1.69-1 to 1.69-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wgcna/armhf r-base
• r-cran-wgcna/i386 (1.69-1 to 1.69-1)
  • Migration status for r-cran-wgcna/i386 (1.69-1 to 1.69-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wgcna/i386 r-base
• r-cran-wgcna/mips64el (1.69-1 to 1.69-1)
  • Migration status for r-cran-wgcna/mips64el (1.69-1 to 1.69-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wgcna/mips64el r-base
• r-cran-wgcna/mipsel (1.69-1 to 1.69-1)
  • Migration status for r-cran-wgcna/mipsel (1.69-1 to 1.69-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wgcna/mipsel r-base
• r-cran-wgcna/ppc64el (1.69-1 to 1.69-1)
  • Migration status for r-cran-wgcna/ppc64el (1.69-1 to 1.69-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wgcna/ppc64el r-base
• r-cran-wgcna/s390x (1.69-1 to 1.69-1)
  • Migration status for r-cran-wgcna/s390x (1.69-1 to 1.69-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wgcna/s390x r-base
• r-cran-wordcloud/amd64 (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/amd64 (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/amd64 r-base
• r-cran-wordcloud/arm64 (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/arm64 (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/arm64 r-base
• r-cran-wordcloud/armel (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/armel (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/armel r-base
• r-cran-wordcloud/armhf (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/armhf (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/armhf r-base
• r-cran-wordcloud/i386 (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/i386 (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/i386 r-base
• r-cran-wordcloud/mips64el (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/mips64el (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/mips64el r-base
• r-cran-wordcloud/mipsel (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/mipsel (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/mipsel r-base
• r-cran-wordcloud/ppc64el (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/ppc64el (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/ppc64el r-base
• r-cran-wordcloud/s390x (2.6-1 to 2.6-1)
  • Migration status for r-cran-wordcloud/s390x (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wordcloud/s390x r-base
• r-cran-xml/amd64 (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/amd64 (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/amd64 r-base
• r-cran-xml/arm64 (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/arm64 (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/arm64 r-base
• r-cran-xml/armel (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/armel (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/armel r-base
• r-cran-xml/armhf (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/armhf (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/armhf r-base
• r-cran-xml/i386 (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/i386 (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/i386 r-base
• r-cran-xml/mips64el (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/mips64el (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/mips64el r-base
• r-cran-xml/mipsel (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/mipsel (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/mipsel r-base
• r-cran-xml/ppc64el (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/ppc64el (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/ppc64el r-base
• r-cran-xml/s390x (3.99-0.3-2 to 3.99-0.3-2)
  • Migration status for r-cran-xml/s390x (3.99-0.3-2 to 3.99-0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml/s390x r-base
• r-cran-xml2/amd64 (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/amd64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/amd64 r-base
• r-cran-xml2/arm64 (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/arm64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/arm64 r-base
• r-cran-xml2/armel (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/armel (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/armel r-base
• r-cran-xml2/armhf (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/armhf (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/armhf r-base
• r-cran-xml2/i386 (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/i386 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/i386 r-base
• r-cran-xml2/mips64el (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/mips64el (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/mips64el r-base
• r-cran-xml2/mipsel (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/mipsel (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/mipsel r-base
• r-cran-xml2/ppc64el (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/ppc64el (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/ppc64el r-base
• r-cran-xml2/s390x (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-xml2/s390x (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xml2/s390x r-base
• r-cran-xts/amd64 (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/amd64 (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/amd64 r-base
• r-cran-xts/arm64 (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/arm64 (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/arm64 r-base
• r-cran-xts/armel (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/armel (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/armel r-base
• r-cran-xts/armhf (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/armhf (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/armhf r-base
• r-cran-xts/i386 (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/i386 (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/i386 r-base
• r-cran-xts/mips64el (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/mips64el (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/mips64el r-base
• r-cran-xts/mipsel (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/mipsel (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/mipsel r-base
• r-cran-xts/ppc64el (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/ppc64el (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/ppc64el r-base
• r-cran-xts/s390x (0.12-0-1 to 0.12-0-1)
  • Migration status for r-cran-xts/s390x (0.12-0-1 to 0.12-0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xts/s390x r-base
• r-cran-yaml/amd64 (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/amd64 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/amd64 r-base
• r-cran-yaml/arm64 (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/arm64 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/arm64 r-base
• r-cran-yaml/armel (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/armel (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/armel r-base
• r-cran-yaml/armhf (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/armhf (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/armhf r-base
• r-cran-yaml/i386 (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/i386 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/i386 r-base
• r-cran-yaml/mips64el (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/mips64el (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/mips64el r-base
• r-cran-yaml/mipsel (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/mipsel (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/mipsel r-base
• r-cran-yaml/ppc64el (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/ppc64el (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/ppc64el r-base
• r-cran-yaml/s390x (2.2.1-1 to 2.2.1-1)
  • Migration status for r-cran-yaml/s390x (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-yaml/s390x r-base
• r-cran-zip/amd64 (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/amd64 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/amd64 r-base
• r-cran-zip/arm64 (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/arm64 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/arm64 r-base
• r-cran-zip/armel (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/armel (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/armel r-base
• r-cran-zip/armhf (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/armhf (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/armhf r-base
• r-cran-zip/i386 (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/i386 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/i386 r-base
• r-cran-zip/mips64el (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/mips64el (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/mips64el r-base
• r-cran-zip/mipsel (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/mipsel (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/mipsel r-base
• r-cran-zip/ppc64el (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/ppc64el (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/ppc64el r-base
• r-cran-zip/s390x (2.0.4-1 to 2.0.4-1)
  • Migration status for r-cran-zip/s390x (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zip/s390x r-base
• r-other-amsmercury/amd64 (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/amd64 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/amd64 r-base
• r-other-amsmercury/arm64 (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/arm64 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/arm64 r-base
• r-other-amsmercury/armel (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/armel (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/armel r-base
• r-other-amsmercury/armhf (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/armhf (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/armhf r-base
• r-other-amsmercury/i386 (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/i386 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/i386 r-base
• r-other-amsmercury/mips64el (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/mips64el (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/mips64el r-base
• r-other-amsmercury/mipsel (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/mipsel (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/mipsel r-base
• r-other-amsmercury/ppc64el (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/ppc64el (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/ppc64el r-base
• r-other-amsmercury/s390x (1.3.0-3 to 1.3.0-3)
  • Migration status for r-other-amsmercury/s390x (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-amsmercury/s390x r-base
• r-other-chbutils/amd64 (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/amd64 (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/amd64 r-base
• r-other-chbutils/arm64 (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/arm64 (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/arm64 r-base
• r-other-chbutils/armel (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/armel (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/armel r-base
• r-other-chbutils/armhf (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/armhf (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/armhf r-base
• r-other-chbutils/i386 (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/i386 (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/i386 r-base
• r-other-chbutils/mips64el (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/mips64el (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/mips64el r-base
• r-other-chbutils/mipsel (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/mipsel (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/mipsel r-base
• r-other-chbutils/ppc64el (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/ppc64el (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/ppc64el r-base
• r-other-chbutils/s390x (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1)
  • Migration status for r-other-chbutils/s390x (0.1+git20171026.a226cee-1 to 0.1+git20171026.a226cee-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-chbutils/s390x r-base
• r-other-iwrlars/amd64 (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/amd64 (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/amd64 r-base
• r-other-iwrlars/arm64 (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/arm64 (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/arm64 r-base
• r-other-iwrlars/armel (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/armel (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/armel r-base
• r-other-iwrlars/armhf (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/armhf (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/armhf r-base
• r-other-iwrlars/i386 (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/i386 (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/i386 r-base
• r-other-iwrlars/mips64el (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/mips64el (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/mips64el r-base
• r-other-iwrlars/mipsel (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/mipsel (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/mipsel r-base
• r-other-iwrlars/ppc64el (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/ppc64el (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/ppc64el r-base
• r-other-iwrlars/s390x (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/s390x (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-iwrlars/s390x r-base
• r-other-mott-happy/amd64 (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/amd64 (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/amd64 r-base
• r-other-mott-happy/arm64 (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/arm64 (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/arm64 r-base
• r-other-mott-happy/armel (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/armel (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/armel r-base
• r-other-mott-happy/armhf (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/armhf (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/armhf r-base
• r-other-mott-happy/i386 (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/i386 (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/i386 r-base
• r-other-mott-happy/mips64el (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/mips64el (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/mips64el r-base
• r-other-mott-happy/mipsel (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/mipsel (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/mipsel r-base
• r-other-mott-happy/ppc64el (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/ppc64el (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/ppc64el r-base
• r-other-mott-happy/s390x (2.4-3 to 2.4-3)
  • Migration status for r-other-mott-happy/s390x (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-mott-happy/s390x r-base
• r-other-x4r/amd64 (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/amd64 (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/amd64 r-base
• r-other-x4r/arm64 (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/arm64 (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/arm64 r-base
• r-other-x4r/armel (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/armel (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/armel r-base
• r-other-x4r/armhf (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/armhf (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/armhf r-base
• r-other-x4r/i386 (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/i386 (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/i386 r-base
• r-other-x4r/mips64el (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/mips64el (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/mips64el r-base
• r-other-x4r/mipsel (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/mipsel (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/mipsel r-base
• r-other-x4r/ppc64el (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/ppc64el (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/ppc64el r-base
• r-other-x4r/s390x (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2)
  • Migration status for r-other-x4r/s390x (1.0.1+git20150806.c6bd9bd-2 to 1.0.1+git20150806.c6bd9bd-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-x4r/s390x r-base
• r-zoo/amd64 (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/amd64 (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/amd64 r-base
• r-zoo/arm64 (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/arm64 (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/arm64 r-base
• r-zoo/armel (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/armel (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/armel r-base
• r-zoo/armhf (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/armhf (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/armhf r-base
• r-zoo/i386 (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/i386 (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/i386 r-base
• r-zoo/mips64el (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/mips64el (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/mips64el r-base
• r-zoo/mipsel (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/mipsel (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/mipsel r-base
• r-zoo/ppc64el (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/ppc64el (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/ppc64el r-base
• r-zoo/s390x (1.8-8-1 to 1.8-8-1)
  • Migration status for r-zoo/s390x (1.8-8-1 to 1.8-8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-zoo/s390x r-base
• rcpp/amd64 (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/amd64 (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/amd64 r-base
• rcpp/arm64 (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/arm64 (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/arm64 r-base
• rcpp/armel (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/armel (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/armel r-base
• rcpp/armhf (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/armhf (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/armhf r-base
• rcpp/i386 (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/i386 (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/i386 r-base
• rcpp/mips64el (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/mips64el (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/mips64el r-base
• rcpp/mipsel (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/mipsel (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/mipsel r-base
• rcpp/ppc64el (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/ppc64el (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/ppc64el r-base
• rcpp/s390x (1.0.4.6-1 to 1.0.4.6-1)
  • Migration status for rcpp/s390x (1.0.4.6-1 to 1.0.4.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: rcpp/s390x r-base
• rggobi/amd64 (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/amd64 (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/amd64 r-base
• rggobi/arm64 (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/arm64 (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/arm64 r-base
• rggobi/armel (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/armel (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/armel r-base
• rggobi/armhf (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/armhf (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/armhf r-base
• rggobi/i386 (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/i386 (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/i386 r-base
• rggobi/mips64el (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/mips64el (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/mips64el r-base
• rggobi/mipsel (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/mipsel (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/mipsel r-base
• rggobi/ppc64el (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/ppc64el (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/ppc64el r-base
• rggobi/s390x (2.1.22-1 to 2.1.22-1)
  • Migration status for rggobi/s390x (2.1.22-1 to 2.1.22-1): Will attempt migration (Any information below is purely informational)
  • Depends: rggobi/s390x r-base
• rglpk/amd64 (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/amd64 (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/amd64 r-base
• rglpk/arm64 (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/arm64 (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/arm64 r-base
• rglpk/armel (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/armel (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/armel r-base
• rglpk/armhf (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/armhf (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/armhf r-base
• rglpk/i386 (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/i386 (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/i386 r-base
• rglpk/mips64el (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/mips64el (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/mips64el r-base
• rglpk/mipsel (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/mipsel (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/mipsel r-base
• rglpk/ppc64el (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/ppc64el (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/ppc64el r-base
• rglpk/s390x (0.6-4-1 to 0.6-4-1)
  • Migration status for rglpk/s390x (0.6-4-1 to 0.6-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: rglpk/s390x r-base
• rgtk2/amd64 (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/amd64 (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/amd64 r-base
• rgtk2/arm64 (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/arm64 (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/arm64 r-base
• rgtk2/armel (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/armel (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/armel r-base
• rgtk2/armhf (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/armhf (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/armhf r-base
• rgtk2/i386 (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/i386 (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/i386 r-base
• rgtk2/mips64el (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/mips64el (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/mips64el r-base
• rgtk2/mipsel (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/mipsel (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/mipsel r-base
• rgtk2/ppc64el (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/ppc64el (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/ppc64el r-base
• rgtk2/s390x (2.20.36-2 to 2.20.36-2)
  • Migration status for rgtk2/s390x (2.20.36-2 to 2.20.36-2): Will attempt migration (Any information below is purely informational)
  • Depends: rgtk2/s390x r-base
• rjava/amd64 (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/amd64 (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/amd64 r-base
• rjava/arm64 (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/arm64 (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/arm64 r-base
• rjava/armel (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/armel (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/armel r-base
• rjava/armhf (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/armhf (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/armhf r-base
• rjava/i386 (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/i386 (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/i386 r-base
• rjava/mips64el (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/mips64el (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/mips64el r-base
• rjava/mipsel (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/mipsel (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/mipsel r-base
• rjava/ppc64el (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/ppc64el (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/ppc64el r-base
• rjava/s390x (0.9-12-1 to 0.9-12-1)
  • Migration status for rjava/s390x (0.9-12-1 to 0.9-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rjava/s390x r-base
• rmatrix/amd64 (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/amd64 (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/amd64 r-base
• rmatrix/arm64 (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/arm64 (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/arm64 r-base
• rmatrix/armel (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/armel (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/armel r-base
• rmatrix/armhf (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/armhf (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/armhf r-base
• rmatrix/i386 (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/i386 (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/i386 r-base
• rmatrix/mips64el (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/mips64el (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/mips64el r-base
• rmatrix/mipsel (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/mipsel (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/mipsel r-base
• rmatrix/ppc64el (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/ppc64el (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/ppc64el r-base
• rmatrix/s390x (1.2-18-1 to 1.2-18-1)
  • Migration status for rmatrix/s390x (1.2-18-1 to 1.2-18-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmatrix/s390x r-base
• rmpi/amd64 (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/amd64 (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/amd64 r-base
• rmpi/arm64 (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/arm64 (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/arm64 r-base
• rmpi/armel (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/armel (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/armel r-base
• rmpi/armhf (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/armhf (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/armhf r-base
• rmpi/i386 (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/i386 (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/i386 r-base
• rmpi/mips64el (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/mips64el (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/mips64el r-base
• rmpi/mipsel (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/mipsel (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/mipsel r-base
• rmpi/ppc64el (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/ppc64el (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/ppc64el r-base
• rmpi/s390x (0.6-9-1 to 0.6-9-1)
  • Migration status for rmpi/s390x (0.6-9-1 to 0.6-9-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmpi/s390x r-base
• rmysql/amd64 (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/amd64 (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/amd64 r-base
• rmysql/arm64 (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/arm64 (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/arm64 r-base
• rmysql/armel (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/armel (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/armel r-base
• rmysql/armhf (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/armhf (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/armhf r-base
• rmysql/i386 (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/i386 (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/i386 r-base
• rmysql/mips64el (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/mips64el (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/mips64el r-base
• rmysql/mipsel (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/mipsel (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/mipsel r-base
• rmysql/ppc64el (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/ppc64el (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/ppc64el r-base
• rmysql/s390x (0.10.20-1 to 0.10.20-1)
  • Migration status for rmysql/s390x (0.10.20-1 to 0.10.20-1): Will attempt migration (Any information below is purely informational)
  • Depends: rmysql/s390x r-base
• robustbase/amd64 (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/amd64 (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/amd64 r-base
• robustbase/arm64 (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/arm64 (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/arm64 r-base
• robustbase/armel (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/armel (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/armel r-base
• robustbase/armhf (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/armhf (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/armhf r-base
• robustbase/i386 (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/i386 (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/i386 r-base
• robustbase/mips64el (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/mips64el (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/mips64el r-base
• robustbase/mipsel (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/mipsel (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/mipsel r-base
• robustbase/ppc64el (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/ppc64el (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/ppc64el r-base
• robustbase/s390x (0.93-6-1 to 0.93-6-1)
  • Migration status for robustbase/s390x (0.93-6-1 to 0.93-6-1): Will attempt migration (Any information below is purely informational)
  • Depends: robustbase/s390x r-base
• roundcube_pu (1.4.4+dfsg.1-1 to 1.3.11+dfsg.1-1~deb10u1)
  • Migration status for roundcube_pu (1.4.4+dfsg.1-1 to 1.3.11+dfsg.1-1~deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: roundcube is newer in the target suite (1.4.4+dfsg.1-1 1.3.11+dfsg.1-1~deb10u1)
• rpart/amd64 (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/amd64 (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/amd64 r-base
• rpart/arm64 (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/arm64 (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/arm64 r-base
• rpart/armel (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/armel (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/armel r-base
• rpart/armhf (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/armhf (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/armhf r-base
• rpart/i386 (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/i386 (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/i386 r-base
• rpart/mips64el (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/mips64el (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/mips64el r-base
• rpart/mipsel (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/mipsel (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/mipsel r-base
• rpart/ppc64el (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/ppc64el (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/ppc64el r-base
• rpart/s390x (4.1-15-2 to 4.1-15-2)
  • Migration status for rpart/s390x (4.1-15-2 to 4.1-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: rpart/s390x r-base
• rquantlib/amd64 (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/amd64 (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/amd64 r-base
• rquantlib/arm64 (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/arm64 (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/arm64 r-base
• rquantlib/armel (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/armel (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/armel r-base
• rquantlib/armhf (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/armhf (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/armhf r-base
• rquantlib/i386 (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/i386 (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/i386 r-base
• rquantlib/mips64el (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/mips64el (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/mips64el r-base
• rquantlib/mipsel (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/mipsel (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/mipsel r-base
• rquantlib/ppc64el (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/ppc64el (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/ppc64el r-base
• rquantlib/s390x (0.4.12-1 to 0.4.12-1)
  • Migration status for rquantlib/s390x (0.4.12-1 to 0.4.12-1): Will attempt migration (Any information below is purely informational)
  • Depends: rquantlib/s390x r-base
• rserve/amd64 (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/amd64 (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/amd64 r-base
• rserve/arm64 (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/arm64 (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/arm64 r-base
• rserve/armel (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/armel (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/armel r-base
• rserve/armhf (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/armhf (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/armhf r-base
• rserve/i386 (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/i386 (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/i386 r-base
• rserve/mips64el (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/mips64el (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/mips64el r-base
• rserve/mipsel (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/mipsel (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/mipsel r-base
• rserve/ppc64el (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/ppc64el (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/ppc64el r-base
• rserve/s390x (1.7-3.1-2 to 1.7-3.1-2)
  • Migration status for rserve/s390x (1.7-3.1-2 to 1.7-3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: rserve/s390x r-base
• rsprng/amd64 (1.0-5 to 1.0-5)
  • Migration status for rsprng/amd64 (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/amd64 r-base
• rsprng/arm64 (1.0-5 to 1.0-5)
  • Migration status for rsprng/arm64 (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/arm64 r-base
• rsprng/armel (1.0-5 to 1.0-5)
  • Migration status for rsprng/armel (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/armel r-base
• rsprng/armhf (1.0-5 to 1.0-5)
  • Migration status for rsprng/armhf (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/armhf r-base
• rsprng/i386 (1.0-5 to 1.0-5)
  • Migration status for rsprng/i386 (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/i386 r-base
• rsprng/mips64el (1.0-5 to 1.0-5)
  • Migration status for rsprng/mips64el (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/mips64el r-base
• rsprng/mipsel (1.0-5 to 1.0-5)
  • Migration status for rsprng/mipsel (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/mipsel r-base
• rsprng/ppc64el (1.0-5 to 1.0-5)
  • Migration status for rsprng/ppc64el (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/ppc64el r-base
• rsprng/s390x (1.0-5 to 1.0-5)
  • Migration status for rsprng/s390x (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: rsprng/s390x r-base
• rsymphony/amd64 (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/amd64 (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/amd64 r-base
• rsymphony/arm64 (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/arm64 (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/arm64 r-base
• rsymphony/armel (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/armel (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/armel r-base
• rsymphony/armhf (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/armhf (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/armhf r-base
• rsymphony/i386 (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/i386 (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/i386 r-base
• rsymphony/mips64el (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/mips64el (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/mips64el r-base
• rsymphony/mipsel (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/mipsel (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/mipsel r-base
• rsymphony/ppc64el (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/ppc64el (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/ppc64el r-base
• rsymphony/s390x (0.1-28-1 to 0.1-28-1)
  • Migration status for rsymphony/s390x (0.1-28-1 to 0.1-28-1): Will attempt migration (Any information below is purely informational)
  • Depends: rsymphony/s390x r-base
• salt_pu (3000.2+dfsg1-1 to 2018.3.4+dfsg1-6+deb10u1)
  • Migration status for salt_pu (3000.2+dfsg1-1 to 2018.3.4+dfsg1-6+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: salt is newer in the target suite (3000.2+dfsg1-1 2018.3.4+dfsg1-6+deb10u1)
• scribus/amd64 (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/amd64 (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/amd64 openscenegraph (not considered)
  • Invalidated by dependency
• scribus/arm64 (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/arm64 (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/arm64 openscenegraph (not considered)
  • Invalidated by dependency
• scribus/armel (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/armel (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/armel openscenegraph (not considered)
  • Invalidated by dependency
• scribus/armhf (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/armhf (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/armhf openscenegraph (not considered)
  • Invalidated by dependency
• scribus/i386 (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/i386 (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/i386 openscenegraph (not considered)
  • Invalidated by dependency
• scribus/mips64el (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/mips64el (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/mips64el openscenegraph (not considered)
  • Invalidated by dependency
• scribus/mipsel (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/mipsel (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/mipsel openscenegraph (not considered)
  • Invalidated by dependency
• scribus/ppc64el (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/ppc64el (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/ppc64el openscenegraph (not considered)
  • Invalidated by dependency
• scribus/s390x (1.5.5+dfsg-6 to 1.5.5+dfsg-6)
  • Migration status for scribus/s390x (1.5.5+dfsg-6 to 1.5.5+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: scribus/s390x openscenegraph (not considered)
  • Invalidated by dependency
• sm/amd64 (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/amd64 (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/amd64 r-base
• sm/arm64 (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/arm64 (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/arm64 r-base
• sm/armel (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/armel (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/armel r-base
• sm/armhf (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/armhf (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/armhf r-base
• sm/i386 (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/i386 (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/i386 r-base
• sm/mips64el (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/mips64el (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/mips64el r-base
• sm/mipsel (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/mipsel (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/mipsel r-base
• sm/ppc64el (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/ppc64el (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/ppc64el r-base
• sm/s390x (2.2-5.6-1 to 2.2-5.6-1)
  • Migration status for sm/s390x (2.2-5.6-1 to 2.2-5.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: sm/s390x r-base
• squid_pu (4.11-2 to 4.6-1+deb10u2)
  • Migration status for squid_pu (4.11-2 to 4.6-1+deb10u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: squid is newer in the target suite (4.11-2 4.6-1+deb10u2)
• strucchange/amd64 (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/amd64 (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/amd64 r-base
• strucchange/arm64 (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/arm64 (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/arm64 r-base
• strucchange/armel (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/armel (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/armel r-base
• strucchange/armhf (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/armhf (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/armhf r-base
• strucchange/i386 (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/i386 (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/i386 r-base
• strucchange/mips64el (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/mips64el (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/mips64el r-base
• strucchange/mipsel (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/mipsel (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/mipsel r-base
• strucchange/ppc64el (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/ppc64el (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/ppc64el r-base
• strucchange/s390x (1.5-2-1+1 to 1.5-2-1+1)
  • Migration status for strucchange/s390x (1.5-2-1+1 to 1.5-2-1+1): Will attempt migration (Any information below is purely informational)
  • Depends: strucchange/s390x r-base
• suricata_pu (1:5.0.3-1 to 1:4.1.2-2+deb10u1)
  • Migration status for suricata_pu (1:5.0.3-1 to 1:4.1.2-2+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: suricata is newer in the target suite (1:5.0.3-1 1:4.1.2-2+deb10u1)
• survival/amd64 (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/amd64 (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/amd64 r-base
• survival/arm64 (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/arm64 (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/arm64 r-base
• survival/armel (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/armel (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/armel r-base
• survival/armhf (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/armhf (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/armhf r-base
• survival/i386 (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/i386 (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/i386 r-base
• survival/mips64el (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/mips64el (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/mips64el r-base
• survival/mipsel (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/mipsel (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/mipsel r-base
• survival/ppc64el (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/ppc64el (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/ppc64el r-base
• survival/s390x (3.1-12-1 to 3.1-12-1)
  • Migration status for survival/s390x (3.1-12-1 to 3.1-12-1): Will attempt migration (Any information below is purely informational)
  • Depends: survival/s390x r-base
• tkrplot/amd64 (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/amd64 (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/amd64 r-base
• tkrplot/arm64 (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/arm64 (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/arm64 r-base
• tkrplot/armel (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/armel (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/armel r-base
• tkrplot/armhf (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/armhf (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/armhf r-base
• tkrplot/i386 (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/i386 (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/i386 r-base
• tkrplot/mips64el (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/mips64el (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/mips64el r-base
• tkrplot/mipsel (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/mipsel (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/mipsel r-base
• tkrplot/ppc64el (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/ppc64el (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/ppc64el r-base
• tkrplot/s390x (0.0.24-1 to 0.0.24-1)
  • Migration status for tkrplot/s390x (0.0.24-1 to 0.0.24-1): Will attempt migration (Any information below is purely informational)
  • Depends: tkrplot/s390x r-base
• tomcat9_pu (9.0.35-1 to 9.0.31-1~deb10u1)
  • Migration status for tomcat9_pu (9.0.35-1 to 9.0.31-1~deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: tomcat9 is newer in the target suite (9.0.35-1 9.0.31-1~deb10u1)
• tseries/amd64 (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/amd64 (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/amd64 r-base
• tseries/arm64 (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/arm64 (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/arm64 r-base
• tseries/armel (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/armel (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/armel r-base
• tseries/armhf (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/armhf (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/armhf r-base
• tseries/i386 (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/i386 (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/i386 r-base
• tseries/mips64el (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/mips64el (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/mips64el r-base
• tseries/mipsel (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/mipsel (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/mipsel r-base
• tseries/ppc64el (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/ppc64el (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/ppc64el r-base
• tseries/s390x (0.10-47-2 to 0.10-47-2)
  • Migration status for tseries/s390x (0.10-47-2 to 0.10-47-2): Will attempt migration (Any information below is purely informational)
  • Depends: tseries/s390x r-base
• urca/amd64 (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/amd64 (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/amd64 r-base
• urca/arm64 (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/arm64 (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/arm64 r-base
• urca/armel (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/armel (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/armel r-base
• urca/armhf (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/armhf (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/armhf r-base
• urca/i386 (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/i386 (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/i386 r-base
• urca/mips64el (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/mips64el (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/mips64el r-base
• urca/mipsel (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/mipsel (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/mipsel r-base
• urca/ppc64el (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/ppc64el (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/ppc64el r-base
• urca/s390x (1.3-0-3 to 1.3-0-3)
  • Migration status for urca/s390x (1.3-0-3 to 1.3-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: urca/s390x r-base
• wordpress_pu (5.4.1+dfsg1-1 to 5.0.4+dfsg1-1+deb10u2)
  • Migration status for wordpress_pu (5.4.1+dfsg1-1 to 5.0.4+dfsg1-1+deb10u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: wordpress is newer in the target suite (5.4.1+dfsg1-1 5.0.4+dfsg1-1+deb10u2)
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • removing xfce4-cpufreq-plugin/1.2.1-1/ppc64el from testing makes xfce4-goodies/4.14.0/ppc64el uninstallable
• zanshin/amd64 (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/amd64 (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/amd64 kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/amd64 akonadi
  • Depends: zanshin/amd64 kontactinterface
• zanshin/arm64 (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/arm64 (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/arm64 kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/arm64 akonadi
  • Depends: zanshin/arm64 kontactinterface
• zanshin/armel (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/armel (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/armel kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/armel akonadi
  • Depends: zanshin/armel kontactinterface
• zanshin/armhf (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/armhf (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/armhf kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/armhf akonadi
  • Depends: zanshin/armhf kontactinterface
• zanshin/i386 (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/i386 (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/i386 kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/i386 akonadi
  • Depends: zanshin/i386 kontactinterface
• zanshin/mips64el (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/mips64el (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/mips64el kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/mips64el akonadi
  • Depends: zanshin/mips64el kontactinterface
• zanshin/mipsel (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/mipsel (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/mipsel kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/mipsel akonadi
  • Depends: zanshin/mipsel kontactinterface
• zanshin/ppc64el (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/ppc64el (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/ppc64el kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/ppc64el akonadi
  • Depends: zanshin/ppc64el kontactinterface
• zanshin/s390x (0.5.71-1 to 0.5.71-1)
  • Migration status for zanshin/s390x (0.5.71-1 to 0.5.71-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: zanshin/s390x kcalcore (not considered)
  • Invalidated by dependency
  • Depends: zanshin/s390x akonadi
  • Depends: zanshin/s390x kontactinterface
• zipios++_pu (0.1.5.9+cvs.2007.04.28-11 to 0.1.5.9+cvs.2007.04.28-10+deb10u1)
  • Migration status for zipios++_pu (0.1.5.9+cvs.2007.04.28-11 to 0.1.5.9+cvs.2007.04.28-10+deb10u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ALERT: zipios++ is newer in the target suite (0.1.5.9+cvs.2007.04.28-11 0.1.5.9+cvs.2007.04.28-10+deb10u1)
• anbox (0.0~git20191115-1 to 0.0~git20200526-1)
  • Migration status for anbox (0.0~git20191115-1 to 0.0~git20200526-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
  • Depends: anbox libsdl2
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
• b4 (0.4.0-1 to 0.5.0-1)
  • Migration status for b4 (0.4.0-1 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 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/b4.html
• clippoly (0.11-8 to 0.11-9)
  • Migration status for clippoly (0.11-8 to 0.11-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/c/clippoly.html
• cockpit (218-1 to 220-1)
  • Migration status for cockpit (218-1 to 220-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:
  • Updating cockpit fixes old bugs: #960752
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cockpit.html
  • Required age reduced by 3 days because of autopkgtest
• composer (1.10.5-1 to 1.10.6-1)
  • Migration status for composer (1.10.5-1 to 1.10.6-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/c/composer.html
  • Required age reduced by 3 days because of autopkgtest
• danmaq (0.2.3.1-5 to 0.2.3.2-1)
  • Migration status for danmaq (0.2.3.1-5 to 0.2.3.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/d/danmaq.html
• dlt-daemon (2.18.4-0.1 to 2.18.4-0.2)
  • Migration status for dlt-daemon (2.18.4-0.1 to 2.18.4-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/d/dlt-daemon.html
• foomatic-db-engine (4.0.13-4 to 4.0.13-5)
  • Migration status for foomatic-db-engine (4.0.13-4 to 4.0.13-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/f/foomatic-db-engine.html
• freerdp2 (2.0.0~git20190204.1.2693389a+dfsg1-2 to 2.1.1+dfsg1-1)
  • Migration status for freerdp2 (2.0.0~git20190204.1.2693389a+dfsg1-2 to 2.1.1+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/f/freerdp2.html
• gdb (9.1-3 to 9.2-1)
  • Migration status for gdb (9.1-3 to 9.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
  • Depends: gdb gcc-10
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdb.html
• gdb-doc (9.1-1 to 9.2-1)
  • Migration status for gdb-doc (9.1-1 to 9.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:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• getdns (1.5.1-1 to 1.5.2-2)
  • Migration status for getdns (1.5.1-1 to 1.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for getdns/1.5.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/getdns.html
• golang-github-optiopay-kafka (- to 2.1.1-1)
  • Migration status for golang-github-optiopay-kafka (- to 2.1.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/g/golang-github-optiopay-kafka.html
  • Required age reduced by 3 days because of autopkgtest
• gradle (4.4.1-10 to 4.4.1-11)
  • Migration status for gradle (4.4.1-10 to 4.4.1-11): 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/gradle.html
• herculesstudio (1.5.0-2 to 1.5.0-4)
  • Migration status for herculesstudio (1.5.0-2 to 1.5.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 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/herculesstudio.html
• jetty9 (9.4.28-1 to 9.4.29-1)
  • Migration status for jetty9 (9.4.28-1 to 9.4.29-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/j/jetty9.html
• libapache-mod-jk (1:1.2.46-1 to 1:1.2.46-2)
  • Migration status for libapache-mod-jk (1:1.2.46-1 to 1:1.2.46-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 libapache-mod-jk fixes old bugs: #928813
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-mod-jk.html
• libblockdev (2.23-2 to 2.24-1)
  • Migration status for libblockdev (2.23-2 to 2.24-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/libb/libblockdev.html
• libcatmandu-perl (1.1000-2 to 1.2012-1)
  • Migration status for libcatmandu-perl (1.1000-2 to 1.2012-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libcatmandu-sru-perl/0.42.1-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcatmandu-perl.html
• libmaus2 (- to 2.0.719+dfsg-1)
  • Migration status for libmaus2 (- to 2.0.719+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libmaus2 introduces new bugs: #934619
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • arch:amd64 not built yet, autopkgtest delayed there
  • arch:arm64 not built yet, autopkgtest delayed there
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmaus2.html
• lintian (2.76.0 to 2.77.1)
  • Migration status for lintian (2.76.0 to 2.77.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/l/lintian.html
  • Required age reduced by 3 days because of autopkgtest
• mwrap (0.33-9 to 0.33-10)
  • Migration status for mwrap (0.33-9 to 0.33-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:
  • Updating mwrap fixes old bugs: #960402
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mwrap.html
  • Required age reduced by 3 days because of autopkgtest
• node-axios (0.19.0+dfsg-2 to 0.19.2+dfsg-1)
  • Migration status for node-axios (0.19.0+dfsg-2 to 0.19.2+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/n/node-axios.html
  • Required age reduced by 3 days because of autopkgtest
• node-is-promise (2.1.0-1 to 4.0.0-1)
  • Migration status for node-is-promise (2.1.0-1 to 4.0.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Too young, only 0 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-is-promise.html
• node-js-yaml (3.13.1+dfsg-2 to 3.14.0+dfsg-1)
  • Migration status for node-js-yaml (3.13.1+dfsg-2 to 3.14.0+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/n/node-js-yaml.html
  • Required age reduced by 3 days because of autopkgtest
• node-regjsgen (0.5.1+ds-1 to 0.5.2+ds-1)
  • Migration status for node-regjsgen (0.5.1+ds-1 to 0.5.2+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-regjsgen.html
  • Required age reduced by 3 days because of autopkgtest
• node-tweetnacl (1.0.1+dfsg-2 to 1.0.3+dfsg-1)
  • Migration status for node-tweetnacl (1.0.1+dfsg-2 to 1.0.3+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/n/node-tweetnacl.html
  • Required age reduced by 3 days because of autopkgtest
• numba (- to 0.48.0-2)
  • Migration status for numba (- to 0.48.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on armhf
  • 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/n/numba.html
• obs-studio (25.0.3+dfsg1-2 to 25.0.8+dfsg1-1)
  • Migration status for obs-studio (25.0.3+dfsg1-2 to 25.0.8+dfsg1-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 i386
  • missing build on mips64el
  • missing build on mipsel
  • arch:arm64 not built yet, autopkgtest delayed there
  • Too young, only 0 of 5 days old
  • Built-Using: obs-studio simde
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-studio.html
• openstack-cluster-installer (28 to 29)
  • Migration status for openstack-cluster-installer (28 to 29): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
  • puppet-module-oci/amd64 has unsatisfiable dependency
  • puppet-module-oci/i386 has unsatisfiable dependency
  • Too young, only 0 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openstack-cluster-installer.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• openstack-meta-packages (0.28 to 0.29)
  • Migration status for openstack-meta-packages (0.28 to 0.29): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
  • Too young, only 0 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openstack-meta-packages.html
  • uninstallable on arch arm64, not running autopkgtest there
• orthanc-dicomweb (1.1+dfsg-1 to 1.2+dfsg-1)
  • Migration status for orthanc-dicomweb (1.1+dfsg-1 to 1.2+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 5 days old
  • Build-Depends(-Arch): orthanc-dicomweb orthanc
  • Depends: orthanc-dicomweb orthanc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-dicomweb.html
• orthanc-webviewer (2.5-2 to 2.6-1)
  • Migration status for orthanc-webviewer (2.5-2 to 2.6-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
  • Depends: orthanc-webviewer orthanc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-webviewer.html
• orthanc-wsi (0.6-2 to 0.7-1)
  • Migration status for orthanc-wsi (0.6-2 to 0.7-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/o/orthanc-wsi.html
• pantalaimon (- to 0.6.2-1)
  • Migration status for pantalaimon (- 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
  • Build-Depends(-Arch): pantalaimon python-matrix-nio
  • Depends: pantalaimon python-matrix-nio
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantalaimon.html
• php-amqplib (2.11.2-1 to 2.11.3-1)
  • Migration status for php-amqplib (2.11.2-1 to 2.11.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 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-amqplib.html
  • Required age reduced by 3 days because of autopkgtest
• ptouch-driver (1.4.2-3 to 1.5.1-2)
  • Migration status for ptouch-driver (1.4.2-3 to 1.5.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
  • Build-Depends(-Arch): ptouch-driver foomatic-db-engine
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ptouch-driver.html
• python-gabbi (1.40.0-5 to 2.0.1-1)
  • Migration status for python-gabbi (1.40.0-5 to 2.0.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 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gabbi.html
• python-httplib2 (0.17.4-1 to 0.18.1-1)
  • Migration status for python-httplib2 (0.17.4-1 to 0.18.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/p/python-httplib2.html
  • Required age reduced by 3 days because of autopkgtest
• python-virtualenv (20.0.21+ds-1 to 20.0.21+ds-2)
  • Migration status for python-virtualenv (20.0.21+ds-1 to 20.0.21+ds-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/p/python-virtualenv.html
  • Required age reduced by 3 days because of autopkgtest
• r-bioc-graph (- to 1.66.0-2)
  • Migration status for r-bioc-graph (- to 1.66.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
  • Depends: r-bioc-graph r-base
  • Depends: r-bioc-graph r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-graph.html
  • Required age reduced by 3 days because of autopkgtest
• r-cran-svglite (1.2.3-2 to 1.2.3-3)
  • Migration status for r-cran-svglite (1.2.3-2 to 1.2.3-3): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-svglite r-base
  • Additional info:
  • Updating r-cran-svglite fixes old bugs: #955316
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-svglite.html
  • Required age reduced by 3 days because of autopkgtest
  • Too young, but urgency pushed by ivodd
  • 0 days old
• rman (3.2-8 to 3.2-9)
  • Migration status for rman (3.2-8 to 3.2-9): 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/rman.html
  • Required age reduced by 3 days because of autopkgtest
• rst2pdf (0.96-1 to 0.97-2)
  • Migration status for rst2pdf (0.96-1 to 0.97-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 rst2pdf fixes old bugs: #960571
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rst2pdf.html
• solaar (1.0.1+dfsg-4 to 1.0.2+dfsg-1)
  • Migration status for solaar (1.0.1+dfsg-4 to 1.0.2+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 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/solaar.html
• spice-html5 (0.1.7-4 to 0.1.7-5)
  • Migration status for spice-html5 (0.1.7-4 to 0.1.7-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/s/spice-html5.html
• symfony (4.4.4-1 to 4.4.8-1)
  • Migration status for symfony (4.4.4-1 to 4.4.8-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:
  • Updating symfony fixes old bugs: #952431, #961415
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/symfony.html
• telemetry-tempest-plugin (1.0.0-2 to 1.0.0-3)
  • Migration status for telemetry-tempest-plugin (1.0.0-2 to 1.0.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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telemetry-tempest-plugin.html
• tome (2.4~0.git.2015.12.29-1.2 to 2.41-ah~0.git.20200131-1)
  • Migration status for tome (2.4~0.git.2015.12.29-1.2 to 2.41-ah~0.git.20200131-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
  • arch:arm64 not built yet, autopkgtest delayed there
  • Too young, only 0 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• udisks2 (2.8.4-2 to 2.9.0-1)
  • Migration status for udisks2 (2.8.4-2 to 2.9.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
  • Build-Depends(-Arch): udisks2 libblockdev
  • Depends: udisks2 libblockdev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/udisks2.html
• vdpauinfo (1.3-1 to 1.4-1)
  • Migration status for vdpauinfo (1.3-1 to 1.4-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/v/vdpauinfo.html
• vows (0.8.3-2 to 0.8.3-3)
  • Migration status for vows (0.8.3-2 to 0.8.3-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/vows.html
  • Required age reduced by 3 days because of autopkgtest
• xen (4.11.3+24-g14b62ab3e5-1 to 4.11.4-1)
  • Migration status for xen (4.11.3+24-g14b62ab3e5-1 to 4.11.4-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/x/xen.html
• zeroc-ice (3.7.3-1 to 3.7.4-1)
  • Migration status for zeroc-ice (3.7.3-1 to 3.7.4-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 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zeroc-ice.html
• akonadi (4:19.08.3-1 to 4:20.04.1-2)
  • Migration status for akonadi (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): akonadi kxmlgui
  • Depends: akonadi kconfig
  • Depends: akonadi kconfigwidgets
  • Depends: akonadi kcoreaddons
  • Depends: akonadi kcrash
  • Depends: akonadi ki18n
  • Depends: akonadi kiconthemes
  • Depends: akonadi kio
  • Depends: akonadi kitemmodels
  • Depends: akonadi kwidgetsaddons
  • Depends: akonadi kwindowsystem
  • Depends: akonadi kxmlgui
  • Implicit dependency: akonadi akonadi-calendar
  • Implicit dependency: akonadi akonadi-calendar-tools
  • Implicit dependency: akonadi akonadi-contacts
  • Implicit dependency: akonadi akonadi-import-wizard
  • Implicit dependency: akonadi akonadi-mime
  • Implicit dependency: akonadi akonadi-search
  • Implicit dependency: akonadi akonadiconsole
  • Implicit dependency: akonadi kaddressbook
  • Implicit dependency: akonadi kalarm
  • Implicit dependency: akonadi kalarmcal
  • Implicit dependency: akonadi kdepim-addons
  • Implicit dependency: akonadi kdepim-runtime
  • Implicit dependency: akonadi kf5-kdepim-apps-libs
  • Implicit dependency: akonadi kf5-messagelib
  • Implicit dependency: akonadi kgpg/amd64
  • Implicit dependency: akonadi kgpg/arm64
  • Implicit dependency: akonadi kgpg/armel
  • Implicit dependency: akonadi kgpg/armhf
  • Implicit dependency: akonadi kgpg/i386
  • Implicit dependency: akonadi kgpg/mips64el
  • Implicit dependency: akonadi kgpg/mipsel
  • Implicit dependency: akonadi kgpg/ppc64el
  • Implicit dependency: akonadi kgpg/s390x
  • Implicit dependency: akonadi kjots/amd64
  • Implicit dependency: akonadi kjots/arm64
  • Implicit dependency: akonadi kjots/armel
  • Implicit dependency: akonadi kjots/armhf
  • Implicit dependency: akonadi kjots/i386
  • Implicit dependency: akonadi kjots/mips64el
  • Implicit dependency: akonadi kjots/mipsel
  • Implicit dependency: akonadi kjots/ppc64el
  • Implicit dependency: akonadi kjots/s390x
  • Implicit dependency: akonadi kmail
  • Implicit dependency: akonadi kmail-account-wizard
  • Implicit dependency: akonadi kmailtransport
  • Implicit dependency: akonadi kmymoney/amd64
  • Implicit dependency: akonadi kmymoney/arm64
  • Implicit dependency: akonadi kmymoney/armel
  • Implicit dependency: akonadi kmymoney/armhf
  • Implicit dependency: akonadi kmymoney/i386
  • Implicit dependency: akonadi kmymoney/mips64el
  • Implicit dependency: akonadi kmymoney/mipsel
  • Implicit dependency: akonadi kmymoney/ppc64el
  • Implicit dependency: akonadi kmymoney/s390x
  • Implicit dependency: akonadi knotes
  • Implicit dependency: akonadi korganizer
  • Implicit dependency: akonadi kraft/amd64
  • Implicit dependency: akonadi kraft/arm64
  • Implicit dependency: akonadi kraft/armel
  • Implicit dependency: akonadi kraft/armhf
  • Implicit dependency: akonadi kraft/i386
  • Implicit dependency: akonadi kraft/mips64el
  • Implicit dependency: akonadi kraft/mipsel
  • Implicit dependency: akonadi kraft/ppc64el
  • Implicit dependency: akonadi kraft/s390x
  • Implicit dependency: akonadi libkf5calendarsupport
  • Implicit dependency: akonadi libkf5eventviews
  • Implicit dependency: akonadi libkf5incidenceeditor
  • Implicit dependency: akonadi libkf5libkdepim
  • Implicit dependency: akonadi libkf5mailcommon
  • Implicit dependency: akonadi libkf5mailimporter
  • Implicit dependency: akonadi libkf5pimcommon
  • Implicit dependency: akonadi mbox-importer
  • Implicit dependency: akonadi pim-data-exporter
  • Implicit dependency: akonadi zanshin/amd64
  • Implicit dependency: akonadi zanshin/arm64
  • Implicit dependency: akonadi zanshin/armel
  • Implicit dependency: akonadi zanshin/armhf
  • Implicit dependency: akonadi zanshin/i386
  • Implicit dependency: akonadi zanshin/mips64el
  • Implicit dependency: akonadi zanshin/mipsel
  • Implicit dependency: akonadi zanshin/ppc64el
  • Implicit dependency: akonadi zanshin/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadi.html
• akonadi-calendar (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akonadi-calendar (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): akonadi-calendar kxmlgui
  • Depends: akonadi-calendar akonadi
  • Depends: akonadi-calendar akonadi-contacts
  • Depends: akonadi-calendar akonadi-mime
  • Depends: akonadi-calendar kcalcore
  • Depends: akonadi-calendar kcalutils
  • Depends: akonadi-calendar kcodecs
  • Depends: akonadi-calendar ki18n
  • Depends: akonadi-calendar kidentitymanagement
  • Depends: akonadi-calendar kio
  • Depends: akonadi-calendar kmailtransport
  • Depends: akonadi-calendar kmime
  • Depends: akonadi-calendar kwidgetsaddons
  • Depends: akonadi-calendar kxmlgui
  • Implicit dependency: akonadi-calendar akonadi-calendar-tools
  • Implicit dependency: akonadi-calendar kdepim-addons
  • Implicit dependency: akonadi-calendar kdepim-runtime
  • Implicit dependency: akonadi-calendar korganizer
  • Implicit dependency: akonadi-calendar libkf5calendarsupport
  • Implicit dependency: akonadi-calendar libkf5eventviews
  • Implicit dependency: akonadi-calendar libkf5incidenceeditor
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadi-calendar.html
• akonadi-calendar-tools (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akonadi-calendar-tools (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • akonadi-calendar-tools unsatisfiable Build-Depends(-Arch) on mipsel: libkf5calendarsupport-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): akonadi-calendar-tools libkf5libkdepim
  • Depends: akonadi-calendar-tools akonadi
  • Depends: akonadi-calendar-tools akonadi-calendar
  • Depends: akonadi-calendar-tools kcalcore
  • Depends: akonadi-calendar-tools kcalutils
  • Depends: akonadi-calendar-tools libkf5calendarsupport
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadi-calendar-tools.html
• akonadi-contacts (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akonadi-contacts (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • migrating libkf5akonadicontact5/4:20.04.1-1/mips64el to testing makes digikam-private-libs/4:6.4.0+dfsg-3/mips64el uninstallable
  • migrating libkf5akonadicontact5/4:20.04.1-1/mipsel to testing makes digikam-private-libs/4:6.4.0+dfsg-3/mipsel uninstallable
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): akonadi-contacts kxmlgui
  • Depends: akonadi-contacts akonadi
  • Depends: akonadi-contacts kcodecs
  • Depends: akonadi-contacts kcompletion
  • Depends: akonadi-contacts kconfig
  • Depends: akonadi-contacts kcontacts
  • Depends: akonadi-contacts ki18n
  • Depends: akonadi-contacts kiconthemes
  • Depends: akonadi-contacts kio
  • Depends: akonadi-contacts kmime
  • Depends: akonadi-contacts kservice
  • Depends: akonadi-contacts ktextwidgets
  • Depends: akonadi-contacts kwidgetsaddons
  • Depends: akonadi-contacts kxmlgui
  • Depends: akonadi-contacts prison-kf5
  • Implicit dependency: akonadi-contacts akonadi-calendar
  • Implicit dependency: akonadi-contacts akonadiconsole
  • Implicit dependency: akonadi-contacts digikam/amd64
  • Implicit dependency: akonadi-contacts digikam/arm64
  • Implicit dependency: akonadi-contacts digikam/armel
  • Implicit dependency: akonadi-contacts digikam/armhf
  • Implicit dependency: akonadi-contacts digikam/i386
  • Implicit dependency: akonadi-contacts digikam/ppc64el
  • Implicit dependency: akonadi-contacts digikam/s390x
  • Implicit dependency: akonadi-contacts grantlee-editor
  • Implicit dependency: akonadi-contacts kaddressbook
  • Implicit dependency: akonadi-contacts kalarm
  • Implicit dependency: akonadi-contacts kdepim-addons
  • Implicit dependency: akonadi-contacts kdepim-runtime
  • Implicit dependency: akonadi-contacts kf5-kdepim-apps-libs
  • Implicit dependency: akonadi-contacts kf5-messagelib
  • Implicit dependency: akonadi-contacts kgpg/amd64
  • Implicit dependency: akonadi-contacts kgpg/arm64
  • Implicit dependency: akonadi-contacts kgpg/armel
  • Implicit dependency: akonadi-contacts kgpg/armhf
  • Implicit dependency: akonadi-contacts kgpg/i386
  • Implicit dependency: akonadi-contacts kgpg/mips64el
  • Implicit dependency: akonadi-contacts kgpg/mipsel
  • Implicit dependency: akonadi-contacts kgpg/ppc64el
  • Implicit dependency: akonadi-contacts kgpg/s390x
  • Implicit dependency: akonadi-contacts kmail
  • Implicit dependency: akonadi-contacts korganizer
  • Implicit dependency: akonadi-contacts kraft/amd64
  • Implicit dependency: akonadi-contacts kraft/arm64
  • Implicit dependency: akonadi-contacts kraft/armel
  • Implicit dependency: akonadi-contacts kraft/armhf
  • Implicit dependency: akonadi-contacts kraft/i386
  • Implicit dependency: akonadi-contacts kraft/mips64el
  • Implicit dependency: akonadi-contacts kraft/mipsel
  • Implicit dependency: akonadi-contacts kraft/ppc64el
  • Implicit dependency: akonadi-contacts kraft/s390x
  • Implicit dependency: akonadi-contacts libkf5incidenceeditor
  • Implicit dependency: akonadi-contacts libkf5libkdepim
  • Implicit dependency: akonadi-contacts libkf5mailcommon
  • Implicit dependency: akonadi-contacts libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadi-contacts.html
• akonadi-import-wizard (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akonadi-import-wizard (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • akonadi-import-wizard unsatisfiable Build-Depends(-Arch) on mipsel: libkf5mailcommon-dev (>= 4:20.04.1~)
  • akonadi-import-wizard unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messageviewer-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): akonadi-import-wizard kwallet-kf5
  • Depends: akonadi-import-wizard akonadi
  • Depends: akonadi-import-wizard kconfig
  • Depends: akonadi-import-wizard kcontacts
  • Depends: akonadi-import-wizard kcrash
  • Depends: akonadi-import-wizard kdbusaddons
  • Depends: akonadi-import-wizard kf5-messagelib
  • Depends: akonadi-import-wizard kidentitymanagement
  • Depends: akonadi-import-wizard kmailtransport
  • Depends: akonadi-import-wizard kwallet-kf5
  • Depends: akonadi-import-wizard libkf5libkdepim
  • Depends: akonadi-import-wizard libkf5mailcommon
  • Depends: akonadi-import-wizard libkf5mailimporter
  • Depends: akonadi-import-wizard libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadi-import-wizard.html
• akonadi-mime (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akonadi-mime (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): akonadi-mime kxmlgui
  • Depends: akonadi-mime akonadi
  • Depends: akonadi-mime kconfigwidgets
  • Depends: akonadi-mime ki18n
  • Depends: akonadi-mime kio
  • Depends: akonadi-mime kmime
  • Depends: akonadi-mime kxmlgui
  • Implicit dependency: akonadi-mime akonadi-calendar
  • Implicit dependency: akonadi-mime akonadi-search
  • Implicit dependency: akonadi-mime kalarm
  • Implicit dependency: akonadi-mime kdepim-addons
  • Implicit dependency: akonadi-mime kdepim-runtime
  • Implicit dependency: akonadi-mime kf5-messagelib
  • Implicit dependency: akonadi-mime kmail
  • Implicit dependency: akonadi-mime kmail-account-wizard
  • Implicit dependency: akonadi-mime kmailtransport
  • Implicit dependency: akonadi-mime korganizer
  • Implicit dependency: akonadi-mime libkf5incidenceeditor
  • Implicit dependency: akonadi-mime libkf5mailcommon
  • Implicit dependency: akonadi-mime libkf5mailimporter
  • Implicit dependency: akonadi-mime pim-data-exporter
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadi-mime.html
• akonadi-notes (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akonadi-notes (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): akonadi-notes kmime
  • Depends: akonadi-notes ki18n
  • Depends: akonadi-notes kmime
  • Implicit dependency: akonadi-notes kdepim-addons
  • Implicit dependency: akonadi-notes kdepim-runtime
  • Implicit dependency: akonadi-notes kjots/amd64
  • Implicit dependency: akonadi-notes kjots/arm64
  • Implicit dependency: akonadi-notes kjots/armel
  • Implicit dependency: akonadi-notes kjots/armhf
  • Implicit dependency: akonadi-notes kjots/i386
  • Implicit dependency: akonadi-notes kjots/mips64el
  • Implicit dependency: akonadi-notes kjots/mipsel
  • Implicit dependency: akonadi-notes kjots/ppc64el
  • Implicit dependency: akonadi-notes kjots/s390x
  • Implicit dependency: akonadi-notes knotes
  • Implicit dependency: akonadi-notes korganizer
  • Implicit dependency: akonadi-notes pim-data-exporter
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadi-notes.html
• akonadi-search (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akonadi-search (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): akonadi-search krunner
  • Depends: akonadi-search akonadi
  • Depends: akonadi-search akonadi-mime
  • Depends: akonadi-search kcalcore
  • Depends: akonadi-search kconfig
  • Depends: akonadi-search kconfigwidgets
  • Depends: akonadi-search kcontacts
  • Depends: akonadi-search ki18n
  • Depends: akonadi-search kmime
  • Depends: akonadi-search krunner
  • Implicit dependency: akonadi-search akonadiconsole
  • Implicit dependency: akonadi-search kaddressbook
  • Implicit dependency: akonadi-search kf5-messagelib
  • Implicit dependency: akonadi-search kmail
  • Implicit dependency: akonadi-search knotes
  • Implicit dependency: akonadi-search libkf5libkdepim
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadi-search.html
• akonadiconsole (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akonadiconsole (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • akonadiconsole unsatisfiable Build-Depends(-Arch) on mipsel: libkf5calendarsupport-dev (>= 4:20.04.1~)
  • akonadiconsole unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messageviewer-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): akonadiconsole kxmlgui
  • Depends: akonadiconsole akonadi
  • Depends: akonadiconsole akonadi-contacts
  • Depends: akonadiconsole akonadi-search
  • Depends: akonadiconsole kcalcore
  • Depends: akonadiconsole kcompletion
  • Depends: akonadiconsole kconfig
  • Depends: akonadiconsole kconfigwidgets
  • Depends: akonadiconsole kcontacts
  • Depends: akonadiconsole kcrash
  • Depends: akonadiconsole kdbusaddons
  • Depends: akonadiconsole kf5-messagelib
  • Depends: akonadiconsole ki18n
  • Depends: akonadiconsole kitemmodels
  • Depends: akonadiconsole kmime
  • Depends: akonadiconsole ktextwidgets
  • Depends: akonadiconsole kwidgetsaddons
  • Depends: akonadiconsole kxmlgui
  • Depends: akonadiconsole libkf5calendarsupport
  • Depends: akonadiconsole libkf5libkdepim
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akonadiconsole.html
• akregator (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for akregator (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • akregator unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messageviewer-dev (>= 4:20.04.1~)
  • akregator unsatisfiable Build-Depends(-Arch) on mipsel: libkf5webengineviewer-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): akregator kxmlgui
  • Depends: akregator kcmutils
  • Depends: akregator kconfigwidgets
  • Depends: akregator kcrash
  • Depends: akregator kf5-messagelib
  • Depends: akregator kio
  • Depends: akregator knotifications
  • Depends: akregator knotifyconfig
  • Depends: akregator kontactinterface
  • Depends: akregator kparts
  • Depends: akregator kpimtextedit
  • Depends: akregator kxmlgui
  • Depends: akregator libkf5grantleetheme
  • Depends: akregator libkf5libkdepim
  • Depends: akregator libkf5pimcommon
  • Depends: akregator syndication
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/akregator.html
• attica-kf5 (5.62.0-1 to 5.70.0-1)
  • Migration status for attica-kf5 (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): attica-kf5 extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/attica-kf5.html
  • Required age reduced by 3 days because of autopkgtest
• azure-uamqp-python (1.2.6-4 to 1.2.8-1)
  • Migration status for azure-uamqp-python (1.2.6-4 to 1.2.8-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/azure-uamqp-python.html
  • Required age reduced by 3 days because of autopkgtest
• baloo-kf5 (5.62.0-2 to 5.70.0-1)
  • Migration status for baloo-kf5 (5.62.0-2 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for baloo-kf5/5.70.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): baloo-kf5 solid
  • Depends: baloo-kf5 kconfig
  • Depends: baloo-kf5 kcoreaddons
  • Depends: baloo-kf5 kcrash
  • Depends: baloo-kf5 kdbusaddons
  • Depends: baloo-kf5 kfilemetadata-kf5
  • Depends: baloo-kf5 ki18n
  • Depends: baloo-kf5 kidletime
  • Depends: baloo-kf5 kio
  • Depends: baloo-kf5 solid
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/baloo-kf5.html
• bamtools (2.5.1+dfsg-5 to 2.5.1+dfsg-6)
  • Migration status for bamtools (2.5.1+dfsg-5 to 2.5.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 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bamtools.html
  • Required age reduced by 3 days because of autopkgtest
• beautifulsoup4 (4.9.0-2 to 4.9.1-1)
  • Migration status for beautifulsoup4 (4.9.0-2 to 4.9.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/b/beautifulsoup4.html
  • Required age reduced by 3 days because of autopkgtest
• bluez-qt (5.62.0-1 to 5.70.0-1)
  • Migration status for bluez-qt (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): bluez-qt extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bluez-qt.html
  • Required age reduced by 3 days because of autopkgtest
• breeze-icons (4:5.62.0-1 to 4:5.70.0-1)
  • Migration status for breeze-icons (4:5.62.0-1 to 4:5.70.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
  • Build-Depends(-Arch): breeze-icons extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breeze-icons.html
• bzip2 (1.0.8-2 to 1.0.8-3)
  • Migration status for bzip2 (1.0.8-2 to 1.0.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 7 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bzip2.html
  • Required age reduced by 3 days because of autopkgtest
• cat-bat (- to 5.0.5-1)
  • Migration status for cat-bat (- to 5.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/c/cat-bat.html
• debian-cd (3.1.28 to 3.1.29)
  • Migration status for debian-cd (3.1.28 to 3.1.29): 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/d/debian-cd.html
• dino-im (0.1.0-3 to 0.1.0-4)
  • Migration status for dino-im (0.1.0-3 to 0.1.0-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/d/dino-im.html
• extra-cmake-modules (5.62.0-1 to 5.70.0-1)
  • Migration status for extra-cmake-modules (5.62.0-1 to 5.70.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:
  • Updating extra-cmake-modules fixes old bugs: #955117
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/extra-cmake-modules.html
• flash (- to 1.2.11-1)
  • Migration status for flash (- to 1.2.11-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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flash.html
• flint (2.5.2-21 to 2.5.2-23)
  • Migration status for flint (2.5.2-21 to 2.5.2-23): 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/flint.html
• fonts-cascadia-code (1911.21-1 to 2005.15-1)
  • Migration status for fonts-cascadia-code (1911.21-1 to 2005.15-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/f/fonts-cascadia-code.html
• fossil (1:2.10-1 to 1:2.11-1)
  • Migration status for fossil (1:2.10-1 to 1:2.11-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/f/fossil.html
• frameworkintegration (5.62.0-1 to 5.70.0-1)
  • Migration status for frameworkintegration (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): frameworkintegration kwidgetsaddons
  • Depends: frameworkintegration kconfig
  • Depends: frameworkintegration kconfigwidgets
  • Depends: frameworkintegration ki18n
  • Depends: frameworkintegration kiconthemes
  • Depends: frameworkintegration knewstuff
  • Depends: frameworkintegration knotifications
  • Depends: frameworkintegration kwidgetsaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frameworkintegration.html
  • Required age reduced by 3 days because of autopkgtest
• frescobaldi (3.1.1+ds1-1 to 3.1.2+ds1-1)
  • Migration status for frescobaldi (3.1.1+ds1-1 to 3.1.2+ds1-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/f/frescobaldi.html
• gazebo (11.0.0+dfsg1-2 to 11.0.0+dfsg1-3)
  • Migration status for gazebo (11.0.0+dfsg1-2 to 11.0.0+dfsg1-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 gazebo fixes old bugs: #961561
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gazebo.html
  • uninstallable on arch arm64, not running autopkgtest there
  • Required age reduced by 3 days because of autopkgtest
• ghc (8.8.1+dfsg1+is+8.6.5+dfsg1-3 to 8.8.3-1)
  • Migration status for ghc (8.8.1+dfsg1+is+8.6.5+dfsg1-3 to 8.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for haskell-hgettext/0.1.31.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for haskell-hoogle/5.0.17.3+dfsg1-5: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for haskell-hopenpgp/2.8.5-1: amd64: Regression ♻ , arm64: Regression ♻
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghc.html
• git (1:2.26.2-1 to 1:2.27.0~rc2-1)
  • Migration status for git (1:2.26.2-1 to 1:2.27.0~rc2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating git introduces new bugs: #961702
  • autopkgtest for fdroidserver/1.1.7-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git.html
• git-cola (3.6-1 to 3.7-1)
  • Migration status for git-cola (3.6-1 to 3.7-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/git-cola.html
• git-remote-hg (- to 1.0.1~ds-2)
  • Migration status for git-remote-hg (- to 1.0.1~ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating git-remote-hg introduces new bugs: #943032
  • Too young, only 1 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-remote-hg.html
  • Required age reduced by 3 days because of autopkgtest
• grantlee-editor (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for grantlee-editor (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • grantlee-editor unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kaddressbookgrantlee-dev (>= 4:20.04.1~)
  • grantlee-editor unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messageviewer-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): grantlee-editor kxmlgui
  • Depends: grantlee-editor akonadi-contacts
  • Depends: grantlee-editor karchive
  • Depends: grantlee-editor kcrash
  • Depends: grantlee-editor kdbusaddons
  • Depends: grantlee-editor kf5-kdepim-apps-libs
  • Depends: grantlee-editor kf5-messagelib
  • Depends: grantlee-editor kio
  • Depends: grantlee-editor kmime
  • Depends: grantlee-editor knewstuff
  • Depends: grantlee-editor kpimtextedit
  • Depends: grantlee-editor ksyntax-highlighting
  • Depends: grantlee-editor kxmlgui
  • Depends: grantlee-editor libkf5grantleetheme
  • Depends: grantlee-editor libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grantlee-editor.html
• groovycsv (1.3-1 to 1.3-2)
  • Migration status for groovycsv (1.3-1 to 1.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 5 days old
  • Additional info:
  • Updating groovycsv fixes old bugs: #952292
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/groovycsv.html
• ivar (- to 1.2.2+dfsg-2)
  • Migration status for ivar (- to 1.2.2+dfsg-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/i/ivar.html
• janus (0.9.4-1 to 0.9.5-1)
  • Migration status for janus (0.9.4-1 to 0.9.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/j/janus.html
• jose (10-2 to 10-3)
  • Migration status for jose (10-2 to 10-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/j/jose.html
  • Required age reduced by 3 days because of autopkgtest
• kactivities-kf5 (5.62.0-1 to 5.70.0-1)
  • Migration status for kactivities-kf5 (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kactivities-kf5 kwindowsystem
  • Depends: kactivities-kf5 kconfig
  • Depends: kactivities-kf5 kcoreaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kactivities-kf5.html
  • Required age reduced by 3 days because of autopkgtest
• kactivities-stats (5.62.0-1 to 5.70.0-1)
  • Migration status for kactivities-stats (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kactivities-stats kconfig
  • Depends: kactivities-stats kactivities-kf5
  • Depends: kactivities-stats kconfig
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kactivities-stats.html
  • Required age reduced by 3 days because of autopkgtest
• kaddressbook (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kaddressbook (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • kaddressbook unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kaddressbookgrantlee-dev (>= 4:20.04.1~)
  • kaddressbook unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kaddressbookimportexport-dev (>= 4:20.04.1~)
  • kaddressbook unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kdepimdbusinterfaces-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kaddressbook prison-kf5
  • Depends: kaddressbook akonadi
  • Depends: kaddressbook akonadi-contacts
  • Depends: kaddressbook akonadi-search
  • Depends: kaddressbook kcmutils
  • Depends: kaddressbook kcrash
  • Depends: kaddressbook kf5-kdepim-apps-libs
  • Depends: kaddressbook kontactinterface
  • Depends: kaddressbook libkf5grantleetheme
  • Depends: kaddressbook libkf5libkdepim
  • Depends: kaddressbook libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kaddressbook.html
• kalarm (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kalarm (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • kalarm unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kdepimdbusinterfaces-dev (>= 4:20.04.1~)
  • kalarm unsatisfiable Build-Depends(-Arch) on mipsel: libkf5mailcommon-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kalarm kxmlgui
  • Depends: kalarm akonadi
  • Depends: kalarm akonadi-contacts
  • Depends: kalarm akonadi-mime
  • Depends: kalarm kalarmcal
  • Depends: kalarm kauth
  • Depends: kalarm kcalcore
  • Depends: kalarm kcalutils
  • Depends: kalarm kcodecs
  • Depends: kalarm kcompletion
  • Depends: kalarm kconfig
  • Depends: kalarm kconfigwidgets
  • Depends: kalarm kcrash
  • Depends: kalarm kdbusaddons
  • Depends: kalarm kglobalaccel
  • Depends: kalarm kguiaddons
  • Depends: kalarm kholidays
  • Depends: kalarm ki18n
  • Depends: kalarm kidentitymanagement
  • Depends: kalarm kio
  • Depends: kalarm kjobwidgets
  • Depends: kalarm kmailtransport
  • Depends: kalarm kmime
  • Depends: kalarm knotifications
  • Depends: kalarm kpimtextedit
  • Depends: kalarm kwidgetsaddons
  • Depends: kalarm kwindowsystem
  • Depends: kalarm kxmlgui
  • Depends: kalarm libkf5libkdepim
  • Depends: kalarm libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kalarm.html
• kalarmcal (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kalarmcal (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): kalarmcal kidentitymanagement
  • Depends: kalarmcal akonadi
  • Depends: kalarmcal kcalcore
  • Depends: kalarmcal kcalutils
  • Depends: kalarmcal kholidays
  • Depends: kalarmcal ki18n
  • Depends: kalarmcal kidentitymanagement
  • Implicit dependency: kalarmcal kalarm
  • Implicit dependency: kalarmcal kdepim-runtime
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kalarmcal.html
• kapidox (5.62.0-1 to 5.70.0-1)
  • Migration status for kapidox (5.62.0-1 to 5.70.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/k/kapidox.html
• karchive (5.62.0-1 to 5.70.0-1)
  • Migration status for karchive (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): karchive extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/karchive.html
  • Required age reduced by 3 days because of autopkgtest
• kauth (5.62.0-1 to 5.70.0-1)
  • Migration status for kauth (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kauth kcoreaddons
  • Depends: kauth kcoreaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kauth.html
  • Required age reduced by 3 days because of autopkgtest
• kblog (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kblog (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): kblog kio
  • Depends: kblog kcalcore
  • Depends: kblog kcoreaddons
  • Depends: kblog ki18n
  • Depends: kblog kio
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kblog.html
• kbookmarks (5.62.0-1 to 5.70.0-1)
  • Migration status for kbookmarks (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kbookmarks kxmlgui
  • Depends: kbookmarks kcodecs
  • Depends: kbookmarks kconfig
  • Depends: kbookmarks kconfigwidgets
  • Depends: kbookmarks kcoreaddons
  • Depends: kbookmarks kwidgetsaddons
  • Depends: kbookmarks kxmlgui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kbookmarks.html
  • Required age reduced by 3 days because of autopkgtest
• kcalcore (4:19.08.3-2 to 5:5.70.0-1)
  • Migration status for kcalcore (4:19.08.3-2 to 5:5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • migrating libkf5calendarcore5abi2/5:5.70.0-1/mips64el to testing makes digikam-private-libs/4:6.4.0+dfsg-3/mips64el uninstallable
  • migrating libkf5calendarcore5abi2/5:5.70.0-1/mipsel to testing makes digikam-private-libs/4:6.4.0+dfsg-3/mipsel uninstallable
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kcalcore extra-cmake-modules
  • Implicit dependency: kcalcore akonadi-calendar
  • Implicit dependency: kcalcore akonadi-calendar-tools
  • Implicit dependency: kcalcore akonadi-search
  • Implicit dependency: kcalcore akonadiconsole
  • Implicit dependency: kcalcore digikam/amd64
  • Implicit dependency: kcalcore digikam/arm64
  • Implicit dependency: kcalcore digikam/armel
  • Implicit dependency: kcalcore digikam/armhf
  • Implicit dependency: kcalcore digikam/i386
  • Implicit dependency: kcalcore digikam/ppc64el
  • Implicit dependency: kcalcore digikam/s390x
  • Implicit dependency: kcalcore kalarm
  • Implicit dependency: kcalcore kalarmcal
  • Implicit dependency: kcalcore kblog
  • Implicit dependency: kcalcore kcalutils
  • Implicit dependency: kcalcore kdepim-addons
  • Implicit dependency: kcalcore kdepim-runtime
  • Implicit dependency: kcalcore kf5-messagelib
  • Implicit dependency: kcalcore kitinerary
  • Implicit dependency: kcalcore kmail
  • Implicit dependency: kcalcore knotes
  • Implicit dependency: kcalcore korganizer
  • Implicit dependency: kcalcore ktnef
  • Implicit dependency: kcalcore libkf5calendarsupport
  • Implicit dependency: kcalcore libkf5eventviews
  • Implicit dependency: kcalcore libkf5incidenceeditor
  • Implicit dependency: kcalcore libkgapi
  • Implicit dependency: kcalcore pim-data-exporter
  • Implicit dependency: kcalcore zanshin/amd64
  • Implicit dependency: kcalcore zanshin/arm64
  • Implicit dependency: kcalcore zanshin/armel
  • Implicit dependency: kcalcore zanshin/armhf
  • Implicit dependency: kcalcore zanshin/i386
  • Implicit dependency: kcalcore zanshin/mips64el
  • Implicit dependency: kcalcore zanshin/mipsel
  • Implicit dependency: kcalcore zanshin/ppc64el
  • Implicit dependency: kcalcore zanshin/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcalcore.html
• kcalutils (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kcalutils (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): kcalutils kwidgetsaddons
  • Depends: kcalutils kcalcore
  • Depends: kcalutils kcodecs
  • Depends: kcalutils kconfig
  • Depends: kcalutils kcoreaddons
  • Depends: kcalutils ki18n
  • Depends: kcalutils kiconthemes
  • Depends: kcalutils kidentitymanagement
  • Depends: kcalutils kwidgetsaddons
  • Implicit dependency: kcalutils akonadi-calendar
  • Implicit dependency: kcalutils akonadi-calendar-tools
  • Implicit dependency: kcalutils kalarm
  • Implicit dependency: kcalutils kalarmcal
  • Implicit dependency: kcalutils kdepim-addons
  • Implicit dependency: kcalutils kmail
  • Implicit dependency: kcalutils knotes
  • Implicit dependency: kcalutils korganizer
  • Implicit dependency: kcalutils ktnef
  • Implicit dependency: kcalutils libkf5calendarsupport
  • Implicit dependency: kcalutils libkf5eventviews
  • Implicit dependency: kcalutils libkf5incidenceeditor
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcalutils.html
• kcmutils (5.62.0-1 to 5.70.0-1)
  • Migration status for kcmutils (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kcmutils kxmlgui
  • Depends: kcmutils kconfigwidgets
  • Depends: kcmutils kcoreaddons
  • Depends: kcmutils kdeclarative
  • Depends: kcmutils kguiaddons
  • Depends: kcmutils ki18n
  • Depends: kcmutils kitemviews
  • Depends: kcmutils kservice
  • Depends: kcmutils kxmlgui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcmutils.html
  • Required age reduced by 3 days because of autopkgtest
• kcodecs (5.62.0-1 to 5.70.0-1)
  • Migration status for kcodecs (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kcodecs extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcodecs.html
  • Required age reduced by 3 days because of autopkgtest
• kcompletion (5.62.0-1 to 5.70.0-1)
  • Migration status for kcompletion (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kcompletion kwidgetsaddons
  • Depends: kcompletion kconfig
  • Depends: kcompletion kwidgetsaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcompletion.html
  • Required age reduced by 3 days because of autopkgtest
• kconfig (5.62.0-1 to 5.70.0-1)
  • Migration status for kconfig (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kconfig extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kconfig.html
  • Required age reduced by 3 days because of autopkgtest
• kconfigwidgets (5.62.0-1 to 5.70.0-1)
  • Migration status for kconfigwidgets (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kconfigwidgets kwidgetsaddons
  • Depends: kconfigwidgets kauth
  • Depends: kconfigwidgets kcodecs
  • Depends: kconfigwidgets kconfig
  • Depends: kconfigwidgets kcoreaddons
  • Depends: kconfigwidgets kguiaddons
  • Depends: kconfigwidgets ki18n
  • Depends: kconfigwidgets kwidgetsaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kconfigwidgets.html
  • Required age reduced by 3 days because of autopkgtest
• kcontacts (4:19.08.3-1 to 5:5.70.0-1)
  • Migration status for kcontacts (4:19.08.3-1 to 5:5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • migrating libkf5contacts5/5:5.70.0-1/mips64el to testing makes digikam-private-libs/4:6.4.0+dfsg-3/mips64el uninstallable
  • migrating libkf5contacts5/5:5.70.0-1/mipsel to testing makes digikam-private-libs/4:6.4.0+dfsg-3/mipsel uninstallable
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kcontacts ki18n
  • Depends: kcontacts kcodecs
  • Depends: kcontacts kconfig
  • Depends: kcontacts kcoreaddons
  • Depends: kcontacts ki18n
  • Implicit dependency: kcontacts akonadi-calendar
  • Implicit dependency: kcontacts akonadi-contacts
  • Implicit dependency: kcontacts akonadi-import-wizard
  • Implicit dependency: kcontacts akonadi-search
  • Implicit dependency: kcontacts akonadiconsole
  • Implicit dependency: kcontacts digikam/amd64
  • Implicit dependency: kcontacts digikam/arm64
  • Implicit dependency: kcontacts digikam/armel
  • Implicit dependency: kcontacts digikam/armhf
  • Implicit dependency: kcontacts digikam/i386
  • Implicit dependency: kcontacts digikam/ppc64el
  • Implicit dependency: kcontacts digikam/s390x
  • Implicit dependency: kcontacts grantlee-editor
  • Implicit dependency: kcontacts kaddressbook
  • Implicit dependency: kcontacts kalarm
  • Implicit dependency: kcontacts kdepim-addons
  • Implicit dependency: kcontacts kdepim-runtime
  • Implicit dependency: kcontacts kf5-kdepim-apps-libs
  • Implicit dependency: kcontacts kf5-messagelib
  • Implicit dependency: kcontacts kgpg/amd64
  • Implicit dependency: kcontacts kgpg/arm64
  • Implicit dependency: kcontacts kgpg/armel
  • Implicit dependency: kcontacts kgpg/armhf
  • Implicit dependency: kcontacts kgpg/i386
  • Implicit dependency: kcontacts kgpg/mips64el
  • Implicit dependency: kcontacts kgpg/mipsel
  • Implicit dependency: kcontacts kgpg/ppc64el
  • Implicit dependency: kcontacts kgpg/s390x
  • Implicit dependency: kcontacts kitinerary
  • Implicit dependency: kcontacts kmail
  • Implicit dependency: kcontacts kmymoney/amd64
  • Implicit dependency: kcontacts kmymoney/arm64
  • Implicit dependency: kcontacts kmymoney/armel
  • Implicit dependency: kcontacts kmymoney/armhf
  • Implicit dependency: kcontacts kmymoney/i386
  • Implicit dependency: kcontacts kmymoney/mips64el
  • Implicit dependency: kcontacts kmymoney/mipsel
  • Implicit dependency: kcontacts kmymoney/ppc64el
  • Implicit dependency: kcontacts kmymoney/s390x
  • Implicit dependency: kcontacts knotes
  • Implicit dependency: kcontacts korganizer
  • Implicit dependency: kcontacts kraft/amd64
  • Implicit dependency: kcontacts kraft/arm64
  • Implicit dependency: kcontacts kraft/armel
  • Implicit dependency: kcontacts kraft/armhf
  • Implicit dependency: kcontacts kraft/i386
  • Implicit dependency: kcontacts kraft/mips64el
  • Implicit dependency: kcontacts kraft/mipsel
  • Implicit dependency: kcontacts kraft/ppc64el
  • Implicit dependency: kcontacts kraft/s390x
  • Implicit dependency: kcontacts ktnef
  • Implicit dependency: kcontacts libkf5eventviews
  • Implicit dependency: kcontacts libkf5incidenceeditor
  • Implicit dependency: kcontacts libkf5libkdepim
  • Implicit dependency: kcontacts libkf5mailcommon
  • Implicit dependency: kcontacts libkf5pimcommon
  • Implicit dependency: kcontacts libkgapi
  • Implicit dependency: kcontacts pim-data-exporter
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcontacts.html
• kcoreaddons (5.62.0-1 to 5.70.0-1)
  • Migration status for kcoreaddons (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kcoreaddons extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcoreaddons.html
  • Required age reduced by 3 days because of autopkgtest
• kcrash (5.62.0-1 to 5.70.0-1)
  • Migration status for kcrash (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kcrash kwindowsystem
  • Depends: kcrash kcoreaddons
  • Depends: kcrash kwindowsystem
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcrash.html
  • Required age reduced by 3 days because of autopkgtest
• kdav (19.08.3-1 to 20.04.1-1)
  • Migration status for kdav (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kdav kio
  • Depends: kdav kcoreaddons
  • Depends: kdav ki18n
  • Depends: kdav kio
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdav.html
• kdbusaddons (5.62.0-1 to 5.70.0-1)
  • Migration status for kdbusaddons (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kdbusaddons extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdbusaddons.html
  • Required age reduced by 3 days because of autopkgtest
• kdeclarative (5.62.0-1 to 5.70.0-1)
  • Migration status for kdeclarative (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kdeclarative kwindowsystem
  • Depends: kdeclarative kconfig
  • Depends: kdeclarative kglobalaccel
  • Depends: kdeclarative ki18n
  • Depends: kdeclarative kiconthemes
  • Depends: kdeclarative kio
  • Depends: kdeclarative kpackage
  • Depends: kdeclarative kwidgetsaddons
  • Depends: kdeclarative kwindowsystem
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdeclarative.html
  • Required age reduced by 3 days because of autopkgtest
• kded (5.62.0-1 to 5.70.0-1)
  • Migration status for kded (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kded kservice
  • Depends: kded kconfig
  • Depends: kded kcoreaddons
  • Depends: kded kcrash
  • Depends: kded kdbusaddons
  • Depends: kded kservice
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kded.html
• kdelibs4support (5.62.0-2 to 5.70.0-1)
  • Migration status for kdelibs4support (5.62.0-2 to 5.70.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
  • Build-Depends(-Arch): kdelibs4support kxmlgui
  • Depends: kdelibs4support kcompletion
  • Depends: kdelibs4support kconfig
  • Depends: kdelibs4support kconfigwidgets
  • Depends: kdelibs4support kcrash
  • Depends: kdelibs4support kdbusaddons
  • Depends: kdelibs4support kdesignerplugin
  • Depends: kdelibs4support kdoctools
  • Depends: kdelibs4support kemoticons
  • Depends: kdelibs4support kglobalaccel
  • Depends: kdelibs4support kguiaddons
  • Depends: kdelibs4support ki18n
  • Depends: kdelibs4support kiconthemes
  • Depends: kdelibs4support kio
  • Depends: kdelibs4support knotifications
  • Depends: kdelibs4support kparts
  • Depends: kdelibs4support kservice
  • Depends: kdelibs4support ktextwidgets
  • Depends: kdelibs4support kunitconversion
  • Depends: kdelibs4support kwidgetsaddons
  • Depends: kdelibs4support kwindowsystem
  • Depends: kdelibs4support kxmlgui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdelibs4support.html
  • Required age reduced by 3 days because of autopkgtest
• kdepim-addons (19.08.3-1 to 20.04.1-1)
  • Migration status for kdepim-addons (19.08.3-1 to 20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5calendarsupport-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5eventviews-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5gravatar-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5incidenceeditor-dev (>= 20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kaddressbookgrantlee-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kaddressbookimportexport-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5ksieve-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5mailcommon-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messagecomposer-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messagecore-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messagelist-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messageviewer-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5templateparser-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkf5webengineviewer-dev (>= 4:20.04.1~)
  • kdepim-addons unsatisfiable Build-Depends(-Arch) on mipsel: libkpimimportwizard-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kdepim-addons kpkpass
  • Depends: kdepim-addons akonadi
  • Depends: kdepim-addons akonadi-calendar
  • Depends: kdepim-addons akonadi-contacts
  • Depends: kdepim-addons akonadi-import-wizard
  • Depends: kdepim-addons akonadi-mime
  • Depends: kdepim-addons akonadi-notes
  • Depends: kdepim-addons kcalcore
  • Depends: kdepim-addons kcalutils
  • Depends: kdepim-addons kconfig
  • Depends: kdepim-addons kcontacts
  • Depends: kdepim-addons kdeclarative
  • Depends: kdepim-addons kf5-kdepim-apps-libs
  • Depends: kdepim-addons kf5-messagelib
  • Depends: kdepim-addons ki18n
  • Depends: kdepim-addons kiconthemes
  • Depends: kdepim-addons kidentitymanagement
  • Depends: kdepim-addons kimap
  • Depends: kdepim-addons kio
  • Depends: kdepim-addons kitinerary
  • Depends: kdepim-addons kmailtransport
  • Depends: kdepim-addons kmime
  • Depends: kdepim-addons kontactinterface
  • Depends: kdepim-addons kpimtextedit
  • Depends: kdepim-addons kpkpass
  • Depends: kdepim-addons ksyntax-highlighting
  • Depends: kdepim-addons ktnef
  • Depends: kdepim-addons kxmlgui
  • Depends: kdepim-addons libkf5calendarsupport
  • Depends: kdepim-addons libkf5eventviews
  • Depends: kdepim-addons libkf5grantleetheme
  • Depends: kdepim-addons libkf5gravatar
  • Depends: kdepim-addons libkf5incidenceeditor
  • Depends: kdepim-addons libkf5ksieve
  • Depends: kdepim-addons libkf5libkdepim
  • Depends: kdepim-addons libkf5libkleo
  • Depends: kdepim-addons libkf5mailcommon
  • Depends: kdepim-addons libkf5mailimporter
  • Depends: kdepim-addons libkf5pimcommon
  • Depends: kdepim-addons prison-kf5
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdepim-addons.html
• kdepim-runtime (4:19.08.3-2 to 4:20.04.1-1)
  • Migration status for kdepim-runtime (4:19.08.3-2 to 4:20.04.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kdepim-runtime kwindowsystem
  • Build-Depends(-Arch): kdepim-runtime libkgapi
  • Depends: kdepim-runtime akonadi
  • Depends: kdepim-runtime akonadi-calendar
  • Depends: kdepim-runtime akonadi-contacts
  • Depends: kdepim-runtime akonadi-mime
  • Depends: kdepim-runtime akonadi-notes
  • Depends: kdepim-runtime kalarmcal
  • Depends: kdepim-runtime kcalcore
  • Depends: kdepim-runtime kcodecs
  • Depends: kdepim-runtime kconfig
  • Depends: kdepim-runtime kconfigwidgets
  • Depends: kdepim-runtime kcontacts
  • Depends: kdepim-runtime kdav
  • Depends: kdepim-runtime kidentitymanagement
  • Depends: kdepim-runtime kimap
  • Depends: kdepim-runtime kio
  • Depends: kdepim-runtime kmailtransport
  • Depends: kdepim-runtime kmbox
  • Depends: kdepim-runtime kmime
  • Depends: kdepim-runtime knotifications
  • Depends: kdepim-runtime knotifyconfig
  • Depends: kdepim-runtime ktextwidgets
  • Depends: kdepim-runtime kwindowsystem
  • Depends: kdepim-runtime libkgapi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdepim-runtime.html
• kdesignerplugin (5.62.0-1 to 5.70.0-1)
  • Migration status for kdesignerplugin (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kdesignerplugin kdoctools
  • Depends: kdesignerplugin kconfig
  • Depends: kdesignerplugin kcoreaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdesignerplugin.html
• kdesu (5.62.0-1 to 5.70.0-1)
  • Migration status for kdesu (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kdelibs4support/5.62.0-2: amd64: Regression ♻ , arm64: Pass
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kdesu kservice
  • Depends: kdesu kcoreaddons
  • Depends: kdesu ki18n
  • Depends: kdesu kpty
  • Depends: kdesu kservice
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdesu.html
• kdewebkit (5.62.0-1 to 5.70.0-1)
  • Migration status for kdewebkit (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kdelibs4support/5.62.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kdewebkit kwallet-kf5
  • Depends: kdewebkit kconfig
  • Depends: kdewebkit kcoreaddons
  • Depends: kdewebkit kio
  • Depends: kdewebkit kjobwidgets
  • Depends: kdewebkit kparts
  • Depends: kdewebkit kservice
  • Depends: kdewebkit kwallet-kf5
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdewebkit.html
• kdnssd-kf5 (5.62.0-1 to 5.70.0-1)
  • Migration status for kdnssd-kf5 (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kdnssd-kf5 extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdnssd-kf5.html
  • Required age reduced by 3 days because of autopkgtest
• kdoctools (5.62.0-1 to 5.70.0-1)
  • Migration status for kdoctools (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kdoctools ki18n
  • Depends: kdoctools karchive
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdoctools.html
  • Required age reduced by 3 days because of autopkgtest
• kemoticons (5.62.0-1 to 5.70.0-1)
  • Migration status for kemoticons (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kemoticons kservice
  • Depends: kemoticons karchive
  • Depends: kemoticons kconfig
  • Depends: kemoticons kcoreaddons
  • Depends: kemoticons kservice
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kemoticons.html
  • Required age reduced by 3 days because of autopkgtest
• kf5-kdepim-apps-libs (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kf5-kdepim-apps-libs (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kf5-kdepim-apps-libs kwidgetsaddons
  • Depends: kf5-kdepim-apps-libs akonadi
  • Depends: kf5-kdepim-apps-libs akonadi-contacts
  • Depends: kf5-kdepim-apps-libs kconfig
  • Depends: kf5-kdepim-apps-libs kconfigwidgets
  • Depends: kf5-kdepim-apps-libs kcontacts
  • Depends: kf5-kdepim-apps-libs kcoreaddons
  • Depends: kf5-kdepim-apps-libs ki18n
  • Depends: kf5-kdepim-apps-libs kio
  • Depends: kf5-kdepim-apps-libs kservice
  • Depends: kf5-kdepim-apps-libs kwidgetsaddons
  • Depends: kf5-kdepim-apps-libs libkf5grantleetheme
  • Depends: kf5-kdepim-apps-libs libkf5libkleo
  • Depends: kf5-kdepim-apps-libs libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kf5-kdepim-apps-libs.html
• kf5-messagelib (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kf5-messagelib (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • kf5-messagelib unsatisfiable Build-Depends(-Arch) on mipsel: libkf5followupreminder-dev (>= 4:20.04.1~)
  • kf5-messagelib unsatisfiable Build-Depends(-Arch) on mipsel: libkf5gravatar-dev (>= 4:20.04.1~)
  • kf5-messagelib unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kaddressbookgrantlee-dev (>= 4:20.04.1~)
  • kf5-messagelib unsatisfiable Build-Depends(-Arch) on mipsel: libkf5sendlater-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kf5-messagelib kxmlgui
  • Depends: kf5-messagelib akonadi
  • Depends: kf5-messagelib akonadi-contacts
  • Depends: kf5-messagelib akonadi-mime
  • Depends: kf5-messagelib akonadi-search
  • Depends: kf5-messagelib karchive
  • Depends: kf5-messagelib kcalcore
  • Depends: kf5-messagelib kcodecs
  • Depends: kf5-messagelib kcompletion
  • Depends: kf5-messagelib kconfig
  • Depends: kf5-messagelib kconfigwidgets
  • Depends: kf5-messagelib kcontacts
  • Depends: kf5-messagelib kf5-kdepim-apps-libs
  • Depends: kf5-messagelib ki18n
  • Depends: kf5-messagelib kiconthemes
  • Depends: kf5-messagelib kidentitymanagement
  • Depends: kf5-messagelib kio
  • Depends: kf5-messagelib kitemviews
  • Depends: kf5-messagelib kjobwidgets
  • Depends: kf5-messagelib kmailtransport
  • Depends: kf5-messagelib kmbox
  • Depends: kf5-messagelib kmime
  • Depends: kf5-messagelib kpimtextedit
  • Depends: kf5-messagelib kservice
  • Depends: kf5-messagelib ksyntax-highlighting
  • Depends: kf5-messagelib ktextwidgets
  • Depends: kf5-messagelib kwidgetsaddons
  • Depends: kf5-messagelib kxmlgui
  • Depends: kf5-messagelib libkf5grantleetheme
  • Depends: kf5-messagelib libkf5gravatar
  • Depends: kf5-messagelib libkf5libkdepim
  • Depends: kf5-messagelib libkf5libkleo
  • Depends: kf5-messagelib libkf5pimcommon
  • Depends: kf5-messagelib sonnet
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kf5-messagelib.html
• kfilemetadata-kf5 (5.62.0-1 to 5.70.0-1)
  • Migration status for kfilemetadata-kf5 (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kfilemetadata-kf5 ki18n
  • Depends: kfilemetadata-kf5 karchive
  • Depends: kfilemetadata-kf5 kcoreaddons
  • Depends: kfilemetadata-kf5 ki18n
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kfilemetadata-kf5.html
  • Required age reduced by 3 days because of autopkgtest
• kglobalaccel (5.62.0-1 to 5.70.0-1)
  • Migration status for kglobalaccel (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kglobalaccel kwindowsystem
  • Depends: kglobalaccel kconfig
  • Depends: kglobalaccel kcoreaddons
  • Depends: kglobalaccel kcrash
  • Depends: kglobalaccel kdbusaddons
  • Depends: kglobalaccel kwindowsystem
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kglobalaccel.html
  • Required age reduced by 3 days because of autopkgtest
• kguiaddons (5.62.0-2 to 5.70.0-1)
  • Migration status for kguiaddons (5.62.0-2 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kguiaddons/5.70.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kguiaddons extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kguiaddons.html
• kholidays (1:5.62.0-1 to 1:5.70.0-1)
  • Migration status for kholidays (1:5.62.0-1 to 1:5.70.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
  • Build-Depends(-Arch): kholidays extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kholidays.html
  • Required age reduced by 3 days because of autopkgtest
• khtml (5.62.0-1 to 5.70.0-1)
  • Migration status for khtml (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kdelibs4support/5.62.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): khtml kxmlgui
  • Depends: khtml karchive
  • Depends: khtml kcodecs
  • Depends: khtml kglobalaccel
  • Depends: khtml ki18n
  • Depends: khtml kiconthemes
  • Depends: khtml kio
  • Depends: khtml kjs
  • Depends: khtml knotifications
  • Depends: khtml kparts
  • Depends: khtml ktextwidgets
  • Depends: khtml kwallet-kf5
  • Depends: khtml kwidgetsaddons
  • Depends: khtml kwindowsystem
  • Depends: khtml kxmlgui
  • Depends: khtml sonnet
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khtml.html
• ki18n (5.62.0-1 to 5.70.0-1)
  • Migration status for ki18n (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): ki18n extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ki18n.html
  • Required age reduced by 3 days because of autopkgtest
• kiconthemes (5.62.0-1 to 5.70.0-1)
  • Migration status for kiconthemes (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kiconthemes kwidgetsaddons
  • Depends: kiconthemes karchive
  • Depends: kiconthemes kconfigwidgets
  • Depends: kiconthemes kcoreaddons
  • Depends: kiconthemes ki18n
  • Depends: kiconthemes kitemviews
  • Depends: kiconthemes kwidgetsaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kiconthemes.html
  • Required age reduced by 3 days because of autopkgtest
• kidentitymanagement (19.08.3-1 to 20.04.1-1)
  • Migration status for kidentitymanagement (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kidentitymanagement kxmlgui
  • Depends: kidentitymanagement kcodecs
  • Depends: kidentitymanagement kconfig
  • Depends: kidentitymanagement kcoreaddons
  • Depends: kidentitymanagement kio
  • Depends: kidentitymanagement kpimtextedit
  • Depends: kidentitymanagement kxmlgui
  • Implicit dependency: kidentitymanagement akonadi-calendar
  • Implicit dependency: kidentitymanagement akonadi-import-wizard
  • Implicit dependency: kidentitymanagement kalarm
  • Implicit dependency: kidentitymanagement kalarmcal
  • Implicit dependency: kidentitymanagement kcalutils
  • Implicit dependency: kidentitymanagement kdepim-addons
  • Implicit dependency: kidentitymanagement kdepim-runtime
  • Implicit dependency: kidentitymanagement kf5-messagelib
  • Implicit dependency: kidentitymanagement kmail
  • Implicit dependency: kidentitymanagement kmail-account-wizard
  • Implicit dependency: kidentitymanagement kmymoney/amd64
  • Implicit dependency: kidentitymanagement kmymoney/arm64
  • Implicit dependency: kidentitymanagement kmymoney/armel
  • Implicit dependency: kidentitymanagement kmymoney/armhf
  • Implicit dependency: kidentitymanagement kmymoney/i386
  • Implicit dependency: kidentitymanagement kmymoney/mips64el
  • Implicit dependency: kidentitymanagement kmymoney/mipsel
  • Implicit dependency: kidentitymanagement kmymoney/ppc64el
  • Implicit dependency: kidentitymanagement kmymoney/s390x
  • Implicit dependency: kidentitymanagement korganizer
  • Implicit dependency: kidentitymanagement libkf5calendarsupport
  • Implicit dependency: kidentitymanagement libkf5incidenceeditor
  • Implicit dependency: kidentitymanagement libkf5ksieve
  • Implicit dependency: kidentitymanagement libkf5mailcommon
  • Implicit dependency: kidentitymanagement mbox-importer
  • Implicit dependency: kidentitymanagement pim-data-exporter
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kidentitymanagement.html
• kidletime (5.62.0-1 to 5.70.0-1)
  • Migration status for kidletime (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kidletime extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kidletime.html
  • Required age reduced by 3 days because of autopkgtest
• kimageformats (5.62.0-1 to 5.70.0-1)
  • Migration status for kimageformats (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kimageformats extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kimageformats.html
  • Required age reduced by 3 days because of autopkgtest
• kimap (19.08.3-1 to 20.04.1-1)
  • Migration status for kimap (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kimap kmime
  • Depends: kimap kcoreaddons
  • Depends: kimap ki18n
  • Depends: kimap kio
  • Depends: kimap kmime
  • Implicit dependency: kimap kdepim-addons
  • Implicit dependency: kimap kdepim-runtime
  • Implicit dependency: kimap libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kimap.html
• kinit (5.62.0-1 to 5.70.0-1)
  • Migration status for kinit (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kdelibs4support/5.62.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kinit kwindowsystem
  • Depends: kinit kconfig
  • Depends: kinit kcrash
  • Depends: kinit kdbusaddons
  • Depends: kinit ki18n
  • Depends: kinit kio
  • Depends: kinit kservice
  • Depends: kinit kwindowsystem
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kinit.html
• kio (5.62.1-2 to 5.70.1-1)
  • Migration status for kio (5.62.1-2 to 5.70.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
  • Build-Depends(-Arch): kio kxmlgui
  • Depends: kio karchive
  • Depends: kio kauth
  • Depends: kio kbookmarks
  • Depends: kio kcompletion
  • Depends: kio kconfig
  • Depends: kio kconfigwidgets
  • Depends: kio kcoreaddons
  • Depends: kio kcrash
  • Depends: kio kdbusaddons
  • Depends: kio kdoctools
  • Depends: kio ki18n
  • Depends: kio kiconthemes
  • Depends: kio kitemviews
  • Depends: kio kjobwidgets
  • Depends: kio knotifications
  • Depends: kio kservice
  • Depends: kio ktextwidgets
  • Depends: kio kwallet-kf5
  • Depends: kio kwidgetsaddons
  • Depends: kio kwindowsystem
  • Depends: kio kxmlgui
  • Depends: kio solid
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kio.html
• kirigami2 (5.62.0-2 to 5.70.0-1)
  • Migration status for kirigami2 (5.62.0-2 to 5.70.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
  • Build-Depends(-Arch): kirigami2 extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kirigami2.html
• kitemmodels (5.62.0-1 to 5.70.0-1)
  • Migration status for kitemmodels (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kitemmodels/5.70.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kitemmodels extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kitemmodels.html
• kitemviews (5.62.0-1 to 5.70.0-1)
  • Migration status for kitemviews (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kitemviews extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kitemviews.html
  • Required age reduced by 3 days because of autopkgtest
• kitinerary (19.08.3-1 to 20.04.1-1)
  • Migration status for kitinerary (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kitinerary kpkpass
  • Depends: kitinerary karchive
  • Depends: kitinerary kcalcore
  • Depends: kitinerary kcontacts
  • Depends: kitinerary ki18n
  • Depends: kitinerary kmime
  • Depends: kitinerary kpkpass
  • Implicit dependency: kitinerary kdepim-addons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kitinerary.html
• kjobwidgets (5.62.0-1 to 5.70.0-1)
  • Migration status for kjobwidgets (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kjobwidgets kwidgetsaddons
  • Depends: kjobwidgets kcoreaddons
  • Depends: kjobwidgets kwidgetsaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kjobwidgets.html
  • Required age reduced by 3 days because of autopkgtest
• kjs (5.62.0-1 to 5.70.0-1)
  • Migration status for kjs (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kjs extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kjs.html
  • Required age reduced by 3 days because of autopkgtest
• kjsembed (5.62.0-1 to 5.70.0-1)
  • Migration status for kjsembed (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kjsembed kjs
  • Depends: kjsembed ki18n
  • Depends: kjsembed kjs
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kjsembed.html
  • Required age reduced by 3 days because of autopkgtest
• kldap (19.08.3-1 to 20.04.1-1)
  • Migration status for kldap (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kldap kwidgetsaddons
  • Depends: kldap ki18n
  • Depends: kldap kio
  • Depends: kldap kwidgetsaddons
  • Implicit dependency: kldap kmail-account-wizard
  • Implicit dependency: kldap libkf5incidenceeditor
  • Implicit dependency: kldap libkf5libkdepim
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kldap.html
• kleopatra (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kleopatra (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): kleopatra kxmlgui
  • Depends: kleopatra kcmutils
  • Depends: kleopatra kcodecs
  • Depends: kleopatra kconfig
  • Depends: kleopatra kconfigwidgets
  • Depends: kleopatra kcoreaddons
  • Depends: kleopatra kcrash
  • Depends: kleopatra kdbusaddons
  • Depends: kleopatra ki18n
  • Depends: kleopatra kiconthemes
  • Depends: kleopatra kitemmodels
  • Depends: kleopatra kmime
  • Depends: kleopatra knotifications
  • Depends: kleopatra ktextwidgets
  • Depends: kleopatra kwidgetsaddons
  • Depends: kleopatra kwindowsystem
  • Depends: kleopatra kxmlgui
  • Depends: kleopatra libkf5libkleo
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kleopatra.html
• kmail (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kmail (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5followupreminder-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5gravatar-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kdepimdbusinterfaces-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5ksieve-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5mailcommon-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messagecomposer-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messagecore-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messagelist-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messageviewer-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5sendlater-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5templateparser-dev (>= 4:20.04.1~)
  • kmail unsatisfiable Build-Depends(-Arch) on mipsel: libkf5webengineviewer-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kmail kxmlgui
  • Depends: kmail akonadi
  • Depends: kmail akonadi-contacts
  • Depends: kmail akonadi-mime
  • Depends: kmail akonadi-search
  • Depends: kmail kbookmarks
  • Depends: kmail kcalcore
  • Depends: kmail kcalutils
  • Depends: kmail kcmutils
  • Depends: kmail kcodecs
  • Depends: kmail kconfig
  • Depends: kmail kconfigwidgets
  • Depends: kmail kcontacts
  • Depends: kmail kcrash
  • Depends: kmail kdbusaddons
  • Depends: kmail kf5-kdepim-apps-libs
  • Depends: kmail kf5-messagelib
  • Depends: kmail kguiaddons
  • Depends: kmail ki18n
  • Depends: kmail kiconthemes
  • Depends: kmail kidentitymanagement
  • Depends: kmail kio
  • Depends: kmail kitemviews
  • Depends: kmail kjobwidgets
  • Depends: kmail kmailtransport
  • Depends: kmail kmime
  • Depends: kmail knotifications
  • Depends: kmail knotifyconfig
  • Depends: kmail kontactinterface
  • Depends: kmail kparts
  • Depends: kmail kpimtextedit
  • Depends: kmail kservice
  • Depends: kmail ktextwidgets
  • Depends: kmail ktnef
  • Depends: kmail kwidgetsaddons
  • Depends: kmail kwindowsystem
  • Depends: kmail kxmlgui
  • Depends: kmail libkf5gravatar
  • Depends: kmail libkf5ksieve
  • Depends: kmail libkf5libkdepim
  • Depends: kmail libkf5libkleo
  • Depends: kmail libkf5mailcommon
  • Depends: kmail libkf5pimcommon
  • Depends: kmail sonnet
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmail.html
• kmail-account-wizard (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kmail-account-wizard (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kmail-account-wizard kwallet-kf5
  • Depends: kmail-account-wizard akonadi
  • Depends: kmail-account-wizard akonadi-mime
  • Depends: kmail-account-wizard kcmutils
  • Depends: kmail-account-wizard kcodecs
  • Depends: kmail-account-wizard kconfig
  • Depends: kmail-account-wizard kcrash
  • Depends: kmail-account-wizard kdbusaddons
  • Depends: kmail-account-wizard kidentitymanagement
  • Depends: kmail-account-wizard kio
  • Depends: kmail-account-wizard kldap
  • Depends: kmail-account-wizard kmailtransport
  • Depends: kmail-account-wizard kmime
  • Depends: kmail-account-wizard knewstuff
  • Depends: kmail-account-wizard knotifications
  • Depends: kmail-account-wizard kross
  • Depends: kmail-account-wizard kwallet-kf5
  • Depends: kmail-account-wizard libkf5libkdepim
  • Depends: kmail-account-wizard libkf5libkleo
  • Depends: kmail-account-wizard libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmail-account-wizard.html
• kmailtransport (19.08.3-1 to 20.04.1-1)
  • Migration status for kmailtransport (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kmailtransport ksmtp
  • Depends: kmailtransport akonadi
  • Depends: kmailtransport akonadi-mime
  • Depends: kmailtransport kconfigwidgets
  • Depends: kmailtransport ki18n
  • Depends: kmailtransport kio
  • Depends: kmailtransport kmime
  • Depends: kmailtransport ksmtp
  • Depends: kmailtransport kwallet-kf5
  • Depends: kmailtransport libkgapi
  • Implicit dependency: kmailtransport akonadi-calendar
  • Implicit dependency: kmailtransport akonadi-import-wizard
  • Implicit dependency: kmailtransport kalarm
  • Implicit dependency: kmailtransport kdepim-addons
  • Implicit dependency: kmailtransport kdepim-runtime
  • Implicit dependency: kmailtransport kf5-messagelib
  • Implicit dependency: kmailtransport kmail
  • Implicit dependency: kmailtransport kmail-account-wizard
  • Implicit dependency: kmailtransport korganizer
  • Implicit dependency: kmailtransport libkf5incidenceeditor
  • Implicit dependency: kmailtransport libkf5mailcommon
  • Implicit dependency: kmailtransport pim-data-exporter
  • Implicit dependency: kmailtransport pim-sieve-editor
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmailtransport.html
• kmbox (19.08.3-1 to 20.04.1-1)
  • Migration status for kmbox (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kmbox kmime
  • Depends: kmbox kmime
  • Implicit dependency: kmbox kdepim-runtime
  • Implicit dependency: kmbox kf5-messagelib
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmbox.html
• kmediaplayer (5.62.0-1 to 5.70.0-1)
  • Migration status for kmediaplayer (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kdelibs4support/5.62.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kmediaplayer kxmlgui
  • Depends: kmediaplayer kparts
  • Depends: kmediaplayer kxmlgui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmediaplayer.html
• kmime (19.08.3-1 to 20.04.1-1)
  • Migration status for kmime (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kmime ki18n
  • Depends: kmime kcodecs
  • Depends: kmime ki18n
  • Implicit dependency: kmime akonadi-calendar
  • Implicit dependency: kmime akonadi-contacts
  • Implicit dependency: kmime akonadi-mime
  • Implicit dependency: kmime akonadi-notes
  • Implicit dependency: kmime akonadi-search
  • Implicit dependency: kmime akonadiconsole
  • Implicit dependency: kmime grantlee-editor
  • Implicit dependency: kmime kalarm
  • Implicit dependency: kmime kdepim-addons
  • Implicit dependency: kmime kdepim-runtime
  • Implicit dependency: kmime kf5-messagelib
  • Implicit dependency: kmime kimap
  • Implicit dependency: kmime kitinerary
  • Implicit dependency: kmime kjots/amd64
  • Implicit dependency: kmime kjots/arm64
  • Implicit dependency: kmime kjots/armel
  • Implicit dependency: kmime kjots/armhf
  • Implicit dependency: kmime kjots/i386
  • Implicit dependency: kmime kjots/mips64el
  • Implicit dependency: kmime kjots/mipsel
  • Implicit dependency: kmime kjots/ppc64el
  • Implicit dependency: kmime kjots/s390x
  • Implicit dependency: kmime kleopatra
  • Implicit dependency: kmime kmail
  • Implicit dependency: kmime kmail-account-wizard
  • Implicit dependency: kmime kmailtransport
  • Implicit dependency: kmime kmbox
  • Implicit dependency: kmime knotes
  • Implicit dependency: kmime korganizer
  • Implicit dependency: kmime libkf5calendarsupport
  • Implicit dependency: kmime libkf5incidenceeditor
  • Implicit dependency: kmime libkf5ksieve
  • Implicit dependency: kmime libkf5mailcommon
  • Implicit dependency: kmime libkf5mailimporter
  • Implicit dependency: kmime pim-data-exporter
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmime.html
• knewstuff (5.62.0-1 to 5.70.0-1)
  • Migration status for knewstuff (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): knewstuff kxmlgui
  • Depends: knewstuff attica-kf5
  • Depends: knewstuff karchive
  • Depends: knewstuff kcompletion
  • Depends: knewstuff kconfig
  • Depends: knewstuff kcoreaddons
  • Depends: knewstuff ki18n
  • Depends: knewstuff kiconthemes
  • Depends: knewstuff kio
  • Depends: knewstuff kitemviews
  • Depends: knewstuff kjobwidgets
  • Depends: knewstuff kservice
  • Depends: knewstuff ktextwidgets
  • Depends: knewstuff kwidgetsaddons
  • Depends: knewstuff kxmlgui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/knewstuff.html
  • Required age reduced by 3 days because of autopkgtest
• knotes (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for knotes (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): knotes kxmlgui
  • Depends: knotes akonadi
  • Depends: knotes akonadi-notes
  • Depends: knotes akonadi-search
  • Depends: knotes kcalcore
  • Depends: knotes kcalutils
  • Depends: knotes kcmutils
  • Depends: knotes kcompletion
  • Depends: knotes kconfig
  • Depends: knotes kconfigwidgets
  • Depends: knotes kcoreaddons
  • Depends: knotes kcrash
  • Depends: knotes kdnssd-kf5
  • Depends: knotes kglobalaccel
  • Depends: knotes kiconthemes
  • Depends: knotes kio
  • Depends: knotes kitemmodels
  • Depends: knotes kitemviews
  • Depends: knotes kmime
  • Depends: knotes knewstuff
  • Depends: knotes knotifications
  • Depends: knotes knotifyconfig
  • Depends: knotes kontactinterface
  • Depends: knotes kparts
  • Depends: knotes kpimtextedit
  • Depends: knotes ktextwidgets
  • Depends: knotes kwidgetsaddons
  • Depends: knotes kwindowsystem
  • Depends: knotes kxmlgui
  • Depends: knotes libkf5grantleetheme
  • Depends: knotes libkf5libkdepim
  • Depends: knotes libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/knotes.html
• knotifications (5.62.0-1 to 5.70.0-1)
  • Migration status for knotifications (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): knotifications kwindowsystem
  • Depends: knotifications kconfig
  • Depends: knotifications kcoreaddons
  • Depends: knotifications kwindowsystem
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/knotifications.html
  • Required age reduced by 3 days because of autopkgtest
• knotifyconfig (5.62.0-1 to 5.70.0-1)
  • Migration status for knotifyconfig (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kdelibs4support/5.62.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): knotifyconfig kxmlgui
  • Depends: knotifyconfig kconfig
  • Depends: knotifyconfig ki18n
  • Depends: knotifyconfig kio
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/knotifyconfig.html
• kodi (- to 2:18.7+dfsg1-1)
  • Migration status for kodi (- to 2:18.7+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kodi introduces new bugs: #936805
  • Too young, only 1 of 2 days old
  • Depends: kodi pillow-python2
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi.html
  • Required age reduced by 3 days because of autopkgtest
• kontact (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for kontact (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • kontact unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kdepimdbusinterfaces-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kontact kwindowsystem
  • Depends: kontact kcmutils
  • Depends: kontact kcrash
  • Depends: kontact kf5-kdepim-apps-libs
  • Depends: kontact kiconthemes
  • Depends: kontact kio
  • Depends: kontact kontactinterface
  • Depends: kontact kwindowsystem
  • Depends: kontact libkf5grantleetheme
  • Depends: kontact libkf5libkdepim
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kontact.html
• kontactinterface (19.08.3-1 to 20.04.1-1)
  • Migration status for kontactinterface (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kontactinterface kxmlgui
  • Depends: kontactinterface kcoreaddons
  • Depends: kontactinterface ki18n
  • Depends: kontactinterface kio
  • Depends: kontactinterface kparts
  • Depends: kontactinterface kwindowsystem
  • Depends: kontactinterface kxmlgui
  • Implicit dependency: kontactinterface akregator
  • Implicit dependency: kontactinterface kaddressbook
  • Implicit dependency: kontactinterface kdepim-addons
  • Implicit dependency: kontactinterface kjots/amd64
  • Implicit dependency: kontactinterface kjots/arm64
  • Implicit dependency: kontactinterface kjots/armel
  • Implicit dependency: kontactinterface kjots/armhf
  • Implicit dependency: kontactinterface kjots/i386
  • Implicit dependency: kontactinterface kjots/mips64el
  • Implicit dependency: kontactinterface kjots/mipsel
  • Implicit dependency: kontactinterface kjots/ppc64el
  • Implicit dependency: kontactinterface kjots/s390x
  • Implicit dependency: kontactinterface kmail
  • Implicit dependency: kontactinterface knotes
  • Implicit dependency: kontactinterface kontact
  • Implicit dependency: kontactinterface korganizer
  • Implicit dependency: kontactinterface zanshin/amd64
  • Implicit dependency: kontactinterface zanshin/arm64
  • Implicit dependency: kontactinterface zanshin/armel
  • Implicit dependency: kontactinterface zanshin/armhf
  • Implicit dependency: kontactinterface zanshin/i386
  • Implicit dependency: kontactinterface zanshin/mips64el
  • Implicit dependency: kontactinterface zanshin/mipsel
  • Implicit dependency: kontactinterface zanshin/ppc64el
  • Implicit dependency: kontactinterface zanshin/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kontactinterface.html
• korganizer (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for korganizer (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • korganizer unsatisfiable Build-Depends(-Arch) on mips64el: libkf5eventviews-dev (>= 4:20.04.1~)
  • korganizer unsatisfiable Build-Depends(-Arch) on mips64el: libkf5incidenceeditor-dev (>= 20.04.1~)
  • korganizer unsatisfiable Build-Depends(-Arch) on mipsel: libkf5calendarsupport-dev (>= 4:20.04.1~)
  • korganizer unsatisfiable Build-Depends(-Arch) on mipsel: libkf5eventviews-dev (>= 4:20.04.1~)
  • korganizer unsatisfiable Build-Depends(-Arch) on mipsel: libkf5incidenceeditor-dev (>= 20.04.1~)
  • korganizer unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kdepimdbusinterfaces-dev (>= 4:20.04.1~)
  • missing build on mips64el
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): korganizer kxmlgui
  • Depends: korganizer akonadi
  • Depends: korganizer akonadi-calendar
  • Depends: korganizer akonadi-contacts
  • Depends: korganizer akonadi-mime
  • Depends: korganizer akonadi-notes
  • Depends: korganizer kcalcore
  • Depends: korganizer kcalutils
  • Depends: korganizer kcmutils
  • Depends: korganizer kcodecs
  • Depends: korganizer kcompletion
  • Depends: korganizer kconfig
  • Depends: korganizer kconfigwidgets
  • Depends: korganizer kcontacts
  • Depends: korganizer kcoreaddons
  • Depends: korganizer kcrash
  • Depends: korganizer kdbusaddons
  • Depends: korganizer kf5-kdepim-apps-libs
  • Depends: korganizer kholidays
  • Depends: korganizer kiconthemes
  • Depends: korganizer kidentitymanagement
  • Depends: korganizer kio
  • Depends: korganizer kitemviews
  • Depends: korganizer kjobwidgets
  • Depends: korganizer kmailtransport
  • Depends: korganizer kmime
  • Depends: korganizer knewstuff
  • Depends: korganizer knotifications
  • Depends: korganizer kontactinterface
  • Depends: korganizer kparts
  • Depends: korganizer kpimtextedit
  • Depends: korganizer kservice
  • Depends: korganizer kwidgetsaddons
  • Depends: korganizer kwindowsystem
  • Depends: korganizer kxmlgui
  • Depends: korganizer libkf5calendarsupport
  • Depends: korganizer libkf5eventviews
  • Depends: korganizer libkf5incidenceeditor
  • Depends: korganizer libkf5libkdepim
  • Depends: korganizer libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/korganizer.html
• kpackage (5.62.0-1 to 5.70.0-1)
  • Migration status for kpackage (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kpackage ki18n
  • Depends: kpackage extra-cmake-modules
  • Depends: kpackage karchive
  • Depends: kpackage kcoreaddons
  • Depends: kpackage ki18n
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kpackage.html
  • Required age reduced by 3 days because of autopkgtest
• kparts (5.62.0-1 to 5.70.0-1)
  • Migration status for kparts (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kparts kxmlgui
  • Depends: kparts kconfig
  • Depends: kparts kcoreaddons
  • Depends: kparts ki18n
  • Depends: kparts kiconthemes
  • Depends: kparts kio
  • Depends: kparts kjobwidgets
  • Depends: kparts kservice
  • Depends: kparts ktextwidgets
  • Depends: kparts kwidgetsaddons
  • Depends: kparts kxmlgui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kparts.html
• kpeople (5.62.0-1 to 5.70.0-1)
  • Migration status for kpeople (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kpeople kwidgetsaddons
  • Depends: kpeople kcoreaddons
  • Depends: kpeople ki18n
  • Depends: kpeople kitemviews
  • Depends: kpeople kwidgetsaddons
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kpeople.html
  • Required age reduced by 3 days because of autopkgtest
• kpimtextedit (19.08.3-1 to 20.04.1-1)
  • Migration status for kpimtextedit (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kpimtextedit kxmlgui
  • Depends: kpimtextedit kcodecs
  • Depends: kpimtextedit kconfig
  • Depends: kpimtextedit kconfigwidgets
  • Depends: kpimtextedit kcoreaddons
  • Depends: kpimtextedit ki18n
  • Depends: kpimtextedit kio
  • Depends: kpimtextedit ksyntax-highlighting
  • Depends: kpimtextedit ktextwidgets
  • Depends: kpimtextedit kwidgetsaddons
  • Depends: kpimtextedit kxmlgui
  • Depends: kpimtextedit sonnet
  • Implicit dependency: kpimtextedit akregator
  • Implicit dependency: kpimtextedit grantlee-editor
  • Implicit dependency: kpimtextedit kalarm
  • Implicit dependency: kpimtextedit kdepim-addons
  • Implicit dependency: kpimtextedit kf5-messagelib
  • Implicit dependency: kpimtextedit kidentitymanagement
  • Implicit dependency: kpimtextedit kjots/amd64
  • Implicit dependency: kpimtextedit kjots/arm64
  • Implicit dependency: kpimtextedit kjots/armel
  • Implicit dependency: kpimtextedit kjots/armhf
  • Implicit dependency: kpimtextedit kjots/i386
  • Implicit dependency: kpimtextedit kjots/mips64el
  • Implicit dependency: kpimtextedit kjots/mipsel
  • Implicit dependency: kpimtextedit kjots/ppc64el
  • Implicit dependency: kpimtextedit kjots/s390x
  • Implicit dependency: kpimtextedit kmail
  • Implicit dependency: kpimtextedit knotes
  • Implicit dependency: kpimtextedit korganizer
  • Implicit dependency: kpimtextedit libkf5incidenceeditor
  • Implicit dependency: kpimtextedit libkf5ksieve
  • Implicit dependency: kpimtextedit libkf5libkleo
  • Implicit dependency: kpimtextedit libkf5mailcommon
  • Implicit dependency: kpimtextedit libkf5pimcommon
  • Implicit dependency: kpimtextedit pim-data-exporter
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kpimtextedit.html
• kpkpass (19.08.3-1 to 20.04.1-1)
  • Migration status for kpkpass (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): kpkpass karchive
  • Depends: kpkpass karchive
  • Implicit dependency: kpkpass kdepim-addons
  • Implicit dependency: kpkpass kitinerary
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kpkpass.html
• kplotting (5.62.0-1 to 5.70.0-1)
  • Migration status for kplotting (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kplotting extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kplotting.html
  • Required age reduced by 3 days because of autopkgtest
• kpty (5.62.0-1 to 5.70.0-1)
  • Migration status for kpty (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kpty ki18n
  • Depends: kpty kcoreaddons
  • Depends: kpty ki18n
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kpty.html
  • Required age reduced by 3 days because of autopkgtest
• kross (5.62.0-1 to 5.70.0-1)
  • Migration status for kross (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kdelibs4support/5.62.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kross kxmlgui
  • Depends: kross kcompletion
  • Depends: kross kcoreaddons
  • Depends: kross ki18n
  • Depends: kross kiconthemes
  • Depends: kross kio
  • Depends: kross kparts
  • Depends: kross kwidgetsaddons
  • Depends: kross kxmlgui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kross.html
• krunner (5.62.0-1 to 5.70.0-1)
  • Migration status for krunner (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): krunner threadweaver
  • Depends: krunner extra-cmake-modules
  • Depends: krunner kconfig
  • Depends: krunner kcoreaddons
  • Depends: krunner ki18n
  • Depends: krunner kio
  • Depends: krunner kservice
  • Depends: krunner plasma-framework
  • Depends: krunner threadweaver
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/krunner.html
  • Required age reduced by 3 days because of autopkgtest
• kservice (5.62.0-1 to 5.70.0-1)
  • Migration status for kservice (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kservice ki18n
  • Depends: kservice kconfig
  • Depends: kservice kcoreaddons
  • Depends: kservice kcrash
  • Depends: kservice kdbusaddons
  • Depends: kservice ki18n
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kservice.html
  • Required age reduced by 3 days because of autopkgtest
• ksmtp (19.08.3-1 to 20.04.1-1)
  • Migration status for ksmtp (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): ksmtp kio
  • Depends: ksmtp kcoreaddons
  • Depends: ksmtp ki18n
  • Depends: ksmtp kio
  • Implicit dependency: ksmtp kmailtransport
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ksmtp.html
• ksyntax-highlighting (5.62.0-3 to 5.70.0-1)
  • Migration status for ksyntax-highlighting (5.62.0-3 to 5.70.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
  • Build-Depends(-Arch): ksyntax-highlighting extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ksyntax-highlighting.html
  • Required age reduced by 3 days because of autopkgtest
• ktexteditor (5.62.0-1 to 5.70.1-1)
  • Migration status for ktexteditor (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): ktexteditor ksyntax-highlighting
  • Depends: ktexteditor karchive
  • Depends: ktexteditor kauth
  • Depends: ktexteditor kconfig
  • Depends: ktexteditor kguiaddons
  • Depends: ktexteditor ki18n
  • Depends: ktexteditor kio
  • Depends: ktexteditor kparts
  • Depends: ktexteditor ksyntax-highlighting
  • Depends: ktexteditor sonnet
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktexteditor.html
  • Required age reduced by 3 days because of autopkgtest
• ktextwidgets (5.62.0-1 to 5.70.0-1)
  • Migration status for ktextwidgets (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): ktextwidgets kwidgetsaddons
  • Depends: ktextwidgets kcompletion
  • Depends: ktextwidgets kconfig
  • Depends: ktextwidgets kconfigwidgets
  • Depends: ktextwidgets ki18n
  • Depends: ktextwidgets kwidgetsaddons
  • Depends: ktextwidgets sonnet
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktextwidgets.html
  • Required age reduced by 3 days because of autopkgtest
• ktnef (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for ktnef (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): ktnef ki18n
  • Depends: ktnef kcalcore
  • Depends: ktnef kcalutils
  • Depends: ktnef kcontacts
  • Depends: ktnef ki18n
  • Implicit dependency: ktnef kdepim-addons
  • Implicit dependency: ktnef kmail
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktnef.html
• kunitconversion (5.62.0-1 to 5.70.0-1)
  • Migration status for kunitconversion (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kunitconversion ki18n
  • Depends: kunitconversion ki18n
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kunitconversion.html
  • Required age reduced by 3 days because of autopkgtest
• kwallet-kf5 (5.62.0-1 to 5.70.0-1)
  • Migration status for kwallet-kf5 (5.62.0-1 to 5.70.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for kdelibs4support/5.62.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): kwallet-kf5 kwindowsystem
  • Depends: kwallet-kf5 kconfig
  • Depends: kwallet-kf5 kconfigwidgets
  • Depends: kwallet-kf5 kcoreaddons
  • Depends: kwallet-kf5 kdbusaddons
  • Depends: kwallet-kf5 ki18n
  • Depends: kwallet-kf5 knotifications
  • Depends: kwallet-kf5 kservice
  • Depends: kwallet-kf5 kwidgetsaddons
  • Depends: kwallet-kf5 kwindowsystem
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwallet-kf5.html
• kwayland (4:5.62.0-2 to 4:5.70.0-1)
  • Migration status for kwayland (4:5.62.0-2 to 4:5.70.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
  • Build-Depends(-Arch): kwayland extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwayland.html
  • Required age reduced by 3 days because of autopkgtest
• kwidgetsaddons (5.62.0-1 to 5.70.0-1)
  • Migration status for kwidgetsaddons (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kwidgetsaddons extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwidgetsaddons.html
  • Required age reduced by 3 days because of autopkgtest
• kwindowsystem (5.62.0-3 to 5.70.0-1)
  • Migration status for kwindowsystem (5.62.0-3 to 5.70.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
  • Build-Depends(-Arch): kwindowsystem extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwindowsystem.html
• kxmlgui (5.62.0-1 to 5.70.0-1)
  • Migration status for kxmlgui (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kxmlgui kwindowsystem
  • Depends: kxmlgui attica-kf5
  • Depends: kxmlgui kconfig
  • Depends: kxmlgui kconfigwidgets
  • Depends: kxmlgui kcoreaddons
  • Depends: kxmlgui kglobalaccel
  • Depends: kxmlgui ki18n
  • Depends: kxmlgui kiconthemes
  • Depends: kxmlgui kitemviews
  • Depends: kxmlgui kwidgetsaddons
  • Depends: kxmlgui kwindowsystem
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kxmlgui.html
  • Required age reduced by 3 days because of autopkgtest
• kxmlrpcclient (5.62.0-1 to 5.70.0-1)
  • Migration status for kxmlrpcclient (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): kxmlrpcclient kio
  • Depends: kxmlrpcclient ki18n
  • Depends: kxmlrpcclient kio
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kxmlrpcclient.html
  • Required age reduced by 3 days because of autopkgtest
• ledger (3.2.0-1 to 3.2.1-1)
  • Migration status for ledger (3.2.0-1 to 3.2.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/l/ledger.html
• libfido2 (1.4.0-1 to 1.4.0-2)
  • Migration status for libfido2 (1.4.0-1 to 1.4.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/libf/libfido2.html
• libkf5calendarsupport (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5calendarsupport (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libkf5calendarsupport unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kdepimdbusinterfaces-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): libkf5calendarsupport libkf5pimcommon
  • Depends: libkf5calendarsupport akonadi
  • Depends: libkf5calendarsupport akonadi-calendar
  • Depends: libkf5calendarsupport kcalcore
  • Depends: libkf5calendarsupport kcalutils
  • Depends: libkf5calendarsupport kcodecs
  • Depends: libkf5calendarsupport kf5-kdepim-apps-libs
  • Depends: libkf5calendarsupport kguiaddons
  • Depends: libkf5calendarsupport kholidays
  • Depends: libkf5calendarsupport ki18n
  • Depends: libkf5calendarsupport kidentitymanagement
  • Depends: libkf5calendarsupport kio
  • Depends: libkf5calendarsupport kmime
  • Depends: libkf5calendarsupport libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5calendarsupport.html
• libkf5eventviews (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5eventviews (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libkf5eventviews unsatisfiable Build-Depends(-Arch) on mipsel: libkf5calendarsupport-dev (>= 4:20.04.1~)
  • missing build on mips64el
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): libkf5eventviews kservice
  • Depends: libkf5eventviews akonadi
  • Depends: libkf5eventviews akonadi-calendar
  • Depends: libkf5eventviews kcalcore
  • Depends: libkf5eventviews kcalutils
  • Depends: libkf5eventviews kcodecs
  • Depends: libkf5eventviews kcompletion
  • Depends: libkf5eventviews kguiaddons
  • Depends: libkf5eventviews kholidays
  • Depends: libkf5eventviews ki18n
  • Depends: libkf5eventviews kiconthemes
  • Depends: libkf5eventviews kservice
  • Depends: libkf5eventviews libkf5calendarsupport
  • Depends: libkf5eventviews libkf5libkdepim
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5eventviews.html
• libkf5grantleetheme (19.08.3-1 to 20.04.1-1)
  • Migration status for libkf5grantleetheme (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): libkf5grantleetheme knewstuff
  • Depends: libkf5grantleetheme kguiaddons
  • Depends: libkf5grantleetheme ki18n
  • Depends: libkf5grantleetheme kiconthemes
  • Depends: libkf5grantleetheme knewstuff
  • Implicit dependency: libkf5grantleetheme akregator
  • Implicit dependency: libkf5grantleetheme grantlee-editor
  • Implicit dependency: libkf5grantleetheme kaddressbook
  • Implicit dependency: libkf5grantleetheme kdepim-addons
  • Implicit dependency: libkf5grantleetheme kf5-kdepim-apps-libs
  • Implicit dependency: libkf5grantleetheme kf5-messagelib
  • Implicit dependency: libkf5grantleetheme knotes
  • Implicit dependency: libkf5grantleetheme kontact
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5grantleetheme.html
• libkf5gravatar (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5gravatar (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): libkf5gravatar kwidgetsaddons
  • Depends: libkf5gravatar kconfig
  • Depends: libkf5gravatar ki18n
  • Depends: libkf5gravatar ktextwidgets
  • Depends: libkf5gravatar kwidgetsaddons
  • Depends: libkf5gravatar libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5gravatar.html
• libkf5incidenceeditor (19.08.3-1 to 20.04.1-1)
  • Migration status for libkf5incidenceeditor (19.08.3-1 to 20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libkf5incidenceeditor unsatisfiable Build-Depends(-Arch) on mips64el: libkf5eventviews-dev (>= 4:20.04.1~)
  • libkf5incidenceeditor unsatisfiable Build-Depends(-Arch) on mipsel: libkf5calendarsupport-dev (>= 4:20.04.1~)
  • libkf5incidenceeditor unsatisfiable Build-Depends(-Arch) on mipsel: libkf5eventviews-dev (>= 4:20.04.1~)
  • libkf5incidenceeditor unsatisfiable Build-Depends(-Arch) on mipsel: libkf5kdepimdbusinterfaces-dev (>= 4:20.04.1~)
  • missing build on mips64el
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): libkf5incidenceeditor kmime
  • Depends: libkf5incidenceeditor akonadi
  • Depends: libkf5incidenceeditor akonadi-calendar
  • Depends: libkf5incidenceeditor akonadi-contacts
  • Depends: libkf5incidenceeditor akonadi-mime
  • Depends: libkf5incidenceeditor kcalcore
  • Depends: libkf5incidenceeditor kcalutils
  • Depends: libkf5incidenceeditor kcodecs
  • Depends: libkf5incidenceeditor kf5-kdepim-apps-libs
  • Depends: libkf5incidenceeditor ki18n
  • Depends: libkf5incidenceeditor kiconthemes
  • Depends: libkf5incidenceeditor kidentitymanagement
  • Depends: libkf5incidenceeditor kio
  • Depends: libkf5incidenceeditor kldap
  • Depends: libkf5incidenceeditor kmailtransport
  • Depends: libkf5incidenceeditor kmime
  • Depends: libkf5incidenceeditor kpimtextedit
  • Depends: libkf5incidenceeditor libkf5calendarsupport
  • Depends: libkf5incidenceeditor libkf5eventviews
  • Depends: libkf5incidenceeditor libkf5libkdepim
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5incidenceeditor.html
• libkf5ksieve (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5ksieve (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): libkf5ksieve ksyntax-highlighting
  • Depends: libkf5ksieve karchive
  • Depends: libkf5ksieve ki18n
  • Depends: libkf5ksieve kiconthemes
  • Depends: libkf5ksieve kidentitymanagement
  • Depends: libkf5ksieve kio
  • Depends: libkf5ksieve kmime
  • Depends: libkf5ksieve knewstuff
  • Depends: libkf5ksieve kpimtextedit
  • Depends: libkf5ksieve ksyntax-highlighting
  • Depends: libkf5ksieve libkf5libkdepim
  • Depends: libkf5ksieve libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5ksieve.html
• libkf5libkdepim (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5libkdepim (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): libkf5libkdepim kwidgetsaddons
  • Depends: libkf5libkdepim akonadi
  • Depends: libkf5libkdepim akonadi-contacts
  • Depends: libkf5libkdepim akonadi-search
  • Depends: libkf5libkdepim kcmutils
  • Depends: libkf5libkdepim kcodecs
  • Depends: libkf5libkdepim kcompletion
  • Depends: libkf5libkdepim kconfig
  • Depends: libkf5libkdepim kconfigwidgets
  • Depends: libkf5libkdepim kcontacts
  • Depends: libkf5libkdepim kcoreaddons
  • Depends: libkf5libkdepim ki18n
  • Depends: libkf5libkdepim kio
  • Depends: libkf5libkdepim kitemviews
  • Depends: libkf5libkdepim kjobwidgets
  • Depends: libkf5libkdepim kldap
  • Depends: libkf5libkdepim kwallet-kf5
  • Depends: libkf5libkdepim kwidgetsaddons
  • Implicit dependency: libkf5libkdepim akonadi-import-wizard
  • Implicit dependency: libkf5libkdepim akonadiconsole
  • Implicit dependency: libkf5libkdepim akregator
  • Implicit dependency: libkf5libkdepim kaddressbook
  • Implicit dependency: libkf5libkdepim kalarm
  • Implicit dependency: libkf5libkdepim kdepim-addons
  • Implicit dependency: libkf5libkdepim kf5-messagelib
  • Implicit dependency: libkf5libkdepim kmail
  • Implicit dependency: libkf5libkdepim kmail-account-wizard
  • Implicit dependency: libkf5libkdepim knotes
  • Implicit dependency: libkf5libkdepim kontact
  • Implicit dependency: libkf5libkdepim korganizer
  • Implicit dependency: libkf5libkdepim libkf5eventviews
  • Implicit dependency: libkf5libkdepim libkf5incidenceeditor
  • Implicit dependency: libkf5libkdepim libkf5ksieve
  • Implicit dependency: libkf5libkdepim libkf5mailcommon
  • Implicit dependency: libkf5libkdepim libkf5mailimporter
  • Implicit dependency: libkf5libkdepim libkf5pimcommon
  • Implicit dependency: libkf5libkdepim pim-data-exporter
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5libkdepim.html
• libkf5libkleo (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5libkleo (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): libkf5libkleo kwidgetsaddons
  • Depends: libkf5libkleo kcodecs
  • Depends: libkf5libkleo kcompletion
  • Depends: libkf5libkleo kconfig
  • Depends: libkf5libkleo kcoreaddons
  • Depends: libkf5libkleo ki18n
  • Depends: libkf5libkleo kitemmodels
  • Depends: libkf5libkleo kpimtextedit
  • Depends: libkf5libkleo kwidgetsaddons
  • Implicit dependency: libkf5libkleo kdepim-addons
  • Implicit dependency: libkf5libkleo kf5-kdepim-apps-libs
  • Implicit dependency: libkf5libkleo kf5-messagelib
  • Implicit dependency: libkf5libkleo kleopatra
  • Implicit dependency: libkf5libkleo kmail
  • Implicit dependency: libkf5libkleo kmail-account-wizard
  • Implicit dependency: libkf5libkleo libkf5mailcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5libkleo.html
• libkf5mailcommon (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5mailcommon (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libkf5mailcommon unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messagecomposer-dev (>= 4:20.04.1~)
  • libkf5mailcommon unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messagecore-dev (>= 4:20.04.1~)
  • libkf5mailcommon unsatisfiable Build-Depends(-Arch) on mipsel: libkf5messageviewer-dev (>= 4:20.04.1~)
  • libkf5mailcommon unsatisfiable Build-Depends(-Arch) on mipsel: libkf5templateparser-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): libkf5mailcommon kxmlgui
  • Depends: libkf5mailcommon akonadi
  • Depends: libkf5mailcommon akonadi-contacts
  • Depends: libkf5mailcommon akonadi-mime
  • Depends: libkf5mailcommon karchive
  • Depends: libkf5mailcommon kcodecs
  • Depends: libkf5mailcommon kcompletion
  • Depends: libkf5mailcommon kconfig
  • Depends: libkf5mailcommon kconfigwidgets
  • Depends: libkf5mailcommon kf5-messagelib
  • Depends: libkf5mailcommon ki18n
  • Depends: libkf5mailcommon kiconthemes
  • Depends: libkf5mailcommon kidentitymanagement
  • Depends: libkf5mailcommon kio
  • Depends: libkf5mailcommon kitemviews
  • Depends: libkf5mailcommon kmailtransport
  • Depends: libkf5mailcommon kmime
  • Depends: libkf5mailcommon kpimtextedit
  • Depends: libkf5mailcommon ksyntax-highlighting
  • Depends: libkf5mailcommon ktextwidgets
  • Depends: libkf5mailcommon kwidgetsaddons
  • Depends: libkf5mailcommon kxmlgui
  • Depends: libkf5mailcommon libkf5libkdepim
  • Depends: libkf5mailcommon libkf5libkleo
  • Depends: libkf5mailcommon libkf5mailimporter
  • Depends: libkf5mailcommon libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5mailcommon.html
• libkf5mailimporter (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5mailimporter (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): libkf5mailimporter kmime
  • Depends: libkf5mailimporter akonadi
  • Depends: libkf5mailimporter akonadi-mime
  • Depends: libkf5mailimporter karchive
  • Depends: libkf5mailimporter kconfig
  • Depends: libkf5mailimporter kcoreaddons
  • Depends: libkf5mailimporter ki18n
  • Depends: libkf5mailimporter kmime
  • Depends: libkf5mailimporter libkf5libkdepim
  • Implicit dependency: libkf5mailimporter akonadi-import-wizard
  • Implicit dependency: libkf5mailimporter kdepim-addons
  • Implicit dependency: libkf5mailimporter libkf5mailcommon
  • Implicit dependency: libkf5mailimporter mbox-importer
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5mailimporter.html
• libkf5pimcommon (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for libkf5pimcommon (4:19.08.3-1 to 4:20.04.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
  • Build-Depends(-Arch): libkf5pimcommon kxmlgui
  • Depends: libkf5pimcommon akonadi
  • Depends: libkf5pimcommon akonadi-contacts
  • Depends: libkf5pimcommon karchive
  • Depends: libkf5pimcommon kcodecs
  • Depends: libkf5pimcommon kcompletion
  • Depends: libkf5pimcommon kconfig
  • Depends: libkf5pimcommon kconfigwidgets
  • Depends: libkf5pimcommon kcontacts
  • Depends: libkf5pimcommon kcoreaddons
  • Depends: libkf5pimcommon ki18n
  • Depends: libkf5pimcommon kimap
  • Depends: libkf5pimcommon kio
  • Depends: libkf5pimcommon kitemmodels
  • Depends: libkf5pimcommon kjobwidgets
  • Depends: libkf5pimcommon knewstuff
  • Depends: libkf5pimcommon kpimtextedit
  • Depends: libkf5pimcommon kwidgetsaddons
  • Depends: libkf5pimcommon kxmlgui
  • Depends: libkf5pimcommon libkf5libkdepim
  • Depends: libkf5pimcommon purpose
  • Implicit dependency: libkf5pimcommon akonadi-import-wizard
  • Implicit dependency: libkf5pimcommon akregator
  • Implicit dependency: libkf5pimcommon grantlee-editor
  • Implicit dependency: libkf5pimcommon kaddressbook
  • Implicit dependency: libkf5pimcommon kalarm
  • Implicit dependency: libkf5pimcommon kdepim-addons
  • Implicit dependency: libkf5pimcommon kf5-kdepim-apps-libs
  • Implicit dependency: libkf5pimcommon kf5-messagelib
  • Implicit dependency: libkf5pimcommon kmail
  • Implicit dependency: libkf5pimcommon kmail-account-wizard
  • Implicit dependency: libkf5pimcommon knotes
  • Implicit dependency: libkf5pimcommon korganizer
  • Implicit dependency: libkf5pimcommon libkf5calendarsupport
  • Implicit dependency: libkf5pimcommon libkf5gravatar
  • Implicit dependency: libkf5pimcommon libkf5ksieve
  • Implicit dependency: libkf5pimcommon libkf5mailcommon
  • Implicit dependency: libkf5pimcommon pim-data-exporter
  • Implicit dependency: libkf5pimcommon pim-sieve-editor
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkf5pimcommon.html
• libkgapi (19.08.3-1 to 20.04.1-1)
  • Migration status for libkgapi (19.08.3-1 to 20.04.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
  • Build-Depends(-Arch): libkgapi kwindowsystem
  • Depends: libkgapi kcalcore
  • Depends: libkgapi kcontacts
  • Depends: libkgapi kio
  • Depends: libkgapi kwallet-kf5
  • Depends: libkgapi kwindowsystem
  • Implicit dependency: libkgapi kdepim-runtime
  • Implicit dependency: libkgapi kio-gdrive/amd64
  • Implicit dependency: libkgapi kio-gdrive/arm64
  • Implicit dependency: libkgapi kio-gdrive/armhf
  • Implicit dependency: libkgapi kio-gdrive/i386
  • Implicit dependency: libkgapi kio-gdrive/mipsel
  • Implicit dependency: libkgapi kmailtransport
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkgapi.html
• libqmi (1.24.8-1.2 to 1.24.12-0.1)
  • Migration status for libqmi (1.24.8-1.2 to 1.24.12-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/libq/libqmi.html
• libreswan (3.29-2 to 3.32-2)
  • Migration status for libreswan (3.29-2 to 3.32-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libreswan/3.32-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: upload info for arch amd64 binaries not found
  • Not built on buildd: upload info for arch arm64 binaries not found
  • Not built on buildd: upload info for arch armel binaries not found
  • Not built on buildd: upload info for arch armhf binaries not found
  • Not built on buildd: upload info for arch i386 binaries not found
  • Not built on buildd: upload info for arch mips64el binaries not found
  • Not built on buildd: upload info for arch mipsel binaries not found
  • Not built on buildd: upload info for arch ppc64el binaries not found
  • Not built on buildd: upload info for arch s390x binaries not found
  • Too young, only 1 of 5 days old
  • Additional info:
  • Updating libreswan fixes old bugs: #960458
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libreswan.html
• libsdl2 (2.0.10+dfsg1-3 to 2.0.12+dfsg1-1)
  • Migration status for libsdl2 (2.0.10+dfsg1-3 to 2.0.12+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 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl2.html
• lollypop (1.2.35-1 to 1.3.0-1)
  • Migration status for lollypop (1.2.35-1 to 1.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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lollypop.html
• lua-luv (1.30.1-1-2 to 1.36.0-0-1)
  • Migration status for lua-luv (1.30.1-1-2 to 1.36.0-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
  • Depends: lua-luv libuv1
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-luv.html
  • Required age reduced by 3 days because of autopkgtest
• mbox-importer (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for mbox-importer (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mbox-importer unsatisfiable Build-Depends(-Arch) on mipsel: libkf5mailcommon-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): mbox-importer kservice
  • Depends: mbox-importer akonadi
  • Depends: mbox-importer kconfig
  • Depends: mbox-importer kcrash
  • Depends: mbox-importer kidentitymanagement
  • Depends: mbox-importer libkf5mailcommon
  • Depends: mbox-importer libkf5mailimporter
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mbox-importer.html
• modemmanager (1.12.8-1.1 to 1.12.10-0.1)
  • Migration status for modemmanager (1.12.8-1.1 to 1.12.10-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/m/modemmanager.html
• modemmanager-qt (5.62.0-1 to 5.70.0-1)
  • Migration status for modemmanager-qt (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): modemmanager-qt extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/modemmanager-qt.html
  • Required age reduced by 3 days because of autopkgtest
• mutter (3.36.2-1 to 3.36.2-3)
  • Migration status for mutter (3.36.2-1 to 3.36.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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mutter.html
• ncbi-vdb (2.9.3+dfsg-2 to 2.10.6+dfsg-5)
  • Migration status for ncbi-vdb (2.9.3+dfsg-2 to 2.10.6+dfsg-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 ncbi-vdb fixes old bugs: #958760
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncbi-vdb.html
• netsurf (3.9-1 to 3.10-1)
  • Migration status for netsurf (3.9-1 to 3.10-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/netsurf.html
• networkmanager-qt (5.62.0-1 to 5.70.0-1)
  • Migration status for networkmanager-qt (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): networkmanager-qt extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networkmanager-qt.html
  • Required age reduced by 3 days because of autopkgtest
• node-deep-for-each (1.0.6+dfsg-2 to 3.0.0-2)
  • Migration status for node-deep-for-each (1.0.6+dfsg-2 to 3.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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-deep-for-each.html
• octave-video (1.2.4-4 to 2.0.0-2)
  • Migration status for octave-video (1.2.4-4 to 2.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 2 days old
  • Additional info:
  • Updating octave-video fixes old bugs: #961548
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-video.html
  • Required age reduced by 3 days because of autopkgtest
• onedrive (2.4.0-1 to 2.4.2-1)
  • Migration status for onedrive (2.4.0-1 to 2.4.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 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onedrive.html
• openorienteering-mapper (0.9.2-1 to 0.9.3-1)
  • Migration status for openorienteering-mapper (0.9.2-1 to 0.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/o/openorienteering-mapper.html
• opensmtpd (6.6.4p1-2 to 6.7.1p1-2)
  • Migration status for opensmtpd (6.6.4p1-2 to 6.7.1p1-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/o/opensmtpd.html
• orthanc (1.6.1+dfsg-1 to 1.7.1+dfsg-1)
  • Migration status for orthanc (1.6.1+dfsg-1 to 1.7.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/o/orthanc.html
• oxygen-icons5 (5:5.62.0-1 to 5:5.70.0-1)
  • Migration status for oxygen-icons5 (5:5.62.0-1 to 5:5.70.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
  • Build-Depends(-Arch): oxygen-icons5 extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oxygen-icons5.html
• pbcopper (1.3.0+dfsg-3 to 1.6.0+dfsg-3)
  • Migration status for pbcopper (1.3.0+dfsg-3 to 1.6.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pbcopper introduces new bugs: #959409
  • autopkgtest for pbbam/1.0.6+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): pbcopper simde
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pbcopper.html
• php-horde-mime (- to 2.11.0-5)
  • Migration status for php-horde-mime (- to 2.11.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-mime/2.11.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Depends: php-horde-mime php-horde-exception
  • Depends: php-horde-mime php-horde-listheaders
  • Depends: php-horde-mime php-horde-mail
  • Depends: php-horde-mime php-horde-stream
  • Depends: php-horde-mime php-horde-stream-filter
  • Depends: php-horde-mime php-horde-support
  • Depends: php-horde-mime php-horde-text-flowed
  • Depends: php-horde-mime php-horde-translation
  • Depends: php-horde-mime php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mime.html
• php-horde-passwd (- to 5.0.7-5)
  • Migration status for php-horde-passwd (- to 5.0.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-passwd/amd64 has unsatisfiable dependency
  • php-horde-passwd/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): php-horde-passwd php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-passwd.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-scheduler (- to 2.0.3-5)
  • Migration status for php-horde-scheduler (- to 2.0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-scheduler/amd64 has unsatisfiable dependency
  • php-horde-scheduler/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-scheduler.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-service-facebook (- to 2.0.10-5)
  • Migration status for php-horde-service-facebook (- to 2.0.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Depends: php-horde-service-facebook php-horde-exception
  • Depends: php-horde-service-facebook php-horde-http
  • Depends: php-horde-service-facebook php-horde-support
  • Depends: php-horde-service-facebook php-horde-translation
  • Depends: php-horde-service-facebook php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-facebook.html
• php-horde-service-gravatar (- to 1.0.1-7)
  • Migration status for php-horde-service-gravatar (- to 1.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-service-gravatar/1.0.1-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Depends: php-horde-service-gravatar php-horde-http
  • Depends: php-horde-service-gravatar php-horde-url
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-gravatar.html
• php-horde-service-twitter (- to 2.1.6-5)
  • Migration status for php-horde-service-twitter (- to 2.1.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Depends: php-horde-service-twitter php-horde-controller
  • Depends: php-horde-service-twitter php-horde-exception
  • Depends: php-horde-service-twitter php-horde-http
  • Depends: php-horde-service-twitter php-horde-oauth
  • Depends: php-horde-service-twitter php-horde-url
  • Depends: php-horde-service-twitter php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-twitter.html
• php-horde-service-weather (- to 2.5.4-5)
  • Migration status for php-horde-service-weather (- to 2.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-service-weather/2.5.4-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): php-horde-service-weather php-horde-role
  • Depends: php-horde-service-weather php-horde-date
  • Depends: php-horde-service-weather php-horde-exception
  • Depends: php-horde-service-weather php-horde-http
  • Depends: php-horde-service-weather php-horde-translation
  • Depends: php-horde-service-weather php-horde-url
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-weather.html
• php-horde-sesha (- to 1.0.0~rc3-5)
  • Migration status for php-horde-sesha (- to 1.0.0~rc3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-sesha/amd64 has unsatisfiable dependency
  • php-horde-sesha/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): php-horde-sesha php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-sesha.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-syncml (- to 2.0.7-6)
  • Migration status for php-horde-syncml (- to 2.0.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Depends: php-horde-syncml php-horde-date
  • Depends: php-horde-syncml php-horde-icalendar
  • Depends: php-horde-syncml php-horde-log
  • Depends: php-horde-syncml php-horde-support
  • Depends: php-horde-syncml php-horde-translation
  • Depends: php-horde-syncml php-horde-util
  • Depends: php-horde-syncml php-horde-xml-wbxml
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-syncml.html
• php-horde-template (- to 2.0.3-8)
  • Migration status for php-horde-template (- to 2.0.3-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-template.html
  • Required age reduced by 3 days because of autopkgtest
• php-horde-test (- to 2.6.3+debian0-5)
  • Migration status for php-horde-test (- to 2.6.3+debian0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Depends: php-horde-test php-horde-support
  • Depends: php-horde-test php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-test.html
• php-horde-text-filter-jsmin (- to 1.0.2-7)
  • Migration status for php-horde-text-filter-jsmin (- to 1.0.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-horde-text-filter-jsmin introduces new bugs: #953489
  • autopkgtest for php-horde-text-filter-jsmin/1.0.2-7: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Depends: php-horde-text-filter-jsmin php-horde-text-filter
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• php-horde-thrift (- to 2.0.3-5)
  • Migration status for php-horde-thrift (- to 2.0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-thrift.html
• php-horde-whups (- to 3.0.12-5)
  • Migration status for php-horde-whups (- to 3.0.12-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-whups/amd64 has unsatisfiable dependency
  • php-horde-whups/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): php-horde-whups php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-whups.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-wicked (- to 2.0.8-5)
  • Migration status for php-horde-wicked (- to 2.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-wicked/amd64 has unsatisfiable dependency
  • php-horde-wicked/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): php-horde-wicked php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-wicked.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-xml-wbxml (- to 2.0.3-7)
  • Migration status for php-horde-xml-wbxml (- to 2.0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-xml-wbxml/2.0.3-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Depends: php-horde-xml-wbxml php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-xml-wbxml.html
• pim-data-exporter (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for pim-data-exporter (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • pim-data-exporter unsatisfiable Build-Depends(-Arch) on mipsel: libkf5mailcommon-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): pim-data-exporter kxmlgui
  • Depends: pim-data-exporter akonadi
  • Depends: pim-data-exporter akonadi-mime
  • Depends: pim-data-exporter akonadi-notes
  • Depends: pim-data-exporter karchive
  • Depends: pim-data-exporter kcalcore
  • Depends: pim-data-exporter kconfig
  • Depends: pim-data-exporter kconfigwidgets
  • Depends: pim-data-exporter kcontacts
  • Depends: pim-data-exporter kcoreaddons
  • Depends: pim-data-exporter kcrash
  • Depends: pim-data-exporter kdbusaddons
  • Depends: pim-data-exporter kidentitymanagement
  • Depends: pim-data-exporter kio
  • Depends: pim-data-exporter kitemviews
  • Depends: pim-data-exporter kmailtransport
  • Depends: pim-data-exporter kmime
  • Depends: pim-data-exporter knotifications
  • Depends: pim-data-exporter kpimtextedit
  • Depends: pim-data-exporter kwidgetsaddons
  • Depends: pim-data-exporter kxmlgui
  • Depends: pim-data-exporter libkf5libkdepim
  • Depends: pim-data-exporter libkf5mailcommon
  • Depends: pim-data-exporter libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pim-data-exporter.html
• pim-sieve-editor (4:19.08.3-1 to 4:20.04.1-1)
  • Migration status for pim-sieve-editor (4:19.08.3-1 to 4:20.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • pim-sieve-editor unsatisfiable Build-Depends(-Arch) on mipsel: libkf5ksieve-dev (>= 4:20.04.1~)
  • missing build on mipsel
  • Too young, only 1 of 5 days old
  • Build-Depends(-Arch): pim-sieve-editor kpimtextedit
  • Depends: pim-sieve-editor kbookmarks
  • Depends: pim-sieve-editor kcrash
  • Depends: pim-sieve-editor kdbusaddons
  • Depends: pim-sieve-editor kiconthemes
  • Depends: pim-sieve-editor kmailtransport
  • Depends: pim-sieve-editor libkf5ksieve
  • Depends: pim-sieve-editor libkf5pimcommon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pim-sieve-editor.html
• plasma-framework (5.62.0-2 to 5.70.1-1)
  • Migration status for plasma-framework (5.62.0-2 to 5.70.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
  • Build-Depends(-Arch): plasma-framework kxmlgui
  • Depends: plasma-framework extra-cmake-modules
  • Depends: plasma-framework kactivities-kf5
  • Depends: plasma-framework karchive
  • Depends: plasma-framework kconfig
  • Depends: plasma-framework kconfigwidgets
  • Depends: plasma-framework kcoreaddons
  • Depends: plasma-framework kdeclarative
  • Depends: plasma-framework kglobalaccel
  • Depends: plasma-framework kguiaddons
  • Depends: plasma-framework ki18n
  • Depends: plasma-framework kiconthemes
  • Depends: plasma-framework kio
  • Depends: plasma-framework knotifications
  • Depends: plasma-framework kpackage
  • Depends: plasma-framework kservice
  • Depends: plasma-framework kwayland
  • Depends: plasma-framework kwidgetsaddons
  • Depends: plasma-framework kwindowsystem
  • Depends: plasma-framework kxmlgui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-framework.html
  • Required age reduced by 3 days because of autopkgtest
• prison-kf5 (5.62.0-1 to 5.70.0-1)
  • Migration status for prison-kf5 (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): prison-kf5 extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prison-kf5.html
• purpose (5.62.0-2 to 5.70.0-1)
  • Migration status for purpose (5.62.0-2 to 5.70.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
  • Build-Depends(-Arch): purpose kio
  • Depends: purpose bluez-qt
  • Depends: purpose kconfig
  • Depends: purpose kcoreaddons
  • Depends: purpose kdeclarative
  • Depends: purpose ki18n
  • Depends: purpose kio
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purpose.html
  • Required age reduced by 3 days because of autopkgtest
• pytest-mpi (0.3+git20191218.a8e7b56-2 to 0.3+git20191218.a8e7b56-3)
  • Migration status for pytest-mpi (0.3+git20191218.a8e7b56-2 to 0.3+git20191218.a8e7b56-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for pytest-mpi/0.3+git20191218.a8e7b56-3: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: upload info for arch all binaries not found, a new source-only upload is needed to allow migration
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-mpi.html
• python-blessed (1.16.1-1 to 1.17.6-1)
  • Migration status for python-blessed (1.16.1-1 to 1.17.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 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-blessed.html
  • Required age reduced by 3 days because of autopkgtest
• python-pip (20.1.1-1 to 20.1.1-2)
  • Migration status for python-pip (20.1.1-1 to 20.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 2 days old
  • Built-Using: python-pip six
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pip.html
  • Required age reduced by 3 days because of autopkgtest
• qqc2-desktop-style (5.62.0-1 to 5.70.0-1)
  • Migration status for qqc2-desktop-style (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): qqc2-desktop-style kiconthemes
  • Depends: qqc2-desktop-style kconfig
  • Depends: qqc2-desktop-style kiconthemes
  • Depends: qqc2-desktop-style kirigami2
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qqc2-desktop-style.html
• quodlibet (4.2.1-2 to 4.3.0-1)
  • Migration status for quodlibet (4.2.1-2 to 4.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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quodlibet.html
• r-bioc-gviz (1.30.3+dfsg-1 to 1.32.0+dfsg-2)
  • Migration status for r-bioc-gviz (1.30.3+dfsg-1 to 1.32.0+dfsg-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-gviz r-bioc-ensembldb
  • Depends: r-bioc-gviz r-base
  • Depends: r-bioc-gviz r-bioc-biocgenerics
  • Depends: r-bioc-gviz r-bioc-ensembldb
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-gviz.html
  • Required age reduced by 3 days because of autopkgtest
  • Too young, but urgency pushed by ginggs
  • 1 days old
• r-bioc-mutationalpatterns (- to 2.0.0-2)
  • Migration status for r-bioc-mutationalpatterns (- to 2.0.0-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-bioc-mutationalpatterns r-base
  • Depends: r-bioc-mutationalpatterns r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-mutationalpatterns.html
  • Required age reduced by 3 days because of autopkgtest
  • Too young, but urgency pushed by ginggs
  • 1 days old
• r-cran-etm (1.1-1 to 1.1-2)
  • Migration status for r-cran-etm (1.1-1 to 1.1-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-etm r-base
  • Additional info:
  • Updating r-cran-etm fixes old bugs: #961357
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-etm.html
  • Required age reduced by 3 days because of autopkgtest
  • Too young, but urgency pushed by ginggs
  • 1 days old
• r-cran-sp (1:1.4-1-1 to 1:1.4-2-2)
  • Migration status for r-cran-sp (1:1.4-1-1 to 1:1.4-2-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-sp r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sp.html
  • Should wait for tests relating to r-cran-sp 1:1.4-2-2, but forced by ginggs
  • autopkgtest for r-cran-raster/3.0-12-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, but urgency pushed by ginggs
  • 1 days old
• r-cran-vctrs (0.2.4-1 to 0.3.0-2)
  • Migration status for r-cran-vctrs (0.2.4-1 to 0.3.0-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-vctrs r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vctrs.html
  • Required age reduced by 3 days because of autopkgtest
  • Too young, but urgency pushed by ginggs
  • 1 days old
• r-other-ascat (- to 2.5.2-2)
  • Migration status for r-other-ascat (- to 2.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for r-other-ascat/2.5.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Depends: r-other-ascat r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-other-ascat.html
• redir (3.2-1 to 3.3-1)
  • Migration status for redir (3.2-1 to 3.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/redir.html
  • Required age reduced by 3 days because of autopkgtest
• ruby-gnome (3.4.1-2 to 3.4.3-1)
  • Migration status for ruby-gnome (3.4.1-2 to 3.4.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/ruby-gnome.html
  • Required age reduced by 3 days because of autopkgtest
• ruby-specinfra (2.82.12-1 to 2.82.16-1)
  • Migration status for ruby-specinfra (2.82.12-1 to 2.82.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/r/ruby-specinfra.html
  • Required age reduced by 3 days because of autopkgtest
• sgml-spell-checker (0.0.20040919-3 to 0.0.20040919-4)
  • Migration status for sgml-spell-checker (0.0.20040919-3 to 0.0.20040919-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/s/sgml-spell-checker.html
• shotwell (0.30.8-1 to 0.30.10-1)
  • Migration status for shotwell (0.30.8-1 to 0.30.10-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/shotwell.html
• simde (0.0.0.git.20200522-1 to 0.0.0.git.20200526-1)
  • Migration status for simde (0.0.0.git.20200522-1 to 0.0.0.git.20200526-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for simde/0.0.0.git.20200526-1: amd64: Pass, arm64: Regression ♻
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simde.html
• solid (5.62.0-2 to 5.70.0-1)
  • Migration status for solid (5.62.0-2 to 5.70.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
  • Build-Depends(-Arch): solid extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/solid.html
  • Required age reduced by 3 days because of autopkgtest
• sonnet (5.62.0-1 to 5.70.0-1)
  • Migration status for sonnet (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): sonnet extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sonnet.html
  • Required age reduced by 3 days because of autopkgtest
• soupsieve (2.0-1 to 2.0.1-1)
  • Migration status for soupsieve (2.0-1 to 2.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 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soupsieve.html
  • Required age reduced by 3 days because of autopkgtest
• stress-ng (0.11.10-1 to 0.11.12-1)
  • Migration status for stress-ng (0.11.10-1 to 0.11.12-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • autopkgtest for stress-ng/0.11.12-1: amd64: Pass, arm64: Test in progress
  • Too young, only 1 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stress-ng.html
• syndication (1:5.62.0-3 to 1:5.70.0-1)
  • Migration status for syndication (1:5.62.0-3 to 1:5.70.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
  • Build-Depends(-Arch): syndication kcodecs
  • Depends: syndication kcodecs
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syndication.html
• tang (7-1 to 7-2)
  • Migration status for tang (7-1 to 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 2 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tang.html
  • Required age reduced by 3 days because of autopkgtest
• telegram-desktop (2.1.5+ds-1 to 2.1.7+ds-1)
  • Migration status for telegram-desktop (2.1.5+ds-1 to 2.1.7+ds-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/telegram-desktop.html
• threadweaver (5.62.0-1 to 5.70.0-1)
  • Migration status for threadweaver (5.62.0-1 to 5.70.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
  • Build-Depends(-Arch): threadweaver extra-cmake-modules
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/threadweaver.html
  • Required age reduced by 3 days because of autopkgtest
• tpm2-tools (4.2-3 to 4.2.1-1)
  • Migration status for tpm2-tools (4.2-3 to 4.2.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 7 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-tools.html
  • Required age reduced by 3 days because of autopkgtest
• transifex-client (0.13.5-2 to 0.13.9-1)
  • Migration status for transifex-client (0.13.5-2 to 0.13.9-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/transifex-client.html
  • Required age reduced by 3 days because of autopkgtest
• tycho (1.5.0-1 to 1.6.0-1)
  • Migration status for tycho (1.5.0-1 to 1.6.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/t/tycho.html
• vagrant-sshfs (1.3.1-1 to 1.3.4-1)
  • Migration status for vagrant-sshfs (1.3.1-1 to 1.3.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/v/vagrant-sshfs.html
  • Required age reduced by 3 days because of autopkgtest
• vamp-plugin-sdk (2.9.0-1 to 2.10.0-1)
  • Migration status for vamp-plugin-sdk (2.9.0-1 to 2.10.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/v/vamp-plugin-sdk.html
• wala (1.5.1-1 to 1.5.2-1)
  • Migration status for wala (1.5.1-1 to 1.5.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 5 days old
  • Additional info:
  • Updating wala fixes old bugs: #955695
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wala.html
• wmcore (0.0.3-1 to 0.0.4-1)
  • Migration status for wmcore (0.0.3-1 to 0.0.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/w/wmcore.html
• wpebackend-fdo (1.6.0-1 to 1.6.1-1)
  • Migration status for wpebackend-fdo (1.6.0-1 to 1.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/w/wpebackend-fdo.html
• wsjtx (2.2.0~rc1+repack-1 to 2.2.0~rc2+repack-1)
  • Migration status for wsjtx (2.2.0~rc1+repack-1 to 2.2.0~rc2+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
  • Depends: wsjtx gcc-10
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wsjtx.html
• zabbix (1:5.0.0+dfsg-1 to 1:5.0.1+dfsg-1)
  • Migration status for zabbix (1:5.0.0+dfsg-1 to 1:5.0.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/z/zabbix.html
• zoneminder (1.34.14-1 to 1.34.15-1)
  • Migration status for zoneminder (1.34.14-1 to 1.34.15-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/z/zoneminder.html
• avahi (0.8-1 to 0.8-3)
  • Migration status for avahi (0.8-1 to 0.8-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:
  • Updating avahi fixes old bugs: #936173
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avahi.html
• backupchecker (- to 1.7-2)
  • Migration status for backupchecker (- to 1.7-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/b/backupchecker.html
• bowtie2 (2.4.1-4 to 2.4.1-5)
  • Migration status for bowtie2 (2.4.1-4 to 2.4.1-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/b/bowtie2.html
  • Required age reduced by 3 days because of autopkgtest
  • 2 days old (needed 2 days)
• cacti-spine (1.2.6-1 to 1.2.12-1)
  • Migration status for cacti-spine (1.2.6-1 to 1.2.12-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/cacti-spine.html
• clusterssh (4.15-1 to 4.15-2)
  • Migration status for clusterssh (4.15-1 to 4.15-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/c/clusterssh.html
• compton (0.1~beta2+20150922-1 to 0.1~beta2+20150922-2)
  • Migration status for compton (0.1~beta2+20150922-1 to 0.1~beta2+20150922-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/c/compton.html
• debian-edu-config (2.11.25 to 2.11.26)
  • Migration status for debian-edu-config (2.11.25 to 2.11.26): 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/d/debian-edu-config.html
• debsums (2.2.5 to 3.0.0)
  • Migration status for debsums (2.2.5 to 3.0.0): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • Too young, only 2 of 7 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debsums.html
  • Required age reduced by 3 days because of autopkgtest
• django-q (1.0.2-1 to 1.2.1-1)
  • Migration status for django-q (1.0.2-1 to 1.2.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/d/django-q.html
• doctest (2.3.7+repack0-1 to 2.3.8+repack0-1)
  • Migration status for doctest (2.3.7+repack0-1 to 2.3.8+repack0-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/d/doctest.html
• drop-seq (- to 2.3.0+dfsg-2)
  • Migration status for drop-seq (- to 2.3.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • drop-seq-tools/i386 has unsatisfiable dependency
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): drop-seq libla4j-java
  • Depends: drop-seq libla4j-java
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drop-seq.html
  • uninstallable on arch arm64, not running autopkgtest there
• elektroid (1.1-1 to 1.2-1)
  • Migration status for elektroid (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 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elektroid.html
• flask-assets (0.12-3 to 2.0-1)
  • Migration status for flask-assets (0.12-3 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 2 of 5 days old
  • Additional info:
  • Updating flask-assets fixes old bugs: #959588
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-assets.html
• fonts-oldstandard (- to 2.2really-4)
  • Migration status for fonts-oldstandard (- to 2.2really-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/f/fonts-oldstandard.html
• gcc-10 (10.1.0-2 to 10.1.0-3)
  • Migration status for gcc-10 (10.1.0-2 to 10.1.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10.html
  • autopkgtest for dolfin/2019.2.0~git20200218.027d9cc-6: amd64: Pass, arm64: Ignored failure
  • autopkgtest for openjdk-14/blacklisted: amd64: Ignored failure, arm64: Ignored failure
  • autopkgtest for swi-prolog/8.1.29+dfsg-2: amd64: Ignored failure, arm64: Ignored failure
  • Required age reduced by 3 days because of autopkgtest
  • 2 days old (needed 2 days)
• gcc-10-cross (7 to 9)
  • Migration status for gcc-10-cross (7 to 9): 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
  • Build-Depends(-Arch): gcc-10-cross gcc-10
  • Built-Using: gcc-10-cross gcc-10
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross.html
• gcc-10-cross-ports (6 to 8)
  • Migration status for gcc-10-cross-ports (6 to 8): 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
  • Build-Depends(-Arch): gcc-10-cross-ports gcc-10
  • Built-Using: gcc-10-cross-ports gcc-10
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-ports.html
• gcc-snapshot (- to 1:20200525-1)
  • Migration status for gcc-snapshot (- to 1:20200525-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gcc-snapshot introduces new bugs: #321449, #651291
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-snapshot.html
  • autopkgtest for dolfin/2019.2.0~git20200218.027d9cc-6: amd64: Pass, arm64: Ignored failure
  • Required age reduced by 3 days because of autopkgtest
  • 2 days old (needed 2 days)
• geronimo-commonj-spec (1.1.1-3 to 1.1.1-4)
  • Migration status for geronimo-commonj-spec (1.1.1-3 to 1.1.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:
  • Updating geronimo-commonj-spec fixes old bugs: #952340
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geronimo-commonj-spec.html
• gfarm (2.7.15+dfsg-1 to 2.7.16+dfsg-1)
  • Migration status for gfarm (2.7.15+dfsg-1 to 2.7.16+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/g/gfarm.html
• gtkwave (3.3.104-1 to 3.3.104-2)
  • Migration status for gtkwave (3.3.104-1 to 3.3.104-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/g/gtkwave.html
• iverilog (10.3-1 to 10.3-2)
  • Migration status for iverilog (10.3-1 to 10.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/i/iverilog.html
• libhdhomerun (20200225-1 to 20200521-1)
  • Migration status for libhdhomerun (20200225-1 to 20200521-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/libh/libhdhomerun.html
• libla4j-java (- to 0.6.0-2)
  • Migration status for libla4j-java (- to 0.6.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/libl/libla4j-java.html
• libmonitoring-icinga2-client-rest-perl (2.0.0-2 to 2.0.3-1)
  • Migration status for libmonitoring-icinga2-client-rest-perl (2.0.0-2 to 2.0.3-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/libm/libmonitoring-icinga2-client-rest-perl.html
• libsndfile (1.0.28-7 to 1.0.28-8)
  • Migration status for libsndfile (1.0.28-7 to 1.0.28-8): 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/libs/libsndfile.html
• lxc (1:3.1.0+really3.0.4-3 to 1:4.0.2-1)
  • Migration status for lxc (1:3.1.0+really3.0.4-3 to 1:4.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lxc introduces new bugs: #961584
  • autopkgtest for lxc/1:4.0.2-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxc.html
• lxcfs (3.0.4-2 to 4.0.3-1)
  • Migration status for lxcfs (3.0.4-2 to 4.0.3-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/l/lxcfs.html
• mecab (0.996-12 to 0.996-13)
  • Migration status for mecab (0.996-12 to 0.996-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for mecab/0.996-13: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 2 of 5 days old
  • Additional info:
  • Updating mecab fixes old bugs: #961253
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mecab.html
• mescc-tools (0.7.0-1 to 1.0.1-2)
  • Migration status for mescc-tools (0.7.0-1 to 1.0.1-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/m/mescc-tools.html
• node-domain-browser (1.2.0-1 to 4.4.0-1)
  • Migration status for node-domain-browser (1.2.0-1 to 4.4.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/n/node-domain-browser.html
• nuitka (- to 0.6.8.3+ds-1)
  • Migration status for nuitka (- to 0.6.8.3+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by yoh, 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/n/nuitka.html
• opencsv (5.1+ds-1 to 5.2-1)
  • Migration status for opencsv (5.1+ds-1 to 5.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/o/opencsv.html
• opensmtpd-extras (6.6.0-1 to 6.7.1-2)
  • Migration status for opensmtpd-extras (6.6.0-1 to 6.7.1-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/o/opensmtpd-extras.html
• php-horde-content (- to 2.0.6-5)
  • Migration status for php-horde-content (- to 2.0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-content/amd64 has unsatisfiable dependency
  • php-horde-content/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-content php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-content.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-dav (- to 1.1.4-5)
  • Migration status for php-horde-dav (- to 1.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-dav/amd64 has unsatisfiable dependency
  • php-horde-dav/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-dav.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-elasticsearch (- to 1.0.4-5)
  • Migration status for php-horde-elasticsearch (- to 1.0.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-elasticsearch php-horde-exception
  • Depends: php-horde-elasticsearch php-horde-http
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-elasticsearch.html
• php-horde-feed (- to 2.0.4-7)
  • Migration status for php-horde-feed (- to 2.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-feed/2.0.4-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-feed php-horde-exception
  • Depends: php-horde-feed php-horde-http
  • Depends: php-horde-feed php-horde-xml-element
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-feed.html
• php-horde-form (- to 2.0.19-2)
  • Migration status for php-horde-form (- to 2.0.19-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-form/amd64 has unsatisfiable dependency
  • php-horde-form/i386 has unsatisfiable dependency
  • Updating php-horde-form introduces new bugs: #955020
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-form.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-gollem (- to 3.0.12-5)
  • Migration status for php-horde-gollem (- to 3.0.12-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-gollem/amd64 has unsatisfiable dependency
  • php-horde-gollem/i386 has unsatisfiable dependency
  • Updating php-horde-gollem introduces new bugs: #961649
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-gollem php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-gollem.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-groupware (- to 5.2.22-5)
  • Migration status for php-horde-groupware (- to 5.2.22-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-groupware/amd64 has unsatisfiable dependency
  • php-horde-groupware/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-groupware php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-groupware.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-hashtable (- to 1.2.6-5)
  • Migration status for php-horde-hashtable (- to 1.2.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-hashtable/1.2.6-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-hashtable php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-hashtable.html
• php-horde-imp (- to 6.2.24-2)
  • Migration status for php-horde-imp (- to 6.2.24-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-imp/amd64 has unsatisfiable dependency
  • php-horde-imp/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-imp php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-imp.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-imsp (- to 2.0.10-5)
  • Migration status for php-horde-imsp (- to 2.0.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-imsp php-horde-translation
  • Depends: php-horde-imsp php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imsp.html
• php-horde-ingo (- to 3.2.16-5)
  • Migration status for php-horde-ingo (- to 3.2.16-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-ingo/amd64 has unsatisfiable dependency
  • php-horde-ingo/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-ingo php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-ingo.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-javascriptminify-jsmin (- to 1.0.2-7)
  • Migration status for php-horde-javascriptminify-jsmin (- to 1.0.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-horde-javascriptminify-jsmin introduces new bugs: #953416
  • autopkgtest for php-horde-javascriptminify-jsmin/1.0.2-7: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 2 of 5 days old
  • Depends: php-horde-javascriptminify-jsmin php-horde-javascriptminify
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• php-horde-kolab-format (- to 2.0.9-5)
  • Migration status for php-horde-kolab-format (- to 2.0.9-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-kolab-format/2.0.9-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-kolab-format php-horde-exception
  • Depends: php-horde-kolab-format php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-format.html
• php-horde-kolab-server (- to 2.0.5-7)
  • Migration status for php-horde-kolab-server (- to 2.0.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-kolab-server/2.0.5-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-kolab-server php-horde-auth
  • Depends: php-horde-kolab-server php-horde-exception
  • Depends: php-horde-kolab-server php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-server.html
• php-horde-kolab-session (- to 2.0.3-7)
  • Migration status for php-horde-kolab-session (- to 2.0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-kolab-session/2.0.3-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-kolab-session php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-session.html
• php-horde-kolab-storage (- to 2.2.3-5)
  • Migration status for php-horde-kolab-storage (- to 2.2.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-kolab-storage/2.2.3-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-kolab-storage php-horde-cache
  • Depends: php-horde-kolab-storage php-horde-exception
  • Depends: php-horde-kolab-storage php-horde-kolab-format
  • Depends: php-horde-kolab-storage php-horde-mime
  • Depends: php-horde-kolab-storage php-horde-support
  • Depends: php-horde-kolab-storage php-horde-translation
  • Depends: php-horde-kolab-storage php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-storage.html
• php-horde-kronolith (- to 4.2.27-2)
  • Migration status for php-horde-kronolith (- to 4.2.27-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-kronolith/amd64 has unsatisfiable dependency
  • php-horde-kronolith/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-kronolith php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-kronolith.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-ldap (- to 2.4.1-3)
  • Migration status for php-horde-ldap (- to 2.4.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-ldap/2.4.1-3: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-ldap php-horde-exception
  • Depends: php-horde-ldap php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ldap.html
• php-horde-lz4 (- to 1.0.10-6)
  • Migration status for php-horde-lz4 (- to 1.0.10-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-lz4/1.0.10-6: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by mike.gabriel@das-netzwerkteam.de
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-lz4.html
• php-horde-mapi (- to 1.0.10-2)
  • Migration status for php-horde-mapi (- to 1.0.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-mapi/1.0.10-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-mapi php-horde-date
  • Depends: php-horde-mapi php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mapi.html
• php-horde-memcache (- to 2.1.1-5)
  • Migration status for php-horde-memcache (- to 2.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-memcache php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-memcache.html
• php-horde-mnemo (- to 4.2.14-5)
  • Migration status for php-horde-mnemo (- to 4.2.14-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-mnemo/amd64 has unsatisfiable dependency
  • php-horde-mnemo/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-mnemo php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-mnemo.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-mongo (- to 1.1.0-5)
  • Migration status for php-horde-mongo (- to 1.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-horde-mongo introduces new bugs: #820091
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mongo.html
• php-horde-nag (- to 4.2.19-3)
  • Migration status for php-horde-nag (- to 4.2.19-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-nag/amd64 has unsatisfiable dependency
  • php-horde-nag/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-nag php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-nag.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-oauth (- to 2.0.4-5)
  • Migration status for php-horde-oauth (- to 2.0.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-oauth php-horde-exception
  • Depends: php-horde-oauth php-horde-http
  • Depends: php-horde-oauth php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-oauth.html
• php-horde-openxchange (- to 1.0.1-5)
  • Migration status for php-horde-openxchange (- to 1.0.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-openxchange php-horde-date
  • Depends: php-horde-openxchange php-horde-http
  • Depends: php-horde-openxchange php-horde-perms
  • Depends: php-horde-openxchange php-horde-url
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-openxchange.html
• php-horde-pdf (- to 2.0.7-7)
  • Migration status for php-horde-pdf (- to 2.0.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-pdf/2.0.7-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-pdf php-horde-exception
  • Depends: php-horde-pdf php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-pdf.html
• php-horde-scribe (- to 2.0.3-5)
  • Migration status for php-horde-scribe (- to 2.0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: php-horde-scribe php-horde-thrift
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-scribe.html
• php-horde-timeobjects (- to 2.1.4-5)
  • Migration status for php-horde-timeobjects (- to 2.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-timeobjects/amd64 has unsatisfiable dependency
  • php-horde-timeobjects/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-timeobjects php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-timeobjects.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-trean (- to 1.1.9-5)
  • Migration status for php-horde-trean (- to 1.1.9-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-trean/amd64 has unsatisfiable dependency
  • php-horde-trean/i386 has unsatisfiable dependency
  • Updating php-horde-trean introduces new bugs: #955019
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-trean php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-trean.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-turba (- to 4.2.25-2)
  • Migration status for php-horde-turba (- to 4.2.25-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-turba/amd64 has unsatisfiable dependency
  • php-horde-turba/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-turba php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-turba.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• php-horde-webmail (- to 5.2.22-5)
  • Migration status for php-horde-webmail (- to 5.2.22-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-webmail/amd64 has unsatisfiable dependency
  • php-horde-webmail/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Build-Depends(-Arch): php-horde-webmail php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-webmail.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• plume-creator (- to 0.66+dfsg1-3.2)
  • Migration status for plume-creator (- to 0.66+dfsg1-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/plume-creator.html
• po4a (0.59-1 to 0.59.1-1)
  • Migration status for po4a (0.59-1 to 0.59.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:
  • Updating po4a fixes old bugs: #960892
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/po4a.html
• poezio (0.12.1-3 to 0.13-1)
  • Migration status for poezio (0.12.1-3 to 0.13-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/poezio.html
• pspp (- to 1.2.0-5)
  • Migration status for pspp (- to 1.2.0-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/pspp.html
• r-bioc-iranges (2.20.2-1 to 2.22.2-1)
  • Migration status for r-bioc-iranges (2.20.2-1 to 2.22.2-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-iranges r-bioc-s4vectors
  • Depends: r-bioc-iranges r-base
  • Depends: r-bioc-iranges r-bioc-biocgenerics
  • Depends: r-bioc-iranges r-bioc-s4vectors
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-iranges.html
  • Should wait for tests relating to r-bioc-iranges 2.22.2-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-bioc-multiassayexperiment/1.12.6+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, but urgency pushed by ginggs
  • 2 days old
• r-cran-fontbitstreamvera (0.1.1+dfsg-2 to 0.1.1+dfsg-4)
  • Migration status for r-cran-fontbitstreamvera (0.1.1+dfsg-2 to 0.1.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fontbitstreamvera r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fontbitstreamvera.html
  • Required age reduced by 3 days because of autopkgtest
  • 2 days old (needed 2 days)
• r-cran-ggeffects (0.14.3-1 to 0.14.3-3)
  • Migration status for r-cran-ggeffects (0.14.3-1 to 0.14.3-3): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-ggeffects r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggeffects.html
  • Should wait for tests relating to r-cran-ggeffects 0.14.3-3, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, but urgency pushed by ginggs
  • 2 days old
• r-cran-mice (3.8.0-2 to 3.9.0-2)
  • Migration status for r-cran-mice (3.8.0-2 to 3.9.0-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-mice r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mice.html
  • Should wait for tests relating to r-cran-mice 3.9.0-2, but forced by ginggs
  • autopkgtest for r-cran-sjmisc/2.8.4-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, but urgency pushed by ginggs
  • 2 days old
• r-cran-sjmisc (2.8.4-1 to 2.8.4-3)
  • Migration status for r-cran-sjmisc (2.8.4-1 to 2.8.4-3): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-sjmisc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sjmisc.html
  • Should wait for tests relating to r-cran-sjmisc 2.8.4-3, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, but urgency pushed by ginggs
  • 2 days old
• r-cran-sjplot (2.8.3-1 to 2.8.3-3)
  • Migration status for r-cran-sjplot (2.8.3-1 to 2.8.3-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sjplot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sjplot.html
  • Required age reduced by 3 days because of autopkgtest
  • 2 days old (needed 2 days)
• remmina (1.4.3+dfsg-2 to 1.4.5+dfsg-1)
  • Migration status for remmina (1.4.3+dfsg-2 to 1.4.5+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/r/remmina.html
• rkward (0.7.1-1 to 0.7.1b-1)
  • Migration status for rkward (0.7.1-1 to 0.7.1b-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: rkward r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rkward.html
  • Too young, but urgency pushed by sramacher
  • 2 days old
• ruby-espeak (- to 1.0.4-2)
  • Migration status for ruby-espeak (- to 1.0.4-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/r/ruby-espeak.html
• sendmail (8.15.2-18 to 8.15.2-19)
  • Migration status for sendmail (8.15.2-18 to 8.15.2-19): 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/sendmail.html
• slang2 (2.3.2-4 to 2.3.2-5)
  • Migration status for slang2 (2.3.2-4 to 2.3.2-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/s/slang2.html
• slixmpp (1.5.1-1 to 1.5.2-1)
  • Migration status for slixmpp (1.5.1-1 to 1.5.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/s/slixmpp.html
• sqlite3 (3.31.1-5 to 3.32.1-1)
  • Migration status for sqlite3 (3.31.1-5 to 3.32.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python3.8/3.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for rspamd/2.5-1: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Updating sqlite3 fixes old bugs: #961488
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlite3.html
  • 2 days old (needed 2 days)
• sra-sdk (2.9.3+dfsg-1 to 2.10.6+dfsg-5)
  • Migration status for sra-sdk (2.9.3+dfsg-1 to 2.10.6+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Build-Depends(-Arch): sra-sdk ncbi-vdb (not considered)
  • Depends: sra-sdk ncbi-vdb (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Updating sra-sdk fixes old bugs: #961049
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sra-sdk.html
  • Required age reduced by 3 days because of autopkgtest
  • 2 days old (needed 2 days)
• sugar (- to 0.117-2)
  • Migration status for sugar (- to 0.117-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Depends: sugar sugar-pippy-activity
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sugar.html
• tempest (1:24.0.0-3 to 1:24.0.0-4)
  • Migration status for tempest (1:24.0.0-3 to 1:24.0.0-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/tempest.html
• tilde (1.0.0-1 to 1.1.2-1)
  • Migration status for tilde (1.0.0-1 to 1.1.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/t/tilde.html
• uwsgi-plugin-luajit (0.0.3 to 0.0.4)
  • Migration status for uwsgi-plugin-luajit (0.0.3 to 0.0.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
  • Depends: uwsgi-plugin-luajit uwsgi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uwsgi-plugin-luajit.html
• uwsgi-plugin-mongo (- to 0.0.5)
  • Migration status for uwsgi-plugin-mongo (- to 0.0.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
  • Build-Depends(-Arch): uwsgi-plugin-mongo mongo-cxx-driver-legacy
  • Depends: uwsgi-plugin-mongo mongo-cxx-driver-legacy
  • Depends: uwsgi-plugin-mongo uwsgi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uwsgi-plugin-mongo.html
• uwsgi-plugin-php (0.0.4 to 0.0.6)
  • Migration status for uwsgi-plugin-php (0.0.4 to 0.0.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for uwsgi-plugin-php/0.0.6: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 2 of 5 days old
  • Depends: uwsgi-plugin-php uwsgi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uwsgi-plugin-php.html
• verilator (4.034-1 to 4.034-2)
  • Migration status for verilator (4.034-1 to 4.034-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 verilator fixes old bugs: #960480
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilator.html
• wireless-regdb (2019.06.03-3 to 2020.04.29-1)
  • Migration status for wireless-regdb (2019.06.03-3 to 2020.04.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by romain.perier@gmail.com, a new source-only upload is needed to allow migration
  • Too young, only 2 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wireless-regdb.html
• wmcube (1.0.2-2 to 1.0.2-3)
  • Migration status for wmcube (1.0.2-2 to 1.0.2-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/w/wmcube.html
• xfonts-terminus (4.48-2 to 4.48-3)
  • Migration status for xfonts-terminus (4.48-2 to 4.48-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/x/xfonts-terminus.html
• apparmor (2.13.4-1 to 2.13.4-2)
  • Migration status for apparmor (2.13.4-1 to 2.13.4-2): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • autopkgtest for php7.4/7.4.5-1: amd64: Pass, arm64: Test in progress
  • autopkgtest for stress-ng/0.11.10-1: amd64: Pass, arm64: Test in progress
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apparmor.html
• bobcat (5.04.01-1 to 5.05.00-1)
  • Migration status for bobcat (5.04.01-1 to 5.05.00-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/bobcat.html
• calibre (4.99.4+dfsg+really4.16.0-1 to 4.99.4+dfsg+really4.17.0-1)
  • Migration status for calibre (4.99.4+dfsg+really4.16.0-1 to 4.99.4+dfsg+really4.17.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/calibre.html
• caml-crush (- to 1.0.9-1)
  • Migration status for caml-crush (- to 1.0.9-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/caml-crush.html
• codespell (1.16.0-2 to 1.17.1-1)
  • Migration status for codespell (1.16.0-2 to 1.17.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/c/codespell.html
• debianutils (4.9.1 to 4.11)
  • Migration status for debianutils (4.9.1 to 4.11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for debianutils/4.11: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debianutils.html
• django-ranged-response (0.2.0-2 to 0.2.0-4)
  • Migration status for django-ranged-response (0.2.0-2 to 0.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-ranged-response.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• e-antic (0.1.3+ds-3 to 0.1.5+ds-2)
  • Migration status for e-antic (0.1.3+ds-3 to 0.1.5+ds-2): 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/e/e-antic.html
• elogind (241.3-1+debian3 to 243.7-1+debian1)
  • Migration status for elogind (241.3-1+debian3 to 243.7-1+debian1): 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/elogind.html
• exabgp (4.2.4-1 to 4.2.8-1)
  • Migration status for exabgp (4.2.4-1 to 4.2.8-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/exabgp.html
• fasttracker2 (1.22-1 to 1.24-1)
  • Migration status for fasttracker2 (1.22-1 to 1.24-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)
• firehol (3.1.6+ds-9 to 3.1.6+ds-10)
  • Migration status for firehol (3.1.6+ds-9 to 3.1.6+ds-10): 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/firehol.html
• gcc-9-cross (21 to 22)
  • Migration status for gcc-9-cross (21 to 22): 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/gcc-9-cross.html
• gcc-9-cross-ports (16 to 20)
  • Migration status for gcc-9-cross-ports (16 to 20): 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 gcc-9-cross-ports fixes old bugs: #961397
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross-ports.html
• gnuastro (0.11-1 to 0.12-1)
  • Migration status for gnuastro (0.11-1 to 0.12-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/g/gnuastro.html
• grcompiler (4.2-7 to 5.2-1)
  • Migration status for grcompiler (4.2-7 to 5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating grcompiler introduces new bugs: #961438, #961444, #961445
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on ppc64el
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grcompiler.html
• gyp (0.1+20180428git4d467626-3 to 0.1+20200513gitcaa6002-1)
  • Migration status for gyp (0.1+20180428git4d467626-3 to 0.1+20200513gitcaa6002-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/g/gyp.html
• hunspell-lv (1.3.0-5 to 1.4.0-1)
  • Migration status for hunspell-lv (1.3.0-5 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/h/hunspell-lv.html
• id-utils (- to 4.6.28-20200521ss15dab)
  • Migration status for id-utils (- to 4.6.28-20200521ss15dab): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by brad
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/id-utils.html
• ivtools (1.2.11a3-1 to 1.2.11a3-3)
  • Migration status for ivtools (1.2.11a3-1 to 1.2.11a3-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/i/ivtools.html
• king-probe (2.16.160404+git20180613.a09b012-1 to 2.16.160404+git20200121.9b198c1-2)
  • Migration status for king-probe (2.16.160404+git20180613.a09b012-1 to 2.16.160404+git20200121.9b198c1-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/k/king-probe.html
• linux-signed-amd64 (5.6.7+1 to 5.6.14+1)
  • Migration status for linux-signed-amd64 (5.6.7+1 to 5.6.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
  • Build-Depends(-Arch): linux-signed-amd64 linux
  • Built-Using: linux-signed-amd64 linux
  • Depends: linux-signed-amd64 linux
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-signed-amd64.html
• linux-signed-arm64 (5.6.7+1 to 5.6.14+1)
  • Migration status for linux-signed-arm64 (5.6.7+1 to 5.6.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
  • Build-Depends(-Arch): linux-signed-arm64 linux
  • Built-Using: linux-signed-arm64 linux
  • Depends: linux-signed-arm64 linux
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• linux-signed-i386 (5.6.7+1 to 5.6.14+1)
  • Migration status for linux-signed-i386 (5.6.7+1 to 5.6.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
  • Build-Depends(-Arch): linux-signed-i386 linux
  • Built-Using: linux-signed-i386 linux
  • Depends: linux-signed-i386 linux
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• maildir-utils (1.4.6-1 to 1.4.7-1)
  • Migration status for maildir-utils (1.4.6-1 to 1.4.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/m/maildir-utils.html
• mapproxy (1.12.0-1 to 1.12.0-2)
  • Migration status for mapproxy (1.12.0-1 to 1.12.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/mapproxy.html
• matrix-synapse (1.12.4-1 to 1.13.0-1)
  • Migration status for matrix-synapse (1.12.4-1 to 1.13.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/m/matrix-synapse.html
• mbpfan (2.1.1-2 to 2.2.1-1)
  • Migration status for mbpfan (2.1.1-2 to 2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mbpfan/amd64 has unsatisfiable dependency
  • mbpfan/arm64 has unsatisfiable dependency
  • mbpfan/armel has unsatisfiable dependency
  • mbpfan/armhf has unsatisfiable dependency
  • mbpfan/i386 has unsatisfiable dependency
  • mbpfan/mips64el has unsatisfiable dependency
  • mbpfan/mipsel has unsatisfiable dependency
  • mbpfan/ppc64el has unsatisfiable dependency
  • mbpfan/s390x has unsatisfiable dependency
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/mbpfan.html
  • Too young, only 3 of 5 days old
  • Additional info:
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
• mes (0.22-1 to 0.22-2)
  • Migration status for mes (0.22-1 to 0.22-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
  • Build-Depends(-Arch): mes mescc-tools
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mes.html
• nautilus-filename-repairer (0.2.0-2 to 0.2.0-3)
  • Migration status for nautilus-filename-repairer (0.2.0-2 to 0.2.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 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-filename-repairer.html
• node-cookie-parser (1.4.4-1 to 1.4.5-1)
  • Migration status for node-cookie-parser (1.4.4-1 to 1.4.5-1): Waiting for test results, another package or too young (no action required now - check later)
  • Issues preventing migration:
  • autopkgtest for node-superagent/5.2.2-2: amd64: Pass, arm64: Test in progress
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-cookie-parser.html
• node-cosmiconfig (5.2.1-2 to 6.0.0+~cs16.3.1-1)
  • Migration status for node-cosmiconfig (5.2.1-2 to 6.0.0+~cs16.3.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/n/node-cosmiconfig.html
• node-cross-spawn (5.1.0-3 to 7.0.2-1)
  • Migration status for node-cross-spawn (5.1.0-3 to 7.0.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/n/node-cross-spawn.html
• node-cryptiles (- to 5.1.0-1)
  • Migration status for node-cryptiles (- to 5.1.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
  • Build-Depends(-Arch): node-cryptiles node-boom
  • Depends: node-cryptiles node-boom
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-cryptiles.html
• node-css-color-names (0.0.4+dfsg-2 to 1.0.1+dfsg-1)
  • Migration status for node-css-color-names (0.0.4+dfsg-2 to 1.0.1+dfsg-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/n/node-css-color-names.html
• node-cssom (0.3.0-1 to 0.4.4-1)
  • Migration status for node-cssom (0.3.0-1 to 0.4.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/n/node-cssom.html
• notcurses (1.4.2.3+dfsg.1-1 to 1.4.3+dfsg.1-1)
  • Migration status for notcurses (1.4.2.3+dfsg.1-1 to 1.4.3+dfsg.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/n/notcurses.html
• nvidia-cuda-toolkit (10.1.168-8 to 10.1.168-11)
  • Migration status for nvidia-cuda-toolkit (10.1.168-8 to 10.1.168-11): 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)
• ocaml-dtools (0.4.1-1 to 0.4.2-1)
  • Migration status for ocaml-dtools (0.4.1-1 to 0.4.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/o/ocaml-dtools.html
• openscenegraph (3.6.4+dfsg1-3 to 3.6.5+dfsg1-3)
  • Migration status for openscenegraph (3.6.4+dfsg1-3 to 3.6.5+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by aluaces@udc.es
  • Not built on buildd: arch all binaries uploaded by aluaces@udc.es, a new source-only upload is needed to allow migration
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openscenegraph.html
• opensurgsim (- to 0.7.0-10)
  • Migration status for opensurgsim (- to 0.7.0-10): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on i386
  • missing build on mips64el
  • Too young, only 3 of 5 days old
  • Depends: opensurgsim openscenegraph
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensurgsim.html
• pt2-clone (1.15-1 to 1.16-1)
  • Migration status for pt2-clone (1.15-1 to 1.16-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/pt2-clone.html
• pveclib (- to 1.0.1+dfsg-1)
  • Migration status for pveclib (- to 1.0.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch ppc64el binaries uploaded by kilobyte
  • Too young, only 3 of 5 days old
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-jenkinsapi (- to 0.3.11-2)
  • Migration status for python-jenkinsapi (- to 0.3.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ahs3, a new source-only upload is needed to allow migration
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jenkinsapi.html
• python-pynetstring (0.2-2 to 0.5-1)
  • Migration status for python-pynetstring (0.2-2 to 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/p/python-pynetstring.html
• r-bioc-chemminer (- to 3.40.0+dfsg-2)
  • Migration status for r-bioc-chemminer (- to 3.40.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-chemminer r-base
  • Depends: r-bioc-chemminer r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-chemminer.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• r-cran-bms (0.3.4-4 to 0.3.4-6)
  • Migration status for r-cran-bms (0.3.4-4 to 0.3.4-6): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bms r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bms.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• r-cran-fontliberation (0.1.0+dfsg-2 to 0.1.0+dfsg-4)
  • Migration status for r-cran-fontliberation (0.1.0+dfsg-2 to 0.1.0+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fontliberation r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fontliberation.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• r-cran-httpuv (1.5.2+dfsg-1 to 1.5.2+dfsg-2)
  • Migration status for r-cran-httpuv (1.5.2+dfsg-1 to 1.5.2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-httpuv r-base
  • Additional info:
  • Updating r-cran-httpuv fixes old bugs: #961405
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-httpuv.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• r-cran-learnbayes (2.15.1-2 to 2.15.1-4)
  • Migration status for r-cran-learnbayes (2.15.1-2 to 2.15.1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-learnbayes r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-learnbayes.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• r-cran-nozzle.r1 (1.1-1+dfsg-2 to 1.1-1+dfsg-4)
  • Migration status for r-cran-nozzle.r1 (1.1-1+dfsg-2 to 1.1-1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nozzle.r1 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-nozzle.r1.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• r-cran-raster (3.0-12-1 to 3.1-5-2)
  • Migration status for r-cran-raster (3.0-12-1 to 3.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-raster r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-raster.html
  • Required age reduced by 3 days because of autopkgtest
  • 3 days old (needed 2 days)
• r-cran-sjlabelled (1.1.3-1 to 1.1.4-3)
  • Migration status for r-cran-sjlabelled (1.1.3-1 to 1.1.4-3): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-sjlabelled r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sjlabelled.html
  • Should wait for tests relating to r-cran-sjlabelled 1.1.4-3, but forced by ginggs
  • autopkgtest for r-cran-ggeffects/0.14.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjmisc/2.8.4-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, but urgency pushed by ginggs
  • 3 days old
• rasdaemon (0.6.5-1 to 0.6.5-2)
  • Migration status for rasdaemon (0.6.5-1 to 0.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ahs3
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rasdaemon.html
• ruby-github-linguist (7.7.0-2 to 7.9.0-1)
  • Migration status for ruby-github-linguist (7.7.0-2 to 7.9.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/r/ruby-github-linguist.html
• ruby-gollum-lib (4.2.7.8-1 to 4.2.7.9-1)
  • Migration status for ruby-gollum-lib (4.2.7.8-1 to 4.2.7.9-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/r/ruby-gollum-lib.html
• trustedqsl (2.5.3-1 to 2.5.4-1)
  • Migration status for trustedqsl (2.5.3-1 to 2.5.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/t/trustedqsl.html
• uwsgi (2.0.18-11 to 2.0.18+20200523-1)
  • Migration status for uwsgi (2.0.18-11 to 2.0.18+20200523-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
  • Implicit dependency: uwsgi uwsgi-plugin-luajit
  • Implicit dependency: uwsgi uwsgi-plugin-php
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uwsgi.html
• wimlib (1.13.1-1 to 1.13.2-1)
  • Migration status for wimlib (1.13.1-1 to 1.13.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on s390x
  • Too young, only 3 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wimlib.html
• xtide-data (20100529-1 to 20191229-1)
  • Migration status for xtide-data (20100529-1 to 20191229-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/x/xtide-data.html
• ytcc (- to 1.8.1-1.1)
  • Migration status for ytcc (- to 1.8.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/y/ytcc.html
• yubioath-desktop (5.0.3-1 to 5.0.4-1)
  • Migration status for yubioath-desktop (5.0.3-1 to 5.0.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/y/yubioath-desktop.html
• zip4j (2.5.2-1 to 2.6.0-1)
  • Migration status for zip4j (2.5.2-1 to 2.6.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/z/zip4j.html
• zurl (1.11.0-1 to 1.11.0-2)
  • Migration status for zurl (1.11.0-1 to 1.11.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/z/zurl.html
• allegro5 (2:5.2.6.0-1 to 2:5.2.6.0-2)
  • Migration status for allegro5 (2:5.2.6.0-1 to 2:5.2.6.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:
  • Updating allegro5 fixes old bugs: #961355
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/allegro5.html
• array-info (0.16-4 to 0.16-4.1)
  • Migration status for array-info (0.16-4 to 0.16-4.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 array-info fixes old bugs: #959452
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/array-info.html
• austin (1.0.0-1 to 1.0.1-1)
  • Migration status for austin (1.0.0-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for austin/1.0.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/austin.html
• cjson (1.7.10-1.1 to 1.7.13-1)
  • Migration status for cjson (1.7.10-1.1 to 1.7.13-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/cjson.html
• collectd (5.10.0-1 to 5.11.0-3)
  • Migration status for collectd (5.10.0-1 to 5.11.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • missing build on mipsel
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/collectd.html
• ell (0.28-1 to 0.31-1)
  • Migration status for ell (0.28-1 to 0.31-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/ell.html
• embree (3.9.0+dfsg-1 to 3.10.0+dfsg-1)
  • Migration status for embree (3.9.0+dfsg-1 to 3.10.0+dfsg-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/embree.html
• fqterm (0.9.9-3 to 0.9.10-1)
  • Migration status for fqterm (0.9.9-3 to 0.9.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/f/fqterm.html
• g810-led (0.3.9-1 to 0.4.2-1)
  • Migration status for g810-led (0.3.9-1 to 0.4.2-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/g/g810-led.html
• gnome-applets (3.36.2-1 to 3.36.4-1)
  • Migration status for gnome-applets (3.36.2-1 to 3.36.4-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/g/gnome-applets.html
• ipset (6.38-1.2 to 7.6-2)
  • Migration status for ipset (6.38-1.2 to 7.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/i/ipset.html
• jcodings (1.0.53-1 to 1.0.54-1)
  • Migration status for jcodings (1.0.53-1 to 1.0.54-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/j/jcodings.html
• jinja-vanish (- to 0.2~git20160124.8980cb2-1)
  • Migration status for jinja-vanish (- to 0.2~git20160124.8980cb2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by benh, a new source-only upload is needed to allow migration
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jinja-vanish.html
• jruby-joni (2.1.37-1 to 2.1.39-1)
  • Migration status for jruby-joni (2.1.37-1 to 2.1.39-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
  • Build-Depends-Indep: jruby-joni jcodings
  • Depends: jruby-joni jcodings
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby-joni.html
• keepassxc (2.4.3+dfsg.1-1 to 2.5.4+dfsg.1-1)
  • Migration status for keepassxc (2.4.3+dfsg.1-1 to 2.5.4+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/k/keepassxc.html
• knockpy (- to 4.1.0-4)
  • Migration status for knockpy (- 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 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/knockpy.html
• libksba (1.3.5-2 to 1.4.0-2)
  • Migration status for libksba (1.3.5-2 to 1.4.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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libksba.html
• libxc (4.3.4-1 to 4.3.4-2)
  • Migration status for libxc (4.3.4-1 to 4.3.4-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:
  • Updating libxc fixes old bugs: #961383
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxc.html
• libxmlbird (1.2.11-1 to 1.2.11-2)
  • Migration status for libxmlbird (1.2.11-1 to 1.2.11-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/libx/libxmlbird.html
• linux (5.6.7-1 to 5.6.14-1)
  • Migration status for linux (5.6.7-1 to 5.6.14-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
  • Implicit dependency: linux linux-signed-amd64
  • Implicit dependency: linux linux-signed-arm64
  • Implicit dependency: linux linux-signed-i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux.html
• lirc (0.10.1-6.1 to 0.10.1-6.2)
  • Migration status for lirc (0.10.1-6.1 to 0.10.1-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:
  • Updating lirc fixes old bugs: #932779
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lirc.html
• mailnag (- to 2.0.0-0.2)
  • Migration status for mailnag (- to 2.0.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/m/mailnag.html
• mate-optimus (19.10.4-2 to 20.04.0-1)
  • Migration status for mate-optimus (19.10.4-2 to 20.04.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/m/mate-optimus.html
• materia-gtk-theme (20190315-1 to 20200320-0.1)
  • Migration status for materia-gtk-theme (20190315-1 to 20200320-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/m/materia-gtk-theme.html
• mhc (1.2.3-1 to 1.2.3+0.20200403-1)
  • Migration status for mhc (1.2.3-1 to 1.2.3+0.20200403-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/m/mhc.html
• mozc (2.23.2815.102+dfsg-8 to 2.23.2815.102+dfsg-9)
  • Migration status for mozc (2.23.2815.102+dfsg-8 to 2.23.2815.102+dfsg-9): 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/mozc.html
• node-bufferjs (2.0.0-2 to 3.0.1-1)
  • Migration status for node-bufferjs (2.0.0-2 to 3.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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-bufferjs.html
• node-cache-loader (2.0.1-3 to 4.1.0-1)
  • Migration status for node-cache-loader (2.0.1-3 to 4.1.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
  • Build-Depends(-Arch): node-cache-loader node-schema-utils
  • Depends: node-cache-loader node-schema-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-cache-loader.html
• node-schema-utils (1.0.0-2 to 2.6.6-1)
  • Migration status for node-schema-utils (1.0.0-2 to 2.6.6-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-schema-utils.html
• openimageio (2.1.14.0~dfsg0-1 to 2.1.15.0~dfsg0-1)
  • Migration status for openimageio (2.1.14.0~dfsg0-1 to 2.1.15.0~dfsg0-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/openimageio.html
• perl6-zef (0.8.2-1 to 0.8.4-1)
  • Migration status for perl6-zef (0.8.2-1 to 0.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating perl6-zef introduces new bugs: #961486
  • 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/p/perl6-zef.html
• plm (2.6+repack-4 to 2.8-1)
  • Migration status for plm (2.6+repack-4 to 2.8-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/p/plm.html
• qtractor (0.9.13-1 to 0.9.14-1)
  • Migration status for qtractor (0.9.13-1 to 0.9.14-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/q/qtractor.html
• r-bioc-delayedarray (0.12.3+dfsg-1 to 0.14.0+dfsg-2)
  • Migration status for r-bioc-delayedarray (0.12.3+dfsg-1 to 0.14.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-delayedarray r-bioc-s4vectors
  • Depends: r-bioc-delayedarray r-base
  • Depends: r-bioc-delayedarray r-bioc-biocgenerics
  • Depends: r-bioc-delayedarray r-bioc-s4vectors
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-delayedarray.html
  • Required age reduced by 3 days because of autopkgtest
  • 4 days old (needed 2 days)
• r-bioc-interactivedisplaybase (1.24.0+dfsg-1 to 1.26.2+dfsg-1)
  • Migration status for r-bioc-interactivedisplaybase (1.24.0+dfsg-1 to 1.26.2+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-interactivedisplaybase r-base
  • Depends: r-bioc-interactivedisplaybase r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-interactivedisplaybase.html
  • Required age reduced by 3 days because of autopkgtest
  • 4 days old (needed 2 days)
• r-cran-covid19us (0.1.4-1 to 0.1.6-1)
  • Migration status for r-cran-covid19us (0.1.4-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-covid19us r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-covid19us.html
  • Required age reduced by 3 days because of autopkgtest
  • 4 days old (needed 2 days)
• r-cran-effectsize (0.3.0-1 to 0.3.1-1)
  • Migration status for r-cran-effectsize (0.3.0-1 to 0.3.1-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-effectsize r-cran-parameters
  • Depends: r-cran-effectsize r-base
  • Depends: r-cran-effectsize r-cran-insight
  • Depends: r-cran-effectsize r-cran-parameters
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-effectsize.html
  • Should wait for tests relating to r-cran-effectsize 0.3.1-1, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • Too young, but urgency pushed by sramacher
  • 4 days old
• r-cran-maptools (1:0.9-9+dfsg-1 to 1:1.0-1+dfsg-1)
  • Migration status for r-cran-maptools (1:0.9-9+dfsg-1 to 1:1.0-1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maptools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-maptools.html
  • Required age reduced by 3 days because of autopkgtest
  • 4 days old (needed 2 days)
• rust-ring (- to 0.16.9-4)
  • Migration status for rust-ring (- to 0.16.9-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/r/rust-ring.html
• shutdown-at-night (0.22 to 0.23)
  • Migration status for shutdown-at-night (0.22 to 0.23): 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/shutdown-at-night.html
• six (1.14.0-3 to 1.15.0-1)
  • Migration status for six (1.14.0-3 to 1.15.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/s/six.html
  • autopkgtest for dolfin/2019.2.0~git20200218.027d9cc-6: amd64: Pass, arm64: Ignored failure
• stella (6.0.2-1 to 6.1.2-1)
  • Migration status for stella (6.0.2-1 to 6.1.2-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/stella.html
• surgescript (0.5.4-1 to 0.5.4.2-1)
  • Migration status for surgescript (0.5.4-1 to 0.5.4.2-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/surgescript.html
• tnseq-transit (3.0.2-1 to 3.1.0-1)
  • Migration status for tnseq-transit (3.0.2-1 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 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tnseq-transit.html
• ttygif (1.4.0-2 to 1.5.0-1)
  • Migration status for ttygif (1.4.0-2 to 1.5.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/t/ttygif.html
• vg (1.23.0+ds-2 to 1.24.0+ds-1)
  • Migration status for vg (1.23.0+ds-2 to 1.24.0+ds-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/v/vg.html
• vlc-plugin-bittorrent (2.6-1 to 2.9-1)
  • Migration status for vlc-plugin-bittorrent (2.6-1 to 2.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: vlc-plugin-bittorrent libtorrent-rasterbar (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vlc-plugin-bittorrent.html
  • Required age reduced by 3 days because of autopkgtest
  • 4 days old (needed 2 days)
• xine-lib-1.2 (1.2.9-1 to 1.2.10-2)
  • Migration status for xine-lib-1.2 (1.2.9-1 to 1.2.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xine-lib-1.2 introduces new bugs: #961509
  • Too young, only 4 of 5 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xine-lib-1.2.html
• fonts-dejavu (2.37-1 to 2.37-2)
  • Migration status for fonts-dejavu (2.37-1 to 2.37-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • removing ttf-dejavu/2.37-1/amd64 from testing makes wmforkplop/0.9.3-2.1+b3/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes astromenace/1.3.2+repack-6/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes blobandconquer-data/1.11-dfsg+20-1.1/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes blobwars-data/2.00-1/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes castle-game-engine-doc/6.4+dfsg1-3/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes enigma-data/1.20-dfsg.1-2.1/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes frogatto-data/1.3.1+dfsg-1/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes libgazebo-dev/11.0.0+dfsg1-2+b1/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes manaplus-data/1.9.3.23-4/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes natbraille/2.0rc3-8/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes otrs2/6.0.28-1/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes scilab-test/6.1.0+dfsg1-3/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes singularity/1.0b1-2/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes xmoto-data/0.5.11+dfsg-8/amd64 uninstallable
  • removing ttf-dejavu-core/2.37-1/amd64 from testing makes zatacka/0.1.8-5.2/amd64 uninstallable
  • removing ttf-dejavu-extra/2.37-1/amd64 from testing makes enigma-data/1.20-dfsg.1-2.1/amd64 uninstallable
  • removing ttf-dejavu-extra/2.37-1/amd64 from testing makes otrs2/6.0.28-1/amd64 uninstallable
  • removing ttf-dejavu/2.37-1/arm64 from testing makes wmforkplop/0.9.3-2.1+b1/arm64 uninstallable
  • removing ttf-dejavu-core/2.37-1/arm64 from testing makes astromenace/1.3.2+repack-6/arm64 uninstallable
  • removing ttf-dejavu-core/2.37-1/arm64 from testing makes zatacka/0.1.8-5.2/arm64 uninstallable
  • removing ttf-dejavu/2.37-1/armel from testing makes wmforkplop/0.9.3-2.1+b3/armel uninstallable
  • removing ttf-dejavu-core/2.37-1/armel from testing makes astromenace/1.3.2+repack-6/armel uninstallable
  • removing ttf-dejavu-core/2.37-1/armel from testing makes zatacka/0.1.8-5.2/armel uninstallable
  • removing ttf-dejavu/2.37-1/armhf from testing makes wmforkplop/0.9.3-2.1+b3/armhf uninstallable
  • removing ttf-dejavu-core/2.37-1/armhf from testing makes astromenace/1.3.2+repack-6/armhf uninstallable
  • removing ttf-dejavu-core/2.37-1/armhf from testing makes zatacka/0.1.8-5.2/armhf uninstallable
  • removing ttf-dejavu/2.37-1/i386 from testing makes wmforkplop/0.9.3-2.1+b3/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes astromenace/1.3.2+repack-6/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes blobandconquer-data/1.11-dfsg+20-1.1/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes blobwars-data/2.00-1/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes castle-game-engine-doc/6.4+dfsg1-3/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes enigma-data/1.20-dfsg.1-2.1/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes frogatto-data/1.3.1+dfsg-1/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes libgazebo-dev/11.0.0+dfsg1-2+b1/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes manaplus-data/1.9.3.23-4/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes natbraille/2.0rc3-8/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes otrs2/6.0.28-1/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes scilab-test/6.1.0+dfsg1-3/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes singularity/1.0b1-2/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes xmoto-data/0.5.11+dfsg-8/i386 uninstallable
  • removing ttf-dejavu-core/2.37-1/i386 from testing makes zatacka/0.1.8-5.2/i386 uninstallable
  • removing ttf-dejavu-extra/2.37-1/i386 from testing makes enigma-data/1.20-dfsg.1-2.1/i386 uninstallable
  • removing ttf-dejavu-extra/2.37-1/i386 from testing makes otrs2/6.0.28-1/i386 uninstallable
  • removing ttf-dejavu/2.37-1/mips64el from testing makes wmforkplop/0.9.3-2.1+b3/mips64el uninstallable
  • removing ttf-dejavu-core/2.37-1/mips64el from testing makes astromenace/1.3.2+repack-6/mips64el uninstallable
  • removing ttf-dejavu-core/2.37-1/mips64el from testing makes zatacka/0.1.8-5.2/mips64el uninstallable
  • removing ttf-dejavu/2.37-1/mipsel from testing makes wmforkplop/0.9.3-2.1+b3/mipsel uninstallable
  • removing ttf-dejavu-core/2.37-1/mipsel from testing makes astromenace/1.3.2+repack-6/mipsel uninstallable
  • removing ttf-dejavu-core/2.37-1/mipsel from testing makes zatacka/0.1.8-5.2/mipsel uninstallable
  • removing ttf-dejavu/2.37-1/ppc64el from testing makes wmforkplop/0.9.3-2.1+b3/ppc64el uninstallable
  • removing ttf-dejavu-core/2.37-1/ppc64el from testing makes astromenace/1.3.2+repack-6/ppc64el uninstallable
  • removing ttf-dejavu-core/2.37-1/ppc64el from testing makes zatacka/0.1.8-5.2/ppc64el uninstallable
  • removing ttf-dejavu/2.37-1/s390x from testing makes wmforkplop/0.9.3-2.1+b3/s390x uninstallable
  • removing ttf-dejavu-core/2.37-1/s390x from testing makes astromenace/1.3.2+repack-6/s390x uninstallable
  • removing ttf-dejavu-core/2.37-1/s390x from testing makes zatacka/0.1.8-5.2/s390x uninstallable
  • Implicit dependency: fonts-dejavu allegro5
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-dejavu.html
  • 5 days old (needed 5 days)
• imx-usb-loader (0~git20200103.f009770d-1 to 0~git20200517.30b43d69-1)
  • Migration status for imx-usb-loader (0~git20200103.f009770d-1 to 0~git20200517.30b43d69-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/i/imx-usb-loader.html
• libuv1 (1.35.0-2 to 1.38.0-1)
  • Migration status for libuv1 (1.35.0-2 to 1.38.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libuv1/1.38.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libuv1.html
  • 5 days old (needed 5 days)
• odt2txt (0.5-2 to 0.5-3)
  • Migration status for odt2txt (0.5-2 to 0.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for odt2txt/0.5-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odt2txt.html
  • 5 days old (needed 5 days)
• php-horde-service-urlshortener (- to 2.0.3-5)
  • Migration status for php-horde-service-urlshortener (- to 2.0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-service-urlshortener php-horde-exception
  • Depends: php-horde-service-urlshortener php-horde-http
  • Depends: php-horde-service-urlshortener php-horde-url
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-urlshortener.html
  • 5 days old (needed 5 days)
• prboom-plus (2:2.5.1.5+svn4540+dfsg1-2 to 2:2.5.1.7um+git72-1)
  • Migration status for prboom-plus (2:2.5.1.5+svn4540+dfsg1-2 to 2:2.5.1.7um+git72-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating prboom-plus introduces new bugs: #961336
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prboom-plus.html
  • 5 days old (needed 5 days)
• r-bioc-cummerbund (2.28.0-1 to 2.30.0-1)
  • Migration status for r-bioc-cummerbund (2.28.0-1 to 2.30.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-cummerbund r-base
  • Depends: r-bioc-cummerbund r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-cummerbund.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-bioc-qusage (2.20.0-1 to 2.22.0-1)
  • Migration status for r-bioc-qusage (2.20.0-1 to 2.22.0-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-qusage r-cran-fftw
  • Depends: r-bioc-qusage r-base
  • Depends: r-bioc-qusage r-bioc-biocgenerics
  • Depends: r-bioc-qusage r-cran-fftw
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-qusage.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-alakazam (1.0.0-1 to 1.0.1-1)
  • Migration status for r-cran-alakazam (1.0.0-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-alakazam r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-alakazam.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-backports (1.1.6-1 to 1.1.7-1)
  • Migration status for r-cran-backports (1.1.6-1 to 1.1.7-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-backports r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-backports.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-diffobj (0.2.4-1 to 0.3.0-1)
  • Migration status for r-cran-diffobj (0.2.4-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diffobj r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-diffobj.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-fftw (- to 1.0-6-2)
  • Migration status for r-cran-fftw (- to 1.0-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fftw r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fftw.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-fitdistrplus (1.0-14-3 to 1.1-1-1)
  • Migration status for r-cran-fitdistrplus (1.0-14-3 to 1.1-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fitdistrplus r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fitdistrplus.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-ggraph (2.0.2-1 to 2.0.3-1)
  • Migration status for r-cran-ggraph (2.0.2-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggraph r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggraph.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-glmnet (3.0-2-1 to 4.0-1)
  • Migration status for r-cran-glmnet (3.0-2-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-glmnet r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-glmnet.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-glue (1.4.0-1 to 1.4.1-1)
  • Migration status for r-cran-glue (1.4.0-1 to 1.4.1-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-glue r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-glue.html
  • Should wait for tests relating to r-cran-glue 1.4.1-1, but forced by ginggs
  • autopkgtest for r-cran-vctrs/0.2.4-1: amd64: Regression ♻ , arm64: Regression ♻
  • 5 days old (needed 5 days)
• r-cran-gwidgetsrgtk2 (0.0-86-2 to 0.0-86.1-1)
  • Migration status for r-cran-gwidgetsrgtk2 (0.0-86-2 to 0.0-86.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gwidgetsrgtk2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gwidgetsrgtk2.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-jomo (2.6-10-1 to 2.7-1-1)
  • Migration status for r-cran-jomo (2.6-10-1 to 2.7-1-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-jomo r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-jomo.html
  • Should wait for tests relating to r-cran-jomo 2.7-1-1, but forced by ginggs
  • autopkgtest for r-cran-mice/3.8.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • 5 days old (needed 5 days)
• r-cran-parameters (0.6.1-1 to 0.7.0-1)
  • Migration status for r-cran-parameters (0.6.1-1 to 0.7.0-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-parameters r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-parameters.html
  • Should wait for tests relating to r-cran-parameters 0.7.0-1, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 5 days old (needed 5 days)
• r-cran-rsvg (1.3-2 to 2.1-1)
  • Migration status for r-cran-rsvg (1.3-2 to 2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsvg r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rsvg.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-sem (3.1.9-2 to 3.1.11-1)
  • Migration status for r-cran-sem (3.1.9-2 to 3.1.11-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sem r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sem.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-spatstat (1.63-3-1 to 1.64-1-1)
  • Migration status for r-cran-spatstat (1.63-3-1 to 1.64-1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-spc (1:0.6.3-1 to 1:0.6.4-1)
  • Migration status for r-cran-spc (1:0.6.3-1 to 1:0.6.4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spc.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-systemfonts (0.2.1-1 to 0.2.2-1)
  • Migration status for r-cran-systemfonts (0.2.1-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-systemfonts r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-systemfonts.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-tidygraph (1.1.2-2 to 1.2.0-1)
  • Migration status for r-cran-tidygraph (1.1.2-2 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidygraph r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tidygraph.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-tidyselect (1.0.0+dfsg-1 to 1.1.0+dfsg-1)
  • Migration status for r-cran-tidyselect (1.0.0+dfsg-1 to 1.1.0+dfsg-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-tidyselect r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tidyselect.html
  • Should wait for tests relating to r-cran-tidyselect 1.1.0+dfsg-1, but forced by ginggs
  • autopkgtest for r-cran-sjmisc/2.8.4-1: amd64: Regression ♻ , arm64: Regression ♻
  • 5 days old (needed 5 days)
• r-cran-tinytex (0.22-1 to 0.23-1)
  • Migration status for r-cran-tinytex (0.22-1 to 0.23-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tinytex r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tinytex.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• r-cran-xslt (1.4.1-1 to 1.4.2-1)
  • Migration status for r-cran-xslt (1.4.1-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xslt r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-xslt.html
  • Required age reduced by 3 days because of autopkgtest
  • 5 days old (needed 2 days)
• rumur (2020.02.17-1 to 2020.05.18-1)
  • Migration status for rumur (2020.02.17-1 to 2020.05.18-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on arm64
  • missing build on mips64el
  • missing build on mipsel
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rumur.html
  • 5 days old (needed 5 days)
• astropy-helpers (4.0-1 to 4.0.1-1)
  • Migration status for astropy-helpers (4.0-1 to 4.0.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 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astropy-helpers.html
• breezy (3.0.2-5 to 3.1~alpha1-1)
  • Migration status for breezy (3.0.2-5 to 3.1~alpha1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for breezy-loom/3.0.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breezy.html
  • 6 days old (needed 5 days)
• car (3.0-7-1 to 3.0-8-1)
  • Migration status for car (3.0-7-1 to 3.0-8-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): car r-base
  • Depends: car r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/car.html
  • 6 days old (needed 5 days)
• hexter (1.1.0-4 to 1.1.0-6)
  • Migration status for hexter (1.1.0-4 to 1.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hexter introduces new bugs: #960407
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hexter.html
  • 6 days old (needed 5 days)
• httping (2.5-5 to 2.5-5.1)
  • Migration status for httping (2.5-5 to 2.5-5.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:
  • Updating httping fixes old bugs: #955535
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/httping.html
  • Required age reduced by 3 days because of autopkgtest
• liquidsoap (1.4.1-1 to 1.4.2-1)
  • Migration status for liquidsoap (1.4.1-1 to 1.4.2-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/l/liquidsoap.html
• mesa (19.3.3-1 to 20.0.7-1)
  • Migration status for mesa (19.3.3-1 to 20.0.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): mesa glslang (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mesa.html
  • 6 days old (needed 5 days)
• publicsuffix (20200201.2258-1 to 20200506.1625-1)
  • Migration status for publicsuffix (20200201.2258-1 to 20200506.1625-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • publicsuffix unsatisfiable Build-Depends(-Arch) on amd64: psl-make-dafsa
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/publicsuffix.html
  • 6 days old (needed 5 days)
• pytest-doctestplus (0.6.1-1 to 0.7.0-1)
  • Migration status for pytest-doctestplus (0.6.1-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 6 of 7 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-doctestplus.html
  • Required age reduced by 3 days because of autopkgtest
• python-casacore (3.3.0-2 to 3.3.1-1)
  • Migration status for python-casacore (3.3.0-2 to 3.3.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 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-casacore.html
• r-bioc-biovizbase (1.34.1-2 to 1.36.0-1)
  • Migration status for r-bioc-biovizbase (1.34.1-2 to 1.36.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-biovizbase r-base
  • Depends: r-bioc-biovizbase r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biovizbase.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• r-bioc-goseq (1.38.0-2 to 1.40.0-1)
  • Migration status for r-bioc-goseq (1.38.0-2 to 1.40.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-goseq r-base
  • Depends: r-bioc-goseq r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-goseq.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• r-bioc-mofa (1.2.0+dfsg-2 to 1.4.0+dfsg-1)
  • Migration status for r-bioc-mofa (1.2.0+dfsg-2 to 1.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-mofa r-base
  • Depends: r-bioc-mofa r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-mofa.html
  • 6 days old (needed 5 days)
• r-bioc-rgsepd (1.18.0-2 to 1.20.0-1)
  • Migration status for r-bioc-rgsepd (1.18.0-2 to 1.20.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-rgsepd r-base
  • Depends: r-bioc-rgsepd r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rgsepd.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• r-bioc-s4vectors (0.24.4-1 to 0.26.1-1)
  • Migration status for r-bioc-s4vectors (0.24.4-1 to 0.26.1-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-bioc-s4vectors r-base
  • Depends: r-bioc-s4vectors r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-s4vectors.html
  • Should wait for tests relating to r-bioc-s4vectors 0.26.1-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-bioc-multiassayexperiment/1.12.6+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • 6 days old (needed 5 days)
• r-bioc-tcgabiolinks (- to 2.16.0+dfsg-1)
  • Migration status for r-bioc-tcgabiolinks (- to 2.16.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-tcgabiolinks r-bioc-sva
  • Depends: r-bioc-tcgabiolinks r-base
  • Depends: r-bioc-tcgabiolinks r-bioc-biocgenerics
  • Depends: r-bioc-tcgabiolinks r-bioc-sva
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tcgabiolinks.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• r-cran-adegenet (2.1.2-1 to 2.1.3-1)
  • Migration status for r-cran-adegenet (2.1.2-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adegenet r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-adegenet.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• r-cran-gss (2.2-0-1 to 2.2-1-1)
  • Migration status for r-cran-gss (2.2-0-1 to 2.2-1-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-gss r-base
  • Depends: r-cran-gss r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gss.html
  • 6 days old (needed 5 days)
• r-cran-lwgeom (0.2-3-1 to 0.2-4-1)
  • Migration status for r-cran-lwgeom (0.2-3-1 to 0.2-4-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lwgeom r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lwgeom.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• r-cran-treescape (1.10.18+dfsg-1 to 1.10.18+dfsg-2)
  • Migration status for r-cran-treescape (1.10.18+dfsg-1 to 1.10.18+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-treescape r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-treescape.html
  • Required age reduced by 3 days because of autopkgtest
  • 6 days old (needed 2 days)
• rpy2 (3.3.2-1 to 3.3.3-1)
  • Migration status for rpy2 (3.3.2-1 to 3.3.3-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): rpy2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rpy2.html
  • 6 days old (needed 5 days)
• slic3r-prusa (2.1.1+dfsg-2 to 2.2.0+dfsg1-2)
  • Migration status for slic3r-prusa (2.1.1+dfsg-2 to 2.2.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating slic3r-prusa introduces new bugs: #961373
  • missing build on armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r-prusa.html
  • 6 days old (needed 5 days)
• sphinx-astropy (1.2-3 to 1.3-1)
  • Migration status for sphinx-astropy (1.2-3 to 1.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/s/sphinx-astropy.html
  • Required age reduced by 3 days because of autopkgtest
• apertium-eng-cat (1.0.1-2 to 1.0.1-3)
  • Migration status for apertium-eng-cat (1.0.1-2 to 1.0.1-3): 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/a/apertium-eng-cat.html
• apertium-oci-fra (0.3.0-2 to 0.3.0-3)
  • Migration status for apertium-oci-fra (0.3.0-2 to 0.3.0-3): 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/a/apertium-oci-fra.html
• iptables-netflow (2.4-2 to 2.5-2)
  • Migration status for iptables-netflow (2.4-2 to 2.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/i/iptables-netflow.html
  • Additional info:
  • 7 days old (needed 5 days)
• its (1.1.8-7 to 1.1.8-8)
  • Migration status for its (1.1.8-7 to 1.1.8-8): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): its r-base
  • Depends: its r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/its.html
  • 7 days old (needed 5 days)
• libgraphics-colornames-perl (2.11-7.1 to 3.5.0-3)
  • Migration status for libgraphics-colornames-perl (2.11-7.1 to 3.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libcolor-calc-perl/1.074-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgraphics-colornames-perl.html
  • 7 days old (needed 5 days)
• make-dfsg (4.2.1-2 to 4.3-1)
  • Migration status for make-dfsg (4.2.1-2 to 4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for cross-toolchain-base/45: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for dpkg/1.19.7: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/make-dfsg.html
  • 7 days old (needed 5 days)
• mercurial (5.3.2-1 to 5.4-1)
  • Migration status for mercurial (5.3.2-1 to 5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mercurial introduces new bugs: #961245
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mercurial.html
  • 7 days old (needed 5 days)
• r-bioc-bsgenome (1.54.0-1 to 1.56.0-1)
  • Migration status for r-bioc-bsgenome (1.54.0-1 to 1.56.0-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-genomeinfodb
  • Depends: r-bioc-bsgenome r-base
  • Depends: r-bioc-bsgenome r-bioc-biocgenerics
  • Depends: r-bioc-bsgenome r-bioc-genomeinfodb
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-bsgenome.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-cner (1.22.0+dfsg-2 to 1.24.0+dfsg-1)
  • Migration status for r-bioc-cner (1.22.0+dfsg-2 to 1.24.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-cner r-base
  • Depends: r-bioc-cner r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-cner.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-dada2 (1.14.1+dfsg-1 to 1.16.0+dfsg-1)
  • Migration status for r-bioc-dada2 (1.14.1+dfsg-1 to 1.16.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-dada2 r-base
  • Depends: r-bioc-dada2 r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dada2.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-deseq (1.38.0-2 to 1.39.0-2)
  • Migration status for r-bioc-deseq (1.38.0-2 to 1.39.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-deseq r-base
  • Depends: r-bioc-deseq r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-deseq.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-deseq2 (1.26.0+dfsg-2 to 1.28.1+dfsg-1)
  • Migration status for r-bioc-deseq2 (1.26.0+dfsg-2 to 1.28.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-deseq2 r-base
  • Depends: r-bioc-deseq2 r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-deseq2.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-edaseq (2.20.0+dfsg-2 to 2.22.0+dfsg-1)
  • Migration status for r-bioc-edaseq (2.20.0+dfsg-2 to 2.22.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-edaseq r-base
  • Depends: r-bioc-edaseq r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-edaseq.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-ensembldb (2.10.2+dfsg-2 to 2.12.1+dfsg-1)
  • Migration status for r-bioc-ensembldb (2.10.2+dfsg-2 to 2.12.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-ensembldb r-base
  • Depends: r-bioc-ensembldb r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ensembldb.html
  • 7 days old (needed 5 days)
• r-bioc-fmcsr (- to 1.30.0+dfsg-1)
  • Migration status for r-bioc-fmcsr (- to 1.30.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-fmcsr r-bioc-chemminer
  • Depends: r-bioc-fmcsr r-base
  • Depends: r-bioc-fmcsr r-bioc-biocgenerics
  • Depends: r-bioc-fmcsr r-bioc-chemminer
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-fmcsr.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-genelendatabase (1.22.0-2 to 1.24.0-1)
  • Migration status for r-bioc-genelendatabase (1.22.0-2 to 1.24.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-genelendatabase r-base
  • Depends: r-bioc-genelendatabase r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genelendatabase.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-genomicfeatures (1.38.2+dfsg-2 to 1.40.0+dfsg-1)
  • Migration status for r-bioc-genomicfeatures (1.38.2+dfsg-2 to 1.40.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-genomeinfodb
  • Depends: r-bioc-genomicfeatures r-base
  • Depends: r-bioc-genomicfeatures r-bioc-biocgenerics
  • Depends: r-bioc-genomicfeatures r-bioc-genomeinfodb
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomicfeatures.html
  • 7 days old (needed 5 days)
• r-bioc-htsfilter (1.26.0-2 to 1.28.0-1)
  • Migration status for r-bioc-htsfilter (1.26.0-2 to 1.28.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-htsfilter r-base
  • Depends: r-bioc-htsfilter r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-htsfilter.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-sva (- to 3.36.0-1)
  • Migration status for r-bioc-sva (- to 3.36.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-sva r-base
  • Depends: r-bioc-sva r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-sva.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-tfbstools (1.24.0+dfsg-2 to 1.26.0+dfsg-1)
  • Migration status for r-bioc-tfbstools (1.24.0+dfsg-2 to 1.26.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-tfbstools r-base
  • Depends: r-bioc-tfbstools r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tfbstools.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-bioc-variantannotation (1.32.0-1 to 1.34.0-1)
  • Migration status for r-bioc-variantannotation (1.32.0-1 to 1.34.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-variantannotation r-base
  • Depends: r-bioc-variantannotation r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-variantannotation.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-aer (1.2-9-1 to 1.2-9-2)
  • Migration status for r-cran-aer (1.2-9-1 to 1.2-9-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-aer r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-aer.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-afex (0.27-2-1 to 0.27-2-2)
  • Migration status for r-cran-afex (0.27-2-1 to 0.27-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-afex r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-afex.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-brms (2.12.0-1 to 2.12.0-2)
  • Migration status for r-cran-brms (2.12.0-1 to 2.12.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brms r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-brms.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-dendextend (1.13.4+dfsg-1 to 1.13.4+dfsg-2)
  • Migration status for r-cran-dendextend (1.13.4+dfsg-1 to 1.13.4+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dendextend r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dendextend.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-dynlm (0.3.6-1 to 0.3.6-2)
  • Migration status for r-cran-dynlm (0.3.6-1 to 0.3.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dynlm r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dynlm.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-factominer (2.3-1 to 2.3-2)
  • Migration status for r-cran-factominer (2.3-1 to 2.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-factominer r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-factominer.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-heatmaply (1.1.0+dfsg-1 to 1.1.0+dfsg-2)
  • Migration status for r-cran-heatmaply (1.1.0+dfsg-1 to 1.1.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-heatmaply r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-heatmaply.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-rcmdrmisc (2.7-0-2 to 2.7-0-3)
  • Migration status for r-cran-rcmdrmisc (2.7-0-2 to 2.7-0-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-rcmdrmisc r-base
  • Depends: r-cran-rcmdrmisc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rcmdrmisc.html
  • 7 days old (needed 5 days)
• r-cran-semplot (1.1.2-2 to 1.1.2-3)
  • Migration status for r-cran-semplot (1.1.2-2 to 1.1.2-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-semplot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-semplot.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-shazam (0.2.3-1 to 1.0.0-1)
  • Migration status for r-cran-shazam (0.2.3-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shazam r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shazam.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-shinystan (2.5.0-2 to 2.5.0-3)
  • Migration status for r-cran-shinystan (2.5.0-2 to 2.5.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shinystan r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shinystan.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-sjstats (0.18.0-1 to 0.18.0-2)
  • Migration status for r-cran-sjstats (0.18.0-1 to 0.18.0-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-sjstats r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sjstats.html
  • Should wait for tests relating to r-cran-sjstats 0.18.0-2, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 7 days old (needed 5 days)
• r-cran-survminer (0.4.6+dfsg-2 to 0.4.6+dfsg-3)
  • Migration status for r-cran-survminer (0.4.6+dfsg-2 to 0.4.6+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-survminer r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-survminer.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-systemfit (1.1-24-1 to 1.1-24-2)
  • Migration status for r-cran-systemfit (1.1-24-1 to 1.1-24-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-systemfit r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-systemfit.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-tidyverse (1.3.0-1 to 1.3.0-2)
  • Migration status for r-cran-tidyverse (1.3.0-1 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tidyverse r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tidyverse.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-tigger (0.4.0-1 to 1.0.0-1)
  • Migration status for r-cran-tigger (0.4.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-tigger r-cran-shazam
  • Depends: r-cran-tigger r-base
  • Depends: r-cran-tigger r-cran-shazam
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tigger.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-whatif (1.5-9-2 to 1.5-9-3)
  • Migration status for r-cran-whatif (1.5-9-2 to 1.5-9-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-whatif r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-whatif.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-zelig (5.1.6.1-1 to 5.1.6.1-2)
  • Migration status for r-cran-zelig (5.1.6.1-1 to 5.1.6.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zelig r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-zelig.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-zeligchoice (0.9-6-2 to 0.9-6-3)
  • Migration status for r-cran-zeligchoice (0.9-6-2 to 0.9-6-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zeligchoice r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-zeligchoice.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-zeligei (0.1-2-2 to 0.1-2-3)
  • Migration status for r-cran-zeligei (0.1-2-2 to 0.1-2-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zeligei r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-zeligei.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• r-cran-zeligverse (0.1.1-2 to 0.1.1-3)
  • Migration status for r-cran-zeligverse (0.1.1-2 to 0.1.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zeligverse r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-zeligverse.html
  • Required age reduced by 3 days because of autopkgtest
  • 7 days old (needed 2 days)
• rcmdr (2.6-2-1 to 2.6-2-2)
  • Migration status for rcmdr (2.6-2-1 to 2.6-2-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): rcmdr r-base
  • Depends: rcmdr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rcmdr.html
  • 7 days old (needed 5 days)
• v4l-utils (1.18.1-1 to 1.20.0-1)
  • Migration status for v4l-utils (1.18.1-1 to 1.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by gjasny@googlemail.com
  • Not built on buildd: arch all binaries uploaded by gjasny@googlemail.com, a new source-only upload is needed to allow migration
  • Too young, only 7 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/v4l-utils.html
• comet-ms (2018012-1 to 2019015+cleaned1-2)
  • Migration status for comet-ms (2018012-1 to 2019015+cleaned1-2): 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/c/comet-ms.html
• cruft-ng (0.4.7 to 0.4.8)
  • Migration status for cruft-ng (0.4.7 to 0.4.8): 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/c/cruft-ng.html
• libmsnumpress (- to 1.0.0-7)
  • Migration status for libmsnumpress (- to 1.0.0-7): 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/libm/libmsnumpress.html
• libwildmagic (5.13-1.1 to 5.17+cleaned1-4)
  • Migration status for libwildmagic (5.13-1.1 to 5.17+cleaned1-4): 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/libw/libwildmagic.html
• pmount (0.9.23-3 to 0.9.23-4)
  • Migration status for pmount (0.9.23-3 to 0.9.23-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pmount introduces new bugs: #961705
  • autopkgtest for pmount/0.9.23-4: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmount.html
  • 8 days old (needed 5 days)
• python-matrix-nio (- to 0.11.2-2)
  • Migration status for python-matrix-nio (- to 0.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python-matrix-nio/0.11.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-matrix-nio.html
  • 8 days old (needed 5 days)
• r-bioc-annotationhub (2.18.0+dfsg-2 to 2.20.0+dfsg-1)
  • Migration status for r-bioc-annotationhub (2.18.0+dfsg-2 to 2.20.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-annotationhub r-base
  • Depends: r-bioc-annotationhub r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-annotationhub.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-biocfilecache (1.10.2+dfsg-1 to 1.12.0+dfsg-1)
  • Migration status for r-bioc-biocfilecache (1.10.2+dfsg-1 to 1.12.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-biocfilecache r-base
  • Depends: r-bioc-biocfilecache r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biocfilecache.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-biomart (2.42.1+dfsg-1 to 2.44.0+dfsg-1)
  • Migration status for r-bioc-biomart (2.42.1+dfsg-1 to 2.44.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-biomart r-base
  • Depends: r-bioc-biomart r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biomart.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-bitseq (1.30.1+dfsg-1 to 1.32.0+dfsg-1)
  • Migration status for r-bioc-bitseq (1.30.1+dfsg-1 to 1.32.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-bitseq r-base
  • Depends: r-bioc-bitseq r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-bitseq.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-demixt (- to 1.4.0-1)
  • Migration status for r-bioc-demixt (- to 1.4.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-demixt r-base
  • Depends: r-bioc-demixt r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-demixt.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-genefilter (1.68.0-2 to 1.70.0-1)
  • Migration status for r-bioc-genefilter (1.68.0-2 to 1.70.0-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-bioc-genefilter r-base
  • Depends: r-bioc-genefilter r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genefilter.html
  • Should wait for tests relating to r-bioc-genefilter 1.70.0-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • 8 days old (needed 5 days)
• r-bioc-geneplotter (1.64.0-1 to 1.66.0-1)
  • Migration status for r-bioc-geneplotter (1.64.0-1 to 1.66.0-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-bioc-geneplotter r-base
  • Depends: r-bioc-geneplotter r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-geneplotter.html
  • Should wait for tests relating to r-bioc-geneplotter 1.66.0-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • 8 days old (needed 5 days)
• r-bioc-genomicalignments (1.22.1-1 to 1.24.0-1)
  • Migration status for r-bioc-genomicalignments (1.22.1-1 to 1.24.0-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-genomicalignments r-bioc-biostrings
  • Depends: r-bioc-genomicalignments r-base
  • Depends: r-bioc-genomicalignments r-bioc-biocgenerics
  • Depends: r-bioc-genomicalignments r-bioc-biostrings
  • Depends: r-bioc-genomicalignments r-bioc-genomicranges
  • Depends: r-bioc-genomicalignments r-bioc-iranges
  • Depends: r-bioc-genomicalignments r-bioc-s4vectors
  • 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
  • 8 days old (needed 2 days)
• r-bioc-geoquery (2.54.1+dfsg-2 to 2.56.0+dfsg-1)
  • Migration status for r-bioc-geoquery (2.54.1+dfsg-2 to 2.56.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-geoquery r-base
  • Depends: r-bioc-geoquery r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-geoquery.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-gosemsim (2.12.1-2 to 2.14.0-1)
  • Migration status for r-bioc-gosemsim (2.12.1-2 to 2.14.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-gosemsim r-base
  • Depends: r-bioc-gosemsim r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-gosemsim.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-multiassayexperiment (1.12.6+dfsg-1 to 1.14.0+dfsg-1)
  • Migration status for r-bioc-multiassayexperiment (1.12.6+dfsg-1 to 1.14.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-multiassayexperiment r-base
  • Depends: r-bioc-multiassayexperiment r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-multiassayexperiment.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-nanostringqcpro (1.18.0-2 to 1.20.0-1)
  • Migration status for r-bioc-nanostringqcpro (1.18.0-2 to 1.20.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-nanostringqcpro r-base
  • Depends: r-bioc-nanostringqcpro r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-nanostringqcpro.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-phyloseq (1.30.0+dfsg-1 to 1.32.0+dfsg-1)
  • Migration status for r-bioc-phyloseq (1.30.0+dfsg-1 to 1.32.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-phyloseq r-base
  • Depends: r-bioc-phyloseq r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-phyloseq.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-qvalue (2.18.0-1 to 2.20.0-1)
  • Migration status for r-bioc-qvalue (2.18.0-1 to 2.20.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-qvalue r-base
  • Depends: r-bioc-qvalue r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-qvalue.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-rtracklayer (1.46.0-2 to 1.48.0-1)
  • Migration status for r-bioc-rtracklayer (1.46.0-2 to 1.48.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-rtracklayer r-base
  • Depends: r-bioc-rtracklayer r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rtracklayer.html
  • 8 days old (needed 5 days)
• r-bioc-savr (1.24.0-1 to 1.26.0-1)
  • Migration status for r-bioc-savr (1.24.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-savr r-base
  • Depends: r-bioc-savr r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-savr.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-bioc-shortread (1.44.3-1 to 1.46.0-1)
  • Migration status for r-bioc-shortread (1.44.3-1 to 1.46.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-shortread r-base
  • Depends: r-bioc-shortread r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-shortread.html
  • 8 days old (needed 5 days)
• r-cran-av (- to 0.5.0+dfsg-3)
  • Migration status for r-cran-av (- to 0.5.0+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-av r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-av.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-bayesplot (1.7.1-2 to 1.7.1-3)
  • Migration status for r-cran-bayesplot (1.7.1-2 to 1.7.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bayesplot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bayesplot.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-colourpicker (1.0+dfsg-2 to 1.0+dfsg-3)
  • Migration status for r-cran-colourpicker (1.0+dfsg-2 to 1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-colourpicker r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-colourpicker.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-cowplot (1.0.0+dfsg-2 to 1.0.0+dfsg-3)
  • Migration status for r-cran-cowplot (1.0.0+dfsg-2 to 1.0.0+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cowplot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cowplot.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-egg (0.4.5-2 to 0.4.5-3)
  • Migration status for r-cran-egg (0.4.5-2 to 0.4.5-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-egg r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-egg.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-fitcoach (1.0-3 to 1.0-4)
  • Migration status for r-cran-fitcoach (1.0-3 to 1.0-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fitcoach r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fitcoach.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ggally (1.5.0-1 to 1.5.0-2)
  • Migration status for r-cran-ggally (1.5.0-1 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggally r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggally.html
  • 8 days old (needed 5 days)
• r-cran-gganimate (- to 1.0.5-3)
  • Migration status for r-cran-gganimate (- to 1.0.5-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gganimate r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gganimate.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ggbeeswarm (0.6.0-2 to 0.6.0-3)
  • Migration status for r-cran-ggbeeswarm (0.6.0-2 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggbeeswarm r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggbeeswarm.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ggdendro (0.1-20+dfsg-2 to 0.1-20+dfsg-3)
  • Migration status for r-cran-ggdendro (0.1-20+dfsg-2 to 0.1-20+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggdendro r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggdendro.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ggpubr (0.2.5-2 to 0.2.5-3)
  • Migration status for r-cran-ggpubr (0.2.5-2 to 0.2.5-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggpubr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggpubr.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ggridges (0.5.2-1 to 0.5.2-2)
  • Migration status for r-cran-ggridges (0.5.2-1 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggridges r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggridges.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ggsci (2.9-2 to 2.9-3)
  • Migration status for r-cran-ggsci (2.9-2 to 2.9-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggsci r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggsci.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ggsignif (0.6.0-2 to 0.6.0-3)
  • Migration status for r-cran-ggsignif (0.6.0-2 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggsignif r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggsignif.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ggthemes (4.2.0-1 to 4.2.0-2)
  • Migration status for r-cran-ggthemes (4.2.0-1 to 4.2.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggthemes r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggthemes.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-htmltable (1.13.3-1 to 1.13.3-2)
  • Migration status for r-cran-htmltable (1.13.3-1 to 1.13.3-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-htmltable r-base
  • Depends: r-cran-htmltable r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-htmltable.html
  • 8 days old (needed 5 days)
• r-cran-htmltools (0.4.0-1 to 0.4.0-2)
  • Migration status for r-cran-htmltools (0.4.0-1 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-htmltools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-htmltools.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-kaos (0.1.2-1 to 0.1.2-2)
  • Migration status for r-cran-kaos (0.1.2-1 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kaos r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-kaos.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-lmertest (3.1-2-1 to 3.1-2-2)
  • Migration status for r-cran-lmertest (3.1-2-1 to 3.1-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lmertest r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lmertest.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-manipulatewidgets (0.9.0-2 to 0.9.0-3)
  • Migration status for r-cran-manipulatewidgets (0.9.0-2 to 0.9.0-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-manipulatewidgets r-base
  • Depends: r-cran-manipulatewidgets r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-manipulatewidgets.html
  • 8 days old (needed 5 days)
• r-cran-mertools (0.5.0-1 to 0.5.0-2)
  • Migration status for r-cran-mertools (0.5.0-1 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mertools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mertools.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-mitml (0.3-7-2 to 0.3-7-3)
  • Migration status for r-cran-mitml (0.3-7-2 to 0.3-7-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mitml r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mitml.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-modelr (0.1.7-1 to 0.1.8-1)
  • Migration status for r-cran-modelr (0.1.7-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modelr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-modelr.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-multidimbio (1.2.2-1 to 1.2.2-2)
  • Migration status for r-cran-multidimbio (1.2.2-1 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multidimbio r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-multidimbio.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ncdfgeom (1.1.0-2 to 1.1.0-3)
  • Migration status for r-cran-ncdfgeom (1.1.0-2 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncdfgeom r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ncdfgeom.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-ncmeta (0.2.0-1 to 0.2.5-1)
  • Migration status for r-cran-ncmeta (0.2.0-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ncmeta r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ncmeta.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-patchwork (1.0.0-2 to 1.0.0-4)
  • Migration status for r-cran-patchwork (1.0.0-2 to 1.0.0-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-patchwork r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-patchwork.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-plotly (4.9.2.1+dfsg-1 to 4.9.2.1+dfsg-2)
  • Migration status for r-cran-plotly (4.9.2.1+dfsg-1 to 4.9.2.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-plotly r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-plotly.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-purrrogress (0.1.1-2 to 0.1.1-3)
  • Migration status for r-cran-purrrogress (0.1.1-2 to 0.1.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-purrrogress r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-purrrogress.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-rdflib (0.2.3+dfsg-1 to 0.2.3+dfsg-2)
  • Migration status for r-cran-rdflib (0.2.3+dfsg-1 to 0.2.3+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rdflib r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rdflib.html
  • 8 days old (needed 5 days)
• r-cran-recipes (0.1.12+dfsg-1 to 0.1.12+dfsg-2)
  • Migration status for r-cran-recipes (0.1.12+dfsg-1 to 0.1.12+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-recipes r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-recipes.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-rglwidget (0.2.1-3 to 0.2.1-4)
  • Migration status for r-cran-rglwidget (0.2.1-3 to 0.2.1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rglwidget r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rglwidget.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-rio (0.5.16-1 to 0.5.16-2)
  • Migration status for r-cran-rio (0.5.16-1 to 0.5.16-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-rio r-base
  • Depends: r-cran-rio r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rio.html
  • 8 days old (needed 5 days)
• r-cran-ritis (0.9.0+dfsg-1 to 0.9.0+dfsg-2)
  • Migration status for r-cran-ritis (0.9.0+dfsg-1 to 0.9.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ritis r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ritis.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-rlumshiny (0.2.2-1 to 0.2.2-2)
  • Migration status for r-cran-rlumshiny (0.2.2-1 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlumshiny r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rlumshiny.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-rnexml (2.4.4+ds-1 to 2.4.4+ds-2)
  • Migration status for r-cran-rnexml (2.4.4+ds-1 to 2.4.4+ds-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rnexml r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rnexml.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-rsample (0.0.6-1 to 0.0.6-2)
  • Migration status for r-cran-rsample (0.0.6-1 to 0.0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsample r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rsample.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-sna (- to 2.5-2)
  • Migration status for r-cran-sna (- to 2.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • r-cran-sna/amd64 has unsatisfiable dependency
  • r-cran-sna unsatisfiable Build-Depends(-Arch) on amd64: r-cran-statnet.common
  • r-cran-sna unsatisfiable Build-Depends(-Arch) on amd64: r-cran-network
  • Not built on buildd: arch amd64 binaries uploaded by tille
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/r-cran-sna.html
  • uninstallable on arch amd64, not running autopkgtest there
  • 8 days old (needed 5 days)
• r-cran-survmisc (0.5.5-2 to 0.5.5-3)
  • Migration status for r-cran-survmisc (0.5.5-2 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-survmisc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-survmisc.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-taxize (0.9.95+dfsg-1 to 0.9.96+dfsg-1)
  • Migration status for r-cran-taxize (0.9.95+dfsg-1 to 0.9.96+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-taxize r-cran-natserv
  • Depends: r-cran-taxize r-base
  • Depends: r-cran-taxize r-cran-natserv
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-taxize.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-tinytest (1.2.0-1 to 1.2.1-1)
  • Migration status for r-cran-tinytest (1.2.0-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tinytest r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tinytest.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• r-cran-viridis (0.5.1-2 to 0.5.1-3)
  • Migration status for r-cran-viridis (0.5.1-2 to 0.5.1-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-viridis r-base
  • Depends: r-cran-viridis r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-viridis.html
  • 8 days old (needed 5 days)
• ruby-eventmachine (1.0.7-4.2 to 1.3~pre20190820-g10fb0c4-2)
  • Migration status for ruby-eventmachine (1.0.7-4.2 to 1.3~pre20190820-g10fb0c4-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/r/ruby-eventmachine.html
  • Required age reduced by 3 days because of autopkgtest
  • 8 days old (needed 2 days)
• tpm2-tss (2.4.0-1 to 2.4.1-1)
  • Migration status for tpm2-tss (2.4.0-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 8 of 10 days old
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-tss.html
• wesnoth-1.14 (- to 1:1.14.12-1)
  • Migration status for wesnoth-1.14 (- to 1:1.14.12-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
  • Not built on buildd: arch amd64 binaries uploaded by rhonda
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wesnoth-1.14.html
  • 8 days old (needed 5 days)
• apertium-dan-nor (1.4.1-1 to 1.4.1-2)
  • Migration status for apertium-dan-nor (1.4.1-1 to 1.4.1-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/a/apertium-dan-nor.html
• effects (4.1.4-1 to 4.1.4-2)
  • Migration status for effects (4.1.4-1 to 4.1.4-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): effects r-base
  • Depends: effects r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/effects.html
  • 9 days old (needed 5 days)
• fexoticoptions (3042.80-2 to 3042.80-3)
  • Migration status for fexoticoptions (3042.80-2 to 3042.80-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): fexoticoptions r-base
  • Depends: fexoticoptions r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fexoticoptions.html
  • 9 days old (needed 5 days)
• fextremes (3042.82-2 to 3042.82-3)
  • Migration status for fextremes (3042.82-2 to 3042.82-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): fextremes r-base
  • Depends: fextremes r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fextremes.html
  • 9 days old (needed 5 days)
• fmultivar (3042.80.1-1 to 3042.80.1-2)
  • Migration status for fmultivar (3042.80.1-1 to 3042.80.1-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): fmultivar r-base
  • Depends: fmultivar r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fmultivar.html
  • 9 days old (needed 5 days)
• foreign (0.8.76-1 to 0.8.79-2)
  • Migration status for foreign (0.8.76-1 to 0.8.79-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): foreign r-base
  • Depends: foreign r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foreign.html
  • 9 days old (needed 5 days)
• gammaray (2.11.0-2 to 2.11.1-1)
  • Migration status for gammaray (2.11.0-2 to 2.11.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): gammaray glslang (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gammaray.html
  • 9 days old (needed 5 days)
• libcli (1.10.2-1 to 1.10.4-1)
  • Migration status for libcli (1.10.2-1 to 1.10.4-1): 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/libc/libcli.html
• multcomp (1.4-13-1 to 1.4-13-2)
  • Migration status for multcomp (1.4-13-1 to 1.4-13-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): multcomp r-base
  • Depends: multcomp r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multcomp.html
  • 9 days old (needed 5 days)
• openmolcas (- to 19.11-5)
  • Migration status for openmolcas (- to 19.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openmolcas introduces new bugs: #961704
  • autopkgtest for openmolcas/19.11-5: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmolcas.html
  • 9 days old (needed 5 days)
• pcs (0.10.5-1 to 0.10.5-2)
  • Migration status for pcs (0.10.5-1 to 0.10.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: pcs python-tornado (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcs.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• prometheus-mongodb-exporter (- to 1.0.0+git20180522.e755a44-2)
  • Migration status for prometheus-mongodb-exporter (- to 1.0.0+git20180522.e755a44-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • prometheus-mongodb-exporter/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-mongodb-exporter.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-bioc-altcdfenvs (- to 1:2.50.0-1)
  • Migration status for r-bioc-altcdfenvs (- to 1:2.50.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Build-Depends(-Arch): r-bioc-altcdfenvs r-bioc-hypergraph (not considered)
  • Depends: r-bioc-altcdfenvs r-bioc-hypergraph (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: r-bioc-altcdfenvs r-base
  • Depends: r-bioc-altcdfenvs r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-altcdfenvs.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-bioc-annotate (1.64.0+dfsg-1 to 1.66.0+dfsg-1)
  • Migration status for r-bioc-annotate (1.64.0+dfsg-1 to 1.66.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-annotate r-base
  • Depends: r-bioc-annotate r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-annotate.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-bioc-annotationdbi (1.48.0-1 to 1.50.0-1)
  • Migration status for r-bioc-annotationdbi (1.48.0-1 to 1.50.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-annotationdbi r-base
  • Depends: r-bioc-annotationdbi r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-annotationdbi.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-bioc-annotationfilter (1.10.0+dfsg-1 to 1.12.0+dfsg-1)
  • Migration status for r-bioc-annotationfilter (1.10.0+dfsg-1 to 1.12.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-annotationfilter r-base
  • Depends: r-bioc-annotationfilter r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-annotationfilter.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-bioc-ebseq (1.26.0-1 to 1.28.0-1)
  • Migration status for r-bioc-ebseq (1.26.0-1 to 1.28.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-ebseq r-base
  • Depends: r-bioc-ebseq r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ebseq.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-bioc-go.db (3.10.0-1 to 3.11.1-1)
  • Migration status for r-bioc-go.db (3.10.0-1 to 3.11.1-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-go.db r-bioc-annotationdbi
  • Depends: r-bioc-go.db r-base
  • Depends: r-bioc-go.db r-bioc-annotationdbi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-go.db.html
  • Should wait for tests relating to r-bioc-go.db 3.11.1-1, but forced by ginggs
  • autopkgtest for r-bioc-limma/3.42.2+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • 9 days old (needed 5 days)
• r-bioc-org.hs.eg.db (3.10.0-2 to 3.11.1-1)
  • Migration status for r-bioc-org.hs.eg.db (3.10.0-2 to 3.11.1-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-org.hs.eg.db r-bioc-annotationdbi
  • Depends: r-bioc-org.hs.eg.db r-base
  • Depends: r-bioc-org.hs.eg.db r-bioc-annotationdbi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-org.hs.eg.db.html
  • Should wait for tests relating to r-bioc-org.hs.eg.db 3.11.1-1, but forced by ginggs
  • autopkgtest for r-bioc-limma/3.42.2+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • 9 days old (needed 5 days)
• r-bioc-pwmenrich (4.22.0-2 to 4.23.0-1)
  • Migration status for r-bioc-pwmenrich (4.22.0-2 to 4.23.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-pwmenrich r-base
  • Depends: r-bioc-pwmenrich r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-pwmenrich.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-bioc-rsamtools (2.2.3-1 to 2.4.0-1)
  • Migration status for r-bioc-rsamtools (2.2.3-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-rsamtools r-base
  • Depends: r-bioc-rsamtools r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rsamtools.html
  • 9 days old (needed 5 days)
• r-bioc-summarizedexperiment (1.16.1+dfsg-1 to 1.18.1+dfsg-1)
  • Migration status for r-bioc-summarizedexperiment (1.16.1+dfsg-1 to 1.18.1+dfsg-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-summarizedexperiment r-bioc-iranges
  • Depends: r-bioc-summarizedexperiment r-base
  • Depends: r-bioc-summarizedexperiment r-bioc-biocgenerics
  • Depends: r-bioc-summarizedexperiment r-bioc-iranges
  • Depends: r-bioc-summarizedexperiment r-bioc-s4vectors
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-summarizedexperiment.html
  • Should wait for tests relating to r-bioc-summarizedexperiment 1.18.1+dfsg-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-bioc-multiassayexperiment/1.12.6+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • 9 days old (needed 5 days)
• r-cran-batchjobs (1.8-1 to 1.8-2)
  • Migration status for r-cran-batchjobs (1.8-1 to 1.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-batchjobs r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-batchjobs.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-bold (1.0.0+dfsg-1 to 1.0.0+dfsg-2)
  • Migration status for r-cran-bold (1.0.0+dfsg-1 to 1.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bold r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bold.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-bookdown (0.18+dfsg-1 to 0.19+dfsg-1)
  • Migration status for r-cran-bookdown (0.18+dfsg-1 to 0.19+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bookdown r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bookdown.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-broom (0.5.6+dfsg-1 to 0.5.6+dfsg-2)
  • Migration status for r-cran-broom (0.5.6+dfsg-1 to 0.5.6+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-broom r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-broom.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-caic4 (0.9-1 to 0.9-2)
  • Migration status for r-cran-caic4 (0.9-1 to 0.9-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-caic4 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-caic4.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-cellranger (1.1.0-2 to 1.1.0-3)
  • Migration status for r-cran-cellranger (1.1.0-2 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-cellranger r-base
  • Depends: r-cran-cellranger r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cellranger.html
  • 9 days old (needed 5 days)
• r-cran-cliapp (0.1.0-1 to 0.1.0-2)
  • Migration status for r-cran-cliapp (0.1.0-1 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cliapp r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cliapp.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-conting (1.7-1 to 1.7-2)
  • Migration status for r-cran-conting (1.7-1 to 1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-conting r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-conting.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-dbitest (1.7.0-1 to 1.7.0-2)
  • Migration status for r-cran-dbitest (1.7.0-1 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dbitest r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dbitest.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-dbplyr (1.4.3-1 to 1.4.3-2)
  • Migration status for r-cran-dbplyr (1.4.3-1 to 1.4.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dbplyr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dbplyr.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-devtools (2.2.2-2 to 2.3.0-2)
  • Migration status for r-cran-devtools (2.2.2-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-devtools r-cran-roxygen2
  • Depends: r-cran-devtools r-base
  • Depends: r-cran-devtools r-cran-roxygen2
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-devtools.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-ei (1.3-3-2 to 1.3-3-3)
  • Migration status for r-cran-ei (1.3-3-2 to 1.3-3-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ei r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ei.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-forcats (0.5.0-1 to 0.5.0-2)
  • Migration status for r-cran-forcats (0.5.0-1 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-forcats r-base
  • Depends: r-cran-forcats r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-forcats.html
  • 9 days old (needed 5 days)
• r-cran-future.batchtools (0.9.0+dfsg-1 to 0.9.0+dfsg-2)
  • Migration status for r-cran-future.batchtools (0.9.0+dfsg-1 to 0.9.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-future.batchtools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-future.batchtools.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-ggplot2 (3.3.0+dfsg-1 to 3.3.0+dfsg-2)
  • Migration status for r-cran-ggplot2 (3.3.0+dfsg-1 to 3.3.0+dfsg-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-ggplot2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggplot2.html
  • Should wait for tests relating to r-cran-ggplot2 3.3.0+dfsg-2, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-ggeffects/0.14.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 9 days old (needed 5 days)
• r-cran-ggvis (0.4.5+dfsg-2 to 0.4.5+dfsg-3)
  • Migration status for r-cran-ggvis (0.4.5+dfsg-2 to 0.4.5+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ggvis r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggvis.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-irdisplay (0.7.0-2 to 0.7.0-3)
  • Migration status for r-cran-irdisplay (0.7.0-2 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irdisplay r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-irdisplay.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-irkernel (1.1-1 to 1.1-2)
  • Migration status for r-cran-irkernel (1.1-1 to 1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-irkernel r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-irkernel.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-jrc (0.3.1-1 to 0.3.1-2)
  • Migration status for r-cran-jrc (0.3.1-1 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jrc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-jrc.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-metap (1.3-1 to 1.3-2)
  • Migration status for r-cran-metap (1.3-1 to 1.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metap r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-metap.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-mi (1.0-7 to 1.0-8)
  • Migration status for r-cran-mi (1.0-7 to 1.0-8): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mi r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mi.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-miniui (0.1.1.1-2 to 0.1.1.1-3)
  • Migration status for r-cran-miniui (0.1.1.1-2 to 0.1.1.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-miniui r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-miniui.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-mockery (0.4.2+dfsg-1 to 0.4.2+dfsg-2)
  • Migration status for r-cran-mockery (0.4.2+dfsg-1 to 0.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mockery r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mockery.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-mutoss (0.1-12-2 to 0.1-12-3)
  • Migration status for r-cran-mutoss (0.1-12-2 to 0.1-12-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mutoss r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mutoss.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-natserv (0.4.0+dfsg-1 to 1.0.0+dfsg-1)
  • Migration status for r-cran-natserv (0.4.0+dfsg-1 to 1.0.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-natserv r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-natserv.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-pbkrtest (0.4-8.6-1 to 0.4-8.6-2)
  • Migration status for r-cran-pbkrtest (0.4-8.6-1 to 0.4-8.6-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-pbkrtest r-base
  • Depends: r-cran-pbkrtest r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pbkrtest.html
  • 9 days old (needed 5 days)
• r-cran-plumber (0.4.6-1 to 0.4.6-2)
  • Migration status for r-cran-plumber (0.4.6-1 to 0.4.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-plumber r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-plumber.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-popepi (0.4.8+dfsg-1 to 0.4.8+dfsg-2)
  • Migration status for r-cran-popepi (0.4.8+dfsg-1 to 0.4.8+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-popepi r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-popepi.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-psychotree (0.15-3-1 to 0.15-3-2)
  • Migration status for r-cran-psychotree (0.15-3-1 to 0.15-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychotree r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-psychotree.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-quantmod (0.4.17-1 to 0.4.17-2)
  • Migration status for r-cran-quantmod (0.4.17-1 to 0.4.17-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-quantmod r-base
  • Depends: r-cran-quantmod r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-quantmod.html
  • 9 days old (needed 5 days)
• r-cran-rematch2 (2.1.2-1 to 2.1.2-2)
  • Migration status for r-cran-rematch2 (2.1.2-1 to 2.1.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rematch2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rematch2.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-reprex (0.3.0-1 to 0.3.0-2)
  • Migration status for r-cran-reprex (0.3.0-1 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reprex r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-reprex.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-rhandsontable (0.3.6+dfsg1-1 to 0.3.6+dfsg2-1)
  • Migration status for r-cran-rhandsontable (0.3.6+dfsg1-1 to 0.3.6+dfsg2-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rhandsontable r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rhandsontable.html
  • 9 days old (needed 5 days)
• r-cran-rotl (3.0.10-1 to 3.0.10-2)
  • Migration status for r-cran-rotl (3.0.10-1 to 3.0.10-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rotl r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rotl.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-rredlist (0.6.0-1 to 0.6.0-2)
  • Migration status for r-cran-rredlist (0.6.0-1 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rredlist r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rredlist.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-shiny (1.4.0.2+dfsg-1 to 1.4.0.2+dfsg-2)
  • Migration status for r-cran-shiny (1.4.0.2+dfsg-1 to 1.4.0.2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shiny r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shiny.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-shinybs (0.61-3 to 0.61-4)
  • Migration status for r-cran-shinybs (0.61-3 to 0.61-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shinybs r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shinybs.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-shinycssloaders (0.3-1 to 0.3-2)
  • Migration status for r-cran-shinycssloaders (0.3-1 to 0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shinycssloaders r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shinycssloaders.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-shinydashboard (0.7.1-1 to 0.7.1-2)
  • Migration status for r-cran-shinydashboard (0.7.1-1 to 0.7.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shinydashboard r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shinydashboard.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-shinyfiles (0.8.0-1 to 0.8.0-2)
  • Migration status for r-cran-shinyfiles (0.8.0-1 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shinyfiles r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shinyfiles.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-shinyjs (1.1-1 to 1.1-2)
  • Migration status for r-cran-shinyjs (1.1-1 to 1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shinyjs r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shinyjs.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-shinythemes (1.1.2+dfsg-1 to 1.1.2+dfsg-2)
  • Migration status for r-cran-shinythemes (1.1.2+dfsg-1 to 1.1.2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shinythemes r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shinythemes.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-sn (1.6-1-2 to 1.6-1-3)
  • Migration status for r-cran-sn (1.6-1-2 to 1.6-1-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-sn r-base
  • Depends: r-cran-sn r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sn.html
  • 9 days old (needed 5 days)
• r-cran-solrium (1.1.4+dfsg-1 to 1.1.4+dfsg-2)
  • Migration status for r-cran-solrium (1.1.4+dfsg-1 to 1.1.4+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-solrium r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-solrium.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-stars (0.4-1-2 to 0.4-1-3)
  • Migration status for r-cran-stars (0.4-1-2 to 0.4-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stars r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-stars.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-testextra (0.1.0.1-2 to 0.1.0.1-3)
  • Migration status for r-cran-testextra (0.1.0.1-2 to 0.1.0.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-testextra r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-testextra.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-testthat (2.3.2-1 to 2.3.2-2)
  • Migration status for r-cran-testthat (2.3.2-1 to 2.3.2-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-testthat r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-testthat.html
  • Should wait for tests relating to r-cran-testthat 2.3.2-2, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-bioc-multiassayexperiment/1.12.6+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-ggeffects/0.14.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-httpuv/1.5.2+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-raster/3.0-12-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjlabelled/1.1.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjmisc/2.8.4-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 9 days old (needed 5 days)
• r-cran-tfisher (0.2.0-2 to 0.2.0-3)
  • Migration status for r-cran-tfisher (0.2.0-2 to 0.2.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tfisher r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tfisher.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-tufte (0.6-1 to 0.6-2)
  • Migration status for r-cran-tufte (0.6-1 to 0.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tufte r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tufte.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-usethis (1.6.1-1 to 1.6.1-2)
  • Migration status for r-cran-usethis (1.6.1-1 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-usethis r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-usethis.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-vcdextra (0.7-1-3 to 0.7-1-4)
  • Migration status for r-cran-vcdextra (0.7-1-3 to 0.7-1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vcdextra r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vcdextra.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-vcr (0.5.4+dfsg-1 to 0.5.4+dfsg-2)
  • Migration status for r-cran-vcr (0.5.4+dfsg-1 to 0.5.4+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vcr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vcr.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-webmockr (0.6.2-1 to 0.6.2-2)
  • Migration status for r-cran-webmockr (0.6.2-1 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webmockr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-webmockr.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-wikidatar (1.4.0+dfsg-1 to 1.4.0+dfsg-2)
  • Migration status for r-cran-wikidatar (1.4.0+dfsg-1 to 1.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wikidatar r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-wikidatar.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-wikitaxa (0.3.0+dfsg-1 to 0.3.0+dfsg-2)
  • Migration status for r-cran-wikitaxa (0.3.0+dfsg-1 to 0.3.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wikitaxa r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-wikitaxa.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• r-cran-worrms (0.4.0+dfsg-1 to 0.4.0+dfsg-2)
  • Migration status for r-cran-worrms (0.4.0+dfsg-1 to 0.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-worrms r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-worrms.html
  • Required age reduced by 3 days because of autopkgtest
  • 9 days old (needed 2 days)
• skesa (2.3.0-2 to 2.4.0-1)
  • Migration status for skesa (2.3.0-2 to 2.4.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: skesa ncbi-vdb (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skesa.html
  • 9 days old (needed 5 days)
• consul (1.7.2+dfsg1-1 to 1.7.3+dfsg1-1)
  • Migration status for consul (1.7.2+dfsg1-1 to 1.7.3+dfsg1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armhf
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/consul.html
  • 10 days old (needed 5 days)
• fbonds (3042.78-3 to 3042.78-4)
  • Migration status for fbonds (3042.78-3 to 3042.78-4): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): fbonds r-base
  • Depends: fbonds r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fbonds.html
  • 10 days old (needed 5 days)
• fimport (3042.85-2 to 3042.85-3)
  • Migration status for fimport (3042.85-2 to 3042.85-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): fimport r-base
  • Depends: fimport r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fimport.html
  • 10 days old (needed 5 days)
• ftrading (3042.79-2 to 3042.79-3)
  • Migration status for ftrading (3042.79-2 to 3042.79-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): ftrading r-base
  • Depends: ftrading r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ftrading.html
  • 10 days old (needed 5 days)
• gitlab-ci-multi-runner (12.9.0+dfsg-1 to 12.10.2+dfsg-1)
  • Migration status for gitlab-ci-multi-runner (12.9.0+dfsg-1 to 12.10.2+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 i386
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
  • 10 days old (needed 5 days)
• gmodels (2.18.1-1 to 2.18.1-2)
  • Migration status for gmodels (2.18.1-1 to 2.18.1-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): gmodels r-base
  • Depends: gmodels r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmodels.html
  • 10 days old (needed 5 days)
• gplots (3.0.3-1 to 3.0.3-2)
  • Migration status for gplots (3.0.3-1 to 3.0.3-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): gplots r-base
  • Depends: gplots r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gplots.html
  • 10 days old (needed 5 days)
• gtkgl2 (2.0.1-2.2 to 2.1.0-0.2)
  • Migration status for gtkgl2 (2.0.1-2.2 to 2.1.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gtkgl2 introduces new bugs: #960872
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkgl2.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• mothur (1.42.1-1 to 1.44.1-1)
  • Migration status for mothur (1.42.1-1 to 1.44.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mothur introduces new bugs: #960873
  • autopkgtest for mothur/1.44.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mothur.html
  • 10 days old (needed 5 days)
• nova (2:20.1.1-1 to 2:21.0.0-2)
  • Migration status for nova (2:20.1.1-1 to 2:21.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
  • uninstallable on arch arm64, not running autopkgtest there
  • 10 days old (needed 5 days)
• r-bioc-aroma.light (3.16.0-1 to 3.18.0-2)
  • Migration status for r-bioc-aroma.light (3.16.0-1 to 3.18.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-aroma.light r-base
  • Depends: r-bioc-aroma.light r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-aroma.light.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-biocparallel (1.20.1-1 to 1.22.0-1)
  • Migration status for r-bioc-biocparallel (1.20.1-1 to 1.22.0-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-bioc-biocparallel r-base
  • Depends: r-bioc-biocparallel r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biocparallel.html
  • Should wait for tests relating to r-bioc-biocparallel 1.22.0-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • 10 days old (needed 5 days)
• r-bioc-biocviews (- to 1.56.0-1)
  • Migration status for r-bioc-biocviews (- to 1.56.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Depends: r-bioc-biocviews r-bioc-graph (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): r-bioc-biocviews r-bioc-rbgl
  • Depends: r-bioc-biocviews r-base
  • Depends: r-bioc-biocviews r-bioc-biocgenerics
  • Depends: r-bioc-biocviews r-bioc-rbgl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biocviews.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-biomformat (1.14.0+dfsg-1 to 1.16.0+dfsg-1)
  • Migration status for r-bioc-biomformat (1.14.0+dfsg-1 to 1.16.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-biomformat r-base
  • Depends: r-bioc-biomformat r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biomformat.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-biostrings (2.54.0-1 to 2.56.0-1)
  • Migration status for r-bioc-biostrings (2.54.0-1 to 2.56.0-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-biostrings r-bioc-xvector
  • Depends: r-bioc-biostrings r-base
  • Depends: r-bioc-biostrings r-bioc-biocgenerics
  • Depends: r-bioc-biostrings r-bioc-iranges
  • Depends: r-bioc-biostrings r-bioc-s4vectors
  • Depends: r-bioc-biostrings r-bioc-xvector
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biostrings.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-consensusclusterplus (1.50.0-1 to 1.52.0-1)
  • Migration status for r-bioc-consensusclusterplus (1.50.0-1 to 1.52.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-consensusclusterplus r-base
  • Depends: r-bioc-consensusclusterplus r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-consensusclusterplus.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-dirichletmultinomial (1.28.0-1 to 1.30.0-1)
  • Migration status for r-bioc-dirichletmultinomial (1.28.0-1 to 1.30.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-dirichletmultinomial r-base
  • Depends: r-bioc-dirichletmultinomial r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dirichletmultinomial.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-genomeinfodb (1.22.1-1 to 1.24.0-1)
  • Migration status for r-bioc-genomeinfodb (1.22.1-1 to 1.24.0-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-genomeinfodb r-bioc-s4vectors
  • Depends: r-bioc-genomeinfodb r-base
  • Depends: r-bioc-genomeinfodb r-bioc-biocgenerics
  • Depends: r-bioc-genomeinfodb r-bioc-s4vectors
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomeinfodb.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-genomicranges (1.38.0+dfsg-1 to 1.40.0+dfsg-1)
  • Migration status for r-bioc-genomicranges (1.38.0+dfsg-1 to 1.40.0+dfsg-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-genomicranges r-bioc-xvector
  • Depends: r-bioc-genomicranges r-base
  • Depends: r-bioc-genomicranges r-bioc-biocgenerics
  • Depends: r-bioc-genomicranges r-bioc-iranges
  • Depends: r-bioc-genomicranges r-bioc-s4vectors
  • Depends: r-bioc-genomicranges r-bioc-xvector
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomicranges.html
  • Should wait for tests relating to r-bioc-genomicranges 1.40.0+dfsg-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-bioc-multiassayexperiment/1.12.6+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • 10 days old (needed 5 days)
• r-bioc-keggrest (1.26.1+dfsg-1 to 1.28.0+dfsg-1)
  • Migration status for r-bioc-keggrest (1.26.1+dfsg-1 to 1.28.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-keggrest r-base
  • Depends: r-bioc-keggrest r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-keggrest.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-makecdfenv (1.62.0-1 to 1.64.0-1)
  • Migration status for r-bioc-makecdfenv (1.62.0-1 to 1.64.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-makecdfenv r-base
  • Depends: r-bioc-makecdfenv r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-makecdfenv.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-metagenomeseq (1.28.2-1 to 1.30.0-1)
  • Migration status for r-bioc-metagenomeseq (1.28.2-1 to 1.30.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-metagenomeseq r-base
  • Depends: r-bioc-metagenomeseq r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-metagenomeseq.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-multtest (2.42.0-1 to 2.44.0-1)
  • Migration status for r-bioc-multtest (2.42.0-1 to 2.44.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-multtest r-base
  • Depends: r-bioc-multtest r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-multtest.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-snpstats (1.36.0+dfsg-1 to 1.38.0+dfsg-1)
  • Migration status for r-bioc-snpstats (1.36.0+dfsg-1 to 1.38.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-snpstats r-base
  • Depends: r-bioc-snpstats r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-snpstats.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-bioc-xvector (0.26.0-1 to 0.28.0-1)
  • Migration status for r-bioc-xvector (0.26.0-1 to 0.28.0-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-bioc-xvector r-bioc-iranges
  • Depends: r-bioc-xvector r-base
  • Depends: r-bioc-xvector r-bioc-biocgenerics
  • Depends: r-bioc-xvector r-bioc-iranges
  • Depends: r-bioc-xvector r-bioc-s4vectors
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-xvector.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-adegraphics (1.0-15-1 to 1.0-15-2)
  • Migration status for r-cran-adegraphics (1.0-15-1 to 1.0-15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-adegraphics r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-adegraphics.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-animation (2.6+dfsg-1 to 2.6+dfsg-2)
  • Migration status for r-cran-animation (2.6+dfsg-1 to 2.6+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-animation r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-animation.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-arm (1.11-1-1 to 1.11-1-2)
  • Migration status for r-cran-arm (1.11-1-1 to 1.11-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-arm r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-arm.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-blme (1.0-4-2 to 1.0-4-3)
  • Migration status for r-cran-blme (1.0-4-2 to 1.0-4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blme r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-blme.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-blob (1.2.1-1 to 1.2.1-2)
  • Migration status for r-cran-blob (1.2.1-1 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-blob r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-blob.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-bradleyterry2 (1.1-2-1 to 1.1-2-2)
  • Migration status for r-cran-bradleyterry2 (1.1-2-1 to 1.1-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bradleyterry2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bradleyterry2.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-bridgesampling (1.0-0-1 to 1.0-0-2)
  • Migration status for r-cran-bridgesampling (1.0-0-1 to 1.0-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bridgesampling r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bridgesampling.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-clubsandwich (0.4.2-1 to 0.4.2-2)
  • Migration status for r-cran-clubsandwich (0.4.2-1 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clubsandwich r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-clubsandwich.html
  • 10 days old (needed 5 days)
• r-cran-crosstalk (1.1.0.1+dfsg-1 to 1.1.0.1+dfsg-2)
  • Migration status for r-cran-crosstalk (1.1.0.1+dfsg-1 to 1.1.0.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-crosstalk r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-crosstalk.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-crul (0.9.0+dfsg-1 to 0.9.0+dfsg-2)
  • Migration status for r-cran-crul (0.9.0+dfsg-1 to 0.9.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-crul r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-crul.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-d3network (0.5.2.1-2 to 0.5.2.1-3)
  • Migration status for r-cran-d3network (0.5.2.1-2 to 0.5.2.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-d3network r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-d3network.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-domc (1.3.6-1 to 1.3.6-2)
  • Migration status for r-cran-domc (1.3.6-1 to 1.3.6-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-domc r-base
  • Depends: r-cran-domc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-domc.html
  • 10 days old (needed 5 days)
• r-cran-dosnow (1.0.18-1 to 1.0.18-2)
  • Migration status for r-cran-dosnow (1.0.18-1 to 1.0.18-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-dosnow r-base
  • Depends: r-cran-dosnow r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dosnow.html
  • 10 days old (needed 5 days)
• r-cran-dt (0.13+dfsg-2 to 0.13+dfsg-3)
  • Migration status for r-cran-dt (0.13+dfsg-2 to 0.13+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dt r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dt.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-dygraphs (1.1.1.6+dfsg-1 to 1.1.1.6+dfsg-2)
  • Migration status for r-cran-dygraphs (1.1.1.6+dfsg-1 to 1.1.1.6+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dygraphs r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dygraphs.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-fitbitscraper (0.1.8-5 to 0.1.8-6)
  • Migration status for r-cran-fitbitscraper (0.1.8-5 to 0.1.8-6): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fitbitscraper r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fitbitscraper.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-furrr (0.1.0-2 to 0.1.0-3)
  • Migration status for r-cran-furrr (0.1.0-2 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-furrr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-furrr.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-future.apply (1.5.0-1 to 1.5.0-2)
  • Migration status for r-cran-future.apply (1.5.0-1 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-future.apply r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-future.apply.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-ggm (- to 2.5-2)
  • Migration status for r-cran-ggm (- to 2.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Build-Depends(-Arch): r-cran-ggm r-bioc-graph (not considered)
  • Depends: r-cran-ggm r-bioc-graph (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: r-cran-ggm r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggm.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-gh (1.1.0-1 to 1.1.0-2)
  • Migration status for r-cran-gh (1.1.0-1 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gh r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gh.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-gprofiler (0.7.0-1 to 0.7.0-2)
  • Migration status for r-cran-gprofiler (0.7.0-1 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gprofiler r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gprofiler.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-hms (0.5.3-1 to 0.5.3-2)
  • Migration status for r-cran-hms (0.5.3-1 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hms r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-hms.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-htmlwidgets (1.5.1+dfsg-1 to 1.5.1+dfsg-2)
  • Migration status for r-cran-htmlwidgets (1.5.1+dfsg-1 to 1.5.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-htmlwidgets r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-htmlwidgets.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-httr (1.4.1-1 to 1.4.1-2)
  • Migration status for r-cran-httr (1.4.1-1 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-httr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-httr.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-jsonld (2.1+dfsg-1 to 2.1+dfsg-2)
  • Migration status for r-cran-jsonld (2.1+dfsg-1 to 2.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-jsonld r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-jsonld.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-kmi (0.5.5-1 to 0.5.5-2)
  • Migration status for r-cran-kmi (0.5.5-1 to 0.5.5-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-kmi r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-kmi.html
  • Should wait for tests relating to r-cran-kmi 0.5.5-2, but forced by ginggs
  • autopkgtest for r-cran-etm/1.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • 10 days old (needed 5 days)
• r-cran-kutils (1.70+dfsg-1 to 1.70+dfsg-2)
  • Migration status for r-cran-kutils (1.70+dfsg-1 to 1.70+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kutils r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-kutils.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-lava (1.6.7-1 to 1.6.7-2)
  • Migration status for r-cran-lava (1.6.7-1 to 1.6.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lava r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lava.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-leiden (0.3.3+dfsg-1 to 0.3.3+dfsg-2)
  • Migration status for r-cran-leiden (0.3.3+dfsg-1 to 0.3.3+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-leiden r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-leiden.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-logcondens (2.1.5-2 to 2.1.5-3)
  • Migration status for r-cran-logcondens (2.1.5-2 to 2.1.5-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logcondens r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-logcondens.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-lsmeans (2.30-0-1 to 2.30-0-2)
  • Migration status for r-cran-lsmeans (2.30-0-1 to 2.30-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lsmeans r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lsmeans.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-maptree (1.4-7-3 to 1.4-7-4)
  • Migration status for r-cran-maptree (1.4-7-3 to 1.4-7-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maptree r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-maptree.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-matrixmodels (0.4-1-2 to 0.4-1-3)
  • Migration status for r-cran-matrixmodels (0.4-1-2 to 0.4-1-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-matrixmodels r-base
  • Depends: r-cran-matrixmodels r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-matrixmodels.html
  • 10 days old (needed 5 days)
• r-cran-maxlik (1.3-8-1 to 1.3-8-2)
  • Migration status for r-cran-maxlik (1.3-8-1 to 1.3-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maxlik r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-maxlik.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-mediana (1.0.8-2 to 1.0.8-3)
  • Migration status for r-cran-mediana (1.0.8-2 to 1.0.8-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mediana r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mediana.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-mlmetrics (1.1.1-2 to 1.1.1-3)
  • Migration status for r-cran-mlmetrics (1.1.1-2 to 1.1.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlmetrics r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mlmetrics.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-mlmrev (1.0-8-1 to 1.0-8-2)
  • Migration status for r-cran-mlmrev (1.0-8-1 to 1.0-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mlmrev r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mlmrev.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-nfactors (2.4.1-1 to 2.4.1-2)
  • Migration status for r-cran-nfactors (2.4.1-1 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nfactors r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-nfactors.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-parallelmap (1.5.0-2 to 1.5.0-3)
  • Migration status for r-cran-parallelmap (1.5.0-2 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parallelmap r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-parallelmap.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-pheatmap (1.0.12-1 to 1.0.12-2)
  • Migration status for r-cran-pheatmap (1.0.12-1 to 1.0.12-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pheatmap r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pheatmap.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-phytools (0.7-20-1 to 0.7-20-2)
  • Migration status for r-cran-phytools (0.7-20-1 to 0.7-20-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-phytools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-phytools.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-pillar (1.4.4-1 to 1.4.4-2)
  • Migration status for r-cran-pillar (1.4.4-1 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pillar r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pillar.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-pkgbuild (1.0.8-1 to 1.0.8-2)
  • Migration status for r-cran-pkgbuild (1.0.8-1 to 1.0.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pkgbuild r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pkgbuild.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-pkgload (1.0.2-1 to 1.0.2-2)
  • Migration status for r-cran-pkgload (1.0.2-1 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pkgload r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pkgload.html
  • 10 days old (needed 5 days)
• r-cran-pkgmaker (0.31.1-1 to 0.31.1-2)
  • Migration status for r-cran-pkgmaker (0.31.1-1 to 0.31.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pkgmaker r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pkgmaker.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-plm (2.2-3-1 to 2.2-3-2)
  • Migration status for r-cran-plm (2.2-3-1 to 2.2-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-plm r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-plm.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-progress (1.2.2-1 to 1.2.2-2)
  • Migration status for r-cran-progress (1.2.2-1 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-progress r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-progress.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-pscbs (0.65.0-2 to 0.65.0-3)
  • Migration status for r-cran-pscbs (0.65.0-2 to 0.65.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pscbs r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pscbs.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-psychtools (1.9.12-2 to 1.9.12-3)
  • Migration status for r-cran-psychtools (1.9.12-2 to 1.9.12-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psychtools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-psychtools.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-r.cache (0.14.0-1 to 0.14.0-2)
  • Migration status for r-cran-r.cache (0.14.0-1 to 0.14.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-r.cache r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-r.cache.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rcarb (0.1.3-1 to 0.1.3-2)
  • Migration status for r-cran-rcarb (0.1.3-1 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcarb r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rcarb.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rcmdcheck (1.3.3-1 to 1.3.3-2)
  • Migration status for r-cran-rcmdcheck (1.3.3-1 to 1.3.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcmdcheck r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rcmdcheck.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rcpparmadillo (0.9.870.2.0-1 to 0.9.880.1.0-1)
  • Migration status for r-cran-rcpparmadillo (0.9.870.2.0-1 to 0.9.880.1.0-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-rcpparmadillo r-base
  • Depends: r-cran-rcpparmadillo r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rcpparmadillo.html
  • Should wait for tests relating to r-cran-rcpparmadillo 0.9.880.1.0-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-etm/1.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • 10 days old (needed 5 days)
• r-cran-rdpack (0.11-1-1 to 0.11-1-2)
  • Migration status for r-cran-rdpack (0.11-1-1 to 0.11-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rdpack r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rdpack.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rentrez (1.2.2+dfsg-1 to 1.2.2+dfsg-2)
  • Migration status for r-cran-rentrez (1.2.2+dfsg-1 to 1.2.2+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rentrez r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rentrez.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-repr (1.1.0-1 to 1.1.0-2)
  • Migration status for r-cran-repr (1.1.0-1 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-repr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-repr.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-reshape (0.8.8-1 to 0.8.8-2)
  • Migration status for r-cran-reshape (0.8.8-1 to 0.8.8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reshape r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-reshape.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rmarkdown (2.1+dfsg-3 to 2.1+dfsg-4)
  • Migration status for r-cran-rmarkdown (2.1+dfsg-3 to 2.1+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rmarkdown r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rmarkdown.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rneos (0.4-0-1 to 0.4-0-2)
  • Migration status for r-cran-rneos (0.4-0-1 to 0.4-0-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-rneos r-base
  • Depends: r-cran-rneos r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rneos.html
  • 10 days old (needed 5 days)
• r-cran-rockchalk (1.8.144+dfsg-2 to 1.8.144+dfsg-3)
  • Migration status for r-cran-rockchalk (1.8.144+dfsg-2 to 1.8.144+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rockchalk r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rockchalk.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rocr (1.0-11-1 to 1.0-11-2)
  • Migration status for r-cran-rocr (1.0-11-1 to 1.0-11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rocr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rocr.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rsconnect (0.8.16-1 to 0.8.16-2)
  • Migration status for r-cran-rsconnect (0.8.16-1 to 0.8.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsconnect r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rsconnect.html
  • 10 days old (needed 5 days)
• r-cran-rsdmx (1:0.5-14+dfsg-1 to 1:0.5-14+dfsg-2)
  • Migration status for r-cran-rsdmx (1:0.5-14+dfsg-1 to 1:0.5-14+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsdmx r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rsdmx.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rstantools (2.0.0-1 to 2.0.0-2)
  • Migration status for r-cran-rstantools (2.0.0-1 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rstantools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rstantools.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rsvd (1.0.3-2 to 1.0.3-3)
  • Migration status for r-cran-rsvd (1.0.3-2 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsvd r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rsvd.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-rvest (0.3.5-1 to 0.3.5-2)
  • Migration status for r-cran-rvest (0.3.5-1 to 0.3.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rvest r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rvest.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-scatterd3 (0.9.1+dfsg-1 to 0.9.1+dfsg-2)
  • Migration status for r-cran-scatterd3 (0.9.1+dfsg-1 to 0.9.1+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-scatterd3 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-scatterd3.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-selectr (0.4-2-1 to 0.4-2-2)
  • Migration status for r-cran-selectr (0.4-2-1 to 0.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-selectr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-selectr.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-spacetime (1.2-3+dfsg-1 to 1.2-3+dfsg-2)
  • Migration status for r-cran-spacetime (1.2-3+dfsg-1 to 1.2-3+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spacetime r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spacetime.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-spdata (0.3.5-1 to 0.3.5-2)
  • Migration status for r-cran-spdata (0.3.5-1 to 0.3.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spdata r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spdata.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-survey (4.0-1 to 4.0-2)
  • Migration status for r-cran-survey (4.0-1 to 4.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-survey r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-survey.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-th.data (1.0-10-1 to 1.0-10-2)
  • Migration status for r-cran-th.data (1.0-10-1 to 1.0-10-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-th.data r-base
  • Depends: r-cran-th.data r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-th.data.html
  • 10 days old (needed 5 days)
• r-cran-threejs (0.3.3+dfsg-1 to 0.3.3+dfsg-2)
  • Migration status for r-cran-threejs (0.3.3+dfsg-1 to 0.3.3+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-threejs r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-threejs.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-vcd (1:1.4-7-1 to 1:1.4-7-2)
  • Migration status for r-cran-vcd (1:1.4-7-1 to 1:1.4-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vcd r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vcd.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-venndiagram (1.6.20-2 to 1.6.20-3)
  • Migration status for r-cran-venndiagram (1.6.20-2 to 1.6.20-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-venndiagram r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-venndiagram.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-webshot (0.5.2-1 to 0.5.2-2)
  • Migration status for r-cran-webshot (0.5.2-1 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-webshot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-webshot.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-cran-wikipedir (1.5.0-2 to 1.5.0-3)
  • Migration status for r-cran-wikipedir (1.5.0-2 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wikipedir r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-wikipedir.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-omegahat-xmlrpc (0.3-0-2 to 0.3-0-3)
  • Migration status for r-omegahat-xmlrpc (0.3-0-2 to 0.3-0-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-omegahat-xmlrpc r-base
  • Depends: r-omegahat-xmlrpc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-omegahat-xmlrpc.html
  • 10 days old (needed 5 days)
• r-other-curvefdp (2.0-5 to 2.0-6)
  • Migration status for r-other-curvefdp (2.0-5 to 2.0-6): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-curvefdp r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-other-curvefdp.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• r-other-wasabi (1.0.1-1 to 1.0.1-2)
  • Migration status for r-other-wasabi (1.0.1-1 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-wasabi r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-other-wasabi.html
  • Required age reduced by 3 days because of autopkgtest
  • 10 days old (needed 2 days)
• sandwich (2.5-1-2 to 2.5-1-3)
  • Migration status for sandwich (2.5-1-2 to 2.5-1-3): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): sandwich r-base
  • Depends: sandwich r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sandwich.html
  • Should wait for tests relating to sandwich 2.5-1-3, but forced by ginggs
  • autopkgtest for r-cran-ggeffects/0.14.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 10 days old (needed 5 days)
• eclipse-jdt-debug (4.12-3 to 4.15-2)
  • Migration status for eclipse-jdt-debug (4.12-3 to 4.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): eclipse-jdt-debug eclipse-platform-debug (not considered)
  • Depends: eclipse-jdt-debug eclipse-platform-debug (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-jdt-debug.html
  • 11 days old (needed 5 days)
• latticeextra (0.6-29-2 to 0.6-29-3)
  • Migration status for latticeextra (0.6-29-2 to 0.6-29-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): latticeextra r-base
  • Depends: latticeextra r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latticeextra.html
  • 11 days old (needed 5 days)
• opendht (1.8.1-1 to 2.1.1-1)
  • Migration status for opendht (1.8.1-1 to 2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • opendht unsatisfiable Build-Depends(-Arch) on armel: librestinio-dev
  • opendht unsatisfiable Build-Depends(-Arch) on mipsel: librestinio-dev
  • missing build on armel
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opendht.html
  • 11 days old (needed 5 days)
• prometheus-mysqld-exporter (- to 0.12.1+ds-1)
  • Migration status for prometheus-mysqld-exporter (- to 0.12.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating prometheus-mysqld-exporter introduces new bugs: #953040
  • prometheus-mysqld-exporter/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-mysqld-exporter.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• python-django-libsass (- to 0.8-2)
  • Migration status for python-django-libsass (- to 0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python-django-libsass/0.8-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-libsass.html
  • 11 days old (needed 5 days)
• r-bioc-affy (1.64.0-1 to 1.66.0-1)
  • Migration status for r-bioc-affy (1.64.0-1 to 1.66.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-affy r-base
  • Depends: r-bioc-affy r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-affy.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-affyio (1.56.0-1 to 1.58.0-1)
  • Migration status for r-bioc-affyio (1.56.0-1 to 1.58.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-affyio r-base
  • Depends: r-bioc-affyio r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-affyio.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-all (1.28.0-2 to 1.30.0-1)
  • Migration status for r-bioc-all (1.28.0-2 to 1.30.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-all r-base
  • Depends: r-bioc-all r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-all.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-bladderbatch (1.24.0-2 to 1.26.0-1)
  • Migration status for r-bioc-bladderbatch (1.24.0-2 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-bladderbatch r-base
  • Depends: r-bioc-bladderbatch r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-bladderbatch.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-ctc (1.60.0-2 to 1.62.0-1)
  • Migration status for r-bioc-ctc (1.60.0-2 to 1.62.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-ctc r-base
  • Depends: r-bioc-ctc r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ctc.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-edger (3.28.1+dfsg-3 to 3.30.0+dfsg-1)
  • Migration status for r-bioc-edger (3.28.1+dfsg-3 to 3.30.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-edger r-base
  • Depends: r-bioc-edger r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-edger.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-hilbertvis (1.44.0-1 to 1.46.0-1)
  • Migration status for r-bioc-hilbertvis (1.44.0-1 to 1.46.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-hilbertvis r-base
  • Depends: r-bioc-hilbertvis r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-hilbertvis.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-hypergraph (- to 1.60.0-1)
  • Migration status for r-bioc-hypergraph (- to 1.60.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Build-Depends(-Arch): r-bioc-hypergraph r-bioc-graph (not considered)
  • Depends: r-bioc-hypergraph r-bioc-graph (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: r-bioc-hypergraph r-base
  • Depends: r-bioc-hypergraph r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-hypergraph.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-ihw (1.14.0+dfsg-1 to 1.16.0+dfsg-1)
  • Migration status for r-bioc-ihw (1.14.0+dfsg-1 to 1.16.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-ihw r-base
  • Depends: r-bioc-ihw r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ihw.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-pcamethods (1.78.0-3 to 1.80.0-1)
  • Migration status for r-bioc-pcamethods (1.78.0-3 to 1.80.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-pcamethods r-base
  • Depends: r-bioc-pcamethods r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-pcamethods.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-rbgl (- to 1.64.0+dfsg-1)
  • Migration status for r-bioc-rbgl (- to 1.64.0+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Build-Depends(-Arch): r-bioc-rbgl r-bioc-graph (not considered)
  • Depends: r-bioc-rbgl r-bioc-graph (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: r-bioc-rbgl r-base
  • Depends: r-bioc-rbgl r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rbgl.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-rhdf5 (2.30.1+dfsg-1 to 2.32.0+dfsg-1)
  • Migration status for r-bioc-rhdf5 (2.30.1+dfsg-1 to 2.32.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-rhdf5 r-base
  • Depends: r-bioc-rhdf5 r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rhdf5.html
  • 11 days old (needed 5 days)
• r-bioc-rhtslib (1.18.1+dfsg-1 to 1.20.0+dfsg-1)
  • Migration status for r-bioc-rhtslib (1.18.1+dfsg-1 to 1.20.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-rhtslib r-base
  • Depends: r-bioc-rhtslib r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rhtslib.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-rots (1.14.0-2 to 1.16.0-1)
  • Migration status for r-bioc-rots (1.14.0-2 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-rots r-base
  • Depends: r-bioc-rots r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rots.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-bioc-wrench (1.4.0+dfsg-2 to 1.6.0+dfsg-1)
  • Migration status for r-bioc-wrench (1.4.0+dfsg-2 to 1.6.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-wrench r-base
  • Depends: r-bioc-wrench r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-wrench.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-assertive.sets (0.0-3-2 to 0.0-3-3)
  • Migration status for r-cran-assertive.sets (0.0-3-2 to 0.0-3-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-assertive.sets r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-assertive.sets.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-bayestestr (0.6.0-1 to 0.6.0-2)
  • Migration status for r-cran-bayestestr (0.6.0-1 to 0.6.0-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-bayestestr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bayestestr.html
  • Should wait for tests relating to r-cran-bayestestr 0.6.0-2, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 11 days old (needed 5 days)
• r-cran-bbmle (1.0.23.1-1 to 1.0.23.1-2)
  • Migration status for r-cran-bbmle (1.0.23.1-1 to 1.0.23.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bbmle r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bbmle.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-calibrate (1.7.5-1 to 1.7.5-2)
  • Migration status for r-cran-calibrate (1.7.5-1 to 1.7.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-calibrate r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-calibrate.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-callr (3.4.3-1 to 3.4.3-2)
  • Migration status for r-cran-callr (3.4.3-1 to 3.4.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-callr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-callr.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-circlize (0.4.9-1 to 0.4.9-2)
  • Migration status for r-cran-circlize (0.4.9-1 to 0.4.9-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-circlize r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-circlize.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-cli (2.0.2-1 to 2.0.2-2)
  • Migration status for r-cran-cli (2.0.2-1 to 2.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cli r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cli.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-clustergeneration (1.3.4-2 to 1.3.4-3)
  • Migration status for r-cran-clustergeneration (1.3.4-2 to 1.3.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clustergeneration r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-clustergeneration.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-coda (0.19-3-1 to 0.19-3-2)
  • Migration status for r-cran-coda (0.19-3-1 to 0.19-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-coda r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-coda.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-cvst (0.2-2-2 to 0.2-2-3)
  • Migration status for r-cran-cvst (0.2-2-2 to 0.2-2-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-cvst r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cvst.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-desc (1.2.0-2 to 1.2.0-3)
  • Migration status for r-cran-desc (1.2.0-2 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-desc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-desc.html
  • 11 days old (needed 5 days)
• r-cran-diagnosismed (0.2.3-6 to 0.2.3-7)
  • Migration status for r-cran-diagnosismed (0.2.3-6 to 0.2.3-7): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-diagnosismed r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-diagnosismed.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-doparallel (1.0.15-1 to 1.0.15-2)
  • Migration status for r-cran-doparallel (1.0.15-1 to 1.0.15-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-doparallel r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-doparallel.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-dorng (1.8.2-1 to 1.8.2-2)
  • Migration status for r-cran-dorng (1.8.2-1 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dorng r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dorng.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-downloader (0.4-3 to 0.4-4)
  • Migration status for r-cran-downloader (0.4-3 to 0.4-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-downloader r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-downloader.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-drr (0.0.4-1 to 0.0.4-2)
  • Migration status for r-cran-drr (0.0.4-1 to 0.0.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-drr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-drr.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-elliptic (1.4-0-1 to 1.4-0-2)
  • Migration status for r-cran-elliptic (1.4-0-1 to 1.4-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-elliptic r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-elliptic.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-emmeans (1.4.6-1 to 1.4.6-2)
  • Migration status for r-cran-emmeans (1.4.6-1 to 1.4.6-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-emmeans r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-emmeans.html
  • Should wait for tests relating to r-cran-emmeans 1.4.6-2, but forced by ginggs
  • autopkgtest for r-cran-ggeffects/0.14.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 11 days old (needed 5 days)
• r-cran-epicalc (2.15.1.0-4 to 2.15.1.0-5)
  • Migration status for r-cran-epicalc (2.15.1.0-4 to 2.15.1.0-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epicalc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-epicalc.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-epir (1.0-14-1 to 1.0-14-2)
  • Migration status for r-cran-epir (1.0-14-1 to 1.0-14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epir r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-epir.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-fail (1.3-3 to 1.3-4)
  • Migration status for r-cran-fail (1.3-3 to 1.3-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fail r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fail.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-fauxpas (0.5.0+dfsg-1 to 0.5.0+dfsg-2)
  • Migration status for r-cran-fauxpas (0.5.0+dfsg-1 to 0.5.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fauxpas r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fauxpas.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-fit.models (0.5-14-2 to 0.5-14-3)
  • Migration status for r-cran-fit.models (0.5-14-2 to 0.5-14-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fit.models r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fit.models.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-flexmix (2.3-15-2 to 2.3-15-3)
  • Migration status for r-cran-flexmix (2.3-15-2 to 2.3-15-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-flexmix r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-flexmix.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-fontquiver (0.2.1-2 to 0.2.1-3)
  • Migration status for r-cran-fontquiver (0.2.1-2 to 0.2.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fontquiver r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fontquiver.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-fpc (2.2-5-1 to 2.2-5-2)
  • Migration status for r-cran-fpc (2.2-5-1 to 2.2-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-fpc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fpc.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-futile.logger (1.4.3-3 to 1.4.3-4)
  • Migration status for r-cran-futile.logger (1.4.3-3 to 1.4.3-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-futile.logger r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-futile.logger.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-future (1.17.0+dfsg-1 to 1.17.0+dfsg-2)
  • Migration status for r-cran-future (1.17.0+dfsg-1 to 1.17.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-future r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-future.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-gclus (1.3.2-1 to 1.3.2-2)
  • Migration status for r-cran-gclus (1.3.2-1 to 1.3.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gclus r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gclus.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-genetics (1.3.8.1.2-1 to 1.3.8.1.2-2)
  • Migration status for r-cran-genetics (1.3.8.1.2-1 to 1.3.8.1.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genetics r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-genetics.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-globals (0.12.5-1 to 0.12.5-2)
  • Migration status for r-cran-globals (0.12.5-1 to 0.12.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-globals r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-globals.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-gmaps (0.2-4 to 0.2-5)
  • Migration status for r-cran-gmaps (0.2-4 to 0.2-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gmaps r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gmaps.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-googlevis (0.6.4+dfsg-1 to 0.6.4+dfsg-2)
  • Migration status for r-cran-googlevis (0.6.4+dfsg-1 to 0.6.4+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-googlevis r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-googlevis.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-gridsvg (1.7-2-1 to 1.7-2-2)
  • Migration status for r-cran-gridsvg (1.7-2-1 to 1.7-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gridsvg r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gridsvg.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-grimport2 (0.2-0-2 to 0.2-0-3)
  • Migration status for r-cran-grimport2 (0.2-0-2 to 0.2-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-grimport2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-grimport2.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-guerry (1.7.0-1 to 1.7.0-2)
  • Migration status for r-cran-guerry (1.7.0-1 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-guerry r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-guerry.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-gwidgetstcltk (- to 0.0-55.1-2)
  • Migration status for r-cran-gwidgetstcltk (- to 0.0-55.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gwidgetstcltk r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gwidgetstcltk.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-hypergeo (1.2-13-3 to 1.2-13-4)
  • Migration status for r-cran-hypergeo (1.2-13-3 to 1.2-13-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hypergeo r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-hypergeo.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-inum (1.0-1-1 to 1.0-1-2)
  • Migration status for r-cran-inum (1.0-1-1 to 1.0-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-inum r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-inum.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-isoweek (0.6-2-2 to 0.6-2-3)
  • Migration status for r-cran-isoweek (0.6-2-2 to 0.6-2-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isoweek r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-isoweek.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-itertools (0.1-3-2 to 0.1-3-3)
  • Migration status for r-cran-itertools (0.1-3-2 to 0.1-3-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-itertools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-itertools.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-knitr (1.28+dfsg-1 to 1.28+dfsg-2)
  • Migration status for r-cran-knitr (1.28+dfsg-1 to 1.28+dfsg-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-knitr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-knitr.html
  • Should wait for tests relating to r-cran-knitr 1.28+dfsg-2, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 11 days old (needed 5 days)
• r-cran-lambda.r (1.2.4-1 to 1.2.4-2)
  • Migration status for r-cran-lambda.r (1.2.4-1 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lambda.r r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lambda.r.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-lavaan (0.6.5-1 to 0.6.6-1)
  • Migration status for r-cran-lavaan (0.6.5-1 to 0.6.6-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lavaan r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lavaan.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-lifecycle (0.2.0-1 to 0.2.0-2)
  • Migration status for r-cran-lifecycle (0.2.0-1 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lifecycle r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lifecycle.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-loo (2.2.0-1 to 2.2.0-2)
  • Migration status for r-cran-loo (2.2.0-1 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-loo r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-loo.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-magic (1.5-9-1 to 1.5-9-2)
  • Migration status for r-cran-magic (1.5-9-1 to 1.5-9-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-magic r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-magic.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-maldiquantforeign (0.12-1 to 0.12-2)
  • Migration status for r-cran-maldiquantforeign (0.12-1 to 0.12-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-maldiquantforeign r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-maldiquantforeign.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-matchit (3.0.2-4 to 3.0.2-5)
  • Migration status for r-cran-matchit (3.0.2-4 to 3.0.2-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matchit r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-matchit.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-memoise (1.1.0-2 to 1.1.0-3)
  • Migration status for r-cran-memoise (1.1.0-2 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-memoise r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-memoise.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-metafor (2.4-0-1 to 2.4-0-2)
  • Migration status for r-cran-metafor (2.4-0-1 to 2.4-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metafor r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-metafor.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-misctools (0.6-26-1 to 0.6-26-2)
  • Migration status for r-cran-misctools (0.6-26-1 to 0.6-26-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-misctools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-misctools.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-mitools (2.4-1 to 2.4-2)
  • Migration status for r-cran-mitools (2.4-1 to 2.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mitools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mitools.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-mockr (0.1-2 to 0.1-3)
  • Migration status for r-cran-mockr (0.1-2 to 0.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mockr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mockr.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-multilevel (2.6-2 to 2.6-3)
  • Migration status for r-cran-multilevel (2.6-2 to 2.6-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multilevel r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-multilevel.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-munsell (0.5.0-1 to 0.5.0-2)
  • Migration status for r-cran-munsell (0.5.0-1 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-munsell r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-munsell.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-npsurv (0.4-0.1-1 to 0.4-0.1-2)
  • Migration status for r-cran-npsurv (0.4-0.1-1 to 0.4-0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-npsurv r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-npsurv.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-optparse (1.6.6-1 to 1.6.6-2)
  • Migration status for r-cran-optparse (1.6.6-1 to 1.6.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-optparse r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-optparse.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-performance (0.4.6-1 to 0.4.6-2)
  • Migration status for r-cran-performance (0.4.6-1 to 0.4.6-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-performance r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-performance.html
  • Should wait for tests relating to r-cran-performance 0.4.6-2, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 11 days old (needed 5 days)
• r-cran-plotmo (3.5.7-1 to 3.5.7-2)
  • Migration status for r-cran-plotmo (3.5.7-1 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-plotmo r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-plotmo.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-plyr (1.8.6-1 to 1.8.6-2)
  • Migration status for r-cran-plyr (1.8.6-1 to 1.8.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-plyr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-plyr.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-polycor (0.7-10-1 to 0.7-10-2)
  • Migration status for r-cran-polycor (0.7-10-1 to 0.7-10-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polycor r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-polycor.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-powerlaw (0.70.6-1 to 0.70.6-2)
  • Migration status for r-cran-powerlaw (0.70.6-1 to 0.70.6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-powerlaw r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-powerlaw.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-prabclus (2.3-2-1 to 2.3-2-2)
  • Migration status for r-cran-prabclus (2.3-2-1 to 2.3-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prabclus r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-prabclus.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-prediction (0.3.14-1 to 0.3.14-2)
  • Migration status for r-cran-prediction (0.3.14-1 to 0.3.14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prediction r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-prediction.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-prettycode (1.1.0-1 to 1.1.0-2)
  • Migration status for r-cran-prettycode (1.1.0-1 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prettycode r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-prettycode.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-psych (1.9.12.31-1 to 1.9.12.31-2)
  • Migration status for r-cran-psych (1.9.12.31-1 to 1.9.12.31-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psych r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-psych.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-pwr (1.3-0-1 to 1.3-0+dfsg-1)
  • Migration status for r-cran-pwr (1.3-0-1 to 1.3-0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pwr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pwr.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-pwt9 (9.1-0-1 to 9.1-0-2)
  • Migration status for r-cran-pwt9 (9.1-0-1 to 9.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pwt9 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pwt9.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-qqman (0.1.4-6 to 0.1.4-7)
  • Migration status for r-cran-qqman (0.1.4-6 to 0.1.4-7): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qqman r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-qqman.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-qvcalc (1.0.2-1 to 1.0.2-2)
  • Migration status for r-cran-qvcalc (1.0.2-1 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-qvcalc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-qvcalc.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-r.oo (1.23.0-1 to 1.23.0-2)
  • Migration status for r-cran-r.oo (1.23.0-1 to 1.23.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-r.oo r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-r.oo.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-r.utils (2.9.2-1 to 2.9.2-2)
  • Migration status for r-cran-r.utils (2.9.2-1 to 2.9.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-r.utils r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-r.utils.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-r2d2 (1.0-0-2 to 1.0-0-3)
  • Migration status for r-cran-r2d2 (1.0-0-2 to 1.0-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-r2d2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-r2d2.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-rcdklibs (2.3+dfsg-3 to 2.3+dfsg-4)
  • Migration status for r-cran-rcdklibs (2.3+dfsg-3 to 2.3+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcdklibs r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rcdklibs.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-rdbnomics (0.6.1-1 to 0.6.1-2)
  • Migration status for r-cran-rdbnomics (0.6.1-1 to 0.6.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rdbnomics r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rdbnomics.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-readmzxmldata (2.8.1-3 to 2.8.1-4)
  • Migration status for r-cran-readmzxmldata (2.8.1-3 to 2.8.1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readmzxmldata r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-readmzxmldata.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-rematch (1.0.1-2 to 1.0.1-3)
  • Migration status for r-cran-rematch (1.0.1-2 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-rematch r-base
  • Depends: r-cran-rematch r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rematch.html
  • 11 days old (needed 5 days)
• r-cran-reshape2 (1.4.4-1 to 1.4.4-2)
  • Migration status for r-cran-reshape2 (1.4.4-1 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-reshape2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-reshape2.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-rex (1.2.0-1 to 1.2.0-2)
  • Migration status for r-cran-rex (1.2.0-1 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rex r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rex.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-rlist (0.4.6.1-3 to 0.4.6.1-4)
  • Migration status for r-cran-rlist (0.4.6.1-3 to 0.4.6.1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rlist r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rlist.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-rngtools (1.5-1 to 1.5-2)
  • Migration status for r-cran-rngtools (1.5-1 to 1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rngtools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rngtools.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-rprojroot (1.3-2-2 to 1.3-2-3)
  • Migration status for r-cran-rprojroot (1.3-2-2 to 1.3-2-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rprojroot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rprojroot.html
  • 11 days old (needed 5 days)
• r-cran-rslurm (0.5.0-1 to 0.5.0-2)
  • Migration status for r-cran-rslurm (0.5.0-1 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rslurm r-base
  • 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
  • 11 days old (needed 2 days)
• r-cran-rsolnp (1.16+dfsg-3 to 1.16+dfsg-4)
  • Migration status for r-cran-rsolnp (1.16+dfsg-3 to 1.16+dfsg-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rsolnp r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rsolnp.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-rstudioapi (0.11-1 to 0.11-2)
  • Migration status for r-cran-rstudioapi (0.11-1 to 0.11-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-rstudioapi r-base
  • Depends: r-cran-rstudioapi r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rstudioapi.html
  • 11 days old (needed 5 days)
• r-cran-rversions (2.0.1-1 to 2.0.1-2)
  • Migration status for r-cran-rversions (2.0.1-1 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rversions r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rversions.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-scales (1.1.0-1 to 1.1.1-1)
  • Migration status for r-cran-scales (1.1.0-1 to 1.1.1-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-scales r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-scales.html
  • Should wait for tests relating to r-cran-scales 1.1.1-1, but forced by ginggs
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 11 days old (needed 5 days)
• r-cran-semtools (0.5.2-1 to 0.5.2-2)
  • Migration status for r-cran-semtools (0.5.2-1 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-semtools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-semtools.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-sendmailr (1.2-1-4 to 1.2-1-5)
  • Migration status for r-cran-sendmailr (1.2-1-4 to 1.2-1-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sendmailr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sendmailr.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-sessioninfo (1.1.1-3 to 1.1.1-4)
  • Migration status for r-cran-sessioninfo (1.1.1-3 to 1.1.1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sessioninfo r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sessioninfo.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-snakecase (0.11.0-1 to 0.11.0-2)
  • Migration status for r-cran-snakecase (0.11.0-1 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snakecase r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-snakecase.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-snowfall (1.84-6.1-2 to 1.84-6.1-3)
  • Migration status for r-cran-snowfall (1.84-6.1-2 to 1.84-6.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-snowfall r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-snowfall.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-spatstat.data (1.4-3-1 to 1.4-3-2)
  • Migration status for r-cran-spatstat.data (1.4-3-1 to 1.4-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-spatstat.data r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.data.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-stringr (1.4.0-1 to 1.4.0-2)
  • Migration status for r-cran-stringr (1.4.0-1 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-stringr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-stringr.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-timeseries (3062.100-1 to 3062.100-2)
  • Migration status for r-cran-timeseries (3062.100-1 to 3062.100-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-timeseries r-base
  • Depends: r-cran-timeseries r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-timeseries.html
  • 11 days old (needed 5 days)
• r-cran-truncdist (1.0-2-3 to 1.0-2-4)
  • Migration status for r-cran-truncdist (1.0-2-3 to 1.0-2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-truncdist r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-truncdist.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-unitizer (1.4.9-1 to 1.4.10-1)
  • Migration status for r-cran-unitizer (1.4.9-1 to 1.4.10-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-unitizer r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-unitizer.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-vioplot (0.3.4-1 to 0.3.4-2)
  • Migration status for r-cran-vioplot (0.3.4-1 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vioplot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vioplot.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-wdi (2.6.0-1 to 2.6.0-2)
  • Migration status for r-cran-wdi (2.6.0-1 to 2.6.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-wdi r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-wdi.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-cran-xopen (1.0.0-1 to 1.0.0-2)
  • Migration status for r-cran-xopen (1.0.0-1 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xopen r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-xopen.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• r-other-nitpick (2.0-6 to 2.0-7)
  • Migration status for r-other-nitpick (2.0-6 to 2.0-7): Will attempt migration (Any information below is purely informational)
  • Depends: r-other-nitpick r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-other-nitpick.html
  • Required age reduced by 3 days because of autopkgtest
  • 11 days old (needed 2 days)
• yara (3.11.0-4 to 4.0.1-1)
  • Migration status for yara (3.11.0-4 to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by bengen
  • Not built on buildd: arch all binaries uploaded by bengen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yara.html
  • 11 days old (needed 5 days)
• yara-python (3.11.0-1 to 4.0.1-1)
  • Migration status for yara-python (3.11.0-1 to 4.0.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): yara-python yara (not considered)
  • Depends: yara-python yara (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yara-python.html
  • 11 days old (needed 5 days)
• abind (1.4-5-1.2 to 1.4-5-2)
  • Migration status for abind (1.4-5-1.2 to 1.4-5-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): abind r-base
  • Depends: abind r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abind.html
  • 12 days old (needed 5 days)
• android-platform-tools-analytics-library (- to 2.2.2-3)
  • Migration status for android-platform-tools-analytics-library (- to 2.2.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): android-platform-tools-analytics-library android-platform-tools-base (not considered)
  • Depends: android-platform-tools-analytics-library android-platform-tools-base (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-tools-analytics-library.html
  • 12 days old (needed 5 days)
• boot (1.3-25-1 to 1.3-25-2)
  • Migration status for boot (1.3-25-1 to 1.3-25-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): boot r-base
  • Depends: boot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boot.html
  • 12 days old (needed 5 days)
• codetools (0.2-16-1 to 0.2-16-2)
  • Migration status for codetools (0.2-16-1 to 0.2-16-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): codetools r-base
  • Depends: codetools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/codetools.html
  • 12 days old (needed 5 days)
• dbi (1.1.0-2 to 1.1.0-3)
  • Migration status for dbi (1.1.0-2 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): dbi r-base
  • Depends: dbi r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbi.html
  • 12 days old (needed 5 days)
• direnv (2.21.2-1 to 2.21.3-1)
  • Migration status for direnv (2.21.2-1 to 2.21.3-1): 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/d/direnv.html
  • 12 days old (needed 5 days)
• gdata (2.18.0-2 to 2.18.0-3)
  • Migration status for gdata (2.18.0-2 to 2.18.0-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): gdata r-base
  • Depends: gdata r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdata.html
  • 12 days old (needed 5 days)
• gsutil (3.1-1 to 3.1-3)
  • Migration status for gsutil (3.1-1 to 3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gsutil introduces new bugs: #961381
  • autopkgtest for gsutil/3.1-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsutil.html
  • 12 days old (needed 5 days)
• idle3-tools (0.9.1-3 to 0.9.1-4)
  • Migration status for idle3-tools (0.9.1-3 to 0.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating idle3-tools introduces new bugs: #961457
  • autopkgtest for idle3-tools/0.9.1-4: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idle3-tools.html
  • 12 days old (needed 5 days)
• libbssolv-perl (- to 0.17-2)
  • Migration status for libbssolv-perl (- to 0.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): libbssolv-perl libsolv (not considered)
  • Depends: libbssolv-perl libsolv (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbssolv-perl.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• libcamera (0~git20200417+35269f0-2 to 0~git20200513+924778e-1)
  • Migration status for libcamera (0~git20200417+35269f0-2 to 0~git20200513+924778e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libcamera introduces new bugs: #960758
  • 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
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcamera.html
  • 12 days old (needed 5 days)
• meson (0.54.1-2 to 0.54.2-1)
  • Migration status for meson (0.54.1-2 to 0.54.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating meson introduces new bugs: #960877
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meson.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• misc3d (0.8-4-4 to 0.8-4-5)
  • Migration status for misc3d (0.8-4-4 to 0.8-4-5): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): misc3d r-base
  • Depends: misc3d r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/misc3d.html
  • 12 days old (needed 5 days)
• ngetty (1.1-3.1 to 1.1-5)
  • Migration status for ngetty (1.1-3.1 to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ngetty introduces new bugs: #961455
  • autopkgtest for ngetty/1.1-5: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ngetty.html
  • 12 days old (needed 5 days)
• parallel-fastq-dump (- to 0.6.6-2)
  • Migration status for parallel-fastq-dump (- to 0.6.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • parallel-fastq-dump/i386 has unsatisfiable dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parallel-fastq-dump.html
  • uninstallable on arch arm64, not running autopkgtest there
  • 12 days old (needed 5 days)
• polspline (1.1.17-1 to 1.1.19-1)
  • Migration status for polspline (1.1.17-1 to 1.1.19-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): polspline r-base
  • Depends: polspline r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polspline.html
  • 12 days old (needed 5 days)
• pwget (2016.1019+git75c6e3e-1 to 2016.1019+git75c6e3e-3)
  • Migration status for pwget (2016.1019+git75c6e3e-1 to 2016.1019+git75c6e3e-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pwget introduces new bugs: #961456
  • autopkgtest for pwget/2016.1019+git75c6e3e-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pwget.html
  • 12 days old (needed 5 days)
• r-bioc-lpsymphony (1.14.0+dfsg-2 to 1.16.0+dfsg-1)
  • Migration status for r-bioc-lpsymphony (1.14.0+dfsg-2 to 1.16.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-lpsymphony r-base
  • Depends: r-bioc-lpsymphony r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-lpsymphony.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-bioc-rhdf5lib (1.8.0+dfsg-1 to 1.10.0+dfsg1-1)
  • Migration status for r-bioc-rhdf5lib (1.8.0+dfsg-1 to 1.10.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-rhdf5lib r-base
  • Depends: r-bioc-rhdf5lib r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rhdf5lib.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-aplpack (1.3.3-1 to 1.3.3-2)
  • Migration status for r-cran-aplpack (1.3.3-1 to 1.3.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-aplpack r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-aplpack.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-assertive.base (0.0-7-3 to 0.0-7-4)
  • Migration status for r-cran-assertive.base (0.0-7-3 to 0.0-7-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-assertive.base r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-assertive.base.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-assertthat (0.2.1-1 to 0.2.1-2)
  • Migration status for r-cran-assertthat (0.2.1-1 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-assertthat r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-assertthat.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-beeswarm (0.2.3-3 to 0.2.3-4)
  • Migration status for r-cran-beeswarm (0.2.3-3 to 0.2.3-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-beeswarm r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-beeswarm.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-bigmemory.sri (0.1.3-2 to 0.1.3-3)
  • Migration status for r-cran-bigmemory.sri (0.1.3-2 to 0.1.3-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bigmemory.sri r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bigmemory.sri.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-bindr (0.1.1-2 to 0.1.1-3)
  • Migration status for r-cran-bindr (0.1.1-2 to 0.1.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-bindr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bindr.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-brew (1.0-6-3 to 1.0-6-4)
  • Migration status for r-cran-brew (1.0-6-3 to 1.0-6-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brew r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-brew.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-brobdingnag (1.2-6-1 to 1.2-6-2)
  • Migration status for r-cran-brobdingnag (1.2-6-1 to 1.2-6-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-brobdingnag r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-brobdingnag.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-ca (0.71.1-1 to 0.71.1-2)
  • Migration status for r-cran-ca (0.71.1-1 to 0.71.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ca r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ca.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-cardata (3.0.3-1 to 3.0.3-2)
  • Migration status for r-cran-cardata (3.0.3-1 to 3.0.3-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-cardata r-base
  • Depends: r-cran-cardata r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cardata.html
  • 12 days old (needed 5 days)
• r-cran-clipr (0.7.0-1 to 0.7.0-2)
  • Migration status for r-cran-clipr (0.7.0-1 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clipr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-clipr.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-clisymbols (1.2.0-1 to 1.2.0-2)
  • Migration status for r-cran-clisymbols (1.2.0-1 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-clisymbols r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-clisymbols.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-combinat (0.0-8-6 to 0.0-8-7)
  • Migration status for r-cran-combinat (0.0-8-6 to 0.0-8-7): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-combinat r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-combinat.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-corpcor (1.6.9-2 to 1.6.9-4)
  • Migration status for r-cran-corpcor (1.6.9-2 to 1.6.9-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-corpcor r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-corpcor.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-corrplot (0.84-2 to 0.84-3)
  • Migration status for r-cran-corrplot (0.84-2 to 0.84-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-corrplot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-corrplot.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-crayon (1.3.4-4 to 1.3.4-5)
  • Migration status for r-cran-crayon (1.3.4-4 to 1.3.4-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-crayon r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-crayon.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-dfoptim (2018.2-1-2 to 2018.2-1-3)
  • Migration status for r-cran-dfoptim (2018.2-1-2 to 2018.2-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dfoptim r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dfoptim.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-dichromat (1:2.0-0-2 to 1:2.0-0-3)
  • Migration status for r-cran-dichromat (1:2.0-0-2 to 1:2.0-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dichromat r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dichromat.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-discriminer (0.1-29-2 to 0.1-29-3)
  • Migration status for r-cran-discriminer (0.1-29-2 to 0.1-29-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-discriminer r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-discriminer.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-dynamictreecut (1.63-1-2 to 1.63-1-3)
  • Migration status for r-cran-dynamictreecut (1.63-1-2 to 1.63-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-dynamictreecut r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dynamictreecut.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-ellipse (0.4.1-2 to 0.4.1-3)
  • Migration status for r-cran-ellipse (0.4.1-2 to 0.4.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ellipse r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ellipse.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-ellipsis (0.3.0-1 to 0.3.1-1)
  • Migration status for r-cran-ellipsis (0.3.0-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-ellipsis r-base
  • Depends: r-cran-ellipsis r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ellipsis.html
  • 12 days old (needed 5 days)
• r-cran-epibasix (1.5-1 to 1.5-2)
  • Migration status for r-cran-epibasix (1.5-1 to 1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epibasix r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-epibasix.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-epitools (1:0.5-10.1-1 to 1:0.5-10.1-2)
  • Migration status for r-cran-epitools (1:0.5-10.1-1 to 1:0.5-10.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-epitools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-epitools.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-estimability (1.3-2 to 1.3-3)
  • Migration status for r-cran-estimability (1.3-2 to 1.3-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-estimability r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-estimability.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-evaluate (0.14-1 to 0.14-2)
  • Migration status for r-cran-evaluate (0.14-1 to 0.14-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-evaluate r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-evaluate.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-ffield (0.1.0-2 to 0.1.0-3)
  • Migration status for r-cran-ffield (0.1.0-2 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ffield r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ffield.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-foreach (1.5.0-1 to 1.5.0-2)
  • Migration status for r-cran-foreach (1.5.0-1 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-foreach r-base
  • Depends: r-cran-foreach r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-foreach.html
  • 12 days old (needed 5 days)
• r-cran-formatr (1.7-1 to 1.7-2)
  • Migration status for r-cran-formatr (1.7-1 to 1.7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-formatr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-formatr.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-formula (1.2-3-2 to 1.2-3-3)
  • Migration status for r-cran-formula (1.2-3-2 to 1.2-3-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-formula r-base
  • Depends: r-cran-formula r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-formula.html
  • 12 days old (needed 5 days)
• r-cran-futile.options (1.0.1-2 to 1.0.1-3)
  • Migration status for r-cran-futile.options (1.0.1-2 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-futile.options r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-futile.options.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-g.data (2.4-3 to 2.4-4)
  • Migration status for r-cran-g.data (2.4-3 to 2.4-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-g.data r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-g.data.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-genabel.data (1.0.0-3 to 1.0.0-4)
  • Migration status for r-cran-genabel.data (1.0.0-3 to 1.0.0-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-genabel.data r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-genabel.data.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-generics (0.0.2-2 to 0.0.2-3)
  • Migration status for r-cran-generics (0.0.2-2 to 0.0.2-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-generics r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-generics.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-getopt (1.20.3-2 to 1.20.3-3)
  • Migration status for r-cran-getopt (1.20.3-2 to 1.20.3-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-getopt r-base
  • Depends: r-cran-getopt r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-getopt.html
  • 12 days old (needed 5 days)
• r-cran-globaloptions (0.1.1-1 to 0.1.1-2)
  • Migration status for r-cran-globaloptions (0.1.1-1 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-globaloptions r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-globaloptions.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-gparotation (2014.11-1-2 to 2014.11-1-3)
  • Migration status for r-cran-gparotation (2014.11-1-2 to 2014.11-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gparotation r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gparotation.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-gridbase (0.4-7-4 to 0.4-7-5)
  • Migration status for r-cran-gridbase (0.4-7-4 to 0.4-7-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gridbase r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gridbase.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-gridextra (2.3-2 to 2.3-3)
  • Migration status for r-cran-gridextra (2.3-2 to 2.3-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-gridextra r-base
  • Depends: r-cran-gridextra r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gridextra.html
  • 12 days old (needed 5 days)
• r-cran-gridgraphics (0.5-0-1 to 0.5-0-2)
  • Migration status for r-cran-gridgraphics (0.5-0-1 to 0.5-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gridgraphics r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gridgraphics.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-gsa (1.03.1-1 to 1.03.1-2)
  • Migration status for r-cran-gsa (1.03.1-1 to 1.03.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gsa r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gsa.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-gtable (0.3.0+dfsg-1 to 0.3.0+dfsg-2)
  • Migration status for r-cran-gtable (0.3.0+dfsg-1 to 0.3.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gtable r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gtable.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-gwidgets (0.0-54.2-1 to 0.0-54.2-2)
  • Migration status for r-cran-gwidgets (0.0-54.2-1 to 0.0-54.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-gwidgets r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gwidgets.html
  • 12 days old (needed 5 days)
• r-cran-hash (2.2.6.1-2 to 2.2.6.1-3)
  • Migration status for r-cran-hash (2.2.6.1-2 to 2.2.6.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hash r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-hash.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-highr (0.8+dfsg-1 to 0.8+dfsg-2)
  • Migration status for r-cran-highr (0.8+dfsg-1 to 0.8+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-highr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-highr.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-hsaur3 (1.0-9-2 to 1.0-9-3)
  • Migration status for r-cran-hsaur3 (1.0-9-2 to 1.0-9-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hsaur3 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-hsaur3.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-httpcode (0.3.0-1 to 0.3.0-2)
  • Migration status for r-cran-httpcode (0.3.0-1 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-httpcode r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-httpcode.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-hwriter (1.3.2-3 to 1.3.2-4)
  • Migration status for r-cran-hwriter (1.3.2-3 to 1.3.2-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-hwriter r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-hwriter.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-ica (1.0-2-2 to 1.0-2-3)
  • Migration status for r-cran-ica (1.0-2-2 to 1.0-2-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ica r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ica.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-ini (0.3.1-1 to 0.3.1-2)
  • Migration status for r-cran-ini (0.3.1-1 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-ini r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ini.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-inline (0.3.15-2 to 0.3.15-3)
  • Migration status for r-cran-inline (0.3.15-2 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-inline r-base
  • Depends: r-cran-inline r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-inline.html
  • 12 days old (needed 5 days)
• r-cran-insight (0.8.3-1 to 0.8.4-1)
  • Migration status for r-cran-insight (0.8.3-1 to 0.8.4-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-insight r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-insight.html
  • Should wait for tests relating to r-cran-insight 0.8.4-1, but forced by ginggs
  • autopkgtest for r-cran-ggeffects/0.14.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjlabelled/1.1.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjmisc/2.8.4-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sjplot/2.8.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 12 days old (needed 5 days)
• r-cran-isocodes (2020.03.16-1 to 2020.03.16-2)
  • Migration status for r-cran-isocodes (2020.03.16-1 to 2020.03.16-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-isocodes r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-isocodes.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-iterators (1.0.12-1 to 1.0.12-2)
  • Migration status for r-cran-iterators (1.0.12-1 to 1.0.12-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-iterators r-base
  • Depends: r-cran-iterators r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-iterators.html
  • 12 days old (needed 5 days)
• r-cran-kedd (1.0.3-1 to 1.0.3-2)
  • Migration status for r-cran-kedd (1.0.3-1 to 1.0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-kedd r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-kedd.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-labeling (0.3-3 to 0.3-4)
  • Migration status for r-cran-labeling (0.3-3 to 0.3-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-labeling r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-labeling.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-lisreltor (0.1.4-2 to 0.1.4-3)
  • Migration status for r-cran-lisreltor (0.1.4-2 to 0.1.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-lisreltor r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lisreltor.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-listenv (0.8.0-1 to 0.8.0+dfsg-1)
  • Migration status for r-cran-listenv (0.8.0-1 to 0.8.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-listenv r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-listenv.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-logging (0.10-108-1 to 0.10-108-2)
  • Migration status for r-cran-logging (0.10-108-1 to 0.10-108-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-logging r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-logging.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-magrittr (1.5-5 to 1.5-6)
  • Migration status for r-cran-magrittr (1.5-5 to 1.5-6): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-magrittr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-magrittr.html
  • Should wait for tests relating to r-cran-magrittr 1.5-6, but forced by ginggs
  • autopkgtest for r-cran-sjmisc/2.8.4-1: amd64: Regression ♻ , arm64: Regression ♻
  • 12 days old (needed 5 days)
• r-cran-matlab (1.0.2-2 to 1.0.2-3)
  • Migration status for r-cran-matlab (1.0.2-2 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matlab r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-matlab.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-matrixcalc (1.0.3-4 to 1.0.3-5)
  • Migration status for r-cran-matrixcalc (1.0.3-4 to 1.0.3-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-matrixcalc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-matrixcalc.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-metrics (0.1.4-1 to 0.1.4-2)
  • Migration status for r-cran-metrics (0.1.4-1 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-metrics r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-metrics.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-mfilter (0.1.5-1 to 0.1.5-2)
  • Migration status for r-cran-mfilter (0.1.5-1 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-mfilter r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mfilter.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-modeldata (0.0.1-2 to 0.0.1-3)
  • Migration status for r-cran-modeldata (0.0.1-2 to 0.0.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modeldata r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-modeldata.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-modeltools (0.2-23-1 to 0.2-23-2)
  • Migration status for r-cran-modeltools (0.2-23-1 to 0.2-23-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-modeltools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-modeltools.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-multcompview (0.1-8-1 to 0.1-8-2)
  • Migration status for r-cran-multcompview (0.1-8-1 to 0.1-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-multcompview r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-multcompview.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-nlp (0.2-0-2 to 0.2-0-3)
  • Migration status for r-cran-nlp (0.2-0-2 to 0.2-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-nlp r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-nlp.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-nortest (1.0-4-2 to 1.0-4-3)
  • Migration status for r-cran-nortest (1.0-4-2 to 1.0-4-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-nortest r-base
  • Depends: r-cran-nortest r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-nortest.html
  • 12 days old (needed 5 days)
• r-cran-numderiv (2016.8-1.1-2 to 2016.8-1.1-3)
  • Migration status for r-cran-numderiv (2016.8-1.1-2 to 2016.8-1.1-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-numderiv r-base
  • Depends: r-cran-numderiv r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-numderiv.html
  • 12 days old (needed 5 days)
• r-cran-packrat (0.5.0-2 to 0.5.0-3)
  • Migration status for r-cran-packrat (0.5.0-2 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-packrat r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-packrat.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-parsetools (0.1.3-1 to 0.1.3-2)
  • Migration status for r-cran-parsetools (0.1.3-1 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-parsetools r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-parsetools.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pbapply (1.4-2-1 to 1.4-2-2)
  • Migration status for r-cran-pbapply (1.4-2-1 to 1.4-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pbapply r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pbapply.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-permute (0.9-5-1 to 0.9-5-2)
  • Migration status for r-cran-permute (0.9-5-1 to 0.9-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-permute r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-permute.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pkgcond (0.1.0-2 to 0.1.0-3)
  • Migration status for r-cran-pkgcond (0.1.0-2 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pkgcond r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pkgcond.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pkgconfig (2.0.3-1 to 2.0.3-2)
  • Migration status for r-cran-pkgconfig (2.0.3-1 to 2.0.3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pkgconfig r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pkgconfig.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pkgkitten (0.1.5-1 to 0.1.5-2)
  • Migration status for r-cran-pkgkitten (0.1.5-1 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-pkgkitten r-base
  • Depends: r-cran-pkgkitten r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pkgkitten.html
  • 12 days old (needed 5 days)
• r-cran-plogr (0.2.0-2 to 0.2.0-3)
  • Migration status for r-cran-plogr (0.2.0-2 to 0.2.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-plogr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-plogr.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-plotrix (3.7-8-1 to 3.7-8-2)
  • Migration status for r-cran-plotrix (3.7-8-1 to 3.7-8-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-plotrix r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-plotrix.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pls (2.7-2-1 to 2.7-2-2)
  • Migration status for r-cran-pls (2.7-2-1 to 2.7-2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pls r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pls.html
  • 12 days old (needed 5 days)
• r-cran-polynom (1.4-0-2 to 1.4-0-3)
  • Migration status for r-cran-polynom (1.4-0-2 to 1.4-0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-polynom r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-polynom.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-postlogic (0.1.0.1-2 to 0.1.0.1-3)
  • Migration status for r-cran-postlogic (0.1.0.1-2 to 0.1.0.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-postlogic r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-postlogic.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pracma (2.2.9-1 to 2.2.9-2)
  • Migration status for r-cran-pracma (2.2.9-1 to 2.2.9-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pracma r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pracma.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-praise (1.0.0-3 to 1.0.0-4)
  • Migration status for r-cran-praise (1.0.0-3 to 1.0.0-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-praise r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-praise.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-prettyr (2.2-3-1 to 2.2-3-2)
  • Migration status for r-cran-prettyr (2.2-3-1 to 2.2-3-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prettyr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-prettyr.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-prettyunits (1.1.1-1 to 1.1.1-2)
  • Migration status for r-cran-prettyunits (1.1.1-1 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-prettyunits r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-prettyunits.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-profilemodel (0.6.0-1 to 0.6.0-2)
  • Migration status for r-cran-profilemodel (0.6.0-1 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-profilemodel r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-profilemodel.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-proto (1.0.0-2 to 1.0.0-3)
  • Migration status for r-cran-proto (1.0.0-2 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-proto r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-proto.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-psy (1.1-4 to 1.1-5)
  • Migration status for r-cran-psy (1.1-4 to 1.1-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psy r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-psy.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-psyphy (0.1-9-2 to 0.1-9-3)
  • Migration status for r-cran-psyphy (0.1-9-2 to 0.1-9-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-psyphy r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-psyphy.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pvclust (2.2-0-1 to 2.2-0-2)
  • Migration status for r-cran-pvclust (2.2-0-1 to 2.2-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pvclust r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pvclust.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pwt (7.1.1-6 to 7.1.1-7)
  • Migration status for r-cran-pwt (7.1.1-6 to 7.1.1-7): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pwt r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pwt.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-pwt8 (8.1.1-4 to 8.1.1-5)
  • Migration status for r-cran-pwt8 (8.1.1-4 to 8.1.1-5): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-pwt8 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-pwt8.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-r.methodss3 (1.8.0-1 to 1.8.0-2)
  • Migration status for r-cran-r.methodss3 (1.8.0-1 to 1.8.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-r.methodss3 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-r.methodss3.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-rcppprogress (0.4.2-1 to 0.4.2-2)
  • Migration status for r-cran-rcppprogress (0.4.2-1 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-rcppprogress r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rcppprogress.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-readbrukerflexdata (1.8.5-2 to 1.8.5-3)
  • Migration status for r-cran-readbrukerflexdata (1.8.5-2 to 1.8.5-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-readbrukerflexdata r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-readbrukerflexdata.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-registry (0.5-1-1 to 0.5-1-2)
  • Migration status for r-cran-registry (0.5-1-1 to 0.5-1-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-registry r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-registry.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-remotes (2.1.1-3 to 2.1.1-4)
  • Migration status for r-cran-remotes (2.1.1-3 to 2.1.1-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-remotes r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-remotes.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-robumeta (2.0-2 to 2.0-3)
  • Migration status for r-cran-robumeta (2.0-2 to 2.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robumeta r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-robumeta.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-robustrankaggreg (1.1-2 to 1.1-3)
  • Migration status for r-cran-robustrankaggreg (1.1-2 to 1.1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-robustrankaggreg r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-robustrankaggreg.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-runit (0.4.32-2 to 0.4.32-3)
  • Migration status for r-cran-runit (0.4.32-2 to 0.4.32-3): Will attempt migration due to a hint (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-runit r-base
  • Depends: r-cran-runit r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-runit.html
  • Should wait for tests relating to r-cran-runit 0.4.32-3, but forced by ginggs
  • autopkgtest for r-bioc-delayedarray/0.12.3+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-cran-sp/1:1.4-1-1: amd64: Regression ♻ , arm64: Regression ♻
  • 12 days old (needed 5 days)
• r-cran-scatterplot3d (0.3-41-2 to 0.3-41-3)
  • Migration status for r-cran-scatterplot3d (0.3-41-2 to 0.3-41-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-scatterplot3d r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-scatterplot3d.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-segmented (1.1-0-1 to 1.1-0-2)
  • Migration status for r-cran-segmented (1.1-0-1 to 1.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-segmented r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-segmented.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-seroincidence (2.0.0-1 to 2.0.0-2)
  • Migration status for r-cran-seroincidence (2.0.0-1 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-seroincidence r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-seroincidence.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-setrng (2013.9-1-2 to 2013.9-1-3)
  • Migration status for r-cran-setrng (2013.9-1-2 to 2013.9-1-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-setrng r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-setrng.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-sfsmisc (1.1-7-1 to 1.1-7-2)
  • Migration status for r-cran-sfsmisc (1.1-7-1 to 1.1-7-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-sfsmisc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sfsmisc.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-shape (1.4.4-2 to 1.4.4-3)
  • Migration status for r-cran-shape (1.4.4-2 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-shape r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shape.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-splines2 (0.2.8-2 to 0.2.8-3)
  • Migration status for r-cran-splines2 (0.2.8-2 to 0.2.8-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-splines2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-splines2.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-squarem (2020.2-1 to 2020.2-2)
  • Migration status for r-cran-squarem (2020.2-1 to 2020.2-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-squarem r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-squarem.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-stabledist (0.7-1-2 to 0.7-1-3)
  • Migration status for r-cran-stabledist (0.7-1-2 to 0.7-1-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-stabledist r-base
  • Depends: r-cran-stabledist r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-stabledist.html
  • 12 days old (needed 5 days)
• r-cran-tcltk2 (1.2-11-2 to 1.2-11-3)
  • Migration status for r-cran-tcltk2 (1.2-11-2 to 1.2-11-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-tcltk2 r-base
  • Depends: r-cran-tcltk2 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tcltk2.html
  • 12 days old (needed 5 days)
• r-cran-teachingdemos (2.12-1 to 2.12-2)
  • Migration status for r-cran-teachingdemos (2.12-1 to 2.12-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-teachingdemos r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-teachingdemos.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-tensor (1.5-3 to 1.5-4)
  • Migration status for r-cran-tensor (1.5-3 to 1.5-4): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tensor r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tensor.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-testit (0.11-1 to 0.11-2)
  • Migration status for r-cran-testit (0.11-1 to 0.11-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-testit r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-testit.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-trimcluster (0.1-5-1 to 0.1-5-2)
  • Migration status for r-cran-trimcluster (0.1-5-1 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-trimcluster r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-trimcluster.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-tsne (0.1-3-2 to 0.1-3-3)
  • Migration status for r-cran-tsne (0.1-3-2 to 0.1-3-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-tsne r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tsne.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-uroot (2.1-0-1 to 2.1-0-2)
  • Migration status for r-cran-uroot (2.1-0-1 to 2.1-0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-uroot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-uroot.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-vipor (0.4.5-2 to 0.4.5-3)
  • Migration status for r-cran-vipor (0.4.5-2 to 0.4.5-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-vipor r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vipor.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-viridislite (0.3.0-3 to 0.3.0-4)
  • Migration status for r-cran-viridislite (0.3.0-3 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): r-cran-viridislite r-base
  • Depends: r-cran-viridislite r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-viridislite.html
  • 12 days old (needed 5 days)
• r-cran-whisker (0.4-1 to 0.4-2)
  • Migration status for r-cran-whisker (0.4-1 to 0.4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-whisker r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-whisker.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-withr (2.2.0-1 to 2.2.0-2)
  • Migration status for r-cran-withr (2.2.0-1 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-withr r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-withr.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-xfun (0.13-1 to 0.13-2)
  • Migration status for r-cran-xfun (0.13-1 to 0.13-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xfun r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-xfun.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-xtable (1:1.8-4-1 to 1:1.8-4-2)
  • Migration status for r-cran-xtable (1:1.8-4-1 to 1:1.8-4-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-xtable r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-xtable.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• r-cran-zeallot (0.1.0-2 to 0.1.0-3)
  • Migration status for r-cran-zeallot (0.1.0-2 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-zeallot r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-zeallot.html
  • Required age reduced by 3 days because of autopkgtest
  • 12 days old (needed 2 days)
• rcolorbrewer (1.1-2-2 to 1.1-2-3)
  • Migration status for rcolorbrewer (1.1-2-2 to 1.1-2-3): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): rcolorbrewer r-base
  • Depends: rcolorbrewer r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rcolorbrewer.html
  • 12 days old (needed 5 days)
• relimp (1.0-5-3 to 1.0-5-4)
  • Migration status for relimp (1.0-5-3 to 1.0-5-4): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): relimp r-base
  • Depends: relimp r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/relimp.html
  • 12 days old (needed 5 days)
• rodbc (1.3-16-1 to 1.3-17-1)
  • Migration status for rodbc (1.3-16-1 to 1.3-17-1): Will attempt migration (Any information below is purely informational)
  • Depends: rodbc r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rodbc.html
  • 12 days old (needed 5 days)
• snow (1:0.4.3-1 to 1:0.4.3-2)
  • Migration status for snow (1:0.4.3-1 to 1:0.4.3-2): Will attempt migration (Any information below is purely informational)
  • Build-Depends(-Arch): snow r-base
  • Depends: snow r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snow.html
  • 12 days old (needed 5 days)
• squid (4.11-2 to 4.11-5)
  • Migration status for squid (4.11-2 to 4.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating squid introduces new bugs: #958708, #960327, #960819
  • autopkgtest for squid/4.11-5: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squid.html
  • 12 days old (needed 5 days)
• tree-puzzle (5.2-11 to 5.3~rc16+dfsg-2)
  • Migration status for tree-puzzle (5.2-11 to 5.3~rc16+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tree-puzzle introduces new bugs: #960760
  • 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:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Updating tree-puzzle fixes old bugs: #951984
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tree-puzzle.html
  • 12 days old (needed 5 days)
• virtualbox (- to 6.1.8-dfsg-1)
  • Migration status for virtualbox (- to 6.1.8-dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating virtualbox introduces new bugs: #794466
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 12 days old (needed 5 days)
• virtualbox-ext-pack (- to 6.1.8-1)
  • Migration status for virtualbox-ext-pack (- to 6.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • virtualbox-ext-pack/i386 has unsatisfiable dependency
  • Depends: virtualbox-ext-pack virtualbox
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • uninstallable on arch arm64, not running autopkgtest there
  • 12 days old (needed 5 days)
• android-sdk-helper (- to 0.2)
  • Migration status for android-sdk-helper (- to 0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: android-sdk-helper android-platform-tools-base (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-sdk-helper.html
  • 13 days old (needed 5 days)
• biojava4-live (4.2.12+dfsg-2 to 4.2.12+dfsg-3)
  • Migration status for biojava4-live (4.2.12+dfsg-2 to 4.2.12+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by olivier.sallou@irisa.fr, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biojava4-live.html
  • 13 days old (needed 5 days)
• fever (1.0.8-4 to 1.0.9-2)
  • Migration status for fever (1.0.8-4 to 1.0.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • fever/mipsel has unsatisfiable Built-Using on golang-1.13 1.13.1-1
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fever.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• firefox (- to 76.0.1-2)
  • Migration status for firefox (- to 76.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating firefox introduces new bugs: #817954, #871947, #888423, #909286, #915582
  • firefox unsatisfiable Build-Depends(-Arch) on mips64el: libnss3-dev (>= 2:3.51.1~)
  • firefox unsatisfiable Build-Depends(-Arch) on s390x: libnss3-dev (>= 2:3.51.1~)
  • missing build on mips64el
  • missing build on mipsel
  • missing build on s390x
  • Build-Depends(-Arch): firefox nss
  • Depends: firefox nss
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox.html
  • 13 days old (needed 5 days)
• mate-hud (- to 19.10.1-3)
  • Migration status for mate-hud (- to 19.10.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: mate-hud vala-panel-appmenu (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-hud.html
  • 13 days old (needed 5 days)
• openrc (0.40.3-1 to 0.42-1)
  • Migration status for openrc (0.40.3-1 to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by heroxbd@gentoo.org
  • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/o/openrc.html
  • Additional info:
  • 13 days old (needed 5 days)
• python-biopython (1.76+dfsg-1 to 1.76+dfsg-2)
  • Migration status for python-biopython (1.76+dfsg-1 to 1.76+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-biopython introduces new bugs: #960756
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • Additional info:
  • Updating python-biopython fixes old bugs: #959587
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-biopython.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• python3-stdlib-extensions (3.8.2-2 to 3.8.3-2)
  • Migration status for python3-stdlib-extensions (3.8.2-2 to 3.8.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python3.7/3.7.7-1: amd64: Regression ♻ , arm64: Regression ♻
  • migrating python3-tk/3.8.3-2/amd64 to testing makes idle-python3.7/3.7.7-1/amd64 uninstallable
  • migrating python3-tk/3.8.3-2/i386 to testing makes idle-python3.7/3.7.7-1/i386 uninstallable
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3-stdlib-extensions.html
  • 13 days old (needed 5 days)
• r-bioc-biobase (2.46.0-1 to 2.48.0-1)
  • Migration status for r-bioc-biobase (2.46.0-1 to 2.48.0-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-bioc-biobase r-base
  • Depends: r-bioc-biobase r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biobase.html
  • Should wait for tests relating to r-bioc-biobase 2.48.0-1, but forced by ginggs
  • autopkgtest for r-bioc-deseq2/1.26.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • autopkgtest for r-bioc-multiassayexperiment/1.12.6+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • 13 days old (needed 5 days)
• r-bioc-biocversion (3.10.1-3 to 3.11.1-1)
  • Migration status for r-bioc-biocversion (3.10.1-3 to 3.11.1-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-biocversion r-base
  • Depends: r-bioc-biocversion r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biocversion.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-dnacopy (1.60.0-1 to 1.62.0-1)
  • Migration status for r-bioc-dnacopy (1.60.0-1 to 1.62.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-dnacopy r-base
  • Depends: r-bioc-dnacopy r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dnacopy.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-genomeinfodbdata (1.2.2-1 to 1.2.3-1)
  • Migration status for r-bioc-genomeinfodbdata (1.2.2-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-genomeinfodbdata r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomeinfodbdata.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-impute (1.60.0-1 to 1.62.0-1)
  • Migration status for r-bioc-impute (1.60.0-1 to 1.62.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-impute r-base
  • Depends: r-bioc-impute r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-impute.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-limma (3.42.2+dfsg-2 to 3.44.1+dfsg-1)
  • Migration status for r-bioc-limma (3.42.2+dfsg-2 to 3.44.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-limma r-base
  • Depends: r-bioc-limma r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-limma.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-mergeomics (1.14.0-1 to 1.16.0-1)
  • Migration status for r-bioc-mergeomics (1.14.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-mergeomics r-base
  • Depends: r-bioc-mergeomics r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-mergeomics.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-preprocesscore (1.48.0-1 to 1.50.0-1)
  • Migration status for r-bioc-preprocesscore (1.48.0-1 to 1.50.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-preprocesscore r-base
  • Depends: r-bioc-preprocesscore r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-preprocesscore.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-protgenerics (1.18.0-1 to 1.20.0-1)
  • Migration status for r-bioc-protgenerics (1.18.0-1 to 1.20.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-protgenerics r-base
  • Depends: r-bioc-protgenerics r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-protgenerics.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-seqlogo (1.52.0-1 to 1.54.3-1)
  • Migration status for r-bioc-seqlogo (1.52.0-1 to 1.54.3-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-seqlogo r-base
  • Depends: r-bioc-seqlogo r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-seqlogo.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-bioc-tximport (1.14.2+dfsg-1 to 1.16.0+dfsg-1)
  • Migration status for r-bioc-tximport (1.14.2+dfsg-1 to 1.16.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-tximport r-base
  • Depends: r-bioc-tximport r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tximport.html
  • 13 days old (needed 5 days)
• r-bioc-zlibbioc (1.32.0+dfsg-1 to 1.34.0+dfsg-1)
  • Migration status for r-bioc-zlibbioc (1.32.0+dfsg-1 to 1.34.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-zlibbioc r-base
  • Depends: r-bioc-zlibbioc r-bioc-biocgenerics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-zlibbioc.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-cran-biocmanager (1.30.10+dfsg-1 to 1.30.10+dfsg-2)
  • Migration status for r-cran-biocmanager (1.30.10+dfsg-1 to 1.30.10+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-biocmanager r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-biocmanager.html
  • Required age reduced by 3 days because of autopkgtest
  • 13 days old (needed 2 days)
• r-cran-r6 (2.4.1-1 to 2.4.1-2)
  • Migration status for r-cran-r6 (2.4.1-1 to 2.4.1-2): Will attempt migration due to a hint (Any information below is purely informational)
  • Depends: r-cran-r6 r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-r6.html
  • Should wait for tests relating to r-cran-r6 2.4.1-2, but forced by ginggs
  • autopkgtest for r-cran-httpuv/1.5.2+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • 13 days old (needed 5 days)
• golang-github-pzhin-go-sophia (0.0~git20191015.0.afcd224-1 to 0.0~git20191015.0.afcd224-4)
  • Migration status for golang-github-pzhin-go-sophia (0.0~git20191015.0.afcd224-1 to 0.0~git20191015.0.afcd224-4): 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/g/golang-github-pzhin-go-sophia.html
  • Required age reduced by 3 days because of autopkgtest
  • 14 days old (needed 2 days)
• libvirt (6.0.0-6 to 6.0.0-7)
  • Migration status for libvirt (6.0.0-6 to 6.0.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libvirt introduces new bugs: #960762
  • missing build on i386
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvirt.html
  • 14 days old (needed 5 days)
• neutron-dynamic-routing (2:15.0.0-3 to 2:16.0.0-1)
  • Migration status for neutron-dynamic-routing (2:15.0.0-3 to 2:16.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/n/neutron-dynamic-routing.html
  • Additional info:
  • 14 days old (needed 5 days)
• neutron-vpnaas (2:15.0.0-2 to 2:16.0.0-1)
  • Migration status for neutron-vpnaas (2:15.0.0-2 to 2:16.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/n/neutron-vpnaas.html
  • Additional info:
  • 14 days old (needed 5 days)
• r-bioc-biocgenerics (0.32.0-1 to 0.34.0-1)
  • Migration status for r-bioc-biocgenerics (0.32.0-1 to 0.34.0-1): Will attempt migration (Any information below is purely informational)
  • Depends: r-bioc-biocgenerics r-base
  • Implicit dependency: r-bioc-biocgenerics r-bioc-affy
  • Implicit dependency: r-bioc-biocgenerics r-bioc-affyio
  • Implicit dependency: r-bioc-biocgenerics r-bioc-all
  • Implicit dependency: r-bioc-biocgenerics r-bioc-annotate
  • Implicit dependency: r-bioc-biocgenerics r-bioc-annotationdbi
  • Implicit dependency: r-bioc-biocgenerics r-bioc-annotationfilter
  • Implicit dependency: r-bioc-biocgenerics r-bioc-annotationhub
  • Implicit dependency: r-bioc-biocgenerics r-bioc-aroma.light
  • Implicit dependency: r-bioc-biocgenerics r-bioc-biobase
  • Implicit dependency: r-bioc-biocgenerics r-bioc-biocfilecache
  • Implicit dependency: r-bioc-biocgenerics r-bioc-biocparallel
  • Implicit dependency: r-bioc-biocgenerics r-bioc-biocversion
  • Implicit dependency: r-bioc-biocgenerics r-bioc-biomart
  • Implicit dependency: r-bioc-biocgenerics r-bioc-biomformat
  • Implicit dependency: r-bioc-biocgenerics r-bioc-biostrings
  • Implicit dependency: r-bioc-biocgenerics r-bioc-biovizbase
  • Implicit dependency: r-bioc-biocgenerics r-bioc-bitseq
  • Implicit dependency: r-bioc-biocgenerics r-bioc-bladderbatch
  • Implicit dependency: r-bioc-biocgenerics r-bioc-bsgenome
  • Implicit dependency: r-bioc-biocgenerics r-bioc-cner
  • Implicit dependency: r-bioc-biocgenerics r-bioc-consensusclusterplus
  • Implicit dependency: r-bioc-biocgenerics r-bioc-ctc
  • Implicit dependency: r-bioc-biocgenerics r-bioc-cummerbund
  • Implicit dependency: r-bioc-biocgenerics r-bioc-dada2
  • Implicit dependency: r-bioc-biocgenerics r-bioc-delayedarray
  • Implicit dependency: r-bioc-biocgenerics r-bioc-deseq
  • Implicit dependency: r-bioc-biocgenerics r-bioc-deseq2
  • Implicit dependency: r-bioc-biocgenerics r-bioc-dirichletmultinomial
  • Implicit dependency: r-bioc-biocgenerics r-bioc-dnacopy
  • Implicit dependency: r-bioc-biocgenerics r-bioc-ebseq
  • Implicit dependency: r-bioc-biocgenerics r-bioc-edaseq
  • Implicit dependency: r-bioc-biocgenerics r-bioc-edger
  • Implicit dependency: r-bioc-biocgenerics r-bioc-ensembldb
  • Implicit dependency: r-bioc-biocgenerics r-bioc-genefilter
  • Implicit dependency: r-bioc-biocgenerics r-bioc-genelendatabase
  • Implicit dependency: r-bioc-biocgenerics r-bioc-geneplotter
  • Implicit dependency: r-bioc-biocgenerics r-bioc-genomeinfodb
  • Implicit dependency: r-bioc-biocgenerics r-bioc-genomicalignments
  • Implicit dependency: r-bioc-biocgenerics r-bioc-genomicfeatures
  • Implicit dependency: r-bioc-biocgenerics r-bioc-genomicranges
  • Implicit dependency: r-bioc-biocgenerics r-bioc-geoquery
  • Implicit dependency: r-bioc-biocgenerics r-bioc-gosemsim
  • Implicit dependency: r-bioc-biocgenerics r-bioc-goseq
  • Implicit dependency: r-bioc-biocgenerics r-bioc-gviz
  • Implicit dependency: r-bioc-biocgenerics r-bioc-hilbertvis
  • Implicit dependency: r-bioc-biocgenerics r-bioc-htsfilter
  • Implicit dependency: r-bioc-biocgenerics r-bioc-ihw
  • Implicit dependency: r-bioc-biocgenerics r-bioc-impute
  • Implicit dependency: r-bioc-biocgenerics r-bioc-interactivedisplaybase
  • Implicit dependency: r-bioc-biocgenerics r-bioc-iranges
  • Implicit dependency: r-bioc-biocgenerics r-bioc-keggrest
  • Implicit dependency: r-bioc-biocgenerics r-bioc-limma
  • Implicit dependency: r-bioc-biocgenerics r-bioc-lpsymphony
  • Implicit dependency: r-bioc-biocgenerics r-bioc-makecdfenv
  • Implicit dependency: r-bioc-biocgenerics r-bioc-mergeomics
  • Implicit dependency: r-bioc-biocgenerics r-bioc-metagenomeseq
  • Implicit dependency: r-bioc-biocgenerics r-bioc-multiassayexperiment
  • Implicit dependency: r-bioc-biocgenerics r-bioc-multtest
  • Implicit dependency: r-bioc-biocgenerics r-bioc-nanostringqcpro
  • Implicit dependency: r-bioc-biocgenerics r-bioc-pcamethods
  • Implicit dependency: r-bioc-biocgenerics r-bioc-phyloseq
  • Implicit dependency: r-bioc-biocgenerics r-bioc-preprocesscore
  • Implicit dependency: r-bioc-biocgenerics r-bioc-protgenerics
  • Implicit dependency: r-bioc-biocgenerics r-bioc-pwmenrich
  • Implicit dependency: r-bioc-biocgenerics r-bioc-qusage
  • Implicit dependency: r-bioc-biocgenerics r-bioc-qvalue
  • Implicit dependency: r-bioc-biocgenerics r-bioc-rgsepd
  • Implicit dependency: r-bioc-biocgenerics r-bioc-rhdf5
  • Implicit dependency: r-bioc-biocgenerics r-bioc-rhdf5lib
  • Implicit dependency: r-bioc-biocgenerics r-bioc-rhtslib
  • Implicit dependency: r-bioc-biocgenerics r-bioc-rots
  • Implicit dependency: r-bioc-biocgenerics r-bioc-rsamtools
  • Implicit dependency: r-bioc-biocgenerics r-bioc-rtracklayer
  • Implicit dependency: r-bioc-biocgenerics r-bioc-s4vectors
  • Implicit dependency: r-bioc-biocgenerics r-bioc-savr
  • Implicit dependency: r-bioc-biocgenerics r-bioc-seqlogo
  • Implicit dependency: r-bioc-biocgenerics r-bioc-shortread
  • Implicit dependency: r-bioc-biocgenerics r-bioc-snpstats
  • Implicit dependency: r-bioc-biocgenerics r-bioc-summarizedexperiment
  • Implicit dependency: r-bioc-biocgenerics r-bioc-tfbstools
  • Implicit dependency: r-bioc-biocgenerics r-bioc-tximport
  • Implicit dependency: r-bioc-biocgenerics r-bioc-variantannotation
  • Implicit dependency: r-bioc-biocgenerics r-bioc-wrench
  • Implicit dependency: r-bioc-biocgenerics r-bioc-xvector
  • Implicit dependency: r-bioc-biocgenerics r-bioc-zlibbioc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biocgenerics.html
  • Required age reduced by 3 days because of autopkgtest
  • 14 days old (needed 2 days)
• dmarcts-report-parser (- to 1.0+git20190809.1.bb5dd8b6-3)
  • Migration status for dmarcts-report-parser (- to 1.0+git20190809.1.bb5dd8b6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dmarcts-report-parser.html
  • 15 days old (needed 5 days)
• drmaa (- to 0.7.9-2)
  • Migration status for drmaa (- to 0.7.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for drmaa/0.7.9-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drmaa.html
  • 15 days old (needed 5 days)
• grml-debootstrap (0.90 to 0.91)
  • Migration status for grml-debootstrap (0.90 to 0.91): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mika, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grml-debootstrap.html
  • 15 days old (needed 5 days)
• mixxx (- to 2.2.3~dfsg-1.1)
  • Migration status for mixxx (- to 2.2.3~dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mixxx introduces new bugs: #950131
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mixxx.html
  • 15 days old (needed 5 days)
• php-horde-argv (- to 2.1.0-5)
  • Migration status for php-horde-argv (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-argv/2.1.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-argv php-horde-cli
  • Depends: php-horde-argv php-horde-exception
  • Depends: php-horde-argv php-horde-translation
  • Depends: php-horde-argv php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-argv.html
  • 15 days old (needed 5 days)
• php-horde-crypt (- to 2.7.12-3)
  • Migration status for php-horde-crypt (- to 2.7.12-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-crypt/2.7.12-3: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-crypt php-horde-exception
  • Depends: php-horde-crypt php-horde-http
  • Depends: php-horde-crypt php-horde-mime
  • Depends: php-horde-crypt php-horde-stream
  • Depends: php-horde-crypt php-horde-stream-filter
  • Depends: php-horde-crypt php-horde-translation
  • Depends: php-horde-crypt php-horde-url
  • Depends: php-horde-crypt php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-crypt.html
  • 15 days old (needed 5 days)
• php-horde-date-parser (- to 2.0.6-5)
  • Migration status for php-horde-date-parser (- to 2.0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-date-parser/2.0.6-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-date-parser php-horde-date
  • Depends: php-horde-date-parser php-horde-support
  • Depends: php-horde-date-parser php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-date-parser.html
  • 15 days old (needed 5 days)
• php-horde-editor (- to 2.0.5+debian0-4)
  • Migration status for php-horde-editor (- to 2.0.5+debian0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-editor/amd64 has unsatisfiable dependency
  • php-horde-editor/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): php-horde-editor php-horde-role
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-editor.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 15 days old (needed 5 days)
• php-horde-http (- to 2.1.7-5)
  • Migration status for php-horde-http (- to 2.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-http/2.1.7-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-http php-horde-exception
  • Depends: php-horde-http php-horde-support
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-http.html
  • 15 days old (needed 5 days)
• php-horde-image (- to 2.6.0-2)
  • Migration status for php-horde-image (- to 2.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-image/2.6.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-image php-horde-exception
  • Depends: php-horde-image php-horde-stream
  • Depends: php-horde-image php-horde-support
  • Depends: php-horde-image php-horde-translation
  • Depends: php-horde-image php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-image.html
  • 15 days old (needed 5 days)
• php-horde-itip (- to 2.1.2-6)
  • Migration status for php-horde-itip (- to 2.1.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-itip/2.1.2-6: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-itip php-horde-icalendar
  • Depends: php-horde-itip php-horde-mime
  • Depends: php-horde-itip php-horde-translation
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-itip.html
  • 15 days old (needed 5 days)
• php-horde-listheaders (- to 1.2.5-5)
  • Migration status for php-horde-listheaders (- to 1.2.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-listheaders/1.2.5-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-listheaders php-horde-mail
  • Depends: php-horde-listheaders php-horde-translation
  • Depends: php-horde-listheaders php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-listheaders.html
  • 15 days old (needed 5 days)
• php-horde-mail-autoconfig (- to 1.0.3-6)
  • Migration status for php-horde-mail-autoconfig (- to 1.0.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-mail-autoconfig/amd64 has unsatisfiable dependency
  • php-horde-mail-autoconfig/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-mail-autoconfig.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 15 days old (needed 5 days)
• php-horde-mime-viewer (- to 2.2.2+debian0-1)
  • Migration status for php-horde-mime-viewer (- to 2.2.2+debian0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-mime-viewer/2.2.2+debian0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): php-horde-mime-viewer php-horde-role
  • Depends: php-horde-mime-viewer php-horde-browser
  • Depends: php-horde-mime-viewer php-horde-compress
  • Depends: php-horde-mime-viewer php-horde-exception
  • Depends: php-horde-mime-viewer php-horde-mime
  • Depends: php-horde-mime-viewer php-horde-text-filter
  • Depends: php-horde-mime-viewer php-horde-text-flowed
  • Depends: php-horde-mime-viewer php-horde-translation
  • Depends: php-horde-mime-viewer php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mime-viewer.html
  • 15 days old (needed 5 days)
• php-horde-pack (- to 1.0.7-5)
  • Migration status for php-horde-pack (- to 1.0.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-pack/1.0.7-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-pack php-horde-compress-fast
  • Depends: php-horde-pack php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-pack.html
  • 15 days old (needed 5 days)
• php-horde-queue (- to 1.1.5-5)
  • Migration status for php-horde-queue (- to 1.1.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-queue.html
  • 15 days old (needed 5 days)
• php-horde-rdo (- to 2.1.0-5)
  • Migration status for php-horde-rdo (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-rdo/2.1.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-rdo php-horde-db
  • Depends: php-horde-rdo php-horde-exception
  • Depends: php-horde-rdo php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rdo.html
  • 15 days old (needed 5 days)
• php-horde-routes (- to 2.0.5-7)
  • Migration status for php-horde-routes (- to 2.0.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-routes/2.0.5-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-routes php-horde-exception
  • Depends: php-horde-routes php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-routes.html
  • 15 days old (needed 5 days)
• php-horde-rpc (- to 2.1.8-5)
  • Migration status for php-horde-rpc (- to 2.1.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • php-horde-rpc/amd64 has unsatisfiable dependency
  • php-horde-rpc/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-horde-rpc.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 15 days old (needed 5 days)
• php-horde-smtp (- to 1.9.5-5)
  • Migration status for php-horde-smtp (- to 1.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-smtp/1.9.5-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-smtp php-horde-exception
  • Depends: php-horde-smtp php-horde-mail
  • Depends: php-horde-smtp php-horde-socket-client
  • Depends: php-horde-smtp php-horde-support
  • Depends: php-horde-smtp php-horde-translation
  • Depends: php-horde-smtp php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-smtp.html
  • 15 days old (needed 5 days)
• php-horde-socket-client (- to 2.1.2-3)
  • Migration status for php-horde-socket-client (- to 2.1.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-socket-client php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-socket-client.html
  • 15 days old (needed 5 days)
• php-horde-spellchecker (- to 2.1.3-7)
  • Migration status for php-horde-spellchecker (- to 2.1.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-spellchecker/2.1.3-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-spellchecker php-horde-exception
  • Depends: php-horde-spellchecker php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-spellchecker.html
  • 15 days old (needed 5 days)
• php-horde-text-diff (- to 2.2.0-5)
  • Migration status for php-horde-text-diff (- to 2.2.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-text-diff/2.2.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-text-diff php-horde-exception
  • Depends: php-horde-text-diff php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-text-diff.html
  • 15 days old (needed 5 days)
• php-horde-timezone (- to 1.1.0-5)
  • Migration status for php-horde-timezone (- to 1.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-timezone/1.1.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-timezone php-horde-date
  • Depends: php-horde-timezone php-horde-icalendar
  • Depends: php-horde-timezone php-horde-vfs
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-timezone.html
  • 15 days old (needed 5 days)
• php-horde-tree (- to 2.0.5-5)
  • Migration status for php-horde-tree (- to 2.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-tree php-horde-exception
  • Depends: php-horde-tree php-horde-url
  • Depends: php-horde-tree php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-tree.html
  • 15 days old (needed 5 days)
• php-horde-vfs (- to 2.4.0-5)
  • Migration status for php-horde-vfs (- to 2.4.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-vfs/2.4.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-vfs php-horde-exception
  • Depends: php-horde-vfs php-horde-translation
  • Depends: php-horde-vfs php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-vfs.html
  • 15 days old (needed 5 days)
• php-horde-xml-element (- to 2.0.4-7)
  • Migration status for php-horde-xml-element (- to 2.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-xml-element/2.0.4-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-xml-element php-horde-exception
  • Depends: php-horde-xml-element php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-xml-element.html
  • 15 days old (needed 5 days)
• python-tornado (6.0.3+really5.1.1-3 to 6.0.4-2)
  • Migration status for python-tornado (6.0.3+really5.1.1-3 to 6.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • migrating python3-tornado/6.0.4-2/amd64 to testing makes mitmproxy/4.0.4-6.1/amd64 uninstallable
  • migrating python3-tornado/6.0.4-2/i386 to testing makes mitmproxy/4.0.4-6.1/i386 uninstallable
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tornado.html
  • Required age reduced by 3 days because of autopkgtest
  • 15 days old (needed 2 days)
• r-base (3.6.3-2 to 4.0.0-3)
  • Migration status for r-base (3.6.3-2 to 4.0.0-3): Will attempt migration (Any information below is purely informational)
  • Implicit dependency: r-base abind
  • Implicit dependency: r-base acepack/amd64
  • Implicit dependency: r-base acepack/arm64
  • Implicit dependency: r-base acepack/armel
  • Implicit dependency: r-base acepack/armhf
  • Implicit dependency: r-base acepack/i386
  • Implicit dependency: r-base acepack/mips64el
  • Implicit dependency: r-base acepack/mipsel
  • Implicit dependency: r-base acepack/ppc64el
  • Implicit dependency: r-base acepack/s390x
  • Implicit dependency: r-base boot
  • Implicit dependency: r-base cairodevice/amd64
  • Implicit dependency: r-base cairodevice/arm64
  • Implicit dependency: r-base cairodevice/armel
  • Implicit dependency: r-base cairodevice/armhf
  • Implicit dependency: r-base cairodevice/i386
  • Implicit dependency: r-base cairodevice/mips64el
  • Implicit dependency: r-base cairodevice/mipsel
  • Implicit dependency: r-base cairodevice/ppc64el
  • Implicit dependency: r-base cairodevice/s390x
  • Implicit dependency: r-base car
  • Implicit dependency: r-base chron/amd64
  • Implicit dependency: r-base chron/arm64
  • Implicit dependency: r-base chron/armel
  • Implicit dependency: r-base chron/armhf
  • Implicit dependency: r-base chron/i386
  • Implicit dependency: r-base chron/mips64el
  • Implicit dependency: r-base chron/mipsel
  • Implicit dependency: r-base chron/ppc64el
  • Implicit dependency: r-base chron/s390x
  • Implicit dependency: r-base cluster/amd64
  • Implicit dependency: r-base cluster/arm64
  • Implicit dependency: r-base cluster/armel
  • Implicit dependency: r-base cluster/armhf
  • Implicit dependency: r-base cluster/i386
  • Implicit dependency: r-base cluster/mips64el
  • Implicit dependency: r-base cluster/mipsel
  • Implicit dependency: r-base cluster/ppc64el
  • Implicit dependency: r-base cluster/s390x
  • Implicit dependency: r-base codetools
  • Implicit dependency: r-base date/amd64
  • Implicit dependency: r-base date/arm64
  • Implicit dependency: r-base date/armel
  • Implicit dependency: r-base date/armhf
  • Implicit dependency: r-base date/i386
  • Implicit dependency: r-base date/mips64el
  • Implicit dependency: r-base date/mipsel
  • Implicit dependency: r-base date/ppc64el
  • Implicit dependency: r-base date/s390x
  • Implicit dependency: r-base dbi
  • Implicit dependency: r-base effects
  • Implicit dependency: r-base fasianoptions/amd64
  • Implicit dependency: r-base fasianoptions/arm64
  • Implicit dependency: r-base fasianoptions/armel
  • Implicit dependency: r-base fasianoptions/armhf
  • Implicit dependency: r-base fasianoptions/i386
  • Implicit dependency: r-base fasianoptions/mips64el
  • Implicit dependency: r-base fasianoptions/mipsel
  • Implicit dependency: r-base fasianoptions/ppc64el
  • Implicit dependency: r-base fasianoptions/s390x
  • Implicit dependency: r-base fassets/amd64
  • Implicit dependency: r-base fassets/arm64
  • Implicit dependency: r-base fassets/armel
  • Implicit dependency: r-base fassets/armhf
  • Implicit dependency: r-base fassets/i386
  • Implicit dependency: r-base fassets/mips64el
  • Implicit dependency: r-base fassets/mipsel
  • Implicit dependency: r-base fassets/ppc64el
  • Implicit dependency: r-base fassets/s390x
  • Implicit dependency: r-base fbasics/amd64
  • Implicit dependency: r-base fbasics/arm64
  • Implicit dependency: r-base fbasics/armel
  • Implicit dependency: r-base fbasics/armhf
  • Implicit dependency: r-base fbasics/i386
  • Implicit dependency: r-base fbasics/mips64el
  • Implicit dependency: r-base fbasics/mipsel
  • Implicit dependency: r-base fbasics/ppc64el
  • Implicit dependency: r-base fbasics/s390x
  • Implicit dependency: r-base fbonds
  • Implicit dependency: r-base fcopulae/amd64
  • Implicit dependency: r-base fcopulae/arm64
  • Implicit dependency: r-base fcopulae/armel
  • Implicit dependency: r-base fcopulae/armhf
  • Implicit dependency: r-base fcopulae/i386
  • Implicit dependency: r-base fcopulae/mips64el
  • Implicit dependency: r-base fcopulae/mipsel
  • Implicit dependency: r-base fcopulae/ppc64el
  • Implicit dependency: r-base fcopulae/s390x
  • Implicit dependency: r-base fexoticoptions
  • Implicit dependency: r-base fextremes
  • Implicit dependency: r-base fgarch/amd64
  • Implicit dependency: r-base fgarch/arm64
  • Implicit dependency: r-base fgarch/armel
  • Implicit dependency: r-base fgarch/armhf
  • Implicit dependency: r-base fgarch/i386
  • Implicit dependency: r-base fgarch/mips64el
  • Implicit dependency: r-base fgarch/mipsel
  • Implicit dependency: r-base fgarch/ppc64el
  • Implicit dependency: r-base fgarch/s390x
  • Implicit dependency: r-base fimport
  • Implicit dependency: r-base fmultivar
  • Implicit dependency: r-base fnonlinear/amd64
  • Implicit dependency: r-base fnonlinear/arm64
  • Implicit dependency: r-base fnonlinear/armel
  • Implicit dependency: r-base fnonlinear/armhf
  • Implicit dependency: r-base fnonlinear/i386
  • Implicit dependency: r-base fnonlinear/mips64el
  • Implicit dependency: r-base fnonlinear/mipsel
  • Implicit dependency: r-base fnonlinear/ppc64el
  • Implicit dependency: r-base fnonlinear/s390x
  • Implicit dependency: r-base foptions/amd64
  • Implicit dependency: r-base foptions/arm64
  • Implicit dependency: r-base foptions/armel
  • Implicit dependency: r-base foptions/armhf
  • Implicit dependency: r-base foptions/i386
  • Implicit dependency: r-base foptions/mips64el
  • Implicit dependency: r-base foptions/mipsel
  • Implicit dependency: r-base foptions/ppc64el
  • Implicit dependency: r-base foptions/s390x
  • Implicit dependency: r-base foreign
  • Implicit dependency: r-base fportfolio/amd64
  • Implicit dependency: r-base fportfolio/arm64
  • Implicit dependency: r-base fportfolio/armel
  • Implicit dependency: r-base fportfolio/armhf
  • Implicit dependency: r-base fportfolio/i386
  • Implicit dependency: r-base fportfolio/mips64el
  • Implicit dependency: r-base fportfolio/mipsel
  • Implicit dependency: r-base fportfolio/ppc64el
  • Implicit dependency: r-base fportfolio/s390x
  • Implicit dependency: r-base fregression/amd64
  • Implicit dependency: r-base fregression/arm64
  • Implicit dependency: r-base fregression/armel
  • Implicit dependency: r-base fregression/armhf
  • Implicit dependency: r-base fregression/i386
  • Implicit dependency: r-base fregression/mips64el
  • Implicit dependency: r-base fregression/mipsel
  • Implicit dependency: r-base fregression/ppc64el
  • Implicit dependency: r-base fregression/s390x
  • Implicit dependency: r-base ftrading
  • Implicit dependency: r-base funitroots/amd64
  • Implicit dependency: r-base funitroots/arm64
  • Implicit dependency: r-base funitroots/armel
  • Implicit dependency: r-base funitroots/armhf
  • Implicit dependency: r-base funitroots/i386
  • Implicit dependency: r-base funitroots/mips64el
  • Implicit dependency: r-base funitroots/mipsel
  • Implicit dependency: r-base funitroots/ppc64el
  • Implicit dependency: r-base funitroots/s390x
  • Implicit dependency: r-base gdata
  • Implicit dependency: r-base gmodels
  • Implicit dependency: r-base gplots
  • Implicit dependency: r-base gtools/amd64
  • Implicit dependency: r-base gtools/arm64
  • Implicit dependency: r-base gtools/armel
  • Implicit dependency: r-base gtools/armhf
  • Implicit dependency: r-base gtools/i386
  • Implicit dependency: r-base gtools/mips64el
  • Implicit dependency: r-base gtools/mipsel
  • Implicit dependency: r-base gtools/ppc64el
  • Implicit dependency: r-base gtools/s390x
  • Implicit dependency: r-base hmisc/amd64
  • Implicit dependency: r-base hmisc/arm64
  • Implicit dependency: r-base hmisc/armhf
  • Implicit dependency: r-base hmisc/i386
  • Implicit dependency: r-base hmisc/mips64el
  • Implicit dependency: r-base hmisc/mipsel
  • Implicit dependency: r-base hmisc/ppc64el
  • Implicit dependency: r-base hmisc/s390x
  • Implicit dependency: r-base its
  • Implicit dependency: r-base kernsmooth/amd64
  • Implicit dependency: r-base kernsmooth/arm64
  • Implicit dependency: r-base kernsmooth/armel
  • Implicit dependency: r-base kernsmooth/armhf
  • Implicit dependency: r-base kernsmooth/i386
  • Implicit dependency: r-base kernsmooth/mips64el
  • Implicit dependency: r-base kernsmooth/mipsel
  • Implicit dependency: r-base kernsmooth/ppc64el
  • Implicit dependency: r-base kernsmooth/s390x
  • Implicit dependency: r-base lattice/amd64
  • Implicit dependency: r-base lattice/arm64
  • Implicit dependency: r-base lattice/armel
  • Implicit dependency: r-base lattice/armhf
  • Implicit dependency: r-base lattice/i386
  • Implicit dependency: r-base lattice/mips64el
  • Implicit dependency: r-base lattice/mipsel
  • Implicit dependency: r-base lattice/ppc64el
  • Implicit dependency: r-base lattice/s390x
  • Implicit dependency: r-base latticeextra
  • Implicit dependency: r-base littler/amd64
  • Implicit dependency: r-base littler/arm64
  • Implicit dependency: r-base littler/armel
  • Implicit dependency: r-base littler/armhf
  • Implicit dependency: r-base littler/i386
  • Implicit dependency: r-base littler/mips64el
  • Implicit dependency: r-base littler/mipsel
  • Implicit dependency: r-base littler/ppc64el
  • Implicit dependency: r-base littler/s390x
  • Implicit dependency: r-base lme4/amd64
  • Implicit dependency: r-base lme4/arm64
  • Implicit dependency: r-base lme4/armel
  • Implicit dependency: r-base lme4/armhf
  • Implicit dependency: r-base lme4/i386
  • Implicit dependency: r-base lme4/mips64el
  • Implicit dependency: r-base lme4/mipsel
  • Implicit dependency: r-base lme4/ppc64el
  • Implicit dependency: r-base lme4/s390x
  • Implicit dependency: r-base lmtest/amd64
  • Implicit dependency: r-base lmtest/arm64
  • Implicit dependency: r-base lmtest/armel
  • Implicit dependency: r-base lmtest/armhf
  • Implicit dependency: r-base lmtest/i386
  • Implicit dependency: r-base lmtest/mips64el
  • Implicit dependency: r-base lmtest/mipsel
  • Implicit dependency: r-base lmtest/ppc64el
  • Implicit dependency: r-base lmtest/s390x
  • Implicit dependency: r-base mgcv/amd64
  • Implicit dependency: r-base mgcv/arm64
  • Implicit dependency: r-base mgcv/armel
  • Implicit dependency: r-base mgcv/armhf
  • Implicit dependency: r-base mgcv/i386
  • Implicit dependency: r-base mgcv/mips64el
  • Implicit dependency: r-base mgcv/mipsel
  • Implicit dependency: r-base mgcv/ppc64el
  • Implicit dependency: r-base mgcv/s390x
  • Implicit dependency: r-base misc3d
  • Implicit dependency: r-base mnormt/amd64
  • Implicit dependency: r-base mnormt/arm64
  • Implicit dependency: r-base mnormt/armel
  • Implicit dependency: r-base mnormt/armhf
  • Implicit dependency: r-base mnormt/i386
  • Implicit dependency: r-base mnormt/mips64el
  • Implicit dependency: r-base mnormt/mipsel
  • Implicit dependency: r-base mnormt/ppc64el
  • Implicit dependency: r-base mnormt/s390x
  • Implicit dependency: r-base multcomp
  • Implicit dependency: r-base mvtnorm/amd64
  • Implicit dependency: r-base mvtnorm/arm64
  • Implicit dependency: r-base mvtnorm/armel
  • Implicit dependency: r-base mvtnorm/armhf
  • Implicit dependency: r-base mvtnorm/i386
  • Implicit dependency: r-base mvtnorm/mips64el
  • Implicit dependency: r-base mvtnorm/mipsel
  • Implicit dependency: r-base mvtnorm/ppc64el
  • Implicit dependency: r-base mvtnorm/s390x
  • Implicit dependency: r-base nlme/amd64
  • Implicit dependency: r-base nlme/arm64
  • Implicit dependency: r-base nlme/armel
  • Implicit dependency: r-base nlme/armhf
  • Implicit dependency: r-base nlme/i386
  • Implicit dependency: r-base nlme/mips64el
  • Implicit dependency: r-base nlme/mipsel
  • Implicit dependency: r-base nlme/ppc64el
  • Implicit dependency: r-base nlme/s390x
  • Implicit dependency: r-base polspline
  • Implicit dependency: r-base quadprog/amd64
  • Implicit dependency: r-base quadprog/arm64
  • Implicit dependency: r-base quadprog/armel
  • Implicit dependency: r-base quadprog/armhf
  • Implicit dependency: r-base quadprog/i386
  • Implicit dependency: r-base quadprog/mips64el
  • Implicit dependency: r-base quadprog/mipsel
  • Implicit dependency: r-base quadprog/ppc64el
  • Implicit dependency: r-base quadprog/s390x
  • Implicit dependency: r-base r-bioc-affy
  • Implicit dependency: r-base r-bioc-affyio
  • Implicit dependency: r-base r-bioc-all
  • Implicit dependency: r-base r-bioc-annotate
  • Implicit dependency: r-base r-bioc-annotationdbi
  • Implicit dependency: r-base r-bioc-annotationfilter
  • Implicit dependency: r-base r-bioc-annotationhub
  • Implicit dependency: r-base r-bioc-aroma.light
  • Implicit dependency: r-base r-bioc-biobase
  • Implicit dependency: r-base r-bioc-biocfilecache
  • Implicit dependency: r-base r-bioc-biocgenerics
  • Implicit dependency: r-base r-bioc-biocparallel
  • Implicit dependency: r-base r-bioc-biocversion
  • Implicit dependency: r-base r-bioc-biomart
  • Implicit dependency: r-base r-bioc-biomformat
  • Implicit dependency: r-base r-bioc-biostrings
  • Implicit dependency: r-base r-bioc-biovizbase
  • Implicit dependency: r-base r-bioc-bitseq
  • Implicit dependency: r-base r-bioc-bladderbatch
  • Implicit dependency: r-base r-bioc-bsgenome
  • Implicit dependency: r-base r-bioc-cner
  • Implicit dependency: r-base r-bioc-consensusclusterplus
  • Implicit dependency: r-base r-bioc-ctc
  • Implicit dependency: r-base r-bioc-cummerbund
  • Implicit dependency: r-base r-bioc-dada2
  • Implicit dependency: r-base r-bioc-delayedarray
  • Implicit dependency: r-base r-bioc-deseq
  • Implicit dependency: r-base r-bioc-deseq2
  • Implicit dependency: r-base r-bioc-dirichletmultinomial
  • Implicit dependency: r-base r-bioc-dnacopy
  • Implicit dependency: r-base r-bioc-ebseq
  • Implicit dependency: r-base r-bioc-edaseq
  • Implicit dependency: r-base r-bioc-edger
  • Implicit dependency: r-base r-bioc-ensembldb
  • Implicit dependency: r-base r-bioc-genefilter
  • Implicit dependency: r-base r-bioc-genelendatabase
  • Implicit dependency: r-base r-bioc-geneplotter
  • Implicit dependency: r-base r-bioc-genomeinfodb
  • Implicit dependency: r-base r-bioc-genomeinfodbdata
  • Implicit dependency: r-base r-bioc-genomicalignments
  • Implicit dependency: r-base r-bioc-genomicfeatures
  • Implicit dependency: r-base r-bioc-genomicranges
  • Implicit dependency: r-base r-bioc-geoquery
  • Implicit dependency: r-base r-bioc-go.db
  • Implicit dependency: r-base r-bioc-gosemsim
  • Implicit dependency: r-base r-bioc-goseq
  • Implicit dependency: r-base r-bioc-gviz
  • Implicit dependency: r-base r-bioc-hilbertvis
  • Implicit dependency: r-base r-bioc-htsfilter
  • Implicit dependency: r-base r-bioc-ihw
  • Implicit dependency: r-base r-bioc-impute
  • Implicit dependency: r-base r-bioc-interactivedisplaybase
  • Implicit dependency: r-base r-bioc-iranges
  • Implicit dependency: r-base r-bioc-keggrest
  • Implicit dependency: r-base r-bioc-limma
  • Implicit dependency: r-base r-bioc-lpsymphony
  • Implicit dependency: r-base r-bioc-makecdfenv
  • Implicit dependency: r-base r-bioc-mergeomics
  • Implicit dependency: r-base r-bioc-metagenomeseq
  • Implicit dependency: r-base r-bioc-multiassayexperiment
  • Implicit dependency: r-base r-bioc-multtest
  • Implicit dependency: r-base r-bioc-nanostringqcpro
  • Implicit dependency: r-base r-bioc-org.hs.eg.db
  • Implicit dependency: r-base r-bioc-pcamethods
  • Implicit dependency: r-base r-bioc-phyloseq
  • Implicit dependency: r-base r-bioc-preprocesscore
  • Implicit dependency: r-base r-bioc-protgenerics
  • Implicit dependency: r-base r-bioc-pwmenrich
  • Implicit dependency: r-base r-bioc-qusage
  • Implicit dependency: r-base r-bioc-qvalue
  • Implicit dependency: r-base r-bioc-rgsepd
  • Implicit dependency: r-base r-bioc-rhdf5
  • Implicit dependency: r-base r-bioc-rhdf5lib
  • Implicit dependency: r-base r-bioc-rhtslib
  • Implicit dependency: r-base r-bioc-rots
  • Implicit dependency: r-base r-bioc-rsamtools
  • Implicit dependency: r-base r-bioc-rtracklayer
  • Implicit dependency: r-base r-bioc-s4vectors
  • Implicit dependency: r-base r-bioc-savr
  • Implicit dependency: r-base r-bioc-seqlogo
  • Implicit dependency: r-base r-bioc-shortread
  • Implicit dependency: r-base r-bioc-snpstats
  • Implicit dependency: r-base r-bioc-summarizedexperiment
  • Implicit dependency: r-base r-bioc-tfbstools
  • Implicit dependency: r-base r-bioc-tximport
  • Implicit dependency: r-base r-bioc-variantannotation
  • Implicit dependency: r-base r-bioc-wrench
  • Implicit dependency: r-base r-bioc-xvector
  • Implicit dependency: r-base r-bioc-zlibbioc
  • Implicit dependency: r-base r-cran-actuar/amd64
  • Implicit dependency: r-base r-cran-actuar/arm64
  • Implicit dependency: r-base r-cran-actuar/armel
  • Implicit dependency: r-base r-cran-actuar/armhf
  • Implicit dependency: r-base r-cran-actuar/i386
  • Implicit dependency: r-base r-cran-actuar/mips64el
  • Implicit dependency: r-base r-cran-actuar/mipsel
  • Implicit dependency: r-base r-cran-actuar/ppc64el
  • Implicit dependency: r-base r-cran-actuar/s390x
  • Implicit dependency: r-base r-cran-ade4/amd64
  • Implicit dependency: r-base r-cran-ade4/arm64
  • Implicit dependency: r-base r-cran-ade4/armel
  • Implicit dependency: r-base r-cran-ade4/armhf
  • Implicit dependency: r-base r-cran-ade4/i386
  • Implicit dependency: r-base r-cran-ade4/mips64el
  • Implicit dependency: r-base r-cran-ade4/mipsel
  • Implicit dependency: r-base r-cran-ade4/ppc64el
  • Implicit dependency: r-base r-cran-ade4/s390x
  • Implicit dependency: r-base r-cran-adegenet
  • Implicit dependency: r-base r-cran-adegraphics
  • Implicit dependency: r-base r-cran-adephylo/amd64
  • Implicit dependency: r-base r-cran-adephylo/arm64
  • Implicit dependency: r-base r-cran-adephylo/armel
  • Implicit dependency: r-base r-cran-adephylo/armhf
  • Implicit dependency: r-base r-cran-adephylo/i386
  • Implicit dependency: r-base r-cran-adephylo/mips64el
  • Implicit dependency: r-base r-cran-adephylo/mipsel
  • Implicit dependency: r-base r-cran-adephylo/ppc64el
  • Implicit dependency: r-base r-cran-adephylo/s390x
  • Implicit dependency: r-base r-cran-aer
  • Implicit dependency: r-base r-cran-afex
  • Implicit dependency: r-base r-cran-alakazam
  • Implicit dependency: r-base r-cran-amap/amd64
  • Implicit dependency: r-base r-cran-amap/arm64
  • Implicit dependency: r-base r-cran-amap/armel
  • Implicit dependency: r-base r-cran-amap/armhf
  • Implicit dependency: r-base r-cran-amap/i386
  • Implicit dependency: r-base r-cran-amap/mips64el
  • Implicit dependency: r-base r-cran-amap/mipsel
  • Implicit dependency: r-base r-cran-amap/ppc64el
  • Implicit dependency: r-base r-cran-amap/s390x
  • Implicit dependency: r-base r-cran-amelia/amd64
  • Implicit dependency: r-base r-cran-amelia/arm64
  • Implicit dependency: r-base r-cran-amelia/armel
  • Implicit dependency: r-base r-cran-amelia/armhf
  • Implicit dependency: r-base r-cran-amelia/i386
  • Implicit dependency: r-base r-cran-amelia/mips64el
  • Implicit dependency: r-base r-cran-amelia/mipsel
  • Implicit dependency: r-base r-cran-amelia/ppc64el
  • Implicit dependency: r-base r-cran-amelia/s390x
  • Implicit dependency: r-base r-cran-amore/amd64
  • Implicit dependency: r-base r-cran-amore/arm64
  • Implicit dependency: r-base r-cran-amore/armel
  • Implicit dependency: r-base r-cran-amore/armhf
  • Implicit dependency: r-base r-cran-amore/i386
  • Implicit dependency: r-base r-cran-amore/mips64el
  • Implicit dependency: r-base r-cran-amore/mipsel
  • Implicit dependency: r-base r-cran-amore/ppc64el
  • Implicit dependency: r-base r-cran-amore/s390x
  • Implicit dependency: r-base r-cran-animation
  • Implicit dependency: r-base r-cran-apcluster/amd64
  • Implicit dependency: r-base r-cran-apcluster/arm64
  • Implicit dependency: r-base r-cran-apcluster/armel
  • Implicit dependency: r-base r-cran-apcluster/armhf
  • Implicit dependency: r-base r-cran-apcluster/i386
  • Implicit dependency: r-base r-cran-apcluster/mips64el
  • Implicit dependency: r-base r-cran-apcluster/mipsel
  • Implicit dependency: r-base r-cran-apcluster/ppc64el
  • Implicit dependency: r-base r-cran-apcluster/s390x
  • Implicit dependency: r-base r-cran-ape/amd64
  • Implicit dependency: r-base r-cran-ape/arm64
  • Implicit dependency: r-base r-cran-ape/armel
  • Implicit dependency: r-base r-cran-ape/armhf
  • Implicit dependency: r-base r-cran-ape/i386
  • Implicit dependency: r-base r-cran-ape/mips64el
  • Implicit dependency: r-base r-cran-ape/mipsel
  • Implicit dependency: r-base r-cran-ape/ppc64el
  • Implicit dependency: r-base r-cran-ape/s390x
  • Implicit dependency: r-base r-cran-aplpack
  • Implicit dependency: r-base r-cran-arm
  • Implicit dependency: r-base r-cran-askpass/amd64
  • Implicit dependency: r-base r-cran-askpass/arm64
  • Implicit dependency: r-base r-cran-askpass/armel
  • Implicit dependency: r-base r-cran-askpass/armhf
  • Implicit dependency: r-base r-cran-askpass/i386
  • Implicit dependency: r-base r-cran-askpass/mips64el
  • Implicit dependency: r-base r-cran-askpass/mipsel
  • Implicit dependency: r-base r-cran-askpass/ppc64el
  • Implicit dependency: r-base r-cran-askpass/s390x
  • Implicit dependency: r-base r-cran-assertive.base
  • Implicit dependency: r-base r-cran-assertive.sets
  • Implicit dependency: r-base r-cran-assertthat
  • Implicit dependency: r-base r-cran-backports
  • Implicit dependency: r-base r-cran-base64enc/amd64
  • Implicit dependency: r-base r-cran-base64enc/arm64
  • Implicit dependency: r-base r-cran-base64enc/armel
  • Implicit dependency: r-base r-cran-base64enc/armhf
  • Implicit dependency: r-base r-cran-base64enc/i386
  • Implicit dependency: r-base r-cran-base64enc/mips64el
  • Implicit dependency: r-base r-cran-base64enc/mipsel
  • Implicit dependency: r-base r-cran-base64enc/ppc64el
  • Implicit dependency: r-base r-cran-base64enc/s390x
  • Implicit dependency: r-base r-cran-base64url/amd64
  • Implicit dependency: r-base r-cran-base64url/arm64
  • Implicit dependency: r-base r-cran-base64url/armel
  • Implicit dependency: r-base r-cran-base64url/armhf
  • Implicit dependency: r-base r-cran-base64url/i386
  • Implicit dependency: r-base r-cran-base64url/mips64el
  • Implicit dependency: r-base r-cran-base64url/mipsel
  • Implicit dependency: r-base r-cran-base64url/ppc64el
  • Implicit dependency: r-base r-cran-base64url/s390x
  • Implicit dependency: r-base r-cran-batchjobs
  • Implicit dependency: r-base r-cran-batchtools/amd64
  • Implicit dependency: r-base r-cran-batchtools/arm64
  • Implicit dependency: r-base r-cran-batchtools/armel
  • Implicit dependency: r-base r-cran-batchtools/armhf
  • Implicit dependency: r-base r-cran-batchtools/i386
  • Implicit dependency: r-base r-cran-batchtools/mips64el
  • Implicit dependency: r-base r-cran-batchtools/mipsel
  • Implicit dependency: r-base r-cran-batchtools/ppc64el
  • Implicit dependency: r-base r-cran-batchtools/s390x
  • Implicit dependency: r-base r-cran-bayesfactor/amd64
  • Implicit dependency: r-base r-cran-bayesfactor/arm64
  • Implicit dependency: r-base r-cran-bayesfactor/armel
  • Implicit dependency: r-base r-cran-bayesfactor/armhf
  • Implicit dependency: r-base r-cran-bayesfactor/i386
  • Implicit dependency: r-base r-cran-bayesfactor/mips64el
  • Implicit dependency: r-base r-cran-bayesfactor/mipsel
  • Implicit dependency: r-base r-cran-bayesfactor/ppc64el
  • Implicit dependency: r-base r-cran-bayesfactor/s390x
  • Implicit dependency: r-base r-cran-bayesfm/amd64
  • Implicit dependency: r-base r-cran-bayesfm/arm64
  • Implicit dependency: r-base r-cran-bayesfm/armel
  • Implicit dependency: r-base r-cran-bayesfm/armhf
  • Implicit dependency: r-base r-cran-bayesfm/i386
  • Implicit dependency: r-base r-cran-bayesfm/mips64el
  • Implicit dependency: r-base r-cran-bayesfm/mipsel
  • Implicit dependency: r-base r-cran-bayesfm/ppc64el
  • Implicit dependency: r-base r-cran-bayesfm/s390x
  • Implicit dependency: r-base r-cran-bayesm/amd64
  • Implicit dependency: r-base r-cran-bayesm/arm64
  • Implicit dependency: r-base r-cran-bayesm/armel
  • Implicit dependency: r-base r-cran-bayesm/armhf
  • Implicit dependency: r-base r-cran-bayesm/i386
  • Implicit dependency: r-base r-cran-bayesm/mips64el
  • Implicit dependency: r-base r-cran-bayesm/mipsel
  • Implicit dependency: r-base r-cran-bayesm/ppc64el
  • Implicit dependency: r-base r-cran-bayesm/s390x
  • Implicit dependency: r-base r-cran-bayesplot
  • Implicit dependency: r-base r-cran-bayestestr
  • Implicit dependency: r-base r-cran-bbmisc/amd64
  • Implicit dependency: r-base r-cran-bbmisc/arm64
  • Implicit dependency: r-base r-cran-bbmisc/armel
  • Implicit dependency: r-base r-cran-bbmisc/armhf
  • Implicit dependency: r-base r-cran-bbmisc/i386
  • Implicit dependency: r-base r-cran-bbmisc/mips64el
  • Implicit dependency: r-base r-cran-bbmisc/mipsel
  • Implicit dependency: r-base r-cran-bbmisc/ppc64el
  • Implicit dependency: r-base r-cran-bbmisc/s390x
  • Implicit dependency: r-base r-cran-bbmle
  • Implicit dependency: r-base r-cran-bdgraph/amd64
  • Implicit dependency: r-base r-cran-bdgraph/arm64
  • Implicit dependency: r-base r-cran-bdgraph/armel
  • Implicit dependency: r-base r-cran-bdgraph/armhf
  • Implicit dependency: r-base r-cran-bdgraph/i386
  • Implicit dependency: r-base r-cran-bdgraph/mips64el
  • Implicit dependency: r-base r-cran-bdgraph/mipsel
  • Implicit dependency: r-base r-cran-bdgraph/ppc64el
  • Implicit dependency: r-base r-cran-bdgraph/s390x
  • Implicit dependency: r-base r-cran-bdsmatrix/amd64
  • Implicit dependency: r-base r-cran-bdsmatrix/arm64
  • Implicit dependency: r-base r-cran-bdsmatrix/armel
  • Implicit dependency: r-base r-cran-bdsmatrix/armhf
  • Implicit dependency: r-base r-cran-bdsmatrix/i386
  • Implicit dependency: r-base r-cran-bdsmatrix/mips64el
  • Implicit dependency: r-base r-cran-bdsmatrix/mipsel
  • Implicit dependency: r-base r-cran-bdsmatrix/ppc64el
  • Implicit dependency: r-base r-cran-bdsmatrix/s390x
  • Implicit dependency: r-base r-cran-beeswarm
  • Implicit dependency: r-base r-cran-biasedurn/amd64
  • Implicit dependency: r-base r-cran-biasedurn/arm64
  • Implicit dependency: r-base r-cran-biasedurn/armel
  • Implicit dependency: r-base r-cran-biasedurn/armhf
  • Implicit dependency: r-base r-cran-biasedurn/i386
  • Implicit dependency: r-base r-cran-biasedurn/mips64el
  • Implicit dependency: r-base r-cran-biasedurn/mipsel
  • Implicit dependency: r-base r-cran-biasedurn/ppc64el
  • Implicit dependency: r-base r-cran-biasedurn/s390x
  • Implicit dependency: r-base r-cran-bibtex/amd64
  • Implicit dependency: r-base r-cran-bibtex/arm64
  • Implicit dependency: r-base r-cran-bibtex/armel
  • Implicit dependency: r-base r-cran-bibtex/armhf
  • Implicit dependency: r-base r-cran-bibtex/i386
  • Implicit dependency: r-base r-cran-bibtex/mips64el
  • Implicit dependency: r-base r-cran-bibtex/mipsel
  • Implicit dependency: r-base r-cran-bibtex/ppc64el
  • Implicit dependency: r-base r-cran-bibtex/s390x
  • Implicit dependency: r-base r-cran-bigmemory.sri
  • Implicit dependency: r-base r-cran-bigmemory/amd64
  • Implicit dependency: r-base r-cran-bigmemory/arm64
  • Implicit dependency: r-base r-cran-bigmemory/armel
  • Implicit dependency: r-base r-cran-bigmemory/armhf
  • Implicit dependency: r-base r-cran-bigmemory/i386
  • Implicit dependency: r-base r-cran-bigmemory/mips64el
  • Implicit dependency: r-base r-cran-bigmemory/mipsel
  • Implicit dependency: r-base r-cran-bigmemory/ppc64el
  • Implicit dependency: r-base r-cran-bigmemory/s390x
  • Implicit dependency: r-base r-cran-bindr
  • Implicit dependency: r-base r-cran-bindrcpp/amd64
  • Implicit dependency: r-base r-cran-bindrcpp/arm64
  • Implicit dependency: r-base r-cran-bindrcpp/armel
  • Implicit dependency: r-base r-cran-bindrcpp/armhf
  • Implicit dependency: r-base r-cran-bindrcpp/i386
  • Implicit dependency: r-base r-cran-bindrcpp/mips64el
  • Implicit dependency: r-base r-cran-bindrcpp/mipsel
  • Implicit dependency: r-base r-cran-bindrcpp/ppc64el
  • Implicit dependency: r-base r-cran-bindrcpp/s390x
  • Implicit dependency: r-base r-cran-bio3d/amd64
  • Implicit dependency: r-base r-cran-bio3d/arm64
  • Implicit dependency: r-base r-cran-bio3d/armel
  • Implicit dependency: r-base r-cran-bio3d/armhf
  • Implicit dependency: r-base r-cran-bio3d/i386
  • Implicit dependency: r-base r-cran-bio3d/mips64el
  • Implicit dependency: r-base r-cran-bio3d/mipsel
  • Implicit dependency: r-base r-cran-bio3d/ppc64el
  • Implicit dependency: r-base r-cran-bio3d/s390x
  • Implicit dependency: r-base r-cran-biocmanager
  • Implicit dependency: r-base r-cran-bit/amd64
  • Implicit dependency: r-base r-cran-bit/arm64
  • Implicit dependency: r-base r-cran-bit/armel
  • Implicit dependency: r-base r-cran-bit/armhf
  • Implicit dependency: r-base r-cran-bit/i386
  • Implicit dependency: r-base r-cran-bit/mips64el
  • Implicit dependency: r-base r-cran-bit/mipsel
  • Implicit dependency: r-base r-cran-bit/ppc64el
  • Implicit dependency: r-base r-cran-bit/s390x
  • Implicit dependency: r-base r-cran-bit64/amd64
  • Implicit dependency: r-base r-cran-bit64/arm64
  • Implicit dependency: r-base r-cran-bit64/armel
  • Implicit dependency: r-base r-cran-bit64/armhf
  • Implicit dependency: r-base r-cran-bit64/i386
  • Implicit dependency: r-base r-cran-bit64/mips64el
  • Implicit dependency: r-base r-cran-bit64/mipsel
  • Implicit dependency: r-base r-cran-bit64/ppc64el
  • Implicit dependency: r-base r-cran-bit64/s390x
  • Implicit dependency: r-base r-cran-bitops/amd64
  • Implicit dependency: r-base r-cran-bitops/arm64
  • Implicit dependency: r-base r-cran-bitops/armel
  • Implicit dependency: r-base r-cran-bitops/armhf
  • Implicit dependency: r-base r-cran-bitops/i386
  • Implicit dependency: r-base r-cran-bitops/mips64el
  • Implicit dependency: r-base r-cran-bitops/mipsel
  • Implicit dependency: r-base r-cran-bitops/ppc64el
  • Implicit dependency: r-base r-cran-bitops/s390x
  • Implicit dependency: r-base r-cran-biwt/amd64
  • Implicit dependency: r-base r-cran-biwt/arm64
  • Implicit dependency: r-base r-cran-biwt/armel
  • Implicit dependency: r-base r-cran-biwt/armhf
  • Implicit dependency: r-base r-cran-biwt/i386
  • Implicit dependency: r-base r-cran-biwt/mips64el
  • Implicit dependency: r-base r-cran-biwt/mipsel
  • Implicit dependency: r-base r-cran-biwt/ppc64el
  • Implicit dependency: r-base r-cran-biwt/s390x
  • Implicit dependency: r-base r-cran-blme
  • Implicit dependency: r-base r-cran-blob
  • Implicit dependency: r-base r-cran-blockmodeling/amd64
  • Implicit dependency: r-base r-cran-blockmodeling/arm64
  • Implicit dependency: r-base r-cran-blockmodeling/armel
  • Implicit dependency: r-base r-cran-blockmodeling/armhf
  • Implicit dependency: r-base r-cran-blockmodeling/i386
  • Implicit dependency: r-base r-cran-blockmodeling/mips64el
  • Implicit dependency: r-base r-cran-blockmodeling/mipsel
  • Implicit dependency: r-base r-cran-blockmodeling/ppc64el
  • Implicit dependency: r-base r-cran-blockmodeling/s390x
  • Implicit dependency: r-base r-cran-bms
  • Implicit dependency: r-base r-cran-bold
  • Implicit dependency: r-base r-cran-bookdown
  • Implicit dependency: r-base r-cran-boolnet/amd64
  • Implicit dependency: r-base r-cran-boolnet/arm64
  • Implicit dependency: r-base r-cran-boolnet/armel
  • Implicit dependency: r-base r-cran-boolnet/armhf
  • Implicit dependency: r-base r-cran-boolnet/i386
  • Implicit dependency: r-base r-cran-boolnet/mips64el
  • Implicit dependency: r-base r-cran-boolnet/mipsel
  • Implicit dependency: r-base r-cran-boolnet/ppc64el
  • Implicit dependency: r-base r-cran-boolnet/s390x
  • Implicit dependency: r-base r-cran-bradleyterry2
  • Implicit dependency: r-base r-cran-brew
  • Implicit dependency: r-base r-cran-brglm/amd64
  • Implicit dependency: r-base r-cran-brglm/arm64
  • Implicit dependency: r-base r-cran-brglm/armel
  • Implicit dependency: r-base r-cran-brglm/armhf
  • Implicit dependency: r-base r-cran-brglm/i386
  • Implicit dependency: r-base r-cran-brglm/mips64el
  • Implicit dependency: r-base r-cran-brglm/mipsel
  • Implicit dependency: r-base r-cran-brglm/ppc64el
  • Implicit dependency: r-base r-cran-brglm/s390x
  • Implicit dependency: r-base r-cran-bridgesampling
  • Implicit dependency: r-base r-cran-brms
  • Implicit dependency: r-base r-cran-brobdingnag
  • Implicit dependency: r-base r-cran-broom
  • Implicit dependency: r-base r-cran-ca
  • Implicit dependency: r-base r-cran-caic4
  • Implicit dependency: r-base r-cran-cairo/amd64
  • Implicit dependency: r-base r-cran-cairo/arm64
  • Implicit dependency: r-base r-cran-cairo/armel
  • Implicit dependency: r-base r-cran-cairo/armhf
  • Implicit dependency: r-base r-cran-cairo/i386
  • Implicit dependency: r-base r-cran-cairo/mips64el
  • Implicit dependency: r-base r-cran-cairo/mipsel
  • Implicit dependency: r-base r-cran-cairo/ppc64el
  • Implicit dependency: r-base r-cran-cairo/s390x
  • Implicit dependency: r-base r-cran-calibrate
  • Implicit dependency: r-base r-cran-callr
  • Implicit dependency: r-base r-cran-cardata
  • Implicit dependency: r-base r-cran-caret/amd64
  • Implicit dependency: r-base r-cran-caret/arm64
  • Implicit dependency: r-base r-cran-caret/armel
  • Implicit dependency: r-base r-cran-caret/armhf
  • Implicit dependency: r-base r-cran-caret/i386
  • Implicit dependency: r-base r-cran-caret/mips64el
  • Implicit dependency: r-base r-cran-caret/mipsel
  • Implicit dependency: r-base r-cran-caret/ppc64el
  • Implicit dependency: r-base r-cran-caret/s390x
  • Implicit dependency: r-base r-cran-catools/amd64
  • Implicit dependency: r-base r-cran-catools/arm64
  • Implicit dependency: r-base r-cran-catools/armel
  • Implicit dependency: r-base r-cran-catools/armhf
  • Implicit dependency: r-base r-cran-catools/i386
  • Implicit dependency: r-base r-cran-catools/mips64el
  • Implicit dependency: r-base r-cran-catools/mipsel
  • Implicit dependency: r-base r-cran-catools/ppc64el
  • Implicit dependency: r-base r-cran-catools/s390x
  • Implicit dependency: r-base r-cran-cellranger
  • Implicit dependency: r-base r-cran-checkmate/amd64
  • Implicit dependency: r-base r-cran-checkmate/arm64
  • Implicit dependency: r-base r-cran-checkmate/armel
  • Implicit dependency: r-base r-cran-checkmate/armhf
  • Implicit dependency: r-base r-cran-checkmate/i386
  • Implicit dependency: r-base r-cran-checkmate/mips64el
  • Implicit dependency: r-base r-cran-checkmate/mipsel
  • Implicit dependency: r-base r-cran-checkmate/ppc64el
  • Implicit dependency: r-base r-cran-checkmate/s390x
  • Implicit dependency: r-base r-cran-circlize
  • Implicit dependency: r-base r-cran-class/amd64
  • Implicit dependency: r-base r-cran-class/arm64
  • Implicit dependency: r-base r-cran-class/armel
  • Implicit dependency: r-base r-cran-class/armhf
  • Implicit dependency: r-base r-cran-class/i386
  • Implicit dependency: r-base r-cran-class/mips64el
  • Implicit dependency: r-base r-cran-class/mipsel
  • Implicit dependency: r-base r-cran-class/ppc64el
  • Implicit dependency: r-base r-cran-class/s390x
  • Implicit dependency: r-base r-cran-classint/amd64
  • Implicit dependency: r-base r-cran-classint/arm64
  • Implicit dependency: r-base r-cran-classint/armel
  • Implicit dependency: r-base r-cran-classint/armhf
  • Implicit dependency: r-base r-cran-classint/i386
  • Implicit dependency: r-base r-cran-classint/mips64el
  • Implicit dependency: r-base r-cran-classint/mipsel
  • Implicit dependency: r-base r-cran-classint/ppc64el
  • Implicit dependency: r-base r-cran-classint/s390x
  • Implicit dependency: r-base r-cran-cli
  • Implicit dependency: r-base r-cran-cliapp
  • Implicit dependency: r-base r-cran-clipr
  • Implicit dependency: r-base r-cran-clisymbols
  • Implicit dependency: r-base r-cran-clubsandwich
  • Implicit dependency: r-base r-cran-clue/amd64
  • Implicit dependency: r-base r-cran-clue/arm64
  • Implicit dependency: r-base r-cran-clue/armel
  • Implicit dependency: r-base r-cran-clue/armhf
  • Implicit dependency: r-base r-cran-clue/i386
  • Implicit dependency: r-base r-cran-clue/mips64el
  • Implicit dependency: r-base r-cran-clue/mipsel
  • Implicit dependency: r-base r-cran-clue/ppc64el
  • Implicit dependency: r-base r-cran-clue/s390x
  • Implicit dependency: r-base r-cran-clustergeneration
  • Implicit dependency: r-base r-cran-cmprsk/amd64
  • Implicit dependency: r-base r-cran-cmprsk/arm64
  • Implicit dependency: r-base r-cran-cmprsk/armel
  • Implicit dependency: r-base r-cran-cmprsk/armhf
  • Implicit dependency: r-base r-cran-cmprsk/i386
  • Implicit dependency: r-base r-cran-cmprsk/mips64el
  • Implicit dependency: r-base r-cran-cmprsk/mipsel
  • Implicit dependency: r-base r-cran-cmprsk/ppc64el
  • Implicit dependency: r-base r-cran-cmprsk/s390x
  • Implicit dependency: r-base r-cran-coda
  • Implicit dependency: r-base r-cran-coin/amd64
  • Implicit dependency: r-base r-cran-coin/arm64
  • Implicit dependency: r-base r-cran-coin/armel
  • Implicit dependency: r-base r-cran-coin/armhf
  • Implicit dependency: r-base r-cran-coin/i386
  • Implicit dependency: r-base r-cran-coin/mips64el
  • Implicit dependency: r-base r-cran-coin/mipsel
  • Implicit dependency: r-base r-cran-coin/ppc64el
  • Implicit dependency: r-base r-cran-coin/s390x
  • Implicit dependency: r-base r-cran-colorspace/amd64
  • Implicit dependency: r-base r-cran-colorspace/arm64
  • Implicit dependency: r-base r-cran-colorspace/armel
  • Implicit dependency: r-base r-cran-colorspace/armhf
  • Implicit dependency: r-base r-cran-colorspace/i386
  • Implicit dependency: r-base r-cran-colorspace/mips64el
  • Implicit dependency: r-base r-cran-colorspace/mipsel
  • Implicit dependency: r-base r-cran-colorspace/ppc64el
  • Implicit dependency: r-base r-cran-colorspace/s390x
  • Implicit dependency: r-base r-cran-colourpicker
  • Implicit dependency: r-base r-cran-combinat
  • Implicit dependency: r-base r-cran-commonmark/amd64
  • Implicit dependency: r-base r-cran-commonmark/arm64
  • Implicit dependency: r-base r-cran-commonmark/armel
  • Implicit dependency: r-base r-cran-commonmark/armhf
  • Implicit dependency: r-base r-cran-commonmark/i386
  • Implicit dependency: r-base r-cran-commonmark/mips64el
  • Implicit dependency: r-base r-cran-commonmark/mipsel
  • Implicit dependency: r-base r-cran-commonmark/ppc64el
  • Implicit dependency: r-base r-cran-commonmark/s390x
  • Implicit dependency: r-base r-cran-contfrac/amd64
  • Implicit dependency: r-base r-cran-contfrac/arm64
  • Implicit dependency: r-base r-cran-contfrac/armel
  • Implicit dependency: r-base r-cran-contfrac/armhf
  • Implicit dependency: r-base r-cran-contfrac/i386
  • Implicit dependency: r-base r-cran-contfrac/mips64el
  • Implicit dependency: r-base r-cran-contfrac/mipsel
  • Implicit dependency: r-base r-cran-contfrac/ppc64el
  • Implicit dependency: r-base r-cran-contfrac/s390x
  • Implicit dependency: r-base r-cran-conting
  • Implicit dependency: r-base r-cran-corpcor
  • Implicit dependency: r-base r-cran-corrplot
  • Implicit dependency: r-base r-cran-covid19us
  • Implicit dependency: r-base r-cran-covr/amd64
  • Implicit dependency: r-base r-cran-covr/arm64
  • Implicit dependency: r-base r-cran-covr/armel
  • Implicit dependency: r-base r-cran-covr/armhf
  • Implicit dependency: r-base r-cran-covr/i386
  • Implicit dependency: r-base r-cran-covr/mips64el
  • Implicit dependency: r-base r-cran-covr/mipsel
  • Implicit dependency: r-base r-cran-covr/ppc64el
  • Implicit dependency: r-base r-cran-covr/s390x
  • Implicit dependency: r-base r-cran-cowplot
  • Implicit dependency: r-base r-cran-crayon
  • Implicit dependency: r-base r-cran-crosstalk
  • Implicit dependency: r-base r-cran-crul
  • Implicit dependency: r-base r-cran-cubature/amd64
  • Implicit dependency: r-base r-cran-cubature/arm64
  • Implicit dependency: r-base r-cran-cubature/armel
  • Implicit dependency: r-base r-cran-cubature/armhf
  • Implicit dependency: r-base r-cran-cubature/i386
  • Implicit dependency: r-base r-cran-cubature/mips64el
  • Implicit dependency: r-base r-cran-cubature/mipsel
  • Implicit dependency: r-base r-cran-cubature/ppc64el
  • Implicit dependency: r-base r-cran-cubature/s390x
  • Implicit dependency: r-base r-cran-curl/amd64
  • Implicit dependency: r-base r-cran-curl/arm64
  • Implicit dependency: r-base r-cran-curl/armel
  • Implicit dependency: r-base r-cran-curl/armhf
  • Implicit dependency: r-base r-cran-curl/i386
  • Implicit dependency: r-base r-cran-curl/mips64el
  • Implicit dependency: r-base r-cran-curl/mipsel
  • Implicit dependency: r-base r-cran-curl/ppc64el
  • Implicit dependency: r-base r-cran-curl/s390x
  • Implicit dependency: r-base r-cran-cvst
  • Implicit dependency: r-base r-cran-d3network
  • Implicit dependency: r-base r-cran-data.table/amd64
  • Implicit dependency: r-base r-cran-data.table/arm64
  • Implicit dependency: r-base r-cran-data.table/armel
  • Implicit dependency: r-base r-cran-data.table/armhf
  • Implicit dependency: r-base r-cran-data.table/i386
  • Implicit dependency: r-base r-cran-data.table/mips64el
  • Implicit dependency: r-base r-cran-data.table/mipsel
  • Implicit dependency: r-base r-cran-data.table/ppc64el
  • Implicit dependency: r-base r-cran-data.table/s390x
  • Implicit dependency: r-base r-cran-dbitest
  • Implicit dependency: r-base r-cran-dbplyr
  • Implicit dependency: r-base r-cran-ddalpha/amd64
  • Implicit dependency: r-base r-cran-ddalpha/arm64
  • Implicit dependency: r-base r-cran-ddalpha/armel
  • Implicit dependency: r-base r-cran-ddalpha/armhf
  • Implicit dependency: r-base r-cran-ddalpha/i386
  • Implicit dependency: r-base r-cran-ddalpha/mips64el
  • Implicit dependency: r-base r-cran-ddalpha/mipsel
  • Implicit dependency: r-base r-cran-ddalpha/ppc64el
  • Implicit dependency: r-base r-cran-ddalpha/s390x
  • Implicit dependency: r-base r-cran-deal/amd64
  • Implicit dependency: r-base r-cran-deal/arm64
  • Implicit dependency: r-base r-cran-deal/armel
  • Implicit dependency: r-base r-cran-deal/armhf
  • Implicit dependency: r-base r-cran-deal/i386
  • Implicit dependency: r-base r-cran-deal/mips64el
  • Implicit dependency: r-base r-cran-deal/mipsel
  • Implicit dependency: r-base r-cran-deal/ppc64el
  • Implicit dependency: r-base r-cran-deal/s390x
  • Implicit dependency: r-base r-cran-deldir/amd64
  • Implicit dependency: r-base r-cran-deldir/arm64
  • Implicit dependency: r-base r-cran-deldir/armel
  • Implicit dependency: r-base r-cran-deldir/armhf
  • Implicit dependency: r-base r-cran-deldir/i386
  • Implicit dependency: r-base r-cran-deldir/mips64el
  • Implicit dependency: r-base r-cran-deldir/mipsel
  • Implicit dependency: r-base r-cran-deldir/ppc64el
  • Implicit dependency: r-base r-cran-deldir/s390x
  • Implicit dependency: r-base r-cran-dendextend
  • Implicit dependency: r-base r-cran-deoptim/amd64
  • Implicit dependency: r-base r-cran-deoptim/arm64
  • Implicit dependency: r-base r-cran-deoptim/armel
  • Implicit dependency: r-base r-cran-deoptim/armhf
  • Implicit dependency: r-base r-cran-deoptim/i386
  • Implicit dependency: r-base r-cran-deoptim/mips64el
  • Implicit dependency: r-base r-cran-deoptim/mipsel
  • Implicit dependency: r-base r-cran-deoptim/ppc64el
  • Implicit dependency: r-base r-cran-deoptim/s390x
  • Implicit dependency: r-base r-cran-deoptimr/amd64
  • Implicit dependency: r-base r-cran-deoptimr/arm64
  • Implicit dependency: r-base r-cran-deoptimr/armel
  • Implicit dependency: r-base r-cran-deoptimr/armhf
  • Implicit dependency: r-base r-cran-deoptimr/i386
  • Implicit dependency: r-base r-cran-deoptimr/mips64el
  • Implicit dependency: r-base r-cran-deoptimr/mipsel
  • Implicit dependency: r-base r-cran-deoptimr/ppc64el
  • Implicit dependency: r-base r-cran-deoptimr/s390x
  • Implicit dependency: r-base r-cran-desc
  • Implicit dependency: r-base r-cran-desolve/amd64
  • Implicit dependency: r-base r-cran-desolve/arm64
  • Implicit dependency: r-base r-cran-desolve/armel
  • Implicit dependency: r-base r-cran-desolve/armhf
  • Implicit dependency: r-base r-cran-desolve/i386
  • Implicit dependency: r-base r-cran-desolve/mips64el
  • Implicit dependency: r-base r-cran-desolve/mipsel
  • Implicit dependency: r-base r-cran-desolve/ppc64el
  • Implicit dependency: r-base r-cran-desolve/s390x
  • Implicit dependency: r-base r-cran-devtools
  • Implicit dependency: r-base r-cran-dfoptim
  • Implicit dependency: r-base r-cran-diagnosismed
  • Implicit dependency: r-base r-cran-dichromat
  • Implicit dependency: r-base r-cran-diffobj
  • Implicit dependency: r-base r-cran-digest/amd64
  • Implicit dependency: r-base r-cran-digest/arm64
  • Implicit dependency: r-base r-cran-digest/armel
  • Implicit dependency: r-base r-cran-digest/armhf
  • Implicit dependency: r-base r-cran-digest/i386
  • Implicit dependency: r-base r-cran-digest/mips64el
  • Implicit dependency: r-base r-cran-digest/mipsel
  • Implicit dependency: r-base r-cran-digest/ppc64el
  • Implicit dependency: r-base r-cran-digest/s390x
  • Implicit dependency: r-base r-cran-dimred/amd64
  • Implicit dependency: r-base r-cran-dimred/arm64
  • Implicit dependency: r-base r-cran-dimred/armel
  • Implicit dependency: r-base r-cran-dimred/armhf
  • Implicit dependency: r-base r-cran-dimred/i386
  • Implicit dependency: r-base r-cran-dimred/mips64el
  • Implicit dependency: r-base r-cran-dimred/mipsel
  • Implicit dependency: r-base r-cran-dimred/ppc64el
  • Implicit dependency: r-base r-cran-dimred/s390x
  • Implicit dependency: r-base r-cran-diptest/amd64
  • Implicit dependency: r-base r-cran-diptest/arm64
  • Implicit dependency: r-base r-cran-diptest/armel
  • Implicit dependency: r-base r-cran-diptest/armhf
  • Implicit dependency: r-base r-cran-diptest/i386
  • Implicit dependency: r-base r-cran-diptest/mips64el
  • Implicit dependency: r-base r-cran-diptest/mipsel
  • Implicit dependency: r-base r-cran-diptest/ppc64el
  • Implicit dependency: r-base r-cran-diptest/s390x
  • Implicit dependency: r-base r-cran-discriminer
  • Implicit dependency: r-base r-cran-distory/amd64
  • Implicit dependency: r-base r-cran-distory/arm64
  • Implicit dependency: r-base r-cran-distory/armel
  • Implicit dependency: r-base r-cran-distory/armhf
  • Implicit dependency: r-base r-cran-distory/i386
  • Implicit dependency: r-base r-cran-distory/mips64el
  • Implicit dependency: r-base r-cran-distory/mipsel
  • Implicit dependency: r-base r-cran-distory/ppc64el
  • Implicit dependency: r-base r-cran-distory/s390x
  • Implicit dependency: r-base r-cran-domc
  • Implicit dependency: r-base r-cran-doparallel
  • Implicit dependency: r-base r-cran-dorng
  • Implicit dependency: r-base r-cran-dosefinding/amd64
  • Implicit dependency: r-base r-cran-dosefinding/arm64
  • Implicit dependency: r-base r-cran-dosefinding/armel
  • Implicit dependency: r-base r-cran-dosefinding/armhf
  • Implicit dependency: r-base r-cran-dosefinding/i386
  • Implicit dependency: r-base r-cran-dosefinding/mips64el
  • Implicit dependency: r-base r-cran-dosefinding/mipsel
  • Implicit dependency: r-base r-cran-dosefinding/ppc64el
  • Implicit dependency: r-base r-cran-dosefinding/s390x
  • Implicit dependency: r-base r-cran-dosnow
  • Implicit dependency: r-base r-cran-dotcall64/amd64
  • Implicit dependency: r-base r-cran-dotcall64/arm64
  • Implicit dependency: r-base r-cran-dotcall64/armel
  • Implicit dependency: r-base r-cran-dotcall64/armhf
  • Implicit dependency: r-base r-cran-dotcall64/i386
  • Implicit dependency: r-base r-cran-dotcall64/mips64el
  • Implicit dependency: r-base r-cran-dotcall64/mipsel
  • Implicit dependency: r-base r-cran-dotcall64/ppc64el
  • Implicit dependency: r-base r-cran-dotcall64/s390x
  • Implicit dependency: r-base r-cran-downloader
  • Implicit dependency: r-base r-cran-dplyr/amd64
  • Implicit dependency: r-base r-cran-dplyr/arm64
  • Implicit dependency: r-base r-cran-dplyr/armel
  • Implicit dependency: r-base r-cran-dplyr/armhf
  • Implicit dependency: r-base r-cran-dplyr/i386
  • Implicit dependency: r-base r-cran-dplyr/mips64el
  • Implicit dependency: r-base r-cran-dplyr/mipsel
  • Implicit dependency: r-base r-cran-dplyr/ppc64el
  • Implicit dependency: r-base r-cran-dplyr/s390x
  • Implicit dependency: r-base r-cran-dqrng/amd64
  • Implicit dependency: r-base r-cran-dqrng/arm64
  • Implicit dependency: r-base r-cran-dqrng/armel
  • Implicit dependency: r-base r-cran-dqrng/armhf
  • Implicit dependency: r-base r-cran-dqrng/i386
  • Implicit dependency: r-base r-cran-dqrng/mips64el
  • Implicit dependency: r-base r-cran-dqrng/mipsel
  • Implicit dependency: r-base r-cran-dqrng/ppc64el
  • Implicit dependency: r-base r-cran-dqrng/s390x
  • Implicit dependency: r-base r-cran-drr
  • Implicit dependency: r-base r-cran-dt
  • Implicit dependency: r-base r-cran-dygraphs
  • Implicit dependency: r-base r-cran-dynamictreecut
  • Implicit dependency: r-base r-cran-dynlm
  • Implicit dependency: r-base r-cran-e1071/amd64
  • Implicit dependency: r-base r-cran-e1071/arm64
  • Implicit dependency: r-base r-cran-e1071/armel
  • Implicit dependency: r-base r-cran-e1071/armhf
  • Implicit dependency: r-base r-cran-e1071/i386
  • Implicit dependency: r-base r-cran-e1071/mips64el
  • Implicit dependency: r-base r-cran-e1071/mipsel
  • Implicit dependency: r-base r-cran-e1071/ppc64el
  • Implicit dependency: r-base r-cran-e1071/s390x
  • Implicit dependency: r-base r-cran-eaf/amd64
  • Implicit dependency: r-base r-cran-eaf/arm64
  • Implicit dependency: r-base r-cran-eaf/armel
  • Implicit dependency: r-base r-cran-eaf/armhf
  • Implicit dependency: r-base r-cran-eaf/i386
  • Implicit dependency: r-base r-cran-eaf/mips64el
  • Implicit dependency: r-base r-cran-eaf/mipsel
  • Implicit dependency: r-base r-cran-eaf/ppc64el
  • Implicit dependency: r-base r-cran-eaf/s390x
  • Implicit dependency: r-base r-cran-earth/amd64
  • Implicit dependency: r-base r-cran-earth/arm64
  • Implicit dependency: r-base r-cran-earth/armel
  • Implicit dependency: r-base r-cran-earth/armhf
  • Implicit dependency: r-base r-cran-earth/i386
  • Implicit dependency: r-base r-cran-earth/mips64el
  • Implicit dependency: r-base r-cran-earth/mipsel
  • Implicit dependency: r-base r-cran-earth/ppc64el
  • Implicit dependency: r-base r-cran-earth/s390x
  • Implicit dependency: r-base r-cran-eco/amd64
  • Implicit dependency: r-base r-cran-eco/arm64
  • Implicit dependency: r-base r-cran-eco/armel
  • Implicit dependency: r-base r-cran-eco/armhf
  • Implicit dependency: r-base r-cran-eco/i386
  • Implicit dependency: r-base r-cran-eco/mips64el
  • Implicit dependency: r-base r-cran-eco/mipsel
  • Implicit dependency: r-base r-cran-eco/ppc64el
  • Implicit dependency: r-base r-cran-eco/s390x
  • Implicit dependency: r-base r-cran-ecodist/amd64
  • Implicit dependency: r-base r-cran-ecodist/arm64
  • Implicit dependency: r-base r-cran-ecodist/armel
  • Implicit dependency: r-base r-cran-ecodist/armhf
  • Implicit dependency: r-base r-cran-ecodist/i386
  • Implicit dependency: r-base r-cran-ecodist/mips64el
  • Implicit dependency: r-base r-cran-ecodist/mipsel
  • Implicit dependency: r-base r-cran-ecodist/ppc64el
  • Implicit dependency: r-base r-cran-ecodist/s390x
  • Implicit dependency: r-base r-cran-effectsize
  • Implicit dependency: r-base r-cran-egg
  • Implicit dependency: r-base r-cran-ei
  • Implicit dependency: r-base r-cran-eipack/amd64
  • Implicit dependency: r-base r-cran-eipack/arm64
  • Implicit dependency: r-base r-cran-eipack/armel
  • Implicit dependency: r-base r-cran-eipack/armhf
  • Implicit dependency: r-base r-cran-eipack/i386
  • Implicit dependency: r-base r-cran-eipack/mips64el
  • Implicit dependency: r-base r-cran-eipack/mipsel
  • Implicit dependency: r-base r-cran-eipack/ppc64el
  • Implicit dependency: r-base r-cran-eipack/s390x
  • Implicit dependency: r-base r-cran-ellipse
  • Implicit dependency: r-base r-cran-ellipsis
  • Implicit dependency: r-base r-cran-elliptic
  • Implicit dependency: r-base r-cran-emmeans
  • Implicit dependency: r-base r-cran-emoa/amd64
  • Implicit dependency: r-base r-cran-emoa/arm64
  • Implicit dependency: r-base r-cran-emoa/armel
  • Implicit dependency: r-base r-cran-emoa/armhf
  • Implicit dependency: r-base r-cran-emoa/i386
  • Implicit dependency: r-base r-cran-emoa/mips64el
  • Implicit dependency: r-base r-cran-emoa/mipsel
  • Implicit dependency: r-base r-cran-emoa/ppc64el
  • Implicit dependency: r-base r-cran-emoa/s390x
  • Implicit dependency: r-base r-cran-energy/amd64
  • Implicit dependency: r-base r-cran-energy/arm64
  • Implicit dependency: r-base r-cran-energy/armel
  • Implicit dependency: r-base r-cran-energy/armhf
  • Implicit dependency: r-base r-cran-energy/i386
  • Implicit dependency: r-base r-cran-energy/mips64el
  • Implicit dependency: r-base r-cran-energy/mipsel
  • Implicit dependency: r-base r-cran-energy/ppc64el
  • Implicit dependency: r-base r-cran-energy/s390x
  • Implicit dependency: r-base r-cran-epi/amd64
  • Implicit dependency: r-base r-cran-epi/arm64
  • Implicit dependency: r-base r-cran-epi/armel
  • Implicit dependency: r-base r-cran-epi/armhf
  • Implicit dependency: r-base r-cran-epi/i386
  • Implicit dependency: r-base r-cran-epi/mips64el
  • Implicit dependency: r-base r-cran-epi/mipsel
  • Implicit dependency: r-base r-cran-epi/ppc64el
  • Implicit dependency: r-base r-cran-epi/s390x
  • Implicit dependency: r-base r-cran-epibasix
  • Implicit dependency: r-base r-cran-epicalc
  • Implicit dependency: r-base r-cran-epir
  • Implicit dependency: r-base r-cran-epitools
  • Implicit dependency: r-base r-cran-erm/amd64
  • Implicit dependency: r-base r-cran-erm/arm64
  • Implicit dependency: r-base r-cran-erm/armel
  • Implicit dependency: r-base r-cran-erm/armhf
  • Implicit dependency: r-base r-cran-erm/i386
  • Implicit dependency: r-base r-cran-erm/mips64el
  • Implicit dependency: r-base r-cran-erm/mipsel
  • Implicit dependency: r-base r-cran-erm/ppc64el
  • Implicit dependency: r-base r-cran-erm/s390x
  • Implicit dependency: r-base r-cran-estimability
  • Implicit dependency: r-base r-cran-etm
  • Implicit dependency: r-base r-cran-evaluate
  • Implicit dependency: r-base r-cran-evd/amd64
  • Implicit dependency: r-base r-cran-evd/arm64
  • Implicit dependency: r-base r-cran-evd/armel
  • Implicit dependency: r-base r-cran-evd/armhf
  • Implicit dependency: r-base r-cran-evd/i386
  • Implicit dependency: r-base r-cran-evd/mips64el
  • Implicit dependency: r-base r-cran-evd/mipsel
  • Implicit dependency: r-base r-cran-evd/ppc64el
  • Implicit dependency: r-base r-cran-evd/s390x
  • Implicit dependency: r-base r-cran-exactranktests/amd64
  • Implicit dependency: r-base r-cran-exactranktests/arm64
  • Implicit dependency: r-base r-cran-exactranktests/armel
  • Implicit dependency: r-base r-cran-exactranktests/armhf
  • Implicit dependency: r-base r-cran-exactranktests/i386
  • Implicit dependency: r-base r-cran-exactranktests/mips64el
  • Implicit dependency: r-base r-cran-exactranktests/mipsel
  • Implicit dependency: r-base r-cran-exactranktests/ppc64el
  • Implicit dependency: r-base r-cran-exactranktests/s390x
  • Implicit dependency: r-base r-cran-expint/amd64
  • Implicit dependency: r-base r-cran-expint/arm64
  • Implicit dependency: r-base r-cran-expint/armel
  • Implicit dependency: r-base r-cran-expint/armhf
  • Implicit dependency: r-base r-cran-expint/i386
  • Implicit dependency: r-base r-cran-expint/mips64el
  • Implicit dependency: r-base r-cran-expint/mipsel
  • Implicit dependency: r-base r-cran-expint/ppc64el
  • Implicit dependency: r-base r-cran-expint/s390x
  • Implicit dependency: r-base r-cran-expm/amd64
  • Implicit dependency: r-base r-cran-expm/arm64
  • Implicit dependency: r-base r-cran-expm/armel
  • Implicit dependency: r-base r-cran-expm/armhf
  • Implicit dependency: r-base r-cran-expm/i386
  • Implicit dependency: r-base r-cran-expm/mips64el
  • Implicit dependency: r-base r-cran-expm/mipsel
  • Implicit dependency: r-base r-cran-expm/ppc64el
  • Implicit dependency: r-base r-cran-expm/s390x
  • Implicit dependency: r-base r-cran-extradistr/amd64
  • Implicit dependency: r-base r-cran-extradistr/arm64
  • Implicit dependency: r-base r-cran-extradistr/armel
  • Implicit dependency: r-base r-cran-extradistr/armhf
  • Implicit dependency: r-base r-cran-extradistr/i386
  • Implicit dependency: r-base r-cran-extradistr/mips64el
  • Implicit dependency: r-base r-cran-extradistr/mipsel
  • Implicit dependency: r-base r-cran-extradistr/ppc64el
  • Implicit dependency: r-base r-cran-extradistr/s390x
  • Implicit dependency: r-base r-cran-factominer
  • Implicit dependency: r-base r-cran-fail
  • Implicit dependency: r-base r-cran-fansi/amd64
  • Implicit dependency: r-base r-cran-fansi/arm64
  • Implicit dependency: r-base r-cran-fansi/armel
  • Implicit dependency: r-base r-cran-fansi/armhf
  • Implicit dependency: r-base r-cran-fansi/i386
  • Implicit dependency: r-base r-cran-fansi/mips64el
  • Implicit dependency: r-base r-cran-fansi/mipsel
  • Implicit dependency: r-base r-cran-fansi/ppc64el
  • Implicit dependency: r-base r-cran-fansi/s390x
  • Implicit dependency: r-base r-cran-farver/amd64
  • Implicit dependency: r-base r-cran-farver/arm64
  • Implicit dependency: r-base r-cran-farver/armel
  • Implicit dependency: r-base r-cran-farver/armhf
  • Implicit dependency: r-base r-cran-farver/i386
  • Implicit dependency: r-base r-cran-farver/mips64el
  • Implicit dependency: r-base r-cran-farver/mipsel
  • Implicit dependency: r-base r-cran-farver/ppc64el
  • Implicit dependency: r-base r-cran-farver/s390x
  • Implicit dependency: r-base r-cran-fastcluster/amd64
  • Implicit dependency: r-base r-cran-fastcluster/arm64
  • Implicit dependency: r-base r-cran-fastcluster/armel
  • Implicit dependency: r-base r-cran-fastcluster/armhf
  • Implicit dependency: r-base r-cran-fastcluster/i386
  • Implicit dependency: r-base r-cran-fastcluster/mips64el
  • Implicit dependency: r-base r-cran-fastcluster/mipsel
  • Implicit dependency: r-base r-cran-fastcluster/ppc64el
  • Implicit dependency: r-base r-cran-fastcluster/s390x
  • Implicit dependency: r-base r-cran-fastica/amd64
  • Implicit dependency: r-base r-cran-fastica/arm64
  • Implicit dependency: r-base r-cran-fastica/armel
  • Implicit dependency: r-base r-cran-fastica/armhf
  • Implicit dependency: r-base r-cran-fastica/i386
  • Implicit dependency: r-base r-cran-fastica/mips64el
  • Implicit dependency: r-base r-cran-fastica/mipsel
  • Implicit dependency: r-base r-cran-fastica/ppc64el
  • Implicit dependency: r-base r-cran-fastica/s390x
  • Implicit dependency: r-base r-cran-fastmap/amd64
  • Implicit dependency: r-base r-cran-fastmap/arm64
  • Implicit dependency: r-base r-cran-fastmap/armel
  • Implicit dependency: r-base r-cran-fastmap/armhf
  • Implicit dependency: r-base r-cran-fastmap/i386
  • Implicit dependency: r-base r-cran-fastmap/mips64el
  • Implicit dependency: r-base r-cran-fastmap/mipsel
  • Implicit dependency: r-base r-cran-fastmap/ppc64el
  • Implicit dependency: r-base r-cran-fastmap/s390x
  • Implicit dependency: r-base r-cran-fastmatch/amd64
  • Implicit dependency: r-base r-cran-fastmatch/arm64
  • Implicit dependency: r-base r-cran-fastmatch/armel
  • Implicit dependency: r-base r-cran-fastmatch/armhf
  • Implicit dependency: r-base r-cran-fastmatch/i386
  • Implicit dependency: r-base r-cran-fastmatch/mips64el
  • Implicit dependency: r-base r-cran-fastmatch/mipsel
  • Implicit dependency: r-base r-cran-fastmatch/ppc64el
  • Implicit dependency: r-base r-cran-fastmatch/s390x
  • Implicit dependency: r-base r-cran-fauxpas
  • Implicit dependency: r-base r-cran-fdrtool/amd64
  • Implicit dependency: r-base r-cran-fdrtool/arm64
  • Implicit dependency: r-base r-cran-fdrtool/armel
  • Implicit dependency: r-base r-cran-fdrtool/armhf
  • Implicit dependency: r-base r-cran-fdrtool/i386
  • Implicit dependency: r-base r-cran-fdrtool/mips64el
  • Implicit dependency: r-base r-cran-fdrtool/mipsel
  • Implicit dependency: r-base r-cran-fdrtool/ppc64el
  • Implicit dependency: r-base r-cran-fdrtool/s390x
  • Implicit dependency: r-base r-cran-ffield
  • Implicit dependency: r-base r-cran-fields/amd64
  • Implicit dependency: r-base r-cran-fields/arm64
  • Implicit dependency: r-base r-cran-fields/armel
  • Implicit dependency: r-base r-cran-fields/armhf
  • Implicit dependency: r-base r-cran-fields/i386
  • Implicit dependency: r-base r-cran-fields/mips64el
  • Implicit dependency: r-base r-cran-fields/mipsel
  • Implicit dependency: r-base r-cran-fields/ppc64el
  • Implicit dependency: r-base r-cran-fields/s390x
  • Implicit dependency: r-base r-cran-filehash/amd64
  • Implicit dependency: r-base r-cran-filehash/arm64
  • Implicit dependency: r-base r-cran-filehash/armel
  • Implicit dependency: r-base r-cran-filehash/armhf
  • Implicit dependency: r-base r-cran-filehash/i386
  • Implicit dependency: r-base r-cran-filehash/mips64el
  • Implicit dependency: r-base r-cran-filehash/mipsel
  • Implicit dependency: r-base r-cran-filehash/ppc64el
  • Implicit dependency: r-base r-cran-filehash/s390x
  • Implicit dependency: r-base r-cran-fingerprint/amd64
  • Implicit dependency: r-base r-cran-fingerprint/arm64
  • Implicit dependency: r-base r-cran-fingerprint/armel
  • Implicit dependency: r-base r-cran-fingerprint/armhf
  • Implicit dependency: r-base r-cran-fingerprint/i386
  • Implicit dependency: r-base r-cran-fingerprint/mips64el
  • Implicit dependency: r-base r-cran-fingerprint/mipsel
  • Implicit dependency: r-base r-cran-fingerprint/ppc64el
  • Implicit dependency: r-base r-cran-fingerprint/s390x
  • Implicit dependency: r-base r-cran-fit.models
  • Implicit dependency: r-base r-cran-fitbitscraper
  • Implicit dependency: r-base r-cran-fitcoach
  • Implicit dependency: r-base r-cran-fitdistrplus
  • Implicit dependency: r-base r-cran-flashclust/amd64
  • Implicit dependency: r-base r-cran-flashclust/arm64
  • Implicit dependency: r-base r-cran-flashclust/armel
  • Implicit dependency: r-base r-cran-flashclust/armhf
  • Implicit dependency: r-base r-cran-flashclust/i386
  • Implicit dependency: r-base r-cran-flashclust/mips64el
  • Implicit dependency: r-base r-cran-flashclust/mipsel
  • Implicit dependency: r-base r-cran-flashclust/ppc64el
  • Implicit dependency: r-base r-cran-flashclust/s390x
  • Implicit dependency: r-base r-cran-flexmix
  • Implicit dependency: r-base r-cran-fnn/amd64
  • Implicit dependency: r-base r-cran-fnn/arm64
  • Implicit dependency: r-base r-cran-fnn/armel
  • Implicit dependency: r-base r-cran-fnn/armhf
  • Implicit dependency: r-base r-cran-fnn/i386
  • Implicit dependency: r-base r-cran-fnn/mips64el
  • Implicit dependency: r-base r-cran-fnn/mipsel
  • Implicit dependency: r-base r-cran-fnn/ppc64el
  • Implicit dependency: r-base r-cran-fnn/s390x
  • Implicit dependency: r-base r-cran-fontbitstreamvera
  • Implicit dependency: r-base r-cran-fontliberation
  • Implicit dependency: r-base r-cran-fontquiver
  • Implicit dependency: r-base r-cran-forcats
  • Implicit dependency: r-base r-cran-foreach
  • Implicit dependency: r-base r-cran-forecast/amd64
  • Implicit dependency: r-base r-cran-forecast/arm64
  • Implicit dependency: r-base r-cran-forecast/armel
  • Implicit dependency: r-base r-cran-forecast/armhf
  • Implicit dependency: r-base r-cran-forecast/i386
  • Implicit dependency: r-base r-cran-forecast/mips64el
  • Implicit dependency: r-base r-cran-forecast/mipsel
  • Implicit dependency: r-base r-cran-forecast/ppc64el
  • Implicit dependency: r-base r-cran-forecast/s390x
  • Implicit dependency: r-base r-cran-formatr
  • Implicit dependency: r-base r-cran-formula
  • Implicit dependency: r-base r-cran-fpc
  • Implicit dependency: r-base r-cran-fracdiff/amd64
  • Implicit dependency: r-base r-cran-fracdiff/arm64
  • Implicit dependency: r-base r-cran-fracdiff/armel
  • Implicit dependency: r-base r-cran-fracdiff/armhf
  • Implicit dependency: r-base r-cran-fracdiff/i386
  • Implicit dependency: r-base r-cran-fracdiff/mips64el
  • Implicit dependency: r-base r-cran-fracdiff/mipsel
  • Implicit dependency: r-base r-cran-fracdiff/ppc64el
  • Implicit dependency: r-base r-cran-fracdiff/s390x
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/amd64
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/arm64
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/armel
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/armhf
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/i386
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/mips64el
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/mipsel
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/ppc64el
  • Implicit dependency: r-base r-cran-freetypeharfbuzz/s390x
  • Implicit dependency: r-base r-cran-fs/amd64
  • Implicit dependency: r-base r-cran-fs/arm64
  • Implicit dependency: r-base r-cran-fs/armel
  • Implicit dependency: r-base r-cran-fs/armhf
  • Implicit dependency: r-base r-cran-fs/i386
  • Implicit dependency: r-base r-cran-fs/mips64el
  • Implicit dependency: r-base r-cran-fs/mipsel
  • Implicit dependency: r-base r-cran-fs/ppc64el
  • Implicit dependency: r-base r-cran-fs/s390x
  • Implicit dependency: r-base r-cran-fts/amd64
  • Implicit dependency: r-base r-cran-fts/arm64
  • Implicit dependency: r-base r-cran-fts/armel
  • Implicit dependency: r-base r-cran-fts/armhf
  • Implicit dependency: r-base r-cran-fts/i386
  • Implicit dependency: r-base r-cran-fts/mips64el
  • Implicit dependency: r-base r-cran-fts/mipsel
  • Implicit dependency: r-base r-cran-fts/ppc64el
  • Implicit dependency: r-base r-cran-fts/s390x
  • Implicit dependency: r-base r-cran-furrr
  • Implicit dependency: r-base r-cran-futile.logger
  • Implicit dependency: r-base r-cran-futile.options
  • Implicit dependency: r-base r-cran-future
  • Implicit dependency: r-base r-cran-future.apply
  • Implicit dependency: r-base r-cran-future.batchtools
  • Implicit dependency: r-base r-cran-g.data
  • Implicit dependency: r-base r-cran-gam/amd64
  • Implicit dependency: r-base r-cran-gam/arm64
  • Implicit dependency: r-base r-cran-gam/armel
  • Implicit dependency: r-base r-cran-gam/armhf
  • Implicit dependency: r-base r-cran-gam/i386
  • Implicit dependency: r-base r-cran-gam/mips64el
  • Implicit dependency: r-base r-cran-gam/mipsel
  • Implicit dependency: r-base r-cran-gam/ppc64el
  • Implicit dependency: r-base r-cran-gam/s390x
  • Implicit dependency: r-base r-cran-gbm/amd64
  • Implicit dependency: r-base r-cran-gbm/arm64
  • Implicit dependency: r-base r-cran-gbm/armel
  • Implicit dependency: r-base r-cran-gbm/armhf
  • Implicit dependency: r-base r-cran-gbm/i386
  • Implicit dependency: r-base r-cran-gbm/mips64el
  • Implicit dependency: r-base r-cran-gbm/mipsel
  • Implicit dependency: r-base r-cran-gbm/ppc64el
  • Implicit dependency: r-base r-cran-gbm/s390x
  • Implicit dependency: r-base r-cran-gbrd/amd64
  • Implicit dependency: r-base r-cran-gbrd/arm64
  • Implicit dependency: r-base r-cran-gbrd/armel
  • Implicit dependency: r-base r-cran-gbrd/armhf
  • Implicit dependency: r-base r-cran-gbrd/i386
  • Implicit dependency: r-base r-cran-gbrd/mips64el
  • Implicit dependency: r-base r-cran-gbrd/mipsel
  • Implicit dependency: r-base r-cran-gbrd/ppc64el
  • Implicit dependency: r-base r-cran-gbrd/s390x
  • Implicit dependency: r-base r-cran-gclus
  • Implicit dependency: r-base r-cran-gdtools/amd64
  • Implicit dependency: r-base r-cran-gdtools/arm64
  • Implicit dependency: r-base r-cran-gdtools/armel
  • Implicit dependency: r-base r-cran-gdtools/armhf
  • Implicit dependency: r-base r-cran-gdtools/i386
  • Implicit dependency: r-base r-cran-gdtools/mips64el
  • Implicit dependency: r-base r-cran-gdtools/mipsel
  • Implicit dependency: r-base r-cran-gdtools/ppc64el
  • Implicit dependency: r-base r-cran-gdtools/s390x
  • Implicit dependency: r-base r-cran-gee/amd64
  • Implicit dependency: r-base r-cran-gee/arm64
  • Implicit dependency: r-base r-cran-gee/armel
  • Implicit dependency: r-base r-cran-gee/armhf
  • Implicit dependency: r-base r-cran-gee/i386
  • Implicit dependency: r-base r-cran-gee/mips64el
  • Implicit dependency: r-base r-cran-gee/mipsel
  • Implicit dependency: r-base r-cran-gee/ppc64el
  • Implicit dependency: r-base r-cran-gee/s390x
  • Implicit dependency: r-base r-cran-geepack/amd64
  • Implicit dependency: r-base r-cran-geepack/arm64
  • Implicit dependency: r-base r-cran-geepack/armel
  • Implicit dependency: r-base r-cran-geepack/armhf
  • Implicit dependency: r-base r-cran-geepack/i386
  • Implicit dependency: r-base r-cran-geepack/mips64el
  • Implicit dependency: r-base r-cran-geepack/mipsel
  • Implicit dependency: r-base r-cran-geepack/ppc64el
  • Implicit dependency: r-base r-cran-geepack/s390x
  • Implicit dependency: r-base r-cran-genabel.data
  • Implicit dependency: r-base r-cran-genabel/amd64
  • Implicit dependency: r-base r-cran-genabel/arm64
  • Implicit dependency: r-base r-cran-genabel/armel
  • Implicit dependency: r-base r-cran-genabel/armhf
  • Implicit dependency: r-base r-cran-genabel/i386
  • Implicit dependency: r-base r-cran-genabel/mips64el
  • Implicit dependency: r-base r-cran-genabel/mipsel
  • Implicit dependency: r-base r-cran-genabel/ppc64el
  • Implicit dependency: r-base r-cran-genabel/s390x
  • Implicit dependency: r-base r-cran-generics
  • Implicit dependency: r-base r-cran-genetics
  • Implicit dependency: r-base r-cran-geometry/amd64
  • Implicit dependency: r-base r-cran-geometry/arm64
  • Implicit dependency: r-base r-cran-geometry/armel
  • Implicit dependency: r-base r-cran-geometry/armhf
  • Implicit dependency: r-base r-cran-geometry/i386
  • Implicit dependency: r-base r-cran-geometry/mips64el
  • Implicit dependency: r-base r-cran-geometry/mipsel
  • Implicit dependency: r-base r-cran-geometry/ppc64el
  • Implicit dependency: r-base r-cran-geometry/s390x
  • Implicit dependency: r-base r-cran-geosphere/amd64
  • Implicit dependency: r-base r-cran-geosphere/arm64
  • Implicit dependency: r-base r-cran-geosphere/armel
  • Implicit dependency: r-base r-cran-geosphere/armhf
  • Implicit dependency: r-base r-cran-geosphere/i386
  • Implicit dependency: r-base r-cran-geosphere/mips64el
  • Implicit dependency: r-base r-cran-geosphere/mipsel
  • Implicit dependency: r-base r-cran-geosphere/ppc64el
  • Implicit dependency: r-base r-cran-geosphere/s390x
  • Implicit dependency: r-base r-cran-getopt
  • Implicit dependency: r-base r-cran-ggally
  • Implicit dependency: r-base r-cran-ggbeeswarm
  • Implicit dependency: r-base r-cran-ggdendro
  • Implicit dependency: r-base r-cran-ggeffects
  • Implicit dependency: r-base r-cran-ggforce/amd64
  • Implicit dependency: r-base r-cran-ggforce/arm64
  • Implicit dependency: r-base r-cran-ggforce/armel
  • Implicit dependency: r-base r-cran-ggforce/armhf
  • Implicit dependency: r-base r-cran-ggforce/i386
  • Implicit dependency: r-base r-cran-ggforce/mips64el
  • Implicit dependency: r-base r-cran-ggforce/mipsel
  • Implicit dependency: r-base r-cran-ggforce/ppc64el
  • Implicit dependency: r-base r-cran-ggforce/s390x
  • Implicit dependency: r-base r-cran-ggplot2
  • Implicit dependency: r-base r-cran-ggpubr
  • Implicit dependency: r-base r-cran-ggraph
  • Implicit dependency: r-base r-cran-ggrepel/amd64
  • Implicit dependency: r-base r-cran-ggrepel/arm64
  • Implicit dependency: r-base r-cran-ggrepel/armel
  • Implicit dependency: r-base r-cran-ggrepel/armhf
  • Implicit dependency: r-base r-cran-ggrepel/i386
  • Implicit dependency: r-base r-cran-ggrepel/mips64el
  • Implicit dependency: r-base r-cran-ggrepel/mipsel
  • Implicit dependency: r-base r-cran-ggrepel/ppc64el
  • Implicit dependency: r-base r-cran-ggrepel/s390x
  • Implicit dependency: r-base r-cran-ggridges
  • Implicit dependency: r-base r-cran-ggsci
  • Implicit dependency: r-base r-cran-ggsignif
  • Implicit dependency: r-base r-cran-ggthemes
  • Implicit dependency: r-base r-cran-ggvis
  • Implicit dependency: r-base r-cran-gh
  • Implicit dependency: r-base r-cran-git2r/amd64
  • Implicit dependency: r-base r-cran-git2r/arm64
  • Implicit dependency: r-base r-cran-git2r/armel
  • Implicit dependency: r-base r-cran-git2r/armhf
  • Implicit dependency: r-base r-cran-git2r/i386
  • Implicit dependency: r-base r-cran-git2r/mips64el
  • Implicit dependency: r-base r-cran-git2r/mipsel
  • Implicit dependency: r-base r-cran-git2r/ppc64el
  • Implicit dependency: r-base r-cran-git2r/s390x
  • Implicit dependency: r-base r-cran-glasso/amd64
  • Implicit dependency: r-base r-cran-glasso/arm64
  • Implicit dependency: r-base r-cran-glasso/armel
  • Implicit dependency: r-base r-cran-glasso/armhf
  • Implicit dependency: r-base r-cran-glasso/i386
  • Implicit dependency: r-base r-cran-glasso/mips64el
  • Implicit dependency: r-base r-cran-glasso/mipsel
  • Implicit dependency: r-base r-cran-glasso/ppc64el
  • Implicit dependency: r-base r-cran-glasso/s390x
  • Implicit dependency: r-base r-cran-glmmtmb/amd64
  • Implicit dependency: r-base r-cran-glmmtmb/arm64
  • Implicit dependency: r-base r-cran-glmmtmb/armel
  • Implicit dependency: r-base r-cran-glmmtmb/armhf
  • Implicit dependency: r-base r-cran-glmmtmb/i386
  • Implicit dependency: r-base r-cran-glmmtmb/mips64el
  • Implicit dependency: r-base r-cran-glmmtmb/mipsel
  • Implicit dependency: r-base r-cran-glmmtmb/ppc64el
  • Implicit dependency: r-base r-cran-glmmtmb/s390x
  • Implicit dependency: r-base r-cran-glmnet
  • Implicit dependency: r-base r-cran-globaloptions
  • Implicit dependency: r-base r-cran-globals
  • Implicit dependency: r-base r-cran-glue
  • Implicit dependency: r-base r-cran-gmaps
  • Implicit dependency: r-base r-cran-gmm/amd64
  • Implicit dependency: r-base r-cran-gmm/arm64
  • Implicit dependency: r-base r-cran-gmm/armel
  • Implicit dependency: r-base r-cran-gmm/armhf
  • Implicit dependency: r-base r-cran-gmm/i386
  • Implicit dependency: r-base r-cran-gmm/mips64el
  • Implicit dependency: r-base r-cran-gmm/mipsel
  • Implicit dependency: r-base r-cran-gmm/ppc64el
  • Implicit dependency: r-base r-cran-gmm/s390x
  • Implicit dependency: r-base r-cran-gnm/amd64
  • Implicit dependency: r-base r-cran-gnm/arm64
  • Implicit dependency: r-base r-cran-gnm/armel
  • Implicit dependency: r-base r-cran-gnm/armhf
  • Implicit dependency: r-base r-cran-gnm/i386
  • Implicit dependency: r-base r-cran-gnm/mips64el
  • Implicit dependency: r-base r-cran-gnm/mipsel
  • Implicit dependency: r-base r-cran-gnm/ppc64el
  • Implicit dependency: r-base r-cran-gnm/s390x
  • Implicit dependency: r-base r-cran-goftest/amd64
  • Implicit dependency: r-base r-cran-goftest/arm64
  • Implicit dependency: r-base r-cran-goftest/armel
  • Implicit dependency: r-base r-cran-goftest/armhf
  • Implicit dependency: r-base r-cran-goftest/i386
  • Implicit dependency: r-base r-cran-goftest/mips64el
  • Implicit dependency: r-base r-cran-goftest/mipsel
  • Implicit dependency: r-base r-cran-goftest/ppc64el
  • Implicit dependency: r-base r-cran-goftest/s390x
  • Implicit dependency: r-base r-cran-googlevis
  • Implicit dependency: r-base r-cran-gower/amd64
  • Implicit dependency: r-base r-cran-gower/arm64
  • Implicit dependency: r-base r-cran-gower/armel
  • Implicit dependency: r-base r-cran-gower/armhf
  • Implicit dependency: r-base r-cran-gower/i386
  • Implicit dependency: r-base r-cran-gower/mips64el
  • Implicit dependency: r-base r-cran-gower/mipsel
  • Implicit dependency: r-base r-cran-gower/ppc64el
  • Implicit dependency: r-base r-cran-gower/s390x
  • Implicit dependency: r-base r-cran-gparotation
  • Implicit dependency: r-base r-cran-gprofiler
  • Implicit dependency: r-base r-cran-graphlayouts/amd64
  • Implicit dependency: r-base r-cran-graphlayouts/arm64
  • Implicit dependency: r-base r-cran-graphlayouts/armel
  • Implicit dependency: r-base r-cran-graphlayouts/armhf
  • Implicit dependency: r-base r-cran-graphlayouts/i386
  • Implicit dependency: r-base r-cran-graphlayouts/mips64el
  • Implicit dependency: r-base r-cran-graphlayouts/mipsel
  • Implicit dependency: r-base r-cran-graphlayouts/ppc64el
  • Implicit dependency: r-base r-cran-graphlayouts/s390x
  • Implicit dependency: r-base r-cran-gridbase
  • Implicit dependency: r-base r-cran-gridextra
  • Implicit dependency: r-base r-cran-gridgraphics
  • Implicit dependency: r-base r-cran-gridsvg
  • Implicit dependency: r-base r-cran-grimport2
  • Implicit dependency: r-base r-cran-gsa
  • Implicit dependency: r-base r-cran-gsl/amd64
  • Implicit dependency: r-base r-cran-gsl/arm64
  • Implicit dependency: r-base r-cran-gsl/armel
  • Implicit dependency: r-base r-cran-gsl/armhf
  • Implicit dependency: r-base r-cran-gsl/i386
  • Implicit dependency: r-base r-cran-gsl/mips64el
  • Implicit dependency: r-base r-cran-gsl/mipsel
  • Implicit dependency: r-base r-cran-gsl/ppc64el
  • Implicit dependency: r-base r-cran-gsl/s390x
  • Implicit dependency: r-base r-cran-gss
  • Implicit dependency: r-base r-cran-gtable
  • Implicit dependency: r-base r-cran-guerry
  • Implicit dependency: r-base r-cran-gwidgets
  • Implicit dependency: r-base r-cran-gwidgetsrgtk2
  • Implicit dependency: r-base r-cran-haplo.stats/amd64
  • Implicit dependency: r-base r-cran-haplo.stats/arm64
  • Implicit dependency: r-base r-cran-haplo.stats/armhf
  • Implicit dependency: r-base r-cran-haplo.stats/i386
  • Implicit dependency: r-base r-cran-haplo.stats/mips64el
  • Implicit dependency: r-base r-cran-haplo.stats/mipsel
  • Implicit dependency: r-base r-cran-haplo.stats/ppc64el
  • Implicit dependency: r-base r-cran-haplo.stats/s390x
  • Implicit dependency: r-base r-cran-hash
  • Implicit dependency: r-base r-cran-haven/amd64
  • Implicit dependency: r-base r-cran-haven/arm64
  • Implicit dependency: r-base r-cran-haven/armel
  • Implicit dependency: r-base r-cran-haven/armhf
  • Implicit dependency: r-base r-cran-haven/i386
  • Implicit dependency: r-base r-cran-haven/mips64el
  • Implicit dependency: r-base r-cran-haven/mipsel
  • Implicit dependency: r-base r-cran-haven/ppc64el
  • Implicit dependency: r-base r-cran-haven/s390x
  • Implicit dependency: r-base r-cran-hdf5/amd64
  • Implicit dependency: r-base r-cran-hdf5/arm64
  • Implicit dependency: r-base r-cran-hdf5/armel
  • Implicit dependency: r-base r-cran-hdf5/armhf
  • Implicit dependency: r-base r-cran-hdf5/i386
  • Implicit dependency: r-base r-cran-hdf5/mips64el
  • Implicit dependency: r-base r-cran-hdf5/mipsel
  • Implicit dependency: r-base r-cran-hdf5/ppc64el
  • Implicit dependency: r-base r-cran-hdf5/s390x
  • Implicit dependency: r-base r-cran-heatmaply
  • Implicit dependency: r-base r-cran-hexbin/amd64
  • Implicit dependency: r-base r-cran-hexbin/arm64
  • Implicit dependency: r-base r-cran-hexbin/armel
  • Implicit dependency: r-base r-cran-hexbin/armhf
  • Implicit dependency: r-base r-cran-hexbin/i386
  • Implicit dependency: r-base r-cran-hexbin/mips64el
  • Implicit dependency: r-base r-cran-hexbin/mipsel
  • Implicit dependency: r-base r-cran-hexbin/ppc64el
  • Implicit dependency: r-base r-cran-hexbin/s390x
  • Implicit dependency: r-base r-cran-highr
  • Implicit dependency: r-base r-cran-hms
  • Implicit dependency: r-base r-cran-hsaur3
  • Implicit dependency: r-base r-cran-htmltable
  • Implicit dependency: r-base r-cran-htmltools
  • Implicit dependency: r-base r-cran-htmlwidgets
  • Implicit dependency: r-base r-cran-httpcode
  • Implicit dependency: r-base r-cran-httpuv
  • Implicit dependency: r-base r-cran-httr
  • Implicit dependency: r-base r-cran-huge/amd64
  • Implicit dependency: r-base r-cran-huge/arm64
  • Implicit dependency: r-base r-cran-huge/armel
  • Implicit dependency: r-base r-cran-huge/armhf
  • Implicit dependency: r-base r-cran-huge/i386
  • Implicit dependency: r-base r-cran-huge/mips64el
  • Implicit dependency: r-base r-cran-huge/mipsel
  • Implicit dependency: r-base r-cran-huge/ppc64el
  • Implicit dependency: r-base r-cran-huge/s390x
  • Implicit dependency: r-base r-cran-hwriter
  • Implicit dependency: r-base r-cran-hypergeo
  • Implicit dependency: r-base r-cran-ica
  • Implicit dependency: r-base r-cran-igraph/amd64
  • Implicit dependency: r-base r-cran-igraph/arm64
  • Implicit dependency: r-base r-cran-igraph/armel
  • Implicit dependency: r-base r-cran-igraph/armhf
  • Implicit dependency: r-base r-cran-igraph/i386
  • Implicit dependency: r-base r-cran-igraph/mips64el
  • Implicit dependency: r-base r-cran-igraph/mipsel
  • Implicit dependency: r-base r-cran-igraph/ppc64el
  • Implicit dependency: r-base r-cran-igraph/s390x
  • Implicit dependency: r-base r-cran-ini
  • Implicit dependency: r-base r-cran-inline
  • Implicit dependency: r-base r-cran-insight
  • Implicit dependency: r-base r-cran-int64/amd64
  • Implicit dependency: r-base r-cran-int64/arm64
  • Implicit dependency: r-base r-cran-int64/armel
  • Implicit dependency: r-base r-cran-int64/armhf
  • Implicit dependency: r-base r-cran-int64/i386
  • Implicit dependency: r-base r-cran-int64/mips64el
  • Implicit dependency: r-base r-cran-int64/mipsel
  • Implicit dependency: r-base r-cran-int64/ppc64el
  • Implicit dependency: r-base r-cran-int64/s390x
  • Implicit dependency: r-base r-cran-interp/amd64
  • Implicit dependency: r-base r-cran-interp/arm64
  • Implicit dependency: r-base r-cran-interp/armel
  • Implicit dependency: r-base r-cran-interp/armhf
  • Implicit dependency: r-base r-cran-interp/i386
  • Implicit dependency: r-base r-cran-interp/mips64el
  • Implicit dependency: r-base r-cran-interp/mipsel
  • Implicit dependency: r-base r-cran-interp/ppc64el
  • Implicit dependency: r-base r-cran-interp/s390x
  • Implicit dependency: r-base r-cran-intervals/amd64
  • Implicit dependency: r-base r-cran-intervals/arm64
  • Implicit dependency: r-base r-cran-intervals/armel
  • Implicit dependency: r-base r-cran-intervals/armhf
  • Implicit dependency: r-base r-cran-intervals/i386
  • Implicit dependency: r-base r-cran-intervals/mips64el
  • Implicit dependency: r-base r-cran-intervals/mipsel
  • Implicit dependency: r-base r-cran-intervals/ppc64el
  • Implicit dependency: r-base r-cran-intervals/s390x
  • Implicit dependency: r-base r-cran-inum
  • Implicit dependency: r-base r-cran-ipred/amd64
  • Implicit dependency: r-base r-cran-ipred/arm64
  • Implicit dependency: r-base r-cran-ipred/armel
  • Implicit dependency: r-base r-cran-ipred/armhf
  • Implicit dependency: r-base r-cran-ipred/i386
  • Implicit dependency: r-base r-cran-ipred/mips64el
  • Implicit dependency: r-base r-cran-ipred/mipsel
  • Implicit dependency: r-base r-cran-ipred/ppc64el
  • Implicit dependency: r-base r-cran-ipred/s390x
  • Implicit dependency: r-base r-cran-irace/amd64
  • Implicit dependency: r-base r-cran-irace/arm64
  • Implicit dependency: r-base r-cran-irace/armel
  • Implicit dependency: r-base r-cran-irace/armhf
  • Implicit dependency: r-base r-cran-irace/i386
  • Implicit dependency: r-base r-cran-irace/mips64el
  • Implicit dependency: r-base r-cran-irace/mipsel
  • Implicit dependency: r-base r-cran-irace/ppc64el
  • Implicit dependency: r-base r-cran-irace/s390x
  • Implicit dependency: r-base r-cran-irdisplay
  • Implicit dependency: r-base r-cran-irkernel
  • Implicit dependency: r-base r-cran-irlba/amd64
  • Implicit dependency: r-base r-cran-irlba/arm64
  • Implicit dependency: r-base r-cran-irlba/armel
  • Implicit dependency: r-base r-cran-irlba/armhf
  • Implicit dependency: r-base r-cran-irlba/i386
  • Implicit dependency: r-base r-cran-irlba/mips64el
  • Implicit dependency: r-base r-cran-irlba/mipsel
  • Implicit dependency: r-base r-cran-irlba/ppc64el
  • Implicit dependency: r-base r-cran-irlba/s390x
  • Implicit dependency: r-base r-cran-iso/amd64
  • Implicit dependency: r-base r-cran-iso/arm64
  • Implicit dependency: r-base r-cran-iso/armel
  • Implicit dependency: r-base r-cran-iso/armhf
  • Implicit dependency: r-base r-cran-iso/i386
  • Implicit dependency: r-base r-cran-iso/mips64el
  • Implicit dependency: r-base r-cran-iso/mipsel
  • Implicit dependency: r-base r-cran-iso/ppc64el
  • Implicit dependency: r-base r-cran-iso/s390x
  • Implicit dependency: r-base r-cran-isoband/amd64
  • Implicit dependency: r-base r-cran-isoband/arm64
  • Implicit dependency: r-base r-cran-isoband/armel
  • Implicit dependency: r-base r-cran-isoband/armhf
  • Implicit dependency: r-base r-cran-isoband/i386
  • Implicit dependency: r-base r-cran-isoband/mips64el
  • Implicit dependency: r-base r-cran-isoband/mipsel
  • Implicit dependency: r-base r-cran-isoband/ppc64el
  • Implicit dependency: r-base r-cran-isoband/s390x
  • Implicit dependency: r-base r-cran-isocodes
  • Implicit dependency: r-base r-cran-isoweek
  • Implicit dependency: r-base r-cran-iterators
  • Implicit dependency: r-base r-cran-itertools
  • Implicit dependency: r-base r-cran-jomo
  • Implicit dependency: r-base r-cran-jpeg/amd64
  • Implicit dependency: r-base r-cran-jpeg/arm64
  • Implicit dependency: r-base r-cran-jpeg/armel
  • Implicit dependency: r-base r-cran-jpeg/armhf
  • Implicit dependency: r-base r-cran-jpeg/i386
  • Implicit dependency: r-base r-cran-jpeg/mips64el
  • Implicit dependency: r-base r-cran-jpeg/mipsel
  • Implicit dependency: r-base r-cran-jpeg/ppc64el
  • Implicit dependency: r-base r-cran-jpeg/s390x
  • Implicit dependency: r-base r-cran-jrc
  • Implicit dependency: r-base r-cran-jsonld
  • Implicit dependency: r-base r-cran-jsonlite/amd64
  • Implicit dependency: r-base r-cran-jsonlite/arm64
  • Implicit dependency: r-base r-cran-jsonlite/armel
  • Implicit dependency: r-base r-cran-jsonlite/armhf
  • Implicit dependency: r-base r-cran-jsonlite/i386
  • Implicit dependency: r-base r-cran-jsonlite/mips64el
  • Implicit dependency: r-base r-cran-jsonlite/mipsel
  • Implicit dependency: r-base r-cran-jsonlite/ppc64el
  • Implicit dependency: r-base r-cran-jsonlite/s390x
  • Implicit dependency: r-base r-cran-kaos
  • Implicit dependency: r-base r-cran-kedd
  • Implicit dependency: r-base r-cran-kernlab/amd64
  • Implicit dependency: r-base r-cran-kernlab/arm64
  • Implicit dependency: r-base r-cran-kernlab/armel
  • Implicit dependency: r-base r-cran-kernlab/armhf
  • Implicit dependency: r-base r-cran-kernlab/i386
  • Implicit dependency: r-base r-cran-kernlab/mips64el
  • Implicit dependency: r-base r-cran-kernlab/mipsel
  • Implicit dependency: r-base r-cran-kernlab/ppc64el
  • Implicit dependency: r-base r-cran-kernlab/s390x
  • Implicit dependency: r-base r-cran-km.ci/amd64
  • Implicit dependency: r-base r-cran-km.ci/arm64
  • Implicit dependency: r-base r-cran-km.ci/armel
  • Implicit dependency: r-base r-cran-km.ci/armhf
  • Implicit dependency: r-base r-cran-km.ci/i386
  • Implicit dependency: r-base r-cran-km.ci/mips64el
  • Implicit dependency: r-base r-cran-km.ci/mipsel
  • Implicit dependency: r-base r-cran-km.ci/ppc64el
  • Implicit dependency: r-base r-cran-km.ci/s390x
  • Implicit dependency: r-base r-cran-kmi
  • Implicit dependency: r-base r-cran-kmsurv/amd64
  • Implicit dependency: r-base r-cran-kmsurv/arm64
  • Implicit dependency: r-base r-cran-kmsurv/armel
  • Implicit dependency: r-base r-cran-kmsurv/armhf
  • Implicit dependency: r-base r-cran-kmsurv/i386
  • Implicit dependency: r-base r-cran-kmsurv/mips64el
  • Implicit dependency: r-base r-cran-kmsurv/mipsel
  • Implicit dependency: r-base r-cran-kmsurv/ppc64el
  • Implicit dependency: r-base r-cran-kmsurv/s390x
  • Implicit dependency: r-base r-cran-knitr
  • Implicit dependency: r-base r-cran-ks/amd64
  • Implicit dependency: r-base r-cran-ks/arm64
  • Implicit dependency: r-base r-cran-ks/armel
  • Implicit dependency: r-base r-cran-ks/armhf
  • Implicit dependency: r-base r-cran-ks/i386
  • Implicit dependency: r-base r-cran-ks/mips64el
  • Implicit dependency: r-base r-cran-ks/mipsel
  • Implicit dependency: r-base r-cran-ks/ppc64el
  • Implicit dependency: r-base r-cran-ks/s390x
  • Implicit dependency: r-base r-cran-kutils
  • Implicit dependency: r-base r-cran-labeling
  • Implicit dependency: r-base r-cran-lambda.r
  • Implicit dependency: r-base r-cran-lasso2/amd64
  • Implicit dependency: r-base r-cran-lasso2/arm64
  • Implicit dependency: r-base r-cran-lasso2/armel
  • Implicit dependency: r-base r-cran-lasso2/armhf
  • Implicit dependency: r-base r-cran-lasso2/i386
  • Implicit dependency: r-base r-cran-lasso2/mips64el
  • Implicit dependency: r-base r-cran-lasso2/mipsel
  • Implicit dependency: r-base r-cran-lasso2/ppc64el
  • Implicit dependency: r-base r-cran-lasso2/s390x
  • Implicit dependency: r-base r-cran-later/amd64
  • Implicit dependency: r-base r-cran-later/arm64
  • Implicit dependency: r-base r-cran-later/armel
  • Implicit dependency: r-base r-cran-later/armhf
  • Implicit dependency: r-base r-cran-later/i386
  • Implicit dependency: r-base r-cran-later/mips64el
  • Implicit dependency: r-base r-cran-later/mipsel
  • Implicit dependency: r-base r-cran-later/ppc64el
  • Implicit dependency: r-base r-cran-later/s390x
  • Implicit dependency: r-base r-cran-lava
  • Implicit dependency: r-base r-cran-lavaan
  • Implicit dependency: r-base r-cran-lavasearch2/amd64
  • Implicit dependency: r-base r-cran-lavasearch2/arm64
  • Implicit dependency: r-base r-cran-lavasearch2/armel
  • Implicit dependency: r-base r-cran-lavasearch2/armhf
  • Implicit dependency: r-base r-cran-lavasearch2/i386
  • Implicit dependency: r-base r-cran-lavasearch2/mips64el
  • Implicit dependency: r-base r-cran-lavasearch2/mipsel
  • Implicit dependency: r-base r-cran-lavasearch2/ppc64el
  • Implicit dependency: r-base r-cran-lavasearch2/s390x
  • Implicit dependency: r-base r-cran-lazyeval/amd64
  • Implicit dependency: r-base r-cran-lazyeval/arm64
  • Implicit dependency: r-base r-cran-lazyeval/armel
  • Implicit dependency: r-base r-cran-lazyeval/armhf
  • Implicit dependency: r-base r-cran-lazyeval/i386
  • Implicit dependency: r-base r-cran-lazyeval/mips64el
  • Implicit dependency: r-base r-cran-lazyeval/mipsel
  • Implicit dependency: r-base r-cran-lazyeval/ppc64el
  • Implicit dependency: r-base r-cran-lazyeval/s390x
  • Implicit dependency: r-base r-cran-leaps/amd64
  • Implicit dependency: r-base r-cran-leaps/arm64
  • Implicit dependency: r-base r-cran-leaps/armel
  • Implicit dependency: r-base r-cran-leaps/armhf
  • Implicit dependency: r-base r-cran-leaps/i386
  • Implicit dependency: r-base r-cran-leaps/mips64el
  • Implicit dependency: r-base r-cran-leaps/mipsel
  • Implicit dependency: r-base r-cran-leaps/ppc64el
  • Implicit dependency: r-base r-cran-leaps/s390x
  • Implicit dependency: r-base r-cran-learnbayes
  • Implicit dependency: r-base r-cran-leiden
  • Implicit dependency: r-base r-cran-lexrankr/amd64
  • Implicit dependency: r-base r-cran-lexrankr/arm64
  • Implicit dependency: r-base r-cran-lexrankr/armel
  • Implicit dependency: r-base r-cran-lexrankr/armhf
  • Implicit dependency: r-base r-cran-lexrankr/i386
  • Implicit dependency: r-base r-cran-lexrankr/mips64el
  • Implicit dependency: r-base r-cran-lexrankr/mipsel
  • Implicit dependency: r-base r-cran-lexrankr/ppc64el
  • Implicit dependency: r-base r-cran-lexrankr/s390x
  • Implicit dependency: r-base r-cran-lhs/amd64
  • Implicit dependency: r-base r-cran-lhs/arm64
  • Implicit dependency: r-base r-cran-lhs/armel
  • Implicit dependency: r-base r-cran-lhs/armhf
  • Implicit dependency: r-base r-cran-lhs/i386
  • Implicit dependency: r-base r-cran-lhs/mips64el
  • Implicit dependency: r-base r-cran-lhs/mipsel
  • Implicit dependency: r-base r-cran-lhs/ppc64el
  • Implicit dependency: r-base r-cran-lhs/s390x
  • Implicit dependency: r-base r-cran-libcoin/amd64
  • Implicit dependency: r-base r-cran-libcoin/arm64
  • Implicit dependency: r-base r-cran-libcoin/armel
  • Implicit dependency: r-base r-cran-libcoin/armhf
  • Implicit dependency: r-base r-cran-libcoin/i386
  • Implicit dependency: r-base r-cran-libcoin/mips64el
  • Implicit dependency: r-base r-cran-libcoin/mipsel
  • Implicit dependency: r-base r-cran-libcoin/ppc64el
  • Implicit dependency: r-base r-cran-libcoin/s390x
  • Implicit dependency: r-base r-cran-lifecycle
  • Implicit dependency: r-base r-cran-linprog/amd64
  • Implicit dependency: r-base r-cran-linprog/arm64
  • Implicit dependency: r-base r-cran-linprog/armel
  • Implicit dependency: r-base r-cran-linprog/armhf
  • Implicit dependency: r-base r-cran-linprog/i386
  • Implicit dependency: r-base r-cran-linprog/mips64el
  • Implicit dependency: r-base r-cran-linprog/mipsel
  • Implicit dependency: r-base r-cran-linprog/ppc64el
  • Implicit dependency: r-base r-cran-linprog/s390x
  • Implicit dependency: r-base r-cran-lisreltor
  • Implicit dependency: r-base r-cran-listenv
  • Implicit dependency: r-base r-cran-lmertest
  • Implicit dependency: r-base r-cran-locfit/amd64
  • Implicit dependency: r-base r-cran-locfit/arm64
  • Implicit dependency: r-base r-cran-locfit/armel
  • Implicit dependency: r-base r-cran-locfit/armhf
  • Implicit dependency: r-base r-cran-locfit/i386
  • Implicit dependency: r-base r-cran-locfit/mips64el
  • Implicit dependency: r-base r-cran-locfit/mipsel
  • Implicit dependency: r-base r-cran-locfit/ppc64el
  • Implicit dependency: r-base r-cran-locfit/s390x
  • Implicit dependency: r-base r-cran-logcondens
  • Implicit dependency: r-base r-cran-logging
  • Implicit dependency: r-base r-cran-logspline/amd64
  • Implicit dependency: r-base r-cran-logspline/arm64
  • Implicit dependency: r-base r-cran-logspline/armel
  • Implicit dependency: r-base r-cran-logspline/armhf
  • Implicit dependency: r-base r-cran-logspline/i386
  • Implicit dependency: r-base r-cran-logspline/mips64el
  • Implicit dependency: r-base r-cran-logspline/mipsel
  • Implicit dependency: r-base r-cran-logspline/ppc64el
  • Implicit dependency: r-base r-cran-logspline/s390x
  • Implicit dependency: r-base r-cran-loo
  • Implicit dependency: r-base r-cran-lpsolve/amd64
  • Implicit dependency: r-base r-cran-lpsolve/arm64
  • Implicit dependency: r-base r-cran-lpsolve/armel
  • Implicit dependency: r-base r-cran-lpsolve/armhf
  • Implicit dependency: r-base r-cran-lpsolve/i386
  • Implicit dependency: r-base r-cran-lpsolve/mips64el
  • Implicit dependency: r-base r-cran-lpsolve/mipsel
  • Implicit dependency: r-base r-cran-lpsolve/ppc64el
  • Implicit dependency: r-base r-cran-lpsolve/s390x
  • Implicit dependency: r-base r-cran-lsei/amd64
  • Implicit dependency: r-base r-cran-lsei/arm64
  • Implicit dependency: r-base r-cran-lsei/armel
  • Implicit dependency: r-base r-cran-lsei/armhf
  • Implicit dependency: r-base r-cran-lsei/i386
  • Implicit dependency: r-base r-cran-lsei/mips64el
  • Implicit dependency: r-base r-cran-lsei/mipsel
  • Implicit dependency: r-base r-cran-lsei/ppc64el
  • Implicit dependency: r-base r-cran-lsei/s390x
  • Implicit dependency: r-base r-cran-lsmeans
  • Implicit dependency: r-base r-cran-lubridate/amd64
  • Implicit dependency: r-base r-cran-lubridate/arm64
  • Implicit dependency: r-base r-cran-lubridate/armel
  • Implicit dependency: r-base r-cran-lubridate/armhf
  • Implicit dependency: r-base r-cran-lubridate/i386
  • Implicit dependency: r-base r-cran-lubridate/mips64el
  • Implicit dependency: r-base r-cran-lubridate/mipsel
  • Implicit dependency: r-base r-cran-lubridate/ppc64el
  • Implicit dependency: r-base r-cran-lubridate/s390x
  • Implicit dependency: r-base r-cran-luminescence/amd64
  • Implicit dependency: r-base r-cran-luminescence/arm64
  • Implicit dependency: r-base r-cran-luminescence/armel
  • Implicit dependency: r-base r-cran-luminescence/armhf
  • Implicit dependency: r-base r-cran-luminescence/i386
  • Implicit dependency: r-base r-cran-luminescence/mips64el
  • Implicit dependency: r-base r-cran-luminescence/mipsel
  • Implicit dependency: r-base r-cran-luminescence/ppc64el
  • Implicit dependency: r-base r-cran-luminescence/s390x
  • Implicit dependency: r-base r-cran-lwgeom
  • Implicit dependency: r-base r-cran-magic
  • Implicit dependency: r-base r-cran-magick/amd64
  • Implicit dependency: r-base r-cran-magick/arm64
  • Implicit dependency: r-base r-cran-magick/armel
  • Implicit dependency: r-base r-cran-magick/armhf
  • Implicit dependency: r-base r-cran-magick/i386
  • Implicit dependency: r-base r-cran-magick/mips64el
  • Implicit dependency: r-base r-cran-magick/mipsel
  • Implicit dependency: r-base r-cran-magick/ppc64el
  • Implicit dependency: r-base r-cran-magick/s390x
  • Implicit dependency: r-base r-cran-magrittr
  • Implicit dependency: r-base r-cran-maldiquant/amd64
  • Implicit dependency: r-base r-cran-maldiquant/arm64
  • Implicit dependency: r-base r-cran-maldiquant/armel
  • Implicit dependency: r-base r-cran-maldiquant/armhf
  • Implicit dependency: r-base r-cran-maldiquant/i386
  • Implicit dependency: r-base r-cran-maldiquant/mips64el
  • Implicit dependency: r-base r-cran-maldiquant/mipsel
  • Implicit dependency: r-base r-cran-maldiquant/ppc64el
  • Implicit dependency: r-base r-cran-maldiquant/s390x
  • Implicit dependency: r-base r-cran-maldiquantforeign
  • Implicit dependency: r-base r-cran-manipulatewidgets
  • Implicit dependency: r-base r-cran-mapdata/amd64
  • Implicit dependency: r-base r-cran-mapdata/arm64
  • Implicit dependency: r-base r-cran-mapdata/armel
  • Implicit dependency: r-base r-cran-mapdata/armhf
  • Implicit dependency: r-base r-cran-mapdata/i386
  • Implicit dependency: r-base r-cran-mapdata/mips64el
  • Implicit dependency: r-base r-cran-mapdata/mipsel
  • Implicit dependency: r-base r-cran-mapdata/ppc64el
  • Implicit dependency: r-base r-cran-mapdata/s390x
  • Implicit dependency: r-base r-cran-mapproj/amd64
  • Implicit dependency: r-base r-cran-mapproj/arm64
  • Implicit dependency: r-base r-cran-mapproj/armel
  • Implicit dependency: r-base r-cran-mapproj/armhf
  • Implicit dependency: r-base r-cran-mapproj/i386
  • Implicit dependency: r-base r-cran-mapproj/mips64el
  • Implicit dependency: r-base r-cran-mapproj/mipsel
  • Implicit dependency: r-base r-cran-mapproj/ppc64el
  • Implicit dependency: r-base r-cran-mapproj/s390x
  • Implicit dependency: r-base r-cran-maps/amd64
  • Implicit dependency: r-base r-cran-maps/arm64
  • Implicit dependency: r-base r-cran-maps/armel
  • Implicit dependency: r-base r-cran-maps/armhf
  • Implicit dependency: r-base r-cran-maps/i386
  • Implicit dependency: r-base r-cran-maps/mips64el
  • Implicit dependency: r-base r-cran-maps/mipsel
  • Implicit dependency: r-base r-cran-maps/ppc64el
  • Implicit dependency: r-base r-cran-maps/s390x
  • Implicit dependency: r-base r-cran-maptools
  • Implicit dependency: r-base r-cran-maptree
  • Implicit dependency: r-base r-cran-markdown/amd64
  • Implicit dependency: r-base r-cran-markdown/arm64
  • Implicit dependency: r-base r-cran-markdown/armel
  • Implicit dependency: r-base r-cran-markdown/armhf
  • Implicit dependency: r-base r-cran-markdown/i386
  • Implicit dependency: r-base r-cran-markdown/mips64el
  • Implicit dependency: r-base r-cran-markdown/mipsel
  • Implicit dependency: r-base r-cran-markdown/ppc64el
  • Implicit dependency: r-base r-cran-markdown/s390x
  • Implicit dependency: r-base r-cran-mass/amd64
  • Implicit dependency: r-base r-cran-mass/arm64
  • Implicit dependency: r-base r-cran-mass/armel
  • Implicit dependency: r-base r-cran-mass/armhf
  • Implicit dependency: r-base r-cran-mass/i386
  • Implicit dependency: r-base r-cran-mass/mips64el
  • Implicit dependency: r-base r-cran-mass/mipsel
  • Implicit dependency: r-base r-cran-mass/ppc64el
  • Implicit dependency: r-base r-cran-mass/s390x
  • Implicit dependency: r-base r-cran-matching/amd64
  • Implicit dependency: r-base r-cran-matching/arm64
  • Implicit dependency: r-base r-cran-matching/armel
  • Implicit dependency: r-base r-cran-matching/armhf
  • Implicit dependency: r-base r-cran-matching/i386
  • Implicit dependency: r-base r-cran-matching/mips64el
  • Implicit dependency: r-base r-cran-matching/mipsel
  • Implicit dependency: r-base r-cran-matching/ppc64el
  • Implicit dependency: r-base r-cran-matching/s390x
  • Implicit dependency: r-base r-cran-matchit
  • Implicit dependency: r-base r-cran-matlab
  • Implicit dependency: r-base r-cran-matrixcalc
  • Implicit dependency: r-base r-cran-matrixmodels
  • Implicit dependency: r-base r-cran-matrixstats/amd64
  • Implicit dependency: r-base r-cran-matrixstats/arm64
  • Implicit dependency: r-base r-cran-matrixstats/armel
  • Implicit dependency: r-base r-cran-matrixstats/armhf
  • Implicit dependency: r-base r-cran-matrixstats/i386
  • Implicit dependency: r-base r-cran-matrixstats/mips64el
  • Implicit dependency: r-base r-cran-matrixstats/mipsel
  • Implicit dependency: r-base r-cran-matrixstats/ppc64el
  • Implicit dependency: r-base r-cran-matrixstats/s390x
  • Implicit dependency: r-base r-cran-maxlik
  • Implicit dependency: r-base r-cran-maxstat/amd64
  • Implicit dependency: r-base r-cran-maxstat/arm64
  • Implicit dependency: r-base r-cran-maxstat/armel
  • Implicit dependency: r-base r-cran-maxstat/armhf
  • Implicit dependency: r-base r-cran-maxstat/i386
  • Implicit dependency: r-base r-cran-maxstat/mips64el
  • Implicit dependency: r-base r-cran-maxstat/mipsel
  • Implicit dependency: r-base r-cran-maxstat/ppc64el
  • Implicit dependency: r-base r-cran-maxstat/s390x
  • Implicit dependency: r-base r-cran-mclust/amd64
  • Implicit dependency: r-base r-cran-mclust/arm64
  • Implicit dependency: r-base r-cran-mclust/armel
  • Implicit dependency: r-base r-cran-mclust/armhf
  • Implicit dependency: r-base r-cran-mclust/i386
  • Implicit dependency: r-base r-cran-mclust/mips64el
  • Implicit dependency: r-base r-cran-mclust/mipsel
  • Implicit dependency: r-base r-cran-mclust/ppc64el
  • Implicit dependency: r-base r-cran-mclust/s390x
  • Implicit dependency: r-base r-cran-mcmc/amd64
  • Implicit dependency: r-base r-cran-mcmc/arm64
  • Implicit dependency: r-base r-cran-mcmc/armel
  • Implicit dependency: r-base r-cran-mcmc/armhf
  • Implicit dependency: r-base r-cran-mcmc/i386
  • Implicit dependency: r-base r-cran-mcmc/mips64el
  • Implicit dependency: r-base r-cran-mcmc/mipsel
  • Implicit dependency: r-base r-cran-mcmc/ppc64el
  • Implicit dependency: r-base r-cran-mcmc/s390x
  • Implicit dependency: r-base r-cran-mcmcpack/amd64
  • Implicit dependency: r-base r-cran-mcmcpack/arm64
  • Implicit dependency: r-base r-cran-mcmcpack/armel
  • Implicit dependency: r-base r-cran-mcmcpack/armhf
  • Implicit dependency: r-base r-cran-mcmcpack/i386
  • Implicit dependency: r-base r-cran-mcmcpack/mips64el
  • Implicit dependency: r-base r-cran-mcmcpack/mipsel
  • Implicit dependency: r-base r-cran-mcmcpack/ppc64el
  • Implicit dependency: r-base r-cran-mcmcpack/s390x
  • Implicit dependency: r-base r-cran-mda/amd64
  • Implicit dependency: r-base r-cran-mda/arm64
  • Implicit dependency: r-base r-cran-mda/armel
  • Implicit dependency: r-base r-cran-mda/armhf
  • Implicit dependency: r-base r-cran-mda/i386
  • Implicit dependency: r-base r-cran-mda/mips64el
  • Implicit dependency: r-base r-cran-mda/mipsel
  • Implicit dependency: r-base r-cran-mda/ppc64el
  • Implicit dependency: r-base r-cran-mda/s390x
  • Implicit dependency: r-base r-cran-medadherence/amd64
  • Implicit dependency: r-base r-cran-medadherence/arm64
  • Implicit dependency: r-base r-cran-medadherence/armel
  • Implicit dependency: r-base r-cran-medadherence/armhf
  • Implicit dependency: r-base r-cran-medadherence/i386
  • Implicit dependency: r-base r-cran-medadherence/mips64el
  • Implicit dependency: r-base r-cran-medadherence/mipsel
  • Implicit dependency: r-base r-cran-medadherence/ppc64el
  • Implicit dependency: r-base r-cran-medadherence/s390x
  • Implicit dependency: r-base r-cran-mediana
  • Implicit dependency: r-base r-cran-memoise
  • Implicit dependency: r-base r-cran-mertools
  • Implicit dependency: r-base r-cran-metafor
  • Implicit dependency: r-base r-cran-metamix/amd64
  • Implicit dependency: r-base r-cran-metamix/arm64
  • Implicit dependency: r-base r-cran-metamix/armel
  • Implicit dependency: r-base r-cran-metamix/armhf
  • Implicit dependency: r-base r-cran-metamix/i386
  • Implicit dependency: r-base r-cran-metamix/mips64el
  • Implicit dependency: r-base r-cran-metamix/mipsel
  • Implicit dependency: r-base r-cran-metamix/ppc64el
  • Implicit dependency: r-base r-cran-metamix/s390x
  • Implicit dependency: r-base r-cran-metap
  • Implicit dependency: r-base r-cran-metrics
  • Implicit dependency: r-base r-cran-mets/amd64
  • Implicit dependency: r-base r-cran-mets/arm64
  • Implicit dependency: r-base r-cran-mets/armel
  • Implicit dependency: r-base r-cran-mets/armhf
  • Implicit dependency: r-base r-cran-mets/i386
  • Implicit dependency: r-base r-cran-mets/mips64el
  • Implicit dependency: r-base r-cran-mets/mipsel
  • Implicit dependency: r-base r-cran-mets/ppc64el
  • Implicit dependency: r-base r-cran-mets/s390x
  • Implicit dependency: r-base r-cran-mfilter
  • Implicit dependency: r-base r-cran-mi
  • Implicit dependency: r-base r-cran-mice
  • Implicit dependency: r-base r-cran-mime/amd64
  • Implicit dependency: r-base r-cran-mime/arm64
  • Implicit dependency: r-base r-cran-mime/armel
  • Implicit dependency: r-base r-cran-mime/armhf
  • Implicit dependency: r-base r-cran-mime/i386
  • Implicit dependency: r-base r-cran-mime/mips64el
  • Implicit dependency: r-base r-cran-mime/mipsel
  • Implicit dependency: r-base r-cran-mime/ppc64el
  • Implicit dependency: r-base r-cran-mime/s390x
  • Implicit dependency: r-base r-cran-minerva/amd64
  • Implicit dependency: r-base r-cran-minerva/arm64
  • Implicit dependency: r-base r-cran-minerva/armel
  • Implicit dependency: r-base r-cran-minerva/armhf
  • Implicit dependency: r-base r-cran-minerva/i386
  • Implicit dependency: r-base r-cran-minerva/mips64el
  • Implicit dependency: r-base r-cran-minerva/mipsel
  • Implicit dependency: r-base r-cran-minerva/ppc64el
  • Implicit dependency: r-base r-cran-minerva/s390x
  • Implicit dependency: r-base r-cran-miniui
  • Implicit dependency: r-base r-cran-minpack.lm/amd64
  • Implicit dependency: r-base r-cran-minpack.lm/arm64
  • Implicit dependency: r-base r-cran-minpack.lm/armel
  • Implicit dependency: r-base r-cran-minpack.lm/armhf
  • Implicit dependency: r-base r-cran-minpack.lm/i386
  • Implicit dependency: r-base r-cran-minpack.lm/mips64el
  • Implicit dependency: r-base r-cran-minpack.lm/mipsel
  • Implicit dependency: r-base r-cran-minpack.lm/ppc64el
  • Implicit dependency: r-base r-cran-minpack.lm/s390x
  • Implicit dependency: r-base r-cran-minqa/amd64
  • Implicit dependency: r-base r-cran-minqa/arm64
  • Implicit dependency: r-base r-cran-minqa/armel
  • Implicit dependency: r-base r-cran-minqa/armhf
  • Implicit dependency: r-base r-cran-minqa/i386
  • Implicit dependency: r-base r-cran-minqa/mips64el
  • Implicit dependency: r-base r-cran-minqa/mipsel
  • Implicit dependency: r-base r-cran-minqa/ppc64el
  • Implicit dependency: r-base r-cran-minqa/s390x
  • Implicit dependency: r-base r-cran-misctools
  • Implicit dependency: r-base r-cran-mitml
  • Implicit dependency: r-base r-cran-mitools
  • Implicit dependency: r-base r-cran-mixtools/amd64
  • Implicit dependency: r-base r-cran-mixtools/arm64
  • Implicit dependency: r-base r-cran-mixtools/armel
  • Implicit dependency: r-base r-cran-mixtools/armhf
  • Implicit dependency: r-base r-cran-mixtools/i386
  • Implicit dependency: r-base r-cran-mixtools/mips64el
  • Implicit dependency: r-base r-cran-mixtools/mipsel
  • Implicit dependency: r-base r-cran-mixtools/ppc64el
  • Implicit dependency: r-base r-cran-mixtools/s390x
  • Implicit dependency: r-base r-cran-mlbench/amd64
  • Implicit dependency: r-base r-cran-mlbench/arm64
  • Implicit dependency: r-base r-cran-mlbench/armel
  • Implicit dependency: r-base r-cran-mlbench/armhf
  • Implicit dependency: r-base r-cran-mlbench/i386
  • Implicit dependency: r-base r-cran-mlbench/mips64el
  • Implicit dependency: r-base r-cran-mlbench/mipsel
  • Implicit dependency: r-base r-cran-mlbench/ppc64el
  • Implicit dependency: r-base r-cran-mlbench/s390x
  • Implicit dependency: r-base r-cran-mlmetrics
  • Implicit dependency: r-base r-cran-mlmrev
  • Implicit dependency: r-base r-cran-mlr/amd64
  • Implicit dependency: r-base r-cran-mlr/arm64
  • Implicit dependency: r-base r-cran-mlr/armel
  • Implicit dependency: r-base r-cran-mlr/armhf
  • Implicit dependency: r-base r-cran-mlr/i386
  • Implicit dependency: r-base r-cran-mlr/mips64el
  • Implicit dependency: r-base r-cran-mlr/mipsel
  • Implicit dependency: r-base r-cran-mlr/ppc64el
  • Implicit dependency: r-base r-cran-mlr/s390x
  • Implicit dependency: r-base r-cran-mnp/amd64
  • Implicit dependency: r-base r-cran-mnp/arm64
  • Implicit dependency: r-base r-cran-mnp/armel
  • Implicit dependency: r-base r-cran-mnp/armhf
  • Implicit dependency: r-base r-cran-mnp/i386
  • Implicit dependency: r-base r-cran-mnp/mips64el
  • Implicit dependency: r-base r-cran-mnp/mipsel
  • Implicit dependency: r-base r-cran-mnp/ppc64el
  • Implicit dependency: r-base r-cran-mnp/s390x
  • Implicit dependency: r-base r-cran-mockery
  • Implicit dependency: r-base r-cran-mockr
  • Implicit dependency: r-base r-cran-modeldata
  • Implicit dependency: r-base r-cran-modelmetrics/amd64
  • Implicit dependency: r-base r-cran-modelmetrics/arm64
  • Implicit dependency: r-base r-cran-modelmetrics/armel
  • Implicit dependency: r-base r-cran-modelmetrics/armhf
  • Implicit dependency: r-base r-cran-modelmetrics/i386
  • Implicit dependency: r-base r-cran-modelmetrics/mips64el
  • Implicit dependency: r-base r-cran-modelmetrics/mipsel
  • Implicit dependency: r-base r-cran-modelmetrics/ppc64el
  • Implicit dependency: r-base r-cran-modelmetrics/s390x
  • Implicit dependency: r-base r-cran-modelr
  • Implicit dependency: r-base r-cran-modeltools
  • Implicit dependency: r-base r-cran-msm/amd64
  • Implicit dependency: r-base r-cran-msm/arm64
  • Implicit dependency: r-base r-cran-msm/armel
  • Implicit dependency: r-base r-cran-msm/armhf
  • Implicit dependency: r-base r-cran-msm/i386
  • Implicit dependency: r-base r-cran-msm/mips64el
  • Implicit dependency: r-base r-cran-msm/mipsel
  • Implicit dependency: r-base r-cran-msm/ppc64el
  • Implicit dependency: r-base r-cran-msm/s390x
  • Implicit dependency: r-base r-cran-multcompview
  • Implicit dependency: r-base r-cran-multicool/amd64
  • Implicit dependency: r-base r-cran-multicool/arm64
  • Implicit dependency: r-base r-cran-multicool/armel
  • Implicit dependency: r-base r-cran-multicool/armhf
  • Implicit dependency: r-base r-cran-multicool/i386
  • Implicit dependency: r-base r-cran-multicool/mips64el
  • Implicit dependency: r-base r-cran-multicool/mipsel
  • Implicit dependency: r-base r-cran-multicool/ppc64el
  • Implicit dependency: r-base r-cran-multicool/s390x
  • Implicit dependency: r-base r-cran-multicore/amd64
  • Implicit dependency: r-base r-cran-multicore/arm64
  • Implicit dependency: r-base r-cran-multicore/armel
  • Implicit dependency: r-base r-cran-multicore/armhf
  • Implicit dependency: r-base r-cran-multicore/i386
  • Implicit dependency: r-base r-cran-multicore/mips64el
  • Implicit dependency: r-base r-cran-multicore/mipsel
  • Implicit dependency: r-base r-cran-multicore/ppc64el
  • Implicit dependency: r-base r-cran-multicore/s390x
  • Implicit dependency: r-base r-cran-multidimbio
  • Implicit dependency: r-base r-cran-multilevel
  • Implicit dependency: r-base r-cran-munsell
  • Implicit dependency: r-base r-cran-mutoss
  • Implicit dependency: r-base r-cran-mvnfast/amd64
  • Implicit dependency: r-base r-cran-mvnfast/arm64
  • Implicit dependency: r-base r-cran-mvnfast/armel
  • Implicit dependency: r-base r-cran-mvnfast/armhf
  • Implicit dependency: r-base r-cran-mvnfast/i386
  • Implicit dependency: r-base r-cran-mvnfast/mips64el
  • Implicit dependency: r-base r-cran-mvnfast/mipsel
  • Implicit dependency: r-base r-cran-mvnfast/ppc64el
  • Implicit dependency: r-base r-cran-mvnfast/s390x
  • Implicit dependency: r-base r-cran-mvnormtest/amd64
  • Implicit dependency: r-base r-cran-mvnormtest/arm64
  • Implicit dependency: r-base r-cran-mvnormtest/armel
  • Implicit dependency: r-base r-cran-mvnormtest/armhf
  • Implicit dependency: r-base r-cran-mvnormtest/i386
  • Implicit dependency: r-base r-cran-mvnormtest/mips64el
  • Implicit dependency: r-base r-cran-mvnormtest/mipsel
  • Implicit dependency: r-base r-cran-mvnormtest/ppc64el
  • Implicit dependency: r-base r-cran-mvnormtest/s390x
  • Implicit dependency: r-base r-cran-natserv
  • Implicit dependency: r-base r-cran-ncdf4/amd64
  • Implicit dependency: r-base r-cran-ncdf4/arm64
  • Implicit dependency: r-base r-cran-ncdf4/armel
  • Implicit dependency: r-base r-cran-ncdf4/armhf
  • Implicit dependency: r-base r-cran-ncdf4/i386
  • Implicit dependency: r-base r-cran-ncdf4/mips64el
  • Implicit dependency: r-base r-cran-ncdf4/mipsel
  • Implicit dependency: r-base r-cran-ncdf4/ppc64el
  • Implicit dependency: r-base r-cran-ncdf4/s390x
  • Implicit dependency: r-base r-cran-ncdfgeom
  • Implicit dependency: r-base r-cran-ncmeta
  • Implicit dependency: r-base r-cran-nfactors
  • Implicit dependency: r-base r-cran-nleqslv/amd64
  • Implicit dependency: r-base r-cran-nleqslv/arm64
  • Implicit dependency: r-base r-cran-nleqslv/armel
  • Implicit dependency: r-base r-cran-nleqslv/armhf
  • Implicit dependency: r-base r-cran-nleqslv/i386
  • Implicit dependency: r-base r-cran-nleqslv/mips64el
  • Implicit dependency: r-base r-cran-nleqslv/mipsel
  • Implicit dependency: r-base r-cran-nleqslv/ppc64el
  • Implicit dependency: r-base r-cran-nleqslv/s390x
  • Implicit dependency: r-base r-cran-nloptr/amd64
  • Implicit dependency: r-base r-cran-nloptr/arm64
  • Implicit dependency: r-base r-cran-nloptr/armel
  • Implicit dependency: r-base r-cran-nloptr/armhf
  • Implicit dependency: r-base r-cran-nloptr/i386
  • Implicit dependency: r-base r-cran-nloptr/mips64el
  • Implicit dependency: r-base r-cran-nloptr/mipsel
  • Implicit dependency: r-base r-cran-nloptr/ppc64el
  • Implicit dependency: r-base r-cran-nloptr/s390x
  • Implicit dependency: r-base r-cran-nlp
  • Implicit dependency: r-base r-cran-nmf/amd64
  • Implicit dependency: r-base r-cran-nmf/arm64
  • Implicit dependency: r-base r-cran-nmf/armel
  • Implicit dependency: r-base r-cran-nmf/armhf
  • Implicit dependency: r-base r-cran-nmf/i386
  • Implicit dependency: r-base r-cran-nmf/mips64el
  • Implicit dependency: r-base r-cran-nmf/mipsel
  • Implicit dependency: r-base r-cran-nmf/ppc64el
  • Implicit dependency: r-base r-cran-nmf/s390x
  • Implicit dependency: r-base r-cran-nnet/amd64
  • Implicit dependency: r-base r-cran-nnet/arm64
  • Implicit dependency: r-base r-cran-nnet/armel
  • Implicit dependency: r-base r-cran-nnet/armhf
  • Implicit dependency: r-base r-cran-nnet/i386
  • Implicit dependency: r-base r-cran-nnet/mips64el
  • Implicit dependency: r-base r-cran-nnet/mipsel
  • Implicit dependency: r-base r-cran-nnet/ppc64el
  • Implicit dependency: r-base r-cran-nnet/s390x
  • Implicit dependency: r-base r-cran-nnls/amd64
  • Implicit dependency: r-base r-cran-nnls/arm64
  • Implicit dependency: r-base r-cran-nnls/armel
  • Implicit dependency: r-base r-cran-nnls/armhf
  • Implicit dependency: r-base r-cran-nnls/i386
  • Implicit dependency: r-base r-cran-nnls/mips64el
  • Implicit dependency: r-base r-cran-nnls/mipsel
  • Implicit dependency: r-base r-cran-nnls/ppc64el
  • Implicit dependency: r-base r-cran-nnls/s390x
  • Implicit dependency: r-base r-cran-nortest
  • Implicit dependency: r-base r-cran-nozzle.r1
  • Implicit dependency: r-base r-cran-npsurv
  • Implicit dependency: r-base r-cran-numderiv
  • Implicit dependency: r-base r-cran-openmx/amd64
  • Implicit dependency: r-base r-cran-openmx/arm64
  • Implicit dependency: r-base r-cran-openmx/armhf
  • Implicit dependency: r-base r-cran-openmx/i386
  • Implicit dependency: r-base r-cran-openmx/ppc64el
  • Implicit dependency: r-base r-cran-openmx/s390x
  • Implicit dependency: r-base r-cran-openssl/amd64
  • Implicit dependency: r-base r-cran-openssl/arm64
  • Implicit dependency: r-base r-cran-openssl/armel
  • Implicit dependency: r-base r-cran-openssl/armhf
  • Implicit dependency: r-base r-cran-openssl/i386
  • Implicit dependency: r-base r-cran-openssl/mips64el
  • Implicit dependency: r-base r-cran-openssl/mipsel
  • Implicit dependency: r-base r-cran-openssl/ppc64el
  • Implicit dependency: r-base r-cran-openssl/s390x
  • Implicit dependency: r-base r-cran-openxlsx/amd64
  • Implicit dependency: r-base r-cran-openxlsx/arm64
  • Implicit dependency: r-base r-cran-openxlsx/armel
  • Implicit dependency: r-base r-cran-openxlsx/armhf
  • Implicit dependency: r-base r-cran-openxlsx/i386
  • Implicit dependency: r-base r-cran-openxlsx/mips64el
  • Implicit dependency: r-base r-cran-openxlsx/mipsel
  • Implicit dependency: r-base r-cran-openxlsx/ppc64el
  • Implicit dependency: r-base r-cran-openxlsx/s390x
  • Implicit dependency: r-base r-cran-optparse
  • Implicit dependency: r-base r-cran-ordinal/amd64
  • Implicit dependency: r-base r-cran-ordinal/arm64
  • Implicit dependency: r-base r-cran-ordinal/armel
  • Implicit dependency: r-base r-cran-ordinal/armhf
  • Implicit dependency: r-base r-cran-ordinal/i386
  • Implicit dependency: r-base r-cran-ordinal/mips64el
  • Implicit dependency: r-base r-cran-ordinal/mipsel
  • Implicit dependency: r-base r-cran-ordinal/ppc64el
  • Implicit dependency: r-base r-cran-ordinal/s390x
  • Implicit dependency: r-base r-cran-packrat
  • Implicit dependency: r-base r-cran-pan/amd64
  • Implicit dependency: r-base r-cran-pan/arm64
  • Implicit dependency: r-base r-cran-pan/armel
  • Implicit dependency: r-base r-cran-pan/armhf
  • Implicit dependency: r-base r-cran-pan/i386
  • Implicit dependency: r-base r-cran-pan/mips64el
  • Implicit dependency: r-base r-cran-pan/mipsel
  • Implicit dependency: r-base r-cran-pan/ppc64el
  • Implicit dependency: r-base r-cran-pan/s390x
  • Implicit dependency: r-base r-cran-parallelmap
  • Implicit dependency: r-base r-cran-parameters
  • Implicit dependency: r-base r-cran-paramhelpers/amd64
  • Implicit dependency: r-base r-cran-paramhelpers/arm64
  • Implicit dependency: r-base r-cran-paramhelpers/armel
  • Implicit dependency: r-base r-cran-paramhelpers/armhf
  • Implicit dependency: r-base r-cran-paramhelpers/i386
  • Implicit dependency: r-base r-cran-paramhelpers/mips64el
  • Implicit dependency: r-base r-cran-paramhelpers/mipsel
  • Implicit dependency: r-base r-cran-paramhelpers/ppc64el
  • Implicit dependency: r-base r-cran-paramhelpers/s390x
  • Implicit dependency: r-base r-cran-parmigene/amd64
  • Implicit dependency: r-base r-cran-parmigene/arm64
  • Implicit dependency: r-base r-cran-parmigene/armel
  • Implicit dependency: r-base r-cran-parmigene/armhf
  • Implicit dependency: r-base r-cran-parmigene/i386
  • Implicit dependency: r-base r-cran-parmigene/mips64el
  • Implicit dependency: r-base r-cran-parmigene/mipsel
  • Implicit dependency: r-base r-cran-parmigene/ppc64el
  • Implicit dependency: r-base r-cran-parmigene/s390x
  • Implicit dependency: r-base r-cran-parsetools
  • Implicit dependency: r-base r-cran-party/amd64
  • Implicit dependency: r-base r-cran-party/arm64
  • Implicit dependency: r-base r-cran-party/armel
  • Implicit dependency: r-base r-cran-party/armhf
  • Implicit dependency: r-base r-cran-party/i386
  • Implicit dependency: r-base r-cran-party/mips64el
  • Implicit dependency: r-base r-cran-party/mipsel
  • Implicit dependency: r-base r-cran-party/ppc64el
  • Implicit dependency: r-base r-cran-party/s390x
  • Implicit dependency: r-base r-cran-partykit/amd64
  • Implicit dependency: r-base r-cran-partykit/arm64
  • Implicit dependency: r-base r-cran-partykit/armel
  • Implicit dependency: r-base r-cran-partykit/armhf
  • Implicit dependency: r-base r-cran-partykit/i386
  • Implicit dependency: r-base r-cran-partykit/mips64el
  • Implicit dependency: r-base r-cran-partykit/mipsel
  • Implicit dependency: r-base r-cran-partykit/ppc64el
  • Implicit dependency: r-base r-cran-partykit/s390x
  • Implicit dependency: r-base r-cran-patchwork
  • Implicit dependency: r-base r-cran-pbapply
  • Implicit dependency: r-base r-cran-pbdzmq/amd64
  • Implicit dependency: r-base r-cran-pbdzmq/arm64
  • Implicit dependency: r-base r-cran-pbdzmq/armel
  • Implicit dependency: r-base r-cran-pbdzmq/armhf
  • Implicit dependency: r-base r-cran-pbdzmq/i386
  • Implicit dependency: r-base r-cran-pbdzmq/mips64el
  • Implicit dependency: r-base r-cran-pbdzmq/mipsel
  • Implicit dependency: r-base r-cran-pbdzmq/ppc64el
  • Implicit dependency: r-base r-cran-pbdzmq/s390x
  • Implicit dependency: r-base r-cran-pbivnorm/amd64
  • Implicit dependency: r-base r-cran-pbivnorm/arm64
  • Implicit dependency: r-base r-cran-pbivnorm/armel
  • Implicit dependency: r-base r-cran-pbivnorm/armhf
  • Implicit dependency: r-base r-cran-pbivnorm/i386
  • Implicit dependency: r-base r-cran-pbivnorm/mips64el
  • Implicit dependency: r-base r-cran-pbivnorm/mipsel
  • Implicit dependency: r-base r-cran-pbivnorm/ppc64el
  • Implicit dependency: r-base r-cran-pbivnorm/s390x
  • Implicit dependency: r-base r-cran-pbkrtest
  • Implicit dependency: r-base r-cran-pbmcapply/amd64
  • Implicit dependency: r-base r-cran-pbmcapply/arm64
  • Implicit dependency: r-base r-cran-pbmcapply/armel
  • Implicit dependency: r-base r-cran-pbmcapply/armhf
  • Implicit dependency: r-base r-cran-pbmcapply/i386
  • Implicit dependency: r-base r-cran-pbmcapply/mips64el
  • Implicit dependency: r-base r-cran-pbmcapply/mipsel
  • Implicit dependency: r-base r-cran-pbmcapply/ppc64el
  • Implicit dependency: r-base r-cran-pbmcapply/s390x
  • Implicit dependency: r-base r-cran-pcapp/amd64
  • Implicit dependency: r-base r-cran-pcapp/arm64
  • Implicit dependency: r-base r-cran-pcapp/armel
  • Implicit dependency: r-base r-cran-pcapp/armhf
  • Implicit dependency: r-base r-cran-pcapp/i386
  • Implicit dependency: r-base r-cran-pcapp/mips64el
  • Implicit dependency: r-base r-cran-pcapp/mipsel
  • Implicit dependency: r-base r-cran-pcapp/ppc64el
  • Implicit dependency: r-base r-cran-pcapp/s390x
  • Implicit dependency: r-base r-cran-pcict/amd64
  • Implicit dependency: r-base r-cran-pcict/arm64
  • Implicit dependency: r-base r-cran-pcict/armel
  • Implicit dependency: r-base r-cran-pcict/armhf
  • Implicit dependency: r-base r-cran-pcict/i386
  • Implicit dependency: r-base r-cran-pcict/mips64el
  • Implicit dependency: r-base r-cran-pcict/mipsel
  • Implicit dependency: r-base r-cran-pcict/ppc64el
  • Implicit dependency: r-base r-cran-pcict/s390x
  • Implicit dependency: r-base r-cran-pdftools/amd64
  • Implicit dependency: r-base r-cran-pdftools/arm64
  • Implicit dependency: r-base r-cran-pdftools/armel
  • Implicit dependency: r-base r-cran-pdftools/armhf
  • Implicit dependency: r-base r-cran-pdftools/i386
  • Implicit dependency: r-base r-cran-pdftools/mips64el
  • Implicit dependency: r-base r-cran-pdftools/mipsel
  • Implicit dependency: r-base r-cran-pdftools/ppc64el
  • Implicit dependency: r-base r-cran-pdftools/s390x
  • Implicit dependency: r-base r-cran-performance
  • Implicit dependency: r-base r-cran-permute
  • Implicit dependency: r-base r-cran-phangorn/amd64
  • Implicit dependency: r-base r-cran-phangorn/arm64
  • Implicit dependency: r-base r-cran-phangorn/armel
  • Implicit dependency: r-base r-cran-phangorn/armhf
  • Implicit dependency: r-base r-cran-phangorn/i386
  • Implicit dependency: r-base r-cran-phangorn/mips64el
  • Implicit dependency: r-base r-cran-phangorn/mipsel
  • Implicit dependency: r-base r-cran-phangorn/ppc64el
  • Implicit dependency: r-base r-cran-phangorn/s390x
  • Implicit dependency: r-base r-cran-pheatmap
  • Implicit dependency: r-base r-cran-phylobase/amd64
  • Implicit dependency: r-base r-cran-phylobase/arm64
  • Implicit dependency: r-base r-cran-phylobase/armel
  • Implicit dependency: r-base r-cran-phylobase/armhf
  • Implicit dependency: r-base r-cran-phylobase/i386
  • Implicit dependency: r-base r-cran-phylobase/mips64el
  • Implicit dependency: r-base r-cran-phylobase/mipsel
  • Implicit dependency: r-base r-cran-phylobase/ppc64el
  • Implicit dependency: r-base r-cran-phylobase/s390x
  • Implicit dependency: r-base r-cran-phytools
  • Implicit dependency: r-base r-cran-pillar
  • Implicit dependency: r-base r-cran-pixmap/amd64
  • Implicit dependency: r-base r-cran-pixmap/arm64
  • Implicit dependency: r-base r-cran-pixmap/armel
  • Implicit dependency: r-base r-cran-pixmap/armhf
  • Implicit dependency: r-base r-cran-pixmap/i386
  • Implicit dependency: r-base r-cran-pixmap/mips64el
  • Implicit dependency: r-base r-cran-pixmap/mipsel
  • Implicit dependency: r-base r-cran-pixmap/ppc64el
  • Implicit dependency: r-base r-cran-pixmap/s390x
  • Implicit dependency: r-base r-cran-pkgbuild
  • Implicit dependency: r-base r-cran-pkgcond
  • Implicit dependency: r-base r-cran-pkgconfig
  • Implicit dependency: r-base r-cran-pkgkitten
  • Implicit dependency: r-base r-cran-pkgload
  • Implicit dependency: r-base r-cran-pkgmaker
  • Implicit dependency: r-base r-cran-pki/amd64
  • Implicit dependency: r-base r-cran-pki/arm64
  • Implicit dependency: r-base r-cran-pki/armel
  • Implicit dependency: r-base r-cran-pki/armhf
  • Implicit dependency: r-base r-cran-pki/i386
  • Implicit dependency: r-base r-cran-pki/mips64el
  • Implicit dependency: r-base r-cran-pki/mipsel
  • Implicit dependency: r-base r-cran-pki/ppc64el
  • Implicit dependency: r-base r-cran-pki/s390x
  • Implicit dependency: r-base r-cran-plm
  • Implicit dependency: r-base r-cran-plogr
  • Implicit dependency: r-base r-cran-plotly
  • Implicit dependency: r-base r-cran-plotmo
  • Implicit dependency: r-base r-cran-plotrix
  • Implicit dependency: r-base r-cran-pls
  • Implicit dependency: r-base r-cran-plumber
  • Implicit dependency: r-base r-cran-plyr
  • Implicit dependency: r-base r-cran-png/amd64
  • Implicit dependency: r-base r-cran-png/arm64
  • Implicit dependency: r-base r-cran-png/armel
  • Implicit dependency: r-base r-cran-png/armhf
  • Implicit dependency: r-base r-cran-png/i386
  • Implicit dependency: r-base r-cran-png/mips64el
  • Implicit dependency: r-base r-cran-png/mipsel
  • Implicit dependency: r-base r-cran-png/ppc64el
  • Implicit dependency: r-base r-cran-png/s390x
  • Implicit dependency: r-base r-cran-polyclip/amd64
  • Implicit dependency: r-base r-cran-polyclip/arm64
  • Implicit dependency: r-base r-cran-polyclip/armel
  • Implicit dependency: r-base r-cran-polyclip/armhf
  • Implicit dependency: r-base r-cran-polyclip/i386
  • Implicit dependency: r-base r-cran-polyclip/mips64el
  • Implicit dependency: r-base r-cran-polyclip/mipsel
  • Implicit dependency: r-base r-cran-polyclip/ppc64el
  • Implicit dependency: r-base r-cran-polyclip/s390x
  • Implicit dependency: r-base r-cran-polycor
  • Implicit dependency: r-base r-cran-polycub/amd64
  • Implicit dependency: r-base r-cran-polycub/arm64
  • Implicit dependency: r-base r-cran-polycub/armel
  • Implicit dependency: r-base r-cran-polycub/armhf
  • Implicit dependency: r-base r-cran-polycub/i386
  • Implicit dependency: r-base r-cran-polycub/mips64el
  • Implicit dependency: r-base r-cran-polycub/mipsel
  • Implicit dependency: r-base r-cran-polycub/ppc64el
  • Implicit dependency: r-base r-cran-polycub/s390x
  • Implicit dependency: r-base r-cran-polynom
  • Implicit dependency: r-base r-cran-popepi
  • Implicit dependency: r-base r-cran-postlogic
  • Implicit dependency: r-base r-cran-powerlaw
  • Implicit dependency: r-base r-cran-prabclus
  • Implicit dependency: r-base r-cran-pracma
  • Implicit dependency: r-base r-cran-praise
  • Implicit dependency: r-base r-cran-prediction
  • Implicit dependency: r-base r-cran-prettycode
  • Implicit dependency: r-base r-cran-prettyr
  • Implicit dependency: r-base r-cran-prettyunits
  • Implicit dependency: r-base r-cran-princurve/amd64
  • Implicit dependency: r-base r-cran-princurve/arm64
  • Implicit dependency: r-base r-cran-princurve/armel
  • Implicit dependency: r-base r-cran-princurve/armhf
  • Implicit dependency: r-base r-cran-princurve/i386
  • Implicit dependency: r-base r-cran-princurve/mips64el
  • Implicit dependency: r-base r-cran-princurve/mipsel
  • Implicit dependency: r-base r-cran-princurve/ppc64el
  • Implicit dependency: r-base r-cran-princurve/s390x
  • Implicit dependency: r-base r-cran-proc/amd64
  • Implicit dependency: r-base r-cran-proc/arm64
  • Implicit dependency: r-base r-cran-proc/armel
  • Implicit dependency: r-base r-cran-proc/armhf
  • Implicit dependency: r-base r-cran-proc/i386
  • Implicit dependency: r-base r-cran-proc/mips64el
  • Implicit dependency: r-base r-cran-proc/mipsel
  • Implicit dependency: r-base r-cran-proc/ppc64el
  • Implicit dependency: r-base r-cran-proc/s390x
  • Implicit dependency: r-base r-cran-processx/amd64
  • Implicit dependency: r-base r-cran-processx/arm64
  • Implicit dependency: r-base r-cran-processx/armel
  • Implicit dependency: r-base r-cran-processx/armhf
  • Implicit dependency: r-base r-cran-processx/i386
  • Implicit dependency: r-base r-cran-processx/mips64el
  • Implicit dependency: r-base r-cran-processx/mipsel
  • Implicit dependency: r-base r-cran-processx/ppc64el
  • Implicit dependency: r-base r-cran-processx/s390x
  • Implicit dependency: r-base r-cran-prodlim/amd64
  • Implicit dependency: r-base r-cran-prodlim/arm64
  • Implicit dependency: r-base r-cran-prodlim/armel
  • Implicit dependency: r-base r-cran-prodlim/armhf
  • Implicit dependency: r-base r-cran-prodlim/i386
  • Implicit dependency: r-base r-cran-prodlim/mips64el
  • Implicit dependency: r-base r-cran-prodlim/mipsel
  • Implicit dependency: r-base r-cran-prodlim/ppc64el
  • Implicit dependency: r-base r-cran-prodlim/s390x
  • Implicit dependency: r-base r-cran-profilemodel
  • Implicit dependency: r-base r-cran-progress
  • Implicit dependency: r-base r-cran-projpred/amd64
  • Implicit dependency: r-base r-cran-projpred/arm64
  • Implicit dependency: r-base r-cran-projpred/armel
  • Implicit dependency: r-base r-cran-projpred/armhf
  • Implicit dependency: r-base r-cran-projpred/i386
  • Implicit dependency: r-base r-cran-projpred/mips64el
  • Implicit dependency: r-base r-cran-projpred/mipsel
  • Implicit dependency: r-base r-cran-projpred/ppc64el
  • Implicit dependency: r-base r-cran-projpred/s390x
  • Implicit dependency: r-base r-cran-promises/amd64
  • Implicit dependency: r-base r-cran-promises/arm64
  • Implicit dependency: r-base r-cran-promises/armel
  • Implicit dependency: r-base r-cran-promises/armhf
  • Implicit dependency: r-base r-cran-promises/i386
  • Implicit dependency: r-base r-cran-promises/mips64el
  • Implicit dependency: r-base r-cran-promises/mipsel
  • Implicit dependency: r-base r-cran-promises/ppc64el
  • Implicit dependency: r-base r-cran-promises/s390x
  • Implicit dependency: r-base r-cran-propclust/amd64
  • Implicit dependency: r-base r-cran-propclust/arm64
  • Implicit dependency: r-base r-cran-propclust/armel
  • Implicit dependency: r-base r-cran-propclust/armhf
  • Implicit dependency: r-base r-cran-propclust/i386
  • Implicit dependency: r-base r-cran-propclust/mips64el
  • Implicit dependency: r-base r-cran-propclust/mipsel
  • Implicit dependency: r-base r-cran-propclust/ppc64el
  • Implicit dependency: r-base r-cran-propclust/s390x
  • Implicit dependency: r-base r-cran-proto
  • Implicit dependency: r-base r-cran-ps/amd64
  • Implicit dependency: r-base r-cran-ps/arm64
  • Implicit dependency: r-base r-cran-ps/armel
  • Implicit dependency: r-base r-cran-ps/armhf
  • Implicit dependency: r-base r-cran-ps/i386
  • Implicit dependency: r-base r-cran-ps/mips64el
  • Implicit dependency: r-base r-cran-ps/mipsel
  • Implicit dependency: r-base r-cran-ps/ppc64el
  • Implicit dependency: r-base r-cran-ps/s390x
  • Implicit dependency: r-base r-cran-pscbs
  • Implicit dependency: r-base r-cran-pscl/amd64
  • Implicit dependency: r-base r-cran-pscl/arm64
  • Implicit dependency: r-base r-cran-pscl/armel
  • Implicit dependency: r-base r-cran-pscl/armhf
  • Implicit dependency: r-base r-cran-pscl/i386
  • Implicit dependency: r-base r-cran-pscl/mips64el
  • Implicit dependency: r-base r-cran-pscl/mipsel
  • Implicit dependency: r-base r-cran-pscl/ppc64el
  • Implicit dependency: r-base r-cran-pscl/s390x
  • Implicit dependency: r-base r-cran-psy
  • Implicit dependency: r-base r-cran-psych
  • Implicit dependency: r-base r-cran-psychometric/amd64
  • Implicit dependency: r-base r-cran-psychometric/arm64
  • Implicit dependency: r-base r-cran-psychometric/armel
  • Implicit dependency: r-base r-cran-psychometric/armhf
  • Implicit dependency: r-base r-cran-psychometric/i386
  • Implicit dependency: r-base r-cran-psychometric/mips64el
  • Implicit dependency: r-base r-cran-psychometric/mipsel
  • Implicit dependency: r-base r-cran-psychometric/ppc64el
  • Implicit dependency: r-base r-cran-psychometric/s390x
  • Implicit dependency: r-base r-cran-psychotools/amd64
  • Implicit dependency: r-base r-cran-psychotools/arm64
  • Implicit dependency: r-base r-cran-psychotools/armel
  • Implicit dependency: r-base r-cran-psychotools/armhf
  • Implicit dependency: r-base r-cran-psychotools/i386
  • Implicit dependency: r-base r-cran-psychotools/mips64el
  • Implicit dependency: r-base r-cran-psychotools/mipsel
  • Implicit dependency: r-base r-cran-psychotools/ppc64el
  • Implicit dependency: r-base r-cran-psychotools/s390x
  • Implicit dependency: r-base r-cran-psychotree
  • Implicit dependency: r-base r-cran-psychtools
  • Implicit dependency: r-base r-cran-psyphy
  • Implicit dependency: r-base r-cran-purrr/amd64
  • Implicit dependency: r-base r-cran-purrr/arm64
  • Implicit dependency: r-base r-cran-purrr/armel
  • Implicit dependency: r-base r-cran-purrr/armhf
  • Implicit dependency: r-base r-cran-purrr/i386
  • Implicit dependency: r-base r-cran-purrr/mips64el
  • Implicit dependency: r-base r-cran-purrr/mipsel
  • Implicit dependency: r-base r-cran-purrr/ppc64el
  • Implicit dependency: r-base r-cran-purrr/s390x
  • Implicit dependency: r-base r-cran-purrrlyr/amd64
  • Implicit dependency: r-base r-cran-purrrlyr/arm64
  • Implicit dependency: r-base r-cran-purrrlyr/armel
  • Implicit dependency: r-base r-cran-purrrlyr/armhf
  • Implicit dependency: r-base r-cran-purrrlyr/i386
  • Implicit dependency: r-base r-cran-purrrlyr/mips64el
  • Implicit dependency: r-base r-cran-purrrlyr/mipsel
  • Implicit dependency: r-base r-cran-purrrlyr/ppc64el
  • Implicit dependency: r-base r-cran-purrrlyr/s390x
  • Implicit dependency: r-base r-cran-purrrogress
  • Implicit dependency: r-base r-cran-pvclust
  • Implicit dependency: r-base r-cran-pwr
  • Implicit dependency: r-base r-cran-pwt
  • Implicit dependency: r-base r-cran-pwt8
  • Implicit dependency: r-base r-cran-pwt9
  • Implicit dependency: r-base r-cran-qap/amd64
  • Implicit dependency: r-base r-cran-qap/arm64
  • Implicit dependency: r-base r-cran-qap/armel
  • Implicit dependency: r-base r-cran-qap/armhf
  • Implicit dependency: r-base r-cran-qap/i386
  • Implicit dependency: r-base r-cran-qap/mips64el
  • Implicit dependency: r-base r-cran-qap/mipsel
  • Implicit dependency: r-base r-cran-qap/ppc64el
  • Implicit dependency: r-base r-cran-qap/s390x
  • Implicit dependency: r-base r-cran-qgraph/amd64
  • Implicit dependency: r-base r-cran-qgraph/arm64
  • Implicit dependency: r-base r-cran-qgraph/armhf
  • Implicit dependency: r-base r-cran-qgraph/i386
  • Implicit dependency: r-base r-cran-qgraph/mips64el
  • Implicit dependency: r-base r-cran-qgraph/mipsel
  • Implicit dependency: r-base r-cran-qgraph/ppc64el
  • Implicit dependency: r-base r-cran-qgraph/s390x
  • Implicit dependency: r-base r-cran-qpdf/amd64
  • Implicit dependency: r-base r-cran-qpdf/arm64
  • Implicit dependency: r-base r-cran-qpdf/armel
  • Implicit dependency: r-base r-cran-qpdf/armhf
  • Implicit dependency: r-base r-cran-qpdf/i386
  • Implicit dependency: r-base r-cran-qpdf/mips64el
  • Implicit dependency: r-base r-cran-qpdf/mipsel
  • Implicit dependency: r-base r-cran-qpdf/ppc64el
  • Implicit dependency: r-base r-cran-qpdf/s390x
  • Implicit dependency: r-base r-cran-qqman
  • Implicit dependency: r-base r-cran-qtl/amd64
  • Implicit dependency: r-base r-cran-qtl/arm64
  • Implicit dependency: r-base r-cran-qtl/armel
  • Implicit dependency: r-base r-cran-qtl/armhf
  • Implicit dependency: r-base r-cran-qtl/i386
  • Implicit dependency: r-base r-cran-qtl/mips64el
  • Implicit dependency: r-base r-cran-qtl/mipsel
  • Implicit dependency: r-base r-cran-qtl/ppc64el
  • Implicit dependency: r-base r-cran-qtl/s390x
  • Implicit dependency: r-base r-cran-quantmod
  • Implicit dependency: r-base r-cran-quantreg/amd64
  • Implicit dependency: r-base r-cran-quantreg/arm64
  • Implicit dependency: r-base r-cran-quantreg/armel
  • Implicit dependency: r-base r-cran-quantreg/armhf
  • Implicit dependency: r-base r-cran-quantreg/i386
  • Implicit dependency: r-base r-cran-quantreg/mips64el
  • Implicit dependency: r-base r-cran-quantreg/mipsel
  • Implicit dependency: r-base r-cran-quantreg/ppc64el
  • Implicit dependency: r-base r-cran-quantreg/s390x
  • Implicit dependency: r-base r-cran-qvcalc
  • Implicit dependency: r-base r-cran-r.cache
  • Implicit dependency: r-base r-cran-r.methodss3
  • Implicit dependency: r-base r-cran-r.oo
  • Implicit dependency: r-base r-cran-r.utils
  • Implicit dependency: r-base r-cran-r2d2
  • Implicit dependency: r-base r-cran-r6
  • Implicit dependency: r-base r-cran-randomfields/amd64
  • Implicit dependency: r-base r-cran-randomfields/arm64
  • Implicit dependency: r-base r-cran-randomfields/armel
  • Implicit dependency: r-base r-cran-randomfields/armhf
  • Implicit dependency: r-base r-cran-randomfields/i386
  • Implicit dependency: r-base r-cran-randomfields/mips64el
  • Implicit dependency: r-base r-cran-randomfields/mipsel
  • Implicit dependency: r-base r-cran-randomfields/ppc64el
  • Implicit dependency: r-base r-cran-randomfields/s390x
  • Implicit dependency: r-base r-cran-randomfieldsutils/amd64
  • Implicit dependency: r-base r-cran-randomfieldsutils/arm64
  • Implicit dependency: r-base r-cran-randomfieldsutils/armel
  • Implicit dependency: r-base r-cran-randomfieldsutils/armhf
  • Implicit dependency: r-base r-cran-randomfieldsutils/i386
  • Implicit dependency: r-base r-cran-randomfieldsutils/mips64el
  • Implicit dependency: r-base r-cran-randomfieldsutils/mipsel
  • Implicit dependency: r-base r-cran-randomfieldsutils/ppc64el
  • Implicit dependency: r-base r-cran-randomfieldsutils/s390x
  • Implicit dependency: r-base r-cran-randomforest/amd64
  • Implicit dependency: r-base r-cran-randomforest/arm64
  • Implicit dependency: r-base r-cran-randomforest/armel
  • Implicit dependency: r-base r-cran-randomforest/armhf
  • Implicit dependency: r-base r-cran-randomforest/i386
  • Implicit dependency: r-base r-cran-randomforest/mips64el
  • Implicit dependency: r-base r-cran-randomforest/mipsel
  • Implicit dependency: r-base r-cran-randomforest/ppc64el
  • Implicit dependency: r-base r-cran-randomforest/s390x
  • Implicit dependency: r-base r-cran-randomglm/amd64
  • Implicit dependency: r-base r-cran-randomglm/arm64
  • Implicit dependency: r-base r-cran-randomglm/armel
  • Implicit dependency: r-base r-cran-randomglm/armhf
  • Implicit dependency: r-base r-cran-randomglm/i386
  • Implicit dependency: r-base r-cran-randomglm/mips64el
  • Implicit dependency: r-base r-cran-randomglm/mipsel
  • Implicit dependency: r-base r-cran-randomglm/ppc64el
  • Implicit dependency: r-base r-cran-randomglm/s390x
  • Implicit dependency: r-base r-cran-ranger/amd64
  • Implicit dependency: r-base r-cran-ranger/arm64
  • Implicit dependency: r-base r-cran-ranger/armel
  • Implicit dependency: r-base r-cran-ranger/armhf
  • Implicit dependency: r-base r-cran-ranger/i386
  • Implicit dependency: r-base r-cran-ranger/mips64el
  • Implicit dependency: r-base r-cran-ranger/mipsel
  • Implicit dependency: r-base r-cran-ranger/ppc64el
  • Implicit dependency: r-base r-cran-ranger/s390x
  • Implicit dependency: r-base r-cran-rann/amd64
  • Implicit dependency: r-base r-cran-rann/arm64
  • Implicit dependency: r-base r-cran-rann/armel
  • Implicit dependency: r-base r-cran-rann/armhf
  • Implicit dependency: r-base r-cran-rann/i386
  • Implicit dependency: r-base r-cran-rann/mips64el
  • Implicit dependency: r-base r-cran-rann/mipsel
  • Implicit dependency: r-base r-cran-rann/ppc64el
  • Implicit dependency: r-base r-cran-rann/s390x
  • Implicit dependency: r-base r-cran-rappdirs/amd64
  • Implicit dependency: r-base r-cran-rappdirs/arm64
  • Implicit dependency: r-base r-cran-rappdirs/armel
  • Implicit dependency: r-base r-cran-rappdirs/armhf
  • Implicit dependency: r-base r-cran-rappdirs/i386
  • Implicit dependency: r-base r-cran-rappdirs/mips64el
  • Implicit dependency: r-base r-cran-rappdirs/mipsel
  • Implicit dependency: r-base r-cran-rappdirs/ppc64el
  • Implicit dependency: r-base r-cran-rappdirs/s390x
  • Implicit dependency: r-base r-cran-raschsampler/amd64
  • Implicit dependency: r-base r-cran-raschsampler/arm64
  • Implicit dependency: r-base r-cran-raschsampler/armel
  • Implicit dependency: r-base r-cran-raschsampler/armhf
  • Implicit dependency: r-base r-cran-raschsampler/i386
  • Implicit dependency: r-base r-cran-raschsampler/mips64el
  • Implicit dependency: r-base r-cran-raschsampler/mipsel
  • Implicit dependency: r-base r-cran-raschsampler/ppc64el
  • Implicit dependency: r-base r-cran-raschsampler/s390x
  • Implicit dependency: r-base r-cran-raster
  • Implicit dependency: r-base r-cran-rcarb
  • Implicit dependency: r-base r-cran-rcdklibs
  • Implicit dependency: r-base r-cran-rcmdcheck
  • Implicit dependency: r-base r-cran-rcmdrmisc
  • Implicit dependency: r-base r-cran-rcppannoy/amd64
  • Implicit dependency: r-base r-cran-rcppannoy/arm64
  • Implicit dependency: r-base r-cran-rcppannoy/armel
  • Implicit dependency: r-base r-cran-rcppannoy/armhf
  • Implicit dependency: r-base r-cran-rcppannoy/i386
  • Implicit dependency: r-base r-cran-rcppannoy/mips64el
  • Implicit dependency: r-base r-cran-rcppannoy/mipsel
  • Implicit dependency: r-base r-cran-rcppannoy/ppc64el
  • Implicit dependency: r-base r-cran-rcppannoy/s390x
  • Implicit dependency: r-base r-cran-rcpparmadillo
  • Implicit dependency: r-base r-cran-rcppeigen/amd64
  • Implicit dependency: r-base r-cran-rcppeigen/arm64
  • Implicit dependency: r-base r-cran-rcppeigen/armel
  • Implicit dependency: r-base r-cran-rcppeigen/armhf
  • Implicit dependency: r-base r-cran-rcppeigen/i386
  • Implicit dependency: r-base r-cran-rcppeigen/mips64el
  • Implicit dependency: r-base r-cran-rcppeigen/mipsel
  • Implicit dependency: r-base r-cran-rcppeigen/ppc64el
  • Implicit dependency: r-base r-cran-rcppeigen/s390x
  • Implicit dependency: r-base r-cran-rcppgsl/amd64
  • Implicit dependency: r-base r-cran-rcppgsl/arm64
  • Implicit dependency: r-base r-cran-rcppgsl/armel
  • Implicit dependency: r-base r-cran-rcppgsl/armhf
  • Implicit dependency: r-base r-cran-rcppgsl/i386
  • Implicit dependency: r-base r-cran-rcppgsl/mips64el
  • Implicit dependency: r-base r-cran-rcppgsl/mipsel
  • Implicit dependency: r-base r-cran-rcppgsl/ppc64el
  • Implicit dependency: r-base r-cran-rcppgsl/s390x
  • Implicit dependency: r-base r-cran-rcppparallel/amd64
  • Implicit dependency: r-base r-cran-rcppparallel/arm64
  • Implicit dependency: r-base r-cran-rcppparallel/armel
  • Implicit dependency: r-base r-cran-rcppparallel/armhf
  • Implicit dependency: r-base r-cran-rcppparallel/i386
  • Implicit dependency: r-base r-cran-rcppparallel/mips64el
  • Implicit dependency: r-base r-cran-rcppparallel/mipsel
  • Implicit dependency: r-base r-cran-rcppparallel/ppc64el
  • Implicit dependency: r-base r-cran-rcppparallel/s390x
  • Implicit dependency: r-base r-cran-rcppprogress
  • Implicit dependency: r-base r-cran-rcpproll/amd64
  • Implicit dependency: r-base r-cran-rcpproll/arm64
  • Implicit dependency: r-base r-cran-rcpproll/armel
  • Implicit dependency: r-base r-cran-rcpproll/armhf
  • Implicit dependency: r-base r-cran-rcpproll/i386
  • Implicit dependency: r-base r-cran-rcpproll/mips64el
  • Implicit dependency: r-base r-cran-rcpproll/mipsel
  • Implicit dependency: r-base r-cran-rcpproll/ppc64el
  • Implicit dependency: r-base r-cran-rcpproll/s390x
  • Implicit dependency: r-base r-cran-rcurl/amd64
  • Implicit dependency: r-base r-cran-rcurl/arm64
  • Implicit dependency: r-base r-cran-rcurl/armel
  • Implicit dependency: r-base r-cran-rcurl/armhf
  • Implicit dependency: r-base r-cran-rcurl/i386
  • Implicit dependency: r-base r-cran-rcurl/mips64el
  • Implicit dependency: r-base r-cran-rcurl/mipsel
  • Implicit dependency: r-base r-cran-rcurl/ppc64el
  • Implicit dependency: r-base r-cran-rcurl/s390x
  • Implicit dependency: r-base r-cran-rdbnomics
  • Implicit dependency: r-base r-cran-rdflib
  • Implicit dependency: r-base r-cran-rdpack
  • Implicit dependency: r-base r-cran-readbrukerflexdata
  • Implicit dependency: r-base r-cran-readmzxmldata
  • Implicit dependency: r-base r-cran-readr/amd64
  • Implicit dependency: r-base r-cran-readr/arm64
  • Implicit dependency: r-base r-cran-readr/armel
  • Implicit dependency: r-base r-cran-readr/armhf
  • Implicit dependency: r-base r-cran-readr/i386
  • Implicit dependency: r-base r-cran-readr/mips64el
  • Implicit dependency: r-base r-cran-readr/mipsel
  • Implicit dependency: r-base r-cran-readr/ppc64el
  • Implicit dependency: r-base r-cran-readr/s390x
  • Implicit dependency: r-base r-cran-readstata13/amd64
  • Implicit dependency: r-base r-cran-readstata13/arm64
  • Implicit dependency: r-base r-cran-readstata13/armel
  • Implicit dependency: r-base r-cran-readstata13/armhf
  • Implicit dependency: r-base r-cran-readstata13/i386
  • Implicit dependency: r-base r-cran-readstata13/mips64el
  • Implicit dependency: r-base r-cran-readstata13/mipsel
  • Implicit dependency: r-base r-cran-readstata13/ppc64el
  • Implicit dependency: r-base r-cran-readstata13/s390x
  • Implicit dependency: r-base r-cran-readxl/amd64
  • Implicit dependency: r-base r-cran-readxl/arm64
  • Implicit dependency: r-base r-cran-readxl/armel
  • Implicit dependency: r-base r-cran-readxl/armhf
  • Implicit dependency: r-base r-cran-readxl/i386
  • Implicit dependency: r-base r-cran-readxl/mips64el
  • Implicit dependency: r-base r-cran-readxl/mipsel
  • Implicit dependency: r-base r-cran-readxl/ppc64el
  • Implicit dependency: r-base r-cran-readxl/s390x
  • Implicit dependency: r-base r-cran-recipes
  • Implicit dependency: r-base r-cran-redland/amd64
  • Implicit dependency: r-base r-cran-redland/arm64
  • Implicit dependency: r-base r-cran-redland/armhf
  • Implicit dependency: r-base r-cran-redland/i386
  • Implicit dependency: r-base r-cran-redland/mips64el
  • Implicit dependency: r-base r-cran-redland/mipsel
  • Implicit dependency: r-base r-cran-redland/ppc64el
  • Implicit dependency: r-base r-cran-redland/s390x
  • Implicit dependency: r-base r-cran-registry
  • Implicit dependency: r-base r-cran-regsem/amd64
  • Implicit dependency: r-base r-cran-regsem/arm64
  • Implicit dependency: r-base r-cran-regsem/armel
  • Implicit dependency: r-base r-cran-regsem/armhf
  • Implicit dependency: r-base r-cran-regsem/i386
  • Implicit dependency: r-base r-cran-regsem/mips64el
  • Implicit dependency: r-base r-cran-regsem/mipsel
  • Implicit dependency: r-base r-cran-regsem/ppc64el
  • Implicit dependency: r-base r-cran-regsem/s390x
  • Implicit dependency: r-base r-cran-relsurv/amd64
  • Implicit dependency: r-base r-cran-relsurv/arm64
  • Implicit dependency: r-base r-cran-relsurv/armel
  • Implicit dependency: r-base r-cran-relsurv/armhf
  • Implicit dependency: r-base r-cran-relsurv/i386
  • Implicit dependency: r-base r-cran-relsurv/mips64el
  • Implicit dependency: r-base r-cran-relsurv/mipsel
  • Implicit dependency: r-base r-cran-relsurv/ppc64el
  • Implicit dependency: r-base r-cran-relsurv/s390x
  • Implicit dependency: r-base r-cran-rematch
  • Implicit dependency: r-base r-cran-rematch2
  • Implicit dependency: r-base r-cran-remotes
  • Implicit dependency: r-base r-cran-rentrez
  • Implicit dependency: r-base r-cran-repr
  • Implicit dependency: r-base r-cran-reprex
  • Implicit dependency: r-base r-cran-reshape
  • Implicit dependency: r-base r-cran-reshape2
  • Implicit dependency: r-base r-cran-reticulate/amd64
  • Implicit dependency: r-base r-cran-reticulate/arm64
  • Implicit dependency: r-base r-cran-reticulate/armel
  • Implicit dependency: r-base r-cran-reticulate/armhf
  • Implicit dependency: r-base r-cran-reticulate/i386
  • Implicit dependency: r-base r-cran-reticulate/mips64el
  • Implicit dependency: r-base r-cran-reticulate/mipsel
  • Implicit dependency: r-base r-cran-reticulate/ppc64el
  • Implicit dependency: r-base r-cran-reticulate/s390x
  • Implicit dependency: r-base r-cran-rex
  • Implicit dependency: r-base r-cran-rgdal/amd64
  • Implicit dependency: r-base r-cran-rgdal/arm64
  • Implicit dependency: r-base r-cran-rgdal/armel
  • Implicit dependency: r-base r-cran-rgdal/armhf
  • Implicit dependency: r-base r-cran-rgdal/i386
  • Implicit dependency: r-base r-cran-rgdal/mips64el
  • Implicit dependency: r-base r-cran-rgdal/mipsel
  • Implicit dependency: r-base r-cran-rgdal/ppc64el
  • Implicit dependency: r-base r-cran-rgdal/s390x
  • Implicit dependency: r-base r-cran-rgenoud/amd64
  • Implicit dependency: r-base r-cran-rgenoud/arm64
  • Implicit dependency: r-base r-cran-rgenoud/armel
  • Implicit dependency: r-base r-cran-rgenoud/armhf
  • Implicit dependency: r-base r-cran-rgenoud/i386
  • Implicit dependency: r-base r-cran-rgenoud/mips64el
  • Implicit dependency: r-base r-cran-rgenoud/mipsel
  • Implicit dependency: r-base r-cran-rgenoud/ppc64el
  • Implicit dependency: r-base r-cran-rgenoud/s390x
  • Implicit dependency: r-base r-cran-rglwidget
  • Implicit dependency: r-base r-cran-rhandsontable
  • Implicit dependency: r-base r-cran-rinside/amd64
  • Implicit dependency: r-base r-cran-rinside/arm64
  • Implicit dependency: r-base r-cran-rinside/armel
  • Implicit dependency: r-base r-cran-rinside/armhf
  • Implicit dependency: r-base r-cran-rinside/i386
  • Implicit dependency: r-base r-cran-rinside/mips64el
  • Implicit dependency: r-base r-cran-rinside/mipsel
  • Implicit dependency: r-base r-cran-rinside/ppc64el
  • Implicit dependency: r-base r-cran-rinside/s390x
  • Implicit dependency: r-base r-cran-rio
  • Implicit dependency: r-base r-cran-ritis
  • Implicit dependency: r-base r-cran-rjags/amd64
  • Implicit dependency: r-base r-cran-rjags/arm64
  • Implicit dependency: r-base r-cran-rjags/armel
  • Implicit dependency: r-base r-cran-rjags/armhf
  • Implicit dependency: r-base r-cran-rjags/i386
  • Implicit dependency: r-base r-cran-rjags/mips64el
  • Implicit dependency: r-base r-cran-rjags/mipsel
  • Implicit dependency: r-base r-cran-rjags/ppc64el
  • Implicit dependency: r-base r-cran-rjags/s390x
  • Implicit dependency: r-base r-cran-rjson/amd64
  • Implicit dependency: r-base r-cran-rjson/arm64
  • Implicit dependency: r-base r-cran-rjson/armel
  • Implicit dependency: r-base r-cran-rjson/armhf
  • Implicit dependency: r-base r-cran-rjson/i386
  • Implicit dependency: r-base r-cran-rjson/mips64el
  • Implicit dependency: r-base r-cran-rjson/mipsel
  • Implicit dependency: r-base r-cran-rjson/ppc64el
  • Implicit dependency: r-base r-cran-rjson/s390x
  • Implicit dependency: r-base r-cran-rlang/amd64
  • Implicit dependency: r-base r-cran-rlang/arm64
  • Implicit dependency: r-base r-cran-rlang/armel
  • Implicit dependency: r-base r-cran-rlang/armhf
  • Implicit dependency: r-base r-cran-rlang/i386
  • Implicit dependency: r-base r-cran-rlang/mips64el
  • Implicit dependency: r-base r-cran-rlang/mipsel
  • Implicit dependency: r-base r-cran-rlang/ppc64el
  • Implicit dependency: r-base r-cran-rlang/s390x
  • Implicit dependency: r-base r-cran-rlist
  • Implicit dependency: r-base r-cran-rlrsim/amd64
  • Implicit dependency: r-base r-cran-rlrsim/arm64
  • Implicit dependency: r-base r-cran-rlrsim/armel
  • Implicit dependency: r-base r-cran-rlrsim/armhf
  • Implicit dependency: r-base r-cran-rlrsim/i386
  • Implicit dependency: r-base r-cran-rlrsim/mips64el
  • Implicit dependency: r-base r-cran-rlrsim/mipsel
  • Implicit dependency: r-base r-cran-rlrsim/ppc64el
  • Implicit dependency: r-base r-cran-rlrsim/s390x
  • Implicit dependency: r-base r-cran-rlumshiny
  • Implicit dependency: r-base r-cran-rmarkdown
  • Implicit dependency: r-base r-cran-rms/amd64
  • Implicit dependency: r-base r-cran-rms/arm64
  • Implicit dependency: r-base r-cran-rms/armhf
  • Implicit dependency: r-base r-cran-rms/i386
  • Implicit dependency: r-base r-cran-rms/mips64el
  • Implicit dependency: r-base r-cran-rms/mipsel
  • Implicit dependency: r-base r-cran-rms/ppc64el
  • Implicit dependency: r-base r-cran-rms/s390x
  • Implicit dependency: r-base r-cran-rncl/amd64
  • Implicit dependency: r-base r-cran-rncl/arm64
  • Implicit dependency: r-base r-cran-rncl/armel
  • Implicit dependency: r-base r-cran-rncl/armhf
  • Implicit dependency: r-base r-cran-rncl/i386
  • Implicit dependency: r-base r-cran-rncl/mips64el
  • Implicit dependency: r-base r-cran-rncl/mipsel
  • Implicit dependency: r-base r-cran-rncl/ppc64el
  • Implicit dependency: r-base r-cran-rncl/s390x
  • Implicit dependency: r-base r-cran-rneos
  • Implicit dependency: r-base r-cran-rnetcdf/amd64
  • Implicit dependency: r-base r-cran-rnetcdf/arm64
  • Implicit dependency: r-base r-cran-rnetcdf/armel
  • Implicit dependency: r-base r-cran-rnetcdf/armhf
  • Implicit dependency: r-base r-cran-rnetcdf/i386
  • Implicit dependency: r-base r-cran-rnetcdf/mips64el
  • Implicit dependency: r-base r-cran-rnetcdf/mipsel
  • Implicit dependency: r-base r-cran-rnetcdf/ppc64el
  • Implicit dependency: r-base r-cran-rnetcdf/s390x
  • Implicit dependency: r-base r-cran-rnexml
  • Implicit dependency: r-base r-cran-rngtools
  • Implicit dependency: r-base r-cran-rniftilib/amd64
  • Implicit dependency: r-base r-cran-rniftilib/arm64
  • Implicit dependency: r-base r-cran-rniftilib/armel
  • Implicit dependency: r-base r-cran-rniftilib/armhf
  • Implicit dependency: r-base r-cran-rniftilib/i386
  • Implicit dependency: r-base r-cran-rniftilib/mips64el
  • Implicit dependency: r-base r-cran-rniftilib/mipsel
  • Implicit dependency: r-base r-cran-rniftilib/ppc64el
  • Implicit dependency: r-base r-cran-rniftilib/s390x
  • Implicit dependency: r-base r-cran-robumeta
  • Implicit dependency: r-base r-cran-robust/amd64
  • Implicit dependency: r-base r-cran-robust/arm64
  • Implicit dependency: r-base r-cran-robust/armel
  • Implicit dependency: r-base r-cran-robust/armhf
  • Implicit dependency: r-base r-cran-robust/i386
  • Implicit dependency: r-base r-cran-robust/mips64el
  • Implicit dependency: r-base r-cran-robust/mipsel
  • Implicit dependency: r-base r-cran-robust/ppc64el
  • Implicit dependency: r-base r-cran-robust/s390x
  • Implicit dependency: r-base r-cran-robustrankaggreg
  • Implicit dependency: r-base r-cran-rockchalk
  • Implicit dependency: r-base r-cran-rocr
  • Implicit dependency: r-base r-cran-rook/amd64
  • Implicit dependency: r-base r-cran-rook/arm64
  • Implicit dependency: r-base r-cran-rook/armel
  • Implicit dependency: r-base r-cran-rook/armhf
  • Implicit dependency: r-base r-cran-rook/i386
  • Implicit dependency: r-base r-cran-rook/mips64el
  • Implicit dependency: r-base r-cran-rook/mipsel
  • Implicit dependency: r-base r-cran-rook/ppc64el
  • Implicit dependency: r-base r-cran-rook/s390x
  • Implicit dependency: r-base r-cran-rotl
  • Implicit dependency: r-base r-cran-roxygen2
  • Implicit dependency: r-base r-cran-rpact/amd64
  • Implicit dependency: r-base r-cran-rpact/arm64
  • Implicit dependency: r-base r-cran-rpact/armel
  • Implicit dependency: r-base r-cran-rpact/armhf
  • Implicit dependency: r-base r-cran-rpact/i386
  • Implicit dependency: r-base r-cran-rpact/mips64el
  • Implicit dependency: r-base r-cran-rpact/mipsel
  • Implicit dependency: r-base r-cran-rpact/ppc64el
  • Implicit dependency: r-base r-cran-rpact/s390x
  • Implicit dependency: r-base r-cran-rpf/amd64
  • Implicit dependency: r-base r-cran-rpf/arm64
  • Implicit dependency: r-base r-cran-rpf/armel
  • Implicit dependency: r-base r-cran-rpf/armhf
  • Implicit dependency: r-base r-cran-rpf/i386
  • Implicit dependency: r-base r-cran-rpf/ppc64el
  • Implicit dependency: r-base r-cran-rpf/s390x
  • Implicit dependency: r-base r-cran-rpostgresql/amd64
  • Implicit dependency: r-base r-cran-rpostgresql/arm64
  • Implicit dependency: r-base r-cran-rpostgresql/armel
  • Implicit dependency: r-base r-cran-rpostgresql/armhf
  • Implicit dependency: r-base r-cran-rpostgresql/i386
  • Implicit dependency: r-base r-cran-rpostgresql/mips64el
  • Implicit dependency: r-base r-cran-rpostgresql/mipsel
  • Implicit dependency: r-base r-cran-rpostgresql/ppc64el
  • Implicit dependency: r-base r-cran-rpostgresql/s390x
  • Implicit dependency: r-base r-cran-rprojroot
  • Implicit dependency: r-base r-cran-rprotobuf/amd64
  • Implicit dependency: r-base r-cran-rprotobuf/arm64
  • Implicit dependency: r-base r-cran-rprotobuf/armel
  • Implicit dependency: r-base r-cran-rprotobuf/armhf
  • Implicit dependency: r-base r-cran-rprotobuf/i386
  • Implicit dependency: r-base r-cran-rprotobuf/mips64el
  • Implicit dependency: r-base r-cran-rprotobuf/mipsel
  • Implicit dependency: r-base r-cran-rprotobuf/ppc64el
  • Implicit dependency: r-base r-cran-rprotobuf/s390x
  • Implicit dependency: r-base r-cran-rrcov/amd64
  • Implicit dependency: r-base r-cran-rrcov/arm64
  • Implicit dependency: r-base r-cran-rrcov/armel
  • Implicit dependency: r-base r-cran-rrcov/armhf
  • Implicit dependency: r-base r-cran-rrcov/i386
  • Implicit dependency: r-base r-cran-rrcov/mips64el
  • Implicit dependency: r-base r-cran-rrcov/mipsel
  • Implicit dependency: r-base r-cran-rrcov/ppc64el
  • Implicit dependency: r-base r-cran-rrcov/s390x
  • Implicit dependency: r-base r-cran-rredlist
  • Implicit dependency: r-base r-cran-rsample
  • Implicit dependency: r-base r-cran-rsclient/amd64
  • Implicit dependency: r-base r-cran-rsclient/arm64
  • Implicit dependency: r-base r-cran-rsclient/armel
  • Implicit dependency: r-base r-cran-rsclient/armhf
  • Implicit dependency: r-base r-cran-rsclient/i386
  • Implicit dependency: r-base r-cran-rsclient/mips64el
  • Implicit dependency: r-base r-cran-rsclient/mipsel
  • Implicit dependency: r-base r-cran-rsclient/ppc64el
  • Implicit dependency: r-base r-cran-rsclient/s390x
  • Implicit dependency: r-base r-cran-rsconnect
  • Implicit dependency: r-base r-cran-rsdmx
  • Implicit dependency: r-base r-cran-rsgcc/amd64
  • Implicit dependency: r-base r-cran-rsgcc/arm64
  • Implicit dependency: r-base r-cran-rsgcc/armel
  • Implicit dependency: r-base r-cran-rsgcc/armhf
  • Implicit dependency: r-base r-cran-rsgcc/i386
  • Implicit dependency: r-base r-cran-rsgcc/mips64el
  • Implicit dependency: r-base r-cran-rsgcc/mipsel
  • Implicit dependency: r-base r-cran-rsgcc/ppc64el
  • Implicit dependency: r-base r-cran-rsgcc/s390x
  • Implicit dependency: r-base r-cran-rslurm
  • Implicit dependency: r-base r-cran-rsolnp
  • Implicit dependency: r-base r-cran-rspectra/amd64
  • Implicit dependency: r-base r-cran-rspectra/arm64
  • Implicit dependency: r-base r-cran-rspectra/armel
  • Implicit dependency: r-base r-cran-rspectra/armhf
  • Implicit dependency: r-base r-cran-rspectra/i386
  • Implicit dependency: r-base r-cran-rspectra/mips64el
  • Implicit dependency: r-base r-cran-rspectra/mipsel
  • Implicit dependency: r-base r-cran-rspectra/ppc64el
  • Implicit dependency: r-base r-cran-rspectra/s390x
  • Implicit dependency: r-base r-cran-rsqlite/amd64
  • Implicit dependency: r-base r-cran-rsqlite/arm64
  • Implicit dependency: r-base r-cran-rsqlite/armel
  • Implicit dependency: r-base r-cran-rsqlite/armhf
  • Implicit dependency: r-base r-cran-rsqlite/i386
  • Implicit dependency: r-base r-cran-rsqlite/mips64el
  • Implicit dependency: r-base r-cran-rsqlite/mipsel
  • Implicit dependency: r-base r-cran-rsqlite/ppc64el
  • Implicit dependency: r-base r-cran-rsqlite/s390x
  • Implicit dependency: r-base r-cran-rstan/amd64
  • Implicit dependency: r-base r-cran-rstan/arm64
  • Implicit dependency: r-base r-cran-rstan/armel
  • Implicit dependency: r-base r-cran-rstan/armhf
  • Implicit dependency: r-base r-cran-rstan/i386
  • Implicit dependency: r-base r-cran-rstan/mips64el
  • Implicit dependency: r-base r-cran-rstan/ppc64el
  • Implicit dependency: r-base r-cran-rstan/s390x
  • Implicit dependency: r-base r-cran-rstanarm/amd64
  • Implicit dependency: r-base r-cran-rstanarm/arm64
  • Implicit dependency: r-base r-cran-rstanarm/armhf
  • Implicit dependency: r-base r-cran-rstanarm/i386
  • Implicit dependency: r-base r-cran-rstanarm/mips64el
  • Implicit dependency: r-base r-cran-rstanarm/ppc64el
  • Implicit dependency: r-base r-cran-rstanarm/s390x
  • Implicit dependency: r-base r-cran-rstantools
  • Implicit dependency: r-base r-cran-rstudioapi
  • Implicit dependency: r-base r-cran-rsvd
  • Implicit dependency: r-base r-cran-rsvg
  • Implicit dependency: r-base r-cran-rtsne/amd64
  • Implicit dependency: r-base r-cran-rtsne/arm64
  • Implicit dependency: r-base r-cran-rtsne/armel
  • Implicit dependency: r-base r-cran-rtsne/armhf
  • Implicit dependency: r-base r-cran-rtsne/i386
  • Implicit dependency: r-base r-cran-rtsne/mips64el
  • Implicit dependency: r-base r-cran-rtsne/mipsel
  • Implicit dependency: r-base r-cran-rtsne/ppc64el
  • Implicit dependency: r-base r-cran-rtsne/s390x
  • Implicit dependency: r-base r-cran-runit
  • Implicit dependency: r-base r-cran-rversions
  • Implicit dependency: r-base r-cran-rvest
  • Implicit dependency: r-base r-cran-rwave/amd64
  • Implicit dependency: r-base r-cran-rwave/arm64
  • Implicit dependency: r-base r-cran-rwave/armel
  • Implicit dependency: r-base r-cran-rwave/armhf
  • Implicit dependency: r-base r-cran-rwave/i386
  • Implicit dependency: r-base r-cran-rwave/mips64el
  • Implicit dependency: r-base r-cran-rwave/mipsel
  • Implicit dependency: r-base r-cran-rwave/ppc64el
  • Implicit dependency: r-base r-cran-rwave/s390x
  • Implicit dependency: r-base r-cran-rwiener/amd64
  • Implicit dependency: r-base r-cran-rwiener/arm64
  • Implicit dependency: r-base r-cran-rwiener/armel
  • Implicit dependency: r-base r-cran-rwiener/armhf
  • Implicit dependency: r-base r-cran-rwiener/i386
  • Implicit dependency: r-base r-cran-rwiener/mips64el
  • Implicit dependency: r-base r-cran-rwiener/mipsel
  • Implicit dependency: r-base r-cran-rwiener/ppc64el
  • Implicit dependency: r-base r-cran-rwiener/s390x
  • Implicit dependency: r-base r-cran-samr/amd64
  • Implicit dependency: r-base r-cran-samr/arm64
  • Implicit dependency: r-base r-cran-samr/armel
  • Implicit dependency: r-base r-cran-samr/armhf
  • Implicit dependency: r-base r-cran-samr/i386
  • Implicit dependency: r-base r-cran-samr/mips64el
  • Implicit dependency: r-base r-cran-samr/mipsel
  • Implicit dependency: r-base r-cran-samr/ppc64el
  • Implicit dependency: r-base r-cran-samr/s390x
  • Implicit dependency: r-base r-cran-satellite/amd64
  • Implicit dependency: r-base r-cran-satellite/arm64
  • Implicit dependency: r-base r-cran-satellite/armel
  • Implicit dependency: r-base r-cran-satellite/armhf
  • Implicit dependency: r-base r-cran-satellite/i386
  • Implicit dependency: r-base r-cran-satellite/mips64el
  • Implicit dependency: r-base r-cran-satellite/mipsel
  • Implicit dependency: r-base r-cran-satellite/ppc64el
  • Implicit dependency: r-base r-cran-satellite/s390x
  • Implicit dependency: r-base r-cran-scales
  • Implicit dependency: r-base r-cran-scatterd3
  • Implicit dependency: r-base r-cran-scatterplot3d
  • Implicit dependency: r-base r-cran-sctransform/amd64
  • Implicit dependency: r-base r-cran-sctransform/arm64
  • Implicit dependency: r-base r-cran-sctransform/armel
  • Implicit dependency: r-base r-cran-sctransform/armhf
  • Implicit dependency: r-base r-cran-sctransform/i386
  • Implicit dependency: r-base r-cran-sctransform/mips64el
  • Implicit dependency: r-base r-cran-sctransform/mipsel
  • Implicit dependency: r-base r-cran-sctransform/ppc64el
  • Implicit dependency: r-base r-cran-sctransform/s390x
  • Implicit dependency: r-base r-cran-sdmtools/amd64
  • Implicit dependency: r-base r-cran-sdmtools/arm64
  • Implicit dependency: r-base r-cran-sdmtools/armel
  • Implicit dependency: r-base r-cran-sdmtools/armhf
  • Implicit dependency: r-base r-cran-sdmtools/i386
  • Implicit dependency: r-base r-cran-sdmtools/mips64el
  • Implicit dependency: r-base r-cran-sdmtools/mipsel
  • Implicit dependency: r-base r-cran-sdmtools/ppc64el
  • Implicit dependency: r-base r-cran-sdmtools/s390x
  • Implicit dependency: r-base r-cran-segmented
  • Implicit dependency: r-base r-cran-selectr
  • Implicit dependency: r-base r-cran-sem
  • Implicit dependency: r-base r-cran-semplot
  • Implicit dependency: r-base r-cran-semtools
  • Implicit dependency: r-base r-cran-sendmailr
  • Implicit dependency: r-base r-cran-seqinr/amd64
  • Implicit dependency: r-base r-cran-seqinr/arm64
  • Implicit dependency: r-base r-cran-seqinr/armel
  • Implicit dependency: r-base r-cran-seqinr/armhf
  • Implicit dependency: r-base r-cran-seqinr/i386
  • Implicit dependency: r-base r-cran-seqinr/mips64el
  • Implicit dependency: r-base r-cran-seqinr/mipsel
  • Implicit dependency: r-base r-cran-seqinr/ppc64el
  • Implicit dependency: r-base r-cran-seqinr/s390x
  • Implicit dependency: r-base r-cran-seriation/amd64
  • Implicit dependency: r-base r-cran-seriation/arm64
  • Implicit dependency: r-base r-cran-seriation/armel
  • Implicit dependency: r-base r-cran-seriation/armhf
  • Implicit dependency: r-base r-cran-seriation/i386
  • Implicit dependency: r-base r-cran-seriation/mips64el
  • Implicit dependency: r-base r-cran-seriation/mipsel
  • Implicit dependency: r-base r-cran-seriation/ppc64el
  • Implicit dependency: r-base r-cran-seriation/s390x
  • Implicit dependency: r-base r-cran-seroincidence
  • Implicit dependency: r-base r-cran-sessioninfo
  • Implicit dependency: r-base r-cran-setrng
  • Implicit dependency: r-base r-cran-seurat/amd64
  • Implicit dependency: r-base r-cran-seurat/arm64
  • Implicit dependency: r-base r-cran-seurat/armel
  • Implicit dependency: r-base r-cran-seurat/armhf
  • Implicit dependency: r-base r-cran-seurat/i386
  • Implicit dependency: r-base r-cran-seurat/mips64el
  • Implicit dependency: r-base r-cran-seurat/mipsel
  • Implicit dependency: r-base r-cran-seurat/ppc64el
  • Implicit dependency: r-base r-cran-seurat/s390x
  • Implicit dependency: r-base r-cran-sf/amd64
  • Implicit dependency: r-base r-cran-sf/arm64
  • Implicit dependency: r-base r-cran-sf/armel
  • Implicit dependency: r-base r-cran-sf/armhf
  • Implicit dependency: r-base r-cran-sf/i386
  • Implicit dependency: r-base r-cran-sf/mips64el
  • Implicit dependency: r-base r-cran-sf/mipsel
  • Implicit dependency: r-base r-cran-sf/ppc64el
  • Implicit dependency: r-base r-cran-sf/s390x
  • Implicit dependency: r-base r-cran-sfsmisc
  • Implicit dependency: r-base r-cran-shape
  • Implicit dependency: r-base r-cran-shazam
  • Implicit dependency: r-base r-cran-shiny
  • Implicit dependency: r-base r-cran-shinybs
  • Implicit dependency: r-base r-cran-shinycssloaders
  • Implicit dependency: r-base r-cran-shinydashboard
  • Implicit dependency: r-base r-cran-shinyfiles
  • Implicit dependency: r-base r-cran-shinyjs
  • Implicit dependency: r-base r-cran-shinystan
  • Implicit dependency: r-base r-cran-shinythemes
  • Implicit dependency: r-base r-cran-sitmo/amd64
  • Implicit dependency: r-base r-cran-sitmo/arm64
  • Implicit dependency: r-base r-cran-sitmo/armel
  • Implicit dependency: r-base r-cran-sitmo/armhf
  • Implicit dependency: r-base r-cran-sitmo/i386
  • Implicit dependency: r-base r-cran-sitmo/mips64el
  • Implicit dependency: r-base r-cran-sitmo/mipsel
  • Implicit dependency: r-base r-cran-sitmo/ppc64el
  • Implicit dependency: r-base r-cran-sitmo/s390x
  • Implicit dependency: r-base r-cran-sjlabelled
  • Implicit dependency: r-base r-cran-sjmisc
  • Implicit dependency: r-base r-cran-sjplot
  • Implicit dependency: r-base r-cran-sjstats
  • Implicit dependency: r-base r-cran-slam/amd64
  • Implicit dependency: r-base r-cran-slam/arm64
  • Implicit dependency: r-base r-cran-slam/armel
  • Implicit dependency: r-base r-cran-slam/armhf
  • Implicit dependency: r-base r-cran-slam/i386
  • Implicit dependency: r-base r-cran-slam/mips64el
  • Implicit dependency: r-base r-cran-slam/mipsel
  • Implicit dependency: r-base r-cran-slam/ppc64el
  • Implicit dependency: r-base r-cran-slam/s390x
  • Implicit dependency: r-base r-cran-sn
  • Implicit dependency: r-base r-cran-snakecase
  • Implicit dependency: r-base r-cran-snowballc/amd64
  • Implicit dependency: r-base r-cran-snowballc/arm64
  • Implicit dependency: r-base r-cran-snowballc/armel
  • Implicit dependency: r-base r-cran-snowballc/armhf
  • Implicit dependency: r-base r-cran-snowballc/i386
  • Implicit dependency: r-base r-cran-snowballc/mips64el
  • Implicit dependency: r-base r-cran-snowballc/mipsel
  • Implicit dependency: r-base r-cran-snowballc/ppc64el
  • Implicit dependency: r-base r-cran-snowballc/s390x
  • Implicit dependency: r-base r-cran-snowfall
  • Implicit dependency: r-base r-cran-sodium/amd64
  • Implicit dependency: r-base r-cran-sodium/arm64
  • Implicit dependency: r-base r-cran-sodium/armel
  • Implicit dependency: r-base r-cran-sodium/armhf
  • Implicit dependency: r-base r-cran-sodium/i386
  • Implicit dependency: r-base r-cran-sodium/mips64el
  • Implicit dependency: r-base r-cran-sodium/mipsel
  • Implicit dependency: r-base r-cran-sodium/ppc64el
  • Implicit dependency: r-base r-cran-sodium/s390x
  • Implicit dependency: r-base r-cran-solrium
  • Implicit dependency: r-base r-cran-sourcetools/amd64
  • Implicit dependency: r-base r-cran-sourcetools/arm64
  • Implicit dependency: r-base r-cran-sourcetools/armel
  • Implicit dependency: r-base r-cran-sourcetools/armhf
  • Implicit dependency: r-base r-cran-sourcetools/i386
  • Implicit dependency: r-base r-cran-sourcetools/mips64el
  • Implicit dependency: r-base r-cran-sourcetools/mipsel
  • Implicit dependency: r-base r-cran-sourcetools/ppc64el
  • Implicit dependency: r-base r-cran-sourcetools/s390x
  • Implicit dependency: r-base r-cran-sp
  • Implicit dependency: r-base r-cran-spacetime
  • Implicit dependency: r-base r-cran-spam/amd64
  • Implicit dependency: r-base r-cran-spam/arm64
  • Implicit dependency: r-base r-cran-spam/armel
  • Implicit dependency: r-base r-cran-spam/armhf
  • Implicit dependency: r-base r-cran-spam/i386
  • Implicit dependency: r-base r-cran-spam/mips64el
  • Implicit dependency: r-base r-cran-spam/mipsel
  • Implicit dependency: r-base r-cran-spam/ppc64el
  • Implicit dependency: r-base r-cran-spam/s390x
  • Implicit dependency: r-base r-cran-sparsem/amd64
  • Implicit dependency: r-base r-cran-sparsem/arm64
  • Implicit dependency: r-base r-cran-sparsem/armel
  • Implicit dependency: r-base r-cran-sparsem/armhf
  • Implicit dependency: r-base r-cran-sparsem/i386
  • Implicit dependency: r-base r-cran-sparsem/mips64el
  • Implicit dependency: r-base r-cran-sparsem/mipsel
  • Implicit dependency: r-base r-cran-sparsem/ppc64el
  • Implicit dependency: r-base r-cran-sparsem/s390x
  • Implicit dependency: r-base r-cran-spatial/amd64
  • Implicit dependency: r-base r-cran-spatial/arm64
  • Implicit dependency: r-base r-cran-spatial/armel
  • Implicit dependency: r-base r-cran-spatial/armhf
  • Implicit dependency: r-base r-cran-spatial/i386
  • Implicit dependency: r-base r-cran-spatial/mips64el
  • Implicit dependency: r-base r-cran-spatial/mipsel
  • Implicit dependency: r-base r-cran-spatial/ppc64el
  • Implicit dependency: r-base r-cran-spatial/s390x
  • Implicit dependency: r-base r-cran-spatialreg/amd64
  • Implicit dependency: r-base r-cran-spatialreg/arm64
  • Implicit dependency: r-base r-cran-spatialreg/armel
  • Implicit dependency: r-base r-cran-spatialreg/armhf
  • Implicit dependency: r-base r-cran-spatialreg/i386
  • Implicit dependency: r-base r-cran-spatialreg/mips64el
  • Implicit dependency: r-base r-cran-spatialreg/mipsel
  • Implicit dependency: r-base r-cran-spatialreg/ppc64el
  • Implicit dependency: r-base r-cran-spatialreg/s390x
  • Implicit dependency: r-base r-cran-spatstat
  • Implicit dependency: r-base r-cran-spatstat.data
  • Implicit dependency: r-base r-cran-spatstat.utils/amd64
  • Implicit dependency: r-base r-cran-spatstat.utils/arm64
  • Implicit dependency: r-base r-cran-spatstat.utils/armel
  • Implicit dependency: r-base r-cran-spatstat.utils/armhf
  • Implicit dependency: r-base r-cran-spatstat.utils/i386
  • Implicit dependency: r-base r-cran-spatstat.utils/mips64el
  • Implicit dependency: r-base r-cran-spatstat.utils/mipsel
  • Implicit dependency: r-base r-cran-spatstat.utils/ppc64el
  • Implicit dependency: r-base r-cran-spatstat.utils/s390x
  • Implicit dependency: r-base r-cran-spc
  • Implicit dependency: r-base r-cran-spdata
  • Implicit dependency: r-base r-cran-spdep/amd64
  • Implicit dependency: r-base r-cran-spdep/arm64
  • Implicit dependency: r-base r-cran-spdep/armel
  • Implicit dependency: r-base r-cran-spdep/armhf
  • Implicit dependency: r-base r-cran-spdep/i386
  • Implicit dependency: r-base r-cran-spdep/mips64el
  • Implicit dependency: r-base r-cran-spdep/mipsel
  • Implicit dependency: r-base r-cran-spdep/ppc64el
  • Implicit dependency: r-base r-cran-spdep/s390x
  • Implicit dependency: r-base r-cran-splines2
  • Implicit dependency: r-base r-cran-spp/amd64
  • Implicit dependency: r-base r-cran-spp/arm64
  • Implicit dependency: r-base r-cran-spp/armel
  • Implicit dependency: r-base r-cran-spp/armhf
  • Implicit dependency: r-base r-cran-spp/i386
  • Implicit dependency: r-base r-cran-spp/mips64el
  • Implicit dependency: r-base r-cran-spp/mipsel
  • Implicit dependency: r-base r-cran-spp/ppc64el
  • Implicit dependency: r-base r-cran-spp/s390x
  • Implicit dependency: r-base r-cran-squarem
  • Implicit dependency: r-base r-cran-stabledist
  • Implicit dependency: r-base r-cran-stanheaders/amd64
  • Implicit dependency: r-base r-cran-stanheaders/arm64
  • Implicit dependency: r-base r-cran-stanheaders/armel
  • Implicit dependency: r-base r-cran-stanheaders/armhf
  • Implicit dependency: r-base r-cran-stanheaders/i386
  • Implicit dependency: r-base r-cran-stanheaders/mips64el
  • Implicit dependency: r-base r-cran-stanheaders/mipsel
  • Implicit dependency: r-base r-cran-stanheaders/ppc64el
  • Implicit dependency: r-base r-cran-stanheaders/s390x
  • Implicit dependency: r-base r-cran-stars
  • Implicit dependency: r-base r-cran-statmod/amd64
  • Implicit dependency: r-base r-cran-statmod/arm64
  • Implicit dependency: r-base r-cran-statmod/armel
  • Implicit dependency: r-base r-cran-statmod/armhf
  • Implicit dependency: r-base r-cran-statmod/i386
  • Implicit dependency: r-base r-cran-statmod/mips64el
  • Implicit dependency: r-base r-cran-statmod/mipsel
  • Implicit dependency: r-base r-cran-statmod/ppc64el
  • Implicit dependency: r-base r-cran-statmod/s390x
  • Implicit dependency: r-base r-cran-stringdist/amd64
  • Implicit dependency: r-base r-cran-stringdist/arm64
  • Implicit dependency: r-base r-cran-stringdist/armel
  • Implicit dependency: r-base r-cran-stringdist/armhf
  • Implicit dependency: r-base r-cran-stringdist/i386
  • Implicit dependency: r-base r-cran-stringdist/mips64el
  • Implicit dependency: r-base r-cran-stringdist/mipsel
  • Implicit dependency: r-base r-cran-stringdist/ppc64el
  • Implicit dependency: r-base r-cran-stringdist/s390x
  • Implicit dependency: r-base r-cran-stringi/amd64
  • Implicit dependency: r-base r-cran-stringi/arm64
  • Implicit dependency: r-base r-cran-stringi/armel
  • Implicit dependency: r-base r-cran-stringi/armhf
  • Implicit dependency: r-base r-cran-stringi/i386
  • Implicit dependency: r-base r-cran-stringi/mips64el
  • Implicit dependency: r-base r-cran-stringi/mipsel
  • Implicit dependency: r-base r-cran-stringi/ppc64el
  • Implicit dependency: r-base r-cran-stringi/s390x
  • Implicit dependency: r-base r-cran-stringr
  • Implicit dependency: r-base r-cran-surveillance/amd64
  • Implicit dependency: r-base r-cran-surveillance/arm64
  • Implicit dependency: r-base r-cran-surveillance/armel
  • Implicit dependency: r-base r-cran-surveillance/armhf
  • Implicit dependency: r-base r-cran-surveillance/i386
  • Implicit dependency: r-base r-cran-surveillance/mips64el
  • Implicit dependency: r-base r-cran-surveillance/mipsel
  • Implicit dependency: r-base r-cran-surveillance/ppc64el
  • Implicit dependency: r-base r-cran-surveillance/s390x
  • Implicit dependency: r-base r-cran-survey
  • Implicit dependency: r-base r-cran-survminer
  • Implicit dependency: r-base r-cran-survmisc
  • Implicit dependency: r-base r-cran-svglite
  • Implicit dependency: r-base r-cran-sys/amd64
  • Implicit dependency: r-base r-cran-sys/arm64
  • Implicit dependency: r-base r-cran-sys/armel
  • Implicit dependency: r-base r-cran-sys/armhf
  • Implicit dependency: r-base r-cran-sys/i386
  • Implicit dependency: r-base r-cran-sys/mips64el
  • Implicit dependency: r-base r-cran-sys/mipsel
  • Implicit dependency: r-base r-cran-sys/ppc64el
  • Implicit dependency: r-base r-cran-sys/s390x
  • Implicit dependency: r-base r-cran-systemfit
  • Implicit dependency: r-base r-cran-systemfonts
  • Implicit dependency: r-base r-cran-taxize
  • Implicit dependency: r-base r-cran-tcltk2
  • Implicit dependency: r-base r-cran-tcr/amd64
  • Implicit dependency: r-base r-cran-tcr/arm64
  • Implicit dependency: r-base r-cran-tcr/armel
  • Implicit dependency: r-base r-cran-tcr/armhf
  • Implicit dependency: r-base r-cran-tcr/i386
  • Implicit dependency: r-base r-cran-tcr/mips64el
  • Implicit dependency: r-base r-cran-tcr/mipsel
  • Implicit dependency: r-base r-cran-tcr/ppc64el
  • Implicit dependency: r-base r-cran-tcr/s390x
  • Implicit dependency: r-base r-cran-teachingdemos
  • Implicit dependency: r-base r-cran-tensor
  • Implicit dependency: r-base r-cran-testextra
  • Implicit dependency: r-base r-cran-testit
  • Implicit dependency: r-base r-cran-testthat
  • Implicit dependency: r-base r-cran-tfisher
  • Implicit dependency: r-base r-cran-tfmpvalue/amd64
  • Implicit dependency: r-base r-cran-tfmpvalue/arm64
  • Implicit dependency: r-base r-cran-tfmpvalue/armel
  • Implicit dependency: r-base r-cran-tfmpvalue/armhf
  • Implicit dependency: r-base r-cran-tfmpvalue/i386
  • Implicit dependency: r-base r-cran-tfmpvalue/mips64el
  • Implicit dependency: r-base r-cran-tfmpvalue/mipsel
  • Implicit dependency: r-base r-cran-tfmpvalue/ppc64el
  • Implicit dependency: r-base r-cran-tfmpvalue/s390x
  • Implicit dependency: r-base r-cran-tgp/amd64
  • Implicit dependency: r-base r-cran-tgp/arm64
  • Implicit dependency: r-base r-cran-tgp/armel
  • Implicit dependency: r-base r-cran-tgp/armhf
  • Implicit dependency: r-base r-cran-tgp/i386
  • Implicit dependency: r-base r-cran-tgp/mips64el
  • Implicit dependency: r-base r-cran-tgp/mipsel
  • Implicit dependency: r-base r-cran-tgp/ppc64el
  • Implicit dependency: r-base r-cran-tgp/s390x
  • Implicit dependency: r-base r-cran-th.data
  • Implicit dependency: r-base r-cran-threejs
  • Implicit dependency: r-base r-cran-tibble/amd64
  • Implicit dependency: r-base r-cran-tibble/arm64
  • Implicit dependency: r-base r-cran-tibble/armel
  • Implicit dependency: r-base r-cran-tibble/armhf
  • Implicit dependency: r-base r-cran-tibble/i386
  • Implicit dependency: r-base r-cran-tibble/mips64el
  • Implicit dependency: r-base r-cran-tibble/mipsel
  • Implicit dependency: r-base r-cran-tibble/ppc64el
  • Implicit dependency: r-base r-cran-tibble/s390x
  • Implicit dependency: r-base r-cran-tidygraph
  • Implicit dependency: r-base r-cran-tidyr/amd64
  • Implicit dependency: r-base r-cran-tidyr/arm64
  • Implicit dependency: r-base r-cran-tidyr/armel
  • Implicit dependency: r-base r-cran-tidyr/armhf
  • Implicit dependency: r-base r-cran-tidyr/i386
  • Implicit dependency: r-base r-cran-tidyr/mips64el
  • Implicit dependency: r-base r-cran-tidyr/mipsel
  • Implicit dependency: r-base r-cran-tidyr/ppc64el
  • Implicit dependency: r-base r-cran-tidyr/s390x
  • Implicit dependency: r-base r-cran-tidyselect
  • Implicit dependency: r-base r-cran-tidyverse
  • Implicit dependency: r-base r-cran-tiff/amd64
  • Implicit dependency: r-base r-cran-tiff/arm64
  • Implicit dependency: r-base r-cran-tiff/armel
  • Implicit dependency: r-base r-cran-tiff/armhf
  • Implicit dependency: r-base r-cran-tiff/i386
  • Implicit dependency: r-base r-cran-tiff/mips64el
  • Implicit dependency: r-base r-cran-tiff/mipsel
  • Implicit dependency: r-base r-cran-tiff/ppc64el
  • Implicit dependency: r-base r-cran-tiff/s390x
  • Implicit dependency: r-base r-cran-tigger
  • Implicit dependency: r-base r-cran-tikzdevice/amd64
  • Implicit dependency: r-base r-cran-tikzdevice/arm64
  • Implicit dependency: r-base r-cran-tikzdevice/armel
  • Implicit dependency: r-base r-cran-tikzdevice/armhf
  • Implicit dependency: r-base r-cran-tikzdevice/i386
  • Implicit dependency: r-base r-cran-tikzdevice/mips64el
  • Implicit dependency: r-base r-cran-tikzdevice/mipsel
  • Implicit dependency: r-base r-cran-tikzdevice/ppc64el
  • Implicit dependency: r-base r-cran-tikzdevice/s390x
  • Implicit dependency: r-base r-cran-timedate/amd64
  • Implicit dependency: r-base r-cran-timedate/arm64
  • Implicit dependency: r-base r-cran-timedate/armel
  • Implicit dependency: r-base r-cran-timedate/armhf
  • Implicit dependency: r-base r-cran-timedate/i386
  • Implicit dependency: r-base r-cran-timedate/mips64el
  • Implicit dependency: r-base r-cran-timedate/mipsel
  • Implicit dependency: r-base r-cran-timedate/ppc64el
  • Implicit dependency: r-base r-cran-timedate/s390x
  • Implicit dependency: r-base r-cran-timereg/amd64
  • Implicit dependency: r-base r-cran-timereg/arm64
  • Implicit dependency: r-base r-cran-timereg/armel
  • Implicit dependency: r-base r-cran-timereg/armhf
  • Implicit dependency: r-base r-cran-timereg/i386
  • Implicit dependency: r-base r-cran-timereg/mips64el
  • Implicit dependency: r-base r-cran-timereg/mipsel
  • Implicit dependency: r-base r-cran-timereg/ppc64el
  • Implicit dependency: r-base r-cran-timereg/s390x
  • Implicit dependency: r-base r-cran-timeseries
  • Implicit dependency: r-base r-cran-tinytest
  • Implicit dependency: r-base r-cran-tinytex
  • Implicit dependency: r-base r-cran-tm/amd64
  • Implicit dependency: r-base r-cran-tm/arm64
  • Implicit dependency: r-base r-cran-tm/armel
  • Implicit dependency: r-base r-cran-tm/armhf
  • Implicit dependency: r-base r-cran-tm/i386
  • Implicit dependency: r-base r-cran-tm/mips64el
  • Implicit dependency: r-base r-cran-tm/mipsel
  • Implicit dependency: r-base r-cran-tm/ppc64el
  • Implicit dependency: r-base r-cran-tm/s390x
  • Implicit dependency: r-base r-cran-tmb/amd64
  • Implicit dependency: r-base r-cran-tmb/arm64
  • Implicit dependency: r-base r-cran-tmb/armel
  • Implicit dependency: r-base r-cran-tmb/armhf
  • Implicit dependency: r-base r-cran-tmb/i386
  • Implicit dependency: r-base r-cran-tmb/mips64el
  • Implicit dependency: r-base r-cran-tmb/mipsel
  • Implicit dependency: r-base r-cran-tmb/ppc64el
  • Implicit dependency: r-base r-cran-tmb/s390x
  • Implicit dependency: r-base r-cran-tmvtnorm/amd64
  • Implicit dependency: r-base r-cran-tmvtnorm/arm64
  • Implicit dependency: r-base r-cran-tmvtnorm/armel
  • Implicit dependency: r-base r-cran-tmvtnorm/armhf
  • Implicit dependency: r-base r-cran-tmvtnorm/i386
  • Implicit dependency: r-base r-cran-tmvtnorm/mips64el
  • Implicit dependency: r-base r-cran-tmvtnorm/mipsel
  • Implicit dependency: r-base r-cran-tmvtnorm/ppc64el
  • Implicit dependency: r-base r-cran-tmvtnorm/s390x
  • Implicit dependency: r-base r-cran-transformr/amd64
  • Implicit dependency: r-base r-cran-transformr/arm64
  • Implicit dependency: r-base r-cran-transformr/armel
  • Implicit dependency: r-base r-cran-transformr/armhf
  • Implicit dependency: r-base r-cran-transformr/i386
  • Implicit dependency: r-base r-cran-transformr/mips64el
  • Implicit dependency: r-base r-cran-transformr/mipsel
  • Implicit dependency: r-base r-cran-transformr/ppc64el
  • Implicit dependency: r-base r-cran-transformr/s390x
  • Implicit dependency: r-base r-cran-treescape
  • Implicit dependency: r-base r-cran-treespace/amd64
  • Implicit dependency: r-base r-cran-treespace/arm64
  • Implicit dependency: r-base r-cran-treespace/armhf
  • Implicit dependency: r-base r-cran-treespace/i386
  • Implicit dependency: r-base r-cran-treespace/mips64el
  • Implicit dependency: r-base r-cran-treespace/mipsel
  • Implicit dependency: r-base r-cran-treespace/ppc64el
  • Implicit dependency: r-base r-cran-treespace/s390x
  • Implicit dependency: r-base r-cran-triebeard/amd64
  • Implicit dependency: r-base r-cran-triebeard/arm64
  • Implicit dependency: r-base r-cran-triebeard/armel
  • Implicit dependency: r-base r-cran-triebeard/armhf
  • Implicit dependency: r-base r-cran-triebeard/i386
  • Implicit dependency: r-base r-cran-triebeard/mips64el
  • Implicit dependency: r-base r-cran-triebeard/mipsel
  • Implicit dependency: r-base r-cran-triebeard/ppc64el
  • Implicit dependency: r-base r-cran-triebeard/s390x
  • Implicit dependency: r-base r-cran-trimcluster
  • Implicit dependency: r-base r-cran-truncdist
  • Implicit dependency: r-base r-cran-truncnorm/amd64
  • Implicit dependency: r-base r-cran-truncnorm/arm64
  • Implicit dependency: r-base r-cran-truncnorm/armel
  • Implicit dependency: r-base r-cran-truncnorm/armhf
  • Implicit dependency: r-base r-cran-truncnorm/i386
  • Implicit dependency: r-base r-cran-truncnorm/mips64el
  • Implicit dependency: r-base r-cran-truncnorm/mipsel
  • Implicit dependency: r-base r-cran-truncnorm/ppc64el
  • Implicit dependency: r-base r-cran-truncnorm/s390x
  • Implicit dependency: r-base r-cran-tsne
  • Implicit dependency: r-base r-cran-tsp/amd64
  • Implicit dependency: r-base r-cran-tsp/arm64
  • Implicit dependency: r-base r-cran-tsp/armel
  • Implicit dependency: r-base r-cran-tsp/armhf
  • Implicit dependency: r-base r-cran-tsp/i386
  • Implicit dependency: r-base r-cran-tsp/mips64el
  • Implicit dependency: r-base r-cran-tsp/mipsel
  • Implicit dependency: r-base r-cran-tsp/ppc64el
  • Implicit dependency: r-base r-cran-tsp/s390x
  • Implicit dependency: r-base r-cran-ttr/amd64
  • Implicit dependency: r-base r-cran-ttr/arm64
  • Implicit dependency: r-base r-cran-ttr/armel
  • Implicit dependency: r-base r-cran-ttr/armhf
  • Implicit dependency: r-base r-cran-ttr/i386
  • Implicit dependency: r-base r-cran-ttr/mips64el
  • Implicit dependency: r-base r-cran-ttr/mipsel
  • Implicit dependency: r-base r-cran-ttr/ppc64el
  • Implicit dependency: r-base r-cran-ttr/s390x
  • Implicit dependency: r-base r-cran-tufte
  • Implicit dependency: r-base r-cran-tweenr/amd64
  • Implicit dependency: r-base r-cran-tweenr/arm64
  • Implicit dependency: r-base r-cran-tweenr/armel
  • Implicit dependency: r-base r-cran-tweenr/armhf
  • Implicit dependency: r-base r-cran-tweenr/i386
  • Implicit dependency: r-base r-cran-tweenr/mips64el
  • Implicit dependency: r-base r-cran-tweenr/mipsel
  • Implicit dependency: r-base r-cran-tweenr/ppc64el
  • Implicit dependency: r-base r-cran-tweenr/s390x
  • Implicit dependency: r-base r-cran-ucminf/amd64
  • Implicit dependency: r-base r-cran-ucminf/arm64
  • Implicit dependency: r-base r-cran-ucminf/armel
  • Implicit dependency: r-base r-cran-ucminf/armhf
  • Implicit dependency: r-base r-cran-ucminf/i386
  • Implicit dependency: r-base r-cran-ucminf/mips64el
  • Implicit dependency: r-base r-cran-ucminf/mipsel
  • Implicit dependency: r-base r-cran-ucminf/ppc64el
  • Implicit dependency: r-base r-cran-ucminf/s390x
  • Implicit dependency: r-base r-cran-udunits2/amd64
  • Implicit dependency: r-base r-cran-udunits2/arm64
  • Implicit dependency: r-base r-cran-udunits2/armel
  • Implicit dependency: r-base r-cran-udunits2/armhf
  • Implicit dependency: r-base r-cran-udunits2/i386
  • Implicit dependency: r-base r-cran-udunits2/mips64el
  • Implicit dependency: r-base r-cran-udunits2/mipsel
  • Implicit dependency: r-base r-cran-udunits2/ppc64el
  • Implicit dependency: r-base r-cran-udunits2/s390x
  • Implicit dependency: r-base r-cran-unitizer
  • Implicit dependency: r-base r-cran-units/amd64
  • Implicit dependency: r-base r-cran-units/arm64
  • Implicit dependency: r-base r-cran-units/armel
  • Implicit dependency: r-base r-cran-units/armhf
  • Implicit dependency: r-base r-cran-units/i386
  • Implicit dependency: r-base r-cran-units/mips64el
  • Implicit dependency: r-base r-cran-units/mipsel
  • Implicit dependency: r-base r-cran-units/ppc64el
  • Implicit dependency: r-base r-cran-units/s390x
  • Implicit dependency: r-base r-cran-urltools/amd64
  • Implicit dependency: r-base r-cran-urltools/arm64
  • Implicit dependency: r-base r-cran-urltools/armel
  • Implicit dependency: r-base r-cran-urltools/armhf
  • Implicit dependency: r-base r-cran-urltools/i386
  • Implicit dependency: r-base r-cran-urltools/mips64el
  • Implicit dependency: r-base r-cran-urltools/mipsel
  • Implicit dependency: r-base r-cran-urltools/ppc64el
  • Implicit dependency: r-base r-cran-urltools/s390x
  • Implicit dependency: r-base r-cran-uroot
  • Implicit dependency: r-base r-cran-usethis
  • Implicit dependency: r-base r-cran-utf8/amd64
  • Implicit dependency: r-base r-cran-utf8/arm64
  • Implicit dependency: r-base r-cran-utf8/armel
  • Implicit dependency: r-base r-cran-utf8/armhf
  • Implicit dependency: r-base r-cran-utf8/i386
  • Implicit dependency: r-base r-cran-utf8/mips64el
  • Implicit dependency: r-base r-cran-utf8/mipsel
  • Implicit dependency: r-base r-cran-utf8/ppc64el
  • Implicit dependency: r-base r-cran-utf8/s390x
  • Implicit dependency: r-base r-cran-uuid/amd64
  • Implicit dependency: r-base r-cran-uuid/arm64
  • Implicit dependency: r-base r-cran-uuid/armel
  • Implicit dependency: r-base r-cran-uuid/armhf
  • Implicit dependency: r-base r-cran-uuid/i386
  • Implicit dependency: r-base r-cran-uuid/mips64el
  • Implicit dependency: r-base r-cran-uuid/mipsel
  • Implicit dependency: r-base r-cran-uuid/ppc64el
  • Implicit dependency: r-base r-cran-uuid/s390x
  • Implicit dependency: r-base r-cran-uwot/amd64
  • Implicit dependency: r-base r-cran-uwot/arm64
  • Implicit dependency: r-base r-cran-uwot/armel
  • Implicit dependency: r-base r-cran-uwot/armhf
  • Implicit dependency: r-base r-cran-uwot/i386
  • Implicit dependency: r-base r-cran-uwot/mips64el
  • Implicit dependency: r-base r-cran-uwot/mipsel
  • Implicit dependency: r-base r-cran-uwot/ppc64el
  • Implicit dependency: r-base r-cran-uwot/s390x
  • Implicit dependency: r-base r-cran-v8/amd64
  • Implicit dependency: r-base r-cran-v8/arm64
  • Implicit dependency: r-base r-cran-v8/armhf
  • Implicit dependency: r-base r-cran-v8/i386
  • Implicit dependency: r-base r-cran-v8/mips64el
  • Implicit dependency: r-base r-cran-v8/mipsel
  • Implicit dependency: r-base r-cran-v8/ppc64el
  • Implicit dependency: r-base r-cran-v8/s390x
  • Implicit dependency: r-base r-cran-vcd
  • Implicit dependency: r-base r-cran-vcdextra
  • Implicit dependency: r-base r-cran-vcr
  • Implicit dependency: r-base r-cran-vctrs
  • Implicit dependency: r-base r-cran-vdiffr/amd64
  • Implicit dependency: r-base r-cran-vdiffr/arm64
  • Implicit dependency: r-base r-cran-vdiffr/armhf
  • Implicit dependency: r-base r-cran-vdiffr/i386
  • Implicit dependency: r-base r-cran-vdiffr/mips64el
  • Implicit dependency: r-base r-cran-vdiffr/mipsel
  • Implicit dependency: r-base r-cran-vdiffr/ppc64el
  • Implicit dependency: r-base r-cran-vdiffr/s390x
  • Implicit dependency: r-base r-cran-vegan/amd64
  • Implicit dependency: r-base r-cran-vegan/arm64
  • Implicit dependency: r-base r-cran-vegan/armel
  • Implicit dependency: r-base r-cran-vegan/armhf
  • Implicit dependency: r-base r-cran-vegan/i386
  • Implicit dependency: r-base r-cran-vegan/mips64el
  • Implicit dependency: r-base r-cran-vegan/mipsel
  • Implicit dependency: r-base r-cran-vegan/ppc64el
  • Implicit dependency: r-base r-cran-vegan/s390x
  • Implicit dependency: r-base r-cran-venndiagram
  • Implicit dependency: r-base r-cran-vgam/amd64
  • Implicit dependency: r-base r-cran-vgam/arm64
  • Implicit dependency: r-base r-cran-vgam/armel
  • Implicit dependency: r-base r-cran-vgam/armhf
  • Implicit dependency: r-base r-cran-vgam/i386
  • Implicit dependency: r-base r-cran-vgam/mips64el
  • Implicit dependency: r-base r-cran-vgam/mipsel
  • Implicit dependency: r-base r-cran-vgam/ppc64el
  • Implicit dependency: r-base r-cran-vgam/s390x
  • Implicit dependency: r-base r-cran-vioplot
  • Implicit dependency: r-base r-cran-vipor
  • Implicit dependency: r-base r-cran-viridis
  • Implicit dependency: r-base r-cran-viridislite
  • Implicit dependency: r-base r-cran-waveslim/amd64
  • Implicit dependency: r-base r-cran-waveslim/arm64
  • Implicit dependency: r-base r-cran-waveslim/armel
  • Implicit dependency: r-base r-cran-waveslim/armhf
  • Implicit dependency: r-base r-cran-waveslim/i386
  • Implicit dependency: r-base r-cran-waveslim/mips64el
  • Implicit dependency: r-base r-cran-waveslim/mipsel
  • Implicit dependency: r-base r-cran-waveslim/ppc64el
  • Implicit dependency: r-base r-cran-waveslim/s390x
  • Implicit dependency: r-base r-cran-wavethresh/amd64
  • Implicit dependency: r-base r-cran-wavethresh/arm64
  • Implicit dependency: r-base r-cran-wavethresh/armel
  • Implicit dependency: r-base r-cran-wavethresh/armhf
  • Implicit dependency: r-base r-cran-wavethresh/i386
  • Implicit dependency: r-base r-cran-wavethresh/mips64el
  • Implicit dependency: r-base r-cran-wavethresh/mipsel
  • Implicit dependency: r-base r-cran-wavethresh/ppc64el
  • Implicit dependency: r-base r-cran-wavethresh/s390x
  • Implicit dependency: r-base r-cran-wdi
  • Implicit dependency: r-base r-cran-webgestaltr/amd64
  • Implicit dependency: r-base r-cran-webgestaltr/arm64
  • Implicit dependency: r-base r-cran-webgestaltr/armel
  • Implicit dependency: r-base r-cran-webgestaltr/armhf
  • Implicit dependency: r-base r-cran-webgestaltr/i386
  • Implicit dependency: r-base r-cran-webgestaltr/mips64el
  • Implicit dependency: r-base r-cran-webgestaltr/mipsel
  • Implicit dependency: r-base r-cran-webgestaltr/ppc64el
  • Implicit dependency: r-base r-cran-webgestaltr/s390x
  • Implicit dependency: r-base r-cran-webmockr
  • Implicit dependency: r-base r-cran-webshot
  • Implicit dependency: r-base r-cran-webutils/amd64
  • Implicit dependency: r-base r-cran-webutils/arm64
  • Implicit dependency: r-base r-cran-webutils/armel
  • Implicit dependency: r-base r-cran-webutils/armhf
  • Implicit dependency: r-base r-cran-webutils/i386
  • Implicit dependency: r-base r-cran-webutils/mips64el
  • Implicit dependency: r-base r-cran-webutils/mipsel
  • Implicit dependency: r-base r-cran-webutils/ppc64el
  • Implicit dependency: r-base r-cran-webutils/s390x
  • Implicit dependency: r-base r-cran-wgcna/amd64
  • Implicit dependency: r-base r-cran-wgcna/arm64
  • Implicit dependency: r-base r-cran-wgcna/armhf
  • Implicit dependency: r-base r-cran-wgcna/i386
  • Implicit dependency: r-base r-cran-wgcna/mips64el
  • Implicit dependency: r-base r-cran-wgcna/mipsel
  • Implicit dependency: r-base r-cran-wgcna/ppc64el
  • Implicit dependency: r-base r-cran-wgcna/s390x
  • Implicit dependency: r-base r-cran-whatif
  • Implicit dependency: r-base r-cran-whisker
  • Implicit dependency: r-base r-cran-wikidatar
  • Implicit dependency: r-base r-cran-wikipedir
  • Implicit dependency: r-base r-cran-wikitaxa
  • Implicit dependency: r-base r-cran-withr
  • Implicit dependency: r-base r-cran-wordcloud/amd64
  • Implicit dependency: r-base r-cran-wordcloud/arm64
  • Implicit dependency: r-base r-cran-wordcloud/armel
  • Implicit dependency: r-base r-cran-wordcloud/armhf
  • Implicit dependency: r-base r-cran-wordcloud/i386
  • Implicit dependency: r-base r-cran-wordcloud/mips64el
  • Implicit dependency: r-base r-cran-wordcloud/mipsel
  • Implicit dependency: r-base r-cran-wordcloud/ppc64el
  • Implicit dependency: r-base r-cran-wordcloud/s390x
  • Implicit dependency: r-base r-cran-worrms
  • Implicit dependency: r-base r-cran-xfun
  • Implicit dependency: r-base r-cran-xml/amd64
  • Implicit dependency: r-base r-cran-xml/arm64
  • Implicit dependency: r-base r-cran-xml/armel
  • Implicit dependency: r-base r-cran-xml/armhf
  • Implicit dependency: r-base r-cran-xml/i386
  • Implicit dependency: r-base r-cran-xml/mips64el
  • Implicit dependency: r-base r-cran-xml/mipsel
  • Implicit dependency: r-base r-cran-xml/ppc64el
  • Implicit dependency: r-base r-cran-xml/s390x
  • Implicit dependency: r-base r-cran-xml2/amd64
  • Implicit dependency: r-base r-cran-xml2/arm64
  • Implicit dependency: r-base r-cran-xml2/armel
  • Implicit dependency: r-base r-cran-xml2/armhf
  • Implicit dependency: r-base r-cran-xml2/i386
  • Implicit dependency: r-base r-cran-xml2/mips64el
  • Implicit dependency: r-base r-cran-xml2/mipsel
  • Implicit dependency: r-base r-cran-xml2/ppc64el
  • Implicit dependency: r-base r-cran-xml2/s390x
  • Implicit dependency: r-base r-cran-xopen
  • Implicit dependency: r-base r-cran-xslt
  • Implicit dependency: r-base r-cran-xtable
  • Implicit dependency: r-base r-cran-xts/amd64
  • Implicit dependency: r-base r-cran-xts/arm64
  • Implicit dependency: r-base r-cran-xts/armel
  • Implicit dependency: r-base r-cran-xts/armhf
  • Implicit dependency: r-base r-cran-xts/i386
  • Implicit dependency: r-base r-cran-xts/mips64el
  • Implicit dependency: r-base r-cran-xts/mipsel
  • Implicit dependency: r-base r-cran-xts/ppc64el
  • Implicit dependency: r-base r-cran-xts/s390x
  • Implicit dependency: r-base r-cran-yaml/amd64
  • Implicit dependency: r-base r-cran-yaml/arm64
  • Implicit dependency: r-base r-cran-yaml/armel
  • Implicit dependency: r-base r-cran-yaml/armhf
  • Implicit dependency: r-base r-cran-yaml/i386
  • Implicit dependency: r-base r-cran-yaml/mips64el
  • Implicit dependency: r-base r-cran-yaml/mipsel
  • Implicit dependency: r-base r-cran-yaml/ppc64el
  • Implicit dependency: r-base r-cran-yaml/s390x
  • Implicit dependency: r-base r-cran-zeallot
  • Implicit dependency: r-base r-cran-zelig
  • Implicit dependency: r-base r-cran-zeligchoice
  • Implicit dependency: r-base r-cran-zeligei
  • Implicit dependency: r-base r-cran-zeligverse
  • Implicit dependency: r-base r-cran-zip/amd64
  • Implicit dependency: r-base r-cran-zip/arm64
  • Implicit dependency: r-base r-cran-zip/armel
  • Implicit dependency: r-base r-cran-zip/armhf
  • Implicit dependency: r-base r-cran-zip/i386
  • Implicit dependency: r-base r-cran-zip/mips64el
  • Implicit dependency: r-base r-cran-zip/mipsel
  • Implicit dependency: r-base r-cran-zip/ppc64el
  • Implicit dependency: r-base r-cran-zip/s390x
  • Implicit dependency: r-base r-omegahat-xmlrpc
  • Implicit dependency: r-base r-other-amsmercury/amd64
  • Implicit dependency: r-base r-other-amsmercury/arm64
  • Implicit dependency: r-base r-other-amsmercury/armel
  • Implicit dependency: r-base r-other-amsmercury/armhf
  • Implicit dependency: r-base r-other-amsmercury/i386
  • Implicit dependency: r-base r-other-amsmercury/mips64el
  • Implicit dependency: r-base r-other-amsmercury/mipsel
  • Implicit dependency: r-base r-other-amsmercury/ppc64el
  • Implicit dependency: r-base r-other-amsmercury/s390x
  • Implicit dependency: r-base r-other-chbutils/amd64
  • Implicit dependency: r-base r-other-chbutils/arm64
  • Implicit dependency: r-base r-other-chbutils/armel
  • Implicit dependency: r-base r-other-chbutils/armhf
  • Implicit dependency: r-base r-other-chbutils/i386
  • Implicit dependency: r-base r-other-chbutils/mips64el
  • Implicit dependency: r-base r-other-chbutils/mipsel
  • Implicit dependency: r-base r-other-chbutils/ppc64el
  • Implicit dependency: r-base r-other-chbutils/s390x
  • Implicit dependency: r-base r-other-curvefdp
  • Implicit dependency: r-base r-other-iwrlars/amd64
  • Implicit dependency: r-base r-other-iwrlars/arm64
  • Implicit dependency: r-base r-other-iwrlars/armel
  • Implicit dependency: r-base r-other-iwrlars/armhf
  • Implicit dependency: r-base r-other-iwrlars/i386
  • Implicit dependency: r-base r-other-iwrlars/mips64el
  • Implicit dependency: r-base r-other-iwrlars/mipsel
  • Implicit dependency: r-base r-other-iwrlars/ppc64el
  • Implicit dependency: r-base r-other-iwrlars/s390x
  • Implicit dependency: r-base r-other-mott-happy/amd64
  • Implicit dependency: r-base r-other-mott-happy/arm64
  • Implicit dependency: r-base r-other-mott-happy/armel
  • Implicit dependency: r-base r-other-mott-happy/armhf
  • Implicit dependency: r-base r-other-mott-happy/i386
  • Implicit dependency: r-base r-other-mott-happy/mips64el
  • Implicit dependency: r-base r-other-mott-happy/mipsel
  • Implicit dependency: r-base r-other-mott-happy/ppc64el
  • Implicit dependency: r-base r-other-mott-happy/s390x
  • Implicit dependency: r-base r-other-nitpick
  • Implicit dependency: r-base r-other-wasabi
  • Implicit dependency: r-base r-other-x4r/amd64
  • Implicit dependency: r-base r-other-x4r/arm64
  • Implicit dependency: r-base r-other-x4r/armel
  • Implicit dependency: r-base r-other-x4r/armhf
  • Implicit dependency: r-base r-other-x4r/i386
  • Implicit dependency: r-base r-other-x4r/mips64el
  • Implicit dependency: r-base r-other-x4r/mipsel
  • Implicit dependency: r-base r-other-x4r/ppc64el
  • Implicit dependency: r-base r-other-x4r/s390x
  • Implicit dependency: r-base r-zoo/amd64
  • Implicit dependency: r-base r-zoo/arm64
  • Implicit dependency: r-base r-zoo/armel
  • Implicit dependency: r-base r-zoo/armhf
  • Implicit dependency: r-base r-zoo/i386
  • Implicit dependency: r-base r-zoo/mips64el
  • Implicit dependency: r-base r-zoo/mipsel
  • Implicit dependency: r-base r-zoo/ppc64el
  • Implicit dependency: r-base r-zoo/s390x
  • Implicit dependency: r-base rcmdr
  • Implicit dependency: r-base rcolorbrewer
  • Implicit dependency: r-base rcpp/amd64
  • Implicit dependency: r-base rcpp/arm64
  • Implicit dependency: r-base rcpp/armel
  • Implicit dependency: r-base rcpp/armhf
  • Implicit dependency: r-base rcpp/i386
  • Implicit dependency: r-base rcpp/mips64el
  • Implicit dependency: r-base rcpp/mipsel
  • Implicit dependency: r-base rcpp/ppc64el
  • Implicit dependency: r-base rcpp/s390x
  • Implicit dependency: r-base relimp
  • Implicit dependency: r-base rggobi/amd64
  • Implicit dependency: r-base rggobi/arm64
  • Implicit dependency: r-base rggobi/armel
  • Implicit dependency: r-base rggobi/armhf
  • Implicit dependency: r-base rggobi/i386
  • Implicit dependency: r-base rggobi/mips64el
  • Implicit dependency: r-base rggobi/mipsel
  • Implicit dependency: r-base rggobi/ppc64el
  • Implicit dependency: r-base rggobi/s390x
  • Implicit dependency: r-base rgl
  • Implicit dependency: r-base rglpk/amd64
  • Implicit dependency: r-base rglpk/arm64
  • Implicit dependency: r-base rglpk/armel
  • Implicit dependency: r-base rglpk/armhf
  • Implicit dependency: r-base rglpk/i386
  • Implicit dependency: r-base rglpk/mips64el
  • Implicit dependency: r-base rglpk/mipsel
  • Implicit dependency: r-base rglpk/ppc64el
  • Implicit dependency: r-base rglpk/s390x
  • Implicit dependency: r-base rgtk2/amd64
  • Implicit dependency: r-base rgtk2/arm64
  • Implicit dependency: r-base rgtk2/armel
  • Implicit dependency: r-base rgtk2/armhf
  • Implicit dependency: r-base rgtk2/i386
  • Implicit dependency: r-base rgtk2/mips64el
  • Implicit dependency: r-base rgtk2/mipsel
  • Implicit dependency: r-base rgtk2/ppc64el
  • Implicit dependency: r-base rgtk2/s390x
  • Implicit dependency: r-base rjava/amd64
  • Implicit dependency: r-base rjava/arm64
  • Implicit dependency: r-base rjava/armel
  • Implicit dependency: r-base rjava/armhf
  • Implicit dependency: r-base rjava/i386
  • Implicit dependency: r-base rjava/mips64el
  • Implicit dependency: r-base rjava/mipsel
  • Implicit dependency: r-base rjava/ppc64el
  • Implicit dependency: r-base rjava/s390x
  • Implicit dependency: r-base rkward
  • Implicit dependency: r-base rmatrix/amd64
  • Implicit dependency: r-base rmatrix/arm64
  • Implicit dependency: r-base rmatrix/armel
  • Implicit dependency: r-base rmatrix/armhf
  • Implicit dependency: r-base rmatrix/i386
  • Implicit dependency: r-base rmatrix/mips64el
  • Implicit dependency: r-base rmatrix/mipsel
  • Implicit dependency: r-base rmatrix/ppc64el
  • Implicit dependency: r-base rmatrix/s390x
  • Implicit dependency: r-base rmpi/amd64
  • Implicit dependency: r-base rmpi/arm64
  • Implicit dependency: r-base rmpi/armel
  • Implicit dependency: r-base rmpi/armhf
  • Implicit dependency: r-base rmpi/i386
  • Implicit dependency: r-base rmpi/mips64el
  • Implicit dependency: r-base rmpi/mipsel
  • Implicit dependency: r-base rmpi/ppc64el
  • Implicit dependency: r-base rmpi/s390x
  • Implicit dependency: r-base rmysql/amd64
  • Implicit dependency: r-base rmysql/arm64
  • Implicit dependency: r-base rmysql/armel
  • Implicit dependency: r-base rmysql/armhf
  • Implicit dependency: r-base rmysql/i386
  • Implicit dependency: r-base rmysql/mips64el
  • Implicit dependency: r-base rmysql/mipsel
  • Implicit dependency: r-base rmysql/ppc64el
  • Implicit dependency: r-base rmysql/s390x
  • Implicit dependency: r-base robustbase/amd64
  • Implicit dependency: r-base robustbase/arm64
  • Implicit dependency: r-base robustbase/armel
  • Implicit dependency: r-base robustbase/armhf
  • Implicit dependency: r-base robustbase/i386
  • Implicit dependency: r-base robustbase/mips64el
  • Implicit dependency: r-base robustbase/mipsel
  • Implicit dependency: r-base robustbase/ppc64el
  • Implicit dependency: r-base robustbase/s390x
  • Implicit dependency: r-base rodbc
  • Implicit dependency: r-base rpart/amd64
  • Implicit dependency: r-base rpart/arm64
  • Implicit dependency: r-base rpart/armel
  • Implicit dependency: r-base rpart/armhf
  • Implicit dependency: r-base rpart/i386
  • Implicit dependency: r-base rpart/mips64el
  • Implicit dependency: r-base rpart/mipsel
  • Implicit dependency: r-base rpart/ppc64el
  • Implicit dependency: r-base rpart/s390x
  • Implicit dependency: r-base rquantlib/amd64
  • Implicit dependency: r-base rquantlib/arm64
  • Implicit dependency: r-base rquantlib/armel
  • Implicit dependency: r-base rquantlib/armhf
  • Implicit dependency: r-base rquantlib/i386
  • Implicit dependency: r-base rquantlib/mips64el
  • Implicit dependency: r-base rquantlib/mipsel
  • Implicit dependency: r-base rquantlib/ppc64el
  • Implicit dependency: r-base rquantlib/s390x
  • Implicit dependency: r-base rserve/amd64
  • Implicit dependency: r-base rserve/arm64
  • Implicit dependency: r-base rserve/armel
  • Implicit dependency: r-base rserve/armhf
  • Implicit dependency: r-base rserve/i386
  • Implicit dependency: r-base rserve/mips64el
  • Implicit dependency: r-base rserve/mipsel
  • Implicit dependency: r-base rserve/ppc64el
  • Implicit dependency: r-base rserve/s390x
  • Implicit dependency: r-base rsprng/amd64
  • Implicit dependency: r-base rsprng/arm64
  • Implicit dependency: r-base rsprng/armel
  • Implicit dependency: r-base rsprng/armhf
  • Implicit dependency: r-base rsprng/i386
  • Implicit dependency: r-base rsprng/mips64el
  • Implicit dependency: r-base rsprng/mipsel
  • Implicit dependency: r-base rsprng/ppc64el
  • Implicit dependency: r-base rsprng/s390x
  • Implicit dependency: r-base rsymphony/amd64
  • Implicit dependency: r-base rsymphony/arm64
  • Implicit dependency: r-base rsymphony/armel
  • Implicit dependency: r-base rsymphony/armhf
  • Implicit dependency: r-base rsymphony/i386
  • Implicit dependency: r-base rsymphony/mips64el
  • Implicit dependency: r-base rsymphony/mipsel
  • Implicit dependency: r-base rsymphony/ppc64el
  • Implicit dependency: r-base rsymphony/s390x
  • Implicit dependency: r-base sandwich
  • Implicit dependency: r-base sm/amd64
  • Implicit dependency: r-base sm/arm64
  • Implicit dependency: r-base sm/armel
  • Implicit dependency: r-base sm/armhf
  • Implicit dependency: r-base sm/i386
  • Implicit dependency: r-base sm/mips64el
  • Implicit dependency: r-base sm/mipsel
  • Implicit dependency: r-base sm/ppc64el
  • Implicit dependency: r-base sm/s390x
  • Implicit dependency: r-base snow
  • Implicit dependency: r-base strucchange/amd64
  • Implicit dependency: r-base strucchange/arm64
  • Implicit dependency: r-base strucchange/armel
  • Implicit dependency: r-base strucchange/armhf
  • Implicit dependency: r-base strucchange/i386
  • Implicit dependency: r-base strucchange/mips64el
  • Implicit dependency: r-base strucchange/mipsel
  • Implicit dependency: r-base strucchange/ppc64el
  • Implicit dependency: r-base strucchange/s390x
  • Implicit dependency: r-base survival/amd64
  • Implicit dependency: r-base survival/arm64
  • Implicit dependency: r-base survival/armel
  • Implicit dependency: r-base survival/armhf
  • Implicit dependency: r-base survival/i386
  • Implicit dependency: r-base survival/mips64el
  • Implicit dependency: r-base survival/mipsel
  • Implicit dependency: r-base survival/ppc64el
  • Implicit dependency: r-base survival/s390x
  • Implicit dependency: r-base tkrplot/amd64
  • Implicit dependency: r-base tkrplot/arm64
  • Implicit dependency: r-base tkrplot/armel
  • Implicit dependency: r-base tkrplot/armhf
  • Implicit dependency: r-base tkrplot/i386
  • Implicit dependency: r-base tkrplot/mips64el
  • Implicit dependency: r-base tkrplot/mipsel
  • Implicit dependency: r-base tkrplot/ppc64el
  • Implicit dependency: r-base tkrplot/s390x
  • Implicit dependency: r-base tseries/amd64
  • Implicit dependency: r-base tseries/arm64
  • Implicit dependency: r-base tseries/armel
  • Implicit dependency: r-base tseries/armhf
  • Implicit dependency: r-base tseries/i386
  • Implicit dependency: r-base tseries/mips64el
  • Implicit dependency: r-base tseries/mipsel
  • Implicit dependency: r-base tseries/ppc64el
  • Implicit dependency: r-base tseries/s390x
  • Implicit dependency: r-base urca/amd64
  • Implicit dependency: r-base urca/arm64
  • Implicit dependency: r-base urca/armel
  • Implicit dependency: r-base urca/armhf
  • Implicit dependency: r-base urca/i386
  • Implicit dependency: r-base urca/mips64el
  • Implicit dependency: r-base urca/mipsel
  • Implicit dependency: r-base urca/ppc64el
  • Implicit dependency: r-base urca/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-base.html
  • 15 days old (needed 5 days)
• ruby-pgplot (0.1.9-3 to 0.2.0-1)
  • Migration status for ruby-pgplot (0.1.9-3 to 0.2.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on i386
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 15 days old (needed 5 days)
• node-katex (- to 0.8.3+dfsg-2)
  • Migration status for node-katex (- to 0.8.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating node-katex introduces new bugs: #901382
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-katex.html
  • Required age reduced by 3 days because of autopkgtest
  • 16 days old (needed 2 days)
• paramiko (2.6.0-2 to 2.7.1-1)
  • Migration status for paramiko (2.6.0-2 to 2.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating paramiko introduces new bugs: #960899
  • autopkgtest for paramiko/2.7.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paramiko.html
  • 16 days old (needed 5 days)
• php-horde-css-parser (- to 1.0.11-6)
  • Migration status for php-horde-css-parser (- to 1.0.11-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-css-parser/1.0.11-6: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-css-parser.html
  • 16 days old (needed 5 days)
• php-horde-date (- to 2.4.1-5)
  • Migration status for php-horde-date (- to 2.4.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-date/2.4.1-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-date php-horde-exception
  • Depends: php-horde-date php-horde-nls
  • Depends: php-horde-date php-horde-translation
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-date.html
  • 16 days old (needed 5 days)
• php-horde-db (- to 2.4.0-5)
  • Migration status for php-horde-db (- to 2.4.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-db/2.4.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-db php-horde-date
  • Depends: php-horde-db php-horde-exception
  • Depends: php-horde-db php-horde-support
  • Depends: php-horde-db php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-db.html
  • 16 days old (needed 5 days)
• php-horde-exception (- to 2.0.8-6)
  • Migration status for php-horde-exception (- to 2.0.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-exception/2.0.8-6: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-exception php-horde-translation
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-exception.html
  • 16 days old (needed 5 days)
• php-horde-group (- to 2.1.1-6)
  • Migration status for php-horde-group (- to 2.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-group/2.1.1-6: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-group php-horde-exception
  • Depends: php-horde-group php-horde-support
  • Depends: php-horde-group php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-group.html
  • 16 days old (needed 5 days)
• php-horde-history (- to 2.3.6-7)
  • Migration status for php-horde-history (- to 2.3.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-history/2.3.6-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-history php-horde-db
  • Depends: php-horde-history php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-history.html
  • 16 days old (needed 5 days)
• php-horde-icalendar (- to 2.1.8-3)
  • Migration status for php-horde-icalendar (- to 2.1.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-icalendar/2.1.8-3: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-icalendar php-horde-date
  • Depends: php-horde-icalendar php-horde-exception
  • Depends: php-horde-icalendar php-horde-mail
  • Depends: php-horde-icalendar php-horde-support
  • Depends: php-horde-icalendar php-horde-translation
  • Depends: php-horde-icalendar php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-icalendar.html
  • 16 days old (needed 5 days)
• php-horde-idna (- to 1.1.1-5)
  • Migration status for php-horde-idna (- to 1.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-idna php-horde-exception
  • Depends: php-horde-idna php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-idna.html
  • 16 days old (needed 5 days)
• php-horde-injector (- to 2.0.5-8)
  • Migration status for php-horde-injector (- to 2.0.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-injector/2.0.5-8: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-injector php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-injector.html
  • 16 days old (needed 5 days)
• php-horde-javascriptminify (- to 1.1.5-5)
  • Migration status for php-horde-javascriptminify (- to 1.1.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-javascriptminify php-horde-exception
  • Depends: php-horde-javascriptminify php-horde-log
  • Depends: php-horde-javascriptminify php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-javascriptminify.html
  • 16 days old (needed 5 days)
• php-horde-lock (- to 2.1.4-5)
  • Migration status for php-horde-lock (- to 2.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-lock/2.1.4-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-lock php-horde-exception
  • Depends: php-horde-lock php-horde-support
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-lock.html
  • 16 days old (needed 5 days)
• php-horde-log (- to 2.3.0-5)
  • Migration status for php-horde-log (- to 2.3.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-log/2.3.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-log php-horde-constraint
  • Depends: php-horde-log php-horde-exception
  • Depends: php-horde-log php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-log.html
  • 16 days old (needed 5 days)
• php-horde-logintasks (- to 2.0.7-6)
  • Migration status for php-horde-logintasks (- to 2.0.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-logintasks/2.0.7-6: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-logintasks php-horde-translation
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-logintasks.html
  • 16 days old (needed 5 days)
• php-horde-mail (- to 2.6.5-3)
  • Migration status for php-horde-mail (- to 2.6.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-mail/2.6.5-3: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-mail php-horde-exception
  • Depends: php-horde-mail php-horde-idna
  • Depends: php-horde-mail php-horde-stream-filter
  • Depends: php-horde-mail php-horde-translation
  • Depends: php-horde-mail php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mail.html
  • 16 days old (needed 5 days)
• php-horde-nls (- to 2.2.1-5)
  • Migration status for php-horde-nls (- to 2.2.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-nls php-horde-translation
  • Depends: php-horde-nls php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-nls.html
  • 16 days old (needed 5 days)
• php-horde-notification (- to 2.0.4-7)
  • Migration status for php-horde-notification (- to 2.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-notification/2.0.4-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-notification php-horde-exception
  • Depends: php-horde-notification php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-notification.html
  • 16 days old (needed 5 days)
• php-horde-perms (- to 2.1.8-2)
  • Migration status for php-horde-perms (- to 2.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-perms/2.1.8-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-perms php-horde-db
  • Depends: php-horde-perms php-horde-exception
  • Depends: php-horde-perms php-horde-group
  • Depends: php-horde-perms php-horde-translation
  • Depends: php-horde-perms php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-perms.html
  • 16 days old (needed 5 days)
• php-horde-prefs (- to 2.9.0-5)
  • Migration status for php-horde-prefs (- to 2.9.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-prefs/2.9.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-prefs php-horde-exception
  • Depends: php-horde-prefs php-horde-mail
  • Depends: php-horde-prefs php-horde-mime
  • Depends: php-horde-prefs php-horde-translation
  • Depends: php-horde-prefs php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-prefs.html
  • 16 days old (needed 5 days)
• php-horde-role (- to 1.0.1-16)
  • Migration status for php-horde-role (- to 1.0.1-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-role.html
  • 16 days old (needed 5 days)
• php-horde-secret (- to 2.0.6-7)
  • Migration status for php-horde-secret (- to 2.0.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-secret/2.0.6-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-secret php-horde-crypt-blowfish
  • Depends: php-horde-secret php-horde-exception
  • Depends: php-horde-secret php-horde-support
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-secret.html
  • 16 days old (needed 5 days)
• php-horde-serialize (- to 2.0.5-7)
  • Migration status for php-horde-serialize (- to 2.0.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-serialize/2.0.5-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-serialize php-horde-exception
  • Depends: php-horde-serialize php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-serialize.html
  • 16 days old (needed 5 days)
• php-horde-sessionhandler (- to 2.2.9-5)
  • Migration status for php-horde-sessionhandler (- to 2.2.9-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-sessionhandler/2.2.9-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-sessionhandler php-horde-exception
  • Depends: php-horde-sessionhandler php-horde-support
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-sessionhandler.html
  • 16 days old (needed 5 days)
• php-horde-share (- to 2.2.0-5)
  • Migration status for php-horde-share (- to 2.2.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-share/2.2.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-share php-horde-db
  • Depends: php-horde-share php-horde-exception
  • Depends: php-horde-share php-horde-group
  • Depends: php-horde-share php-horde-perms
  • Depends: php-horde-share php-horde-support
  • Depends: php-horde-share php-horde-translation
  • Depends: php-horde-share php-horde-url
  • Depends: php-horde-share php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-share.html
  • 16 days old (needed 5 days)
• php-horde-stream (- to 1.6.3-7)
  • Migration status for php-horde-stream (- to 1.6.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-stream/1.6.3-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-stream php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-stream.html
  • 16 days old (needed 5 days)
• php-horde-stream-filter (- to 2.0.4-7)
  • Migration status for php-horde-stream-filter (- to 2.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-stream-filter/2.0.4-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-stream-filter.html
  • 16 days old (needed 5 days)
• php-horde-stream-wrapper (- to 2.1.4-4)
  • Migration status for php-horde-stream-wrapper (- to 2.1.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-stream-wrapper/2.1.4-4: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-stream-wrapper.html
  • 16 days old (needed 5 days)
• php-horde-support (- to 2.2.0-5)
  • Migration status for php-horde-support (- to 2.2.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-support/2.2.0-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-support php-horde-exception
  • Depends: php-horde-support php-horde-stream-wrapper
  • Depends: php-horde-support php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-support.html
  • 16 days old (needed 5 days)
• php-horde-text-filter (- to 2.3.6-4)
  • Migration status for php-horde-text-filter (- to 2.3.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-text-filter/2.3.6-4: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-text-filter php-horde-exception
  • Depends: php-horde-text-filter php-horde-idna
  • Depends: php-horde-text-filter php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-text-filter.html
  • 16 days old (needed 5 days)
• php-horde-text-flowed (- to 2.0.3-8)
  • Migration status for php-horde-text-flowed (- to 2.0.3-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-text-flowed/2.0.3-8: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-text-flowed php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-text-flowed.html
  • 16 days old (needed 5 days)
• php-horde-token (- to 2.0.9-6)
  • Migration status for php-horde-token (- to 2.0.9-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-token/2.0.9-6: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-token php-horde-exception
  • Depends: php-horde-token php-horde-translation
  • Depends: php-horde-token php-horde-url
  • Depends: php-horde-token php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-token.html
  • 16 days old (needed 5 days)
• php-horde-translation (- to 2.2.2-5)
  • Migration status for php-horde-translation (- to 2.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-translation/2.2.2-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-translation.html
  • 16 days old (needed 5 days)
• php-horde-url (- to 2.2.6-5)
  • Migration status for php-horde-url (- to 2.2.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-url/2.2.6-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-url php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-url.html
  • 16 days old (needed 5 days)
• php-horde-util (- to 2.5.8-5)
  • Migration status for php-horde-util (- to 2.5.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-util/2.5.8-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-util.html
  • 16 days old (needed 5 days)
• php-horde-view (- to 2.0.6-7)
  • Migration status for php-horde-view (- to 2.0.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-view/2.0.6-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-view php-horde-exception
  • Depends: php-horde-view php-horde-support
  • Depends: php-horde-view php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-view.html
  • 16 days old (needed 5 days)
• python-cobra (0.14.2-2 to 0.18.0-3)
  • Migration status for python-cobra (0.14.2-2 to 0.18.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-cobra introduces new bugs: #958538, #961224
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cobra.html
  • Required age reduced by 3 days because of autopkgtest
  • 16 days old (needed 2 days)
• daq (2.0.4-3 to 2.0.7-2)
  • Migration status for daq (2.0.4-3 to 2.0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating daq introduces new bugs: #960479
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/daq.html
  • 17 days old (needed 5 days)
• gopass (1.2.0-2 to 1.3.0-1)
  • Migration status for gopass (1.2.0-2 to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • gopass/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gopass.html
  • Required age reduced by 3 days because of autopkgtest
  • 17 days old (needed 2 days)
• instead (- to 3.3.2-1)
  • Migration status for instead (- to 3.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by gq
  • Not built on buildd: arch all binaries uploaded by gq, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/instead.html
  • 17 days old (needed 10 days)
• libsolv (- to 0.7.11-1)
  • Migration status for libsolv (- to 0.7.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libsolv introduces new bugs: #960347
  • Not built on buildd: arch amd64 binaries uploaded by mike.gabriel@das-netzwerkteam.de
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsolv.html
  • 17 days old (needed 5 days)
• loggerhead (- to 1.19~bzr498-1)
  • Migration status for loggerhead (- to 1.19~bzr498-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: loggerhead yui3 (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/loggerhead.html
  • Required age reduced by 3 days because of autopkgtest
  • 17 days old (needed 2 days)
• mrbayes (3.2.6+dfsg-2 to 3.2.7a-2)
  • Migration status for mrbayes (3.2.6+dfsg-2 to 3.2.7a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mrbayes introduces new bugs: #958125
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrbayes.html
  • Required age reduced by 3 days because of autopkgtest
  • 17 days old (needed 2 days)
• php-defaults (69 to 76)
  • Migration status for php-defaults (69 to 76): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-defaults.html
  • autopkgtest for php7.3/7.3.15-3: amd64: Ignored failure, arm64: Ignored failure
  • 17 days old (needed 5 days)
• php-horde-alarm (- to 2.2.10-5)
  • Migration status for php-horde-alarm (- to 2.2.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-alarm/2.2.10-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-alarm php-horde-date
  • Depends: php-horde-alarm php-horde-exception
  • Depends: php-horde-alarm php-horde-translation
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-alarm.html
  • 17 days old (needed 5 days)
• php-horde-auth (- to 2.2.2-5)
  • Migration status for php-horde-auth (- to 2.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-auth/2.2.2-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-auth php-horde-exception
  • Depends: php-horde-auth php-horde-translation
  • Depends: php-horde-auth php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-auth.html
  • 17 days old (needed 5 days)
• php-horde-autoloader (- to 2.1.2-7)
  • Migration status for php-horde-autoloader (- to 2.1.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-autoloader/2.1.2-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-autoloader.html
  • 17 days old (needed 5 days)
• php-horde-browser (- to 2.0.16-2)
  • Migration status for php-horde-browser (- to 2.0.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-browser php-horde-exception
  • Depends: php-horde-browser php-horde-translation
  • Depends: php-horde-browser php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-browser.html
  • 17 days old (needed 5 days)
• php-horde-cache (- to 2.5.5-5)
  • Migration status for php-horde-cache (- to 2.5.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-cache php-horde-compress-fast
  • Depends: php-horde-cache php-horde-exception
  • Depends: php-horde-cache php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-cache.html
  • 17 days old (needed 5 days)
• php-horde-cli (- to 2.3.0-4)
  • Migration status for php-horde-cli (- to 2.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-cli php-horde-support
  • Depends: php-horde-cli php-horde-translation
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-cli.html
  • 17 days old (needed 5 days)
• php-horde-compress (- to 2.2.2-2)
  • Migration status for php-horde-compress (- to 2.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-compress/2.2.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-compress php-horde-exception
  • Depends: php-horde-compress php-horde-mime
  • Depends: php-horde-compress php-horde-translation
  • Depends: php-horde-compress php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-compress.html
  • 17 days old (needed 5 days)
• php-horde-compress-fast (- to 1.1.1-7)
  • Migration status for php-horde-compress-fast (- to 1.1.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-compress-fast/1.1.1-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-compress-fast php-horde-exception
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-compress-fast.html
  • 17 days old (needed 5 days)
• php-horde-constraint (- to 2.0.3-7)
  • Migration status for php-horde-constraint (- to 2.0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-constraint/2.0.3-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-constraint.html
  • 17 days old (needed 5 days)
• php-horde-controller (- to 2.0.5-3)
  • Migration status for php-horde-controller (- to 2.0.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-controller/2.0.5-3: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-controller php-horde-exception
  • Depends: php-horde-controller php-horde-injector
  • Depends: php-horde-controller php-horde-log
  • Depends: php-horde-controller php-horde-support
  • Depends: php-horde-controller php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-controller.html
  • 17 days old (needed 5 days)
• php-horde-crypt-blowfish (- to 1.1.2-5)
  • Migration status for php-horde-crypt-blowfish (- to 1.1.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for php-horde-crypt-blowfish/1.1.2-5: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-crypt-blowfish php-horde-exception
  • Depends: php-horde-crypt-blowfish php-horde-support
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-crypt-blowfish.html
  • 17 days old (needed 5 days)
• php-horde-cssminify (- to 1.0.4-5)
  • Migration status for php-horde-cssminify (- to 1.0.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-cssminify php-horde-css-parser
  • Depends: php-horde-cssminify php-horde-exception
  • Depends: php-horde-cssminify php-horde-log
  • Depends: php-horde-cssminify php-horde-url
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-cssminify.html
  • 17 days old (needed 5 days)
• php-horde-data (- to 2.1.4-7)
  • Migration status for php-horde-data (- to 2.1.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-horde-data introduces new bugs: #951537
  • autopkgtest for php-horde-data/2.1.4-7: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Depends: php-horde-data php-horde-browser
  • Depends: php-horde-data php-horde-exception
  • Depends: php-horde-data php-horde-icalendar
  • Depends: php-horde-data php-horde-mail
  • Depends: php-horde-data php-horde-mime
  • Depends: php-horde-data php-horde-translation
  • Depends: php-horde-data php-horde-util
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-data.html
  • 17 days old (needed 5 days)
• prads (0.3.3-1 to 0.3.3-1.1)
  • Migration status for prads (0.3.3-1 to 0.3.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating prads introduces new bugs: #960768
  • 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
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prads.html
  • 17 days old (needed 5 days)
• rust-base64 (0.11.0-1 to 0.12.1-1)
  • Migration status for rust-base64 (0.11.0-1 to 0.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • migrating librust-base64-dev/0.12.1-1/amd64 to testing makes librust-pem-dev/0.7.0-1/amd64 uninstallable
  • migrating librust-base64-dev/0.12.1-1/amd64 to testing makes librust-plist-dev/0.5.4-1/amd64 uninstallable
  • migrating librust-base64-dev/0.12.1-1/amd64 to testing makes librust-ron-dev/0.5.1-2/amd64 uninstallable
  • migrating librust-base64-dev/0.12.1-1/amd64 to testing makes librust-sequoia-openpgp-dev/0.16.0-3/amd64 uninstallable
  • migrating librust-base64-dev/0.12.1-1/arm64 to testing makes librust-pem-dev/0.7.0-1/arm64 uninstallable
  • migrating librust-base64-dev/0.12.1-1/arm64 to testing makes librust-plist-dev/0.5.4-1/arm64 uninstallable
  • migrating librust-base64-dev/0.12.1-1/arm64 to testing makes librust-ron-dev/0.5.1-2/arm64 uninstallable
  • migrating librust-base64-dev/0.12.1-1/arm64 to testing makes librust-sequoia-openpgp-dev/0.16.0-3/arm64 uninstallable
  • migrating librust-base64-dev/0.12.1-1/armel to testing makes librust-pem-dev/0.7.0-1/armel uninstallable
  • migrating librust-base64-dev/0.12.1-1/armel to testing makes librust-plist-dev/0.5.4-1/armel uninstallable
  • migrating librust-base64-dev/0.12.1-1/armel to testing makes librust-ron-dev/0.5.1-2/armel uninstallable
  • migrating librust-base64-dev/0.12.1-1/armel to testing makes librust-sequoia-openpgp-dev/0.16.0-3/armel uninstallable
  • migrating librust-base64-dev/0.12.1-1/armhf to testing makes librust-pem-dev/0.7.0-1/armhf uninstallable
  • migrating librust-base64-dev/0.12.1-1/armhf to testing makes librust-plist-dev/0.5.4-1/armhf uninstallable
  • migrating librust-base64-dev/0.12.1-1/armhf to testing makes librust-ron-dev/0.5.1-2/armhf uninstallable
  • migrating librust-base64-dev/0.12.1-1/armhf to testing makes librust-sequoia-openpgp-dev/0.16.0-3/armhf uninstallable
  • migrating librust-base64-dev/0.12.1-1/i386 to testing makes librust-pem-dev/0.7.0-1/i386 uninstallable
  • migrating librust-base64-dev/0.12.1-1/i386 to testing makes librust-plist-dev/0.5.4-1/i386 uninstallable
  • migrating librust-base64-dev/0.12.1-1/i386 to testing makes librust-ron-dev/0.5.1-2/i386 uninstallable
  • migrating librust-base64-dev/0.12.1-1/i386 to testing makes librust-sequoia-openpgp-dev/0.16.0-3/i386 uninstallable
  • migrating librust-base64-dev/0.12.1-1/mips64el to testing makes librust-pem-dev/0.7.0-1/mips64el uninstallable
  • migrating librust-base64-dev/0.12.1-1/mips64el to testing makes librust-plist-dev/0.5.4-1/mips64el uninstallable
  • migrating librust-base64-dev/0.12.1-1/mips64el to testing makes librust-ron-dev/0.5.1-2/mips64el uninstallable
  • migrating librust-base64-dev/0.12.1-1/mips64el to testing makes librust-sequoia-openpgp-dev/0.16.0-3/mips64el uninstallable
  • migrating librust-base64-dev/0.12.1-1/mipsel to testing makes librust-pem-dev/0.7.0-1/mipsel uninstallable
  • migrating librust-base64-dev/0.12.1-1/mipsel to testing makes librust-plist-dev/0.5.4-1/mipsel uninstallable
  • migrating librust-base64-dev/0.12.1-1/mipsel to testing makes librust-ron-dev/0.5.1-2/mipsel uninstallable
  • migrating librust-base64-dev/0.12.1-1/mipsel to testing makes librust-sequoia-openpgp-dev/0.16.0-3/mipsel uninstallable
  • migrating librust-base64-dev/0.12.1-1/ppc64el to testing makes librust-pem-dev/0.7.0-1/ppc64el uninstallable
  • migrating librust-base64-dev/0.12.1-1/ppc64el to testing makes librust-plist-dev/0.5.4-1/ppc64el uninstallable
  • migrating librust-base64-dev/0.12.1-1/ppc64el to testing makes librust-ron-dev/0.5.1-2/ppc64el uninstallable
  • migrating librust-base64-dev/0.12.1-1/ppc64el to testing makes librust-sequoia-openpgp-dev/0.16.0-3/ppc64el uninstallable
  • migrating librust-base64-dev/0.12.1-1/s390x to testing makes librust-pem-dev/0.7.0-1/s390x uninstallable
  • migrating librust-base64-dev/0.12.1-1/s390x to testing makes librust-plist-dev/0.5.4-1/s390x uninstallable
  • migrating librust-base64-dev/0.12.1-1/s390x to testing makes librust-ron-dev/0.5.1-2/s390x uninstallable
  • migrating librust-base64-dev/0.12.1-1/s390x to testing makes librust-sequoia-openpgp-dev/0.16.0-3/s390x uninstallable
  • Implicit dependency: rust-base64 rust-grep-printer
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-base64.html
  • 17 days old (needed 5 days)
• rust-grep (0.2.5-1 to 0.2.6-1)
  • Migration status for rust-grep (0.2.5-1 to 0.2.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-grep rust-grep-printer (not considered)
  • Depends: rust-grep rust-grep-printer (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-grep.html
  • Required age reduced by 3 days because of autopkgtest
  • 17 days old (needed 2 days)
• rust-grep-printer (0.1.4-1 to 0.1.5-1)
  • Migration status for rust-grep-printer (0.1.4-1 to 0.1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-grep-printer rust-base64 (not considered)
  • Depends: rust-grep-printer rust-base64 (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-grep-printer.html
  • Required age reduced by 3 days because of autopkgtest
  • 17 days old (needed 2 days)
• rust-ripgrep (12.0.1-1 to 12.1.0-1)
  • Migration status for rust-ripgrep (12.0.1-1 to 12.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-ripgrep rust-grep (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ripgrep.html
  • 17 days old (needed 5 days)
• android-platform-art (8.1.0+r23-3 to 8.1.0+r23-4)
  • Migration status for android-platform-art (8.1.0+r23-3 to 8.1.0+r23-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on arm64
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-art.html
  • 18 days old (needed 5 days)
• kazoo (2.6.1-6 to 2.7.0-2)
  • Migration status for kazoo (2.6.1-6 to 2.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kazoo introduces new bugs: #960965
  • autopkgtest for kazoo/2.7.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kazoo.html
  • 18 days old (needed 5 days)
• neutron-fwaas (1:15.0.1-1 to 1:16.0.0~rc1-2)
  • Migration status for neutron-fwaas (1:15.0.1-1 to 1:16.0.0~rc1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/n/neutron-fwaas.html
  • Additional info:
  • 18 days old (needed 5 days)
• taffybar (- to 3.0.0-3)
  • Migration status for taffybar (- to 3.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: taffybar haskell-gi-pango (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): taffybar haskell-gtk-strut
  • Build-Depends-Indep: taffybar haskell-gtk-strut
  • Depends: taffybar haskell-gi-gdk
  • Depends: taffybar haskell-gi-gdkx11
  • Depends: taffybar haskell-gi-gtk
  • Depends: taffybar haskell-gi-gtk-hs
  • Depends: taffybar haskell-gtk-sni-tray
  • Depends: taffybar haskell-gtk-strut
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taffybar.html
  • 18 days old (needed 5 days)
• astroidmail (- to 0.15-3.1)
  • Migration status for astroidmail (- to 0.15-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for astroidmail/0.15-3.1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astroidmail.html
  • 19 days old (needed 5 days)
• criu (- to 3.14-1)
  • Migration status for criu (- to 3.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating criu introduces new bugs: #796536
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/criu.html
  • 19 days old (needed 5 days)
• eclipse-jdt-ui (4.12-1 to 4.15-1)
  • Migration status for eclipse-jdt-ui (4.12-1 to 4.15-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): eclipse-jdt-ui eclipse-platform-text (not considered)
  • Depends: eclipse-jdt-ui eclipse-platform-text (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-jdt-ui.html
  • 20 days old (needed 5 days)
• eclipse-platform-debug (4.12-1 to 4.15-1)
  • Migration status for eclipse-platform-debug (4.12-1 to 4.15-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): eclipse-platform-debug eclipse-platform-text (not considered)
  • Depends: eclipse-platform-debug eclipse-platform-text (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-platform-debug.html
  • 20 days old (needed 5 days)
• eclipse-platform-text (4.12-1 to 4.15-1)
  • Migration status for eclipse-platform-text (4.12-1 to 4.15-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): eclipse-platform-text eclipse-platform-ui (not considered)
  • Depends: eclipse-platform-text eclipse-platform-ui (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-platform-text.html
  • 20 days old (needed 5 days)
• python-ceilometermiddleware (1.5.0-3 to 2.0.0-2)
  • Migration status for python-ceilometermiddleware (1.5.0-3 to 2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-ceilometermiddleware introduces new bugs: #955080
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ceilometermiddleware.html
  • 20 days old (needed 5 days)
• runescape (- to 0.8-1)
  • Migration status for runescape (- to 0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating runescape introduces new bugs: #953487
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • Required age reduced by 3 days because of autopkgtest
  • 20 days old (needed 2 days)
• swt4-gtk (4.13.0-1 to 4.15.0-1)
  • Migration status for swt4-gtk (4.13.0-1 to 4.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating swt4-gtk introduces new bugs: #960769
  • 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/swt4-gtk.html
  • 20 days old (needed 5 days)
• beads (1.1.18+dfsg-4 to 1.1.20-1)
  • Migration status for beads (1.1.18+dfsg-4 to 1.1.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by lopippo
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • Depends: beads libodsstream
  • Additional info:
  • Updating beads fixes old bugs: #959637
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beads.html
  • 21 days old (needed 10 days)
• connectagram (1.2.10-1 to 1.2.11-1)
  • Migration status for connectagram (1.2.10-1 to 1.2.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by jonathan@bluemosh.com
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/connectagram.html
  • 21 days old (needed 5 days)
• eclipse-platform-ui (4.12-1 to 4.15-1)
  • Migration status for eclipse-platform-ui (4.12-1 to 4.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-platform-ui.html
  • 21 days old (needed 5 days)
• fastqc (0.11.9+dfsg-3 to 0.11.9+dfsg-4)
  • Migration status for fastqc (0.11.9+dfsg-3 to 0.11.9+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): fastqc libsis-jhdf5-java (not considered)
  • Depends: fastqc libsis-jhdf5-java (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fastqc.html
  • Required age reduced by 3 days because of autopkgtest
  • 21 days old (needed 2 days)
• libsis-jhdf5-java (- to 19.04.0+dfsg-1)
  • Migration status for libsis-jhdf5-java (- to 19.04.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libsis-jhdf5-java introduces new bugs: #959955
  • autopkgtest for libsis-jhdf5-java/19.04.0+dfsg-1: amd64: Regression ♻ , arm64: Pass
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsis-jhdf5-java.html
  • 21 days old (needed 5 days)
• ncbi-entrez-direct (12.0.20190816+ds-1 to 12.0.20190816+ds-2)
  • Migration status for ncbi-entrez-direct (12.0.20190816+ds-1 to 12.0.20190816+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ncbi-entrez-direct/mips64el has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • missing build on mips64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncbi-entrez-direct.html
  • Required age reduced by 3 days because of autopkgtest
  • 21 days old (needed 2 days)
• numpy (1:1.17.4-5 to 1:1.18.4-1)
  • Migration status for numpy (1:1.17.4-5 to 1:1.18.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for dolfin/2019.2.0~git20200218.027d9cc-6: amd64: Pass, arm64: Ignored failure
  • autopkgtest for nipy/0.4.2-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Updating numpy fixes old bugs: #948354
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numpy.html
  • 21 days old (needed 5 days)
• simgrid (3.25+dfsg-2 to 3.25+dfsg-3)
  • Migration status for simgrid (3.25+dfsg-2 to 3.25+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • simgrid unsatisfiable Build-Depends(-Arch) on s390x: libunwind-dev
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simgrid.html
  • 21 days old (needed 5 days)
• docker-systemctl-replacement (1.4.4147-1 to 1.4.4181-1)
  • Migration status for docker-systemctl-replacement (1.4.4147-1 to 1.4.4181-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating docker-systemctl-replacement introduces new bugs: #959828
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docker-systemctl-replacement.html
  • 22 days old (needed 5 days)
• hurd (- to 1:0.9.git20200416-3)
  • Migration status for hurd (- to 1:0.9.git20200416-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~)
  • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-disk-dev
  • Not built on buildd: arch all binaries uploaded by sthibault, a new source-only upload is needed to allow migration
  • Not touching package due to block request by freeze (please contact debian-release if update is needed)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hurd.html
  • 22 days old (needed 5 days)
• libodsstream (0.7.0-3 to 0.7.8-2)
  • Migration status for libodsstream (0.7.0-3 to 0.7.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libodsstream introduces new bugs: #959539
  • Not built on buildd: arch amd64 binaries uploaded by lopippo
  • Not built on buildd: arch all binaries uploaded by lopippo, a new source-only upload is needed to allow migration
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libo/libodsstream.html
  • 22 days old (needed 10 days)
• m2crypto (0.31.0-9 to 0.35.2-2)
  • Migration status for m2crypto (0.31.0-9 to 0.35.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating m2crypto introduces new bugs: #959947
  • Not built on buildd: arch all binaries uploaded by morph, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by morph
  • Additional info:
  • Updating m2crypto fixes old bugs: #954462, #958496
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/m2crypto.html
  • Required age reduced by 3 days because of autopkgtest
  • 22 days old (needed 2 days)
• nss (2:3.49.1-1 to 2:3.52-1)
  • Migration status for nss (2:3.49.1-1 to 2:3.52-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on mips64el
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nss.html
  • 22 days old (needed 5 days)
• cb2bib (1.9.9-1 to 2.0.0-1)
  • Migration status for cb2bib (1.9.9-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by lopippo
  • missing build on mips64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cb2bib.html
  • 23 days old (needed 10 days)
• geary (3.36.1-1 to 3.36.2-1)
  • Migration status for geary (3.36.1-1 to 3.36.2-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
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geary.html
  • 23 days old (needed 5 days)
• rust-rand-chacha (0.2.1-1 to 0.2.2-1)
  • Migration status for rust-rand-chacha (0.2.1-1 to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rust-rand-chacha unsatisfiable Build-Depends(-Arch) on s390x: librust-ppv-lite86-0.2+simd-dev (>= 0.2.6-~~)
  • rust-rand-chacha unsatisfiable Build-Depends(-Arch) on s390x: librust-ppv-lite86-0.2+std-dev (>= 0.2.6-~~)
  • missing build on s390x
  • Build-Depends(-Arch): rust-rand-chacha rust-ppv-lite86
  • Depends: rust-rand-chacha rust-ppv-lite86
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rand-chacha.html
  • Required age reduced by 3 days because of autopkgtest
  • 23 days old (needed 2 days)
• fscrypt (0.2.5-2 to 0.2.7-1)
  • Migration status for fscrypt (0.2.5-2 to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fscrypt introduces new bugs: #959531
  • fscrypt/armel has unsatisfiable Built-Using on golang-1.13 1.13.4-1
  • libpam-fscrypt/armel has unsatisfiable Built-Using on golang-1.13 1.13.4-1
  • fscrypt/armhf has unsatisfiable Built-Using on golang-1.13 1.13.4-1
  • libpam-fscrypt/armhf has unsatisfiable Built-Using on golang-1.13 1.13.4-1
  • fscrypt/i386 has unsatisfiable Built-Using on golang-1.13 1.13.4-1
  • libpam-fscrypt/i386 has unsatisfiable Built-Using on golang-1.13 1.13.4-1
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fscrypt.html
  • Required age reduced by 3 days because of autopkgtest
  • 24 days old (needed 2 days)
• haskell-http-types (0.12.3-2 to 0.12.3-3)
  • Migration status for haskell-http-types (0.12.3-2 to 0.12.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by picca
  • Not built on buildd: arch all binaries uploaded by picca, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-http-types.html
  • 24 days old (needed 5 days)
• hslogger (1.2.12-1 to 1.2.12+dfsg-1)
  • Migration status for hslogger (1.2.12-1 to 1.2.12+dfsg-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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hslogger.html
  • 24 days old (needed 5 days)
• nbdkit (1.18.3-1 to 1.18.4-1)
  • Migration status for nbdkit (1.18.3-1 to 1.18.4-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbdkit.html
  • 24 days old (needed 5 days)
• rust-ppv-lite86 (0.2.5-2 to 0.2.6-1)
  • Migration status for rust-ppv-lite86 (0.2.5-2 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-ppv-lite86 introduces new bugs: #961335
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ppv-lite86.html
  • Required age reduced by 3 days because of autopkgtest
  • 24 days old (needed 2 days)
• sec (2.8.2-1.1 to 2.8.3-1)
  • Migration status for sec (2.8.2-1.1 to 2.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by liiwi, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sec.html
  • 25 days old (needed 5 days)
• diamond-aligner (0.9.30-3 to 0.9.32-2)
  • Migration status for diamond-aligner (0.9.30-3 to 0.9.32-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating diamond-aligner introduces new bugs: #958090, #959374
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diamond-aligner.html
  • Required age reduced by 3 days because of autopkgtest
  • 27 days old (needed 2 days)
• localslackirc (1.7-1 to 1.9-2)
  • Migration status for localslackirc (1.7-1 to 1.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by tiposchi@tiscali.it, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/localslackirc.html
  • 27 days old (needed 2 days)
• libdevel-declare-perl (0.006019-1 to 0.006022-1)
  • Migration status for libdevel-declare-perl (0.006019-1 to 0.006022-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libperl5i-perl/2.13.2-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdevel-declare-perl.html
  • 28 days old (needed 5 days)
• quickfix (1.15.1+dfsg-3 to 1.15.1+dfsg-4)
  • Migration status for quickfix (1.15.1+dfsg-3 to 1.15.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickfix.html
  • 28 days old (needed 5 days)
• dolfinx (- to 2019.2.0~git20200420.6043d6d-5)
  • Migration status for dolfinx (- to 2019.2.0~git20200420.6043d6d-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dolfinx introduces new bugs: #961569
  • autopkgtest for dolfinx/2019.2.0~git20200420.6043d6d-5: amd64: Pass, arm64: Regression ♻
  • Build-Depends(-Arch): dolfinx numba
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolfinx.html
  • 29 days old (needed 5 days)
• openhft-chronicle-network (- to 1.0.58-2)
  • Migration status for openhft-chronicle-network (- to 1.0.58-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): openhft-chronicle-network openhft-chronicle-wire (not considered)
  • Depends: openhft-chronicle-network openhft-chronicle-wire (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: openhft-chronicle-network openhft-chronicle-bytes
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openhft-chronicle-network.html
  • 29 days old (needed 5 days)
• edict (2019.02.20-1 to 2020.04.28-1)
  • Migration status for edict (2019.02.20-1 to 2020.04.28-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ldrolez, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/edict.html
  • 30 days old (needed 5 days)
• gnucobol (2.2-5 to 3.0~rc1-1)
  • Migration status for gnucobol (2.2-5 to 3.0~rc1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ahs3
  • Not built on buildd: arch all binaries uploaded by ahs3, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnucobol.html
  • 30 days old (needed 5 days)
• mdp (3.5-1.1 to 3.6-1)
  • Migration status for mdp (3.5-1.1 to 3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdp.html
  • 30 days old (needed 5 days)
• printrun (- to 2.0.0~rc5-1.1)
  • Migration status for printrun (- to 2.0.0~rc5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating printrun introduces new bugs: #939658
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/printrun.html
  • Required age reduced by 3 days because of autopkgtest
  • 30 days old (needed 2 days)
• sbcl (2:2.0.3-1 to 2:2.0.4-1)
  • Migration status for sbcl (2:2.0.3-1 to 2:2.0.4-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on arm64
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbcl.html
  • 30 days old (needed 5 days)
• xrdesktop (- to 0.14.1-2)
  • Migration status for xrdesktop (- to 0.14.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): xrdesktop gxr (not considered)
  • Depends: xrdesktop gxr (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: xrdesktop gulkan
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrdesktop.html
  • 30 days old (needed 5 days)
• python-molotov (- to 1.6-7)
  • Migration status for python-molotov (- to 1.6-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): python-molotov uvloop (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-molotov.html
  • Required age reduced by 3 days because of autopkgtest
  • 31 days old (needed 2 days)
• golang-github-emersion-go-imap (- to 1.0.4-2)
  • Migration status for golang-github-emersion-go-imap (- to 1.0.4-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
  • Build-Depends(-Arch): golang-github-emersion-go-imap golang-github-martinlindhe-base36
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-emersion-go-imap.html
  • 33 days old (needed 5 days)
• golang-github-emersion-go-imap-idle (- to 0.0~git20190519.2704abd-2)
  • Migration status for golang-github-emersion-go-imap-idle (- to 0.0~git20190519.2704abd-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): golang-github-emersion-go-imap-idle golang-github-emersion-go-imap (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-emersion-go-imap-idle.html
  • Required age reduced by 3 days because of autopkgtest
  • 33 days old (needed 2 days)
• jinja2 (2.10.1-2 to 2.11.1-1)
  • Migration status for jinja2 (2.10.1-2 to 2.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for oca-core/11.0.20180730-1: amd64: Regression ♻ , arm64: Regression ♻
  • migrating python3-jinja2/2.11.1-1/amd64 to testing makes glue-sprite/0.13-3/amd64 uninstallable
  • migrating python3-jinja2/2.11.1-1/i386 to testing makes glue-sprite/0.13-3/i386 uninstallable
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jinja2.html
  • 33 days old (needed 5 days)
• golang-github-emersion-go-message (- to 0.10.7-1)
  • Migration status for golang-github-emersion-go-message (- to 0.10.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): golang-github-emersion-go-message golang-github-martinlindhe-base36
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-emersion-go-message.html
  • Required age reduced by 3 days because of autopkgtest
  • 34 days old (needed 2 days)
• gxr (0.13.2-2 to 0.14.0-4)
  • Migration status for gxr (0.13.2-2 to 0.14.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gxr introduces new bugs: #959608
  • Build-Depends(-Arch): gxr gulkan
  • Depends: gxr gulkan
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gxr.html
  • 34 days old (needed 5 days)
• khard (0.15.1-1 to 0.16.1-2)
  • Migration status for khard (0.15.1-1 to 0.16.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): khard sphinx-autoapi (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khard.html
  • 34 days old (needed 5 days)
• libpath-tiny-perl (0.108-1 to 0.112-1)
  • Migration status for libpath-tiny-perl (0.108-1 to 0.112-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpath-tiny-perl.html
  • Required age reduced by 3 days because of autopkgtest
  • 34 days old (needed 2 days)
• qbittorrent (4.1.7-1 to 4.2.4-1)
  • Migration status for qbittorrent (4.1.7-1 to 4.2.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: qbittorrent libtorrent-rasterbar (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qbittorrent.html
  • 34 days old (needed 5 days)
• rust-num (- to 0.2.0-1)
  • Migration status for rust-num (- to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-num rust-num-rational (not considered)
  • Depends: rust-num rust-num-rational (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: rust-num rust-num-bigint
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num.html
  • Required age reduced by 3 days because of autopkgtest
  • 34 days old (needed 2 days)
• ensmallen (2.12.0-1 to 2.12.1-1)
  • Migration status for ensmallen (2.12.0-1 to 2.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ensmallen introduces new bugs: #961203
  • missing build on armel
  • missing build on armhf
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ensmallen.html
  • 35 days old (needed 5 days)
• golang-github-zenhack-go.notmuch (- to 0.0~git20190821.5a19619-1)
  • Migration status for golang-github-zenhack-go.notmuch (- to 0.0~git20190821.5a19619-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-zenhack-go.notmuch.html
  • Required age reduced by 3 days because of autopkgtest
  • 35 days old (needed 2 days)
• jhdf (- to 2.11.0+dfsg-4)
  • Migration status for jhdf (- to 2.11.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jhdf introduces new bugs: #853750
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jhdf.html
  • 35 days old (needed 5 days)
• libtorrent-rasterbar (1.1.13-1.1 to 1.2.5-1)
  • Migration status for libtorrent-rasterbar (1.1.13-1.1 to 1.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libtorrent-rasterbar introduces new bugs: #956285, #958958
  • Not built on buildd: arch all binaries uploaded by a.starr.b@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtorrent-rasterbar.html
  • 35 days old (needed 5 days)
• sphinx-autoapi (- to 1.3.0-1)
  • Migration status for sphinx-autoapi (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-autoapi.html
  • 35 days old (needed 5 days)
• urwid (2.0.1-3 to 2.1.0-1)
  • Migration status for urwid (2.0.1-3 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating urwid introduces new bugs: #959619
  • 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/u/urwid.html
  • 35 days old (needed 5 days)
• fenics (1:2019.1.0.3 to 1:2019.2.0.2)
  • Migration status for fenics (1:2019.1.0.3 to 1:2019.2.0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: fenics dolfinx (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenics.html
  • Required age reduced by 3 days because of autopkgtest
  • 36 days old (needed 2 days)
• mathicgb (- to 1.0~git20181123-1)
  • Migration status for mathicgb (- to 1.0~git20181123-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for mathicgb/1.0~git20181123-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathicgb.html
  • 36 days old (needed 5 days)
• rust-curl-sys (- to 0.4.30-2)
  • Migration status for rust-curl-sys (- to 0.4.30-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-curl-sys/0.4.30-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-curl-sys.html
  • 36 days old (needed 5 days)
• rust-derive-builder (- to 0.9.0-2)
  • Migration status for rust-derive-builder (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-derive-builder+compiletest-rs-dev/amd64 has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/amd64 has unsatisfiable dependency
  • librust-derive-builder+logging-dev/amd64 has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/amd64 has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/amd64 has unsatisfiable dependency
  • librust-derive-builder+compiletest-rs-dev/arm64 has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/arm64 has unsatisfiable dependency
  • librust-derive-builder+logging-dev/arm64 has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/arm64 has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/arm64 has unsatisfiable dependency
  • librust-derive-builder+compiletest-rs-dev/armel has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/armel has unsatisfiable dependency
  • librust-derive-builder+logging-dev/armel has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/armel has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/armel has unsatisfiable dependency
  • librust-derive-builder+compiletest-rs-dev/armhf has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/armhf has unsatisfiable dependency
  • librust-derive-builder+logging-dev/armhf has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/armhf has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/armhf has unsatisfiable dependency
  • librust-derive-builder+compiletest-rs-dev/i386 has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/i386 has unsatisfiable dependency
  • librust-derive-builder+logging-dev/i386 has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/i386 has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/i386 has unsatisfiable dependency
  • librust-derive-builder+compiletest-rs-dev/mips64el has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/mips64el has unsatisfiable dependency
  • librust-derive-builder+logging-dev/mips64el has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/mips64el has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/mips64el has unsatisfiable dependency
  • librust-derive-builder+compiletest-rs-dev/mipsel has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/mipsel has unsatisfiable dependency
  • librust-derive-builder+logging-dev/mipsel has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/mipsel has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/mipsel has unsatisfiable dependency
  • librust-derive-builder+compiletest-rs-dev/ppc64el has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/ppc64el has unsatisfiable dependency
  • librust-derive-builder+logging-dev/ppc64el has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/ppc64el has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/ppc64el has unsatisfiable dependency
  • librust-derive-builder+compiletest-rs-dev/s390x has unsatisfiable dependency
  • librust-derive-builder+env-logger-dev/s390x has unsatisfiable dependency
  • librust-derive-builder+logging-dev/s390x has unsatisfiable dependency
  • librust-derive-builder+skeptic-dev/s390x has unsatisfiable dependency
  • librust-derive-builder+skeptic-tests-dev/s390x has unsatisfiable dependency
  • Updating rust-derive-builder introduces new bugs: #959907
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-derive-builder.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 36 days old (needed 5 days)
• rust-gstreamer (- to 0.14.5-2)
  • Migration status for rust-gstreamer (- to 0.14.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-gstreamer+futures-dev/amd64 has unsatisfiable dependency
  • librust-gstreamer+paste-dev/amd64 has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/amd64 has unsatisfiable dependency
  • librust-gstreamer+futures-dev/arm64 has unsatisfiable dependency
  • librust-gstreamer+paste-dev/arm64 has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/arm64 has unsatisfiable dependency
  • librust-gstreamer+futures-dev/armel has unsatisfiable dependency
  • librust-gstreamer+paste-dev/armel has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/armel has unsatisfiable dependency
  • librust-gstreamer+futures-dev/armhf has unsatisfiable dependency
  • librust-gstreamer+paste-dev/armhf has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/armhf has unsatisfiable dependency
  • librust-gstreamer+futures-dev/i386 has unsatisfiable dependency
  • librust-gstreamer+paste-dev/i386 has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/i386 has unsatisfiable dependency
  • librust-gstreamer+futures-dev/mips64el has unsatisfiable dependency
  • librust-gstreamer+paste-dev/mips64el has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/mips64el has unsatisfiable dependency
  • librust-gstreamer+futures-dev/mipsel has unsatisfiable dependency
  • librust-gstreamer+paste-dev/mipsel has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/mipsel has unsatisfiable dependency
  • librust-gstreamer+futures-dev/ppc64el has unsatisfiable dependency
  • librust-gstreamer+paste-dev/ppc64el has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/ppc64el has unsatisfiable dependency
  • librust-gstreamer+futures-dev/s390x has unsatisfiable dependency
  • librust-gstreamer+paste-dev/s390x has unsatisfiable dependency
  • librust-gstreamer+subclassing-dev/s390x has unsatisfiable dependency
  • Build-Depends(-Arch): rust-gstreamer rust-num-rational
  • Depends: rust-gstreamer rust-num-rational
  • Depends: rust-gstreamer rust-serde-bytes
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gstreamer.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 36 days old (needed 5 days)
• rust-gstreamer-audio (- to 0.14.5-2)
  • Migration status for rust-gstreamer-audio (- to 0.14.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-gstreamer-audio rust-gstreamer (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-gstreamer-audio rust-gstreamer-base
  • Depends: rust-gstreamer-audio rust-gstreamer-base
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gstreamer-audio.html
  • 36 days old (needed 5 days)
• rust-gstreamer-base (- to 0.14.4-2)
  • Migration status for rust-gstreamer-base (- to 0.14.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-gstreamer-base rust-gstreamer (not considered)
  • Depends: rust-gstreamer-base rust-gstreamer (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gstreamer-base.html
  • 36 days old (needed 5 days)
• rust-gstreamer-video (- to 0.14.5-2)
  • Migration status for rust-gstreamer-video (- to 0.14.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-gstreamer-video rust-gstreamer (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-gstreamer-video rust-gstreamer-base
  • Depends: rust-gstreamer-video rust-gstreamer-base
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gstreamer-video.html
  • 36 days old (needed 5 days)
• rust-image (- to 0.22.1-2)
  • Migration status for rust-image (- to 0.22.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-image.html
  • arch:amd64 not built yet, autopkgtest delayed there
  • Build-Depends(-Arch): rust-image rust-tiff
  • Additional info:
  • 36 days old (needed 5 days)
• rust-librespot-protocol (- to 0.1.0-2)
  • Migration status for rust-librespot-protocol (- to 0.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-librespot-protocol rust-protobuf (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-librespot-protocol rust-protobuf-codegen-pure
  • Depends: rust-librespot-protocol rust-protobuf-codegen
  • Depends: rust-librespot-protocol rust-protobuf-codegen-pure
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-librespot-protocol.html
  • Required age reduced by 3 days because of autopkgtest
  • 36 days old (needed 2 days)
• rust-libsodium-sys (- to 0.2.5-2)
  • Migration status for rust-libsodium-sys (- to 0.2.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-libsodium-sys/0.2.5-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libsodium-sys.html
  • 36 days old (needed 5 days)
• rust-num-bigint (- to 0.2.6-1)
  • Migration status for rust-num-bigint (- to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-num-bigint+quickcheck-macros-dev/amd64 has unsatisfiable dependency
  • librust-num-bigint+quickcheck-macros-dev/arm64 has unsatisfiable dependency
  • librust-num-bigint+quickcheck-macros-dev/armel has unsatisfiable dependency
  • librust-num-bigint+quickcheck-macros-dev/armhf has unsatisfiable dependency
  • librust-num-bigint+quickcheck-macros-dev/i386 has unsatisfiable dependency
  • librust-num-bigint+quickcheck-macros-dev/mips64el has unsatisfiable dependency
  • librust-num-bigint+quickcheck-macros-dev/mipsel has unsatisfiable dependency
  • librust-num-bigint+quickcheck-macros-dev/ppc64el has unsatisfiable dependency
  • librust-num-bigint+quickcheck-macros-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-num-bigint.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 36 days old (needed 5 days)
• rust-protobuf (- to 2.8.1-2)
  • Migration status for rust-protobuf (- to 2.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-protobuf/2.8.1-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-protobuf.html
  • 36 days old (needed 5 days)
• rust-protobuf-codegen (- to 2.8.1-2)
  • Migration status for rust-protobuf-codegen (- to 2.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-protobuf-codegen rust-protobuf (not considered)
  • Depends: rust-protobuf-codegen rust-protobuf (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-protobuf-codegen.html
  • Required age reduced by 3 days because of autopkgtest
  • 36 days old (needed 2 days)
• rust-protobuf-codegen-pure (- to 2.8.1-2)
  • Migration status for rust-protobuf-codegen-pure (- to 2.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-protobuf-codegen-pure rust-protobuf (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-protobuf-codegen-pure rust-protobuf-codegen
  • Depends: rust-protobuf-codegen-pure rust-protobuf-codegen
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-protobuf-codegen-pure.html
  • Required age reduced by 3 days because of autopkgtest
  • 36 days old (needed 2 days)
• rust-simplelog (- to 0.7.4-2)
  • Migration status for rust-simplelog (- to 0.7.4-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-simplelog.html
  • 36 days old (needed 5 days)
• rust-tui (- to 0.8.0-2)
  • Migration status for rust-tui (- to 0.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-tui+crossterm-dev/amd64 has unsatisfiable dependency
  • librust-tui+curses-dev/amd64 has unsatisfiable dependency
  • librust-tui+easycurses-dev/amd64 has unsatisfiable dependency
  • librust-tui+pancurses-dev/amd64 has unsatisfiable dependency
  • librust-tui+rustbox-dev/amd64 has unsatisfiable dependency
  • librust-tui+crossterm-dev/arm64 has unsatisfiable dependency
  • librust-tui+curses-dev/arm64 has unsatisfiable dependency
  • librust-tui+easycurses-dev/arm64 has unsatisfiable dependency
  • librust-tui+pancurses-dev/arm64 has unsatisfiable dependency
  • librust-tui+rustbox-dev/arm64 has unsatisfiable dependency
  • librust-tui+crossterm-dev/armel has unsatisfiable dependency
  • librust-tui+curses-dev/armel has unsatisfiable dependency
  • librust-tui+easycurses-dev/armel has unsatisfiable dependency
  • librust-tui+pancurses-dev/armel has unsatisfiable dependency
  • librust-tui+rustbox-dev/armel has unsatisfiable dependency
  • librust-tui+crossterm-dev/armhf has unsatisfiable dependency
  • librust-tui+curses-dev/armhf has unsatisfiable dependency
  • librust-tui+easycurses-dev/armhf has unsatisfiable dependency
  • librust-tui+pancurses-dev/armhf has unsatisfiable dependency
  • librust-tui+rustbox-dev/armhf has unsatisfiable dependency
  • librust-tui+crossterm-dev/i386 has unsatisfiable dependency
  • librust-tui+curses-dev/i386 has unsatisfiable dependency
  • librust-tui+easycurses-dev/i386 has unsatisfiable dependency
  • librust-tui+pancurses-dev/i386 has unsatisfiable dependency
  • librust-tui+rustbox-dev/i386 has unsatisfiable dependency
  • librust-tui+crossterm-dev/mips64el has unsatisfiable dependency
  • librust-tui+curses-dev/mips64el has unsatisfiable dependency
  • librust-tui+easycurses-dev/mips64el has unsatisfiable dependency
  • librust-tui+pancurses-dev/mips64el has unsatisfiable dependency
  • librust-tui+rustbox-dev/mips64el has unsatisfiable dependency
  • librust-tui+crossterm-dev/mipsel has unsatisfiable dependency
  • librust-tui+curses-dev/mipsel has unsatisfiable dependency
  • librust-tui+easycurses-dev/mipsel has unsatisfiable dependency
  • librust-tui+pancurses-dev/mipsel has unsatisfiable dependency
  • librust-tui+rustbox-dev/mipsel has unsatisfiable dependency
  • librust-tui+crossterm-dev/ppc64el has unsatisfiable dependency
  • librust-tui+curses-dev/ppc64el has unsatisfiable dependency
  • librust-tui+easycurses-dev/ppc64el has unsatisfiable dependency
  • librust-tui+pancurses-dev/ppc64el has unsatisfiable dependency
  • librust-tui+rustbox-dev/ppc64el has unsatisfiable dependency
  • librust-tui+crossterm-dev/s390x has unsatisfiable dependency
  • librust-tui+curses-dev/s390x has unsatisfiable dependency
  • librust-tui+easycurses-dev/s390x has unsatisfiable dependency
  • librust-tui+pancurses-dev/s390x has unsatisfiable dependency
  • librust-tui+rustbox-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tui.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 36 days old (needed 5 days)
• rust-unicode-script (- to 0.3.0-2)
  • Migration status for rust-unicode-script (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-unicode-script+harfbuzz-dev/amd64 has unsatisfiable dependency
  • librust-unicode-script+harfbuzz-dev/arm64 has unsatisfiable dependency
  • librust-unicode-script+harfbuzz-dev/armel has unsatisfiable dependency
  • librust-unicode-script+harfbuzz-dev/armhf has unsatisfiable dependency
  • librust-unicode-script+harfbuzz-dev/i386 has unsatisfiable dependency
  • librust-unicode-script+harfbuzz-dev/mips64el has unsatisfiable dependency
  • librust-unicode-script+harfbuzz-dev/mipsel has unsatisfiable dependency
  • librust-unicode-script+harfbuzz-dev/ppc64el has unsatisfiable dependency
  • librust-unicode-script+harfbuzz-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-unicode-script.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 36 days old (needed 5 days)
• rust-xcb (- to 0.9.0-2)
  • Migration status for rust-xcb (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-xcb/0.9.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xcb.html
  • 36 days old (needed 5 days)
• gnome-shell-xrdesktop (- to 3.36.1-2)
  • Migration status for gnome-shell-xrdesktop (- to 3.36.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): gnome-shell-xrdesktop xrdesktop (not considered)
  • Depends: gnome-shell-xrdesktop xrdesktop (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: gnome-shell-xrdesktop gulkan
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-xrdesktop.html
  • 37 days old (needed 5 days)
• golang-github-martinlindhe-base36 (- to 1.0.0-1)
  • Migration status for golang-github-martinlindhe-base36 (- 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 praveen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-martinlindhe-base36.html
  • Required age reduced by 3 days because of autopkgtest
  • 37 days old (needed 2 days)
• kwin-effect-xrdesktop (- to 0.14.0-2)
  • Migration status for kwin-effect-xrdesktop (- to 0.14.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kwin-effect-xrdesktop gxr (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kwin-effect-xrdesktop xrdesktop
  • Depends: kwin-effect-xrdesktop gulkan
  • Depends: kwin-effect-xrdesktop xrdesktop
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwin-effect-xrdesktop.html
  • 37 days old (needed 5 days)
• python-django-health-check (- to 3.12.1-2)
  • Migration status for python-django-health-check (- to 3.12.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for python-django-health-check/3.12.1-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-health-check.html
  • 37 days old (needed 5 days)
• rust-lewton (- to 0.9.4-1)
  • Migration status for rust-lewton (- to 0.9.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-lewton-dev/amd64 has unsatisfiable dependency
  • rust-lewton unsatisfiable Build-Depends(-Arch) on amd64: librust-smallvec-0.6+default-dev
  • Not built on buildd: arch amd64 binaries uploaded by infinity0
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-lewton.html
  • uninstallable on arch amd64, not running autopkgtest there
  • 37 days old (needed 5 days)
• dnsmasq (2.80-1.1 to 2.81-3)
  • Migration status for dnsmasq (2.80-1.1 to 2.81-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by srk, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by srk
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnsmasq.html
  • 38 days old (needed 5 days)
• oci-image-tools (- to 1.0.0~rc2+really.rc1+dfsg-1)
  • Migration status for oci-image-tools (- to 1.0.0~rc2+really.rc1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for oci-image-tools/1.0.0~rc2+really.rc1+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by siretart
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oci-image-tools.html
  • 38 days old (needed 5 days)
• php-slim (- to 3.12.3-1)
  • Migration status for php-slim (- to 3.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): php-slim php-pimple
  • Depends: php-slim php-pimple
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-slim.html
  • Required age reduced by 3 days because of autopkgtest
  • 38 days old (needed 2 days)
• plyara (- to 2.0.3-3)
  • Migration status for plyara (- to 2.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by rhaist@mailbox.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plyara.html
  • 38 days old (needed 5 days)
• python-altair (- to 4.0.1-1)
  • Migration status for python-altair (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-altair unsatisfiable Build-Depends(-Arch) on amd64: python3-vega-datasets
  • Not built on buildd: arch all binaries uploaded by santiago, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-altair.html
  • 38 days old (needed 5 days)
• python-clickhouse-driver (- to 0.1.3-1)
  • Migration status for python-clickhouse-driver (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-clickhouse-driver.html
  • 38 days old (needed 5 days)
• rhc (- to 1.38.7-3)
  • Migration status for rhc (- to 1.38.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rhc introduces new bugs: #908295
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rhc.html
  • 38 days old (needed 5 days)
• rust-aes (- to 0.3.2-2)
  • Migration status for rust-aes (- to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-aes/0.3.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-aes.html
  • 38 days old (needed 5 days)
• rust-aes-ctr (- to 0.3.0-2)
  • Migration status for rust-aes-ctr (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-aes-ctr/0.3.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-aes-ctr.html
  • 38 days old (needed 5 days)
• rust-ammonia (- to 3.0.0-2)
  • Migration status for rust-ammonia (- to 3.0.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • arch:arm64 not built yet, autopkgtest delayed there
  • Build-Depends(-Arch): rust-ammonia rust-html5ever
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ammonia.html
  • 38 days old (needed 5 days)
• rust-barrel (- to 0.6.5-2)
  • Migration status for rust-barrel (- to 0.6.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-barrel rust-diesel (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-barrel.html
  • Required age reduced by 3 days because of autopkgtest
  • 38 days old (needed 2 days)
• rust-expat-sys (- to 2.1.6-2)
  • Migration status for rust-expat-sys (- to 2.1.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-expat-sys/2.1.6-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-expat-sys.html
  • 38 days old (needed 5 days)
• rust-migrations-macros (- to 1.4.1-2)
  • Migration status for rust-migrations-macros (- to 1.4.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-migrations-macros rust-migrations-internals (not considered)
  • Depends: rust-migrations-macros rust-migrations-internals (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-migrations-macros.html
  • 38 days old (needed 5 days)
• rust-pest-generator (- to 2.1.1-2)
  • Migration status for rust-pest-generator (- to 2.1.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-pest-generator rust-pest (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-pest-generator rust-pest-meta
  • Depends: rust-pest-generator rust-pest-meta
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pest-generator.html
  • Required age reduced by 3 days because of autopkgtest
  • 38 days old (needed 2 days)
• rust-sct (- to 0.6.0-2)
  • Migration status for rust-sct (- to 0.6.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-sct rust-ring (not considered)
  • Depends: rust-sct rust-ring (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sct.html
  • Required age reduced by 3 days because of autopkgtest
  • 38 days old (needed 2 days)
• rust-spotify-tui (- to 0.11.0-2)
  • Migration status for rust-spotify-tui (- to 0.11.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • arch:amd64 not built yet, autopkgtest delayed there
  • Build-Depends(-Arch): rust-spotify-tui rust-tui
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-spotify-tui.html
  • 38 days old (needed 5 days)
• rust-strip-ansi-escapes (- to 0.1.0-2)
  • Migration status for rust-strip-ansi-escapes (- to 0.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-strip-ansi-escapes rust-vte (not considered)
  • Depends: rust-strip-ansi-escapes rust-vte (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-strip-ansi-escapes.html
  • Required age reduced by 3 days because of autopkgtest
  • 38 days old (needed 2 days)
• rust-toml-edit (- to 0.1.5-2)
  • Migration status for rust-toml-edit (- to 0.1.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-toml-edit rust-combine (not considered)
  • Depends: rust-toml-edit rust-combine (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-toml-edit.html
  • Required age reduced by 3 days because of autopkgtest
  • 38 days old (needed 2 days)
• rust-webpki (- to 0.21.0-2)
  • Migration status for rust-webpki (- to 0.21.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-webpki rust-ring (not considered)
  • Depends: rust-webpki rust-ring (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-webpki.html
  • 38 days old (needed 5 days)
• xpra (3.0.7+dfsg1-1 to 3.0.9+dfsg1-1)
  • Migration status for xpra (3.0.7+dfsg1-1 to 3.0.9+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xpra introduces new bugs: #956822
  • missing build on armel
  • missing build on armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xpra.html
  • Required age reduced by 3 days because of autopkgtest
  • 38 days old (needed 2 days)
• cloop (- to 3.14.1.3)
  • Migration status for cloop (- to 3.14.1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cloop introduces new bugs: #916936
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cloop.html
  • 39 days old (needed 5 days)
• golang-github-emersion-go-smtp (- to 0.11.2-1)
  • Migration status for golang-github-emersion-go-smtp (- to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-emersion-go-smtp.html
  • Required age reduced by 3 days because of autopkgtest
  • 39 days old (needed 2 days)
• golang-github-jackpal-go-nat-pmp (- to 1.0.2-1)
  • Migration status for golang-github-jackpal-go-nat-pmp (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jackpal-go-nat-pmp.html
  • Required age reduced by 3 days because of autopkgtest
  • 39 days old (needed 2 days)
• golang-github-miolini-datacounter (- to 1.0.2-1)
  • Migration status for golang-github-miolini-datacounter (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-miolini-datacounter.html
  • Required age reduced by 3 days because of autopkgtest
  • 39 days old (needed 2 days)
• json-schema-test-suite (- to 2.0.0-1)
  • Migration status for json-schema-test-suite (- 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 guptautkarsh2102@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/json-schema-test-suite.html
  • 39 days old (needed 5 days)
• node-prosemirror-markdown (- to 1.4.4-1)
  • Migration status for node-prosemirror-markdown (- to 1.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • node-prosemirror-markdown/amd64 has unsatisfiable dependency
  • node-prosemirror-markdown/i386 has unsatisfiable dependency
  • node-prosemirror-markdown unsatisfiable Build-Depends(-Arch) on amd64: node-markdown-it
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/node-prosemirror-markdown.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 39 days old (needed 5 days)
• nohang (- to 0.1-1)
  • Migration status for nohang (- to 0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by 073plan@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nohang.html
  • 39 days old (needed 5 days)
• plakativ (- to 0.2-2)
  • Migration status for plakativ (- to 0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by josch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plakativ.html
  • 39 days old (needed 5 days)
• progress-linux-metapackages (- to 20190701-17)
  • Migration status for progress-linux-metapackages (- to 20190701-17): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/progress-linux-metapackages.html
  • 39 days old (needed 5 days)
• python-gitlab (1:2.1.2-1 to 1:2.2.0-1)
  • Migration status for python-gitlab (1:2.1.2-1 to 1:2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gitlab.html
  • 39 days old (needed 5 days)
• ruby-procto (- to 0.0.3-1)
  • Migration status for ruby-procto (- to 0.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by abhijith@openmailbox.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-procto.html
  • Required age reduced by 3 days because of autopkgtest
  • 39 days old (needed 2 days)
• rust-cargo (- to 0.43.1-1)
  • Migration status for rust-cargo (- to 0.43.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rust-cargo unsatisfiable Build-Depends(-Arch) on amd64: librust-im-rc-14+default-dev
  • rust-cargo unsatisfiable Build-Depends(-Arch) on arm64: librust-im-rc-14+default-dev
  • rust-cargo unsatisfiable Build-Depends(-Arch) on armel: librust-im-rc-14+default-dev
  • rust-cargo unsatisfiable Build-Depends(-Arch) on armhf: librust-im-rc-14+default-dev
  • rust-cargo unsatisfiable Build-Depends(-Arch) on i386: librust-im-rc-14+default-dev
  • rust-cargo unsatisfiable Build-Depends(-Arch) on mips64el: librust-im-rc-14+default-dev
  • rust-cargo unsatisfiable Build-Depends(-Arch) on mipsel: librust-im-rc-14+default-dev
  • rust-cargo unsatisfiable Build-Depends(-Arch) on ppc64el: librust-im-rc-14+default-dev
  • rust-cargo unsatisfiable Build-Depends(-Arch) on s390x: librust-im-rc-14+default-dev
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • arch:arm64 not built yet, autopkgtest delayed there
  • Build-Depends(-Arch): rust-cargo rust-strip-ansi-escapes
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo.html
  • 39 days old (needed 5 days)
• rust-cargo-outdated (- to 0.9.9-1)
  • Migration status for rust-cargo-outdated (- to 0.9.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rust-cargo-outdated unsatisfiable Build-Depends(-Arch) on amd64: librust-cargo-0.43+default-dev (>= 0.43.1-~~)
  • rust-cargo-outdated unsatisfiable Build-Depends(-Arch) on arm64: librust-cargo-0.43+default-dev (>= 0.43.1-~~)
  • rust-cargo-outdated unsatisfiable Build-Depends(-Arch) on armhf: librust-cargo-0.43+default-dev (>= 0.43.1-~~)
  • rust-cargo-outdated unsatisfiable Build-Depends(-Arch) on i386: librust-cargo-0.43+default-dev (>= 0.43.1-~~)
  • rust-cargo-outdated unsatisfiable Build-Depends(-Arch) on mips64el: librust-cargo-0.43+default-dev (>= 0.43.1-~~)
  • rust-cargo-outdated unsatisfiable Build-Depends(-Arch) on ppc64el: librust-cargo-0.43+default-dev (>= 0.43.1-~~)
  • rust-cargo-outdated unsatisfiable Build-Depends(-Arch) on s390x: librust-cargo-0.43+default-dev (>= 0.43.1-~~)
  • missing build on amd64
  • missing build on arm64
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • arch:arm64 not built yet, autopkgtest delayed there
  • Build-Depends(-Arch): rust-cargo-outdated rust-git2-curl
  • Built-Using: rust-cargo-outdated rust-im-rc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-outdated.html
  • 39 days old (needed 5 days)
• rust-crates-io (- to 0.31.0-1)
  • Migration status for rust-crates-io (- to 0.31.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-crates-io rust-curl (not considered)
  • Depends: rust-crates-io rust-curl (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-crates-io.html
  • Required age reduced by 3 days because of autopkgtest
  • 39 days old (needed 2 days)
• rust-debcargo (- to 2.4.3-1)
  • Migration status for rust-debcargo (- to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on amd64: librust-cargo-0.43+default-dev
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on arm64: librust-cargo-0.43+default-dev
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on armel: librust-cargo-0.43+default-dev
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on armhf: librust-cargo-0.43+default-dev
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on i386: librust-cargo-0.43+default-dev
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on mips64el: librust-cargo-0.43+default-dev
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on mipsel: librust-cargo-0.43+default-dev
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on ppc64el: librust-cargo-0.43+default-dev
  • rust-debcargo unsatisfiable Build-Depends(-Arch) on s390x: librust-cargo-0.43+default-dev
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • arch:arm64 not built yet, autopkgtest delayed there
  • Built-Using: rust-debcargo rust-im-rc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-debcargo.html
  • 39 days old (needed 5 days)
• rust-git2-curl (- to 0.12.0-1)
  • Migration status for rust-git2-curl (- to 0.12.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-git2-curl rust-curl (not considered)
  • Depends: rust-git2-curl rust-curl (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-git2-curl.html
  • 39 days old (needed 5 days)
• rust-pretty-assertions (- to 0.6.1-3)
  • Migration status for rust-pretty-assertions (- to 0.6.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-pretty-assertions rust-difference (not considered)
  • Depends: rust-pretty-assertions rust-difference (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pretty-assertions.html
  • Required age reduced by 3 days because of autopkgtest
  • 39 days old (needed 2 days)
• sugar-pippy-activity (- to 75-1)
  • Migration status for sugar-pippy-activity (- to 75-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: sugar-pippy-activity sugar (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sugar-pippy-activity.html
  • 39 days old (needed 5 days)
• pbsuite (- to 15.8.24+dfsg-5)
  • Migration status for pbsuite (- to 15.8.24+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • pbhoney/i386 has unsatisfiable dependency
  • pbjelly/i386 has unsatisfiable dependency
  • python3-pbbanana/i386 has unsatisfiable dependency
  • autopkgtest for pbsuite/15.8.24+dfsg-5: amd64: Regression ♻ , arm64: Regression ♻
  • Depends: pbsuite python-intervaltree-bio
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pbsuite.html
  • 40 days old (needed 5 days)
• pyode (- to 1.2.0.dev15-1)
  • Migration status for pyode (- to 1.2.0.dev15-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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyode.html
  • Required age reduced by 3 days because of autopkgtest
  • 40 days old (needed 2 days)
• snort (- to 2.9.15.1-2)
  • Migration status for snort (- to 2.9.15.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating snort introduces new bugs: #959858
  • snort unsatisfiable Build-Depends(-Arch) on s390x: libluajit-5.1-dev
  • missing build on i386
  • missing build on s390x
  • Depends: snort daq
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snort.html
  • 40 days old (needed 5 days)
• rgl (0.100.50-1 to 0.100.54-1)
  • Migration status for rgl (0.100.50-1 to 0.100.54-1): Will attempt migration (Any information below is purely informational)
  • Depends: rgl r-base
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rgl.html
  • 41 days old (needed 5 days)
• djangorestframework-api-key (- to 2.0.0-1)
  • Migration status for djangorestframework-api-key (- 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 guptautkarsh2102@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djangorestframework-api-key.html
  • 42 days old (needed 5 days)
• libpostscriptbarcode (- to 20200401-1)
  • Migration status for libpostscriptbarcode (- to 20200401-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alex, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpostscriptbarcode.html
  • 42 days old (needed 5 days)
• octave-mapping (1.2.1-5 to 1.4.0-1)
  • Migration status for octave-mapping (1.2.1-5 to 1.4.0-1): 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/o/octave-mapping.html
  • Required age reduced by 3 days because of autopkgtest
  • 42 days old (needed 2 days)
• openjdk-11 (11.0.7+9-1 to 11.0.7+10-3)
  • Migration status for openjdk-11 (11.0.7+9-1 to 11.0.7+10-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11.html
  • 42 days old (needed 5 days)
• openjdk-15 (- to 15~19-1)
  • Migration status for openjdk-15 (- to 15~19-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-15.html
  • 42 days old (needed 5 days)
• openjdk-8 (- to 8u252-b09-1)
  • Migration status for openjdk-8 (- to 8u252-b09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openjdk-8 introduces new bugs: #929650
  • missing build on armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-8.html
  • autopkgtest for openjdk-8/blacklisted: amd64: Ignored failure, arm64: Ignored failure
  • 42 days old (needed 5 days)
• roger-router (- to 2.1.6-4)
  • Migration status for roger-router (- to 2.1.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating roger-router introduces new bugs: #916178
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/roger-router.html
  • 42 days old (needed 5 days)
• frobtads (- to 1:1.2.4-1.1)
  • Migration status for frobtads (- to 1:1.2.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating frobtads introduces new bugs: #836934
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 44 days old (needed 5 days)
• open-build-service (- to 2.9.4-3)
  • Migration status for open-build-service (- to 2.9.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating open-build-service introduces new bugs: #924233
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/open-build-service.html
  • Build-Depends(-Arch): open-build-service libbssolv-perl
  • Depends: open-build-service libbssolv-perl
  • Additional info:
  • 44 days old (needed 5 days)
• rust-bat (- to 0.12.1-2)
  • Migration status for rust-bat (- to 0.12.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rust-bat unsatisfiable Build-Depends(-Arch) on amd64: librust-git2-0.10-dev
  • rust-bat unsatisfiable Build-Depends(-Arch) on arm64: librust-git2-0.10-dev
  • rust-bat unsatisfiable Build-Depends(-Arch) on armel: librust-git2-0.10-dev
  • rust-bat unsatisfiable Build-Depends(-Arch) on armhf: librust-git2-0.10-dev
  • rust-bat unsatisfiable Build-Depends(-Arch) on i386: librust-git2-0.10-dev
  • rust-bat unsatisfiable Build-Depends(-Arch) on mips64el: librust-git2-0.10-dev
  • rust-bat unsatisfiable Build-Depends(-Arch) on mipsel: librust-git2-0.10-dev
  • rust-bat unsatisfiable Build-Depends(-Arch) on ppc64el: librust-git2-0.10-dev
  • rust-bat unsatisfiable Build-Depends(-Arch) on s390x: librust-git2-0.10-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bat.html
  • 44 days old (needed 5 days)
• rust-curl (- to 0.4.25-2)
  • Migration status for rust-curl (- to 0.4.25-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-curl introduces new bugs: #946733
  • autopkgtest for rust-curl/0.4.25-2: amd64: Regression ♻ , arm64: Regression ♻
  • Build-Depends(-Arch): rust-curl rust-curl-sys
  • Depends: rust-curl rust-curl-sys
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-curl.html
  • 44 days old (needed 5 days)
• sibelia (- to 3.0.7+dfsg-3)
  • Migration status for sibelia (- to 3.0.7+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sibelia introduces new bugs: #959059
  • autopkgtest for sibelia/3.0.7+dfsg-3: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sibelia.html
  • 44 days old (needed 5 days)
• meep (- to 1.12.0-3)
  • Migration status for meep (- to 1.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating meep introduces new bugs: #940491
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meep.html
  • 45 days old (needed 5 days)
• rust-exa (- to 0.9.0-3)
  • Migration status for rust-exa (- to 0.9.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-exa rust-users (not considered)
  • Depends: rust-exa rust-users (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-exa.html
  • 45 days old (needed 5 days)
• kwartz-client (- to 1.5-1)
  • Migration status for kwartz-client (- to 1.5-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
  • Additional info:
  • 46 days old (needed 5 days)
• libkqueue (- to 2.3.1-1)
  • Migration status for libkqueue (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for libkqueue/2.3.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • missing build on ppc64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkqueue.html
  • 46 days old (needed 5 days)
• ruby-mustermann (1.0.0-4 to 1.1.1-1)
  • Migration status for ruby-mustermann (1.0.0-4 to 1.1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): ruby-mustermann ruby-ruby2-keywords (not considered)
  • Depends: ruby-mustermann ruby-ruby2-keywords (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-mustermann.html
  • 47 days old (needed 5 days)
• glslang (8.13.3559-3 to 8.13.3559+git3727-1)
  • Migration status for glslang (8.13.3559-3 to 8.13.3559+git3727-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): glslang spirv-tools (not considered)
  • Depends: glslang spirv-tools (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glslang.html
  • 48 days old (needed 5 days)
• monado (- to 0.1.0+git108.a8a4d8c3-2)
  • Migration status for monado (- to 0.1.0+git108.a8a4d8c3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): monado glslang (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monado.html
  • 48 days old (needed 5 days)
• nomad (- to 0.10.5+dfsg1-1)
  • Migration status for nomad (- to 0.10.5+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • nomad/armel has unsatisfiable Built-Using on golang-1.13 1.13.8-1
  • missing build on armel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomad.html
  • 48 days old (needed 5 days)
• vulkan-validationlayers (1.1.126.0-1 to 1.2.135.0-1)
  • Migration status for vulkan-validationlayers (1.1.126.0-1 to 1.2.135.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): vulkan-validationlayers spirv-tools (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vulkan-validationlayers.html
  • 48 days old (needed 5 days)
• xrayutilities (- to 1.6.0-2)
  • Migration status for xrayutilities (- to 1.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): xrayutilities lmfit-py (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrayutilities.html
  • 48 days old (needed 5 days)
• golang-github-alangpierce-go-forceexport (- to 0.0~git20160317.8f1d694-1)
  • Migration status for golang-github-alangpierce-go-forceexport (- to 0.0~git20160317.8f1d694-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alangpierce-go-forceexport.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• golang-github-fatih-set (- to 0.2.1-1)
  • Migration status for golang-github-fatih-set (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-fatih-set.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• golang-github-gigawattio-window (- to 0.0~git20180317.0f5467e-1)
  • Migration status for golang-github-gigawattio-window (- to 0.0~git20180317.0f5467e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gigawattio-window.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• golang-github-marten-seemann-qpack (- to 0.1.0-2)
  • Migration status for golang-github-marten-seemann-qpack (- to 0.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-marten-seemann-qpack.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• golang-github-marten-seemann-qtls (- to 0.8.0-1)
  • Migration status for golang-github-marten-seemann-qtls (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-marten-seemann-qtls.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• golang-github-mmcdole-goxpp (- to 0.0~git20181012.0068e33-1)
  • Migration status for golang-github-mmcdole-goxpp (- to 0.0~git20181012.0068e33-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-mmcdole-goxpp.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• golang-github-valyala-tcplisten (- to 0.0~git20161114.ceec8f9-1)
  • Migration status for golang-github-valyala-tcplisten (- to 0.0~git20161114.ceec8f9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-valyala-tcplisten.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• libgnatcoll-python (- to 19-3)
  • Migration status for libgnatcoll-python (- to 19-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libgnatcoll-python introduces new bugs: #936869
  • Not built on buildd: arch amd64 binaries uploaded by nicolas.boulenguez@free.fr
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgnatcoll-python.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• phpunit-code-unit (- to 1.0.0-1)
  • Migration status for phpunit-code-unit (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpunit-code-unit.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• platformio (- to 4.2.1-1)
  • Migration status for platformio (- to 4.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by paddatrapper, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/platformio.html
  • 49 days old (needed 5 days)
• pydle (- to 0.9.3-1)
  • Migration status for pydle (- to 0.9.3-1): 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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydle.html
  • 49 days old (needed 5 days)
• rnc2rng (- to 2.6.2-1)
  • Migration status for rnc2rng (- to 2.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rnc2rng.html
  • 49 days old (needed 5 days)
• ruby-ruby2-keywords (- to 0.0.2-1)
  • Migration status for ruby-ruby2-keywords (- to 0.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by terceiro, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ruby2-keywords.html
  • Required age reduced by 3 days because of autopkgtest
  • 49 days old (needed 2 days)
• shim-helpers-amd64-signed (1+15+1533136590.3beb971+7 to 1+15+1533136590.3beb971+9)
  • Migration status for shim-helpers-amd64-signed (1+15+1533136590.3beb971+7 to 1+15+1533136590.3beb971+9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): shim-helpers-amd64-signed shim (not considered)
  • Built-Using: shim-helpers-amd64-signed shim (not considered)
  • Depends: shim-helpers-amd64-signed shim (not considered)
  • Invalidated by build-dependency
  • Invalidated by built-using
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shim-helpers-amd64-signed.html
  • 49 days old (needed 5 days)
• shim-helpers-arm64-signed (1+15+1533136590.3beb971+7 to 1+15+1533136590.3beb971+9)
  • Migration status for shim-helpers-arm64-signed (1+15+1533136590.3beb971+7 to 1+15+1533136590.3beb971+9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): shim-helpers-arm64-signed shim (not considered)
  • Built-Using: shim-helpers-arm64-signed shim (not considered)
  • Depends: shim-helpers-arm64-signed shim (not considered)
  • Invalidated by build-dependency
  • Invalidated by built-using
  • Invalidated by dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 49 days old (needed 5 days)
• shim-helpers-i386-signed (1+15+1533136590.3beb971+7 to 1+15+1533136590.3beb971+9)
  • Migration status for shim-helpers-i386-signed (1+15+1533136590.3beb971+7 to 1+15+1533136590.3beb971+9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): shim-helpers-i386-signed shim (not considered)
  • Built-Using: shim-helpers-i386-signed shim (not considered)
  • Depends: shim-helpers-i386-signed shim (not considered)
  • Invalidated by build-dependency
  • Invalidated by built-using
  • Invalidated by dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 49 days old (needed 5 days)
• spirv-tools (2020.1-2 to 2020.2-1)
  • Migration status for spirv-tools (2020.1-2 to 2020.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating spirv-tools introduces new bugs: #956510
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-tools.html
  • 49 days old (needed 5 days)
• rally-openstack (- to 1.7.0-1)
  • Migration status for rally-openstack (- 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 zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rally-openstack.html
  • 50 days old (needed 5 days)
• scalene (- to 0.7.5-1)
  • Migration status for scalene (- to 0.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scalene.html
  • 50 days old (needed 5 days)
• citadel (- to 917-5)
  • Migration status for citadel (- to 917-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating citadel introduces new bugs: #939377
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/citadel.html
  • 51 days old (needed 5 days)
• freeipa (- to 4.8.6-1)
  • Migration status for freeipa (- to 4.8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for freeipa/4.8.6-1: amd64: Regression ♻ , arm64: Regression ♻
  • Build-Depends(-Arch): freeipa dogtag-pki
  • Depends: freeipa dogtag-pki
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freeipa.html
  • 51 days old (needed 5 days)
• psychtoolbox-3 (3.0.16.20200130.dfsg1-2 to 3.0.16.20200326.dfsg1-1)
  • Migration status for psychtoolbox-3 (3.0.16.20200130.dfsg1-2 to 3.0.16.20200326.dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by yoh
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psychtoolbox-3.html
  • 51 days old (needed 5 days)
• python-csa (- to 0.1.12-1)
  • Migration status for python-csa (- to 0.1.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-csa introduces new bugs: #952499
  • Not built on buildd: arch amd64 binaries uploaded by mdj
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-csa.html
  • 51 days old (needed 5 days)
• webcit (- to 917-dfsg-5)
  • Migration status for webcit (- to 917-dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: webcit citadel (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webcit.html
  • 51 days old (needed 5 days)
• pagure (- to 5.9.1+dfsg-1)
  • Migration status for pagure (- to 5.9.1+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): pagure jquery-at.js (not considered)
  • Depends: pagure jquery-at.js (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pagure.html
  • 52 days old (needed 5 days)
• python-loompy (- to 3.0.6+dfsg-2)
  • Migration status for python-loompy (- to 3.0.6+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: python-loompy numba (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): python-loompy python-numpy-groupies
  • Depends: python-loompy python-numpy-groupies
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-loompy.html
  • 52 days old (needed 5 days)
• dimmer-el (- to 0.4.2+repack-1)
  • Migration status for dimmer-el (- to 0.4.2+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by dogsleg, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dimmer-el.html
  • 53 days old (needed 5 days)
• esup-el (- to 0.7.1-1)
  • Migration status for esup-el (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by dogsleg, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esup-el.html
  • Required age reduced by 3 days because of autopkgtest
  • 53 days old (needed 2 days)
• rust-cargo-lock (- to 4.0.1-1)
  • Migration status for rust-cargo-lock (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-cargo-lock/4.0.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-lock.html
  • 53 days old (needed 5 days)
• wine-development (5.4-1 to 5.5-3)
  • Migration status for wine-development (5.4-1 to 5.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating wine-development introduces new bugs: #956028
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine-development.html
  • 53 days old (needed 5 days)
• aionotify (- to 0.2.0-1)
  • Migration status for aionotify (- 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 sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aionotify.html
  • 54 days old (needed 5 days)
• proteinortho (6.0.14+dfsg-1 to 6.0.15+dfsg-1)
  • Migration status for proteinortho (6.0.14+dfsg-1 to 6.0.15+dfsg-1): 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/p/proteinortho.html
  • Required age reduced by 3 days because of autopkgtest
  • 54 days old (needed 2 days)
• pynn (- to 0.9.5-2)
  • Migration status for pynn (- to 0.9.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pynn introduces new bugs: #959061
  • autopkgtest for pynn/0.9.5-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: upload info for arch all binaries not found, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynn.html
  • 54 days old (needed 5 days)
• wav2cdr (2.3.4-2 to 2.3.4-3)
  • Migration status for wav2cdr (2.3.4-2 to 2.3.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating wav2cdr introduces new bugs: #958578
  • autopkgtest for wav2cdr/2.3.4-3: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wav2cdr.html
  • 54 days old (needed 5 days)
• dar (2.6.8-2 to 2.6.9-1)
  • Migration status for dar (2.6.8-2 to 2.6.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Built-Using: dar gpgme1.0 (not considered)
  • Invalidated by built-using
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dar.html
  • 55 days old (needed 5 days)
• gulkan (0.13.2-2 to 0.14.0-2)
  • Migration status for gulkan (0.13.2-2 to 0.14.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): gulkan glslang (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gulkan.html
  • 55 days old (needed 5 days)
• isc-kea (- to 1.7.5-1)
  • Migration status for isc-kea (- to 1.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating isc-kea introduces new bugs: #959149
  • Not built on buildd: arch all binaries uploaded by ondrej, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by ondrej
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/isc-kea.html
  • 55 days old (needed 5 days)
• ruby-ahoy-email (- to 1.0.3-2)
  • Migration status for ruby-ahoy-email (- to 1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ruby-ahoy-email introduces new bugs: #959060
  • autopkgtest for ruby-ahoy-email/1.0.3-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ahoy-email.html
  • 55 days old (needed 5 days)
• xfce4-screensaver (- to 0.1.10-1)
  • Migration status for xfce4-screensaver (- to 0.1.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xfce4-screensaver introduces new bugs: #919348
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-screensaver.html
  • 55 days old (needed 5 days)
• acpica-unix (20190509-1 to 20200326-1)
  • Migration status for acpica-unix (20190509-1 to 20200326-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating acpica-unix introduces new bugs: #958491
  • 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
  • 56 days old (needed 5 days)
• golang-github-hashicorp-terraform-svchost (- to 0.0~git20191119.d2e4933-2)
  • Migration status for golang-github-hashicorp-terraform-svchost (- to 0.0~git20191119.d2e4933-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for golang-github-hashicorp-terraform-svchost/0.0~git20191119.d2e4933-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-terraform-svchost.html
  • 56 days old (needed 5 days)
• libcatmandu-mab2-perl (0.21-1 to 0.24-1)
  • Migration status for libcatmandu-mab2-perl (0.21-1 to 0.24-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: libcatmandu-mab2-perl libcatmandu-perl (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): libcatmandu-mab2-perl libcatmandu-sru-perl
  • Depends: libcatmandu-mab2-perl libcatmandu-sru-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcatmandu-mab2-perl.html
  • 56 days old (needed 5 days)
• libcatmandu-sru-perl (0.42.1-2 to 0.42.8-1)
  • Migration status for libcatmandu-sru-perl (0.42.1-2 to 0.42.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): libcatmandu-sru-perl libcatmandu-perl (not considered)
  • Depends: libcatmandu-sru-perl libcatmandu-perl (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcatmandu-sru-perl.html
  • Required age reduced by 3 days because of autopkgtest
  • 56 days old (needed 2 days)
• iptables-converter (- to 0.9.8-1.1)
  • Migration status for iptables-converter (- to 0.9.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating iptables-converter introduces new bugs: #956018
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iptables-converter.html
  • 57 days old (needed 5 days)
• shim (15+1533136590.3beb971-7 to 15+1533136590.3beb971-9)
  • Migration status for shim (15+1533136590.3beb971-7 to 15+1533136590.3beb971-9): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
  • Not touching package due to block request by ivodd (please contact debian-release if update is needed)
  • Implicit dependency: shim shim-helpers-amd64-signed
  • Implicit dependency: shim shim-helpers-arm64-signed
  • Implicit dependency: shim shim-helpers-i386-signed
  • Additional info:
  • Updating shim fixes old bugs: #925826
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shim.html
  • 58 days old (needed 5 days)
• dogtag-pki (- to 10.8.3-2)
  • Migration status for dogtag-pki (- to 10.8.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dogtag-pki introduces new bugs: #920725, #921926
  • Build-Depends(-Arch): dogtag-pki openjdk-8
  • Depends: dogtag-pki freeipa-healthcheck
  • Depends: dogtag-pki openjdk-8
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dogtag-pki.html
  • Required age reduced by 3 days because of autopkgtest
  • 59 days old (needed 2 days)
• radare2-cutter (- to 1.10.2-1)
  • Migration status for radare2-cutter (- to 1.10.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): radare2-cutter radare2 (not considered)
  • Depends: radare2-cutter radare2 (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radare2-cutter.html
  • 59 days old (needed 5 days)
• freeipa-healthcheck (- to 0.5-2)
  • Migration status for freeipa-healthcheck (- to 0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by tjaalton@ubuntu.com, a new source-only upload is needed to allow migration
  • Depends: freeipa-healthcheck freeipa
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freeipa-healthcheck.html
  • 60 days old (needed 5 days)
• gr-gsm (- to 0.42.2.20200214-1)
  • Migration status for gr-gsm (- to 0.42.2.20200214-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gr-gsm.html
  • 60 days old (needed 5 days)
• python-get-version (- to 2.1-1)
  • Migration status for python-get-version (- to 2.1-1): 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/p/python-get-version.html
  • Required age reduced by 3 days because of autopkgtest
  • 60 days old (needed 2 days)
• python-numpy-groupies (- to 0.9.10-2)
  • Migration status for python-numpy-groupies (- to 0.9.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): python-numpy-groupies numba
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-numpy-groupies.html
  • 60 days old (needed 5 days)
• libextractor-python (- to 1:0.6-8)
  • Migration status for libextractor-python (- to 1:0.6-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libe/libextractor-python.html
  • Not built on buildd: arch all binaries uploaded by beberking@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • 61 days old (needed 5 days)
• radare2 (- to 4.3.1+dfsg-1)
  • Migration status for radare2 (- to 4.3.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating radare2 introduces new bugs: #950372
  • Not built on buildd: arch amd64 binaries uploaded by sre
  • Not built on buildd: arch all binaries uploaded by sre, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radare2.html
  • 61 days old (needed 5 days)
• biobambam2 (- to 2.0.160+ds-1)
  • Migration status for biobambam2 (- to 2.0.160+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating biobambam2 introduces new bugs: #933937
  • biobambam2 unsatisfiable Build-Depends(-Arch) on armel: libmaus2-dev (>= 2.0.713)
  • biobambam2 unsatisfiable Build-Depends(-Arch) on armhf: libmaus2-dev (>= 2.0.713)
  • biobambam2 unsatisfiable Build-Depends(-Arch) on i386: libmaus2-dev (>= 2.0.713)
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • Not built on buildd: upload info for arch amd64 binaries not found
  • Not built on buildd: upload info for arch arm64 binaries not found
  • Not built on buildd: upload info for arch ppc64el binaries not found
  • Build-Depends(-Arch): biobambam2 libmaus2
  • Depends: biobambam2 libmaus2
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biobambam2.html
  • 62 days old (needed 5 days)
• galera-3 (25.3.28-2 to 25.3.29-2)
  • Migration status for galera-3 (25.3.28-2 to 25.3.29-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating galera-3 introduces new bugs: #958040
  • missing build on armel
  • Additional info:
  • Updating galera-3 fixes old bugs: #961636
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/galera-3.html
  • 62 days old (needed 5 days)
• fotoxx (- to 20.08-1)
  • Migration status for fotoxx (- to 20.08-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fotoxx introduces new bugs: #955727
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fotoxx.html
  • 63 days old (needed 5 days)
• gcc-10-cross-mipsen (- to 2+c1)
  • Migration status for gcc-10-cross-mipsen (- to 2+c1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by wzssyqa@gmail.com
  • Not built on buildd: arch all binaries uploaded by wzssyqa@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-mipsen.html
  • 63 days old (needed 5 days)
• gcc-9-cross-mipsen (- to 4+c2)
  • Migration status for gcc-9-cross-mipsen (- to 4+c2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gcc-9-cross-mipsen introduces new bugs: #946352
  • Build-Depends(-Arch): gcc-9-cross-mipsen gcc-10-cross-mipsen
  • Depends: gcc-9-cross-mipsen gcc-10-cross-mipsen
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross-mipsen.html
  • 63 days old (needed 5 days)
• openafs (- to 1.8.6~pre1-3)
  • Migration status for openafs (- to 1.8.6~pre1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/openafs.html
  • Additional info:
  • 63 days old (needed 5 days)
• hgsubversion (- to 1.9.3+git20190419+6a6ce-5)
  • Migration status for hgsubversion (- to 1.9.3+git20190419+6a6ce-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hgsubversion introduces new bugs: #954531
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hgsubversion.html
  • Required age reduced by 3 days because of autopkgtest
  • 64 days old (needed 2 days)
• neomutt (- to 20191207+dfsg.1-1.1)
  • Migration status for neomutt (- to 20191207+dfsg.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating neomutt introduces new bugs: #945442
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neomutt.html
  • 64 days old (needed 5 days)
• node-eslint-plugin-html (- to 3.2.1-3)
  • Migration status for node-eslint-plugin-html (- to 3.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating node-eslint-plugin-html introduces new bugs: #950654
  • autopkgtest for node-eslint-plugin-html/3.2.1-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-eslint-plugin-html.html
  • 64 days old (needed 5 days)
• python-flask-jwt-extended (- to 3.24.1-1)
  • Migration status for python-flask-jwt-extended (- to 3.24.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by eamanu@yaerobi.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flask-jwt-extended.html
  • 64 days old (needed 5 days)
• python-nest-asyncio (- to 1.2.3-1)
  • Migration status for python-nest-asyncio (- to 1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-nest-asyncio introduces new bugs: #959532
  • Not built on buildd: arch amd64 binaries uploaded by guptautkarsh2102@gmail.com
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nest-asyncio.html
  • 64 days old (needed 5 days)
• llvm-toolchain-7 (- to 1:7.0.1-12)
  • Migration status for llvm-toolchain-7 (- to 1:7.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • clang-tidy-7/amd64 has unsatisfiable dependency
  • llvm-7-tools/amd64 has unsatisfiable dependency
  • clang-tidy-7/arm64 has unsatisfiable dependency
  • llvm-7-tools/arm64 has unsatisfiable dependency
  • clang-tidy-7/armel has unsatisfiable dependency
  • llvm-7-tools/armel has unsatisfiable dependency
  • clang-tidy-7/armhf has unsatisfiable dependency
  • llvm-7-tools/armhf has unsatisfiable dependency
  • clang-tidy-7/i386 has unsatisfiable dependency
  • llvm-7-tools/i386 has unsatisfiable dependency
  • clang-tidy-7/mips64el has unsatisfiable dependency
  • llvm-7-tools/mips64el has unsatisfiable dependency
  • clang-tidy-7/mipsel has unsatisfiable dependency
  • llvm-7-tools/mipsel has unsatisfiable dependency
  • clang-tidy-7/ppc64el has unsatisfiable dependency
  • llvm-7-tools/ppc64el has unsatisfiable dependency
  • clang-tidy-7/s390x has unsatisfiable dependency
  • llvm-7-tools/s390x has unsatisfiable dependency
  • Updating llvm-toolchain-7 introduces new bugs: #916945, #941890
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-7.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 66 days old (needed 5 days)
• gitlab (- to 12.6.8-3)
  • Migration status for gitlab (- to 12.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • gitlab/amd64 has unsatisfiable dependency
  • gitlab/i386 has unsatisfiable dependency
  • Updating gitlab introduces new bugs: #915050, #942633, #943987, #953415, #955555
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 67 days old (needed 5 days)
• kodi-pvr-argustv (- to 3.5.4-1)
  • Migration status for kodi-pvr-argustv (- to 3.5.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kodi-pvr-argustv kodi (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kodi-pvr-argustv kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-argustv.html
  • 67 days old (needed 5 days)
• kodi-pvr-dvbviewer (- to 3.7.11-1)
  • Migration status for kodi-pvr-dvbviewer (- to 3.7.11-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): kodi-pvr-dvbviewer kodi (not considered)
  • Depends: kodi-pvr-dvbviewer kodi (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: kodi-pvr-dvbviewer kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-dvbviewer.html
  • 67 days old (needed 5 days)
• kodi-pvr-hdhomerun (- to 3.4.3-1)
  • Migration status for kodi-pvr-hdhomerun (- to 3.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kodi-pvr-hdhomerun introduces new bugs: #886499
  • Build-Depends(-Arch): kodi-pvr-hdhomerun kodiplatform
  • Depends: kodi-pvr-hdhomerun kodi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-hdhomerun.html
  • 67 days old (needed 5 days)
• kodi-pvr-hts (- to 4.4.20-1)
  • Migration status for kodi-pvr-hts (- to 4.4.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): kodi-pvr-hts kodi (not considered)
  • Depends: kodi-pvr-hts kodi (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-hts.html
  • 67 days old (needed 5 days)
• kodi-pvr-iptvsimple (- to 3.9.8-1)
  • Migration status for kodi-pvr-iptvsimple (- to 3.9.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kodi-pvr-iptvsimple kodi (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kodi-pvr-iptvsimple kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-iptvsimple.html
  • 67 days old (needed 5 days)
• kodi-pvr-mediaportal-tvserver (- to 3.5.18-1)
  • Migration status for kodi-pvr-mediaportal-tvserver (- to 3.5.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kodi-pvr-mediaportal-tvserver kodi (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kodi-pvr-mediaportal-tvserver kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-mediaportal-tvserver.html
  • 67 days old (needed 5 days)
• kodi-pvr-mythtv (- to 5.10.15-1)
  • Migration status for kodi-pvr-mythtv (- to 5.10.15-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kodi-pvr-mythtv kodi (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kodi-pvr-mythtv kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-mythtv.html
  • 67 days old (needed 5 days)
• kodi-pvr-nextpvr (- to 3.3.18-1)
  • Migration status for kodi-pvr-nextpvr (- to 3.3.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kodi-pvr-nextpvr kodi (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kodi-pvr-nextpvr kodiplatform
  • Depends: kodi-pvr-nextpvr kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-nextpvr.html
  • 67 days old (needed 5 days)
• kodi-pvr-njoy (- to 3.4.2-1)
  • Migration status for kodi-pvr-njoy (- to 3.4.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kodi-pvr-njoy kodi (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kodi-pvr-njoy kodiplatform
  • Depends: kodi-pvr-njoy kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-njoy.html
  • 67 days old (needed 5 days)
• kodi-pvr-vdr-vnsi (- to 3.6.4-1)
  • Migration status for kodi-pvr-vdr-vnsi (- to 3.6.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): kodi-pvr-vdr-vnsi kodi (not considered)
  • Depends: kodi-pvr-vdr-vnsi kodi (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-vdr-vnsi.html
  • 67 days old (needed 5 days)
• kodi-pvr-vuplus (- to 3.28.9-1)
  • Migration status for kodi-pvr-vuplus (- to 3.28.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kodi-pvr-vuplus kodi (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kodi-pvr-vuplus kodiplatform
  • Depends: kodi-pvr-vuplus kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-vuplus.html
  • 67 days old (needed 5 days)
• kodi-pvr-wmc (- to 2.4.5-1)
  • Migration status for kodi-pvr-wmc (- to 2.4.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kodi-pvr-wmc kodi (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): kodi-pvr-wmc kodiplatform
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-wmc.html
  • 67 days old (needed 5 days)
• kodi-visualization-spectrum (- to 3.0.3-1)
  • Migration status for kodi-visualization-spectrum (- to 3.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): kodi-visualization-spectrum kodi (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-visualization-spectrum.html
  • 67 days old (needed 5 days)
• kodiplatform (- to 20180302-1)
  • Migration status for kodiplatform (- to 20180302-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): kodiplatform kodi (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodiplatform.html
  • 67 days old (needed 5 days)
• python-linecache2 (1.0.0-3 to 1.0.0-4)
  • Migration status for python-linecache2 (1.0.0-3 to 1.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • removing python-linecache2/1.0.0-3/amd64 from testing makes python-unittest2/1.1.0-6.1/amd64 uninstallable
  • removing python-linecache2/1.0.0-3/i386 from testing makes python-unittest2/1.1.0-6.1/i386 uninstallable
  • Implicit dependency: python-linecache2 python-traceback2
  • Additional info:
  • Updating python-linecache2 fixes old bugs: #952127
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-linecache2.html
  • 67 days old (needed 5 days)
• python-traceback2 (1.4.0-5 to 1.4.0-6)
  • Migration status for python-traceback2 (1.4.0-5 to 1.4.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • removing python-traceback2/1.4.0-5/amd64 from testing makes python-unittest2/1.1.0-6.1/amd64 uninstallable
  • removing python-traceback2/1.4.0-5/i386 from testing makes python-unittest2/1.1.0-6.1/i386 uninstallable
  • Additional info:
  • Updating python-traceback2 fixes old bugs: #952130, #961191
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-traceback2.html
  • 67 days old (needed 5 days)
• golang-gopkg-yaml.v3 (- to 3.0.0~git20200121.a6ecf24-1)
  • Migration status for golang-gopkg-yaml.v3 (- to 3.0.0~git20200121.a6ecf24-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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gopkg-yaml.v3.html
  • Required age reduced by 3 days because of autopkgtest
  • 68 days old (needed 2 days)
• xdebug (2.7.2+2.5.5-1 to 2.9.3+2.8.1+2.5.5-1)
  • Migration status for xdebug (2.7.2+2.5.5-1 to 2.9.3+2.8.1+2.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xdebug introduces new bugs: #953727
  • Additional info:
  • Updating xdebug fixes old bugs: #952091, #961071
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdebug.html
  • 68 days old (needed 5 days)
• diploma (1.2.14 to 1.2.15)
  • Migration status for diploma (1.2.14 to 1.2.15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by anfra, a new source-only upload is needed to allow migration
  • Additional info:
  • Updating diploma fixes old bugs: #960958
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diploma.html
  • 70 days old (needed 5 days)
• node-jquery.waitforimages (- to 2.4.0+ds-5)
  • Migration status for node-jquery.waitforimages (- to 2.4.0+ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating node-jquery.waitforimages introduces new bugs: #955558
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-jquery.waitforimages.html
  • Required age reduced by 3 days because of autopkgtest
  • 70 days old (needed 2 days)
• prokka (- to 1.14.6+dfsg-1)
  • Migration status for prokka (- to 1.14.6+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
  • Additional info:
  • uninstallable on arch arm64, not running autopkgtest there
  • Required age reduced by 3 days because of autopkgtest
  • 70 days old (needed 2 days)
• r-cran-roxygen2 (7.0.2-1 to 7.1.0-2)
  • Migration status for r-cran-roxygen2 (7.0.2-1 to 7.1.0-2): Will attempt migration (Any information below is purely informational)
  • Depends: r-cran-roxygen2 r-base
  • Additional info:
  • Updating r-cran-roxygen2 fixes old bugs: #960962
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-roxygen2.html
  • Required age reduced by 3 days because of autopkgtest
  • 70 days old (needed 2 days)
• nvidia-graphics-drivers-legacy-304xx (- to 304.137-8)
  • Migration status for nvidia-graphics-drivers-legacy-304xx (- to 304.137-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • xserver-xorg-video-nvidia-legacy-304xx/amd64 has unsatisfiable dependency
  • xserver-xorg-video-nvidia-legacy-304xx/i386 has unsatisfiable dependency
  • Updating nvidia-graphics-drivers-legacy-304xx introduces new bugs: #900787, #925340
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • uninstallable on arch amd64, not running autopkgtest there
  • 72 days old (needed 5 days)
• zsnapd (- to 0.8.11h-1)
  • Migration status for zsnapd (- to 0.8.11h-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating zsnapd introduces new bugs: #919595
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 72 days old (needed 5 days)
• pychess (0.12.2-1 to 1.0.0-1)
  • Migration status for pychess (0.12.2-1 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 varun, a new source-only upload is needed to allow migration
  • Additional info:
  • Updating pychess fixes old bugs: #960712
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pychess.html
  • 73 days old (needed 5 days)
• rust-signal-hook (- to 0.1.13-1)
  • Migration status for rust-signal-hook (- to 0.1.13-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-signal-hook.html
  • 73 days old (needed 5 days)
• theme-d-gnome (0.8.2-1 to 0.9.0-1)
  • Migration status for theme-d-gnome (0.8.2-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/theme-d-gnome.html
  • 74 days old (needed 5 days)
• bcbio (1.1.2-3 to 1.2.0-2)
  • Migration status for bcbio (1.1.2-3 to 1.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): bcbio tophat-recondition (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Updating bcbio fixes old bugs: #960316
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 77 days old (needed 5 days)
• libpam-alreadyloggedin (0.3-6 to 0.3-8)
  • Migration status for libpam-alreadyloggedin (0.3-6 to 0.3-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libpam-alreadyloggedin introduces new bugs: #958224
  • autopkgtest for libpam-alreadyloggedin/0.3-8: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Updating libpam-alreadyloggedin fixes old bugs: #960173
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-alreadyloggedin.html
  • 78 days old (needed 5 days)
• gpgme1.0 (1.13.1-6 to 1.13.1-7)
  • Migration status for gpgme1.0 (1.13.1-6 to 1.13.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gpgme1.0 introduces new bugs: #953800
  • Additional info:
  • Updating gpgme1.0 fixes old bugs: #960077
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpgme1.0.html
  • Required age reduced by 3 days because of autopkgtest
  • 79 days old (needed 2 days)
• xfsdump (3.1.6+nmu2 to 3.1.9)
  • Migration status for xfsdump (3.1.6+nmu2 to 3.1.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xfsdump introduces new bugs: #953537
  • Not built on buildd: arch amd64 binaries uploaded by nathans
  • Additional info:
  • Updating xfsdump fixes old bugs: #952095, #960078
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfsdump.html
  • 79 days old (needed 5 days)
• libqtdbustest (0.2+bzr42+repack1-5 to 0.2+bzr42+repack1-9)
  • Migration status for libqtdbustest (0.2+bzr42+repack1-5 to 0.2+bzr42+repack1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libqtdbustest introduces new bugs: #879937
  • Not built on buildd: arch amd64 binaries uploaded by mike.gabriel@das-netzwerkteam.de
  • 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:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Updating libqtdbustest fixes old bugs: #960053
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libq/libqtdbustest.html
  • 80 days old (needed 5 days)
• upx-ucl (3.95-2 to 3.96-1)
  • Migration status for upx-ucl (3.95-2 to 3.96-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating upx-ucl introduces new bugs: #955157
  • autopkgtest for upx-ucl/3.96-1: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Updating upx-ucl fixes old bugs: #960057
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/upx-ucl.html
  • 80 days old (needed 5 days)
• clipman (- to 1.2.0+git20200218.39fd4fe-1)
  • Migration status for clipman (- to 1.2.0+git20200218.39fd4fe-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • clipman/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • Not built on buildd: arch amd64 binaries uploaded by alexandre@alexandreviau.net
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clipman.html
  • Required age reduced by 3 days because of autopkgtest
  • 81 days old (needed 2 days)
• flask-jwt-simple (- to 0.0.3-2)
  • Migration status for flask-jwt-simple (- to 0.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for flask-jwt-simple/0.0.3-2: amd64: Pass, arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by eamanu@yaerobi.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-jwt-simple.html
  • 81 days old (needed 5 days)
• json2file-go (- to 1.12)
  • Migration status for json2file-go (- to 1.12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/j/json2file-go.html
  • json2file-go/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • Not built on buildd: arch amd64 binaries uploaded by sto
  • Additional info:
  • 81 days old (needed 5 days)
• ydotool (- to 0.1.8-2)
  • Migration status for ydotool (- to 0.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ydotool introduces new bugs: #959905
  • Not built on buildd: arch amd64 binaries uploaded by alexandre@alexandreviau.net
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ydotool.html
  • 81 days old (needed 5 days)
• aboot (- to 1.0~pre20200212-1)
  • Migration status for aboot (- to 1.0~pre20200212-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • aboot-cross/amd64 has unsatisfiable dependency
  • aboot-cross/arm64 has unsatisfiable dependency
  • aboot-cross/armel has unsatisfiable dependency
  • aboot-cross/armhf has unsatisfiable dependency
  • aboot-cross/i386 has unsatisfiable dependency
  • aboot-cross/mips64el has unsatisfiable dependency
  • aboot-cross/mipsel has unsatisfiable dependency
  • aboot-cross/ppc64el has unsatisfiable dependency
  • aboot-cross/s390x has unsatisfiable dependency
  • Updating aboot introduces new bugs: #805988
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/aboot.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 82 days old (needed 5 days)
• mlpy (- to 3.5.0+ds-1)
  • Migration status for mlpy (- to 3.5.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mlpy introduces new bugs: #956019
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlpy.html
  • 82 days old (needed 5 days)
• pg-fact-loader (- to 1.5.2-2)
  • Migration status for pg-fact-loader (- to 1.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pg-fact-loader introduces new bugs: #950764
  • autopkgtest for pg-fact-loader/1.5.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by myon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-fact-loader.html
  • 82 days old (needed 5 days)
• pglogical-ticker (- to 1.4.0-2)
  • Migration status for pglogical-ticker (- to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pglogical-ticker introduces new bugs: #950677
  • autopkgtest for pglogical-ticker/1.4.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch amd64 binaries uploaded by myon
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pglogical-ticker.html
  • 82 days old (needed 5 days)
• dcmstack (- to 0.8-1)
  • Migration status for dcmstack (- to 0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for dcmstack/0.8-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dcmstack.html
  • 83 days old (needed 5 days)
• libqtdbusmock (0.7+bzr49+repack1-3 to 0.7+bzr49+repack1-4)
  • Migration status for libqtdbusmock (0.7+bzr49+repack1-3 to 0.7+bzr49+repack1-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on 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:
  • Updating libqtdbusmock fixes old bugs: #959813
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libq/libqtdbusmock.html
  • 83 days old (needed 5 days)
• win-iconv (- to 0.0.8-4)
  • Migration status for win-iconv (- to 0.0.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating win-iconv introduces new bugs: #921904
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/win-iconv.html
  • 83 days old (needed 5 days)
• openjdk-11-jre-dcevm (- to 11.0.5+5-1)
  • Migration status for openjdk-11-jre-dcevm (- to 11.0.5+5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openjdk-11-jre-dcevm introduces new bugs: #942876
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11-jre-dcevm.html
  • 84 days old (needed 5 days)
• build-essential-mipsen (- to 12.8)
  • Migration status for build-essential-mipsen (- to 12.8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by wzssyqa@gmail.com, a new source-only upload is needed to allow migration
  • Depends: build-essential-mipsen gcc-defaults-mipsen
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/build-essential-mipsen.html
  • uninstallable on arch arm64, not running autopkgtest there
  • 85 days old (needed 5 days)
• pythonmagick (- to 0.9.19-6)
  • Migration status for pythonmagick (- to 0.9.19-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pythonmagick introduces new bugs: #954812
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pythonmagick.html
  • Required age reduced by 3 days because of autopkgtest
  • 85 days old (needed 2 days)
• php-imagick (3.4.4-3 to 3.4.4-4)
  • Migration status for php-imagick (3.4.4-3 to 3.4.4-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on armel
  • Additional info:
  • Updating php-imagick fixes old bugs: #959386
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-imagick.html
  • 87 days old (needed 5 days)
• pillow-python2 (- to 6.2.1-3)
  • Migration status for pillow-python2 (- to 6.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pillow-python2 introduces new bugs: #952969, #954180
  • autopkgtest for pillow-python2/6.2.1-3: amd64: Regression ♻ , arm64: Regression ♻
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on amd64: python-pytest
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on arm64: python-pytest
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on armel: python-pytest
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on armhf: python-pytest
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on i386: python-pytest
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on mips64el: python-pytest
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on mipsel: python-pytest
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-pytest
  • pillow-python2 unsatisfiable Build-Depends(-Arch) on s390x: python-pytest
  • Not built on buildd: arch amd64 binaries uploaded by doko
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pillow-python2.html
  • 87 days old (needed 5 days)
• node-boom (- to 9.0.0+~2.0.0+ds-1)
  • Migration status for node-boom (- to 9.0.0+~2.0.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): node-boom node-hoek (not considered)
  • Depends: node-boom node-hoek (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-boom.html
  • 89 days old (needed 5 days)
• rpmlint (- to 1.11-0.2)
  • Migration status for rpmlint (- to 1.11-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rpmlint introduces new bugs: #953380
  • autopkgtest for rpmlint/1.11-0.2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rpmlint.html
  • 89 days old (needed 5 days)
• sks (- to 1.1.6-15)
  • Migration status for sks (- to 1.1.6-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sks introduces new bugs: #939962
  • 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
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sks.html
  • 89 days old (needed 5 days)
• broker (- to 1.2.5+ds1-1)
  • Migration status for broker (- to 1.2.5+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-broker/amd64 has unsatisfiable dependency
  • python3-broker/arm64 has unsatisfiable dependency
  • python3-broker/armel has unsatisfiable dependency
  • python3-broker/armhf has unsatisfiable dependency
  • python3-broker/i386 has unsatisfiable dependency
  • python3-broker/mips64el has unsatisfiable dependency
  • python3-broker/mipsel has unsatisfiable dependency
  • python3-broker/ppc64el has unsatisfiable dependency
  • python3-broker/s390x has unsatisfiable dependency
  • Updating broker introduces new bugs: #956948
  • broker unsatisfiable Build-Depends(-Arch) on amd64: swig3.0
  • broker unsatisfiable Build-Depends(-Arch) on arm64: swig3.0
  • broker unsatisfiable Build-Depends(-Arch) on armel: swig3.0
  • broker unsatisfiable Build-Depends(-Arch) on armhf: swig3.0
  • broker unsatisfiable Build-Depends(-Arch) on i386: swig3.0
  • broker unsatisfiable Build-Depends(-Arch) on mips64el: swig3.0
  • broker unsatisfiable Build-Depends(-Arch) on mipsel: swig3.0
  • broker unsatisfiable Build-Depends(-Arch) on ppc64el: swig3.0
  • broker unsatisfiable Build-Depends(-Arch) on s390x: swig3.0
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/broker.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 90 days old (needed 5 days)
• chirp (- to 1:20200227-1)
  • Migration status for chirp (- to 1:20200227-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • chirp/amd64 has unsatisfiable dependency
  • chirp/i386 has unsatisfiable dependency
  • Updating chirp introduces new bugs: #885265, #936299
  • chirp unsatisfiable Build-Depends(-Arch) on amd64: python-serial
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chirp.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 90 days old (needed 5 days)
• gajim-syntaxhighlight (- to 1.1.4-2)
  • Migration status for gajim-syntaxhighlight (- to 1.1.4-2): 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/g/gajim-syntaxhighlight.html
  • 90 days old (needed 5 days)
• knot-resolver (- to 5.0.1-2)
  • Migration status for knot-resolver (- to 5.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating knot-resolver introduces new bugs: #952673, #961076
  • autopkgtest for knot-resolver/5.0.1-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/knot-resolver.html
  • 90 days old (needed 5 days)
• rust-zstd (- to 0.5.1-1)
  • Migration status for rust-zstd (- to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-zstd+bindgen-dev/amd64 has unsatisfiable dependency
  • librust-zstd+legacy-dev/amd64 has unsatisfiable dependency
  • librust-zstd+wasm-dev/amd64 has unsatisfiable dependency
  • librust-zstd-dev/amd64 has unsatisfiable dependency
  • rust-zstd unsatisfiable Build-Depends(-Arch) on amd64: librust-zstd-safe-2.0.3+experimental-dev
  • rust-zstd unsatisfiable Build-Depends(-Arch) on amd64: librust-zstd-safe-2.0.3+legacy-dev
  • Not built on buildd: arch amd64 binaries uploaded by infinity0
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-zstd.html
  • uninstallable on arch amd64, not running autopkgtest there
  • 90 days old (needed 5 days)
• node-hoek (8.5.0+~4.2.1+~3.3.1-1 to 9.0.3+~5.0.0+~4.0.0-2)
  • Migration status for node-hoek (8.5.0+~4.2.1+~3.3.1-1 to 9.0.3+~5.0.0+~4.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by auto-removals
  • Trying to remove package, not update it
  • Updating node-hoek introduces new bugs: #952143
  • migrating node-hoek/9.0.3+~5.0.0+~4.0.0-2/amd64 to testing makes node-code/6.0.0-3/amd64 uninstallable
  • migrating node-hoek/9.0.3+~5.0.0+~4.0.0-2/i386 to testing makes node-code/6.0.0-3/i386 uninstallable
  • Additional info:
  • Updating node-hoek fixes old bugs: #958990
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-hoek.html
  • 91 days old (needed 5 days)
• pure-ftpd (- to 1.0.49-4)
  • Migration status for pure-ftpd (- to 1.0.49-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pure-ftpd introduces new bugs: #943874
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pure-ftpd.html
  • 91 days old (needed 5 days)
• smrtanalysis (- to 0~20200227)
  • Migration status for smrtanalysis (- to 0~20200227): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • smrtanalysis/i386 has unsatisfiable dependency
  • smrtanalysis-dev/i386 has unsatisfiable dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smrtanalysis.html
  • uninstallable on arch arm64, not running autopkgtest there
  • 91 days old (needed 5 days)
• gnat-gps (- to 19.2-3)
  • Migration status for gnat-gps (- to 19.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnat-gps introduces new bugs: #936624
  • Build-Depends(-Arch): gnat-gps libgnatcoll-python
  • Depends: gnat-gps libgnatcoll-python
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnat-gps.html
  • 92 days old (needed 5 days)
• gtk-gnutella (- to 1.1.15-1)
  • Migration status for gtk-gnutella (- to 1.1.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gtk-gnutella introduces new bugs: #956000
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-gnutella.html
  • 92 days old (needed 5 days)
• nant (- to 0.92~rc1+dfsg-7)
  • Migration status for nant (- to 0.92~rc1+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating nant introduces new bugs: #845733
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nant.html
  • 92 days old (needed 5 days)
• python-uvicorn (- to 0.11.3-1)
  • Migration status for python-uvicorn (- to 0.11.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): python-uvicorn uvloop (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-uvicorn.html
  • 92 days old (needed 5 days)
• prometheus-node-exporter-collectors (- to 0+git20200110.fc91c86-1)
  • Migration status for prometheus-node-exporter-collectors (- to 0+git20200110.fc91c86-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating prometheus-node-exporter-collectors introduces new bugs: #953893
  • autopkgtest for prometheus-node-exporter-collectors/0+git20200110.fc91c86-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by tincho, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-node-exporter-collectors.html
  • 93 days old (needed 5 days)
• puppet-module-puppetlabs-mount-core (- to 1.0.4+dfsg1-1)
  • Migration status for puppet-module-puppetlabs-mount-core (- to 1.0.4+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-mount-core.html
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • 93 days old (needed 5 days)
• haskell-fold-debounce (- to 0.2.0.9-1)
  • Migration status for haskell-fold-debounce (- to 0.2.0.9-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
  • Build-Depends(-Arch): haskell-fold-debounce haskell-stm-delay
  • Build-Depends-Indep: haskell-fold-debounce haskell-stm-delay
  • Depends: haskell-fold-debounce haskell-stm-delay
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-fold-debounce.html
  • 94 days old (needed 5 days)
• haskell-stm-delay (- to 0.1.1.1-1)
  • Migration status for haskell-stm-delay (- to 0.1.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
  • Depends: haskell-stm-delay ghc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-stm-delay.html
  • 94 days old (needed 5 days)
• haskell-taskell (- to 1.4.0.0-1)
  • Migration status for haskell-taskell (- to 1.4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by schizo
  • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): haskell-taskell haskell-tasty-discover
  • Build-Depends-Indep: haskell-taskell haskell-fold-debounce
  • Depends: haskell-taskell haskell-fold-debounce
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-taskell.html
  • 94 days old (needed 5 days)
• haskell-tasty-discover (- to 4.2.1-1)
  • Migration status for haskell-tasty-discover (- to 4.2.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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-tasty-discover.html
  • 94 days old (needed 5 days)
• mod-gnutls (- to 0.9.0-1.1)
  • Migration status for mod-gnutls (- to 0.9.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mod-gnutls introduces new bugs: #942737
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mod-gnutls.html
  • 94 days old (needed 5 days)
• ruby-tty-which (- to 0.4.2-1)
  • Migration status for ruby-tty-which (- 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 cedric.boutillier@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-tty-which.html
  • Required age reduced by 3 days because of autopkgtest
  • 94 days old (needed 2 days)
• ufoai (- to 2.5-5)
  • Migration status for ufoai (- to 2.5-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: ufoai ufoai-maps (not considered)
  • Invalidated by dependency
  • Depends: ufoai ufoai-data
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ufoai.html
  • 94 days old (needed 5 days)
• libpam-radius-auth (- to 1.4.0-3)
  • Migration status for libpam-radius-auth (- to 1.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libpam-radius-auth introduces new bugs: #951770
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-radius-auth.html
  • 97 days old (needed 5 days)
• olive-editor (- to 20200210-1)
  • Migration status for olive-editor (- to 20200210-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating olive-editor introduces new bugs: #950564
  • missing build on i386
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/olive-editor.html
  • 97 days old (needed 5 days)
• dbus-cpp (- to 5.0.1-4)
  • Migration status for dbus-cpp (- to 5.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dbus-cpp introduces new bugs: #888995
  • autopkgtest for dbus-cpp/5.0.1-4: amd64: Regression ♻ , arm64: Regression ♻
  • missing build on armel
  • missing build on armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbus-cpp.html
  • 99 days old (needed 5 days)
• frr (- to 7.2.1-1)
  • Migration status for frr (- to 7.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating frr introduces new bugs: #955067
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frr.html
  • Required age reduced by 3 days because of autopkgtest
  • 102 days old (needed 2 days)
• casparcg-server (- to 2.2.0+dfsg-2.1)
  • Migration status for casparcg-server (- to 2.2.0+dfsg-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating casparcg-server introduces new bugs: #947518
  • missing build on amd64
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 103 days old (needed 5 days)
• python-cassandra-driver (3.16.0-2 to 3.20.2-2)
  • Migration status for python-cassandra-driver (3.16.0-2 to 3.20.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-cassandra-driver introduces new bugs: #952753, #956548
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Updating python-cassandra-driver fixes old bugs: #956726
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cassandra-driver.html
  • 104 days old (needed 5 days)
• purple-matrix (- to 0.0.0+git20191228-1)
  • Migration status for purple-matrix (- to 0.0.0+git20191228-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating purple-matrix introduces new bugs: #855541
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purple-matrix.html
  • 106 days old (needed 5 days)
• dxvk (- to 1.5.4+ds1-2)
  • Migration status for dxvk (- to 1.5.4+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dxvk introduces new bugs: #954539
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dxvk.html
  • uninstallable on arch arm64, not running autopkgtest there
  • Required age reduced by 3 days because of autopkgtest
  • 108 days old (needed 2 days)
• ksh93 (- to 93u+20120801-7)
  • Migration status for ksh93 (- to 93u+20120801-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ksh93 introduces new bugs: #950762
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ksh93.html
  • 108 days old (needed 5 days)
• nim-unicodeplus (- to 0.5.1-1)
  • Migration status for nim-unicodeplus (- to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • nim-unicodeplus-dev/amd64 has unsatisfiable dependency
  • nim-unicodeplus-dev/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/nim-unicodeplus.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 109 days old (needed 5 days)
• ember (- to 0.8.0~snap1)
  • Migration status for ember (- to 0.8.0~snap1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ember/mips64el has unsatisfiable dependency
  • ember/mipsel has unsatisfiable dependency
  • Updating ember introduces new bugs: #950926
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ember.html
  • 110 days old (needed 5 days)
• pymtbl (- to 0.4.1-2)
  • Migration status for pymtbl (- to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pymtbl introduces new bugs: #937483
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymtbl.html
  • 111 days old (needed 5 days)
• flang (- to 20190329-5)
  • Migration status for flang (- to 20190329-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating flang introduces new bugs: #947437
  • Build-Depends(-Arch): flang llvm-toolchain-7
  • Depends: flang llvm-toolchain-7
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flang.html
  • 113 days old (needed 5 days)
• nanopb (- to 0.4.1-1)
  • Migration status for nanopb (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by gcs
  • Not built on buildd: arch all binaries uploaded by gcs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanopb.html
  • 113 days old (needed 5 days)
• puppet-module-puppetlabs-host-core (- to 1.0.3-1)
  • Migration status for puppet-module-puppetlabs-host-core (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-host-core.html
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • 113 days old (needed 5 days)
• puppet-module-puppetlabs-selinux-core (- to 1.0.4-1)
  • Migration status for puppet-module-puppetlabs-selinux-core (- to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-selinux-core.html
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • 113 days old (needed 5 days)
• puppet-module-puppetlabs-sshkeys-core (- to 1.0.3-1)
  • Migration status for puppet-module-puppetlabs-sshkeys-core (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-sshkeys-core.html
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • 113 days old (needed 5 days)
• golang-github-coreos-discovery-etcd-io (- to 2.0.0+git2019.04.19.git.78fb45d3c9-1)
  • Migration status for golang-github-coreos-discovery-etcd-io (- to 2.0.0+git2019.04.19.git.78fb45d3c9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • etcd-discovery/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • etcd-discovery/arm64 has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • etcd-discovery/armel has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • etcd-discovery/armhf has unsatisfiable Built-Using on golang-1.13 1.13.6-2
  • etcd-discovery/i386 has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • etcd-discovery/mips64el has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • etcd-discovery/mipsel has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • etcd-discovery/ppc64el has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • etcd-discovery/s390x has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • Not built on buildd: arch amd64 binaries uploaded by zigo
  • Build-Depends(-Arch): golang-github-coreos-discovery-etcd-io golang-github-rsc-devweb
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-coreos-discovery-etcd-io.html
  • 115 days old (needed 5 days)
• golang-github-xanzy-go-gitlab (- to 0.22.2-1)
  • Migration status for golang-github-xanzy-go-gitlab (- to 0.22.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-github-xanzy-go-gitlab introduces new bugs: #953224
  • autopkgtest for golang-github-xanzy-go-gitlab/0.22.2-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by anarcat@koumbit.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-xanzy-go-gitlab.html
  • 115 days old (needed 5 days)
• libjpeg9 (- to 1:9d-1)
  • Migration status for libjpeg9 (- to 1:9d-1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
  • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg9.html
  • 115 days old (needed 5 days)
• puppet-module-puppetlabs-augeas-core (- to 1.0.5-1)
  • Migration status for puppet-module-puppetlabs-augeas-core (- to 1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-augeas-core.html
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • 115 days old (needed 5 days)
• puppet-module-puppetlabs-cron-core (- to 1.0.3+dfsg1-1)
  • Migration status for puppet-module-puppetlabs-cron-core (- to 1.0.3+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-cron-core.html
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • 115 days old (needed 5 days)
• q2-metadata (- to 2019.10.0+dfsg-2)
  • Migration status for q2-metadata (- to 2019.10.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: q2-metadata qiime (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): q2-metadata q2-types
  • Depends: q2-metadata q2-types
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-metadata.html
  • Required age reduced by 3 days because of autopkgtest
  • 115 days old (needed 2 days)
• xboxdrv (- to 0.8.8-2)
  • Migration status for xboxdrv (- to 0.8.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xboxdrv introduces new bugs: #945748
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xboxdrv.html
  • 115 days old (needed 5 days)
• vagrant-bindfs (- to 1.1.6-1)
  • Migration status for vagrant-bindfs (- to 1.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vagrant-bindfs introduces new bugs: #953226
  • autopkgtest for vagrant-bindfs/1.1.6-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-bindfs.html
  • 116 days old (needed 5 days)
• boxfort (- to 0.0.0-git20200105-3e16c0a-6)
  • Migration status for boxfort (- to 0.0.0-git20200105-3e16c0a-6): 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/b/boxfort.html
  • Required age reduced by 3 days because of autopkgtest
  • 117 days old (needed 2 days)
• gobgp (- to 2.12.0-1)
  • Migration status for gobgp (- to 2.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gobgp introduces new bugs: #871692
  • gobgpd/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • gobgpd/arm64 has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • gobgpd/armel has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • gobgpd/armhf has unsatisfiable Built-Using on golang-1.13 1.13.6-2
  • gobgpd/i386 has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • gobgpd/mips64el has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • gobgpd/mipsel has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • gobgpd/ppc64el has unsatisfiable Built-Using on golang-1.13 1.13.7-1
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gobgp.html
  • 117 days old (needed 5 days)
• node-shell-quote (- to 1.7.2-1)
  • Migration status for node-shell-quote (- to 1.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating node-shell-quote introduces new bugs: #873148
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-shell-quote.html
  • Required age reduced by 3 days because of autopkgtest
  • 117 days old (needed 2 days)
• interimap (- to 0.5-1)
  • Migration status for interimap (- to 0.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): interimap dovecot (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/interimap.html
  • 120 days old (needed 5 days)
• python-trezor (- to 0.11.6-1)
  • Migration status for python-trezor (- to 0.11.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): python-trezor python-libusb1 (not considered)
  • Depends: python-trezor python-libusb1 (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-trezor.html
  • 120 days old (needed 5 days)
• debian-design (- to 3.0.17)
  • Migration status for debian-design (- to 3.0.17): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: debian-design origami-pdf (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-design.html
  • 123 days old (needed 5 days)
• q2-cutadapt (- to 2019.10.0-1)
  • Migration status for q2-cutadapt (- to 2019.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for q2-cutadapt/2019.10.0-1: amd64: Pass, arm64: Regression ♻
  • Build-Depends(-Arch): q2-cutadapt q2-types
  • Depends: q2-cutadapt q2-types
  • Depends: q2-cutadapt qiime
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-cutadapt.html
  • 123 days old (needed 5 days)
• q2-demux (- to 2019.10.0-1)
  • Migration status for q2-demux (- to 2019.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • q2-demux/i386 has unsatisfiable dependency
  • Build-Depends(-Arch): q2-demux q2-types
  • Depends: q2-demux q2-types
  • Depends: q2-demux qiime
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-demux.html
  • Required age reduced by 3 days because of autopkgtest
  • 123 days old (needed 2 days)
• q2-feature-table (- to 2019.10.0+dfsg-1)
  • Migration status for q2-feature-table (- to 2019.10.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • q2-feature-table/i386 has unsatisfiable dependency
  • Build-Depends(-Arch): q2-feature-table q2-types
  • Depends: q2-feature-table q2-types
  • Depends: q2-feature-table qiime
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-feature-table.html
  • Required age reduced by 3 days because of autopkgtest
  • 123 days old (needed 2 days)
• q2-quality-filter (- to 2019.10.0-1)
  • Migration status for q2-quality-filter (- to 2019.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for q2-quality-filter/2019.10.0-1: amd64: Pass, arm64: Regression ♻
  • Build-Depends(-Arch): q2-quality-filter q2-types
  • Depends: q2-quality-filter q2-types
  • Depends: q2-quality-filter qiime
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-quality-filter.html
  • 123 days old (needed 5 days)
• clap (- to 0.14.0-1)
  • Migration status for clap (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by phls@softwarelivre.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clap.html
  • Required age reduced by 3 days because of autopkgtest
  • 125 days old (needed 2 days)
• haskell-rank2classes (- to 1.3.1.1-1)
  • Migration status for haskell-rank2classes (- to 1.3.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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-rank2classes.html
  • 125 days old (needed 5 days)
• python-enable (- to 4.8.1-1)
  • Migration status for python-enable (- to 4.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-enable introduces new bugs: #951888
  • Not built on buildd: arch amd64 binaries uploaded by varun
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-enable.html
  • 125 days old (needed 5 days)
• rust-serde-bytes (- to 0.11.3-2)
  • Migration status for rust-serde-bytes (- to 0.11.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-serde-bytes/0.11.3-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde-bytes.html
  • 125 days old (needed 5 days)
• rust-xdg (- to 2.2.0-2)
  • Migration status for rust-xdg (- to 2.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-xdg introduces new bugs: #958398
  • autopkgtest for rust-xdg/2.2.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xdg.html
  • 125 days old (needed 5 days)
• ghemical (- to 3.0.0-5)
  • Migration status for ghemical (- to 3.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): ghemical mpqc (not considered)
  • Depends: ghemical mpqc (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: ghemical libghemical
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghemical.html
  • 126 days old (needed 5 days)
• gnome-chemistry-utils (- to 0.14.17-3)
  • Migration status for gnome-chemistry-utils (- to 0.14.17-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnome-chemistry-utils introduces new bugs: #947529
  • Build-Depends(-Arch): gnome-chemistry-utils gnome-doc-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-chemistry-utils.html
  • 126 days old (needed 5 days)
• rust-getopts (- to 0.2.21-2)
  • Migration status for rust-getopts (- to 0.2.21-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-getopts+rustc-dep-of-std-dev/amd64 has unsatisfiable dependency
  • librust-getopts+std-dev/amd64 has unsatisfiable dependency
  • librust-getopts+rustc-dep-of-std-dev/arm64 has unsatisfiable dependency
  • librust-getopts+std-dev/arm64 has unsatisfiable dependency
  • librust-getopts+rustc-dep-of-std-dev/armel has unsatisfiable dependency
  • librust-getopts+std-dev/armel has unsatisfiable dependency
  • librust-getopts+rustc-dep-of-std-dev/armhf has unsatisfiable dependency
  • librust-getopts+std-dev/armhf has unsatisfiable dependency
  • librust-getopts+rustc-dep-of-std-dev/i386 has unsatisfiable dependency
  • librust-getopts+std-dev/i386 has unsatisfiable dependency
  • librust-getopts+rustc-dep-of-std-dev/mips64el has unsatisfiable dependency
  • librust-getopts+std-dev/mips64el has unsatisfiable dependency
  • librust-getopts+rustc-dep-of-std-dev/mipsel has unsatisfiable dependency
  • librust-getopts+std-dev/mipsel has unsatisfiable dependency
  • librust-getopts+rustc-dep-of-std-dev/ppc64el has unsatisfiable dependency
  • librust-getopts+std-dev/ppc64el has unsatisfiable dependency
  • librust-getopts+rustc-dep-of-std-dev/s390x has unsatisfiable dependency
  • librust-getopts+std-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-getopts.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 126 days old (needed 5 days)
• golang-github-powerman-check (- to 1.2.1-1)
  • Migration status for golang-github-powerman-check (- 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 eric, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-powerman-check.html
  • Required age reduced by 3 days because of autopkgtest
  • 128 days old (needed 2 days)
• uncertainties (- to 3.1.2-1)
  • Migration status for uncertainties (- to 3.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating uncertainties introduces new bugs: #949613
  • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uncertainties.html
  • 128 days old (needed 5 days)
• lizardfs (- to 3.12.0+dfsg-4)
  • Migration status for lizardfs (- to 3.12.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lizardfs introduces new bugs: #936955
  • missing build on armel
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lizardfs.html
  • 130 days old (needed 5 days)
• python-simpy (- to 2.3.1+dfsg-2)
  • Migration status for python-simpy (- to 2.3.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-simpy introduces new bugs: #955055
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-simpy.html
  • 132 days old (needed 5 days)
• rust-der-parser (- to 3.0.3-1)
  • Migration status for rust-der-parser (- to 3.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-der-parser rust-num-bigint (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-der-parser.html
  • 134 days old (needed 5 days)
• rust-hdrhistogram (- to 6.3.4-2)
  • Migration status for rust-hdrhistogram (- to 6.3.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-hdrhistogram+crossbeam-channel-dev/amd64 has unsatisfiable dependency
  • librust-hdrhistogram+crossbeam-channel-dev/arm64 has unsatisfiable dependency
  • librust-hdrhistogram+crossbeam-channel-dev/armel has unsatisfiable dependency
  • librust-hdrhistogram+crossbeam-channel-dev/armhf has unsatisfiable dependency
  • librust-hdrhistogram+crossbeam-channel-dev/i386 has unsatisfiable dependency
  • librust-hdrhistogram+crossbeam-channel-dev/mips64el has unsatisfiable dependency
  • librust-hdrhistogram+crossbeam-channel-dev/mipsel has unsatisfiable dependency
  • librust-hdrhistogram+crossbeam-channel-dev/ppc64el has unsatisfiable dependency
  • librust-hdrhistogram+crossbeam-channel-dev/s390x has unsatisfiable dependency
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-channel-0.3+default-dev
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-channel-0.3+default-dev
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-channel-0.3+default-dev
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-channel-0.3+default-dev
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-channel-0.3+default-dev
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-channel-0.3+default-dev
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-channel-0.3+default-dev
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-channel-0.3+default-dev
  • rust-hdrhistogram unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-channel-0.3+default-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hdrhistogram.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 134 days old (needed 5 days)
• rust-sloppy-rfc4880 (- to 0.1.5-2)
  • Migration status for rust-sloppy-rfc4880 (- to 0.1.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-sloppy-rfc4880 rust-sha-1 (not considered)
  • Depends: rust-sloppy-rfc4880 rust-sha-1 (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sloppy-rfc4880.html
  • Required age reduced by 3 days because of autopkgtest
  • 134 days old (needed 2 days)
• viking (- to 1.7-2)
  • Migration status for viking (- to 1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating viking introduces new bugs: #947541
  • Build-Depends(-Arch): viking gnome-doc-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/viking.html
  • 134 days old (needed 5 days)
• axtls (- to 2.1.5+ds-1)
  • Migration status for axtls (- to 2.1.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating axtls introduces new bugs: #953326
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/axtls.html
  • Required age reduced by 3 days because of autopkgtest
  • 135 days old (needed 2 days)
• gitaly (- to 1.78.0+dfsg-2)
  • Migration status for gitaly (- to 1.78.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: gitaly gitlab (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitaly.html
  • Required age reduced by 3 days because of autopkgtest
  • 135 days old (needed 2 days)
• opensysusers (- to 0.5.1-1)
  • Migration status for opensysusers (- to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensysusers.html
  • 135 days old (needed 5 days)
• rust-num-rational (- to 0.2.3-1)
  • Migration status for rust-num-rational (- to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-num-rational/0.2.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • Build-Depends(-Arch): rust-num-rational rust-num-bigint
  • Depends: rust-num-rational rust-num-bigint
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-rational.html
  • 135 days old (needed 5 days)
• mysql-workbench (- to 8.0.19+dfsg-1)
  • Migration status for mysql-workbench (- to 8.0.19+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mysql-workbench/amd64 has unsatisfiable dependency
  • mysql-workbench/arm64 has unsatisfiable dependency
  • mysql-workbench/armel has unsatisfiable dependency
  • mysql-workbench/armhf has unsatisfiable dependency
  • mysql-workbench/i386 has unsatisfiable dependency
  • mysql-workbench/mips64el has unsatisfiable dependency
  • mysql-workbench/mipsel has unsatisfiable dependency
  • mysql-workbench/ppc64el has unsatisfiable dependency
  • mysql-workbench/s390x has unsatisfiable dependency
  • Updating mysql-workbench introduces new bugs: #944177, #953138
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on amd64: python-paramiko
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on arm64: python-paramiko
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on armel: python-paramiko
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on armhf: python-paramiko
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on i386: python-paramiko
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on mips64el: python-paramiko
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on mipsel: python-paramiko
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on ppc64el: python-paramiko
  • mysql-workbench unsatisfiable Build-Depends(-Arch) on s390x: python-paramiko
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-workbench.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 136 days old (needed 5 days)
• simka (- to 1.5.1-4)
  • Migration status for simka (- to 1.5.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for simka/1.5.1-4: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simka.html
  • 136 days old (needed 5 days)
• sinntp (- to 1.6-1)
  • Migration status for sinntp (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sinntp introduces new bugs: #953908
  • autopkgtest for sinntp/1.6-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sinntp.html
  • 137 days old (needed 5 days)
• paleomix (- to 1.2.14-1)
  • Migration status for paleomix (- to 1.2.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • paleomix/amd64 has unsatisfiable dependency
  • Updating paleomix introduces new bugs: #937232
  • paleomix unsatisfiable Build-Depends(-Arch) on amd64: python-flexmock
  • paleomix unsatisfiable Build-Depends(-Arch) on amd64: python-pysam
  • paleomix unsatisfiable Build-Depends(-Arch) on amd64: python-setproctitle
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paleomix.html
  • uninstallable on arch amd64, not running autopkgtest there
  • 139 days old (needed 5 days)
• rust-cookie (- to 0.12.0-4)
  • Migration status for rust-cookie (- to 0.12.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-cookie+ring-dev/amd64 has unsatisfiable dependency
  • librust-cookie+secure-dev/amd64 has unsatisfiable dependency
  • librust-cookie+ring-dev/arm64 has unsatisfiable dependency
  • librust-cookie+secure-dev/arm64 has unsatisfiable dependency
  • librust-cookie+ring-dev/armel has unsatisfiable dependency
  • librust-cookie+secure-dev/armel has unsatisfiable dependency
  • librust-cookie+ring-dev/armhf has unsatisfiable dependency
  • librust-cookie+secure-dev/armhf has unsatisfiable dependency
  • librust-cookie+ring-dev/i386 has unsatisfiable dependency
  • librust-cookie+secure-dev/i386 has unsatisfiable dependency
  • librust-cookie+ring-dev/mips64el has unsatisfiable dependency
  • librust-cookie+secure-dev/mips64el has unsatisfiable dependency
  • librust-cookie+ring-dev/mipsel has unsatisfiable dependency
  • librust-cookie+secure-dev/mipsel has unsatisfiable dependency
  • librust-cookie+ring-dev/ppc64el has unsatisfiable dependency
  • librust-cookie+secure-dev/ppc64el has unsatisfiable dependency
  • librust-cookie+ring-dev/s390x has unsatisfiable dependency
  • librust-cookie+secure-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cookie.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 140 days old (needed 5 days)
• rust-cssparser (- to 0.27.2-1)
  • Migration status for rust-cssparser (- to 0.27.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-cssparser/0.27.2-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cssparser.html
  • 140 days old (needed 5 days)
• rust-grcov (- to 0.4.1-2)
  • Migration status for rust-grcov (- to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-grcov introduces new bugs: #948630
  • rust-grcov unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on amd64: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on amd64: librust-uuid-0.7+v4-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on arm64: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on arm64: librust-uuid-0.7+v4-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on armel: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on armel: librust-uuid-0.7+v4-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on armhf: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on armhf: librust-uuid-0.7+v4-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on i386: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on i386: librust-uuid-0.7+v4-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on mips64el: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on mips64el: librust-uuid-0.7+v4-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on mipsel: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on mipsel: librust-uuid-0.7+v4-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on ppc64el: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on ppc64el: librust-uuid-0.7+v4-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-0.4+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on s390x: librust-uuid-0.7+default-dev
  • rust-grcov unsatisfiable Build-Depends(-Arch) on s390x: librust-uuid-0.7+v4-dev
  • missing build on amd64
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-grcov.html
  • 140 days old (needed 5 days)
• zypper (- to 1.14.11-2)
  • Migration status for zypper (- to 1.14.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): zypper libzypp (not considered)
  • Depends: zypper libzypp (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zypper.html
  • 140 days old (needed 5 days)
• staticsite (- to 1.4.1-1)
  • Migration status for staticsite (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating staticsite introduces new bugs: #949756
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/staticsite.html
  • 141 days old (needed 5 days)
• cyphesis-cpp (- to 0.7.0~snap1)
  • Migration status for cyphesis-cpp (- to 0.7.0~snap1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • cyphesis-cpp/mips64el has unsatisfiable dependency
  • cyphesis-cpp/mipsel has unsatisfiable dependency
  • Updating cyphesis-cpp introduces new bugs: #948734
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cyphesis-cpp.html
  • Additional info:
  • 142 days old (needed 5 days)
• kopano-webapp-plugin-files (- to 2.1.5+dfsg1-2)
  • Migration status for kopano-webapp-plugin-files (- to 2.1.5+dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: kopano-webapp-plugin-files php-sabredav (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kopano-webapp-plugin-files.html
  • 144 days old (needed 5 days)
• pysurfer (- to 0.9.0-3)
  • Migration status for pysurfer (- to 0.9.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for pysurfer/0.9.0-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysurfer.html
  • 144 days old (needed 5 days)
• pagekite (- to 1.5.0.191126-1)
  • Migration status for pagekite (- to 1.5.0.191126-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pagekite introduces new bugs: #950249
  • autopkgtest for pagekite/1.5.0.191126-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pagekite.html
  • 145 days old (needed 5 days)
• rust-rspotify (- to 0.7.0-2)
  • Migration status for rust-rspotify (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by infinity0
  • Build-Depends(-Arch): rust-rspotify rust-webbrowser
  • Depends: rust-rspotify rust-derive-builder
  • Depends: rust-rspotify rust-reqwest
  • Depends: rust-rspotify rust-webbrowser
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-rspotify.html
  • 145 days old (needed 5 days)
• rust-bcder (- to 0.4.1-1)
  • Migration status for rust-bcder (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-bcder-dev/amd64 has unsatisfiable dependency
  • librust-bcder-dev/arm64 has unsatisfiable dependency
  • librust-bcder-dev/armel has unsatisfiable dependency
  • librust-bcder-dev/armhf has unsatisfiable dependency
  • librust-bcder-dev/i386 has unsatisfiable dependency
  • librust-bcder-dev/mips64el has unsatisfiable dependency
  • librust-bcder-dev/mipsel has unsatisfiable dependency
  • librust-bcder-dev/ppc64el has unsatisfiable dependency
  • librust-bcder-dev/s390x has unsatisfiable dependency
  • Updating rust-bcder introduces new bugs: #948632
  • rust-bcder unsatisfiable Build-Depends(-Arch) on amd64: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • rust-bcder unsatisfiable Build-Depends(-Arch) on arm64: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • rust-bcder unsatisfiable Build-Depends(-Arch) on armel: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • rust-bcder unsatisfiable Build-Depends(-Arch) on armhf: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • rust-bcder unsatisfiable Build-Depends(-Arch) on i386: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • rust-bcder unsatisfiable Build-Depends(-Arch) on mips64el: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • rust-bcder unsatisfiable Build-Depends(-Arch) on mipsel: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • rust-bcder unsatisfiable Build-Depends(-Arch) on ppc64el: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • rust-bcder unsatisfiable Build-Depends(-Arch) on s390x: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
  • Not built on buildd: arch amd64 binaries uploaded by md
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bcder.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 146 days old (needed 5 days)
• rust-sniffglue (- to 0.10.1-1)
  • Migration status for rust-sniffglue (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • rust-sniffglue unsatisfiable Build-Depends(-Arch) on arm64: librust-syscallz-0.12+default-dev
  • rust-sniffglue unsatisfiable Build-Depends(-Arch) on mips64el: librust-syscallz-0.12+default-dev
  • rust-sniffglue unsatisfiable Build-Depends(-Arch) on mipsel: librust-syscallz-0.12+default-dev
  • rust-sniffglue unsatisfiable Build-Depends(-Arch) on s390x: librust-syscallz-0.12+default-dev
  • missing build on arm64
  • missing build on mips64el
  • missing build on mipsel
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Build-Depends(-Arch): rust-sniffglue rust-users
  • Depends: rust-sniffglue rust-users
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sniffglue.html
  • 148 days old (needed 5 days)
• rust-clipboard (- to 0.5.0-2)
  • Migration status for rust-clipboard (- to 0.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-clipboard/0.5.0-2: amd64: Regression ♻ , arm64: No test results
  • Build-Depends(-Arch): rust-clipboard rust-x11-clipboard
  • Depends: rust-clipboard rust-x11-clipboard
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-clipboard.html
  • 149 days old (needed 5 days)
• rust-reqwest (- to 0.9.19-3)
  • Migration status for rust-reqwest (- to 0.9.19-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-reqwest+hyper-011-dev/amd64 has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/amd64 has unsatisfiable dependency
  • librust-reqwest+rustls-dev/amd64 has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/amd64 has unsatisfiable dependency
  • librust-reqwest+socks-dev/amd64 has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/amd64 has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/amd64 has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/amd64 has unsatisfiable dependency
  • librust-reqwest+hyper-011-dev/arm64 has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/arm64 has unsatisfiable dependency
  • librust-reqwest+rustls-dev/arm64 has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/arm64 has unsatisfiable dependency
  • librust-reqwest+socks-dev/arm64 has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/arm64 has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/arm64 has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/arm64 has unsatisfiable dependency
  • librust-reqwest+hyper-011-dev/armel has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/armel has unsatisfiable dependency
  • librust-reqwest+rustls-dev/armel has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/armel has unsatisfiable dependency
  • librust-reqwest+socks-dev/armel has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/armel has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/armel has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/armel has unsatisfiable dependency
  • librust-reqwest+hyper-011-dev/armhf has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/armhf has unsatisfiable dependency
  • librust-reqwest+rustls-dev/armhf has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/armhf has unsatisfiable dependency
  • librust-reqwest+socks-dev/armhf has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/armhf has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/armhf has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/armhf has unsatisfiable dependency
  • librust-reqwest+hyper-011-dev/i386 has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/i386 has unsatisfiable dependency
  • librust-reqwest+rustls-dev/i386 has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/i386 has unsatisfiable dependency
  • librust-reqwest+socks-dev/i386 has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/i386 has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/i386 has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/i386 has unsatisfiable dependency
  • librust-reqwest+hyper-011-dev/mips64el has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/mips64el has unsatisfiable dependency
  • librust-reqwest+rustls-dev/mips64el has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/mips64el has unsatisfiable dependency
  • librust-reqwest+socks-dev/mips64el has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/mips64el has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/mips64el has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/mips64el has unsatisfiable dependency
  • librust-reqwest+hyper-011-dev/mipsel has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/mipsel has unsatisfiable dependency
  • librust-reqwest+rustls-dev/mipsel has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/mipsel has unsatisfiable dependency
  • librust-reqwest+socks-dev/mipsel has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/mipsel has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/mipsel has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/mipsel has unsatisfiable dependency
  • librust-reqwest+hyper-011-dev/ppc64el has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/ppc64el has unsatisfiable dependency
  • librust-reqwest+rustls-dev/ppc64el has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/ppc64el has unsatisfiable dependency
  • librust-reqwest+socks-dev/ppc64el has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/ppc64el has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/ppc64el has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/ppc64el has unsatisfiable dependency
  • librust-reqwest+hyper-011-dev/s390x has unsatisfiable dependency
  • librust-reqwest+hyper-rustls-dev/s390x has unsatisfiable dependency
  • librust-reqwest+rustls-dev/s390x has unsatisfiable dependency
  • librust-reqwest+rustls-tls-dev/s390x has unsatisfiable dependency
  • librust-reqwest+socks-dev/s390x has unsatisfiable dependency
  • librust-reqwest+tokio-rustls-dev/s390x has unsatisfiable dependency
  • librust-reqwest+trust-dns-dev/s390x has unsatisfiable dependency
  • librust-reqwest+webpki-roots-dev/s390x has unsatisfiable dependency
  • Build-Depends(-Arch): rust-reqwest rust-tokio-timer
  • Depends: rust-reqwest rust-cookie
  • Depends: rust-reqwest rust-cookie-store
  • Depends: rust-reqwest rust-hyper
  • Depends: rust-reqwest rust-hyper-tls
  • Depends: rust-reqwest rust-tokio
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-reqwest.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 149 days old (needed 5 days)
• rust-webbrowser (- to 0.5.2-2)
  • Migration status for rust-webbrowser (- to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-webbrowser/0.5.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-webbrowser.html
  • 149 days old (needed 5 days)
• rust-x11-clipboard (- to 0.5.1-2)
  • Migration status for rust-x11-clipboard (- to 0.5.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-x11-clipboard/0.5.1-2: amd64: Regression ♻ , arm64: No test results
  • Build-Depends(-Arch): rust-x11-clipboard rust-xcb
  • Depends: rust-x11-clipboard rust-xcb
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-x11-clipboard.html
  • 149 days old (needed 5 days)
• pytest-services (- to 2.0.1-2)
  • Migration status for pytest-services (- to 2.0.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): pytest-services mysql-5.7 (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-services.html
  • Required age reduced by 3 days because of autopkgtest
  • 150 days old (needed 2 days)
• rust-pbkdf2 (- to 0.3.0-1)
  • Migration status for rust-pbkdf2 (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-pbkdf2+base64-dev/amd64 has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/amd64 has unsatisfiable dependency
  • librust-pbkdf2+base64-dev/arm64 has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/arm64 has unsatisfiable dependency
  • librust-pbkdf2+base64-dev/armel has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/armel has unsatisfiable dependency
  • librust-pbkdf2+base64-dev/armhf has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/armhf has unsatisfiable dependency
  • librust-pbkdf2+base64-dev/i386 has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/i386 has unsatisfiable dependency
  • librust-pbkdf2+base64-dev/mips64el has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/mips64el has unsatisfiable dependency
  • librust-pbkdf2+base64-dev/mipsel has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/mipsel has unsatisfiable dependency
  • librust-pbkdf2+base64-dev/ppc64el has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/ppc64el has unsatisfiable dependency
  • librust-pbkdf2+base64-dev/s390x has unsatisfiable dependency
  • librust-pbkdf2+include-simple-dev/s390x has unsatisfiable dependency
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on amd64: librust-base64-0.10+default-dev
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on arm64: librust-base64-0.10+default-dev
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armel: librust-base64-0.10+default-dev
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armhf: librust-base64-0.10+default-dev
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on i386: librust-base64-0.10+default-dev
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-base64-0.10+default-dev
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-base64-0.10+default-dev
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-base64-0.10+default-dev
  • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on s390x: librust-base64-0.10+default-dev
  • Not built on buildd: arch amd64 binaries uploaded by infinity0
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-pbkdf2.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 150 days old (needed 5 days)
• rust-tokio-process (- to 0.2.4-1)
  • Migration status for rust-tokio-process (- to 0.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-tokio-process-dev/amd64 has unsatisfiable dependency
  • librust-tokio-process-dev/arm64 has unsatisfiable dependency
  • librust-tokio-process-dev/armel has unsatisfiable dependency
  • librust-tokio-process-dev/armhf has unsatisfiable dependency
  • librust-tokio-process-dev/i386 has unsatisfiable dependency
  • librust-tokio-process-dev/mips64el has unsatisfiable dependency
  • librust-tokio-process-dev/mipsel has unsatisfiable dependency
  • librust-tokio-process-dev/ppc64el has unsatisfiable dependency
  • librust-tokio-process-dev/s390x has unsatisfiable dependency
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • rust-tokio-process unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-queue-0.1+default-dev (>= 0.1.2-~~)
  • Not built on buildd: arch amd64 binaries uploaded by infinity0
  • Build-Depends(-Arch): rust-tokio-process rust-tokio-signal
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-process.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 150 days old (needed 5 days)
• ndpi (2.6-5 to 3.0-1)
  • Migration status for ndpi (2.6-5 to 3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ndpi introduces new bugs: #950404
  • Not built on buildd: arch amd64 binaries uploaded by cavedon
  • missing build on arm64
  • missing build on i386
  • missing build on ppc64el
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Updating ndpi fixes old bugs: #953181
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ndpi.html
  • 151 days old (needed 5 days)
• openturns (- to 1.14-1)
  • Migration status for openturns (- to 1.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openturns introduces new bugs: #937214, #948602
  • missing build on arm64
  • missing build on i386
  • missing build on ppc64el
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openturns.html
  • 151 days old (needed 5 days)
• python-psycogreen (- to 1.0.1-1)
  • Migration status for python-psycogreen (- 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 onlyjob@member.fsf.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-psycogreen.html
  • 151 days old (needed 5 days)
• rust-trust-dns-proto (- to 0.8.0-1)
  • Migration status for rust-trust-dns-proto (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-trust-dns-proto-dev/amd64 has unsatisfiable dependency
  • librust-trust-dns-proto-dev/arm64 has unsatisfiable dependency
  • librust-trust-dns-proto-dev/armel has unsatisfiable dependency
  • librust-trust-dns-proto-dev/armhf has unsatisfiable dependency
  • librust-trust-dns-proto-dev/i386 has unsatisfiable dependency
  • librust-trust-dns-proto+dnssec-ring-dev/mips64el has unsatisfiable dependency
  • librust-trust-dns-proto+ring-dev/mips64el has unsatisfiable dependency
  • librust-trust-dns-proto-dev/mips64el has unsatisfiable dependency
  • librust-trust-dns-proto+dnssec-ring-dev/mipsel has unsatisfiable dependency
  • librust-trust-dns-proto+ring-dev/mipsel has unsatisfiable dependency
  • librust-trust-dns-proto-dev/mipsel has unsatisfiable dependency
  • librust-trust-dns-proto+dnssec-ring-dev/ppc64el has unsatisfiable dependency
  • librust-trust-dns-proto+ring-dev/ppc64el has unsatisfiable dependency
  • librust-trust-dns-proto-dev/ppc64el has unsatisfiable dependency
  • librust-trust-dns-proto+dnssec-ring-dev/s390x has unsatisfiable dependency
  • librust-trust-dns-proto+ring-dev/s390x has unsatisfiable dependency
  • librust-trust-dns-proto-dev/s390x has unsatisfiable dependency
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on amd64: librust-smallvec-0.6+default-dev
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on arm64: librust-smallvec-0.6+default-dev
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armel: librust-smallvec-0.6+default-dev
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armhf: librust-smallvec-0.6+default-dev
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on i386: librust-smallvec-0.6+default-dev
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mips64el: librust-smallvec-0.6+default-dev
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mipsel: librust-smallvec-0.6+default-dev
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on ppc64el: librust-smallvec-0.6+default-dev
  • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on s390x: librust-smallvec-0.6+default-dev
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Build-Depends(-Arch): rust-trust-dns-proto rust-tokio-udp
  • Depends: rust-trust-dns-proto rust-ring
  • Depends: rust-trust-dns-proto rust-tokio-tcp
  • Depends: rust-trust-dns-proto rust-tokio-udp
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-trust-dns-proto.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 151 days old (needed 5 days)
• pyglossary (- to 3.2.1-1)
  • Migration status for pyglossary (- to 3.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by emfox, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyglossary.html
  • 152 days old (needed 5 days)
• centreon-broker (- to 19.10.2-1)
  • Migration status for centreon-broker (- to 19.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • centreon-broker/amd64 has unsatisfiable dependency
  • centreon-broker/arm64 has unsatisfiable dependency
  • centreon-broker/armel has unsatisfiable dependency
  • centreon-broker/armhf has unsatisfiable dependency
  • centreon-broker/i386 has unsatisfiable dependency
  • centreon-broker/mips64el has unsatisfiable dependency
  • centreon-broker/ppc64el has unsatisfiable dependency
  • centreon-broker/s390x has unsatisfiable dependency
  • Updating centreon-broker introduces new bugs: #939626
  • centreon-broker unsatisfiable Build-Depends(-Arch) on amd64: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on amd64: libqt4-opengl-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on arm64: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on arm64: libqt4-opengl-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on armel: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on armel: libqt4-opengl-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on armhf: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on armhf: libqt4-opengl-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on i386: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on i386: libqt4-opengl-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on mips64el: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on mips64el: libqt4-opengl-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on mipsel: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on mipsel: libqt4-opengl-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on ppc64el: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on ppc64el: libqt4-opengl-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on s390x: libqt4-dev
  • centreon-broker unsatisfiable Build-Depends(-Arch) on s390x: libqt4-opengl-dev
  • Not built on buildd: arch amd64 binaries uploaded by seb
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/centreon-broker.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 153 days old (needed 5 days)
• centreon-engine (- to 19.10.8-1)
  • Migration status for centreon-engine (- to 19.10.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating centreon-engine introduces new bugs: #948491
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/centreon-engine.html
  • 153 days old (needed 5 days)
• gajim-lengthnotifier (- to 1.1.0-1)
  • Migration status for gajim-lengthnotifier (- 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 debacle, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gajim-lengthnotifier.html
  • 153 days old (needed 5 days)
• nomad-driver-lxc (- to 0.1.0-1)
  • Migration status for nomad-driver-lxc (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for nomad-driver-lxc/0.1.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • nomad-driver-lxc unsatisfiable Build-Depends(-Arch) on armel: golang-github-hashicorp-nomad-dev
  • nomad-driver-lxc/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • nomad-driver-lxc/arm64 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • nomad-driver-lxc/armel has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • nomad-driver-lxc/armhf has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • nomad-driver-lxc/i386 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • nomad-driver-lxc/mips64el has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • nomad-driver-lxc/mipsel has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • nomad-driver-lxc/ppc64el has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • nomad-driver-lxc/s390x has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • Not built on buildd: arch amd64 binaries uploaded by onlyjob@member.fsf.org
  • Build-Depends(-Arch): nomad-driver-lxc nomad
  • Built-Using: nomad-driver-lxc nomad
  • Depends: nomad-driver-lxc nomad
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomad-driver-lxc.html
  • 153 days old (needed 5 days)
• golang-github-census-instrumentation-opencensus-proto (- to 0.2.1+dfsg1-1)
  • Migration status for golang-github-census-instrumentation-opencensus-proto (- to 0.2.1+dfsg1-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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-census-instrumentation-opencensus-proto.html
  • Required age reduced by 3 days because of autopkgtest
  • 154 days old (needed 2 days)
• golang-github-rsc-devweb (- to 0.0.0+2016.01.15.git.29cc9e1b05-1)
  • Migration status for golang-github-rsc-devweb (- to 0.0.0+2016.01.15.git.29cc9e1b05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • golang-github-rsc-devweb/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.4-1
  • golang-github-rsc-devweb/arm64 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • golang-github-rsc-devweb/armel has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • golang-github-rsc-devweb/armhf has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • golang-github-rsc-devweb/i386 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • golang-github-rsc-devweb/mips64el has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • golang-github-rsc-devweb/mipsel has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • golang-github-rsc-devweb/ppc64el has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • golang-github-rsc-devweb/s390x has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • Not built on buildd: arch amd64 binaries uploaded by zigo
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-rsc-devweb.html
  • 154 days old (needed 5 days)
• ntopng (3.8+dfsg1-2.1 to 3.8.1+dfsg1-1)
  • Migration status for ntopng (3.8+dfsg1-2.1 to 3.8.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ntopng unsatisfiable Build-Depends(-Arch) on arm64: libndpi-dev (>= 3.0~)
  • ntopng unsatisfiable Build-Depends(-Arch) on i386: libndpi-dev (>= 3.0~)
  • ntopng unsatisfiable Build-Depends(-Arch) on ppc64el: libndpi-dev (>= 3.0~)
  • ntopng unsatisfiable Build-Depends(-Arch) on s390x: libndpi-dev (>= 3.0~)
  • Not built on buildd: arch amd64 binaries uploaded by cavedon
  • Not built on buildd: arch all binaries uploaded by cavedon, a new source-only upload is needed to allow migration
  • missing build on arm64
  • missing build on i386
  • missing build on ppc64el
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Build-Depends(-Arch): ntopng ndpi
  • Depends: ntopng ndpi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntopng.html
  • 155 days old (needed 5 days)
• rust-syscallz (- to 0.12.0-1)
  • Migration status for rust-syscallz (- to 0.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-syscallz-dev/amd64 has unsatisfiable dependency
  • librust-syscallz-dev/armel has unsatisfiable dependency
  • librust-syscallz-dev/armhf has unsatisfiable dependency
  • librust-syscallz-dev/i386 has unsatisfiable dependency
  • librust-syscallz-dev/ppc64el has unsatisfiable dependency
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on amd64: librust-strum-macros-0.15+default-dev
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on arm64: librust-strum-macros-0.15+default-dev
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on armel: librust-strum-macros-0.15+default-dev
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on armhf: librust-strum-macros-0.15+default-dev
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on i386: librust-strum-macros-0.15+default-dev
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on mips64el: librust-strum-macros-0.15+default-dev
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on mipsel: librust-strum-macros-0.15+default-dev
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on ppc64el: librust-strum-macros-0.15+default-dev
  • rust-syscallz unsatisfiable Build-Depends(-Arch) on s390x: librust-strum-macros-0.15+default-dev
  • missing build on arm64
  • missing build on mips64el
  • missing build on mipsel
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-syscallz.html
  • uninstallable on arch amd64, not running autopkgtest there
  • 155 days old (needed 5 days)
• derpconf (- to 0.8.2-3)
  • Migration status for derpconf (- to 0.8.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by metal, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/derpconf.html
  • 156 days old (needed 5 days)
• jupyter-sphinx (- to 0.2.3-1)
  • Migration status for jupyter-sphinx (- to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jupyter-sphinx introduces new bugs: #950598
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-sphinx.html
  • 156 days old (needed 5 days)
• q2-types (- to 2019.10.0-1)
  • Migration status for q2-types (- to 2019.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • q2-types/i386 has unsatisfiable dependency
  • Build-Depends(-Arch): q2-types qiime
  • Depends: q2-types qiime
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-types.html
  • Required age reduced by 3 days because of autopkgtest
  • 156 days old (needed 2 days)
• squaremap (- to 1:1.0.5-1)
  • Migration status for squaremap (- to 1:1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squaremap.html
  • 156 days old (needed 5 days)
• dirspec (- to 13.10-1.1)
  • Migration status for dirspec (- to 13.10-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dirspec introduces new bugs: #949937
  • dirspec unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dirspec.html
  • 157 days old (needed 5 days)
• lmfit-py (- to 1.0.0-1)
  • Migration status for lmfit-py (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lmfit-py introduces new bugs: #947265
  • Build-Depends(-Arch): lmfit-py uncertainties
  • Depends: lmfit-py uncertainties
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lmfit-py.html
  • Required age reduced by 3 days because of autopkgtest
  • 157 days old (needed 2 days)
• php-fig-link-util (- to 1.1.0-1)
  • Migration status for php-fig-link-util (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-fig-link-util introduces new bugs: #947346
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fig-link-util.html
  • Required age reduced by 3 days because of autopkgtest
  • 157 days old (needed 2 days)
• python-intervaltree-bio (- to 1.0.1-3.1)
  • Migration status for python-intervaltree-bio (- to 1.0.1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-intervaltree-bio introduces new bugs: #920545
  • autopkgtest for python-intervaltree-bio/1.0.1-3.1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-intervaltree-bio.html
  • 157 days old (needed 5 days)
• greylistd (- to 0.8.8.8)
  • Migration status for greylistd (- to 0.8.8.8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating greylistd introduces new bugs: #948706
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/greylistd.html
  • 158 days old (needed 5 days)
• linphone (- to 3.12.0-3.1)
  • Migration status for linphone (- to 3.12.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating linphone introduces new bugs: #943162
  • linphone unsatisfiable Build-Depends(-Arch) on amd64: python-pystache
  • linphone unsatisfiable Build-Depends(-Arch) on arm64: python-pystache
  • linphone unsatisfiable Build-Depends(-Arch) on armel: python-pystache
  • linphone unsatisfiable Build-Depends(-Arch) on armhf: python-pystache
  • linphone unsatisfiable Build-Depends(-Arch) on i386: python-pystache
  • linphone unsatisfiable Build-Depends(-Arch) on mips64el: python-pystache
  • linphone unsatisfiable Build-Depends(-Arch) on mipsel: python-pystache
  • linphone unsatisfiable Build-Depends(-Arch) on ppc64el: python-pystache
  • linphone unsatisfiable Build-Depends(-Arch) on s390x: python-pystache
  • Build-Depends(-Arch): linphone belle-sip
  • Depends: linphone belle-sip
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linphone.html
  • 159 days old (needed 5 days)
• rkt (- to 1.30.0+dfsg1-9)
  • Migration status for rkt (- to 1.30.0+dfsg1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rkt introduces new bugs: #929781
  • rkt/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • rkt/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • rkt/arm64 has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • rkt/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20180124.0ed95ab+dfsg-2
  • rkt/armel has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • rkt/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • rkt/armhf has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • rkt/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • rkt/i386 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • rkt/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • rkt/ppc64el has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • rkt/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20180124.0ed95ab+dfsg-2
  • missing build on arm64
  • missing build on ppc64el
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rkt.html
  • 160 days old (needed 5 days)
• gitbatch (- to 0.5.0-2)
  • Migration status for gitbatch (- to 0.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • gitbatch/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • gitbatch/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • gitbatch/arm64 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • gitbatch/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • gitbatch/armel has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • gitbatch/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • gitbatch/armhf has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • gitbatch/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • gitbatch/i386 has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • gitbatch/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • gitbatch/ppc64el has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • gitbatch/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • gitbatch/s390x has unsatisfiable Built-Using on golang-1.13 1.13.5-1
  • gitbatch/s390x has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20191112.2180aed+dfsg-1
  • Build-Depends(-Arch): gitbatch golang-gopkg-src-d-go-git.v4
  • Built-Using: gitbatch golang-github-src-d-gcfg
  • Built-Using: gitbatch golang-gopkg-src-d-go-git.v4
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitbatch.html
  • Required age reduced by 3 days because of autopkgtest
  • 162 days old (needed 2 days)
• norsnet (- to 1.0.17-6)
  • Migration status for norsnet (- to 1.0.17-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: norsnet profnet (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/norsnet.html
  • Required age reduced by 3 days because of autopkgtest
  • 162 days old (needed 2 days)
• runsnakerun (- to 2.0.5-1)
  • Migration status for runsnakerun (- to 2.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Depends: runsnakerun squaremap
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/runsnakerun.html
  • 162 days old (needed 5 days)
• pathspider (- to 2.0.1-2.1)
  • Migration status for pathspider (- to 2.0.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pathspider introduces new bugs: #906500
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pathspider.html
  • 164 days old (needed 5 days)
• q2cli (- to 2019.10.0-1)
  • Migration status for q2cli (- to 2019.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating q2cli introduces new bugs: #954601
  • Build-Depends(-Arch): q2cli qiime
  • Depends: q2cli qiime
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2cli.html
  • Required age reduced by 3 days because of autopkgtest
  • 164 days old (needed 2 days)
• qiime (- to 2019.10.0-1)
  • Migration status for qiime (- to 2019.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating qiime introduces new bugs: #950842
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiime.html
  • Required age reduced by 3 days because of autopkgtest
  • 164 days old (needed 2 days)
• check-all-the-things (- to 2017.05.20+nmu1)
  • Migration status for check-all-the-things (- to 2017.05.20+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating check-all-the-things introduces new bugs: #862378
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-all-the-things.html
  • 165 days old (needed 5 days)
• sambamba (- to 0.7.1-1)
  • Migration status for sambamba (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sambamba introduces new bugs: #948919
  • missing build on amd64
  • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sambamba.html
  • 165 days old (needed 5 days)
• bareos (- to 17.2.7-2.1)
  • Migration status for bareos (- to 17.2.7-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • bareos-filedaemon-ldap-python-plugin/amd64 has unsatisfiable dependency
  • bareos-filedaemon-ldap-python-plugin/arm64 has unsatisfiable dependency
  • bareos-filedaemon-ldap-python-plugin/armel has unsatisfiable dependency
  • bareos-filedaemon-ldap-python-plugin/armhf has unsatisfiable dependency
  • bareos-filedaemon-ldap-python-plugin/i386 has unsatisfiable dependency
  • bareos-filedaemon-ldap-python-plugin/mips64el has unsatisfiable dependency
  • bareos-filedaemon-ldap-python-plugin/mipsel has unsatisfiable dependency
  • bareos-filedaemon-ldap-python-plugin/ppc64el has unsatisfiable dependency
  • bareos-filedaemon-ldap-python-plugin/s390x has unsatisfiable dependency
  • Updating bareos introduces new bugs: #922344, #936185
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bareos.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 166 days old (needed 5 days)
• mysql-connector-python (- to 8.0.15-2)
  • Migration status for mysql-connector-python (- to 8.0.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mysql-connector-python introduces new bugs: #923347
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-connector-python.html
  • 167 days old (needed 5 days)
• predictprotein (- to 1.1.09-2)
  • Migration status for predictprotein (- to 1.1.09-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: predictprotein profphd (not considered)
  • Invalidated by dependency
  • Depends: predictprotein norsnet
  • Depends: predictprotein profbval
  • Depends: predictprotein profisis
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/predictprotein.html
  • uninstallable on arch arm64, not running autopkgtest there
  • 168 days old (needed 5 days)
• lysdr (- to 1.0~git20141206+dfsg1-2)
  • Migration status for lysdr (- to 1.0~git20141206+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lysdr introduces new bugs: #936974
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lysdr.html
  • 169 days old (needed 5 days)
• haskell-dhall (- to 1.19.1-1)
  • Migration status for haskell-dhall (- to 1.19.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): haskell-dhall haskell-serialise
  • Build-Depends-Indep: haskell-dhall haskell-serialise
  • Depends: haskell-dhall haskell-serialise
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-dhall.html
  • 170 days old (needed 5 days)
• haskell-hindent (- to 5.3.1-1)
  • Migration status for haskell-hindent (- to 5.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-hindent introduces new bugs: #960353
  • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hindent.html
  • 170 days old (needed 5 days)
• php-psr-event-dispatcher (- to 1.0.0-1)
  • Migration status for php-psr-event-dispatcher (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-psr-event-dispatcher.html
  • 170 days old (needed 5 days)
• ganeti (- to 2.16.1-2)
  • Migration status for ganeti (- to 2.16.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ganeti-2.16/amd64 has unsatisfiable dependency
  • ganeti-testsuite/amd64 has unsatisfiable dependency
  • python-ganeti-rapi/amd64 has unsatisfiable dependency
  • ganeti-2.16/i386 has unsatisfiable dependency
  • ganeti-testsuite/i386 has unsatisfiable dependency
  • python-ganeti-rapi/i386 has unsatisfiable dependency
  • Updating ganeti introduces new bugs: #935677, #936580
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 1.0.7+dfsg)
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx (>= 1.0.7+dfsg)
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on armel: python-sphinx (>= 1.0.7+dfsg)
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx (>= 1.0.7+dfsg)
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on i386: python-sphinx (>= 1.0.7+dfsg)
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx (>= 1.0.7+dfsg)
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx (>= 1.0.7+dfsg)
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx (>= 1.0.7+dfsg)
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-simplejson
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-pyparsing
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-openssl
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-bitarray
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-pyinotify
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-pycurl
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-paramiko
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-ipaddr
  • ganeti unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx (>= 1.0.7+dfsg)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganeti.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 172 days old (needed 5 days)
• ladish (- to 1+dfsg0-6)
  • Migration status for ladish (- to 1+dfsg0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ladish introduces new bugs: #936812
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ladish.html
  • 172 days old (needed 5 days)
• python-whiteboard (- to 1.0+git20170915-3)
  • Migration status for python-whiteboard (- to 1.0+git20170915-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-whiteboard/amd64 has unsatisfiable dependency
  • python3-whiteboard/i386 has unsatisfiable dependency
  • Updating python-whiteboard introduces new bugs: #952496
  • Not built on buildd: arch all binaries uploaded by georgesk, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-whiteboard.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 174 days old (needed 5 days)
• stimfit (- to 0.16.0-1)
  • Migration status for stimfit (- to 0.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating stimfit introduces new bugs: #948020, #951824
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stimfit.html
  • 174 days old (needed 5 days)
• pycorrfit (- to 1.1.7+dfsg-1)
  • Migration status for pycorrfit (- to 1.1.7+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): pycorrfit lmfit-py (not considered)
  • Depends: pycorrfit lmfit-py (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycorrfit.html
  • Required age reduced by 3 days because of autopkgtest
  • 176 days old (needed 2 days)
• uvloop (- to 0.14.0+ds1-1)
  • Migration status for uvloop (- to 0.14.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating uvloop introduces new bugs: #950165
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uvloop.html
  • 176 days old (needed 5 days)
• incron (- to 0.5.12-2)
  • Migration status for incron (- to 0.5.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating incron introduces new bugs: #947425
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/incron.html
  • 177 days old (needed 5 days)
• zorp (- to 7.0.1~alpha2-3)
  • Migration status for zorp (- to 7.0.1~alpha2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • zorp/amd64 has unsatisfiable dependency
  • zorp/arm64 has unsatisfiable dependency
  • zorp/armel has unsatisfiable dependency
  • zorp/armhf has unsatisfiable dependency
  • zorp/i386 has unsatisfiable dependency
  • zorp/mips64el has unsatisfiable dependency
  • zorp/mipsel has unsatisfiable dependency
  • zorp/ppc64el has unsatisfiable dependency
  • zorp/s390x has unsatisfiable dependency
  • Updating zorp introduces new bugs: #938921, #953377
  • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-netaddr
  • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-netaddr
  • zorp unsatisfiable Build-Depends(-Arch) on armel: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on armel: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on armel: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on armel: python-netaddr
  • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-netaddr
  • zorp unsatisfiable Build-Depends(-Arch) on i386: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on i386: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on i386: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on i386: python-netaddr
  • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-netaddr
  • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-netaddr
  • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-netaddr
  • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-dnspython
  • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-openssl (>= 0.10)
  • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-radix
  • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-netaddr
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zorp.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 178 days old (needed 5 days)
• haskell-gtk-sni-tray (- to 0.1.6.0-1)
  • Migration status for haskell-gtk-sni-tray (- to 0.1.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: haskell-gtk-sni-tray haskell-gi-gdk (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gtk-strut
  • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gtk-strut
  • Depends: haskell-gtk-sni-tray haskell-gi-dbusmenugtk3
  • Depends: haskell-gtk-sni-tray haskell-gi-gtk
  • Depends: haskell-gtk-sni-tray haskell-gtk-strut
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gtk-sni-tray.html
  • 180 days old (needed 5 days)
• ruby-serverengine (- to 2.2.0-1)
  • Migration status for ruby-serverengine (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ruby-serverengine introduces new bugs: #951806
  • autopkgtest for ruby-serverengine/2.2.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-serverengine.html
  • 180 days old (needed 5 days)
• vala-panel-appmenu (- to 0.7.3+dfsg1-2)
  • Migration status for vala-panel-appmenu (- to 0.7.3+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vala-panel-appmenu introduces new bugs: #951968
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vala-panel-appmenu.html
  • 184 days old (needed 5 days)
• odin (- to 2.0.3-2)
  • Migration status for odin (- to 2.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating odin introduces new bugs: #953064
  • missing build on i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odin.html
  • 190 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fst.html
  • 196 days old (needed 5 days)
• golang-github-getlantern-errors (- to 0.0~git20190325.abdb3e3-2)
  • Migration status for golang-github-getlantern-errors (- to 0.0~git20190325.abdb3e3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for golang-github-getlantern-errors/0.0~git20190325.abdb3e3-2: amd64: Pass, arm64: Regression ♻
  • Build-Depends(-Arch): golang-github-getlantern-errors golang-github-getlantern-ops
  • Depends: golang-github-getlantern-errors golang-github-getlantern-hex
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-errors.html
  • 196 days old (needed 5 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): golang-github-getlantern-hidden golang-github-getlantern-hex (not considered)
  • Depends: golang-github-getlantern-hidden golang-github-getlantern-hex (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • 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
  • 196 days old (needed 2 days)
• pympler (- to 0.7+dfsg1-1)
  • Migration status for pympler (- to 0.7+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pympler introduces new bugs: #946265
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pympler.html
  • 196 days old (needed 5 days)
• hg-git (- to 0.8.12-1.2)
  • Migration status for hg-git (- to 0.8.12-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mercurial-git/amd64 has unsatisfiable dependency
  • mercurial-git/i386 has unsatisfiable dependency
  • Updating hg-git introduces new bugs: #936699
  • hg-git unsatisfiable Build-Depends(-Arch) on amd64: python-dulwich
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hg-git.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 197 days old (needed 5 days)
• golang-gopkg-go-playground-colors.v1 (- to 1.2.0-2)
  • Migration status for golang-gopkg-go-playground-colors.v1 (- to 1.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-gopkg-go-playground-colors.v1 introduces new bugs: #954559
  • autopkgtest for golang-gopkg-go-playground-colors.v1/1.2.0-2: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gopkg-go-playground-colors.v1.html
  • 198 days old (needed 5 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
  • 198 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sop.html
  • Required age reduced by 3 days because of autopkgtest
  • 198 days old (needed 2 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:
  • librust-selectors-dev/amd64 has unsatisfiable dependency
  • librust-selectors-dev/arm64 has unsatisfiable dependency
  • librust-selectors-dev/armel has unsatisfiable dependency
  • librust-selectors-dev/armhf has unsatisfiable dependency
  • librust-selectors-dev/i386 has unsatisfiable dependency
  • librust-selectors-dev/mips64el has unsatisfiable dependency
  • librust-selectors-dev/mipsel has unsatisfiable dependency
  • librust-selectors-dev/ppc64el has unsatisfiable dependency
  • librust-selectors-dev/s390x has unsatisfiable dependency
  • Updating rust-selectors introduces new bugs: #951683
  • rust-selectors unsatisfiable Build-Depends(-Arch) on amd64: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on amd64: librust-smallvec-0.6+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on arm64: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on arm64: librust-smallvec-0.6+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on armel: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on armel: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on armel: librust-smallvec-0.6+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on armhf: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on armhf: librust-smallvec-0.6+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on i386: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on i386: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on i386: librust-smallvec-0.6+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on mips64el: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on mips64el: librust-smallvec-0.6+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on mipsel: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on mipsel: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on mipsel: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on mipsel: librust-smallvec-0.6+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on ppc64el: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on ppc64el: librust-smallvec-0.6+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on s390x: librust-cssparser-0.25+default-dev
  • rust-selectors unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
  • rust-selectors unsatisfiable Build-Depends(-Arch) on s390x: librust-smallvec-0.6+default-dev
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Build-Depends(-Arch): rust-selectors rust-servo-arc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-selectors.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 198 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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bzr-loom.html
  • 199 days old (needed 5 days)
• 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intellij-java-compatibility.html
  • 199 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:
  • Updating medialibrary introduces new bugs: #949532
  • Not built on buildd: arch amd64 binaries uploaded by s.ramacher@gmail.com
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/medialibrary.html
  • 199 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyperform.html
  • 199 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:
  • q2-feature-classifier/i386 has unsatisfiable dependency
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): q2-feature-classifier q2-types
  • Depends: q2-feature-classifier q2-types
  • Depends: q2-feature-classifier qiime
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-feature-classifier.html
  • uninstallable on arch arm64, not running autopkgtest there
  • Required age reduced by 3 days because of autopkgtest
  • 199 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:
  • Updating vdjtools introduces new bugs: #946492
  • autopkgtest for vdjtools/1.2.1+git20190311-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 199 days old (needed 5 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-toqueteos-webbrowser.html
  • Required age reduced by 3 days because of autopkgtest
  • 200 days old (needed 2 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/testinfra.html
  • 200 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
  • 201 days old (needed 2 days)
• abinit (- to 8.10.3-2)
  • Migration status for abinit (- to 8.10.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating abinit introduces new bugs: #936105
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abinit.html
  • Required age reduced by 3 days because of autopkgtest
  • 202 days old (needed 2 days)
• node-hawk (- to 7.1.2+dfsg-1)
  • Migration status for node-hawk (- to 7.1.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for node-hawk/7.1.2+dfsg-1: amd64: No test results, arm64: Regression ♻
  • Build-Depends(-Arch): node-hawk node-cryptiles
  • Depends: node-hawk node-boom
  • Depends: node-hawk node-cryptiles
  • Depends: node-hawk node-sntp
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-hawk.html
  • 206 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-jemalloc-sys rust-fs-extra (not considered)
  • Depends: rust-jemalloc-sys rust-fs-extra (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-jemalloc-sys.html
  • Required age reduced by 3 days because of autopkgtest
  • 206 days old (needed 2 days)
• rust-process-viewer (- to 0.2.6-1)
  • Migration status for rust-process-viewer (- to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-process-viewer introduces new bugs: #954613
  • rust-process-viewer unsatisfiable Build-Depends(-Arch) on amd64: librust-sysinfo-0.9+default-dev
  • rust-process-viewer unsatisfiable Build-Depends(-Arch) on arm64: librust-sysinfo-0.9+default-dev
  • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armel: librust-sysinfo-0.9+default-dev
  • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armhf: librust-sysinfo-0.9+default-dev
  • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mips64el: librust-sysinfo-0.9+default-dev
  • rust-process-viewer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-sysinfo-0.9+default-dev
  • rust-process-viewer unsatisfiable Build-Depends(-Arch) on s390x: librust-sysinfo-0.9+default-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-process-viewer.html
  • 206 days old (needed 5 days)
• swiftsc (- to 0.5-1.1)
  • Migration status for swiftsc (- to 0.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating swiftsc introduces new bugs: #949933, #952353
  • swiftsc unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swiftsc.html
  • 206 days old (needed 5 days)
• python-libusb1 (- to 1.7-2)
  • Migration status for python-libusb1 (- to 1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-libusb1 introduces new bugs: #944020
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-libusb1.html
  • 207 days old (needed 5 days)
• python-bayespy (- to 0.5.18-2)
  • Migration status for python-bayespy (- to 0.5.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-bayespy introduces new bugs: #954590
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bayespy.html
  • Required age reduced by 3 days because of autopkgtest
  • 208 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:
  • librust-combine+combine-regex-1-dev/amd64 has unsatisfiable dependency
  • librust-combine+doc-dev/amd64 has unsatisfiable dependency
  • librust-combine+regex-dev/amd64 has unsatisfiable dependency
  • librust-combine+combine-regex-1-dev/arm64 has unsatisfiable dependency
  • librust-combine+doc-dev/arm64 has unsatisfiable dependency
  • librust-combine+regex-dev/arm64 has unsatisfiable dependency
  • librust-combine+combine-regex-1-dev/armel has unsatisfiable dependency
  • librust-combine+doc-dev/armel has unsatisfiable dependency
  • librust-combine+regex-dev/armel has unsatisfiable dependency
  • librust-combine+combine-regex-1-dev/armhf has unsatisfiable dependency
  • librust-combine+doc-dev/armhf has unsatisfiable dependency
  • librust-combine+regex-dev/armhf has unsatisfiable dependency
  • librust-combine+combine-regex-1-dev/i386 has unsatisfiable dependency
  • librust-combine+doc-dev/i386 has unsatisfiable dependency
  • librust-combine+regex-dev/i386 has unsatisfiable dependency
  • librust-combine+combine-regex-1-dev/mips64el has unsatisfiable dependency
  • librust-combine+doc-dev/mips64el has unsatisfiable dependency
  • librust-combine+regex-dev/mips64el has unsatisfiable dependency
  • librust-combine+combine-regex-1-dev/mipsel has unsatisfiable dependency
  • librust-combine+doc-dev/mipsel has unsatisfiable dependency
  • librust-combine+regex-dev/mipsel has unsatisfiable dependency
  • librust-combine+combine-regex-1-dev/ppc64el has unsatisfiable dependency
  • librust-combine+doc-dev/ppc64el has unsatisfiable dependency
  • librust-combine+regex-dev/ppc64el has unsatisfiable dependency
  • librust-combine+combine-regex-1-dev/s390x has unsatisfiable dependency
  • librust-combine+doc-dev/s390x has unsatisfiable dependency
  • librust-combine+regex-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-combine.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 208 days old (needed 5 days)
• rust-ucd-generate (- to 0.2.3-1)
  • Migration status for rust-ucd-generate (- to 0.2.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-ucd-generate rust-ucd-trie (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ucd-generate.html
  • 208 days old (needed 5 days)
• rust-ucd-trie (- to 0.1.2-1)
  • Migration status for rust-ucd-trie (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-ucd-trie/0.1.2-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ucd-trie.html
  • 208 days old (needed 5 days)
• vdr-plugin-xineliboutput (- to 2.1.0+git20191101-1)
  • Migration status for vdr-plugin-xineliboutput (- to 2.1.0+git20191101-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vdr-plugin-xineliboutput introduces new bugs: #951921
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-xineliboutput.html
  • 208 days old (needed 5 days)
• dmarc-cat (- to 0.12.0-1)
  • Migration status for dmarc-cat (- to 0.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for dmarc-cat/0.12.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • dmarc-cat/amd64 has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • dmarc-cat/arm64 has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • dmarc-cat/armel has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • dmarc-cat/armhf has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • dmarc-cat/i386 has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • dmarc-cat/mips64el has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • dmarc-cat/mipsel has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • dmarc-cat/ppc64el has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • dmarc-cat/s390x has unsatisfiable Built-Using on golang-1.13 1.13.3-1
  • Build-Depends(-Arch): dmarc-cat golang-github-keltia-archive
  • Built-Using: dmarc-cat golang-github-keltia-archive
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dmarc-cat.html
  • 212 days old (needed 5 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
  • 212 days old (needed 5 days)
• rust-crossbeam (- to 0.7.2-2)
  • Migration status for rust-crossbeam (- to 0.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-crossbeam+alloc-dev/amd64 has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/amd64 has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/amd64 has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/amd64 has unsatisfiable dependency
  • librust-crossbeam+std-dev/amd64 has unsatisfiable dependency
  • librust-crossbeam-dev/amd64 has unsatisfiable dependency
  • librust-crossbeam+alloc-dev/arm64 has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/arm64 has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/arm64 has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/arm64 has unsatisfiable dependency
  • librust-crossbeam+std-dev/arm64 has unsatisfiable dependency
  • librust-crossbeam-dev/arm64 has unsatisfiable dependency
  • librust-crossbeam+alloc-dev/armel has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/armel has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/armel has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/armel has unsatisfiable dependency
  • librust-crossbeam+std-dev/armel has unsatisfiable dependency
  • librust-crossbeam-dev/armel has unsatisfiable dependency
  • librust-crossbeam+alloc-dev/armhf has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/armhf has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/armhf has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/armhf has unsatisfiable dependency
  • librust-crossbeam+std-dev/armhf has unsatisfiable dependency
  • librust-crossbeam-dev/armhf has unsatisfiable dependency
  • librust-crossbeam+alloc-dev/i386 has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/i386 has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/i386 has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/i386 has unsatisfiable dependency
  • librust-crossbeam+std-dev/i386 has unsatisfiable dependency
  • librust-crossbeam-dev/i386 has unsatisfiable dependency
  • librust-crossbeam+alloc-dev/mips64el has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/mips64el has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/mips64el has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/mips64el has unsatisfiable dependency
  • librust-crossbeam+std-dev/mips64el has unsatisfiable dependency
  • librust-crossbeam-dev/mips64el has unsatisfiable dependency
  • librust-crossbeam+alloc-dev/mipsel has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/mipsel has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/mipsel has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/mipsel has unsatisfiable dependency
  • librust-crossbeam+std-dev/mipsel has unsatisfiable dependency
  • librust-crossbeam-dev/mipsel has unsatisfiable dependency
  • librust-crossbeam+alloc-dev/ppc64el has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/ppc64el has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/ppc64el has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/ppc64el has unsatisfiable dependency
  • librust-crossbeam+std-dev/ppc64el has unsatisfiable dependency
  • librust-crossbeam-dev/ppc64el has unsatisfiable dependency
  • librust-crossbeam+alloc-dev/s390x has unsatisfiable dependency
  • librust-crossbeam+crossbeam-channel-dev/s390x has unsatisfiable dependency
  • librust-crossbeam+crossbeam-queue-dev/s390x has unsatisfiable dependency
  • librust-crossbeam+nightly-dev/s390x has unsatisfiable dependency
  • librust-crossbeam+std-dev/s390x has unsatisfiable dependency
  • librust-crossbeam-dev/s390x has unsatisfiable dependency
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-channel-0.3+default-dev (>= 0.3.9-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-epoch-0.7+std-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-epoch-0.7-dev (>= 0.7.2-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-queue-0.1+default-dev
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-utils-0.6+std-dev (>= 0.6.6-~~)
  • rust-crossbeam unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-utils-0.6-dev (>= 0.6.6-~~)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-crossbeam.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 212 days old (needed 5 days)
• backup2swift (- to 0.8-1.1)
  • Migration status for backup2swift (- to 0.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating backup2swift introduces new bugs: #949942
  • backup2swift unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Build-Depends(-Arch): backup2swift swiftsc
  • Depends: backup2swift swiftsc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backup2swift.html
  • 213 days old (needed 5 days)
• gandi-cli (- to 1.5-1)
  • Migration status for gandi-cli (- to 1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gandi-cli introduces new bugs: #922420
  • autopkgtest for gandi-cli/1.5-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gandi-cli.html
  • 213 days old (needed 5 days)
• golang-github-keltia-archive (- to 0.7.0-1)
  • Migration status for golang-github-keltia-archive (- 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 ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-keltia-archive.html
  • 213 days old (needed 5 days)
• python-pex (- to 1.1.14-3)
  • Migration status for python-pex (- to 1.1.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-pex introduces new bugs: #949472
  • autopkgtest for python-pex/1.1.14-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pex.html
  • 213 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
  • 213 days old (needed 5 days)
• lava (- to 2019.10-1)
  • Migration status for lava (- to 2019.10-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/l/lava.html
  • Additional info:
  • Required age reduced by 3 days because of autopkgtest
  • 215 days old (needed 2 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
  • 216 days old (needed 5 days)
• renpy (- to 7.3.5+dfsg-1)
  • Migration status for renpy (- to 7.3.5+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating renpy introduces new bugs: #938351
  • renpy unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx-bootstrap-theme
  • renpy unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx-bootstrap-theme
  • renpy unsatisfiable Build-Depends(-Arch) on armel: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on armel: python-sphinx-bootstrap-theme
  • renpy unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx-bootstrap-theme
  • renpy unsatisfiable Build-Depends(-Arch) on i386: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on i386: python-sphinx-bootstrap-theme
  • renpy unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx-bootstrap-theme
  • renpy unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx-bootstrap-theme
  • renpy unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx-bootstrap-theme
  • renpy unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx
  • renpy unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx-bootstrap-theme
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/renpy.html
  • 220 days old (needed 5 days)
• ruby-invisible-captcha (- to 0.12.2-2)
  • Migration status for ruby-invisible-captcha (- to 0.12.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ruby-invisible-captcha introduces new bugs: #952085
  • autopkgtest for ruby-invisible-captcha/0.12.2-2: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-invisible-captcha.html
  • 220 days old (needed 5 days)
• cdist (- to 6.0.2-1)
  • Migration status for cdist (- to 6.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cdist introduces new bugs: #955110
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdist.html
  • Required age reduced by 3 days because of autopkgtest
  • 222 days old (needed 2 days)
• rust-os-pipe (- to 0.9.1-1)
  • Migration status for rust-os-pipe (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-os-pipe/0.9.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-os-pipe.html
  • 222 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:
  • bro/amd64 has unsatisfiable dependency
  • bro/arm64 has unsatisfiable dependency
  • bro/i386 has unsatisfiable dependency
  • bro/mips64el has unsatisfiable dependency
  • bro/mipsel has unsatisfiable dependency
  • bro/ppc64el has unsatisfiable dependency
  • Updating bro introduces new bugs: #949043
  • missing build on armel
  • missing build on armhf
  • missing build on s390x
  • Build-Depends(-Arch): bro broker
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bro.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 224 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:
  • Depends: gcc-defaults-mipsen gcc-9-cross-mipsen (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-defaults-mipsen.html
  • autopkgtest for dolfin/2019.2.0~git20200218.027d9cc-6: amd64: Pass, arm64: Ignored failure
  • 224 days old (needed 5 days)
• rust-tokio-threadpool (- to 0.1.16-1)
  • Migration status for rust-tokio-threadpool (- to 0.1.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-tokio-threadpool-dev/amd64 has unsatisfiable dependency
  • librust-tokio-threadpool-dev/arm64 has unsatisfiable dependency
  • librust-tokio-threadpool-dev/armel has unsatisfiable dependency
  • librust-tokio-threadpool-dev/armhf has unsatisfiable dependency
  • librust-tokio-threadpool-dev/i386 has unsatisfiable dependency
  • librust-tokio-threadpool-dev/mips64el has unsatisfiable dependency
  • librust-tokio-threadpool-dev/mipsel has unsatisfiable dependency
  • librust-tokio-threadpool-dev/ppc64el has unsatisfiable dependency
  • librust-tokio-threadpool-dev/s390x has unsatisfiable dependency
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-queue-0.1+default-dev
  • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-utils-0.6+default-dev (>= 0.6.4-~~)
  • Build-Depends(-Arch): rust-tokio-threadpool rust-tokio-executor
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-threadpool.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 226 days old (needed 5 days)
• sysdig (- to 0.26.4-1)
  • Migration status for sysdig (- to 0.26.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sysdig introduces new bugs: #904489, #955279, #958643
  • Impossible Depends: sysdig -> libprotobuf17/3.6.1.3-2+b3/amd64
  • Impossible Depends: sysdig -> libprotobuf17/3.6.1.3-2+b3/arm64
  • Impossible Depends: sysdig -> libprotobuf17/3.6.1.3-2+b3/armel
  • Impossible Depends: sysdig -> libprotobuf17/3.6.1.3-2+b3/armhf
  • Impossible Depends: sysdig -> libprotobuf17/3.6.1.3-2+b3/i386
  • Impossible Depends: sysdig -> libprotobuf17/3.6.1.3-2+b3/ppc64el
  • Impossible Depends: sysdig -> libprotobuf17/3.6.1.3-2+b3/s390x
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysdig.html
  • 226 days old (needed 5 days)
• rust-pest (- to 2.1.2-1)
  • Migration status for rust-pest (- to 2.1.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-pest rust-ucd-trie (not considered)
  • Depends: rust-pest rust-ucd-trie (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pest.html
  • 227 days old (needed 5 days)
• genetic (- to 0.1.1b+git20170527.98255cb-1)
  • Migration status for genetic (- to 0.1.1b+git20170527.98255cb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-genetic/amd64 has unsatisfiable dependency
  • python3-genetic/i386 has unsatisfiable dependency
  • Updating genetic introduces new bugs: #951246
  • genetic unsatisfiable Build-Depends(-Arch) on amd64: python3-multiprocess
  • 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) - https://piuparts.debian.org/sid/source/g/genetic.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 228 days old (needed 5 days)
• python-lepl (- to 5.1.3-2.1)
  • Migration status for python-lepl (- to 5.1.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-lepl introduces new bugs: #950059
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lepl.html
  • 228 days old (needed 5 days)
• universal-ctags (- to 0+git20191013-1)
  • Migration status for universal-ctags (- to 0+git20191013-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating universal-ctags introduces new bugs: #956349
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mipsel
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/universal-ctags.html
  • 228 days old (needed 5 days)
• gspiceui (- to 1.2.36+dfsg-1)
  • Migration status for gspiceui (- to 1.2.36+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: gspiceui geda-gaf (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gspiceui.html
  • 235 days old (needed 5 days)
• socket-activate (- to 0.1-2)
  • Migration status for socket-activate (- to 0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating socket-activate introduces new bugs: #922504
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socket-activate.html
  • 236 days old (needed 5 days)
• highwayhash (- to 0~git20191002.0aaf66b-1)
  • Migration status for highwayhash (- to 0~git20191002.0aaf66b-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on arm64
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/highwayhash.html
  • 237 days old (needed 5 days)
• rust-hyper (- to 0.12.35-1)
  • Migration status for rust-hyper (- to 0.12.35-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-hyper rust-tokio-timer (not considered)
  • Invalidated by build-dependency
  • Depends: rust-hyper rust-tokio
  • Depends: rust-hyper rust-tokio-tcp
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hyper.html
  • 238 days old (needed 5 days)
• rust-hyper-tls (- to 0.3.2-2)
  • Migration status for rust-hyper-tls (- to 0.3.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-hyper-tls rust-hyper (not considered)
  • Depends: rust-hyper-tls rust-hyper (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hyper-tls.html
  • 238 days old (needed 5 days)
• assaultcube (- to 1.2.0.2.1-2)
  • Migration status for assaultcube (- to 1.2.0.2.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: assaultcube assaultcube-data (not considered)
  • Invalidated by dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 246 days old (needed 5 days)
• assaultcube-data (- to 1.2.0.2.1-3)
  • Migration status for assaultcube-data (- to 1.2.0.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating assaultcube-data introduces new bugs: #935669
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 246 days old (needed 5 days)
• desktopnova (- to 0.8.1-1.2)
  • Migration status for desktopnova (- to 0.8.1-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating desktopnova introduces new bugs: #651313
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/desktopnova.html
  • 247 days old (needed 5 days)
• tt-rss (- to 19.8+dfsg-1)
  • Migration status for tt-rss (- to 19.8+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: tt-rss php-gettext (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tt-rss.html
  • 247 days old (needed 5 days)
• python-limits (- to 1.3-2)
  • Migration status for python-limits (- to 1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-limits introduces new bugs: #949276
  • autopkgtest for python-limits/1.3-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-limits.html
  • 250 days old (needed 5 days)
• libgtk2-perl (- to 2:1.24993-1)
  • Migration status for libgtk2-perl (- to 2:1.24993-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libgtk2-perl/amd64 has unsatisfiable dependency
  • libgtk2-perl/arm64 has unsatisfiable dependency
  • libgtk2-perl/armel has unsatisfiable dependency
  • libgtk2-perl/armhf has unsatisfiable dependency
  • libgtk2-perl/i386 has unsatisfiable dependency
  • libgtk2-perl/mips64el has unsatisfiable dependency
  • libgtk2-perl/mipsel has unsatisfiable dependency
  • libgtk2-perl/ppc64el has unsatisfiable dependency
  • libgtk2-perl/s390x has unsatisfiable dependency
  • Updating libgtk2-perl introduces new bugs: #912860, #942135
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgtk2-perl.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 254 days old (needed 5 days)
• node-diffie-hellman (- to 5.0.3-2)
  • Migration status for node-diffie-hellman (- to 5.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating node-diffie-hellman introduces new bugs: #860939
  • missing build on all
  • arch:all not built yet, autopkgtest delayed
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-diffie-hellman.html
  • 254 days old (needed 5 days)
• php-sabredav (- to 1.8.12-8)
  • Migration status for php-sabredav (- to 1.8.12-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-sabredav introduces new bugs: #943210, #952356
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabredav.html
  • Required age reduced by 3 days because of autopkgtest
  • 256 days old (needed 2 days)
• android-platform-frameworks-data-binding (- to 2.2.2-4)
  • Migration status for android-platform-frameworks-data-binding (- to 2.2.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): android-platform-frameworks-data-binding android-platform-tools-base (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-frameworks-data-binding.html
  • 257 days old (needed 5 days)
• xfce4-sntray-plugin (- to 0.4.12-2)
  • Migration status for xfce4-sntray-plugin (- to 0.4.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xfce4-sntray-plugin introduces new bugs: #951981
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-sntray-plugin.html
  • 257 days old (needed 5 days)
• openhft-chronicle-wire (- to 1.1.13-2)
  • Migration status for openhft-chronicle-wire (- to 1.1.13-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openhft-chronicle-wire introduces new bugs: #893498
  • Build-Depends(-Arch): openhft-chronicle-wire openhft-chronicle-bytes
  • Depends: openhft-chronicle-wire openhft-chronicle-bytes
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openhft-chronicle-wire.html
  • 258 days old (needed 5 days)
• pytest-instafail (- to 0.3.0-2)
  • Migration status for pytest-instafail (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pytest-instafail introduces new bugs: #894705
  • autopkgtest for pytest-instafail/0.3.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-instafail.html
  • 258 days old (needed 5 days)
• android-platform-external-rappor (- to 9.0.0+r35-1)
  • Migration status for android-platform-external-rappor (- to 9.0.0+r35-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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-rappor.html
  • 259 days old (needed 5 days)
• android-platform-system-tools-hidl (- to 9.0.0+r45-1)
  • Migration status for android-platform-system-tools-hidl (- to 9.0.0+r45-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating android-platform-system-tools-hidl introduces new bugs: #959904
  • Not built on buildd: arch amd64 binaries uploaded by seamlikok@gmail.com
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-system-tools-hidl.html
  • 259 days old (needed 5 days)
• rust-sha1-asm (- to 0.4.3-2)
  • Migration status for rust-sha1-asm (- to 0.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-sha1-asm/0.4.3-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha1-asm.html
  • 259 days old (needed 5 days)
• streamex (- to 0.6.7-1)
  • Migration status for streamex (- to 0.6.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/streamex.html
  • 259 days old (needed 5 days)
• crypto-policies (- to 20190816git-1)
  • Migration status for crypto-policies (- to 20190816git-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating crypto-policies introduces new bugs: #940017
  • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crypto-policies.html
  • 260 days old (needed 5 days)
• golang-github-shurcool-httpfs (- to 0.0~git20190707.8d4bc4b-1)
  • Migration status for golang-github-shurcool-httpfs (- to 0.0~git20190707.8d4bc4b-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
  • Build-Depends(-Arch): golang-github-shurcool-httpfs golang-github-shurcool-httpgzip
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-shurcool-httpfs.html
  • Required age reduced by 3 days because of autopkgtest
  • 260 days old (needed 2 days)
• node-nodedbi (- to 1.0.13+dfsg-1)
  • Migration status for node-nodedbi (- to 1.0.13+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating node-nodedbi introduces new bugs: #953028
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-nodedbi.html
  • 260 days old (needed 5 days)
• jfractionlab (- to 0.92-2)
  • Migration status for jfractionlab (- to 0.92-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jfractionlab introduces new bugs: #952058
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jfractionlab.html
  • 261 days old (needed 5 days)
• performous-composer (- to 2.0+20181009-gitbeeea23-2)
  • Migration status for performous-composer (- to 2.0+20181009-gitbeeea23-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating performous-composer introduces new bugs: #939712
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/performous-composer.html
  • 261 days old (needed 5 days)
• arbtt (- to 0.10.2-0.1)
  • Migration status for arbtt (- to 0.10.2-0.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on ppc64el
  • Build-Depends(-Arch): arbtt haskell-bytestring-progress
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arbtt.html
  • 262 days old (needed 5 days)
• rust-html5ever (- to 0.24.0-1)
  • Migration status for rust-html5ever (- to 0.24.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-html5ever-dev/amd64 has unsatisfiable dependency
  • librust-html5ever-dev/arm64 has unsatisfiable dependency
  • librust-html5ever-dev/armel has unsatisfiable dependency
  • librust-html5ever-dev/armhf has unsatisfiable dependency
  • librust-html5ever-dev/i386 has unsatisfiable dependency
  • librust-html5ever-dev/mips64el has unsatisfiable dependency
  • librust-html5ever-dev/mipsel has unsatisfiable dependency
  • librust-html5ever-dev/ppc64el has unsatisfiable dependency
  • librust-html5ever-dev/s390x has unsatisfiable dependency
  • Updating rust-html5ever introduces new bugs: #951682
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on amd64: librust-markup5ever-0.9+default-dev
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on arm64: librust-markup5ever-0.9+default-dev
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on armel: librust-markup5ever-0.9+default-dev
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on armhf: librust-markup5ever-0.9+default-dev
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on i386: librust-markup5ever-0.9+default-dev
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on mips64el: librust-markup5ever-0.9+default-dev
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on mipsel: librust-markup5ever-0.9+default-dev
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on ppc64el: librust-markup5ever-0.9+default-dev
  • rust-html5ever unsatisfiable Build-Depends(-Arch) on s390x: librust-markup5ever-0.9+default-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-html5ever.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 262 days old (needed 5 days)
• cicero (- to 0.7.2-5)
  • Migration status for cicero (- to 0.7.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cicero introduces new bugs: #945625
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 263 days old (needed 5 days)
• amule (- to 1:2.3.2-6)
  • Migration status for amule (- to 1:2.3.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • amule/amd64 has unsatisfiable dependency
  • amule-utils-gui/amd64 has unsatisfiable dependency
  • amule/arm64 has unsatisfiable dependency
  • amule-utils-gui/arm64 has unsatisfiable dependency
  • amule/armel has unsatisfiable dependency
  • amule-utils-gui/armel has unsatisfiable dependency
  • amule/armhf has unsatisfiable dependency
  • amule-utils-gui/armhf has unsatisfiable dependency
  • amule/i386 has unsatisfiable dependency
  • amule-utils-gui/i386 has unsatisfiable dependency
  • amule/mips64el has unsatisfiable dependency
  • amule-utils-gui/mips64el has unsatisfiable dependency
  • amule/mipsel has unsatisfiable dependency
  • amule-utils-gui/mipsel has unsatisfiable dependency
  • amule/ppc64el has unsatisfiable dependency
  • amule-utils-gui/ppc64el has unsatisfiable dependency
  • amule/s390x has unsatisfiable dependency
  • amule-utils-gui/s390x has unsatisfiable dependency
  • Updating amule introduces new bugs: #933439
  • amule unsatisfiable Build-Depends(-Arch) on amd64: libwxgtk3.0-dev
  • amule unsatisfiable Build-Depends(-Arch) on arm64: libwxgtk3.0-dev
  • amule unsatisfiable Build-Depends(-Arch) on armel: libwxgtk3.0-dev
  • amule unsatisfiable Build-Depends(-Arch) on armhf: libwxgtk3.0-dev
  • amule unsatisfiable Build-Depends(-Arch) on i386: libwxgtk3.0-dev
  • amule unsatisfiable Build-Depends(-Arch) on mips64el: libwxgtk3.0-dev
  • amule unsatisfiable Build-Depends(-Arch) on mipsel: libwxgtk3.0-dev
  • amule unsatisfiable Build-Depends(-Arch) on ppc64el: libwxgtk3.0-dev
  • amule unsatisfiable Build-Depends(-Arch) on s390x: libwxgtk3.0-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amule.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 264 days old (needed 5 days)
• golang-github-rivo-uniseg (- to 0.1.0-1)
  • Migration status for golang-github-rivo-uniseg (- 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 alteholz, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-rivo-uniseg.html
  • Required age reduced by 3 days because of autopkgtest
  • 264 days old (needed 2 days)
• haskell-yesod-bin (- to 1.6.0.3-5)
  • Migration status for haskell-yesod-bin (- to 1.6.0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-yesod-bin introduces new bugs: #949913
  • autopkgtest for haskell-yesod-bin/1.6.0.3-5: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-yesod-bin.html
  • 264 days old (needed 5 days)
• libcircle-fe-gtk-perl (- to 0.173170-2)
  • Migration status for libcircle-fe-gtk-perl (- to 0.173170-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libcircle-fe-gtk-perl introduces new bugs: #932220
  • autopkgtest for libcircle-fe-gtk-perl/0.173170-2: amd64: Pass, arm64: Regression ♻
  • Build-Depends-Indep: libcircle-fe-gtk-perl libgtk2-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcircle-fe-gtk-perl.html
  • 264 days old (needed 5 days)
• libtm-perl (- to 1.56-10)
  • Migration status for libtm-perl (- to 1.56-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libtm-perl introduces new bugs: #812619
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtm-perl.html
  • 264 days old (needed 5 days)
• icingaweb2-module-audit (- to 1.0.0-1)
  • Migration status for icingaweb2-module-audit (- 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 mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-audit.html
  • 265 days old (needed 5 days)
• icingaweb2-module-boxydash (- to 0.0.1+20160321-1)
  • Migration status for icingaweb2-module-boxydash (- to 0.0.1+20160321-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-boxydash.html
  • 265 days old (needed 5 days)
• icingaweb2-module-businessprocess (- to 2.1.0-1)
  • Migration status for icingaweb2-module-businessprocess (- 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 mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Depends: icingaweb2-module-businessprocess icingaweb2-module-ipl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-businessprocess.html
  • 265 days old (needed 5 days)
• icingaweb2-module-cube (- to 1.0.1-1)
  • Migration status for icingaweb2-module-cube (- 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 mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-cube.html
  • 265 days old (needed 5 days)
• icingaweb2-module-director (- to 1.6.0-1)
  • Migration status for icingaweb2-module-director (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-director.html
  • 265 days old (needed 5 days)
• icingaweb2-module-eventdb (- to 1.3.0-1)
  • Migration status for icingaweb2-module-eventdb (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-eventdb.html
  • 265 days old (needed 5 days)
• icingaweb2-module-graphite (- to 1.1.0-1)
  • Migration status for icingaweb2-module-graphite (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating icingaweb2-module-graphite introduces new bugs: #939568
  • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-graphite.html
  • 265 days old (needed 5 days)
• icingaweb2-module-map (- to 1.1.0-1)
  • Migration status for icingaweb2-module-map (- 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 mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-map.html
  • 265 days old (needed 5 days)
• icingaweb2-module-nagvis (- to 1.1.1-1)
  • Migration status for icingaweb2-module-nagvis (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating icingaweb2-module-nagvis introduces new bugs: #952435
  • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-nagvis.html
  • 265 days old (needed 5 days)
• icingaweb2-module-statusmap (- to 20160720-1)
  • Migration status for icingaweb2-module-statusmap (- to 20160720-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating icingaweb2-module-statusmap introduces new bugs: #939569
  • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-statusmap.html
  • 265 days old (needed 5 days)
• icingaweb2-module-x509 (- to 20190125-1)
  • Migration status for icingaweb2-module-x509 (- to 20190125-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • icingaweb2-module-x509/amd64 has unsatisfiable dependency
  • icingaweb2-module-x509/i386 has unsatisfiable dependency
  • Updating icingaweb2-module-x509 introduces new bugs: #953093
  • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/i/icingaweb2-module-x509.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 265 days old (needed 5 days)
• python-arrayfire (- to 3.3.20160624-3)
  • Migration status for python-arrayfire (- to 3.3.20160624-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): python-arrayfire arrayfire (not considered)
  • Depends: python-arrayfire arrayfire (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-arrayfire.html
  • Required age reduced by 3 days because of autopkgtest
  • 265 days old (needed 2 days)
• node-sntp (- to 3.1.2-2)
  • Migration status for node-sntp (- to 3.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for node-sntp/3.1.2-2: amd64: Pass, arm64: Regression ♻
  • Build-Depends(-Arch): node-sntp node-boom
  • Depends: node-sntp node-boom
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-sntp.html
  • 266 days old (needed 5 days)
• cookiecutter (- to 1.6.0-4)
  • Migration status for cookiecutter (- to 1.6.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): cookiecutter jinja2-time (not considered)
  • Depends: cookiecutter jinja2-time (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cookiecutter.html
  • 269 days old (needed 5 days)
• haskell-simple (- to 0.11.3-1)
  • Migration status for haskell-simple (- to 0.11.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): haskell-simple haskell-simple-templates (not considered)
  • Build-Depends-Indep: haskell-simple haskell-simple-templates (not considered)
  • Depends: haskell-simple haskell-simple-templates (not considered)
  • Invalidated by build-dependency
  • Invalidated by build-dependency (indep)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-simple.html
  • 269 days old (needed 5 days)
• haskell-simple-templates (- to 0.9.0.0-1)
  • Migration status for haskell-simple-templates (- to 0.9.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-simple-templates introduces new bugs: #914369
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-simple-templates.html
  • 269 days old (needed 5 days)
• jinja2-time (- to 0.2.0-2)
  • Migration status for jinja2-time (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jinja2-time introduces new bugs: #944030
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jinja2-time.html
  • 269 days old (needed 5 days)
• win32-loader (0.9.5 to 0.10.0)
  • Migration status for win32-loader (0.9.5 to 0.10.0): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
  • Not touching package due to block-udeb request by freeze (please contact the d-i release manager if an update is needed)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/win32-loader.html
  • 269 days old (needed 5 days)
• haskell-bytestring-progress (- to 1.4-1)
  • Migration status for haskell-bytestring-progress (- to 1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • haskell-bytestring-progress unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-terminal-progress-bar-dev (>= 0.4)
  • missing build on ppc64el
  • Build-Depends(-Arch): haskell-bytestring-progress haskell-terminal-progress-bar
  • Build-Depends-Indep: haskell-bytestring-progress haskell-terminal-progress-bar
  • Depends: haskell-bytestring-progress haskell-terminal-progress-bar
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-bytestring-progress.html
  • 270 days old (needed 5 days)
• haskell-gtk-strut (- to 0.1.3.0-1)
  • Migration status for haskell-gtk-strut (- to 0.1.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: haskell-gtk-strut haskell-gi-gdk (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): haskell-gtk-strut haskell-gi-gtk
  • Build-Depends-Indep: haskell-gtk-strut haskell-gi-gtk
  • Depends: haskell-gtk-strut haskell-gi-gtk
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gtk-strut.html
  • 270 days old (needed 5 days)
• haskell-serialise (- to 0.2.1.0-3)
  • Migration status for haskell-serialise (- to 0.2.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-serialise introduces new bugs: #939323
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-serialise.html
  • 270 days old (needed 5 days)
• golang-github-jesseduffield-gocui (- to 0.3.0+git20190803.ad0cd60-1)
  • Migration status for golang-github-jesseduffield-gocui (- to 0.3.0+git20190803.ad0cd60-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): golang-github-jesseduffield-gocui golang-github-jesseduffield-termbox-go (not considered)
  • Depends: golang-github-jesseduffield-gocui golang-github-jesseduffield-termbox-go (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-gocui.html
  • Required age reduced by 3 days because of autopkgtest
  • 271 days old (needed 2 days)
• dovecot (- to 1:2.3.7.2-1)
  • Migration status for dovecot (- to 1:2.3.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dovecot introduces new bugs: #951722, #960963
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dovecot.html
  • Required age reduced by 3 days because of autopkgtest
  • 273 days old (needed 2 days)
• webcheck (- to 1.10.4-3)
  • Migration status for webcheck (- to 1.10.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating webcheck introduces new bugs: #939259
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webcheck.html
  • Required age reduced by 3 days because of autopkgtest
  • 273 days old (needed 2 days)
• rust-bigdecimal (- to 0.1.0-1)
  • Migration status for rust-bigdecimal (- to 0.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-bigdecimal rust-num-bigint (not considered)
  • Depends: rust-bigdecimal rust-num-bigint (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bigdecimal.html
  • Required age reduced by 3 days because of autopkgtest
  • 274 days old (needed 2 days)
• rust-cookie-store (- to 0.8.0-1)
  • Migration status for rust-cookie-store (- to 0.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-cookie-store rust-cookie (not considered)
  • Depends: rust-cookie-store rust-cookie (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cookie-store.html
  • 274 days old (needed 5 days)
• rust-fs-extra (- to 1.1.0-1)
  • Migration status for rust-fs-extra (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-fs-extra/1.1.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fs-extra.html
  • 274 days old (needed 5 days)
• rust-migrations-internals (- to 1.4.0-1)
  • Migration status for rust-migrations-internals (- to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-migrations-internals+barrel-dev/amd64 has unsatisfiable dependency
  • librust-migrations-internals+barrel-dev/arm64 has unsatisfiable dependency
  • librust-migrations-internals+barrel-dev/armel has unsatisfiable dependency
  • librust-migrations-internals+barrel-dev/armhf has unsatisfiable dependency
  • librust-migrations-internals+barrel-dev/i386 has unsatisfiable dependency
  • librust-migrations-internals+barrel-dev/mips64el has unsatisfiable dependency
  • librust-migrations-internals+barrel-dev/mipsel has unsatisfiable dependency
  • librust-migrations-internals+barrel-dev/ppc64el has unsatisfiable dependency
  • librust-migrations-internals+barrel-dev/s390x has unsatisfiable dependency
  • Build-Depends(-Arch): rust-migrations-internals rust-diesel
  • Depends: rust-migrations-internals rust-diesel
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-migrations-internals.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 274 days old (needed 5 days)
• rust-vte (- to 0.3.3-1)
  • Migration status for rust-vte (- to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-vte/0.3.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-vte.html
  • 274 days old (needed 5 days)
• bup (- to 0.29.3-2)
  • Migration status for bup (- to 0.29.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • bup/amd64 has unsatisfiable dependency
  • bup/arm64 has unsatisfiable dependency
  • bup/armel has unsatisfiable dependency
  • bup/armhf has unsatisfiable dependency
  • bup/i386 has unsatisfiable dependency
  • bup/mips64el has unsatisfiable dependency
  • bup/mipsel has unsatisfiable dependency
  • bup/ppc64el has unsatisfiable dependency
  • bup/s390x has unsatisfiable dependency
  • bup unsatisfiable Build-Depends(-Arch) on amd64: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on amd64: python-pyxattr [linux-any]
  • bup unsatisfiable Build-Depends(-Arch) on arm64: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on arm64: python-pyxattr [linux-any]
  • bup unsatisfiable Build-Depends(-Arch) on armel: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on armel: python-pyxattr [linux-any]
  • bup unsatisfiable Build-Depends(-Arch) on armhf: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on armhf: python-pyxattr [linux-any]
  • bup unsatisfiable Build-Depends(-Arch) on i386: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on i386: python-pyxattr [linux-any]
  • bup unsatisfiable Build-Depends(-Arch) on mips64el: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on mips64el: python-pyxattr [linux-any]
  • bup unsatisfiable Build-Depends(-Arch) on mipsel: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on mipsel: python-pyxattr [linux-any]
  • bup unsatisfiable Build-Depends(-Arch) on ppc64el: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on ppc64el: python-pyxattr [linux-any]
  • bup unsatisfiable Build-Depends(-Arch) on s390x: python-pylibacl
  • bup unsatisfiable Build-Depends(-Arch) on s390x: python-pyxattr [linux-any]
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bup.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 275 days old (needed 5 days)
• persp-projectile (- to 1:0.2.0-3)
  • Migration status for persp-projectile (- to 1:0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating persp-projectile introduces new bugs: #919035
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/persp-projectile.html
  • 275 days old (needed 5 days)
• gocode (- to 20170907-3)
  • Migration status for gocode (- to 20170907-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gocode introduces new bugs: #925546
  • gocode/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • gocode/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • gocode/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • gocode/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • gocode/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • gocode/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • gocode/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • gocode/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • gocode/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gocode.html
  • 276 days old (needed 5 days)
• php-doctrine-cache-bundle (- to 1.3.5+git-1)
  • Migration status for php-doctrine-cache-bundle (- to 1.3.5+git-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-doctrine-cache-bundle introduces new bugs: #949016
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-doctrine-cache-bundle.html
  • Required age reduced by 3 days because of autopkgtest
  • 276 days old (needed 2 days)
• pound (- to 2.8-2)
  • Migration status for pound (- to 2.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pound introduces new bugs: #795897
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pound.html
  • 276 days old (needed 5 days)
• pysdl2 (- to 0.9.6+dfsg1-1)
  • Migration status for pysdl2 (- to 0.9.6+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pysdl2 introduces new bugs: #950040
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysdl2.html
  • 276 days old (needed 5 days)
• python-django-debug-toolbar (- to 1:2.0-1)
  • Migration status for python-django-debug-toolbar (- to 1:2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by a.starr.b@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-debug-toolbar.html
  • Required age reduced by 3 days because of autopkgtest
  • 276 days old (needed 2 days)
• sphinxcontrib-rubydomain (- to 0.1~dev-20100804-2)
  • Migration status for sphinxcontrib-rubydomain (- to 0.1~dev-20100804-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sphinxcontrib-rubydomain introduces new bugs: #896395
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-rubydomain.html
  • 276 days old (needed 5 days)
• bitcoin (- to 0.18.1~dfsg-1)
  • Migration status for bitcoin (- to 0.18.1~dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating bitcoin introduces new bugs: #939608
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bitcoin.html
  • 279 days old (needed 5 days)
• git-hub (- to 1.0.3-1)
  • Migration status for git-hub (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating git-hub introduces new bugs: #943037
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-hub.html
  • 279 days old (needed 5 days)
• libhibernate-validator-java (4.3.4-1 to 5.3.6-1)
  • Migration status for libhibernate-validator-java (4.3.4-1 to 5.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libhibernate-validator-java introduces new bugs: #942814
  • Build-Depends(-Arch): libhibernate-validator-java classmate
  • Depends: libhibernate-validator-java classmate
  • Additional info:
  • Updating libhibernate-validator-java fixes old bugs: #953338
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhibernate-validator-java.html
  • 279 days old (needed 5 days)
• mailman3 (- to 3.2.2-1)
  • Migration status for mailman3 (- to 3.2.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: mailman3 mailman-hyperkitty (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman3.html
  • Required age reduced by 3 days because of autopkgtest
  • 279 days old (needed 2 days)
• transip (- to 2.0.0-1)
  • Migration status for transip (- 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 mattia@mapreri.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/transip.html
  • 280 days old (needed 5 days)
• dmtcp (- to 2.6.0-1)
  • Migration status for dmtcp (- to 2.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by yoh
  • missing build on armhf
  • missing build on i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dmtcp.html
  • 282 days old (needed 5 days)
• rust-im-rc (- to 13.0.0-1)
  • Migration status for rust-im-rc (- to 13.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-im-rc+quickcheck-dev/amd64 has unsatisfiable dependency
  • librust-im-rc+quickcheck-dev/arm64 has unsatisfiable dependency
  • librust-im-rc+quickcheck-dev/armel has unsatisfiable dependency
  • librust-im-rc+quickcheck-dev/armhf has unsatisfiable dependency
  • librust-im-rc+quickcheck-dev/i386 has unsatisfiable dependency
  • librust-im-rc+quickcheck-dev/mips64el has unsatisfiable dependency
  • librust-im-rc+quickcheck-dev/mipsel has unsatisfiable dependency
  • librust-im-rc+quickcheck-dev/ppc64el has unsatisfiable dependency
  • librust-im-rc+quickcheck-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-im-rc.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 286 days old (needed 5 days)
• kissplice (- to 2.4.0-p1-5)
  • Migration status for kissplice (- to 2.4.0-p1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kissplice introduces new bugs: #936798
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kissplice.html
  • Required age reduced by 3 days because of autopkgtest
  • 287 days old (needed 2 days)
• tophat-recondition (- to 1.4-1)
  • Migration status for tophat-recondition (- to 1.4-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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tophat-recondition.html
  • 287 days old (needed 5 days)
• classmate (- to 1.3.4-1)
  • Migration status for classmate (- to 1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/classmate.html
  • 289 days old (needed 5 days)
• opensips (- to 2.2.2-3.1)
  • Migration status for opensips (- to 2.2.2-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating opensips introduces new bugs: #937212
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensips.html
  • 289 days old (needed 5 days)
• cinfony (- to 1.2-4)
  • Migration status for cinfony (- to 1.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cinfony introduces new bugs: #936303, #939065
  • autopkgtest for cinfony/1.2-4: amd64: Regression ♻ , arm64: Regression ♻
  • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python-indigo
  • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python-jpype
  • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python-openbabel
  • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python-rdkit
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cinfony.html
  • 290 days old (needed 5 days)
• psgml (- to 1.4.0-7.1)
  • Migration status for psgml (- to 1.4.0-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating psgml introduces new bugs: #952262
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psgml.html
  • 290 days old (needed 5 days)
• rust-md5-asm (- to 0.4.3-2)
  • Migration status for rust-md5-asm (- to 0.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-md5-asm/0.4.3-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-md5-asm.html
  • 291 days old (needed 5 days)
• python-pychart (- to 1.39-7.2)
  • Migration status for python-pychart (- to 1.39-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-pychart introduces new bugs: #938057
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pychart.html
  • 292 days old (needed 5 days)
• rust-tokio-timer (- to 0.2.11-1)
  • Migration status for rust-tokio-timer (- to 0.2.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-tokio-timer-dev/amd64 has unsatisfiable dependency
  • librust-tokio-timer-dev/arm64 has unsatisfiable dependency
  • librust-tokio-timer-dev/armel has unsatisfiable dependency
  • librust-tokio-timer-dev/armhf has unsatisfiable dependency
  • librust-tokio-timer-dev/i386 has unsatisfiable dependency
  • librust-tokio-timer-dev/mips64el has unsatisfiable dependency
  • librust-tokio-timer-dev/mipsel has unsatisfiable dependency
  • librust-tokio-timer-dev/ppc64el has unsatisfiable dependency
  • librust-tokio-timer-dev/s390x has unsatisfiable dependency
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-utils-0.6+default-dev
  • Build-Depends(-Arch): rust-tokio-timer rust-tokio-executor
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-timer.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 292 days old (needed 5 days)
• de4dot (- to 3.1.41592.3405-1)
  • Migration status for de4dot (- to 3.1.41592.3405-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating de4dot introduces new bugs: #934374
  • Not built on buildd: arch all binaries uploaded by bengen, a new source-only upload is needed to allow migration
  • Depends: de4dot dnlib
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/de4dot.html
  • 293 days old (needed 5 days)
• golang-github-shurcool-httpgzip (- to 0.0~git20190516.1c7afaa-1)
  • Migration status for golang-github-shurcool-httpgzip (- to 0.0~git20190516.1c7afaa-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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-shurcool-httpgzip.html
  • Required age reduced by 3 days because of autopkgtest
  • 293 days old (needed 2 days)
• golang-gopkg-src-d-go-git.v4 (- to 4.11.0-1)
  • Migration status for golang-gopkg-src-d-go-git.v4 (- to 4.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): golang-gopkg-src-d-go-git.v4 golang-github-src-d-gcfg
  • Depends: golang-gopkg-src-d-go-git.v4 golang-github-src-d-gcfg
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gopkg-src-d-go-git.v4.html
  • Required age reduced by 3 days because of autopkgtest
  • 293 days old (needed 2 days)
• kupfer (- to 0+v319-5)
  • Migration status for kupfer (- to 0+v319-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kupfer introduces new bugs: #947533
  • Build-Depends-Indep: kupfer gnome-doc-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kupfer.html
  • 294 days old (needed 5 days)
• rust-diesel (- to 1.4.2-2)
  • Migration status for rust-diesel (- to 1.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-diesel+bigdecimal-dev/amd64 has unsatisfiable dependency
  • librust-diesel+extras-dev/amd64 has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/amd64 has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/amd64 has unsatisfiable dependency
  • librust-diesel+mysql-dev/amd64 has unsatisfiable dependency
  • librust-diesel+network-address-dev/amd64 has unsatisfiable dependency
  • librust-diesel+numeric-dev/amd64 has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/amd64 has unsatisfiable dependency
  • librust-diesel+r2d2-dev/amd64 has unsatisfiable dependency
  • librust-diesel+sqlite-dev/amd64 has unsatisfiable dependency
  • librust-diesel+url-dev/amd64 has unsatisfiable dependency
  • librust-diesel+uuid-dev/amd64 has unsatisfiable dependency
  • librust-diesel+bigdecimal-dev/arm64 has unsatisfiable dependency
  • librust-diesel+extras-dev/arm64 has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/arm64 has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/arm64 has unsatisfiable dependency
  • librust-diesel+mysql-dev/arm64 has unsatisfiable dependency
  • librust-diesel+network-address-dev/arm64 has unsatisfiable dependency
  • librust-diesel+numeric-dev/arm64 has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/arm64 has unsatisfiable dependency
  • librust-diesel+r2d2-dev/arm64 has unsatisfiable dependency
  • librust-diesel+sqlite-dev/arm64 has unsatisfiable dependency
  • librust-diesel+url-dev/arm64 has unsatisfiable dependency
  • librust-diesel+uuid-dev/arm64 has unsatisfiable dependency
  • librust-diesel+bigdecimal-dev/armel has unsatisfiable dependency
  • librust-diesel+extras-dev/armel has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/armel has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/armel has unsatisfiable dependency
  • librust-diesel+mysql-dev/armel has unsatisfiable dependency
  • librust-diesel+mysqlclient-sys-dev/armel has unsatisfiable dependency
  • librust-diesel+network-address-dev/armel has unsatisfiable dependency
  • librust-diesel+numeric-dev/armel has unsatisfiable dependency
  • librust-diesel+postgres-dev/armel has unsatisfiable dependency
  • librust-diesel+pq-sys-dev/armel has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/armel has unsatisfiable dependency
  • librust-diesel+r2d2-dev/armel has unsatisfiable dependency
  • librust-diesel+sqlite-dev/armel has unsatisfiable dependency
  • librust-diesel+url-dev/armel has unsatisfiable dependency
  • librust-diesel+uuid-dev/armel has unsatisfiable dependency
  • librust-diesel+bigdecimal-dev/armhf has unsatisfiable dependency
  • librust-diesel+extras-dev/armhf has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/armhf has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/armhf has unsatisfiable dependency
  • librust-diesel+mysql-dev/armhf has unsatisfiable dependency
  • librust-diesel+mysqlclient-sys-dev/armhf has unsatisfiable dependency
  • librust-diesel+network-address-dev/armhf has unsatisfiable dependency
  • librust-diesel+numeric-dev/armhf has unsatisfiable dependency
  • librust-diesel+postgres-dev/armhf has unsatisfiable dependency
  • librust-diesel+pq-sys-dev/armhf has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/armhf has unsatisfiable dependency
  • librust-diesel+r2d2-dev/armhf has unsatisfiable dependency
  • librust-diesel+sqlite-dev/armhf has unsatisfiable dependency
  • librust-diesel+url-dev/armhf has unsatisfiable dependency
  • librust-diesel+uuid-dev/armhf has unsatisfiable dependency
  • librust-diesel+bigdecimal-dev/i386 has unsatisfiable dependency
  • librust-diesel+extras-dev/i386 has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/i386 has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/i386 has unsatisfiable dependency
  • librust-diesel+mysql-dev/i386 has unsatisfiable dependency
  • librust-diesel+mysqlclient-sys-dev/i386 has unsatisfiable dependency
  • librust-diesel+network-address-dev/i386 has unsatisfiable dependency
  • librust-diesel+numeric-dev/i386 has unsatisfiable dependency
  • librust-diesel+postgres-dev/i386 has unsatisfiable dependency
  • librust-diesel+pq-sys-dev/i386 has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/i386 has unsatisfiable dependency
  • librust-diesel+r2d2-dev/i386 has unsatisfiable dependency
  • librust-diesel+sqlite-dev/i386 has unsatisfiable dependency
  • librust-diesel+url-dev/i386 has unsatisfiable dependency
  • librust-diesel+uuid-dev/i386 has unsatisfiable dependency
  • librust-diesel+bigdecimal-dev/mips64el has unsatisfiable dependency
  • librust-diesel+extras-dev/mips64el has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/mips64el has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/mips64el has unsatisfiable dependency
  • librust-diesel+mysql-dev/mips64el has unsatisfiable dependency
  • librust-diesel+network-address-dev/mips64el has unsatisfiable dependency
  • librust-diesel+numeric-dev/mips64el has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/mips64el has unsatisfiable dependency
  • librust-diesel+r2d2-dev/mips64el has unsatisfiable dependency
  • librust-diesel+sqlite-dev/mips64el has unsatisfiable dependency
  • librust-diesel+url-dev/mips64el has unsatisfiable dependency
  • librust-diesel+uuid-dev/mips64el has unsatisfiable dependency
  • librust-diesel+bigdecimal-dev/mipsel has unsatisfiable dependency
  • librust-diesel+extras-dev/mipsel has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/mipsel has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/mipsel has unsatisfiable dependency
  • librust-diesel+mysql-dev/mipsel has unsatisfiable dependency
  • librust-diesel+mysqlclient-sys-dev/mipsel has unsatisfiable dependency
  • librust-diesel+network-address-dev/mipsel has unsatisfiable dependency
  • librust-diesel+numeric-dev/mipsel has unsatisfiable dependency
  • librust-diesel+postgres-dev/mipsel has unsatisfiable dependency
  • librust-diesel+pq-sys-dev/mipsel has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/mipsel has unsatisfiable dependency
  • librust-diesel+r2d2-dev/mipsel has unsatisfiable dependency
  • librust-diesel+sqlite-dev/mipsel has unsatisfiable dependency
  • librust-diesel+url-dev/mipsel has unsatisfiable dependency
  • librust-diesel+uuid-dev/mipsel has unsatisfiable dependency
  • librust-diesel+bigdecimal-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+extras-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+mysql-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+network-address-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+numeric-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+r2d2-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+sqlite-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+url-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+uuid-dev/ppc64el has unsatisfiable dependency
  • librust-diesel+bigdecimal-dev/s390x has unsatisfiable dependency
  • librust-diesel+extras-dev/s390x has unsatisfiable dependency
  • librust-diesel+ipnetwork-dev/s390x has unsatisfiable dependency
  • librust-diesel+libsqlite3-sys-dev/s390x has unsatisfiable dependency
  • librust-diesel+mysql-dev/s390x has unsatisfiable dependency
  • librust-diesel+network-address-dev/s390x has unsatisfiable dependency
  • librust-diesel+numeric-dev/s390x has unsatisfiable dependency
  • librust-diesel+quickcheck-dev/s390x has unsatisfiable dependency
  • librust-diesel+r2d2-dev/s390x has unsatisfiable dependency
  • librust-diesel+sqlite-dev/s390x has unsatisfiable dependency
  • librust-diesel+url-dev/s390x has unsatisfiable dependency
  • librust-diesel+uuid-dev/s390x has unsatisfiable dependency
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Depends: rust-diesel rust-num-bigint
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-diesel.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 294 days old (needed 5 days)
• moonshot-trust-router (- to 3.5.0+1)
  • Migration status for moonshot-trust-router (- to 3.5.0+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating moonshot-trust-router introduces new bugs: #944714
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/amd64
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/arm64
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/armel
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/armhf
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/i386
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/mips64el
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/mipsel
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/ppc64el
  • Impossible Depends: moonshot-trust-router -> libevent-2.1-6/2.1.8-stable-4/s390x
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/amd64
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/arm64
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/armel
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/armhf
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/i386
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/mips64el
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/mipsel
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/ppc64el
  • Impossible Depends: moonshot-trust-router -> libevent-pthreads-2.1-6/2.1.8-stable-4/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moonshot-trust-router.html
  • 295 days old (needed 5 days)
• ocamlviz (- to 1.01-3)
  • Migration status for ocamlviz (- to 1.01-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libocamlviz-ocaml-dev/amd64 has unsatisfiable dependency
  • libocamlviz-ocaml-dev/arm64 has unsatisfiable dependency
  • libocamlviz-ocaml-dev/armel has unsatisfiable dependency
  • ocamlviz/armel has unsatisfiable dependency
  • libocamlviz-ocaml-dev/armhf has unsatisfiable dependency
  • libocamlviz-ocaml-dev/i386 has unsatisfiable dependency
  • libocamlviz-ocaml-dev/mips64el has unsatisfiable dependency
  • ocamlviz/mips64el has unsatisfiable dependency
  • libocamlviz-ocaml-dev/mipsel has unsatisfiable dependency
  • ocamlviz/mipsel has unsatisfiable dependency
  • libocamlviz-ocaml-dev/ppc64el has unsatisfiable dependency
  • libocamlviz-ocaml-dev/s390x has unsatisfiable dependency
  • Updating ocamlviz introduces new bugs: #944601
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlviz.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 295 days old (needed 5 days)
• python-flask-cors (- to 3.0.8-2)
  • Migration status for python-flask-cors (- to 3.0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-flask-cors introduces new bugs: #950058
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flask-cors.html
  • 295 days old (needed 5 days)
• rust-argon2rs (- to 0.2.5-2)
  • Migration status for rust-argon2rs (- to 0.2.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-argon2rs rust-blake2-rfc (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-argon2rs.html
  • 295 days old (needed 5 days)
• rust-assert-cli (- to 0.6.3-2)
  • Migration status for rust-assert-cli (- to 0.6.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-assert-cli rust-difference (not considered)
  • Depends: rust-assert-cli rust-difference (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-assert-cli.html
  • 295 days old (needed 5 days)
• rust-blake2-rfc (- to 0.2.18-2)
  • Migration status for rust-blake2-rfc (- to 0.2.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-blake2-rfc+clippy-dev/amd64 has unsatisfiable dependency
  • librust-blake2-rfc-dev/amd64 has unsatisfiable dependency
  • librust-blake2-rfc+clippy-dev/arm64 has unsatisfiable dependency
  • librust-blake2-rfc-dev/arm64 has unsatisfiable dependency
  • librust-blake2-rfc+clippy-dev/armel has unsatisfiable dependency
  • librust-blake2-rfc-dev/armel has unsatisfiable dependency
  • librust-blake2-rfc+clippy-dev/armhf has unsatisfiable dependency
  • librust-blake2-rfc-dev/armhf has unsatisfiable dependency
  • librust-blake2-rfc+clippy-dev/i386 has unsatisfiable dependency
  • librust-blake2-rfc-dev/i386 has unsatisfiable dependency
  • librust-blake2-rfc+clippy-dev/mips64el has unsatisfiable dependency
  • librust-blake2-rfc-dev/mips64el has unsatisfiable dependency
  • librust-blake2-rfc+clippy-dev/mipsel has unsatisfiable dependency
  • librust-blake2-rfc-dev/mipsel has unsatisfiable dependency
  • librust-blake2-rfc+clippy-dev/ppc64el has unsatisfiable dependency
  • librust-blake2-rfc-dev/ppc64el has unsatisfiable dependency
  • librust-blake2-rfc+clippy-dev/s390x has unsatisfiable dependency
  • librust-blake2-rfc-dev/s390x has unsatisfiable dependency
  • Updating rust-blake2-rfc introduces new bugs: #935674
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on amd64: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on arm64: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on armel: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on armhf: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on i386: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on mips64el: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on mipsel: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on ppc64el: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • rust-blake2-rfc unsatisfiable Build-Depends(-Arch) on s390x: librust-arrayvec-0.4-dev (>= 0.4.6-~~)
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-blake2-rfc.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 295 days old (needed 5 days)
• rust-deflate (- to 0.7.19-2)
  • Migration status for rust-deflate (- to 0.7.19-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-deflate+gzip-dev/amd64 has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/amd64 has unsatisfiable dependency
  • librust-deflate+gzip-dev/arm64 has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/arm64 has unsatisfiable dependency
  • librust-deflate+gzip-dev/armel has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/armel has unsatisfiable dependency
  • librust-deflate+gzip-dev/armhf has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/armhf has unsatisfiable dependency
  • librust-deflate+gzip-dev/i386 has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/i386 has unsatisfiable dependency
  • librust-deflate+gzip-dev/mips64el has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/mips64el has unsatisfiable dependency
  • librust-deflate+gzip-dev/mipsel has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/mipsel has unsatisfiable dependency
  • librust-deflate+gzip-dev/ppc64el has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/ppc64el has unsatisfiable dependency
  • librust-deflate+gzip-dev/s390x has unsatisfiable dependency
  • librust-deflate+gzip-header-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-deflate.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 295 days old (needed 5 days)
• rust-libsqlite3-sys (- to 0.15.0-2)
  • Migration status for rust-libsqlite3-sys (- to 0.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-libsqlite3-sys+bindgen-dev/amd64 has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/amd64 has unsatisfiable dependency
  • librust-libsqlite3-sys+bindgen-dev/arm64 has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/arm64 has unsatisfiable dependency
  • librust-libsqlite3-sys+bindgen-dev/armel has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/armel has unsatisfiable dependency
  • librust-libsqlite3-sys+bindgen-dev/armhf has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/armhf has unsatisfiable dependency
  • librust-libsqlite3-sys+bindgen-dev/i386 has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/i386 has unsatisfiable dependency
  • librust-libsqlite3-sys+bindgen-dev/mips64el has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/mips64el has unsatisfiable dependency
  • librust-libsqlite3-sys+bindgen-dev/mipsel has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/mipsel has unsatisfiable dependency
  • librust-libsqlite3-sys+bindgen-dev/ppc64el has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/ppc64el has unsatisfiable dependency
  • librust-libsqlite3-sys+bindgen-dev/s390x has unsatisfiable dependency
  • librust-libsqlite3-sys+buildtime-bindgen-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-libsqlite3-sys.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 295 days old (needed 5 days)
• rust-md-5 (- to 0.8.0-2)
  • Migration status for rust-md-5 (- to 0.8.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-md-5 rust-md5-asm (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-md-5.html
  • 295 days old (needed 5 days)
• rust-sha-1 (- to 0.8.1-2)
  • Migration status for rust-sha-1 (- to 0.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-sha-1 rust-sha1-asm (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha-1.html
  • 295 days old (needed 5 days)
• rust-tiff (- to 0.3.1-2)
  • Migration status for rust-tiff (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-tiff-dev/amd64 has unsatisfiable dependency
  • librust-tiff-dev/arm64 has unsatisfiable dependency
  • librust-tiff-dev/armel has unsatisfiable dependency
  • librust-tiff-dev/armhf has unsatisfiable dependency
  • librust-tiff-dev/i386 has unsatisfiable dependency
  • librust-tiff-dev/mips64el has unsatisfiable dependency
  • librust-tiff-dev/mipsel has unsatisfiable dependency
  • librust-tiff-dev/ppc64el has unsatisfiable dependency
  • librust-tiff-dev/s390x has unsatisfiable dependency
  • Updating rust-tiff introduces new bugs: #945857
  • rust-tiff unsatisfiable Build-Depends(-Arch) on amd64: librust-num-derive-0.2+default-dev
  • rust-tiff unsatisfiable Build-Depends(-Arch) on arm64: librust-num-derive-0.2+default-dev
  • rust-tiff unsatisfiable Build-Depends(-Arch) on armel: librust-num-derive-0.2+default-dev
  • rust-tiff unsatisfiable Build-Depends(-Arch) on armhf: librust-num-derive-0.2+default-dev
  • rust-tiff unsatisfiable Build-Depends(-Arch) on i386: librust-num-derive-0.2+default-dev
  • rust-tiff unsatisfiable Build-Depends(-Arch) on mips64el: librust-num-derive-0.2+default-dev
  • rust-tiff unsatisfiable Build-Depends(-Arch) on mipsel: librust-num-derive-0.2+default-dev
  • rust-tiff unsatisfiable Build-Depends(-Arch) on ppc64el: librust-num-derive-0.2+default-dev
  • rust-tiff unsatisfiable Build-Depends(-Arch) on s390x: librust-num-derive-0.2+default-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tiff.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 295 days old (needed 5 days)
• rust-tokio-signal (- to 0.2.7-2)
  • Migration status for rust-tokio-signal (- to 0.2.7-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-tokio-signal rust-tokio-reactor (not considered)
  • Invalidated by build-dependency
  • Depends: rust-tokio-signal rust-signal-hook
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-signal.html
  • 295 days old (needed 5 days)
• golang-github-knqyf263-go-version (- to 1.1.1-2)
  • Migration status for golang-github-knqyf263-go-version (- to 1.1.1-2): 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-knqyf263-go-version.html
  • Required age reduced by 3 days because of autopkgtest
  • 296 days old (needed 2 days)
• macsyfinder (- to 1.0.5-3)
  • Migration status for macsyfinder (- to 1.0.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating macsyfinder introduces new bugs: #933928, #936977
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/macsyfinder.html
  • uninstallable on arch arm64, not running autopkgtest there
  • Required age reduced by 3 days because of autopkgtest
  • 296 days old (needed 2 days)
• sandsifter (- to 1.04-1)
  • Migration status for sandsifter (- to 1.04-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • sandsifter/amd64 has unsatisfiable dependency
  • sandsifter/i386 has unsatisfiable dependency
  • Updating sandsifter introduces new bugs: #938432
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sandsifter.html
  • uninstallable on arch amd64, not running autopkgtest there
  • 297 days old (needed 5 days)
• tika (- to 1.22-1)
  • Migration status for tika (- to 1.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tika introduces new bugs: #954302, #954303
  • Build-Depends(-Arch): tika vorbis-java
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tika.html
  • 297 days old (needed 5 days)
• willow (- to 1.1-4)
  • Migration status for willow (- to 1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating willow introduces new bugs: #951990
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/willow.html
  • Required age reduced by 3 days because of autopkgtest
  • 297 days old (needed 2 days)
• cfv (- to 1.18.3-2.1)
  • Migration status for cfv (- to 1.18.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cfv introduces new bugs: #936288
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cfv.html
  • 298 days old (needed 5 days)
• flask-limiter (- to 1.0.1-2)
  • Migration status for flask-limiter (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for flask-limiter/1.0.1-2: amd64: Pass, arm64: Regression ♻
  • Build-Depends(-Arch): flask-limiter python-limits
  • Depends: flask-limiter python-limits
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-limiter.html
  • 298 days old (needed 5 days)
• golang-github-briandowns-spinner (- to 1.6.1-2)
  • Migration status for golang-github-briandowns-spinner (- to 1.6.1-2): 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-briandowns-spinner.html
  • Required age reduced by 3 days because of autopkgtest
  • 298 days old (needed 2 days)
• litecoin (- to 0.17.1-1)
  • Migration status for litecoin (- to 0.17.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating litecoin introduces new bugs: #908987
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/litecoin.html
  • 299 days old (needed 5 days)
• jugglemaster (- to 0.4-10)
  • Migration status for jugglemaster (- to 0.4-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jugglemaster introduces new bugs: #900890
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jugglemaster.html
  • 302 days old (needed 5 days)
• python-ruamel.ordereddict (- to 0.4.14-1)
  • Migration status for python-ruamel.ordereddict (- to 0.4.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-ruamel.ordereddict introduces new bugs: #938150
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ruamel.ordereddict.html
  • 302 days old (needed 5 days)
• haskell-gi-gtk-hs (- to 0.3.6.3-1)
  • Migration status for haskell-gi-gtk-hs (- to 0.3.6.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: haskell-gi-gtk-hs haskell-gi-gdk (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): haskell-gi-gtk-hs haskell-gi-gtk
  • Build-Depends-Indep: haskell-gi-gtk-hs haskell-gi-gtk
  • Depends: haskell-gi-gtk-hs haskell-gi-gtk
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gtk-hs.html
  • 304 days old (needed 5 days)
• haskell-gi-gtk (- to 3.0.27-1)
  • Migration status for haskell-gi-gtk (- to 3.0.27-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): haskell-gi-gtk haskell-gi-pango (not considered)
  • Build-Depends-Indep: haskell-gi-gtk haskell-gi-pango (not considered)
  • Depends: haskell-gi-gtk haskell-gi-pango (not considered)
  • Invalidated by build-dependency
  • Invalidated by build-dependency (indep)
  • Invalidated by dependency
  • Depends: haskell-gi-gtk haskell-gi-gdk
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gtk.html
  • 305 days old (needed 5 days)
• haskell-gi-pango (- to 1.0.19-1)
  • Migration status for haskell-gi-pango (- to 1.0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-gi-pango introduces new bugs: #955674
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-pango.html
  • 305 days old (needed 5 days)
• haskell-terminal-progress-bar (- to 0.4.1-1)
  • Migration status for haskell-terminal-progress-bar (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-terminal-progress-bar introduces new bugs: #942583
  • missing build on ppc64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-terminal-progress-bar.html
  • 305 days old (needed 5 days)
• django-cas-server (- to 1.1.0-1)
  • Migration status for django-cas-server (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating django-cas-server introduces new bugs: #955118
  • autopkgtest for django-cas-server/1.1.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-cas-server.html
  • 306 days old (needed 5 days)
• haskell-classy-prelude-yesod (- to 1.5.0-1)
  • Migration status for haskell-classy-prelude-yesod (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-classy-prelude-yesod introduces new bugs: #912924
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-classy-prelude-yesod.html
  • 306 days old (needed 5 days)
• pytest-cookies (- to 0.4.0-1)
  • Migration status for pytest-cookies (- to 0.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: pytest-cookies cookiecutter (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-cookies.html
  • 306 days old (needed 5 days)
• yui3 (- to 3.5.1-1.1)
  • Migration status for yui3 (- to 3.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating yui3 introduces new bugs: #788319
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yui3.html
  • 310 days old (needed 5 days)
• rust-png (- to 0.15.0-1)
  • Migration status for rust-png (- to 0.15.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-png rust-deflate (not considered)
  • Depends: rust-png rust-deflate (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-png.html
  • 311 days old (needed 5 days)
• mailavenger (- to 0.8.5-2)
  • Migration status for mailavenger (- to 0.8.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mailavenger introduces new bugs: #944658, #944693
  • missing build on i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailavenger.html
  • Required age reduced by 3 days because of autopkgtest
  • 312 days old (needed 2 days)
• dyndns (- to 2016.1021-3)
  • Migration status for dyndns (- to 2016.1021-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dyndns introduces new bugs: #932796
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dyndns.html
  • Required age reduced by 3 days because of autopkgtest
  • 313 days old (needed 2 days)
• espresso (- to 6.4.1-1)
  • Migration status for espresso (- to 6.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating espresso introduces new bugs: #946915
  • missing build on arm64
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/espresso.html
  • 313 days old (needed 5 days)
• golang-github-caarlos0-env (- to 6.0.0-1)
  • Migration status for golang-github-caarlos0-env (- to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by iwamatsu, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-caarlos0-env.html
  • Required age reduced by 3 days because of autopkgtest
  • 313 days old (needed 2 days)
• golang-github-getlantern-hex (- to 0.0~git20160523.083fba3-1)
  • Migration status for golang-github-getlantern-hex (- to 0.0~git20160523.083fba3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by micah, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-hex.html
  • Required age reduced by 3 days because of autopkgtest
  • 313 days old (needed 2 days)
• libkiokudb-perl (- to 0.57-2)
  • Migration status for libkiokudb-perl (- to 0.57-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libkiokudb-perl introduces new bugs: #950999
  • autopkgtest for libkiokudb-perl/0.57-2: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkiokudb-perl.html
  • 313 days old (needed 5 days)
• golang-github-knqyf263-go-dep-parser (- to 0.0~git20190521.1ef8521-1)
  • Migration status for golang-github-knqyf263-go-dep-parser (- to 0.0~git20190521.1ef8521-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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-knqyf263-go-dep-parser.html
  • Required age reduced by 3 days because of autopkgtest
  • 315 days old (needed 2 days)
• golang-github-knqyf263-nested (- to 0.0.1-1)
  • Migration status for golang-github-knqyf263-nested (- to 0.0.1-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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-knqyf263-nested.html
  • Required age reduced by 3 days because of autopkgtest
  • 315 days old (needed 2 days)
• hpcc (- to 1.5.0-2)
  • Migration status for hpcc (- to 1.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hpcc introduces new bugs: #952067
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hpcc.html
  • 315 days old (needed 5 days)
• puppetdb (- to 6.2.0-4)
  • Migration status for puppetdb (- to 6.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for puppetdb/6.2.0-4: amd64: Pass, arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by apoikos@dmesg.gr, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): puppetdb pantomime-clojure
  • Depends: puppetdb pantomime-clojure
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppetdb.html
  • 316 days old (needed 5 days)
• rust-tokio (- to 0.1.14-2)
  • Migration status for rust-tokio (- to 0.1.14-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-tokio rust-tokio-fs (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): rust-tokio rust-tokio-uds
  • Depends: rust-tokio rust-tokio-current-thread
  • Depends: rust-tokio rust-tokio-tcp
  • Depends: rust-tokio rust-tokio-udp
  • Depends: rust-tokio rust-tokio-uds
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio.html
  • 316 days old (needed 5 days)
• rust-tokio-core (- to 0.1.17-2)
  • Migration status for rust-tokio-core (- to 0.1.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-tokio-core-dev/amd64 has unsatisfiable dependency
  • librust-tokio-core-dev/arm64 has unsatisfiable dependency
  • librust-tokio-core-dev/armel has unsatisfiable dependency
  • librust-tokio-core-dev/armhf has unsatisfiable dependency
  • librust-tokio-core-dev/i386 has unsatisfiable dependency
  • librust-tokio-core-dev/mips64el has unsatisfiable dependency
  • librust-tokio-core-dev/mipsel has unsatisfiable dependency
  • librust-tokio-core-dev/ppc64el has unsatisfiable dependency
  • librust-tokio-core-dev/s390x has unsatisfiable dependency
  • Updating rust-tokio-core introduces new bugs: #952137
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on amd64: librust-scoped-tls-0.1+default-dev
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on arm64: librust-scoped-tls-0.1+default-dev
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armel: librust-scoped-tls-0.1+default-dev
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armhf: librust-scoped-tls-0.1+default-dev
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on i386: librust-scoped-tls-0.1+default-dev
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mips64el: librust-scoped-tls-0.1+default-dev
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mipsel: librust-scoped-tls-0.1+default-dev
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on ppc64el: librust-scoped-tls-0.1+default-dev
  • rust-tokio-core unsatisfiable Build-Depends(-Arch) on s390x: librust-scoped-tls-0.1+default-dev
  • Build-Depends(-Arch): rust-tokio-core rust-tokio-timer
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-core.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 316 days old (needed 5 days)
• rust-tokio-current-thread (- to 0.1.6-1)
  • Migration status for rust-tokio-current-thread (- to 0.1.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-tokio-current-thread rust-tokio-executor (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-current-thread.html
  • 317 days old (needed 5 days)
• rust-tokio-udp (- to 0.1.3-2)
  • Migration status for rust-tokio-udp (- to 0.1.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-tokio-udp rust-tokio-reactor (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-udp.html
  • 317 days old (needed 5 days)
• rust-tokio-uds (- to 0.2.5-1)
  • Migration status for rust-tokio-uds (- to 0.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-tokio-uds rust-tokio-reactor (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-uds.html
  • 317 days old (needed 5 days)
• rust-users (- to 0.9.1-1)
  • Migration status for rust-users (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for rust-users/0.9.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-users.html
  • 318 days old (needed 5 days)
• rust-pest-meta (- to 2.1.1-1)
  • Migration status for rust-pest-meta (- to 2.1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-pest-meta rust-pest (not considered)
  • Depends: rust-pest-meta rust-pest (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pest-meta.html
  • Required age reduced by 3 days because of autopkgtest
  • 319 days old (needed 2 days)
• resvg (- to 0.5.0-2)
  • Migration status for resvg (- to 0.5.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
  • missing build on amd64
  • missing build on arm64
  • missing build on armhf
  • missing build on i386
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resvg.html
  • 321 days old (needed 5 days)
• aiorwlock (- to 0.6.0-2)
  • Migration status for aiorwlock (- to 0.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): aiorwlock uvloop (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiorwlock.html
  • 322 days old (needed 5 days)
• ifupdown2 (- to 1.2.7-1)
  • Migration status for ifupdown2 (- to 1.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ifupdown2/amd64 has unsatisfiable dependency
  • ifupdown2/i386 has unsatisfiable dependency
  • Updating ifupdown2 introduces new bugs: #927134, #936724
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifupdown2.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 322 days old (needed 5 days)
• rust-tokio-executor (- to 0.1.8-1)
  • Migration status for rust-tokio-executor (- to 0.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-tokio-executor-dev/amd64 has unsatisfiable dependency
  • librust-tokio-executor-dev/arm64 has unsatisfiable dependency
  • librust-tokio-executor-dev/armel has unsatisfiable dependency
  • librust-tokio-executor-dev/armhf has unsatisfiable dependency
  • librust-tokio-executor-dev/i386 has unsatisfiable dependency
  • librust-tokio-executor-dev/mips64el has unsatisfiable dependency
  • librust-tokio-executor-dev/mipsel has unsatisfiable dependency
  • librust-tokio-executor-dev/ppc64el has unsatisfiable dependency
  • librust-tokio-executor-dev/s390x has unsatisfiable dependency
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-utils-0.6+default-dev (>= 0.6.2-~~)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-executor.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 322 days old (needed 5 days)
• rust-tokio-fs (- to 0.1.6-1)
  • Migration status for rust-tokio-fs (- to 0.1.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-tokio-fs rust-tokio-threadpool (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-fs.html
  • 322 days old (needed 5 days)
• pluginhook (- to 0~20150216.0~a320158-2.1)
  • Migration status for pluginhook (- to 0~20150216.0~a320158-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • pluginhook/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • pluginhook/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • pluginhook/armel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • pluginhook/armhf has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • pluginhook/i386 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • pluginhook/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • pluginhook/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • pluginhook/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • pluginhook/s390x has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • missing build on mips64el
  • missing build on mipsel
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pluginhook.html
  • 335 days old (needed 5 days)
• sklearn-pandas (- to 1.8.0-1)
  • Migration status for sklearn-pandas (- to 1.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sklearn-pandas introduces new bugs: #961606
  • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sklearn-pandas.html
  • 339 days old (needed 5 days)
• mysql-5.7 (- to 5.7.26-1)
  • Migration status for mysql-5.7 (- to 5.7.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mysql-5.7 introduces new bugs: #853008, #932340, #942443, #949994, #956832
  • Impossible Depends: mysql-5.7 -> libevent-core-2.1-6/2.1.8-stable-4/i386
  • Impossible Depends: mysql-5.7 -> libevent-extra-2.1-6/2.1.8-stable-4/i386
  • Not touching package due to block request by pochu (please contact debian-release if update is needed)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-5.7.html
  • Required age reduced by 3 days because of autopkgtest
  • 344 days old (needed 2 days)
• utf8.h (- to 0~git20190120.2a7c5bf-1)
  • Migration status for utf8.h (- to 0~git20190120.2a7c5bf-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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utf8.h.html
  • 351 days old (needed 5 days)
• ola (- to 0.10.7.nojsmin-2)
  • Migration status for ola (- to 0.10.7.nojsmin-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ola introduces new bugs: #925793, #937186
  • Not built on buildd: arch amd64 binaries uploaded by wouter
  • Not built on buildd: arch all binaries uploaded by wouter, a new source-only upload is needed to allow migration
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/amd64
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/arm64
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/armel
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/armhf
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/i386
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/mips64el
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/mipsel
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/ppc64el
  • Impossible Build-Depends(-Arch): ola -> python-protobuf/3.6.1.3-2+b3/s390x
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/amd64
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/arm64
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/armel
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/armhf
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/i386
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/mips64el
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/mipsel
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/ppc64el
  • Impossible Depends: ola -> libprotobuf17/3.6.1.3-2+b3/s390x
  • Impossible Depends: ola -> python-protobuf/3.6.1.3-2+b3/amd64
  • Impossible Depends: ola -> python-protobuf/3.6.1.3-2+b3/i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ola.html
  • Required age reduced by 3 days because of autopkgtest
  • 353 days old (needed 2 days)
• ghmm (- to 0.9~rc3-2)
  • Migration status for ghmm (- to 0.9~rc3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ghmm introduces new bugs: #936609
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghmm.html
  • 361 days old (needed 5 days)
• averell (- to 1.2.5-1.1)
  • Migration status for averell (- to 1.2.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): averell erlang-cowboy (not considered)
  • Depends: averell erlang-cowboy (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/averell.html
  • 371 days old (needed 5 days)
• typecatcher (- to 0.3-1.1)
  • Migration status for typecatcher (- to 0.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mattia@mapreri.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/typecatcher.html
  • 371 days old (needed 5 days)
• dnlib (- to 2.1-2)
  • Migration status for dnlib (- to 2.1-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/d/dnlib.html
  • 373 days old (needed 5 days)
• einsteinpy (- to 0.1.0+dfsg-1)
  • Migration status for einsteinpy (- to 0.1.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by debian@liska.ath.cx, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/einsteinpy.html
  • 373 days old (needed 5 days)
• vim-textobj-user (- to 0.7.6-1)
  • Migration status for vim-textobj-user (- to 0.7.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-textobj-user.html
  • 374 days old (needed 5 days)
• mininet (- to 2.2.2-5)
  • Migration status for mininet (- to 2.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mininet introduces new bugs: #937051
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mininet.html
  • 375 days old (needed 5 days)
• gambc (- to 4.9.3-1)
  • Migration status for gambc (- to 4.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gambc introduces new bugs: #953728
  • Not built on buildd: arch amd64 binaries uploaded by tiago
  • Not built on buildd: arch all binaries uploaded by tiago, a new source-only upload is needed to allow migration
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gambc.html
  • 376 days old (needed 5 days)
• upass (- to 0.3.0-1)
  • Migration status for upass (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by nik@naturalnet.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/upass.html
  • 377 days old (needed 5 days)
• slt (- to 0.0.git20140301-6)
  • Migration status for slt (- to 0.0.git20140301-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating slt introduces new bugs: #903059
  • slt/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • slt/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • slt/armel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • slt/armhf has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • slt/i386 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • slt/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • slt/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • slt/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • slt/s390x has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slt.html
  • Required age reduced by 3 days because of autopkgtest
  • 384 days old (needed 2 days)
• golang-github-mgutz-str (- to 1.2.0-1)
  • Migration status for golang-github-mgutz-str (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-mgutz-str.html
  • Required age reduced by 3 days because of autopkgtest
  • 389 days old (needed 2 days)
• golang-github-src-d-gcfg (- to 1.4.0-1)
  • Migration status for golang-github-src-d-gcfg (- to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for golang-github-src-d-gcfg/1.4.0-1: amd64: Pass, arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-src-d-gcfg.html
  • 389 days old (needed 5 days)
• golang-github-alecthomas-binary (- to 0.0~git20171101.6e8df1b-1)
  • Migration status for golang-github-alecthomas-binary (- to 0.0~git20171101.6e8df1b-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by balasankarc, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alecthomas-binary.html
  • Required age reduced by 3 days because of autopkgtest
  • 390 days old (needed 2 days)
• golang-github-muesli-crunchy (- to 0.2-1)
  • Migration status for golang-github-muesli-crunchy (- to 0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by balasankarc, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): golang-github-muesli-crunchy golang-github-xrash-smetrics
  • Depends: golang-github-muesli-crunchy golang-github-xrash-smetrics
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-muesli-crunchy.html
  • Required age reduced by 3 days because of autopkgtest
  • 390 days old (needed 2 days)
• live-wrapper (- to 0.10)
  • Migration status for live-wrapper (- to 0.10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • live-wrapper/amd64 has unsatisfiable dependency
  • live-wrapper/i386 has unsatisfiable dependency
  • Updating live-wrapper introduces new bugs: #916716, #936954
  • live-wrapper unsatisfiable Build-Depends(-Arch) on amd64: python-apt
  • live-wrapper unsatisfiable Build-Depends(-Arch) on amd64: python-cliapp
  • live-wrapper unsatisfiable Build-Depends(-Arch) on amd64: python-requests
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): live-wrapper vmdebootstrap
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/live-wrapper.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 393 days old (needed 5 days)
• belle-sip (- to 1.6.3-5)
  • Migration status for belle-sip (- to 1.6.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating belle-sip introduces new bugs: #925638
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/belle-sip.html
  • 406 days old (needed 5 days)
• django-measurement (- to 3.1.1-1)
  • Migration status for django-measurement (- to 3.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by terceiro, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-measurement.html
  • Required age reduced by 3 days because of autopkgtest
  • 407 days old (needed 2 days)
• golang-github-getlantern-ops (- to 0.0~git20190325.d70cb0d-1)
  • Migration status for golang-github-getlantern-ops (- to 0.0~git20190325.d70cb0d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by micah, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-ops.html
  • Required age reduced by 3 days because of autopkgtest
  • 407 days old (needed 2 days)
• golang-github-jesseduffield-termbox-go (- to 0.0~git20180919.1e272ff-1)
  • Migration status for golang-github-jesseduffield-termbox-go (- to 0.0~git20180919.1e272ff-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-termbox-go.html
  • Required age reduced by 3 days because of autopkgtest
  • 409 days old (needed 2 days)
• icingaweb2-module-ipl (- to 0.1.1-1)
  • Migration status for icingaweb2-module-ipl (- to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-ipl.html
  • 409 days old (needed 5 days)
• mini-buildd (- to 1.0.41)
  • Migration status for mini-buildd (- to 1.0.41): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mini-buildd/amd64 has unsatisfiable dependency
  • python-mini-buildd/amd64 has unsatisfiable dependency
  • mini-buildd/i386 has unsatisfiable dependency
  • python-mini-buildd/i386 has unsatisfiable dependency
  • Updating mini-buildd introduces new bugs: #933751, #937049
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 1.1.3)
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-pygraphviz
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-argcomplete (>= 0.5.4)
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-daemon (>= 2.0.5)
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-debian (>= 0.1.18~)
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-cherrypy3
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-pyftpdlib (>= 1.2.0)
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-django (>= 1.7)
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-django (<< 1:1.12)
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-django-registration (>= 2.0.4)
  • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-tzlocal
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mini-buildd.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 411 days old (needed 5 days)
• golang-github-gokyle-fswatch (- to 0.0~git20121217.1dbdf83-1)
  • Migration status for golang-github-gokyle-fswatch (- to 0.0~git20121217.1dbdf83-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by balasankarc, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gokyle-fswatch.html
  • Required age reduced by 3 days because of autopkgtest
  • 413 days old (needed 2 days)
• golang-github-muesli-goprogressbar (- to 0.1+git20180221.8ba3888-1)
  • Migration status for golang-github-muesli-goprogressbar (- to 0.1+git20180221.8ba3888-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-muesli-goprogressbar.html
  • Required age reduced by 3 days because of autopkgtest
  • 413 days old (needed 2 days)
• golang-github-xrash-smetrics (- to 0.0~git20170218.a3153f7-1)
  • Migration status for golang-github-xrash-smetrics (- to 0.0~git20170218.a3153f7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-xrash-smetrics.html
  • Required age reduced by 3 days because of autopkgtest
  • 413 days old (needed 2 days)
• pbgenomicconsensus (- to 2.3.2-5)
  • Migration status for pbgenomicconsensus (- to 2.3.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-pbgenomicconsensus/amd64 has unsatisfiable dependency
  • python-pbgenomicconsensus/i386 has unsatisfiable dependency
  • Updating pbgenomicconsensus introduces new bugs: #937255
  • pbgenomicconsensus unsatisfiable Build-Depends(-Arch) on amd64: python-pbconsensuscore
  • pbgenomicconsensus unsatisfiable Build-Depends(-Arch) on amd64: python-pbcore (>= 1.2.9)
  • pbgenomicconsensus unsatisfiable Build-Depends(-Arch) on amd64: python-pbcommand (>= 0.3.20)
  • pbgenomicconsensus unsatisfiable Build-Depends(-Arch) on amd64: python-h5py
  • pbgenomicconsensus unsatisfiable Build-Depends(-Arch) on amd64: python-cram
  • pbgenomicconsensus unsatisfiable Build-Depends(-Arch) on amd64: python-pytest
  • Build-Depends(-Arch): pbgenomicconsensus unanimity
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pbgenomicconsensus.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 416 days old (needed 5 days)
• golang-gitlab-lupine-go-mimedb (- to 1.33.0-1)
  • Migration status for golang-gitlab-lupine-go-mimedb (- to 1.33.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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gitlab-lupine-go-mimedb.html
  • Required age reduced by 3 days because of autopkgtest
  • 420 days old (needed 2 days)
• khal (- to 1:0.9.10-1.1)
  • Migration status for khal (- to 1:0.9.10-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating khal introduces new bugs: #921257
  • Build-Depends(-Arch): khal vdirsyncer
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khal.html
  • Required age reduced by 3 days because of autopkgtest
  • 424 days old (needed 2 days)
• vmdebootstrap (- to 1.11-2)
  • Migration status for vmdebootstrap (- to 1.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • vmdebootstrap/amd64 has unsatisfiable dependency
  • vmdebootstrap/arm64 has unsatisfiable dependency
  • vmdebootstrap/armel has unsatisfiable dependency
  • vmdebootstrap/armhf has unsatisfiable dependency
  • vmdebootstrap/i386 has unsatisfiable dependency
  • vmdebootstrap/mips64el has unsatisfiable dependency
  • vmdebootstrap/mipsel has unsatisfiable dependency
  • vmdebootstrap/ppc64el has unsatisfiable dependency
  • vmdebootstrap/s390x has unsatisfiable dependency
  • Updating vmdebootstrap introduces new bugs: #910201, #938792
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vmdebootstrap.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 424 days old (needed 5 days)
• python-pylibsrtp (- to 0.6.1-1)
  • Migration status for python-pylibsrtp (- 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 debacle, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pylibsrtp.html
  • 426 days old (needed 5 days)
• phamm (- to 0.6.8-1)
  • Migration status for phamm (- to 0.6.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating phamm introduces new bugs: #924731
  • Not built on buildd: arch all binaries uploaded by kobold, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phamm.html
  • 427 days old (needed 5 days)
• cider (- to 0.19.0+dfsg-2)
  • Migration status for cider (- to 0.19.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cider introduces new bugs: #954699
  • autopkgtest for cider/0.19.0+dfsg-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cider.html
  • 435 days old (needed 5 days)
• ubuntu-keyring (- to 2018.09.18.1-5)
  • Migration status for ubuntu-keyring (- to 2018.09.18.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ubuntu-keyring introduces new bugs: #929165
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ubuntu-keyring.html
  • Required age reduced by 3 days because of autopkgtest
  • 443 days old (needed 2 days)
• mono-basic (- to 4.0.1-3)
  • Migration status for mono-basic (- to 4.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mono-basic.html
  • 449 days old (needed 5 days)
• ruby-handlebars-assets (- to 2:0.23.3+dfsg-2)
  • Migration status for ruby-handlebars-assets (- to 2:0.23.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ruby-handlebars-assets introduces new bugs: #952026
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-handlebars-assets.html
  • Required age reduced by 3 days because of autopkgtest
  • 450 days old (needed 2 days)
• os-autoinst (- to 4.5.1527308405.8b586d5-4.1)
  • Migration status for os-autoinst (- to 4.5.1527308405.8b586d5-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating os-autoinst introduces new bugs: #937217, #943602
  • Impossible Depends: os-autoinst -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-core3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-flann3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-ml3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-photo3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-shape3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-superres3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-video3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: os-autoinst -> libopencv-viz3.2/3.2.0+dfsg-6+b1/amd64
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/os-autoinst.html
  • 452 days old (needed 5 days)
• packer (- to 1.3.4+dfsg-4)
  • Migration status for packer (- to 1.3.4+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating packer introduces new bugs: #948000
  • autopkgtest for packer/1.3.4+dfsg-4: amd64: Regression ♻ , arm64: Regression ♻
  • packer/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • packer/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • packer/armel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • packer/armhf has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • packer/i386 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • packer/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/mips64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • packer/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/mipsel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • packer/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • packer/s390x has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • packer/s390x has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packer.html
  • 453 days old (needed 5 days)
• adequate (- to 0.15.2)
  • Migration status for adequate (- to 0.15.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating adequate introduces new bugs: #942926
  • autopkgtest for adequate/0.15.2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by abe, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adequate.html
  • 454 days old (needed 5 days)
• netbeans (- to 10.0-3)
  • Migration status for netbeans (- to 10.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating netbeans introduces new bugs: #925509, #929561
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netbeans.html
  • 454 days old (needed 5 days)
• openhft-chronicle-bytes (- to 1.1.15-2)
  • Migration status for openhft-chronicle-bytes (- to 1.1.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openhft-chronicle-bytes introduces new bugs: #929713
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openhft-chronicle-bytes.html
  • 454 days old (needed 5 days)
• kthresher (- to 1.4.0-1)
  • Migration status for kthresher (- to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kthresher introduces new bugs: #931024
  • Not built on buildd: arch all binaries uploaded by mika, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kthresher.html
  • 455 days old (needed 5 days)
• netkit-telnet-ssl (- to 0.17.41+0.2-3.2)
  • Migration status for netkit-telnet-ssl (- to 0.17.41+0.2-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating netkit-telnet-ssl introduces new bugs: #920371
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netkit-telnet-ssl.html
  • 455 days old (needed 5 days)
• infnoise (- to 0.3.1+dfsg-1)
  • Migration status for infnoise (- to 0.3.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating infnoise introduces new bugs: #911587
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/infnoise.html
  • 459 days old (needed 5 days)
• libmath-gsl-perl (- to 0.40-1)
  • Migration status for libmath-gsl-perl (- to 0.40-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Removal request by ginggs
  • Trying to remove package, not update it
  • Updating libmath-gsl-perl introduces new bugs: #960011
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmath-gsl-perl.html
  • Required age reduced by 3 days because of autopkgtest
  • 459 days old (needed 2 days)
• ruby-jquery-atwho-rails (- to 1.5.4+dfsg-1)
  • Migration status for ruby-jquery-atwho-rails (- to 1.5.4+dfsg-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
  • Depends: ruby-jquery-atwho-rails jquery-at.js
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jquery-atwho-rails.html
  • Required age reduced by 3 days because of autopkgtest
  • 461 days old (needed 2 days)
• ring (- to 20190215.1.f152c98~ds1-1)
  • Migration status for ring (- to 20190215.1.f152c98~ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): ring restbed (not considered)
  • Depends: ring restbed (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ring.html
  • 464 days old (needed 5 days)
• python-static3 (- to 0.7.0-6)
  • Migration status for python-static3 (- to 0.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-static3 introduces new bugs: #950065
  • Not built on buildd: arch all binaries uploaded by hpfn, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-static3.html
  • Required age reduced by 3 days because of autopkgtest
  • 467 days old (needed 2 days)
• filemanager-actions (- to 3.4-2)
  • Migration status for filemanager-actions (- to 3.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating filemanager-actions introduces new bugs: #922129, #947520
  • Not built on buildd: arch amd64 binaries uploaded by jeremy@bicha.net
  • Not built on buildd: arch all binaries uploaded by jeremy@bicha.net, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): filemanager-actions gnome-doc-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/filemanager-actions.html
  • Required age reduced by 3 days because of autopkgtest
  • 470 days old (needed 2 days)
• mongo-tools (- to 3.4.14-4)
  • Migration status for mongo-tools (- to 3.4.14-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mongo-tools introduces new bugs: #935286
  • mongo-tools/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mongo-tools/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mongo-tools/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mongo-tools/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mongo-tools/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mongo-tools/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mongo-tools/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mongo-tools/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • mongo-tools/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • Not built on buildd: arch amd64 binaries uploaded by apoikos@dmesg.gr
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongo-tools.html
  • 471 days old (needed 5 days)
• erlang-ranch (- to 1.3.0-2)
  • Migration status for erlang-ranch (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by iwamatsu
  • Not built on buildd: arch all binaries uploaded by iwamatsu, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-ranch.html
  • 472 days old (needed 5 days)
• crossfire (- to 1.71.0+dfsg1-2)
  • Migration status for crossfire (- to 1.71.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating crossfire introduces new bugs: #936344
  • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crossfire.html
  • 474 days old (needed 5 days)
• diaspora (- to 0.7.9.0+dfsg-4)
  • Migration status for diaspora (- to 0.7.9.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating diaspora introduces new bugs: #924109
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/diaspora.html
  • autopkgtest for diaspora/0.7.9.0+dfsg-4: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Depends: diaspora ruby-handlebars-assets
  • Additional info:
  • 474 days old (needed 5 days)
• veusz (- to 3.0.1-1)
  • Migration status for veusz (- to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-veusz.helpers/armel has unsatisfiable dependency
  • python3-veusz.helpers/armhf has unsatisfiable dependency
  • python3-veusz.helpers/i386 has unsatisfiable dependency
  • Updating veusz introduces new bugs: #945467
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/veusz.html
  • Required age reduced by 3 days because of autopkgtest
  • 474 days old (needed 2 days)
• broccoli-ruby (- to 1.62-1)
  • Migration status for broccoli-ruby (- to 1.62-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating broccoli-ruby introduces new bugs: #951717
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/broccoli-ruby.html
  • 475 days old (needed 5 days)
• fades (- to 8.1-1)
  • Migration status for fades (- to 8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fades introduces new bugs: #950858
  • autopkgtest for fades/8.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by inaki@malerba.space, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fades.html
  • 475 days old (needed 5 days)
• libvma (- to 8.8.1.really.8.7.7-1)
  • Migration status for libvma (- to 8.8.1.really.8.7.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libvma introduces new bugs: #934384
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvma.html
  • 475 days old (needed 5 days)
• nostalgy (- to 0.2.36-1.2)
  • Migration status for nostalgy (- to 0.2.36-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating nostalgy introduces new bugs: #953182
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nostalgy.html
  • 475 days old (needed 5 days)
• courier (- to 1.0.6-1)
  • Migration status for courier (- to 1.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating courier introduces new bugs: #933948, #946591
  • Not built on buildd: arch all binaries uploaded by markus@bluegap.ch, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier.html
  • 477 days old (needed 5 days)
• mpqc (- to 2.3.1-19)
  • Migration status for mpqc (- to 2.3.1-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mpqc introduces new bugs: #951999
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpqc.html
  • 477 days old (needed 5 days)
• unanimity (- to 3.3.0+dfsg-2.1)
  • Migration status for unanimity (- to 3.3.0+dfsg-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • unanimity/amd64 has unsatisfiable dependency
  • unanimity/arm64 has unsatisfiable dependency
  • unanimity/mips64el has unsatisfiable dependency
  • unanimity/ppc64el has unsatisfiable dependency
  • Updating unanimity introduces new bugs: #938751, #939506
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unanimity.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 477 days old (needed 5 days)
• nipype (- to 1.1.8-1)
  • Migration status for nipype (- to 1.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-nipype/amd64 has unsatisfiable dependency
  • python-nipype/i386 has unsatisfiable dependency
  • Updating nipype introduces new bugs: #932197, #937144
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-concurrent.futures
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 0.6)
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-dateutil (>= 2.2)
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-numpydoc
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-packaging
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-pytest
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-pytest-xdist
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-pydot
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-pydotplus
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-click
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-simplejson
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-traits (>= 4.5.0) | python-traits4 (>= 4.5)
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-scipy
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-matplotlib
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-sympy
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-nibabel (>= 1.0.0~)
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-nitime
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-nipy (>= 0.1.2+20101206-1~)
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-mock
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-networkx (>= 1.3)
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-future
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-psutil
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: python-prov
  • nipype unsatisfiable Build-Depends(-Arch) on amd64: ipython (>= 1~) | ipython1x
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nipype.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 478 days old (needed 5 days)
• rust-difference (- to 2.0.0-1)
  • Migration status for rust-difference (- to 2.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-difference rust-getopts (not considered)
  • Depends: rust-difference rust-getopts (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-difference.html
  • 479 days old (needed 5 days)
• python-cjson (- to 1.2.1-1)
  • Migration status for python-cjson (- to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-cjson introduces new bugs: #937645
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cjson.html
  • 480 days old (needed 5 days)
• mlucas (- to 17.1-3)
  • Migration status for mlucas (- to 17.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mlucas introduces new bugs: #945666
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlucas.html
  • 481 days old (needed 5 days)
• node-millstone (- to 0.6.17-2)
  • Migration status for node-millstone (- to 0.6.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): node-millstone node-srs (not considered)
  • Depends: node-millstone node-srs (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-millstone.html
  • Required age reduced by 3 days because of autopkgtest
  • 482 days old (needed 2 days)
• igv (- to 2.4.17+dfsg-1)
  • Migration status for igv (- to 2.4.17+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • igv/i386 has unsatisfiable dependency
  • Build-Depends(-Arch): igv jhdf
  • Depends: igv jhdf
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • uninstallable on arch arm64, not running autopkgtest there
  • 483 days old (needed 5 days)
• simpleitk (- to 1.0.1-3)
  • Migration status for simpleitk (- to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-simpleitk/amd64 has unsatisfiable dependency
  • python3-simpleitk/i386 has unsatisfiable dependency
  • Updating simpleitk introduces new bugs: #949355
  • Impossible Depends: simpleitk -> libgdcm2.8/2.8.8-9+b1/amd64
  • Impossible Depends: simpleitk -> libgdcm2.8/2.8.8-9+b1/i386
  • Impossible Depends: simpleitk -> libhdf5-cpp-103/1.10.4+repack-11/amd64
  • Impossible Depends: simpleitk -> libhdf5-cpp-103/1.10.4+repack-11/i386
  • Impossible Depends: simpleitk -> libinsighttoolkit4.12/4.12.2-dfsg1-4+b2/amd64
  • Impossible Depends: simpleitk -> libinsighttoolkit4.12/4.12.2-dfsg1-4.1/i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simpleitk.html
  • uninstallable on arch amd64, not running autopkgtest there
  • 484 days old (needed 5 days)
• sshuttle (- to 0.78.5-1)
  • Migration status for sshuttle (- to 0.78.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sshuttle introduces new bugs: #943238, #953621
  • sshuttle unsatisfiable Build-Depends(-Arch) on amd64: python-pytest-runner
  • sshuttle unsatisfiable Build-Depends(-Arch) on amd64: python-pytest-cov
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sshuttle.html
  • 485 days old (needed 5 days)
• sqwebmail-de (- to 6.0.0-1)
  • Migration status for sqwebmail-de (- to 6.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): sqwebmail-de courier (not considered)
  • Built-Using: sqwebmail-de courier (not considered)
  • Depends: sqwebmail-de courier (not considered)
  • Invalidated by build-dependency
  • Invalidated by built-using
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqwebmail-de.html
  • 486 days old (needed 5 days)
• ovirt-guest-agent (- to 1.0.15.dfsg-1)
  • Migration status for ovirt-guest-agent (- to 1.0.15.dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ovirt-guest-agent/amd64 has unsatisfiable dependency
  • ovirt-guest-agent/i386 has unsatisfiable dependency
  • Updating ovirt-guest-agent introduces new bugs: #937224, #949982, #950078
  • ovirt-guest-agent unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ovirt-guest-agent.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 487 days old (needed 5 days)
• ndiswrapper (- to 1.60-8)
  • Migration status for ndiswrapper (- to 1.60-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ndiswrapper introduces new bugs: #942148
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ndiswrapper.html
  • 488 days old (needed 5 days)
• node-srs (- to 0.4.8+dfsg-4)
  • Migration status for node-srs (- to 0.4.8+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating node-srs introduces new bugs: #949027
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-srs.html
  • Required age reduced by 3 days because of autopkgtest
  • 488 days old (needed 2 days)
• dhex (- to 0.69-1)
  • Migration status for dhex (- to 0.69-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dhex introduces new bugs: #940536
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dhex.html
  • 490 days old (needed 5 days)
• rust-tokio-reactor (- to 0.1.8-1)
  • Migration status for rust-tokio-reactor (- to 0.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-tokio-reactor-dev/amd64 has unsatisfiable dependency
  • librust-tokio-reactor-dev/arm64 has unsatisfiable dependency
  • librust-tokio-reactor-dev/armel has unsatisfiable dependency
  • librust-tokio-reactor-dev/armhf has unsatisfiable dependency
  • librust-tokio-reactor-dev/i386 has unsatisfiable dependency
  • librust-tokio-reactor-dev/mips64el has unsatisfiable dependency
  • librust-tokio-reactor-dev/mipsel has unsatisfiable dependency
  • librust-tokio-reactor-dev/ppc64el has unsatisfiable dependency
  • librust-tokio-reactor-dev/s390x has unsatisfiable dependency
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-utils-0.6+default-dev
  • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-utils-0.6+default-dev
  • Build-Depends(-Arch): rust-tokio-reactor rust-tokio-executor
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-reactor.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 491 days old (needed 5 days)
• vdirsyncer (- to 0.16.7-2)
  • Migration status for vdirsyncer (- to 0.16.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vdirsyncer introduces new bugs: #951948
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdirsyncer.html
  • Required age reduced by 3 days because of autopkgtest
  • 492 days old (needed 2 days)
• asterisk-espeak (- to 5.0~1-3)
  • Migration status for asterisk-espeak (- to 5.0~1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating asterisk-espeak introduces new bugs: #947510
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-espeak.html
  • Required age reduced by 3 days because of autopkgtest
  • 493 days old (needed 2 days)
• gnucap-python (- to 0.0.2-1.1)
  • Migration status for gnucap-python (- to 0.0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnucap-python introduces new bugs: #936628
  • gnucap-python unsatisfiable Build-Depends(-Arch) on amd64: python-scipy
  • gnucap-python unsatisfiable Build-Depends(-Arch) on arm64: python-scipy
  • gnucap-python unsatisfiable Build-Depends(-Arch) on armel: python-scipy
  • gnucap-python unsatisfiable Build-Depends(-Arch) on armhf: python-scipy
  • gnucap-python unsatisfiable Build-Depends(-Arch) on i386: python-scipy
  • gnucap-python unsatisfiable Build-Depends(-Arch) on mips64el: python-scipy
  • gnucap-python unsatisfiable Build-Depends(-Arch) on mipsel: python-scipy
  • gnucap-python unsatisfiable Build-Depends(-Arch) on ppc64el: python-scipy
  • gnucap-python unsatisfiable Build-Depends(-Arch) on s390x: python-scipy
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnucap-python.html
  • 493 days old (needed 5 days)
• rust-tokio-tcp (- to 0.1.3-1)
  • Migration status for rust-tokio-tcp (- to 0.1.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-tokio-tcp rust-tokio-reactor (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-tcp.html
  • 493 days old (needed 5 days)
• gitano (- to 1.2-1)
  • Migration status for gitano (- to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gitano introduces new bugs: #945415
  • Not built on buildd: arch all binaries uploaded by dsilvers, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitano.html
  • 494 days old (needed 5 days)
• fonts-alegreya-sans (- to 2.008-1)
  • Migration status for fonts-alegreya-sans (- to 2.008-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fonts-alegreya-sans introduces new bugs: #944499
  • Not built on buildd: arch all binaries uploaded by jeremy@bicha.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-alegreya-sans.html
  • 495 days old (needed 5 days)
• nextepc (- to 0.3.10+nods-3)
  • Migration status for nextepc (- to 0.3.10+nods-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • nextepc/i386 has unsatisfiable dependency
  • Updating nextepc introduces new bugs: #954512
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nextepc.html
  • Required age reduced by 3 days because of autopkgtest
  • 495 days old (needed 2 days)
• sieve-extension (- to 0.3.0+dfsg-1)
  • Migration status for sieve-extension (- to 0.3.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sieve-extension introduces new bugs: #918163
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sieve-extension.html
  • 496 days old (needed 5 days)
• dump1090-mutability (- to 1.15~20180310.4a16df3+dfsg-6)
  • Migration status for dump1090-mutability (- to 1.15~20180310.4a16df3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dump1090-mutability introduces new bugs: #945665
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dump1090-mutability.html
  • 497 days old (needed 5 days)
• fsl (- to 5.0.8-6)
  • Migration status for fsl (- to 5.0.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fsl introduces new bugs: #936564
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 498 days old (needed 5 days)
• aseba (- to 1.6.0-5)
  • Migration status for aseba (- to 1.6.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): aseba enki-aseba (not considered)
  • Depends: aseba enki-aseba (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aseba.html
  • 500 days old (needed 5 days)
• prometheus-process-exporter (- to 0.4.0+ds-1)
  • Migration status for prometheus-process-exporter (- to 0.4.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating prometheus-process-exporter introduces new bugs: #948002
  • autopkgtest for prometheus-process-exporter/0.4.0+ds-1: amd64: Regression ♻ , arm64: Regression ♻
  • prometheus-process-exporter/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • prometheus-process-exporter/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • prometheus-process-exporter/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • prometheus-process-exporter/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • prometheus-process-exporter/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • prometheus-process-exporter/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • prometheus-process-exporter/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • prometheus-process-exporter/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • prometheus-process-exporter/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-process-exporter.html
  • 500 days old (needed 5 days)
• python-pytc (- to 0.8-3)
  • Migration status for python-pytc (- to 0.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-pytc introduces new bugs: #938101
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pytc.html
  • 501 days old (needed 5 days)
• rivet (- to 1.8.3-3)
  • Migration status for rivet (- to 1.8.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rivet hepmc (not considered)
  • Depends: rivet hepmc (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rivet.html
  • 502 days old (needed 5 days)
• vibe.d (- to 0.8.4-2)
  • Migration status for vibe.d (- to 0.8.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vibe.d introduces new bugs: #941453
  • Impossible Depends: vibe.d -> libevent-2.1-6/2.1.8-stable-4/amd64
  • Impossible Depends: vibe.d -> libevent-2.1-6/2.1.8-stable-4/arm64
  • Impossible Depends: vibe.d -> libevent-2.1-6/2.1.8-stable-4/armhf
  • Impossible Depends: vibe.d -> libevent-2.1-6/2.1.8-stable-4/i386
  • Impossible Depends: vibe.d -> libphobos2-ldc-shared82/1:1.12.0-1+b1/amd64
  • Impossible Depends: vibe.d -> libphobos2-ldc-shared82/1:1.12.0-1+b1/arm64
  • Impossible Depends: vibe.d -> libphobos2-ldc-shared82/1:1.12.0-1+b1/armhf
  • Impossible Depends: vibe.d -> libphobos2-ldc-shared82/1:1.12.0-1+b1/i386
  • Build-Depends(-Arch): vibe.d diet-ng
  • Depends: vibe.d diet-ng
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vibe.d.html
  • 502 days old (needed 5 days)
• oss4 (- to 4.2-build2017-1)
  • Migration status for oss4 (- to 4.2-build2017-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating oss4 introduces new bugs: #796636, #919246
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/oss4.html
  • Not built on buildd: arch all binaries uploaded by sthibault, a new source-only upload is needed to allow migration
  • Additional info:
  • 505 days old (needed 5 days)
• gjots2 (- to 3.0.2-0.1)
  • Migration status for gjots2 (- to 3.0.2-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gjots2 introduces new bugs: #936619
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gjots2.html
  • 506 days old (needed 5 days)
• nat-rtsp (- to 0.7+4.18-0.1)
  • Migration status for nat-rtsp (- to 0.7+4.18-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating nat-rtsp introduces new bugs: #955488
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nat-rtsp.html
  • 506 days old (needed 5 days)
• vorbis-java (- to 0.8-3)
  • Migration status for vorbis-java (- to 0.8-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): vorbis-java tika (not considered)
  • Depends: vorbis-java tika (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vorbis-java.html
  • 507 days old (needed 5 days)
• octave-mpi (- to 1.2.0-6)
  • Migration status for octave-mpi (- to 1.2.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • octave-mpi/amd64 has unsatisfiable dependency
  • octave-mpi/arm64 has unsatisfiable dependency
  • octave-mpi/armel has unsatisfiable dependency
  • octave-mpi/armhf has unsatisfiable dependency
  • octave-mpi/i386 has unsatisfiable dependency
  • octave-mpi/mips64el has unsatisfiable dependency
  • octave-mpi/mipsel has unsatisfiable dependency
  • octave-mpi/ppc64el has unsatisfiable dependency
  • octave-mpi/s390x has unsatisfiable dependency
  • Updating octave-mpi introduces new bugs: #945323
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-mpi.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 508 days old (needed 5 days)
• rust-nom-3 (- to 3.2.1-2)
  • Migration status for rust-nom-3 (- to 3.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • librust-nom-3+compiler-error-dev/amd64 has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/amd64 has unsatisfiable dependency
  • librust-nom-3+nightly-dev/amd64 has unsatisfiable dependency
  • librust-nom-3+regex-dev/amd64 has unsatisfiable dependency
  • librust-nom-3+regexp-dev/amd64 has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/amd64 has unsatisfiable dependency
  • librust-nom-3+compiler-error-dev/arm64 has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/arm64 has unsatisfiable dependency
  • librust-nom-3+nightly-dev/arm64 has unsatisfiable dependency
  • librust-nom-3+regex-dev/arm64 has unsatisfiable dependency
  • librust-nom-3+regexp-dev/arm64 has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/arm64 has unsatisfiable dependency
  • librust-nom-3+compiler-error-dev/armel has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/armel has unsatisfiable dependency
  • librust-nom-3+nightly-dev/armel has unsatisfiable dependency
  • librust-nom-3+regex-dev/armel has unsatisfiable dependency
  • librust-nom-3+regexp-dev/armel has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/armel has unsatisfiable dependency
  • librust-nom-3+compiler-error-dev/armhf has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/armhf has unsatisfiable dependency
  • librust-nom-3+nightly-dev/armhf has unsatisfiable dependency
  • librust-nom-3+regex-dev/armhf has unsatisfiable dependency
  • librust-nom-3+regexp-dev/armhf has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/armhf has unsatisfiable dependency
  • librust-nom-3+compiler-error-dev/i386 has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/i386 has unsatisfiable dependency
  • librust-nom-3+nightly-dev/i386 has unsatisfiable dependency
  • librust-nom-3+regex-dev/i386 has unsatisfiable dependency
  • librust-nom-3+regexp-dev/i386 has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/i386 has unsatisfiable dependency
  • librust-nom-3+compiler-error-dev/mips64el has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/mips64el has unsatisfiable dependency
  • librust-nom-3+nightly-dev/mips64el has unsatisfiable dependency
  • librust-nom-3+regex-dev/mips64el has unsatisfiable dependency
  • librust-nom-3+regexp-dev/mips64el has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/mips64el has unsatisfiable dependency
  • librust-nom-3+compiler-error-dev/mipsel has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/mipsel has unsatisfiable dependency
  • librust-nom-3+nightly-dev/mipsel has unsatisfiable dependency
  • librust-nom-3+regex-dev/mipsel has unsatisfiable dependency
  • librust-nom-3+regexp-dev/mipsel has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/mipsel has unsatisfiable dependency
  • librust-nom-3+compiler-error-dev/ppc64el has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/ppc64el has unsatisfiable dependency
  • librust-nom-3+nightly-dev/ppc64el has unsatisfiable dependency
  • librust-nom-3+regex-dev/ppc64el has unsatisfiable dependency
  • librust-nom-3+regexp-dev/ppc64el has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/ppc64el has unsatisfiable dependency
  • librust-nom-3+compiler-error-dev/s390x has unsatisfiable dependency
  • librust-nom-3+lazy-static-dev/s390x has unsatisfiable dependency
  • librust-nom-3+nightly-dev/s390x has unsatisfiable dependency
  • librust-nom-3+regex-dev/s390x has unsatisfiable dependency
  • librust-nom-3+regexp-dev/s390x has unsatisfiable dependency
  • librust-nom-3+regexp-macros-dev/s390x has unsatisfiable dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-nom-3.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 508 days old (needed 5 days)
• peframe (- to 5.0.1+git20170303.0.e482def+dfsg-3)
  • Migration status for peframe (- to 5.0.1+git20170303.0.e482def+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • peframe/amd64 has unsatisfiable dependency
  • peframe/i386 has unsatisfiable dependency
  • Updating peframe introduces new bugs: #937269
  • peframe unsatisfiable Build-Depends(-Arch) on amd64: python-pefile
  • peframe unsatisfiable Build-Depends(-Arch) on amd64: python-magic
  • Not built on buildd: arch all binaries uploaded by satta@tetrinetsucht.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/peframe.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 509 days old (needed 5 days)
• resteasy (- to 3.6.2-2)
  • Migration status for resteasy (- to 3.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating resteasy introduces new bugs: #879469
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resteasy.html
  • 512 days old (needed 5 days)
• bagel (- to 1.2.2-1)
  • Migration status for bagel (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating bagel introduces new bugs: #952463
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bagel.html
  • Required age reduced by 3 days because of autopkgtest
  • 513 days old (needed 2 days)
• haskell-termonad (- to 0.2.1.0-2)
  • Migration status for haskell-termonad (- to 0.2.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): haskell-termonad haskell-gi-vte (not considered)
  • Build-Depends-Indep: haskell-termonad haskell-gi-vte (not considered)
  • Depends: haskell-termonad haskell-gi-vte (not considered)
  • Invalidated by build-dependency
  • Invalidated by build-dependency (indep)
  • Invalidated by dependency
  • Depends: haskell-termonad haskell-gi-gdk
  • Depends: haskell-termonad haskell-gi-gtk
  • Depends: haskell-termonad haskell-gi-pango
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-termonad.html
  • 514 days old (needed 5 days)
• photocollage (- to 1.4.3-2.1)
  • Migration status for photocollage (- to 1.4.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating photocollage introduces new bugs: #952336
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/photocollage.html
  • 514 days old (needed 5 days)
• owncloud-client (- to 2.5.1.10973+dfsg-1)
  • Migration status for owncloud-client (- to 2.5.1.10973+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • caja-owncloud/amd64 has unsatisfiable dependency
  • nautilus-owncloud/amd64 has unsatisfiable dependency
  • caja-owncloud/i386 has unsatisfiable dependency
  • nautilus-owncloud/i386 has unsatisfiable dependency
  • Updating owncloud-client introduces new bugs: #933290, #945718
  • Impossible Build-Depends-Indep: owncloud-client -> texlive-generic-extra/2018.20190227-2/amd64
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/owncloud-client.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 516 days old (needed 5 days)
• haskell-gi-dbusmenugtk3 (- to 0.4.2-1)
  • Migration status for haskell-gi-dbusmenugtk3 (- 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 schizo, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): haskell-gi-dbusmenugtk3 haskell-gi-gtk
  • Build-Depends-Indep: haskell-gi-dbusmenugtk3 haskell-gi-gtk
  • Depends: haskell-gi-dbusmenugtk3 haskell-gi-gdk
  • Depends: haskell-gi-dbusmenugtk3 haskell-gi-gtk
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-dbusmenugtk3.html
  • 517 days old (needed 5 days)
• haskell-gi-gdk (- to 3.0.16-1)
  • Migration status for haskell-gi-gdk (- to 3.0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): haskell-gi-gdk haskell-gi-pango
  • Build-Depends-Indep: haskell-gi-gdk haskell-gi-pango
  • Depends: haskell-gi-gdk haskell-gi-pango
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gdk.html
  • 517 days old (needed 5 days)
• haskell-gi-gdkx11 (- to 3.0.2-1)
  • Migration status for haskell-gi-gdkx11 (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): haskell-gi-gdkx11 haskell-gi-gdk
  • Build-Depends-Indep: haskell-gi-gdkx11 haskell-gi-gdk
  • Depends: haskell-gi-gdkx11 haskell-gi-gdk
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gdkx11.html
  • 517 days old (needed 5 days)
• haskell-gi-vte (- to 2.91.19-1)
  • Migration status for haskell-gi-vte (- to 2.91.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): haskell-gi-vte haskell-gi-pango
  • Build-Depends-Indep: haskell-gi-vte haskell-gi-pango
  • Depends: haskell-gi-vte haskell-gi-gdk
  • Depends: haskell-gi-vte haskell-gi-gtk
  • Depends: haskell-gi-vte haskell-gi-pango
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-vte.html
  • 517 days old (needed 5 days)
• freshplayerplugin (- to 0.3.9-2)
  • Migration status for freshplayerplugin (- to 0.3.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating freshplayerplugin introduces new bugs: #947288, #949478
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 519 days old (needed 5 days)
• gnome-doc-utils (- to 0.20.10-5)
  • Migration status for gnome-doc-utils (- to 0.20.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnome-doc-utils introduces new bugs: #889019
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-doc-utils.html
  • 521 days old (needed 5 days)
• redeclipse (- to 1.6.0-1)
  • Migration status for redeclipse (- to 1.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: redeclipse redeclipse-data (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redeclipse.html
  • 521 days old (needed 5 days)
• redeclipse-data (- to 1.6.0-1)
  • Migration status for redeclipse-data (- to 1.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): redeclipse-data fonts-play (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redeclipse-data.html
  • 521 days old (needed 5 days)
• coyim (- to 0.3.8+ds-6)
  • Migration status for coyim (- to 0.3.8+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating coyim introduces new bugs: #930332
  • coyim/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • coyim/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • coyim/arm64 has unsatisfiable Built-Using on golang-1.10 1.10.7-1
  • coyim/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-2
  • coyim/armel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • coyim/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • coyim/armhf has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • coyim/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • coyim/i386 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • coyim/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • coyim/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • coyim/mipsel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • coyim/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • coyim/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • coyim/s390x has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • coyim/s390x has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coyim.html
  • 522 days old (needed 5 days)
• mp3check (- to 0.8.7-3)
  • Migration status for mp3check (- to 0.8.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mp3check introduces new bugs: #925782
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mp3check.html
  • 522 days old (needed 5 days)
• rust-cargo-lichking (- to 0.7.0-1)
  • Migration status for rust-cargo-lichking (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-cargo-lichking introduces new bugs: #943306
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on amd64: librust-cargo-0.32+default-dev
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on arm64: librust-cargo-0.32+default-dev
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on armel: librust-cargo-0.32+default-dev
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on armhf: librust-cargo-0.32+default-dev
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on i386: librust-cargo-0.32+default-dev
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on mips64el: librust-cargo-0.32+default-dev
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on mipsel: librust-cargo-0.32+default-dev
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on ppc64el: librust-cargo-0.32+default-dev
  • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on s390x: librust-cargo-0.32+default-dev
  • Not built on buildd: arch amd64 binaries uploaded by kraai
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/amd64
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/arm64
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/armel
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/armhf
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/i386
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/mips64el
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/mipsel
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/ppc64el
  • Impossible Depends: rust-cargo-lichking -> libgit2-27/0.27.7+dfsg.1-0.2+b1/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-lichking.html
  • 522 days old (needed 5 days)
• gnome-pie (- to 0.7.2-1)
  • Migration status for gnome-pie (- to 0.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnome-pie introduces new bugs: #948129
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-pie.html
  • 523 days old (needed 5 days)
• open-ath9k-htc-firmware (- to 1.4.0-97-g75b3e59+dfsg-3)
  • Migration status for open-ath9k-htc-firmware (- to 1.4.0-97-g75b3e59+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating open-ath9k-htc-firmware introduces new bugs: #944169, #951891
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-ath9k-htc-firmware.html
  • 523 days old (needed 5 days)
• xapers (- to 0.8.2-1.1)
  • Migration status for xapers (- to 0.8.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xapers introduces new bugs: #923327
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xapers.html
  • Required age reduced by 3 days because of autopkgtest
  • 523 days old (needed 2 days)
• gemma (- to 0.98.1+dfsg-1)
  • Migration status for gemma (- to 0.98.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gemma introduces new bugs: #952190
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gemma.html
  • Required age reduced by 3 days because of autopkgtest
  • 526 days old (needed 2 days)
• dewalls (- to 1.0.0+ds1-7)
  • Migration status for dewalls (- to 1.0.0+ds1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dewalls introduces new bugs: #925669
  • Not built on buildd: arch amd64 binaries uploaded by wookey
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dewalls.html
  • 527 days old (needed 5 days)
• freeture (- to 1.3.0-1)
  • Migration status for freeture (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating freeture introduces new bugs: #922579
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-core3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-flann3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-ml3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-video3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: freeture -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freeture.html
  • 527 days old (needed 5 days)
• mpqc3 (- to 0.0~git20170114-4.1)
  • Migration status for mpqc3 (- to 0.0~git20170114-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mpqc3 introduces new bugs: #946452
  • Impossible Depends: mpqc3 -> libopenbabel5/2.4.1+dfsg-6/amd64
  • Impossible Depends: mpqc3 -> libopenbabel5/2.4.1+dfsg-6/arm64
  • Impossible Depends: mpqc3 -> libopenbabel5/2.4.1+dfsg-6/armel
  • Impossible Depends: mpqc3 -> libopenbabel5/2.4.1+dfsg-6/armhf
  • Impossible Depends: mpqc3 -> libopenbabel5/2.4.1+dfsg-6/i386
  • Impossible Depends: mpqc3 -> libopenbabel5/2.4.1+dfsg-6/mips64el
  • Impossible Depends: mpqc3 -> libopenbabel5/2.4.1+dfsg-6/ppc64el
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpqc3.html
  • 528 days old (needed 5 days)
• vland (- to 0.8-1)
  • Migration status for vland (- to 0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • vland/amd64 has unsatisfiable dependency
  • vland/i386 has unsatisfiable dependency
  • Updating vland introduces new bugs: #938790
  • Not built on buildd: arch all binaries uploaded by 93sam, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vland.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 532 days old (needed 5 days)
• check (0.10.0-3 to 0.12.0-0.1)
  • Migration status for check (0.10.0-3 to 0.12.0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating check introduces new bugs: #918572
  • Not built on buildd: arch amd64 binaries uploaded by guus
  • missing build on ppc64el
  • Additional info:
  • Updating check fixes old bugs: #951667
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check.html
  • 534 days old (needed 5 days)
• erlang-cuttlefish (- to 2.0.11+dfsg-4)
  • Migration status for erlang-cuttlefish (- to 2.0.11+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating erlang-cuttlefish introduces new bugs: #935279
  • Not built on buildd: arch amd64 binaries uploaded by iwamatsu
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-cuttlefish.html
  • 535 days old (needed 5 days)
• mongo-cxx-driver-legacy (- to 1.1.3-3)
  • Migration status for mongo-cxx-driver-legacy (- to 1.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mongo-cxx-driver-legacy introduces new bugs: #947569
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongo-cxx-driver-legacy.html
  • 538 days old (needed 5 days)
• python-thinc (- to 6.12.1-1)
  • Migration status for python-thinc (- to 6.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-thinc/amd64 has unsatisfiable dependency
  • python3-thinc/arm64 has unsatisfiable dependency
  • python3-thinc/armel has unsatisfiable dependency
  • python3-thinc/armhf has unsatisfiable dependency
  • python3-thinc/i386 has unsatisfiable dependency
  • python3-thinc/mips64el has unsatisfiable dependency
  • python3-thinc/mipsel has unsatisfiable dependency
  • python3-thinc/ppc64el has unsatisfiable dependency
  • python3-thinc/s390x has unsatisfiable dependency
  • Updating python-thinc introduces new bugs: #947111
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-thinc.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 539 days old (needed 5 days)
• spyder-reports (- to 0.1.1-3)
  • Migration status for spyder-reports (- to 0.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating spyder-reports introduces new bugs: #954612
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spyder-reports.html
  • Required age reduced by 3 days because of autopkgtest
  • 539 days old (needed 2 days)
• libgtextutils (- to 0.7-6)
  • Migration status for libgtextutils (- to 0.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libgtextutils introduces new bugs: #925745
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgtextutils.html
  • 541 days old (needed 5 days)
• xiphos (- to 4.1.0.1+dfsg1-1)
  • Migration status for xiphos (- to 4.1.0.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xiphos introduces new bugs: #947542
  • Build-Depends(-Arch): xiphos gnome-doc-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xiphos.html
  • 541 days old (needed 5 days)
• rust-nodrop (- to 0.1.13-1)
  • Migration status for rust-nodrop (- to 0.1.13-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: rust-nodrop rust-nodrop-union (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nodrop.html
  • 542 days old (needed 5 days)
• rng-tools (- to 5-1)
  • Migration status for rng-tools (- to 5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rng-tools introduces new bugs: #915689, #919412, #951799
  • rng-tools unsatisfiable Build-Depends(-Arch) on amd64: libgcrypt11-dev
  • rng-tools unsatisfiable Build-Depends(-Arch) on arm64: libgcrypt11-dev
  • rng-tools unsatisfiable Build-Depends(-Arch) on armel: libgcrypt11-dev
  • rng-tools unsatisfiable Build-Depends(-Arch) on armhf: libgcrypt11-dev
  • rng-tools unsatisfiable Build-Depends(-Arch) on i386: libgcrypt11-dev
  • rng-tools unsatisfiable Build-Depends(-Arch) on mips64el: libgcrypt11-dev
  • rng-tools unsatisfiable Build-Depends(-Arch) on mipsel: libgcrypt11-dev
  • rng-tools unsatisfiable Build-Depends(-Arch) on ppc64el: libgcrypt11-dev
  • rng-tools unsatisfiable Build-Depends(-Arch) on s390x: libgcrypt11-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rng-tools.html
  • 543 days old (needed 5 days)
• tootle (- to 0.2.0-2)
  • Migration status for tootle (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tootle introduces new bugs: #952099
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tootle.html
  • 543 days old (needed 5 days)
• python-hug (- to 2.4.1-1)
  • Migration status for python-hug (- to 2.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-hug introduces new bugs: #904576, #916022, #953258
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/python-hug.html
  • autopkgtest for python-hug/2.4.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • 544 days old (needed 5 days)
• rust-servo-arc (- to 0.1.1-1)
  • Migration status for rust-servo-arc (- to 0.1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-servo-arc rust-nodrop (not considered)
  • Depends: rust-servo-arc rust-nodrop (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-servo-arc.html
  • 549 days old (needed 5 days)
• libhtml-calendarmonth-perl (- to 2.04-2)
  • Migration status for libhtml-calendarmonth-perl (- to 2.04-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libhtml-calendarmonth-perl introduces new bugs: #952219
  • Not built on buildd: arch all binaries uploaded by don, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhtml-calendarmonth-perl.html
  • 550 days old (needed 5 days)
• golang-golang-x-exp (- to 0.0~git20181112.a3060d4-1)
  • Migration status for golang-golang-x-exp (- to 0.0~git20181112.a3060d4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-golang-x-exp introduces new bugs: #918417
  • ebnflint/amd64 has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • ebnflint/arm64 has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • ebnflint/armel has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • ebnflint/armhf has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • ebnflint/i386 has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • ebnflint/mips64el has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • ebnflint/mipsel has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • ebnflint/ppc64el has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • ebnflint/s390x has unsatisfiable Built-Using on golang-1.10 1.10.4-2
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-golang-x-exp.html
  • 553 days old (needed 5 days)
• rust-pulldown-cmark (- to 0.2.0-1)
  • Migration status for rust-pulldown-cmark (- to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): rust-pulldown-cmark rust-getopts (not considered)
  • Depends: rust-pulldown-cmark rust-getopts (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pulldown-cmark.html
  • 555 days old (needed 5 days)
• din (- to 5.2.1-6)
  • Migration status for din (- to 5.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating din introduces new bugs: #948074
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/din.html
  • 556 days old (needed 5 days)
• openms (- to 2.4.0-real-1)
  • Migration status for openms (- to 2.4.0-real-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openms introduces new bugs: #943450
  • Not built on buildd: arch all binaries uploaded by lopippo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openms.html
  • 557 days old (needed 5 days)
• fonts-beteckna (- to 0.5-2)
  • Migration status for fonts-beteckna (- to 0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fonts-beteckna introduces new bugs: #944505
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-beteckna.html
  • 558 days old (needed 5 days)
• openstereogram (- to 0.1+20080921-3)
  • Migration status for openstereogram (- to 0.1+20080921-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): openstereogram netbeans (not considered)
  • Depends: openstereogram netbeans (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstereogram.html
  • 561 days old (needed 5 days)
• django-test-without-migrations (- to 0.6-5)
  • Migration status for django-test-without-migrations (- to 0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating django-test-without-migrations introduces new bugs: #915041
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-test-without-migrations.html
  • Required age reduced by 3 days because of autopkgtest
  • 562 days old (needed 2 days)
• evqueue-core (- to 2.1-1)
  • Migration status for evqueue-core (- to 2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating evqueue-core introduces new bugs: #914801
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/evqueue-core.html
  • Additional info:
  • 562 days old (needed 5 days)
• faumachine (- to 20180503-4)
  • Migration status for faumachine (- to 20180503-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating faumachine introduces new bugs: #925676
  • Not built on buildd: arch amd64 binaries uploaded by fuddl
  • Not built on buildd: arch all binaries uploaded by fuddl, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/faumachine.html
  • 564 days old (needed 5 days)
• python-louvain (- to 0.0+20181013git3fc1f575-1)
  • Migration status for python-louvain (- to 0.0+20181013git3fc1f575-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-louvain introduces new bugs: #913377
  • autopkgtest for python-louvain/0.0+20181013git3fc1f575-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by moeller, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-louvain.html
  • 565 days old (needed 5 days)
• squeak-plugins-scratch (- to 1.4.0.2~svn.r83-3)
  • Migration status for squeak-plugins-scratch (- to 1.4.0.2~svn.r83-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating squeak-plugins-scratch introduces new bugs: #909352
  • Not built on buildd: arch amd64 binaries uploaded by miriam
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squeak-plugins-scratch.html
  • 566 days old (needed 5 days)
• haskell-werewolf (- to 1.5.2.0-4)
  • Migration status for haskell-werewolf (- to 1.5.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libghc-werewolf-dev/amd64 has unsatisfiable dependency
  • libghc-werewolf-prof/amd64 has unsatisfiable dependency
  • libghc-werewolf-dev/arm64 has unsatisfiable dependency
  • libghc-werewolf-prof/arm64 has unsatisfiable dependency
  • libghc-werewolf-dev/armel has unsatisfiable dependency
  • libghc-werewolf-prof/armel has unsatisfiable dependency
  • libghc-werewolf-dev/armhf has unsatisfiable dependency
  • libghc-werewolf-prof/armhf has unsatisfiable dependency
  • libghc-werewolf-dev/i386 has unsatisfiable dependency
  • libghc-werewolf-prof/i386 has unsatisfiable dependency
  • libghc-werewolf-dev/mips64el has unsatisfiable dependency
  • libghc-werewolf-prof/mips64el has unsatisfiable dependency
  • libghc-werewolf-dev/mipsel has unsatisfiable dependency
  • libghc-werewolf-prof/mipsel has unsatisfiable dependency
  • libghc-werewolf-dev/ppc64el has unsatisfiable dependency
  • libghc-werewolf-prof/ppc64el has unsatisfiable dependency
  • libghc-werewolf-dev/s390x has unsatisfiable dependency
  • libghc-werewolf-prof/s390x has unsatisfiable dependency
  • Updating haskell-werewolf introduces new bugs: #943479
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-dev (<< 4.17)
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-dev (<< 4.17)
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on armel: libghc-lens-dev (<< 4.17)
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-dev (<< 4.17)
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-dev (<< 4.17)
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on mips64el: libghc-lens-dev (<< 4.17)
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on mipsel: libghc-lens-dev (<< 4.17)
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-dev (<< 4.17)
  • haskell-werewolf unsatisfiable Build-Depends(-Arch) on s390x: libghc-lens-dev (<< 4.17)
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/amd64
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/arm64
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/armel
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/armhf
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/i386
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/mips64el
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/mipsel
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/ppc64el
  • Impossible Depends: haskell-werewolf -> libffi6/3.2.1-9/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-werewolf.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 567 days old (needed 5 days)
• picprog (- to 1.9.1-4)
  • Migration status for picprog (- to 1.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating picprog introduces new bugs: #946039
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picprog.html
  • 567 days old (needed 5 days)
• qiskit-terra (- to 0.5.6-1)
  • Migration status for qiskit-terra (- to 0.5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-qiskit/amd64 has unsatisfiable dependency
  • python3-qiskit/i386 has unsatisfiable dependency
  • Updating qiskit-terra introduces new bugs: #913561
  • Not built on buildd: arch all binaries uploaded by luciano, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by luciano
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/q/qiskit-terra.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 568 days old (needed 5 days)
• arduino-builder (- to 1.3.25-1)
  • Migration status for arduino-builder (- to 1.3.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating arduino-builder introduces new bugs: #952313
  • arduino-builder/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • arduino-builder/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • arduino-builder/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • arduino-builder/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • arduino-builder/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • arduino-builder/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • arduino-builder/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • arduino-builder/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • arduino-builder/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino-builder.html
  • Required age reduced by 3 days because of autopkgtest
  • 569 days old (needed 2 days)
• mxt-app (- to 1.28-2)
  • Migration status for mxt-app (- to 1.28-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mxt-app introduces new bugs: #952059
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mxt-app.html
  • 570 days old (needed 5 days)
• gnome-shell-mailnag (- to 3.28.0-0.1)
  • Migration status for gnome-shell-mailnag (- to 3.28.0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnome-shell-mailnag introduces new bugs: #948128
  • Depends: gnome-shell-mailnag mailnag
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-mailnag.html
  • 571 days old (needed 5 days)
• regina-normal (- to 5.1-6)
  • Migration status for regina-normal (- to 5.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating regina-normal introduces new bugs: #938346
  • Not built on buildd: arch all binaries uploaded by bab, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/regina-normal.html
  • 578 days old (needed 5 days)
• profnet (- to 1.0.22-6)
  • Migration status for profnet (- to 1.0.22-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating profnet introduces new bugs: #905206
  • autopkgtest for profnet/1.0.22-6: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/profnet.html
  • 582 days old (needed 5 days)
• pynast (- to 1.2.2-4)
  • Migration status for pynast (- to 1.2.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pynast introduces new bugs: #937488, #948081
  • autopkgtest for pynast/1.2.2-4: amd64: Regression ♻ , arm64: Regression ♻
  • pynast unsatisfiable Build-Depends(-Arch) on amd64: python-cogent (>= 1.5.3)
  • pynast unsatisfiable Build-Depends(-Arch) on amd64: blast2
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynast.html
  • 582 days old (needed 5 days)
• florence (- to 0.6.3-1.2)
  • Migration status for florence (- to 0.6.3-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating florence introduces new bugs: #947521
  • Build-Depends(-Arch): florence gnome-doc-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/florence.html
  • 584 days old (needed 5 days)
• openshot-qt (- to 2.4.3+dfsg1-1)
  • Migration status for openshot-qt (- to 2.4.3+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openshot-qt introduces new bugs: #940247, #955975
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openshot-qt.html
  • 585 days old (needed 5 days)
• k3d (- to 0.8.0.6-8)
  • Migration status for k3d (- to 0.8.0.6-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • k3d/amd64 has unsatisfiable dependency
  • k3d/arm64 has unsatisfiable dependency
  • k3d/armhf has unsatisfiable dependency
  • k3d/i386 has unsatisfiable dependency
  • k3d/mips64el has unsatisfiable dependency
  • k3d/mipsel has unsatisfiable dependency
  • k3d/ppc64el has unsatisfiable dependency
  • k3d/s390x has unsatisfiable dependency
  • Updating k3d introduces new bugs: #936777, #946228
  • Not built on buildd: arch all binaries uploaded by manuel.montezelo@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/k3d.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 586 days old (needed 5 days)
• profbval (- to 1.0.22-6)
  • Migration status for profbval (- to 1.0.22-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: profbval profnet (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/profbval.html
  • Required age reduced by 3 days because of autopkgtest
  • 588 days old (needed 2 days)
• profisis (- to 1.0.11-5)
  • Migration status for profisis (- to 1.0.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: profisis profnet (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/profisis.html
  • Required age reduced by 3 days because of autopkgtest
  • 592 days old (needed 2 days)
• grokmirror (- to 1.0.0-1.1)
  • Migration status for grokmirror (- to 1.0.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • grokmirror/amd64 has unsatisfiable dependency
  • grokmirror/i386 has unsatisfiable dependency
  • Updating grokmirror introduces new bugs: #936665
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/grokmirror.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 594 days old (needed 5 days)
• rust-nodrop-union (- to 0.1.9-1)
  • Migration status for rust-nodrop-union (- to 0.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rust-nodrop-union introduces new bugs: #952159
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nodrop-union.html
  • 595 days old (needed 5 days)
• libwfut (- to 0.2.3-6)
  • Migration status for libwfut (- to 0.2.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libwfut introduces new bugs: #936939
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwfut.html
  • 598 days old (needed 5 days)
• aws-shell (- to 0.2.1-1)
  • Migration status for aws-shell (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating aws-shell introduces new bugs: #944542
  • 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/a/aws-shell.html
  • 601 days old (needed 5 days)
• haskell-polynomial (- to 0.7.3-5)
  • Migration status for haskell-polynomial (- to 0.7.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-polynomial introduces new bugs: #902901
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-polynomial.html
  • 601 days old (needed 5 days)
• haskell-hit (- to 0.6.3-11)
  • Migration status for haskell-hit (- to 0.6.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-hit introduces new bugs: #911569
  • 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/h/haskell-hit.html
  • 602 days old (needed 5 days)
• mailman-hyperkitty (- to 1.1.0-9)
  • Migration status for mailman-hyperkitty (- to 1.1.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mailman-hyperkitty introduces new bugs: #954604
  • Build-Depends(-Arch): mailman-hyperkitty mailman3
  • Depends: mailman-hyperkitty mailman3
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman-hyperkitty.html
  • Required age reduced by 3 days because of autopkgtest
  • 602 days old (needed 2 days)
• hdbc-odbc (- to 2.5.0.1-2)
  • Migration status for hdbc-odbc (- to 2.5.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hdbc-odbc introduces new bugs: #914353
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on amd64: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on amd64: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on amd64: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on amd64: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on arm64: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on arm64: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on arm64: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on arm64: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on armel: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on armel: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on armel: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on armel: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on armhf: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on armhf: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on armhf: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on armhf: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on i386: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on i386: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on i386: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on i386: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on mips64el: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on mips64el: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on mipsel: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on mipsel: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on mipsel: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on mipsel: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on ppc64el: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on ppc64el: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on s390x: libghc-concurrent-extra-dev (>= 0.7.0.8)
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on s390x: libghc-concurrent-extra-prof
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on s390x: libodbc-dev
  • hdbc-odbc unsatisfiable Build-Depends(-Arch) on s390x: libpthread-dev
  • hdbc-odbc unsatisfiable Build-Depends-Indep on amd64: libghc-concurrent-extra-doc
  • 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/h/hdbc-odbc.html
  • 604 days old (needed 5 days)
• uuagc (- to 0.9.52.1-2)
  • Migration status for uuagc (- to 0.9.52.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating uuagc introduces new bugs: #912241
  • missing build on amd64
  • missing build on arm64
  • missing build on armhf
  • missing build on i386
  • missing build on ppc64el
  • missing build on s390x
  • arch:amd64 not built yet, autopkgtest delayed there
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uuagc.html
  • 604 days old (needed 5 days)
• haskell-dpkg (- to 0.0.3-12)
  • Migration status for haskell-dpkg (- to 0.0.3-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating haskell-dpkg introduces new bugs: #880879
  • 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/h/haskell-dpkg.html
  • 605 days old (needed 5 days)
• dh-virtualenv (- to 1.1-1)
  • Migration status for dh-virtualenv (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dh-virtualenv introduces new bugs: #936392
  • dh-virtualenv unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
  • dh-virtualenv unsatisfiable Build-Depends(-Arch) on amd64: python-mock
  • dh-virtualenv unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx-rtd-theme
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-virtualenv.html
  • 611 days old (needed 5 days)
• libopenshot (- to 0.2.2+dfsg1-1)
  • Migration status for libopenshot (- to 0.2.2+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-openshot/amd64 has unsatisfiable dependency
  • python3-openshot/arm64 has unsatisfiable dependency
  • python3-openshot/armel has unsatisfiable dependency
  • python3-openshot/armhf has unsatisfiable dependency
  • python3-openshot/i386 has unsatisfiable dependency
  • python3-openshot/mips64el has unsatisfiable dependency
  • python3-openshot/mipsel has unsatisfiable dependency
  • python3-openshot/s390x has unsatisfiable dependency
  • Updating libopenshot introduces new bugs: #925754, #949216, #955156
  • Not built on buildd: arch all binaries uploaded by toddy, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libopenshot libopenshot-audio
  • Depends: libopenshot libopenshot-audio
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libo/libopenshot.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 612 days old (needed 5 days)
• networking-arista (- to 2018.1.0+2018.08.21.git.3adf6272bd-1)
  • Migration status for networking-arista (- to 2018.1.0+2018.08.21.git.3adf6272bd-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-arista.html
  • 612 days old (needed 5 days)
• libopenshot-audio (- to 0.1.7+dfsg1-1)
  • Migration status for libopenshot-audio (- to 0.1.7+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libopenshot-audio introduces new bugs: #925755
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libopenshot-audio.html
  • 613 days old (needed 5 days)
• easyspice (- to 0.6.8-3)
  • Migration status for easyspice (- to 0.6.8-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: easyspice geda-gaf (not considered)
  • Invalidated by dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 614 days old (needed 5 days)
• ruby-browser (- to 2.5.3-1)
  • Migration status for ruby-browser (- to 2.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ruby-browser introduces new bugs: #952044
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-browser.html
  • Required age reduced by 3 days because of autopkgtest
  • 614 days old (needed 2 days)
• libzypp (- to 17.7.0-1)
  • Migration status for libzypp (- to 17.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libzypp introduces new bugs: #949196, #960619
  • Build-Depends(-Arch): libzypp libsolv
  • Depends: libzypp libsolv
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libz/libzypp.html
  • 619 days old (needed 5 days)
• nethack (- to 3.6.1-1)
  • Migration status for nethack (- to 3.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating nethack introduces new bugs: #947005
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nethack.html
  • 619 days old (needed 5 days)
• bdfproxy (- to 0.3.9-3)
  • Migration status for bdfproxy (- to 0.3.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating bdfproxy introduces new bugs: #905782
  • autopkgtest for bdfproxy/0.3.9-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bdfproxy.html
  • 624 days old (needed 5 days)
• hddemux (- to 0.4-7)
  • Migration status for hddemux (- to 0.4-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): hddemux knot-resolver (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hddemux.html
  • 624 days old (needed 5 days)
• freewheeling (- to 0.6.4-1)
  • Migration status for freewheeling (- to 0.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • freewheeling/amd64 has unsatisfiable dependency
  • freewheeling/arm64 has unsatisfiable dependency
  • freewheeling/armel has unsatisfiable dependency
  • freewheeling/armhf has unsatisfiable dependency
  • freewheeling/i386 has unsatisfiable dependency
  • freewheeling/mips64el has unsatisfiable dependency
  • freewheeling/mipsel has unsatisfiable dependency
  • freewheeling/ppc64el has unsatisfiable dependency
  • freewheeling/s390x has unsatisfiable dependency
  • Updating freewheeling introduces new bugs: #946863
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freewheeling.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 625 days old (needed 5 days)
• gconf-editor (- to 3.0.1-6)
  • Migration status for gconf-editor (- to 3.0.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gconf-editor introduces new bugs: #947523
  • Build-Depends(-Arch): gconf-editor gnome-doc-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gconf-editor.html
  • 625 days old (needed 5 days)
• limereg (- to 1.4.1-4)
  • Migration status for limereg (- to 1.4.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating limereg introduces new bugs: #922584
  • autopkgtest for limereg/1.4.1-4: amd64: Regression ♻ , arm64: Regression ♻
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: limereg -> libopencv-core3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: limereg -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/s390x
  • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/l/limereg.html
  • Additional info:
  • 628 days old (needed 5 days)
• teem (- to 1.12.0~20160122-3)
  • Migration status for teem (- to 1.12.0~20160122-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating teem introduces new bugs: #880316
  • missing build on arm64
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/teem.html
  • 629 days old (needed 5 days)
• reprozip (- to 1.0.14-2)
  • Migration status for reprozip (- to 1.0.14-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating reprozip introduces new bugs: #943442
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reprozip.html
  • uninstallable on arch arm64, not running autopkgtest there
  • Required age reduced by 3 days because of autopkgtest
  • 631 days old (needed 2 days)
• crtmpserver (- to 1.0~dfsg-5.5)
  • Migration status for crtmpserver (- to 1.0~dfsg-5.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating crtmpserver introduces new bugs: #954903
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crtmpserver.html
  • 637 days old (needed 5 days)
• diet-ng (- to 1.5.0-1)
  • Migration status for diet-ng (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating diet-ng introduces new bugs: #944626
  • Impossible Depends: diet-ng -> libphobos2-ldc-shared86/1:1.16.0-1+b1/armhf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diet-ng.html
  • 638 days old (needed 5 days)
• perl-doc-html (- to 5.26.0-4)
  • Migration status for perl-doc-html (- to 5.26.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating perl-doc-html introduces new bugs: #907974
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perl-doc-html.html
  • 641 days old (needed 5 days)
• undertaker (- to 1.6.1-4.2)
  • Migration status for undertaker (- to 1.6.1-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • undertaker/amd64 has unsatisfiable dependency
  • undertaker/arm64 has unsatisfiable dependency
  • undertaker/armel has unsatisfiable dependency
  • undertaker/armhf has unsatisfiable dependency
  • undertaker/i386 has unsatisfiable dependency
  • undertaker/mips64el has unsatisfiable dependency
  • undertaker/mipsel has unsatisfiable dependency
  • undertaker/ppc64el has unsatisfiable dependency
  • undertaker/s390x has unsatisfiable dependency
  • Updating undertaker introduces new bugs: #938754
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/undertaker.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 641 days old (needed 5 days)
• hepmc (- to 2.06.09-3)
  • Migration status for hepmc (- to 2.06.09-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hepmc introduces new bugs: #916132
  • Depends: hepmc pythia8
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hepmc.html
  • 643 days old (needed 5 days)
• liblemon (- to 1.3.1+dfsg-2)
  • Migration status for liblemon (- to 1.3.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating liblemon introduces new bugs: #925749
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libl/liblemon.html
  • 644 days old (needed 5 days)
• vmtk (- to 1.3+dfsg-2.3)
  • Migration status for vmtk (- to 1.3+dfsg-2.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vmtk introduces new bugs: #938795, #939594
  • Impossible Build-Depends(-Arch): vmtk -> libvtk6-java/6.3.0+dfsg2-2+b5/amd64
  • Impossible Build-Depends(-Arch): vmtk -> libvtk6-java/6.3.0+dfsg2-2+b5/i386
  • Impossible Depends: vmtk -> libinsighttoolkit4.12/4.12.2-dfsg1-4+b2/amd64
  • Impossible Depends: vmtk -> libinsighttoolkit4.12/4.12.2-dfsg1-4.1/i386
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • uninstallable on arch arm64, not running autopkgtest there
  • 654 days old (needed 5 days)
• geda-gaf (- to 1:1.8.2-11)
  • Migration status for geda-gaf (- to 1:1.8.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating geda-gaf introduces new bugs: #885195, #936593
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geda-gaf.html
  • 656 days old (needed 5 days)
• php-symfony-polyfill (- to 1.9.0-1)
  • Migration status for php-symfony-polyfill (- to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-symfony-polyfill introduces new bugs: #911832
  • autopkgtest for php-symfony-polyfill/1.9.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-symfony-polyfill.html
  • 658 days old (needed 5 days)
• kiki-the-nano-bot (- to 1.0.2+dfsg1-8)
  • Migration status for kiki-the-nano-bot (- to 1.0.2+dfsg1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kiki-the-nano-bot introduces new bugs: #936796
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kiki-the-nano-bot.html
  • 663 days old (needed 5 days)
• hdate-applet (- to 0.15.11-3)
  • Migration status for hdate-applet (- to 0.15.11-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): hdate-applet libhdate (not considered)
  • Depends: hdate-applet libhdate (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hdate-applet.html
  • 668 days old (needed 5 days)
• libhdate (- to 1.6.02-2)
  • Migration status for libhdate (- to 1.6.02-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libhdate introduces new bugs: #936873
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhdate.html
  • 668 days old (needed 5 days)
• libxsmm (- to 1.9-1)
  • Migration status for libxsmm (- to 1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libxsmm introduces new bugs: #906765, #917526
  • Not built on buildd: arch amd64 binaries uploaded by mbanck
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxsmm.html
  • 670 days old (needed 5 days)
• vowpal-wabbit (- to 8.6.1.dfsg1-1)
  • Migration status for vowpal-wabbit (- to 8.6.1.dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vowpal-wabbit introduces new bugs: #836450, #893031
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vowpal-wabbit.html
  • 670 days old (needed 5 days)
• jp (- to 0.1.3-1)
  • Migration status for jp (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jp introduces new bugs: #904742
  • jp/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • jp/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • jp/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • jp/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • jp/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • jp/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • jp/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • jp/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • jp/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jp.html
  • 671 days old (needed 5 days)
• scap-security-guide (- to 0.1.39-2)
  • Migration status for scap-security-guide (- to 0.1.39-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating scap-security-guide introduces new bugs: #938438
  • scap-security-guide unsatisfiable Build-Depends(-Arch) on amd64: python-requests
  • scap-security-guide unsatisfiable Build-Depends(-Arch) on amd64: python-yaml
  • scap-security-guide unsatisfiable Build-Depends(-Arch) on amd64: python-lxml
  • Build-Depends(-Arch): scap-security-guide openscap
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scap-security-guide.html
  • 671 days old (needed 5 days)
• openscap-daemon (- to 0.1.10-3)
  • Migration status for openscap-daemon (- to 0.1.10-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: openscap-daemon openscap (not considered)
  • Invalidated by dependency
  • Depends: openscap-daemon scap-security-guide
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openscap-daemon.html
  • Required age reduced by 3 days because of autopkgtest
  • 672 days old (needed 2 days)
• pjproject (- to 2.7.2~dfsg-4)
  • Migration status for pjproject (- to 2.7.2~dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pjproject introduces new bugs: #925263, #937296
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pjproject.html
  • 675 days old (needed 5 days)
• opencfu (- to 3.9.0-3)
  • Migration status for opencfu (- to 3.9.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating opencfu introduces new bugs: #922589
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-calib3d3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-contrib3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-core3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-features2d3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-flann3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-highgui3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-imgproc3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-ml3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-objdetect3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-photo3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-shape3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-stitching3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-superres3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-video3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-videoio3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-videostab3.2/3.2.0+dfsg-6+b1/s390x
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/amd64
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/arm64
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/armel
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/armhf
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/i386
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/mips64el
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/mipsel
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/ppc64el
  • Impossible Depends: opencfu -> libopencv-viz3.2/3.2.0+dfsg-6+b1/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencfu.html
  • 679 days old (needed 5 days)
• mlton (- to 20180207-1)
  • Migration status for mlton (- to 20180207-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mlton-compiler/amd64 has unsatisfiable dependency
  • mlton-runtime-x86-64-linux-gnu/amd64 has unsatisfiable dependency
  • Updating mlton introduces new bugs: #904475, #917644
  • Not built on buildd: arch amd64 binaries uploaded by terpstra
  • 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:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mlton.html
  • 682 days old (needed 5 days)
• profphd (- to 1.0.42-3)
  • Migration status for profphd (- to 1.0.42-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating profphd introduces new bugs: #942064
  • autopkgtest for profphd/1.0.42-3: amd64: Regression ♻ , arm64: Regression ♻
  • Depends: profphd profnet
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/profphd.html
  • 685 days old (needed 5 days)
• openzwave (- to 1.5+ds-6)
  • Migration status for openzwave (- to 1.5+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openzwave introduces new bugs: #944172
  • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openzwave.html
  • 687 days old (needed 5 days)
• libhtml-microformats-perl (- to 0.105-5)
  • Migration status for libhtml-microformats-perl (- to 0.105-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): libhtml-microformats-perl libhtml-html5-parser-perl (not considered)
  • Depends: libhtml-microformats-perl libhtml-html5-parser-perl (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhtml-microformats-perl.html
  • Required age reduced by 3 days because of autopkgtest
  • 689 days old (needed 2 days)
• etcd-fs (- to 0.0+git20140621.0.395eacb-4)
  • Migration status for etcd-fs (- to 0.0+git20140621.0.395eacb-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating etcd-fs introduces new bugs: #907761
  • etcd-fs/amd64 has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • etcd-fs/arm64 has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • etcd-fs/armel has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • etcd-fs/armhf has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • etcd-fs/i386 has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • etcd-fs/mips64el has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • etcd-fs/mipsel has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • etcd-fs/ppc64el has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • etcd-fs/s390x has unsatisfiable Built-Using on golang-1.10 1.10.3-1
  • Not built on buildd: arch amd64 binaries uploaded by onlyjob@member.fsf.org
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/etcd-fs.html
  • 693 days old (needed 5 days)
• pymvpa2 (- to 2.6.5-1)
  • Migration status for pymvpa2 (- to 2.6.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pymvpa2 introduces new bugs: #906399, #931888, #937485
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-statsmodels [!s390x]
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on amd64: python-mock
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-statsmodels [!s390x]
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on arm64: python-mock
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-statsmodels [!s390x]
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armel: python-mock
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-statsmodels [!s390x]
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on armhf: python-mock
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-statsmodels [!s390x]
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on i386: python-mock
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-statsmodels [!s390x]
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mips64el: python-mock
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-statsmodels [!s390x]
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on mipsel: python-mock
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-statsmodels [!s390x]
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-mock
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-scipy
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-nibabel
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-h5py
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-lxml
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-numpydoc
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-matplotlib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-joblib
  • pymvpa2 unsatisfiable Build-Depends(-Arch) on s390x: python-mock
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by yoh
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymvpa2.html
  • 701 days old (needed 5 days)
• acbuild (- to 0.4.0+dfsg-3)
  • Migration status for acbuild (- to 0.4.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • acbuild/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • acbuild/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • acbuild/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • acbuild/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • acbuild/armel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • acbuild/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • acbuild/armhf has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • acbuild/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • acbuild/i386 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • acbuild/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • acbuild/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • acbuild/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • Build-Depends(-Arch): acbuild rkt
  • Built-Using: acbuild rkt
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acbuild.html
  • 705 days old (needed 5 days)
• golang-gopkg-gcfg.v1 (- to 1.2.3-1)
  • Migration status for golang-gopkg-gcfg.v1 (- to 1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-gopkg-gcfg.v1 introduces new bugs: #952227
  • autopkgtest for golang-gopkg-gcfg.v1/1.2.3-1: amd64: Regression ♻ , arm64: Regression ♻
  • 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gopkg-gcfg.v1.html
  • 705 days old (needed 5 days)
• linkchecker (- to 9.4.0-2)
  • Migration status for linkchecker (- to 9.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • linkchecker/amd64 has unsatisfiable dependency
  • linkchecker/arm64 has unsatisfiable dependency
  • linkchecker/armel has unsatisfiable dependency
  • linkchecker/armhf has unsatisfiable dependency
  • linkchecker/i386 has unsatisfiable dependency
  • linkchecker/mips64el has unsatisfiable dependency
  • linkchecker/mipsel has unsatisfiable dependency
  • linkchecker/ppc64el has unsatisfiable dependency
  • linkchecker/s390x has unsatisfiable dependency
  • Updating linkchecker introduces new bugs: #936950, #953375
  • linkchecker unsatisfiable Build-Depends(-Arch) on amd64: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on amd64: python-urllib3
  • linkchecker unsatisfiable Build-Depends(-Arch) on arm64: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on arm64: python-urllib3
  • linkchecker unsatisfiable Build-Depends(-Arch) on armel: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on armel: python-urllib3
  • linkchecker unsatisfiable Build-Depends(-Arch) on armhf: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on armhf: python-urllib3
  • linkchecker unsatisfiable Build-Depends(-Arch) on i386: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on i386: python-urllib3
  • linkchecker unsatisfiable Build-Depends(-Arch) on mips64el: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on mips64el: python-urllib3
  • linkchecker unsatisfiable Build-Depends(-Arch) on mipsel: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on mipsel: python-urllib3
  • linkchecker unsatisfiable Build-Depends(-Arch) on ppc64el: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on ppc64el: python-urllib3
  • linkchecker unsatisfiable Build-Depends(-Arch) on s390x: python-requests (>= 2.2.1)
  • linkchecker unsatisfiable Build-Depends(-Arch) on s390x: python-urllib3
  • Not built on buildd: arch all binaries uploaded by anarcat@koumbit.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linkchecker.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 706 days old (needed 5 days)
• dj-static (- to 0.0.6-6)
  • Migration status for dj-static (- to 0.0.6-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: dj-static python-static3 (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dj-static.html
  • Required age reduced by 3 days because of autopkgtest
  • 712 days old (needed 2 days)
• relion (- to 1.4+dfsg-4)
  • Migration status for relion (- to 1.4+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating relion introduces new bugs: #952003
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/relion.html
  • 714 days old (needed 5 days)
• parallelpython (- to 1.6.6-1)
  • Migration status for parallelpython (- to 1.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating parallelpython introduces new bugs: #937237
  • Not built on buildd: arch all binaries uploaded by morph, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parallelpython.html
  • 718 days old (needed 5 days)
• erlang-cowboy (- to 2.0.0~pre.1+dfsg1-4)
  • Migration status for erlang-cowboy (- to 2.0.0~pre.1+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by iwamatsu
  • Not built on buildd: arch all binaries uploaded by iwamatsu, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): erlang-cowboy erlang-ranch
  • Depends: erlang-cowboy erlang-ranch
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-cowboy.html
  • 721 days old (needed 5 days)
• python-omniorb (- to 4.2.2-0.2)
  • Migration status for python-omniorb (- to 4.2.2-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-omniorb introduces new bugs: #899676, #937970
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-omniorb.html
  • 723 days old (needed 5 days)
• wotsap (- to 0.7-6)
  • Migration status for wotsap (- to 0.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating wotsap introduces new bugs: #945746
  • Depends: wotsap pillow-python2
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wotsap.html
  • 730 days old (needed 5 days)
• erlang-bitcask (- to 2.0.8+dfsg-2)
  • Migration status for erlang-bitcask (- to 2.0.8+dfsg-2): 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
  • Build-Depends(-Arch): erlang-bitcask erlang-cuttlefish
  • Depends: erlang-bitcask erlang-cuttlefish
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-bitcask.html
  • 731 days old (needed 5 days)
• php-cache-lite (- to 1.8.2-1)
  • Migration status for php-cache-lite (- to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-cache-lite introduces new bugs: #940275, #941264
  • autopkgtest for php-cache-lite/1.8.2-1: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-cache-lite.html
  • 736 days old (needed 5 days)
• dipy (- to 0.14.0-1)
  • Migration status for dipy (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-dipy/amd64 has unsatisfiable dependency
  • python-dipy/i386 has unsatisfiable dependency
  • Updating dipy introduces new bugs: #851048, #896620, #936400, #942973
  • dipy unsatisfiable Build-Depends(-Arch) on amd64: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on amd64: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on amd64: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on amd64: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on amd64: python-nibabel (>= 2.1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on arm64: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on arm64: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on arm64: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on arm64: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on arm64: python-nibabel (>= 2.1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on armel: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on armel: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on armel: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on armel: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on armel: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on armel: python-nibabel (>= 2.1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on armhf: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on armhf: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on armhf: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on armhf: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on armhf: python-nibabel (>= 2.1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on i386: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on i386: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on i386: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on i386: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on i386: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on i386: python-nibabel (>= 2.1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on mips64el: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on mips64el: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on mips64el: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on mips64el: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on mips64el: python-nibabel (>= 2.1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on mipsel: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on mipsel: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on mipsel: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on mipsel: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on mipsel: python-nibabel (>= 2.1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on ppc64el: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on ppc64el: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on ppc64el: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on ppc64el: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on ppc64el: python-nibabel (>= 2.1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on s390x: python-h5py
  • dipy unsatisfiable Build-Depends(-Arch) on s390x: python-scipy
  • dipy unsatisfiable Build-Depends(-Arch) on s390x: python-matplotlib
  • dipy unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx (>= 1.0)
  • dipy unsatisfiable Build-Depends(-Arch) on s390x: python-numpydoc
  • dipy unsatisfiable Build-Depends(-Arch) on s390x: python-nibabel (>= 2.1.0)
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by yoh
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dipy.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 743 days old (needed 5 days)
• tpm2-pk11 (- to 0~git20180426-1)
  • Migration status for tpm2-pk11 (- to 0~git20180426-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • tpm2-pk11/amd64 has unsatisfiable dependency
  • tpm2-pk11/arm64 has unsatisfiable dependency
  • tpm2-pk11/armel has unsatisfiable dependency
  • tpm2-pk11/armhf has unsatisfiable dependency
  • tpm2-pk11/i386 has unsatisfiable dependency
  • tpm2-pk11/mips64el has unsatisfiable dependency
  • tpm2-pk11/mipsel has unsatisfiable dependency
  • tpm2-pk11/ppc64el has unsatisfiable dependency
  • tpm2-pk11/s390x has unsatisfiable dependency
  • Updating tpm2-pk11 introduces new bugs: #913368
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on amd64: libsapi-dev
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on arm64: libsapi-dev
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on armel: libsapi-dev
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on armhf: libsapi-dev
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on i386: libsapi-dev
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on mips64el: libsapi-dev
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on mipsel: libsapi-dev
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on ppc64el: libsapi-dev
  • tpm2-pk11 unsatisfiable Build-Depends(-Arch) on s390x: libsapi-dev
  • Not built on buildd: arch amd64 binaries uploaded by szlin@cs.nctu.edu.tw
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-pk11.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 743 days old (needed 5 days)
• ggcov (- to 0.9-21)
  • Migration status for ggcov (- to 0.9-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ggcov introduces new bugs: #897758
  • Not built on buildd: arch amd64 binaries uploaded by mckinstry
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ggcov.html
  • 744 days old (needed 5 days)
• childsplay (- to 3.3-2)
  • Migration status for childsplay (- to 3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating childsplay introduces new bugs: #912485, #936298
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/childsplay.html
  • 749 days old (needed 5 days)
• rows (- to 0.3.1-3)
  • Migration status for rows (- to 0.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-rows/amd64 has unsatisfiable dependency
  • rows/amd64 has unsatisfiable dependency
  • python-rows/i386 has unsatisfiable dependency
  • rows/i386 has unsatisfiable dependency
  • Updating rows introduces new bugs: #938408
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-click
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-ipdb
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-lxml
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-mock
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-nose-yanc
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-openpyxl
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-pip
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-requests
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-unicodecsv
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-xlrd
  • rows unsatisfiable Build-Depends(-Arch) on amd64: python-xlwt
  • Not built on buildd: arch all binaries uploaded by kretcheu@jabber.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rows.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 755 days old (needed 5 days)
• openscap (- to 1.2.16-2)
  • Migration status for openscap (- to 1.2.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating openscap introduces new bugs: #930673, #937211
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/amd64
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/arm64
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/armel
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/armhf
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/i386
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/mips64el
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/mipsel
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/ppc64el
  • Impossible Depends: openscap -> libapt-pkg5.0/1.8.2.1/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openscap.html
  • 756 days old (needed 5 days)
• astk (- to 1.13.1-2.1)
  • Migration status for astk (- to 1.13.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating astk introduces new bugs: #936159
  • Not built on buildd: arch all binaries uploaded by sgolovan, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astk.html
  • 761 days old (needed 5 days)
• xpp (- to 1.5-cvs20081009-4)
  • Migration status for xpp (- to 1.5-cvs20081009-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xpp introduces new bugs: #945545
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xpp.html
  • 761 days old (needed 5 days)
• dovecot-antispam (- to 2.0+20171229-1)
  • Migration status for dovecot-antispam (- to 2.0+20171229-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): dovecot-antispam dovecot (not considered)
  • Depends: dovecot-antispam dovecot (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: dovecot-antispam dovecot_pu
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dovecot-antispam.html
  • 766 days old (needed 5 days)
• golang-github-clusterhq-flocker-go (- to 0.0~git20160209.0.1c0a791-2)
  • Migration status for golang-github-clusterhq-flocker-go (- to 0.0~git20160209.0.1c0a791-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-github-clusterhq-flocker-go introduces new bugs: #849664
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-clusterhq-flocker-go.html
  • Required age reduced by 3 days because of autopkgtest
  • 766 days old (needed 2 days)
• wicd (- to 1.7.4+tb2-6)
  • Migration status for wicd (- to 1.7.4+tb2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • wicd-curses/amd64 has unsatisfiable dependency
  • wicd-daemon/amd64 has unsatisfiable dependency
  • wicd-gtk/amd64 has unsatisfiable dependency
  • wicd-curses/i386 has unsatisfiable dependency
  • wicd-daemon/i386 has unsatisfiable dependency
  • wicd-gtk/i386 has unsatisfiable dependency
  • Updating wicd introduces new bugs: #885140, #938823, #956159
  • wicd unsatisfiable Build-Depends-Indep on amd64: python-babel
  • Not built on buildd: arch all binaries uploaded by abe, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wicd.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 766 days old (needed 5 days)
• libghemical (- to 3.0.0-4.2)
  • Migration status for libghemical (- to 3.0.0-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by mckinstry, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libghemical mpqc
  • Depends: libghemical mpqc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libghemical.html
  • 770 days old (needed 5 days)
• golang-github-coreos-go-tspi (- to 0.1.1-2)
  • Migration status for golang-github-coreos-go-tspi (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-github-coreos-go-tspi introduces new bugs: #849665
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-coreos-go-tspi.html
  • 773 days old (needed 5 days)
• vdr-plugin-softhddevice (- to 0.6.0+git20160108-3)
  • Migration status for vdr-plugin-softhddevice (- to 0.6.0+git20160108-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • vdr-plugin-softhddevice/amd64 has unsatisfiable dependency
  • vdr-plugin-softhddevice/arm64 has unsatisfiable dependency
  • vdr-plugin-softhddevice/armel has unsatisfiable dependency
  • vdr-plugin-softhddevice/armhf has unsatisfiable dependency
  • vdr-plugin-softhddevice/i386 has unsatisfiable dependency
  • vdr-plugin-softhddevice/mips64el has unsatisfiable dependency
  • vdr-plugin-softhddevice/mipsel has unsatisfiable dependency
  • vdr-plugin-softhddevice/ppc64el has unsatisfiable dependency
  • vdr-plugin-softhddevice/s390x has unsatisfiable dependency
  • Updating vdr-plugin-softhddevice introduces new bugs: #888331
  • Not built on buildd: arch amd64 binaries uploaded by etobi
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-softhddevice.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 773 days old (needed 5 days)
• mldemos (- to 0.5.1+git.1.ee5d11f-4)
  • Migration status for mldemos (- to 0.5.1+git.1.ee5d11f-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mldemos introduces new bugs: #915711, #922585
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mldemos.html
  • 774 days old (needed 5 days)
• enki-aseba (- to 1:1.6.0-6)
  • Migration status for enki-aseba (- to 1:1.6.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating enki-aseba introduces new bugs: #936483
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enki-aseba.html
  • 775 days old (needed 5 days)
• aseba-plugin-blockly (- to 20180211+git-2)
  • Migration status for aseba-plugin-blockly (- to 20180211+git-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating aseba-plugin-blockly introduces new bugs: #936153
  • aseba-plugin-blockly unsatisfiable Build-Depends(-Arch) on amd64: python-bs4
  • aseba-plugin-blockly unsatisfiable Build-Depends(-Arch) on amd64: python-lxml
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 781 days old (needed 5 days)
• condor (- to 8.6.8~dfsg.1-2)
  • Migration status for condor (- to 8.6.8~dfsg.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating condor introduces new bugs: #925657
  • Not built on buildd: arch all binaries uploaded by mih, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/condor.html
  • 783 days old (needed 5 days)
• tendermint-go-logger (- to 0~20161018~0gitcefb3a4-3)
  • Migration status for tendermint-go-logger (- to 0~20161018~0gitcefb3a4-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): tendermint-go-logger tendermint-go-common (not considered)
  • Depends: tendermint-go-logger tendermint-go-common (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-logger.html
  • 786 days old (needed 5 days)
• libkiokudb-backend-dbi-perl (- to 1.23-2)
  • Migration status for libkiokudb-backend-dbi-perl (- to 1.23-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libkiokudb-backend-dbi-perl introduces new bugs: #952229
  • autopkgtest for libkiokudb-backend-dbi-perl/1.23-2: amd64: Pass, arm64: Regression ♻
  • Build-Depends-Indep: libkiokudb-backend-dbi-perl libkiokudb-perl
  • Depends: libkiokudb-backend-dbi-perl libkiokudb-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkiokudb-backend-dbi-perl.html
  • 790 days old (needed 5 days)
• phpunit-dbunit (- to 4.0.0-2)
  • Migration status for phpunit-dbunit (- to 4.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • phpunit-dbunit/amd64 has unsatisfiable dependency
  • phpunit-dbunit/i386 has unsatisfiable dependency
  • Updating phpunit-dbunit introduces new bugs: #935639
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpunit-dbunit.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 790 days old (needed 5 days)
• tunnelx (- to 20170928-2)
  • Migration status for tunnelx (- to 20170928-2): 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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tunnelx.html
  • 791 days old (needed 5 days)
• debbugs (- to 2.6.0)
  • Migration status for debbugs (- to 2.6.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating debbugs introduces new bugs: #903413
  • autopkgtest for debbugs/2.6.0: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by don, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debbugs.html
  • 793 days old (needed 5 days)
• glare (- to 0.5.0-4)
  • Migration status for glare (- to 0.5.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating glare introduces new bugs: #909045
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glare.html
  • 793 days old (needed 5 days)
• skales (- to 0.20170929-1)
  • Migration status for skales (- to 0.20170929-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating skales introduces new bugs: #943273
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skales.html
  • 799 days old (needed 5 days)
• collada2gltf (- to 20140924-5)
  • Migration status for collada2gltf (- to 20140924-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating collada2gltf introduces new bugs: #893203
  • Not built on buildd: arch amd64 binaries uploaded by rene
  • 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:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/collada2gltf.html
  • 800 days old (needed 5 days)
• bindgraph (- to 0.2a-6)
  • Migration status for bindgraph (- to 0.2a-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating bindgraph introduces new bugs: #806946, #931756
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bindgraph.html
  • 804 days old (needed 5 days)
• sicherboot (- to 0.1.5)
  • Migration status for sicherboot (- to 0.1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sicherboot introduces new bugs: #901610
  • Not built on buildd: arch all binaries uploaded by jak, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sicherboot.html
  • 804 days old (needed 5 days)
• tendermint-go-event-meter (- to 0.0~git20160420.0.c9240a5-2)
  • Migration status for tendermint-go-event-meter (- to 0.0~git20160420.0.c9240a5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): tendermint-go-event-meter tendermint-go-rpc (not considered)
  • Depends: tendermint-go-event-meter tendermint-go-rpc (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: tendermint-go-event-meter tendermint-go-common
  • Depends: tendermint-go-event-meter tendermint-go-events
  • Depends: tendermint-go-event-meter tendermint-go-logger
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-event-meter.html
  • 805 days old (needed 5 days)
• nvidia-settings-legacy-304xx (- to 304.137-2)
  • Migration status for nvidia-settings-legacy-304xx (- to 304.137-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: nvidia-settings-legacy-304xx nvidia-graphics-drivers-legacy-304xx (not considered)
  • Invalidated by dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 809 days old (needed 5 days)
• verdigris (- to 1.0-1)
  • Migration status for verdigris (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating verdigris introduces new bugs: #952157
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verdigris.html
  • 811 days old (needed 5 days)
• go-wire (- to 1.0~rc+git20161223.40.2f3b7aa-2)
  • Migration status for go-wire (- to 1.0~rc+git20161223.40.2f3b7aa-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • wire/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • wire/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • wire/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • wire/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • wire/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • wire/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • wire/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • wire/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • wire/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • Build-Depends(-Arch): go-wire tendermint-go-logger
  • Built-Using: go-wire tendermint-go-common
  • Built-Using: go-wire tendermint-go-logger
  • Built-Using: go-wire tendermint-log15
  • Depends: go-wire tendermint-go-common
  • Depends: go-wire tendermint-go-logger
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-wire.html
  • 814 days old (needed 5 days)
• golang-petname (- to 2.5~git20160928-3)
  • Migration status for golang-petname (- to 2.5~git20160928-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • golang-petname/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • golang-petname/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • golang-petname/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • golang-petname/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • golang-petname/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • golang-petname/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • golang-petname/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • golang-petname/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • golang-petname/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-1
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-petname.html
  • 814 days old (needed 5 days)
• funny-manpages (- to 2.3-1)
  • Migration status for funny-manpages (- to 2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating funny-manpages introduces new bugs: #737395
  • Not built on buildd: arch all binaries uploaded by mattia@mapreri.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/funny-manpages.html
  • 816 days old (needed 5 days)
• android-platform-tools-base (- to 2.2.2-3)
  • Migration status for android-platform-tools-base (- to 2.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating android-platform-tools-base introduces new bugs: #894284
  • Not built on buildd: arch all binaries uploaded by eighthave, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): android-platform-tools-base android-platform-tools-analytics-library
  • Depends: android-platform-tools-base android-platform-frameworks-data-binding
  • Depends: android-platform-tools-base android-platform-tools-analytics-library
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-tools-base.html
  • 819 days old (needed 5 days)
• ardour (- to 1:5.12.0-3)
  • Migration status for ardour (- to 1:5.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ardour/amd64 has unsatisfiable dependency
  • ardour/arm64 has unsatisfiable dependency
  • ardour/armel has unsatisfiable dependency
  • ardour/armhf has unsatisfiable dependency
  • ardour/i386 has unsatisfiable dependency
  • ardour/mips64el has unsatisfiable dependency
  • ardour/mipsel has unsatisfiable dependency
  • ardour/ppc64el has unsatisfiable dependency
  • ardour/s390x has unsatisfiable dependency
  • Updating ardour introduces new bugs: #946989
  • ardour unsatisfiable Build-Depends(-Arch) on amd64: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on amd64: python-rdflib
  • ardour unsatisfiable Build-Depends(-Arch) on arm64: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on arm64: python-rdflib
  • ardour unsatisfiable Build-Depends(-Arch) on armel: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on armel: python-rdflib
  • ardour unsatisfiable Build-Depends(-Arch) on armhf: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on armhf: python-rdflib
  • ardour unsatisfiable Build-Depends(-Arch) on i386: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on i386: python-rdflib
  • ardour unsatisfiable Build-Depends(-Arch) on mips64el: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on mips64el: python-rdflib
  • ardour unsatisfiable Build-Depends(-Arch) on mipsel: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on mipsel: python-rdflib
  • ardour unsatisfiable Build-Depends(-Arch) on ppc64el: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on ppc64el: python-rdflib
  • ardour unsatisfiable Build-Depends(-Arch) on s390x: python-isodate
  • ardour unsatisfiable Build-Depends(-Arch) on s390x: python-rdflib
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ardour.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 819 days old (needed 5 days)
• conky (- to 1.10.8-1)
  • Migration status for conky (- to 1.10.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): conky tolua++ (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/conky.html
  • 820 days old (needed 5 days)
• pidcat (- to 2.1.0-2)
  • Migration status for pidcat (- to 2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pidcat introduces new bugs: #943164
  • Not built on buildd: arch all binaries uploaded by eighthave, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pidcat.html
  • 822 days old (needed 5 days)
• jquery-at.js (- to 1.5.4+dfsg.1-2)
  • Migration status for jquery-at.js (- to 1.5.4+dfsg.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jquery-at.js introduces new bugs: #954680
  • Not built on buildd: arch all binaries uploaded by ben@benfinney.id.au, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-at.js.html
  • 823 days old (needed 5 days)
• pyfeed (- to 0.7.4-2)
  • Migration status for pyfeed (- to 0.7.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pyfeed introduces new bugs: #937437
  • Not built on buildd: arch all binaries uploaded by robotux@celest.fr, a new source-only upload is needed to allow migration
  • Depends: pyfeed xmlelements
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfeed.html
  • 823 days old (needed 5 days)
• xmlelements (- to 0.7.4-2)
  • Migration status for xmlelements (- to 0.7.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xmlelements introduces new bugs: #938850
  • Not built on buildd: arch all binaries uploaded by robotux@celest.fr, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmlelements.html
  • 823 days old (needed 5 days)
• qpid-python (- to 1.37.0+dfsg-1)
  • Migration status for qpid-python (- to 1.37.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating qpid-python introduces new bugs: #938314
  • Not built on buildd: arch all binaries uploaded by gcs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-python.html
  • 830 days old (needed 5 days)
• octave-tisean (- to 0.2.3-3)
  • Migration status for octave-tisean (- to 0.2.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • octave-tisean/amd64 has unsatisfiable dependency
  • Updating octave-tisean introduces new bugs: #902158
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-tisean.html
  • uninstallable on arch amd64, not running autopkgtest there
  • 837 days old (needed 5 days)
• xfonts-efont-unicode (- to 0.4.2-11)
  • Migration status for xfonts-efont-unicode (- to 0.4.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xfonts-efont-unicode introduces new bugs: #944496
  • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfonts-efont-unicode.html
  • 838 days old (needed 5 days)
• golang-go-dbus (- to 1~bzr20150122-3)
  • Migration status for golang-go-dbus (- to 1~bzr20150122-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-go-dbus introduces new bugs: #952299
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-go-dbus.html
  • 839 days old (needed 5 days)
• librsl (- to 1.43-1.2)
  • Migration status for librsl (- to 1.43-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating librsl introduces new bugs: #893023
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librsl.html
  • 843 days old (needed 5 days)
• pd-py (- to 0.2.2+git20170625.1.88fc77a-2)
  • Migration status for pd-py (- to 0.2.2+git20170625.1.88fc77a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pd-py introduces new bugs: #937266
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pd-py.html
  • 843 days old (needed 5 days)
• gobby (- to 0.6.0~20170204~e5c2d1-3)
  • Migration status for gobby (- to 0.6.0~20170204~e5c2d1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): gobby libinfinity (not considered)
  • Depends: gobby libinfinity (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gobby.html
  • 844 days old (needed 5 days)
• hyantesite (- to 1.3.0-2)
  • Migration status for hyantesite (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hyantesite introduces new bugs: #888733
  • missing build on arm64
  • 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:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyantesite.html
  • 853 days old (needed 5 days)
• network-manager-iodine (- to 1.2.0-3)
  • Migration status for network-manager-iodine (- to 1.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating network-manager-iodine introduces new bugs: #908017
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/network-manager-iodine.html
  • 856 days old (needed 5 days)
• dms (- to 1.0.8.1-1)
  • Migration status for dms (- to 1.0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dms introduces new bugs: #883795, #887635, #904297
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/dms.html
  • Not built on buildd: arch amd64 binaries uploaded by grantma
  • Not built on buildd: arch all binaries uploaded by grantma, a new source-only upload is needed to allow migration
  • missing build on arm64
  • missing build on armel
  • missing build on armhf
  • missing build on i386
  • missing build on mips64el
  • missing build on mipsel
  • missing build on ppc64el
  • missing build on s390x
  • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
  • 861 days old (needed 5 days)
• mp3splt (- to 2.6.2+20170630-3)
  • Migration status for mp3splt (- to 2.6.2+20170630-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mp3splt introduces new bugs: #947534
  • Build-Depends(-Arch): mp3splt gnome-doc-utils
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mp3splt.html
  • 866 days old (needed 5 days)
• gnome-shell-extension-tilix-shortcut (- to 1.0.1-2)
  • Migration status for gnome-shell-extension-tilix-shortcut (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnome-shell-extension-tilix-shortcut introduces new bugs: #959741
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-tilix-shortcut.html
  • 867 days old (needed 5 days)
• ignore-me (- to 0.1.2-1)
  • Migration status for ignore-me (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ignore-me introduces new bugs: #912037, #948875
  • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ignore-me.html
  • 869 days old (needed 5 days)
• boinc-app-eah-brp (- to 0.20170426+dfsg-10)
  • Migration status for boinc-app-eah-brp (- to 0.20170426+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • boinc-app-eah-brp/amd64 has unsatisfiable dependency
  • boinc-app-eah-brp/arm64 has unsatisfiable dependency
  • boinc-app-eah-brp/armel has unsatisfiable dependency
  • boinc-app-eah-brp/armhf has unsatisfiable dependency
  • boinc-app-eah-brp/i386 has unsatisfiable dependency
  • boinc-app-eah-brp/mips64el has unsatisfiable dependency
  • boinc-app-eah-brp/mipsel has unsatisfiable dependency
  • boinc-app-eah-brp/ppc64el has unsatisfiable dependency
  • boinc-app-eah-brp/s390x has unsatisfiable dependency
  • Updating boinc-app-eah-brp introduces new bugs: #887880, #949603
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on amd64: g++-5 | g++ (<< 6)
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on arm64: g++-5 | g++ (<< 6)
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on armel: g++-5 | g++ (<< 6)
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on armhf: g++-5 | g++ (<< 6)
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on i386: g++-5 | g++ (<< 6)
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on mips64el: g++-5 | g++ (<< 6)
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on mipsel: g++-5 | g++ (<< 6)
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on ppc64el: g++-5 | g++ (<< 6)
  • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on s390x: g++-5 | g++ (<< 6)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boinc-app-eah-brp.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 870 days old (needed 5 days)
• debirf (- to 0.38)
  • Migration status for debirf (- to 0.38): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating debirf introduces new bugs: #901779
  • autopkgtest for debirf/0.38: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debirf.html
  • 870 days old (needed 5 days)
• bkchem (- to 0.13.0-6)
  • Migration status for bkchem (- to 0.13.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating bkchem introduces new bugs: #956336
  • Build-Depends-Indep: bkchem python-pmw
  • Depends: bkchem pillow-python2
  • Depends: bkchem python-pmw
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bkchem.html
  • 871 days old (needed 5 days)
• ibsim (- to 0.7-2)
  • Migration status for ibsim (- to 0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ibsim introduces new bugs: #952061
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibsim.html
  • 875 days old (needed 5 days)
• postnews (- to 0.7-1)
  • Migration status for postnews (- to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating postnews introduces new bugs: #937312
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postnews.html
  • 880 days old (needed 5 days)
• restbed (- to 4.0~dfsg1-5)
  • Migration status for restbed (- to 4.0~dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating restbed introduces new bugs: #951877
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/restbed.html
  • 881 days old (needed 5 days)
• mkchromecast (- to 0.3.8.1-1)
  • Migration status for mkchromecast (- to 0.3.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mkchromecast introduces new bugs: #909822
  • Not built on buildd: arch all binaries uploaded by muammar, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkchromecast.html
  • 885 days old (needed 5 days)
• oneliner-el (- to 0.3.6-8)
  • Migration status for oneliner-el (- to 0.3.6-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating oneliner-el introduces new bugs: #952253
  • Not built on buildd: arch all binaries uploaded by ohura, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oneliner-el.html
  • 890 days old (needed 5 days)
• snowballz (- to 0.9.5.1-5)
  • Migration status for snowballz (- to 0.9.5.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • snowballz/amd64 has unsatisfiable dependency
  • snowballz/i386 has unsatisfiable dependency
  • Updating snowballz introduces new bugs: #938509
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snowballz.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 890 days old (needed 5 days)
• falcon (- to 1.8.8-1)
  • Migration status for falcon (- to 1.8.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • falcon/amd64 has unsatisfiable dependency
  • falcon/arm64 has unsatisfiable dependency
  • falcon/mips64el has unsatisfiable dependency
  • falcon/ppc64el has unsatisfiable dependency
  • falcon/s390x has unsatisfiable dependency
  • Updating falcon introduces new bugs: #902132, #936503
  • falcon unsatisfiable Build-Depends(-Arch) on amd64: python-networkx (>= 1.7)
  • falcon unsatisfiable Build-Depends(-Arch) on amd64: python-pytest
  • falcon unsatisfiable Build-Depends(-Arch) on arm64: python-networkx (>= 1.7)
  • falcon unsatisfiable Build-Depends(-Arch) on arm64: python-pytest
  • falcon unsatisfiable Build-Depends(-Arch) on mips64el: python-networkx (>= 1.7)
  • falcon unsatisfiable Build-Depends(-Arch) on mips64el: python-pytest
  • falcon unsatisfiable Build-Depends(-Arch) on ppc64el: python-networkx (>= 1.7)
  • falcon unsatisfiable Build-Depends(-Arch) on ppc64el: python-pytest
  • falcon unsatisfiable Build-Depends(-Arch) on s390x: python-networkx (>= 1.7)
  • falcon unsatisfiable Build-Depends(-Arch) on s390x: python-pytest
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/falcon.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 894 days old (needed 5 days)
• ktp-call-ui (- to 17.08.3-1)
  • Migration status for ktp-call-ui (- to 17.08.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ktp-call-ui introduces new bugs: #948907
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-call-ui.html
  • 901 days old (needed 5 days)
• libmagpie-perl (- to 1.163200-1)
  • Migration status for libmagpie-perl (- to 1.163200-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libmagpie-perl libkiokudb-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmagpie-perl.html
  • 904 days old (needed 5 days)
• terraintool (- to 1.13-2)
  • Migration status for terraintool (- to 1.13-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating terraintool introduces new bugs: #952369
  • Not built on buildd: arch all binaries uploaded by wookey, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/terraintool.html
  • 906 days old (needed 5 days)
• cvs2svn (- to 2.5.0-1)
  • Migration status for cvs2svn (- to 2.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cvs2svn introduces new bugs: #942980
  • Not built on buildd: arch all binaries uploaded by gcs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvs2svn.html
  • 909 days old (needed 5 days)
• gemrb (- to 0.8.5-1)
  • Migration status for gemrb (- to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gemrb introduces new bugs: #936595
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 911 days old (needed 5 days)
• jajuk (- to 1:1.10.9+dfsg2-4)
  • Migration status for jajuk (- to 1:1.10.9+dfsg2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jajuk introduces new bugs: #923330
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jajuk.html
  • 911 days old (needed 5 days)
• flannel (- to 0.9.1~ds1-1)
  • Migration status for flannel (- to 0.9.1~ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating flannel introduces new bugs: #880914
  • flannel/amd64 has unsatisfiable Built-Using on golang-1.9 1.9.2-3
  • flannel/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20170629.c81e7f2+dfsg-1
  • flannel/arm64 has unsatisfiable Built-Using on golang-1.9 1.9.2-3
  • flannel/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20170629.c81e7f2+dfsg-1
  • flannel/armel has unsatisfiable Built-Using on golang-1.9 1.9.2-3
  • flannel/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20170629.c81e7f2+dfsg-1
  • flannel/armhf has unsatisfiable Built-Using on golang-1.9 1.9.2-3
  • flannel/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20170629.c81e7f2+dfsg-1
  • flannel/i386 has unsatisfiable Built-Using on golang-1.9 1.9.2-3
  • flannel/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20170629.c81e7f2+dfsg-1
  • flannel/mips64el has unsatisfiable Built-Using on golang-1.9 1.9.2-4
  • flannel/mips64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20170629.c81e7f2+dfsg-1
  • flannel/mipsel has unsatisfiable Built-Using on golang-1.9 1.9.2-4
  • flannel/mipsel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20170629.c81e7f2+dfsg-1
  • flannel/ppc64el has unsatisfiable Built-Using on golang-1.9 1.9.2-3
  • flannel/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20170629.c81e7f2+dfsg-1
  • Not built on buildd: arch amd64 binaries uploaded by tpot@samba.org
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flannel.html
  • 919 days old (needed 5 days)
• php-enum (- to 2.3.1-1)
  • Migration status for php-enum (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-enum introduces new bugs: #882928
  • autopkgtest for php-enum/2.3.1-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-enum.html
  • 926 days old (needed 5 days)
• asciio (- to 1.51.3-1)
  • Migration status for asciio (- to 1.51.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating asciio introduces new bugs: #912870
  • Not built on buildd: arch all binaries uploaded by dapal, a new source-only upload is needed to allow migration
  • Build-Depends-Indep: asciio libdata-treedumper-renderer-gtk-perl
  • Depends: asciio libdata-treedumper-renderer-gtk-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asciio.html
  • 932 days old (needed 5 days)
• mldonkey (- to 3.1.6-1)
  • Migration status for mldonkey (- to 3.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mldonkey-server/armel has unsatisfiable dependency
  • mldonkey-server/mips64el has unsatisfiable dependency
  • mldonkey-server/mipsel has unsatisfiable dependency
  • Updating mldonkey introduces new bugs: #939334
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mldonkey.html
  • 932 days old (needed 5 days)
• marionnet (- to 0.90.6+bzr508-1)
  • Migration status for marionnet (- to 0.90.6+bzr508-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating marionnet introduces new bugs: #952310
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/marionnet.html
  • 940 days old (needed 5 days)
• octicons (- to 4.4.0-2)
  • Migration status for octicons (- to 4.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating octicons introduces new bugs: #883107
  • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octicons.html
  • 945 days old (needed 5 days)
• libinfinity (- to 0.7.1-1)
  • Migration status for libinfinity (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libinfinity introduces new bugs: #935614
  • Not built on buildd: arch amd64 binaries uploaded by pkern
  • Not built on buildd: arch all binaries uploaded by pkern, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libinfinity.html
  • 955 days old (needed 5 days)
• libextutils-parsexs-perl (- to 3.350000-1)
  • Migration status for libextutils-parsexs-perl (- to 3.350000-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libextutils-parsexs-perl introduces new bugs: #912682
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libe/libextutils-parsexs-perl.html
  • autopkgtest for libextutils-parsexs-perl/3.350000-1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by fsfs, a new source-only upload is needed to allow migration
  • Additional info:
  • 962 days old (needed 5 days)
• qpid-qmf (- to 0.32-1)
  • Migration status for qpid-qmf (- to 0.32-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating qpid-qmf introduces new bugs: #938315
  • Not built on buildd: arch all binaries uploaded by gcs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-qmf.html
  • 971 days old (needed 5 days)
• otags (- to 4.05.1-1)
  • Migration status for otags (- to 4.05.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • otags/armel has unsatisfiable dependency
  • otags/mips64el has unsatisfiable dependency
  • otags/mipsel has unsatisfiable dependency
  • Updating otags introduces new bugs: #939817
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/otags.html
  • 976 days old (needed 5 days)
• xxdiff (- to 1:4.0.1+hg487+dfsg-1)
  • Migration status for xxdiff (- to 1:4.0.1+hg487+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by fsfs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xxdiff.html
  • 982 days old (needed 5 days)
• urweb (- to 20170720+dfsg-2)
  • Migration status for urweb (- to 20170720+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • urweb unsatisfiable Build-Depends(-Arch) on amd64: mlton
  • Build-Depends(-Arch): urweb mlton
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urweb.html
  • 983 days old (needed 5 days)
• i8c (- to 0.0.6-1)
  • Migration status for i8c (- to 0.0.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): i8c libi8x (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i8c.html
  • 990 days old (needed 5 days)
• libi8x (- to 0.0.5-1)
  • Migration status for libi8x (- to 0.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python3-libi8x/mipsel has unsatisfiable dependency
  • Updating libi8x introduces new bugs: #875373, #918519
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libi8x.html
  • 990 days old (needed 5 days)
• pantomime-clojure (- to 2.1.0+dfsg-1)
  • Migration status for pantomime-clojure (- to 2.1.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by apoikos@dmesg.gr, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): pantomime-clojure tika
  • Depends: pantomime-clojure tika
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantomime-clojure.html
  • 990 days old (needed 5 days)
• libdata-treedumper-renderer-gtk-perl (- to 0.02-2)
  • Migration status for libdata-treedumper-renderer-gtk-perl (- to 0.02-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libdata-treedumper-renderer-gtk-perl introduces new bugs: #912874
  • autopkgtest for libdata-treedumper-renderer-gtk-perl/0.02-2: amd64: Pass, arm64: Regression ♻
  • Build-Depends-Indep: libdata-treedumper-renderer-gtk-perl libgtk2-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdata-treedumper-renderer-gtk-perl.html
  • 993 days old (needed 5 days)
• libhtml-html5-parser-perl (- to 0.301-2)
  • Migration status for libhtml-html5-parser-perl (- to 0.301-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libhtml-html5-parser-perl introduces new bugs: #750946
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhtml-html5-parser-perl.html
  • 1000 days old (needed 5 days)
• pycalendar (- to 1:2.1~git20161130.0.e68e150-1)
  • Migration status for pycalendar (- to 1:2.1~git20161130.0.e68e150-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pycalendar introduces new bugs: #937398
  • Not built on buildd: arch all binaries uploaded by amaramrahul@users.sourceforge.net, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycalendar.html
  • 1006 days old (needed 5 days)
• curlpp (- to 0.8.1-2)
  • Migration status for curlpp (- to 0.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating curlpp introduces new bugs: #867666, #907496
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curlpp.html
  • 1007 days old (needed 5 days)
• fretsonfire (- to 1.3.110.dfsg2-5)
  • Migration status for fretsonfire (- to 1.3.110.dfsg2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • fretsonfire-game/amd64 has unsatisfiable dependency
  • fretsonfire-game/i386 has unsatisfiable dependency
  • Updating fretsonfire introduces new bugs: #943027, #956335
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fretsonfire.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1009 days old (needed 5 days)
• openzwave-controlpanel (- to 0.2a+git20161006.a390f35-2)
  • Migration status for openzwave-controlpanel (- to 0.2a+git20161006.a390f35-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): openzwave-controlpanel openzwave (not considered)
  • Depends: openzwave-controlpanel openzwave (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 1012 days old (needed 5 days)
• sofa-framework (- to 1.0~beta4-12)
  • Migration status for sofa-framework (- to 1.0~beta4-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libsofa1/amd64 has unsatisfiable dependency
  • sofa-apps/amd64 has unsatisfiable dependency
  • libsofa1/arm64 has unsatisfiable dependency
  • sofa-apps/arm64 has unsatisfiable dependency
  • libsofa1/armel has unsatisfiable dependency
  • sofa-apps/armel has unsatisfiable dependency
  • libsofa1/armhf has unsatisfiable dependency
  • sofa-apps/armhf has unsatisfiable dependency
  • libsofa1/i386 has unsatisfiable dependency
  • sofa-apps/i386 has unsatisfiable dependency
  • libsofa1/mips64el has unsatisfiable dependency
  • sofa-apps/mips64el has unsatisfiable dependency
  • libsofa1/mipsel has unsatisfiable dependency
  • sofa-apps/mipsel has unsatisfiable dependency
  • libsofa1/ppc64el has unsatisfiable dependency
  • sofa-apps/ppc64el has unsatisfiable dependency
  • libsofa1/s390x has unsatisfiable dependency
  • sofa-apps/s390x has unsatisfiable dependency
  • Updating sofa-framework introduces new bugs: #875184
  • sofa-framework unsatisfiable Build-Depends(-Arch) on amd64: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on amd64: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on amd64: libqwt5-qt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on arm64: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on arm64: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on arm64: libqwt5-qt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on armel: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on armel: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on armel: libqwt5-qt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on armhf: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on armhf: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on armhf: libqwt5-qt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on i386: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on i386: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on i386: libqwt5-qt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on mips64el: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on mips64el: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on mips64el: libqwt5-qt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on mipsel: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on mipsel: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on mipsel: libqwt5-qt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on ppc64el: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on ppc64el: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on ppc64el: libqwt5-qt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on s390x: libqt4-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on s390x: libqt4-opengl-dev
  • sofa-framework unsatisfiable Build-Depends(-Arch) on s390x: libqwt5-qt4-dev
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sofa-framework.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1016 days old (needed 5 days)
• libjpeg6b (- to 1:6b2-3)
  • Migration status for libjpeg6b (- to 1:6b2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by ballombe
  • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg6b.html
  • 1020 days old (needed 5 days)
• sbt (- to 0.13.13-2)
  • Migration status for sbt (- to 0.13.13-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sbt introduces new bugs: #894540, #915504
  • Not built on buildd: arch all binaries uploaded by tmancill, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbt.html
  • 1020 days old (needed 5 days)
• phpunit-git (- to 2.1.4-1)
  • Migration status for phpunit-git (- to 2.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating phpunit-git introduces new bugs: #935384
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpunit-git.html
  • 1027 days old (needed 5 days)
• php-crypt-gpg (- to 1.6.0-1)
  • Migration status for php-crypt-gpg (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-crypt-gpg introduces new bugs: #882896
  • autopkgtest for php-crypt-gpg/1.6.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-crypt-gpg.html
  • 1030 days old (needed 5 days)
• google-cloud-print-connector (- to 1.12-1)
  • Migration status for google-cloud-print-connector (- to 1.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating google-cloud-print-connector introduces new bugs: #942331, #943542
  • google-cloud-print-connector/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • google-cloud-print-connector/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • google-cloud-print-connector/armel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • google-cloud-print-connector/armhf has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • google-cloud-print-connector/i386 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • google-cloud-print-connector/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/mips64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • google-cloud-print-connector/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/mipsel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • google-cloud-print-connector/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • google-cloud-print-connector/s390x has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • google-cloud-print-connector/s390x has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/amd64
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/arm64
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/armel
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/armhf
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/i386
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/mips64el
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/mipsel
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/ppc64el
  • Impossible Depends: google-cloud-print-connector -> libsnmp30/5.7.3+dfsg-5+b2/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/google-cloud-print-connector.html
  • 1031 days old (needed 5 days)
• ruby-license-finder (- to 2.1.2-2)
  • Migration status for ruby-license-finder (- to 2.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ruby-license-finder introduces new bugs: #880324, #943251
  • autopkgtest for ruby-license-finder/2.1.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • ruby-license-finder unsatisfiable Build-Depends(-Arch) on amd64: python-pip
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-license-finder.html
  • 1031 days old (needed 5 days)
• ocaml-melt (- to 1.4.0-2)
  • Migration status for ocaml-melt (- to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libmelt-ocaml-dev/amd64 has unsatisfiable dependency
  • libmelt-ocaml-dev/arm64 has unsatisfiable dependency
  • libmelt-ocaml-dev/armel has unsatisfiable dependency
  • ocaml-melt/armel has unsatisfiable dependency
  • libmelt-ocaml-dev/armhf has unsatisfiable dependency
  • libmelt-ocaml-dev/i386 has unsatisfiable dependency
  • libmelt-ocaml-dev/mips64el has unsatisfiable dependency
  • ocaml-melt/mips64el has unsatisfiable dependency
  • libmelt-ocaml-dev/mipsel has unsatisfiable dependency
  • ocaml-melt/mipsel has unsatisfiable dependency
  • libmelt-ocaml-dev/ppc64el has unsatisfiable dependency
  • libmelt-ocaml-dev/s390x has unsatisfiable dependency
  • Updating ocaml-melt introduces new bugs: #944600
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-melt.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1033 days old (needed 5 days)
• golang-pault-go-ykpiv (- to 1.1-1)
  • Migration status for golang-pault-go-ykpiv (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-pault-go-ykpiv introduces new bugs: #890929
  • Not built on buildd: arch all binaries uploaded by admwiggin@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-pault-go-ykpiv.html
  • 1038 days old (needed 5 days)
• weresync (- to 1.0.7-1)
  • Migration status for weresync (- to 1.0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating weresync introduces new bugs: #872103, #917729
  • Not built on buildd: arch all binaries uploaded by piotr, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/weresync.html
  • Required age reduced by 3 days because of autopkgtest
  • 1042 days old (needed 2 days)
• ocaml-expect (- to 0.0.5-2)
  • Migration status for ocaml-expect (- to 0.0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libexpect-ocaml/amd64 has unsatisfiable dependency
  • libexpect-ocaml-dev/amd64 has unsatisfiable dependency
  • libexpect-ocaml/arm64 has unsatisfiable dependency
  • libexpect-ocaml-dev/arm64 has unsatisfiable dependency
  • libexpect-ocaml/armel has unsatisfiable dependency
  • libexpect-ocaml-dev/armel has unsatisfiable dependency
  • libexpect-ocaml/armhf has unsatisfiable dependency
  • libexpect-ocaml-dev/armhf has unsatisfiable dependency
  • libexpect-ocaml/i386 has unsatisfiable dependency
  • libexpect-ocaml-dev/i386 has unsatisfiable dependency
  • libexpect-ocaml/mips64el has unsatisfiable dependency
  • libexpect-ocaml-dev/mips64el has unsatisfiable dependency
  • libexpect-ocaml/mipsel has unsatisfiable dependency
  • libexpect-ocaml-dev/mipsel has unsatisfiable dependency
  • libexpect-ocaml/ppc64el has unsatisfiable dependency
  • libexpect-ocaml-dev/ppc64el has unsatisfiable dependency
  • libexpect-ocaml/s390x has unsatisfiable dependency
  • libexpect-ocaml-dev/s390x has unsatisfiable dependency
  • Updating ocaml-expect introduces new bugs: #944599
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-expect.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1043 days old (needed 5 days)
• reprounzip (- to 1.0.10-1)
  • Migration status for reprounzip (- to 1.0.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating reprounzip introduces new bugs: #950839
  • autopkgtest for reprounzip/1.0.10-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reprounzip.html
  • 1049 days old (needed 5 days)
• coq-doc (- to 8.6-1)
  • Migration status for coq-doc (- to 8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating coq-doc introduces new bugs: #939741
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 1050 days old (needed 5 days)
• golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1)
  • Migration status for golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-github-minio-cli introduces new bugs: #869190
  • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-minio-cli.html
  • 1050 days old (needed 5 days)
• xdeb (- to 0.6.7)
  • Migration status for xdeb (- to 0.6.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • xdeb/amd64 has unsatisfiable dependency
  • xdeb/i386 has unsatisfiable dependency
  • xdeb unsatisfiable Build-Depends-Indep on amd64: python-debian (>= 0.1.15~)
  • xdeb unsatisfiable Build-Depends-Indep on amd64: python-apt (>= 0.7.91)
  • Not built on buildd: arch all binaries uploaded by lool, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdeb.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1052 days old (needed 5 days)
• golang-gopkg-mcuadros-go-syslog.v2 (- to 2.2.1-1)
  • Migration status for golang-gopkg-mcuadros-go-syslog.v2 (- to 2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-gopkg-mcuadros-go-syslog.v2 introduces new bugs: #954514
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gopkg-mcuadros-go-syslog.v2.html
  • 1055 days old (needed 5 days)
• coz-profiler (- to 0.1.0-2)
  • Migration status for coz-profiler (- to 0.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating coz-profiler introduces new bugs: #936336
  • autopkgtest for coz-profiler/0.1.0-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coz-profiler.html
  • 1061 days old (needed 5 days)
• openhft-chronicle-queue (- to 3.6.0-2)
  • Migration status for openhft-chronicle-queue (- to 3.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: openhft-chronicle-queue openhft-chronicle-wire (not considered)
  • Invalidated by dependency
  • Build-Depends(-Arch): openhft-chronicle-queue openhft-chronicle-network
  • Depends: openhft-chronicle-queue openhft-chronicle-network
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openhft-chronicle-queue.html
  • 1063 days old (needed 5 days)
• metche (- to 1:1.2.4-1)
  • Migration status for metche (- to 1:1.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating metche introduces new bugs: #913719
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metche.html
  • 1064 days old (needed 5 days)
• libvirt-sandbox (- to 0.5.1+git20160404-1)
  • Migration status for libvirt-sandbox (- to 0.5.1+git20160404-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libvirt-sandbox introduces new bugs: #936935, #939940
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvirt-sandbox.html
  • Required age reduced by 3 days because of autopkgtest
  • 1096 days old (needed 2 days)
• opensvc (- to 1.8~20170412-3)
  • Migration status for opensvc (- to 1.8~20170412-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating opensvc introduces new bugs: #872208, #945680
  • Not built on buildd: arch all binaries uploaded by kelbert, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensvc.html
  • 1110 days old (needed 5 days)
• tendermint-go-db (- to 0.1~20170131~0git72f6dac-2)
  • Migration status for tendermint-go-db (- to 0.1~20170131~0git72f6dac-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): tendermint-go-db tendermint-go-common (not considered)
  • Depends: tendermint-go-db tendermint-go-common (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-db.html
  • 1148 days old (needed 5 days)
• spyder-line-profiler (- to 0.1.1-1)
  • Migration status for spyder-line-profiler (- to 0.1.1-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
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spyder-line-profiler.html
  • Required age reduced by 3 days because of autopkgtest
  • 1150 days old (needed 2 days)
• socklog (- to 2.1.0-8.1)
  • Migration status for socklog (- to 2.1.0-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating socklog introduces new bugs: #834089, #857208
  • Not built on buildd: arch all binaries uploaded by mattia@mapreri.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socklog.html
  • 1161 days old (needed 5 days)
• ecryptfs-utils (- to 111-4)
  • Migration status for ecryptfs-utils (- to 111-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ecryptfs-utils introduces new bugs: #765854, #936465
  • Not built on buildd: arch amd64 binaries uploaded by gcs
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecryptfs-utils.html
  • 1166 days old (needed 5 days)
• rt-app (- to 0.3-2)
  • Migration status for rt-app (- to 0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rt-app introduces new bugs: #945733
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rt-app.html
  • 1166 days old (needed 5 days)
• tendermint-go-common (- to 0~20170309~0gitdcb015d-1)
  • Migration status for tendermint-go-common (- to 0~20170309~0gitdcb015d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-common tendermint-log15
  • Depends: tendermint-go-common tendermint-log15
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-common.html
  • 1175 days old (needed 5 days)
• ants (- to 2.1.0-5)
  • Migration status for ants (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ants introduces new bugs: #872741, #909833
  • Impossible Depends: ants -> libinsighttoolkit4.12/4.12.2-dfsg1-4+b2/amd64
  • Impossible Depends: ants -> libinsighttoolkit4.12/4.12.2-dfsg1-4.1/i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ants.html
  • 1176 days old (needed 5 days)
• tendermint-go-rpc (- to 0.0~git20161021.0.e6e3853-2)
  • Migration status for tendermint-go-rpc (- to 0.0~git20161021.0.e6e3853-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-rpc tendermint-log15
  • Depends: tendermint-go-rpc go-wire
  • Depends: tendermint-go-rpc tendermint-go-common
  • Depends: tendermint-go-rpc tendermint-go-events
  • Depends: tendermint-go-rpc tendermint-log15
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-rpc.html
  • 1178 days old (needed 5 days)
• regina-rexx (- to 3.6-2.1)
  • Migration status for regina-rexx (- to 3.6-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating regina-rexx introduces new bugs: #930005
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/regina-rexx.html
  • 1179 days old (needed 5 days)
• python-django-push-notifications (- to 1.4.1-1)
  • Migration status for python-django-push-notifications (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-django-push-notifications introduces new bugs: #917677
  • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-push-notifications.html
  • 1181 days old (needed 5 days)
• dh-kpatches (- to 0.99.36+nmu4)
  • Migration status for dh-kpatches (- to 0.99.36+nmu4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dh-kpatches introduces new bugs: #876892
  • dh-kpatches unsatisfiable Build-Depends-Indep on amd64: nowebm
  • Not built on buildd: arch all binaries uploaded by lamby, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-kpatches.html
  • 1186 days old (needed 5 days)
• golang-github-karlseguin-ccache (- to 2.0.2+git20161222.2.12c7ffd-1)
  • Migration status for golang-github-karlseguin-ccache (- to 2.0.2+git20161222.2.12c7ffd-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating golang-github-karlseguin-ccache introduces new bugs: #952187
  • Not built on buildd: arch all binaries uploaded by tpot@samba.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-karlseguin-ccache.html
  • 1200 days old (needed 5 days)
• merkleeyes (- to 0.0~git20170130.0.549dd01-1)
  • Migration status for merkleeyes (- to 0.0~git20170130.0.549dd01-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • merkleeyes/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • merkleeyes/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • merkleeyes/armel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • merkleeyes/armhf has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • merkleeyes/i386 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • merkleeyes/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/mips64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • merkleeyes/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/mipsel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • merkleeyes/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • merkleeyes/s390x has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • merkleeyes/s390x has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • Build-Depends(-Arch): merkleeyes go-wire
  • Built-Using: merkleeyes abci
  • Built-Using: merkleeyes go-wire
  • Built-Using: merkleeyes tendermint-go-common
  • Built-Using: merkleeyes tendermint-go-db
  • Built-Using: merkleeyes tendermint-go-logger
  • Built-Using: merkleeyes tendermint-go-merkle
  • Built-Using: merkleeyes tendermint-log15
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/merkleeyes.html
  • 1203 days old (needed 5 days)
• pysiogame (- to 3.60.814-2)
  • Migration status for pysiogame (- to 3.60.814-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pysiogame introduces new bugs: #912491, #945699
  • Not built on buildd: arch all binaries uploaded by miriam, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysiogame.html
  • 1204 days old (needed 5 days)
• tendermint-go-autofile (- to 0.0~20170129~0git48b17de-1)
  • Migration status for tendermint-go-autofile (- to 0.0~20170129~0git48b17de-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-autofile tendermint-go-common
  • Depends: tendermint-go-autofile tendermint-go-common
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-autofile.html
  • 1211 days old (needed 5 days)
• php-gettext (- to 1.0.12-0.1)
  • Migration status for php-gettext (- to 1.0.12-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-gettext introduces new bugs: #851771
  • Not built on buildd: arch all binaries uploaded by jmw, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-gettext.html
  • 1212 days old (needed 5 days)
• tendermint-go-merkle (- to 0.1~20170131~0git7a86b44-1)
  • Migration status for tendermint-go-merkle (- to 0.1~20170131~0git7a86b44-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-merkle go-wire
  • Depends: tendermint-go-merkle go-wire
  • Depends: tendermint-go-merkle tendermint-go-common
  • Depends: tendermint-go-merkle tendermint-go-db
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-merkle.html
  • 1212 days old (needed 5 days)
• tendermint-go-p2p (- to 0.0~git20170113.0.3d98f67-1)
  • Migration status for tendermint-go-p2p (- to 0.0~git20170113.0.3d98f67-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-p2p tendermint-log15
  • Depends: tendermint-go-p2p go-wire
  • Depends: tendermint-go-p2p tendermint-go-common
  • Depends: tendermint-go-p2p tendermint-go-config
  • Depends: tendermint-go-p2p tendermint-go-crypto
  • Depends: tendermint-go-p2p tendermint-go-logger
  • Depends: tendermint-go-p2p tendermint-log15
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-p2p.html
  • 1212 days old (needed 5 days)
• abci (- to 0.0~git20170124.0.f94ae5e-2)
  • Migration status for abci (- to 0.0~git20170124.0.f94ae5e-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • abci/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/amd64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • abci/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/arm64 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • abci/armel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/armel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • abci/armhf has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/armhf has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • abci/i386 has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/i386 has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • abci/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/mips64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • abci/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/mipsel has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • abci/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/ppc64el has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • abci/s390x has unsatisfiable Built-Using on golang-1.11 1.11.6-1
  • abci/s390x has unsatisfiable Built-Using on golang-golang-x-net-dev 1:0.0+git20181201.351d144+dfsg-3
  • Build-Depends(-Arch): abci go-wire
  • Built-Using: abci go-wire
  • Built-Using: abci tendermint-go-common
  • Built-Using: abci tendermint-go-crypto
  • Built-Using: abci tendermint-go-db
  • Built-Using: abci tendermint-go-logger
  • Built-Using: abci tendermint-go-merkle
  • Built-Using: abci tendermint-go-process
  • Built-Using: abci tendermint-log15
  • Depends: abci go-wire
  • Depends: abci tendermint-go-common
  • Depends: abci tendermint-go-crypto
  • Depends: abci tendermint-go-db
  • Depends: abci tendermint-go-logger
  • Depends: abci tendermint-go-merkle
  • Depends: abci tendermint-go-process
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abci.html
  • 1215 days old (needed 5 days)
• clblas (- to 2.12-1)
  • Migration status for clblas (- to 2.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating clblas introduces new bugs: #949767
  • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clblas.html
  • Required age reduced by 3 days because of autopkgtest
  • 1218 days old (needed 2 days)
• guacamole-server (- to 0.9.9-2)
  • Migration status for guacamole-server (- to 0.9.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libguac-client-rdp0/amd64 has unsatisfiable dependency
  • libguac-client-rdp0/arm64 has unsatisfiable dependency
  • libguac-client-rdp0/armel has unsatisfiable dependency
  • libguac-client-rdp0/armhf has unsatisfiable dependency
  • libguac-client-rdp0/i386 has unsatisfiable dependency
  • libguac-client-rdp0/mips64el has unsatisfiable dependency
  • libguac-client-rdp0/mipsel has unsatisfiable dependency
  • libguac-client-rdp0/ppc64el has unsatisfiable dependency
  • libguac-client-rdp0/s390x has unsatisfiable dependency
  • Updating guacamole-server introduces new bugs: #888321
  • guacamole-server unsatisfiable Build-Depends(-Arch) on amd64: libfreerdp-dev (>= 1.0.1)
  • guacamole-server unsatisfiable Build-Depends(-Arch) on arm64: libfreerdp-dev (>= 1.0.1)
  • guacamole-server unsatisfiable Build-Depends(-Arch) on armel: libfreerdp-dev (>= 1.0.1)
  • guacamole-server unsatisfiable Build-Depends(-Arch) on armhf: libfreerdp-dev (>= 1.0.1)
  • guacamole-server unsatisfiable Build-Depends(-Arch) on i386: libfreerdp-dev (>= 1.0.1)
  • guacamole-server unsatisfiable Build-Depends(-Arch) on mips64el: libfreerdp-dev (>= 1.0.1)
  • guacamole-server unsatisfiable Build-Depends(-Arch) on mipsel: libfreerdp-dev (>= 1.0.1)
  • guacamole-server unsatisfiable Build-Depends(-Arch) on ppc64el: libfreerdp-dev (>= 1.0.1)
  • guacamole-server unsatisfiable Build-Depends(-Arch) on s390x: libfreerdp-dev (>= 1.0.1)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guacamole-server.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1218 days old (needed 5 days)
• osmalchemy (- to 0.1.+3-1)
  • Migration status for osmalchemy (- to 0.1.+3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating osmalchemy introduces new bugs: #934958
  • autopkgtest for osmalchemy/0.1.+3-1: amd64: Pass, arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/osmalchemy.html
  • 1218 days old (needed 5 days)
• tendermint-go-process (- to 0.1~20170125~0gitb27edfd-1)
  • Migration status for tendermint-go-process (- to 0.1~20170125~0gitb27edfd-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-process tendermint-go-common
  • Depends: tendermint-go-process tendermint-go-common
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-process.html
  • 1218 days old (needed 5 days)
• ketchup (- to 1.0.1+git20111228+e1c62066-2)
  • Migration status for ketchup (- to 1.0.1+git20111228+e1c62066-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ketchup introduces new bugs: #936785
  • Not built on buildd: arch all binaries uploaded by johfel@gmx.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ketchup.html
  • 1220 days old (needed 5 days)
• nxt-firmware (- to 1.29-20120908+dfsg-7)
  • Migration status for nxt-firmware (- to 1.29-20120908+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating nxt-firmware introduces new bugs: #954598
  • Not built on buildd: arch all binaries uploaded by nik@naturalnet.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nxt-firmware.html
  • 1224 days old (needed 5 days)
• neard (- to 0.16-0.1)
  • Migration status for neard (- to 0.16-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating neard introduces new bugs: #937125
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neard.html
  • 1225 days old (needed 5 days)
• tendermint-go-crypto (- to 0.0~git20160724.0.4b11d62-1)
  • Migration status for tendermint-go-crypto (- to 0.0~git20160724.0.4b11d62-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-crypto go-wire
  • Depends: tendermint-go-crypto go-wire
  • Depends: tendermint-go-crypto tendermint-go-common
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-crypto.html
  • 1226 days old (needed 5 days)
• util-vserver (- to 0.30.216-pre3120-1.4)
  • Migration status for util-vserver (- to 0.30.216-pre3120-1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating util-vserver introduces new bugs: #938764
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/util-vserver.html
  • 1226 days old (needed 5 days)
• bookkeeper (- to 4.4.0-1)
  • Migration status for bookkeeper (- to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating bookkeeper introduces new bugs: #906340
  • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookkeeper.html
  • 1227 days old (needed 5 days)
• mysqmail (- to 0.4.9-10.2)
  • Migration status for mysqmail (- to 0.4.9-10.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: mysqmail pure-ftpd (not considered)
  • Invalidated by dependency
  • Depends: mysqmail courier
  • Depends: mysqmail dovecot
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysqmail.html
  • 1229 days old (needed 5 days)
• binutils-msp430 (- to 2.22~msp20120406-5.1)
  • Migration status for binutils-msp430 (- to 2.22~msp20120406-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating binutils-msp430 introduces new bugs: #853329
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-msp430.html
  • 1230 days old (needed 5 days)
• free42-nologo (- to 1.4.77-1.2)
  • Migration status for free42-nologo (- to 1.4.77-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating free42-nologo introduces new bugs: #911464
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/free42-nologo.html
  • 1230 days old (needed 5 days)
• gcc-msp430 (- to 4.6.3~mspgcc-20120406-7.1)
  • Migration status for gcc-msp430 (- to 4.6.3~mspgcc-20120406-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gcc-msp430 introduces new bugs: #925692
  • Build-Depends(-Arch): gcc-msp430 binutils-msp430
  • Depends: gcc-msp430 binutils-msp430
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-msp430.html
  • 1230 days old (needed 5 days)
• gdb-msp430 (- to 7.2a~mspgcc-20111205-3.1)
  • Migration status for gdb-msp430 (- to 7.2a~mspgcc-20111205-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): gdb-msp430 binutils-msp430 (not considered)
  • Depends: gdb-msp430 binutils-msp430 (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdb-msp430.html
  • 1230 days old (needed 5 days)
• origami (- to 1.2.7+really0.7.4-1.1)
  • Migration status for origami (- to 1.2.7+really0.7.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating origami introduces new bugs: #953144
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/origami.html
  • 1230 days old (needed 5 days)
• gli (- to 0.8.2.0+ds1-2)
  • Migration status for gli (- to 0.8.2.0+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gli introduces new bugs: #888933
  • autopkgtest for gli/0.8.2.0+ds1-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gli.html
  • 1231 days old (needed 5 days)
• vmm (- to 0.6.2-2)
  • Migration status for vmm (- to 0.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • vmm/amd64 has unsatisfiable dependency
  • vmm/i386 has unsatisfiable dependency
  • Updating vmm introduces new bugs: #938794
  • vmm unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
  • Not built on buildd: arch all binaries uploaded by madduck, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vmm.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1233 days old (needed 5 days)
• mytop (- to 1.9.1-4)
  • Migration status for mytop (- to 1.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mytop introduces new bugs: #863596
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mytop.html
  • 1234 days old (needed 5 days)
• ion (- to 3.2.1+dfsg-1.1)
  • Migration status for ion (- to 3.2.1+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ion introduces new bugs: #853456
  • Not built on buildd: arch amd64 binaries uploaded by glaubitz@physik.fu-berlin.de
  • Not built on buildd: arch all binaries uploaded by glaubitz@physik.fu-berlin.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ion.html
  • 1235 days old (needed 5 days)
• libaria (- to 2.8.0+repack-1.2)
  • Migration status for libaria (- to 2.8.0+repack-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libaria introduces new bugs: #936842
  • Not built on buildd: arch all binaries uploaded by glaubitz@physik.fu-berlin.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libaria.html
  • 1235 days old (needed 5 days)
• rdup (- to 1.1.15-1)
  • Migration status for rdup (- to 1.1.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rdup introduces new bugs: #941101
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/amd64
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/arm64
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/armel
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/armhf
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/i386
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/mips64el
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/mipsel
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/ppc64el
  • Impossible Depends: rdup -> libnettle6/3.5.1+really3.4.1-1/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdup.html
  • 1235 days old (needed 5 days)
• mysql-utilities (- to 1.6.4-1)
  • Migration status for mysql-utilities (- to 1.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mysql-utilities/amd64 has unsatisfiable dependency
  • mysql-utilities/i386 has unsatisfiable dependency
  • Updating mysql-utilities introduces new bugs: #877856
  • mysql-utilities unsatisfiable Build-Depends(-Arch) on amd64: python-mysql.connector (>= 1.2.1)
  • Not built on buildd: arch all binaries uploaded by morph, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-utilities.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1237 days old (needed 5 days)
• verilog-mode (- to 20161124.fd230e6-2)
  • Migration status for verilog-mode (- to 20161124.fd230e6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating verilog-mode introduces new bugs: #934977
  • verilog-mode unsatisfiable Build-Depends(-Arch) on amd64: emacs25
  • Not built on buildd: arch all binaries uploaded by spwhitton@spwhitton.name, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilog-mode.html
  • 1240 days old (needed 5 days)
• caldav-tester (- to 7.0-3)
  • Migration status for caldav-tester (- to 7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • caldav-tester unsatisfiable Build-Depends(-Arch) on amd64: python-pip
  • Depends: caldav-tester pycalendar
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caldav-tester.html
  • Required age reduced by 3 days because of autopkgtest
  • 1244 days old (needed 2 days)
• simpleburn (- to 1.8.0-1)
  • Migration status for simpleburn (- to 1.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating simpleburn introduces new bugs: #929381
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simpleburn.html
  • 1248 days old (needed 5 days)
• petri-foo (- to 0.1.87-4)
  • Migration status for petri-foo (- to 0.1.87-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating petri-foo introduces new bugs: #907691
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/petri-foo.html
  • 1250 days old (needed 5 days)
• scanlogd (- to 2.2.5-3.3)
  • Migration status for scanlogd (- to 2.2.5-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating scanlogd introduces new bugs: #945478
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scanlogd.html
  • 1250 days old (needed 5 days)
• klick (- to 0.12.2-4)
  • Migration status for klick (- to 0.12.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating klick introduces new bugs: #947566
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/klick.html
  • 1252 days old (needed 5 days)
• xenomai (- to 2.6.4+dfsg-1)
  • Migration status for xenomai (- to 2.6.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • xenomai-kernel-source/amd64 has unsatisfiable dependency
  • xenomai-kernel-source/i386 has unsatisfiable dependency
  • Updating xenomai introduces new bugs: #925451, #925453
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xenomai.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1253 days old (needed 5 days)
• gnuift (- to 0.1.14+ds-1)
  • Migration status for gnuift (- to 0.1.14+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gnuift introduces new bugs: #897761, #906032
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnuift.html
  • 1254 days old (needed 5 days)
• iptables-optimizer (- to 0.9.14-1)
  • Migration status for iptables-optimizer (- to 0.9.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating iptables-optimizer introduces new bugs: #943064
  • iptables-optimizer unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 1.2.3)
  • Not built on buildd: arch all binaries uploaded by agx, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iptables-optimizer.html
  • 1258 days old (needed 5 days)
• sugar-etoys-activity (- to 116-7)
  • Migration status for sugar-etoys-activity (- to 116-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sugar-etoys-activity introduces new bugs: #938587
  • sugar-etoys-activity unsatisfiable Build-Depends(-Arch) on amd64: python-sugar3
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 1261 days old (needed 5 days)
• tendermint-go-config (- to 0.0~git20160626.0.e64b424-1)
  • Migration status for tendermint-go-config (- to 0.0~git20160626.0.e64b424-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-config tendermint-go-common
  • Depends: tendermint-go-config tendermint-go-common
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-config.html
  • 1266 days old (needed 5 days)
• freehdl (- to 0.0.8-2.2)
  • Migration status for freehdl (- to 0.0.8-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating freehdl introduces new bugs: #885188
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freehdl.html
  • 1268 days old (needed 5 days)
• netperf (- to 2.6.0-2.1)
  • Migration status for netperf (- to 2.6.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating netperf introduces new bugs: #910625
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 1272 days old (needed 5 days)
• debget (- to 1.6+nmu4)
  • Migration status for debget (- to 1.6+nmu4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating debget introduces new bugs: #816393
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debget.html
  • 1273 days old (needed 5 days)
• guacamole-client (- to 0.9.9+dfsg-1)
  • Migration status for guacamole-client (- to 0.9.9+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • guacamole/amd64 has unsatisfiable dependency
  • guacamole/i386 has unsatisfiable dependency
  • Updating guacamole-client introduces new bugs: #891798, #926275, #926276
  • Not built on buildd: arch all binaries uploaded by nik@naturalnet.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guacamole-client.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1275 days old (needed 5 days)
• php-xml-rpc2 (- to 1.1.3-0.1)
  • Migration status for php-xml-rpc2 (- to 1.1.3-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ondrej, a new source-only upload is needed to allow migration
  • Depends: php-xml-rpc2 php-cache-lite
  • Depends: php-xml-rpc2 php-http-request2
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-xml-rpc2.html
  • 1275 days old (needed 5 days)
• battery-stats (- to 0.5.6-1)
  • Migration status for battery-stats (- to 0.5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating battery-stats introduces new bugs: #936187
  • battery-stats unsatisfiable Build-Depends(-Arch) on amd64: python-matplotlib
  • battery-stats unsatisfiable Build-Depends(-Arch) on arm64: python-matplotlib
  • battery-stats unsatisfiable Build-Depends(-Arch) on armel: python-matplotlib
  • battery-stats unsatisfiable Build-Depends(-Arch) on armhf: python-matplotlib
  • battery-stats unsatisfiable Build-Depends(-Arch) on i386: python-matplotlib
  • battery-stats unsatisfiable Build-Depends(-Arch) on mips64el: python-matplotlib
  • battery-stats unsatisfiable Build-Depends(-Arch) on mipsel: python-matplotlib
  • battery-stats unsatisfiable Build-Depends(-Arch) on ppc64el: python-matplotlib
  • battery-stats unsatisfiable Build-Depends(-Arch) on s390x: python-matplotlib
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/battery-stats.html
  • 1287 days old (needed 5 days)
• powermock (- to 1.6.6-1)
  • Migration status for powermock (- to 1.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating powermock introduces new bugs: #875358
  • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/powermock.html
  • 1293 days old (needed 5 days)
• zyn (- to 1+git.20100609+dfsg0-4)
  • Migration status for zyn (- to 1+git.20100609+dfsg0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): zyn lv2dynparam1 (not considered)
  • Depends: zyn lv2dynparam1 (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zyn.html
  • 1294 days old (needed 5 days)
• lv2dynparam1 (- to 2-6)
  • Migration status for lv2dynparam1 (- to 2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lv2dynparam1 introduces new bugs: #946068
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lv2dynparam1.html
  • 1297 days old (needed 5 days)
• paulstretch (- to 2.2-2-4)
  • Migration status for paulstretch (- to 2.2-2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating paulstretch introduces new bugs: #952055
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paulstretch.html
  • 1300 days old (needed 5 days)
• tendermint-go-events (- to 0.0~git20161021.0.1c85cb9-1)
  • Migration status for tendermint-go-events (- to 0.0~git20161021.0.1c85cb9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): tendermint-go-events tendermint-go-logger
  • Depends: tendermint-go-events tendermint-go-common
  • Depends: tendermint-go-events tendermint-go-logger
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-go-events.html
  • 1302 days old (needed 5 days)
• origami-pdf (- to 2.0.0-1)
  • Migration status for origami-pdf (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating origami-pdf introduces new bugs: #951248
  • autopkgtest for origami-pdf/2.0.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/origami-pdf.html
  • 1306 days old (needed 5 days)
• node-jsdom (- to 0.8.10+dfsg1-2)
  • Migration status for node-jsdom (- to 0.8.10+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • node-jsdom/amd64 has unsatisfiable dependency
  • node-jsdom/i386 has unsatisfiable dependency
  • Updating node-jsdom introduces new bugs: #743151, #842023
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/node-jsdom.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1310 days old (needed 5 days)
• debdry (- to 0.2.2-1)
  • Migration status for debdry (- to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating debdry introduces new bugs: #954560
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debdry.html
  • 1311 days old (needed 5 days)
• python-nemu (- to 0.3.1-1)
  • Migration status for python-nemu (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-nemu introduces new bugs: #937940
  • Not built on buildd: arch all binaries uploaded by tincho, a new source-only upload is needed to allow migration
  • Depends: python-nemu python-passfd
  • Depends: python-nemu python-unshare
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nemu.html
  • 1311 days old (needed 5 days)
• python-passfd (- to 0.2-3)
  • Migration status for python-passfd (- to 0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-passfd introduces new bugs: #938001
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-passfd.html
  • 1311 days old (needed 5 days)
• python-unshare (- to 0.2-1)
  • Migration status for python-unshare (- to 0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-unshare introduces new bugs: #938241
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-unshare.html
  • 1311 days old (needed 5 days)
• oidua (- to 0.16.1-9)
  • Migration status for oidua (- to 0.16.1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating oidua introduces new bugs: #943136
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oidua.html
  • 1312 days old (needed 5 days)
• mps-youtube (- to 0.2.7.1-2)
  • Migration status for mps-youtube (- to 0.2.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mps-youtube introduces new bugs: #867505, #877035, #952583
  • Not built on buildd: arch all binaries uploaded by zlatan, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mps-youtube.html
  • 1316 days old (needed 5 days)
• pycmail (- to 0.1.6)
  • Migration status for pycmail (- to 0.1.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pycmail introduces new bugs: #934903, #945727
  • Not built on buildd: arch all binaries uploaded by garabik, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycmail.html
  • 1318 days old (needed 5 days)
• tendermint-log15 (- to 2.3-67-g9545b24-2)
  • Migration status for tendermint-log15 (- to 2.3-67-g9545b24-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tendermint-log15 introduces new bugs: #954519
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tendermint-log15.html
  • 1326 days old (needed 5 days)
• rtpproxy (- to 1.2.1-2.2)
  • Migration status for rtpproxy (- to 1.2.1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rtpproxy introduces new bugs: #874070
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rtpproxy.html
  • 1334 days old (needed 5 days)
• kryo-serializers (- to 0.22-3)
  • Migration status for kryo-serializers (- to 0.22-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating kryo-serializers introduces new bugs: #875594
  • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kryo-serializers.html
  • 1338 days old (needed 5 days)
• field3d (- to 1.7.2-1)
  • Migration status for field3d (- to 1.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating field3d introduces new bugs: #939660
  • autopkgtest for field3d/1.7.2-1: amd64: Pass, arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mfv.debian@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/field3d.html
  • 1346 days old (needed 5 days)
• inform-mode (- to 1.5.8-4)
  • Migration status for inform-mode (- to 1.5.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating inform-mode introduces new bugs: #941829
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/inform-mode.html
  • 1346 days old (needed 5 days)
• eurephia (- to 1.1.0-6)
  • Migration status for eurephia (- to 1.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating eurephia introduces new bugs: #951780
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eurephia.html
  • 1349 days old (needed 5 days)
• linux-wlan-ng (- to 0.2.9+dfsg-6)
  • Migration status for linux-wlan-ng (- to 0.2.9+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch amd64 binaries uploaded by gareuselesinge
  • Not built on buildd: arch all binaries uploaded by gareuselesinge, a new source-only upload is needed to allow migration
  • Not touching package due to block request by jcristau (please contact debian-release if update is needed)
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-wlan-ng.html
  • 1353 days old (needed 5 days)
• nurpawiki (- to 1.2.3-10)
  • Migration status for nurpawiki (- to 1.2.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • nurpawiki/amd64 has unsatisfiable dependency
  • nurpawiki/arm64 has unsatisfiable dependency
  • nurpawiki/armel has unsatisfiable dependency
  • nurpawiki/armhf has unsatisfiable dependency
  • nurpawiki/i386 has unsatisfiable dependency
  • nurpawiki/mips64el has unsatisfiable dependency
  • nurpawiki/mipsel has unsatisfiable dependency
  • nurpawiki/ppc64el has unsatisfiable dependency
  • nurpawiki/s390x has unsatisfiable dependency
  • Build-Depends(-Arch): nurpawiki eliom
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/nurpawiki.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1373 days old (needed 5 days)
• eliom (- to 4.2-3)
  • Migration status for eliom (- to 4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libeliom-ocaml-dev/amd64 has unsatisfiable dependency
  • libeliom-ocaml-dev/arm64 has unsatisfiable dependency
  • libeliom-ocaml-dev/armel has unsatisfiable dependency
  • libeliom-ocaml-dev/armhf has unsatisfiable dependency
  • libeliom-ocaml-dev/i386 has unsatisfiable dependency
  • eliom/mips64el has unsatisfiable dependency
  • libeliom-ocaml-dev/mips64el has unsatisfiable dependency
  • eliom/mipsel has unsatisfiable dependency
  • libeliom-ocaml-dev/mipsel has unsatisfiable dependency
  • eliom/ppc64el has unsatisfiable dependency
  • libeliom-ocaml-dev/ppc64el has unsatisfiable dependency
  • eliom/s390x has unsatisfiable dependency
  • libeliom-ocaml-dev/s390x has unsatisfiable dependency
  • Updating eliom introduces new bugs: #956887
  • Not built on buildd: arch all binaries uploaded by glondu, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/eliom.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1374 days old (needed 5 days)
• arrayfire (- to 3.3.2+dfsg1-4)
  • Migration status for arrayfire (- to 3.3.2+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating arrayfire introduces new bugs: #892288, #897707
  • autopkgtest for arrayfire/3.3.2+dfsg1-4: amd64: Pass, arm64: Regression ♻
  • Build-Depends(-Arch): arrayfire clblas
  • Depends: arrayfire clblas
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arrayfire.html
  • 1380 days old (needed 5 days)
• galax (- to 1.1-15)
  • Migration status for galax (- to 1.1-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libgalax-ocaml-dev/amd64 has unsatisfiable dependency
  • libgalax-ocaml-dev/arm64 has unsatisfiable dependency
  • galax-extra/armel has unsatisfiable dependency
  • galaxd/armel has unsatisfiable dependency
  • libgalax-ocaml-dev/armel has unsatisfiable dependency
  • libgalax-ocaml-dev/armhf has unsatisfiable dependency
  • libgalax-ocaml-dev/i386 has unsatisfiable dependency
  • galax-extra/mips64el has unsatisfiable dependency
  • galaxd/mips64el has unsatisfiable dependency
  • libgalax-ocaml-dev/mips64el has unsatisfiable dependency
  • galax-extra/mipsel has unsatisfiable dependency
  • galaxd/mipsel has unsatisfiable dependency
  • libgalax-ocaml-dev/mipsel has unsatisfiable dependency
  • libgalax-ocaml-dev/ppc64el has unsatisfiable dependency
  • libgalax-ocaml-dev/s390x has unsatisfiable dependency
  • Updating galax introduces new bugs: #922692
  • Not built on buildd: arch all binaries uploaded by glondu, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/galax.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1383 days old (needed 5 days)
• the (- to 3.3~rc1-3)
  • Migration status for the (- to 3.3~rc1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): the regina-rexx (not considered)
  • Depends: the regina-rexx (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/the.html
  • 1386 days old (needed 5 days)
• ecere-sdk (- to 0.44.15-1)
  • Migration status for ecere-sdk (- to 0.44.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ecere-sdk introduces new bugs: #898832
  • Impossible Depends: ecere-sdk -> libffi6/3.2.1-9/i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecere-sdk.html
  • 1391 days old (needed 5 days)
• blcr (- to 0.8.5-2.3)
  • Migration status for blcr (- to 0.8.5-2.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating blcr introduces new bugs: #876908, #877238
  • Build-Depends(-Arch): blcr dh-kpatches
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blcr.html
  • 1392 days old (needed 5 days)
• flashplugin-nonfree (- to 1:3.7)
  • Migration status for flashplugin-nonfree (- to 1:3.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • flashplugin-nonfree/amd64 has unsatisfiable dependency
  • flashplugin-nonfree/i386 has unsatisfiable dependency
  • Updating flashplugin-nonfree introduces new bugs: #851066, #889804, #946889
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • uninstallable on arch amd64, not running autopkgtest there
  • 1392 days old (needed 5 days)
• projectreactor (- to 2.0.8-1)
  • Migration status for projectreactor (- to 2.0.8-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
  • Build-Depends(-Arch): projectreactor openhft-chronicle-queue
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/projectreactor.html
  • 1393 days old (needed 5 days)
• lout (- to 3.39-3)
  • Migration status for lout (- to 3.39-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lout introduces new bugs: #947113
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lout.html
  • 1395 days old (needed 5 days)
• nfqueue-bindings (- to 0.6-1)
  • Migration status for nfqueue-bindings (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libnfqueue-perl/amd64 has unsatisfiable dependency
  • libnfqueue-perl/arm64 has unsatisfiable dependency
  • libnfqueue-perl/armel has unsatisfiable dependency
  • libnfqueue-perl/armhf has unsatisfiable dependency
  • libnfqueue-perl/i386 has unsatisfiable dependency
  • libnfqueue-perl/mips64el has unsatisfiable dependency
  • libnfqueue-perl/mipsel has unsatisfiable dependency
  • libnfqueue-perl/ppc64el has unsatisfiable dependency
  • libnfqueue-perl/s390x has unsatisfiable dependency
  • Updating nfqueue-bindings introduces new bugs: #906495, #937136
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nfqueue-bindings.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1401 days old (needed 5 days)
• accelio (- to 1.7-2)
  • Migration status for accelio (- to 1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating accelio introduces new bugs: #853298
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/accelio.html
  • 1403 days old (needed 5 days)
• spyne (- to 2.12.11-1)
  • Migration status for spyne (- to 2.12.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-spyne/amd64 has unsatisfiable dependency
  • python-spyne/i386 has unsatisfiable dependency
  • Updating spyne introduces new bugs: #938554, #960662
  • Not built on buildd: arch all binaries uploaded by ras, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spyne.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1403 days old (needed 5 days)
• xorp (- to 1.8.6~wip.20160715-2)
  • Migration status for xorp (- to 1.8.6~wip.20160715-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xorp introduces new bugs: #947586
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xorp.html
  • 1404 days old (needed 5 days)
• cons (- to 2.3.0.1+2.2.0-2)
  • Migration status for cons (- to 2.3.0.1+2.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cons introduces new bugs: #904627
  • Not built on buildd: arch all binaries uploaded by hsteoh, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cons.html
  • 1408 days old (needed 5 days)
• grip (- to 4.2.0-3)
  • Migration status for grip (- to 4.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating grip introduces new bugs: #953967
  • autopkgtest for grip/4.2.0-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grip.html
  • 1423 days old (needed 5 days)
• python-keepkey (- to 0.7.3-1)
  • Migration status for python-keepkey (- to 0.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-keepkey/amd64 has unsatisfiable dependency
  • python-keepkey/i386 has unsatisfiable dependency
  • Updating python-keepkey introduces new bugs: #934839, #937869
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-keepkey.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1423 days old (needed 5 days)
• dhcpy6d (- to 0.4.3-1)
  • Migration status for dhcpy6d (- to 0.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating dhcpy6d introduces new bugs: #936391
  • Not built on buildd: arch all binaries uploaded by abe, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dhcpy6d.html
  • 1429 days old (needed 5 days)
• pdf.js (- to 1.5.188+dfsg-1)
  • Migration status for pdf.js (- to 1.5.188+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pdf.js introduces new bugs: #906835
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdf.js.html
  • 1429 days old (needed 5 days)
• php-net-ldap2 (- to 2.2.0-3)
  • Migration status for php-net-ldap2 (- to 2.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-net-ldap2 introduces new bugs: #882938
  • autopkgtest for php-net-ldap2/2.2.0-3: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-ldap2.html
  • 1434 days old (needed 5 days)
• pegtl (- to 1.3.1-1)
  • Migration status for pegtl (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pegtl introduces new bugs: #908493
  • Not built on buildd: arch amd64 binaries uploaded by wrar
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pegtl.html
  • 1436 days old (needed 5 days)
• libretro-mupen64plus (- to 2.0+git20160207+dfsg2-1)
  • Migration status for libretro-mupen64plus (- to 2.0+git20160207+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libretro-mupen64plus introduces new bugs: #935282
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-mupen64plus.html
  • 1444 days old (needed 5 days)
• tightvnc-java (- to 1.2.7-9)
  • Migration status for tightvnc-java (- to 1.2.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tightvnc-java introduces new bugs: #894789
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 1446 days old (needed 5 days)
• vnc-java (- to 3.3.3r2-9)
  • Migration status for vnc-java (- to 3.3.3r2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vnc-java introduces new bugs: #894788
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 1446 days old (needed 5 days)
• ruby-packable (- to 1.3.8-1)
  • Migration status for ruby-packable (- to 1.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ruby-packable introduces new bugs: #888164
  • autopkgtest for ruby-packable/1.3.8-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-packable.html
  • 1450 days old (needed 5 days)
• elektra (- to 0.8.14-5.1)
  • Migration status for elektra (- to 0.8.14-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • elektra-tests/amd64 has unsatisfiable dependency
  • libelektra4-python/amd64 has unsatisfiable dependency
  • python3-elektra/amd64 has unsatisfiable dependency
  • elektra-tests/arm64 has unsatisfiable dependency
  • libelektra4-python/arm64 has unsatisfiable dependency
  • python3-elektra/arm64 has unsatisfiable dependency
  • elektra-tests/armel has unsatisfiable dependency
  • libelektra4-python/armel has unsatisfiable dependency
  • python3-elektra/armel has unsatisfiable dependency
  • elektra-tests/armhf has unsatisfiable dependency
  • libelektra4-python/armhf has unsatisfiable dependency
  • python3-elektra/armhf has unsatisfiable dependency
  • elektra-tests/i386 has unsatisfiable dependency
  • libelektra4-python/i386 has unsatisfiable dependency
  • python3-elektra/i386 has unsatisfiable dependency
  • elektra-tests/mips64el has unsatisfiable dependency
  • libelektra4-python/mips64el has unsatisfiable dependency
  • python3-elektra/mips64el has unsatisfiable dependency
  • elektra-tests/mipsel has unsatisfiable dependency
  • libelektra4-python/mipsel has unsatisfiable dependency
  • python3-elektra/mipsel has unsatisfiable dependency
  • elektra-tests/ppc64el has unsatisfiable dependency
  • libelektra4-python/ppc64el has unsatisfiable dependency
  • python3-elektra/ppc64el has unsatisfiable dependency
  • elektra-tests/s390x has unsatisfiable dependency
  • libelektra4-python/s390x has unsatisfiable dependency
  • python3-elektra/s390x has unsatisfiable dependency
  • Updating elektra introduces new bugs: #844145, #846200, #851592, #881676, #956949
  • elektra unsatisfiable Build-Depends(-Arch) on amd64: swig3.0
  • elektra unsatisfiable Build-Depends(-Arch) on arm64: swig3.0
  • elektra unsatisfiable Build-Depends(-Arch) on armel: swig3.0
  • elektra unsatisfiable Build-Depends(-Arch) on armhf: swig3.0
  • elektra unsatisfiable Build-Depends(-Arch) on i386: swig3.0
  • elektra unsatisfiable Build-Depends(-Arch) on mips64el: swig3.0
  • elektra unsatisfiable Build-Depends(-Arch) on mipsel: swig3.0
  • elektra unsatisfiable Build-Depends(-Arch) on ppc64el: swig3.0
  • elektra unsatisfiable Build-Depends(-Arch) on s390x: swig3.0
  • Not built on buildd: arch amd64 binaries uploaded by aeb
  • Not built on buildd: arch all binaries uploaded by aeb, a new source-only upload is needed to allow migration
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/elektra.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1454 days old (needed 5 days)
• nglister (- to 1.0.2)
  • Migration status for nglister (- to 1.0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating nglister introduces new bugs: #937138
  • Not built on buildd: arch all binaries uploaded by jgoerzen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nglister.html
  • 1459 days old (needed 5 days)
• autofill-forms (- to 1.1.3-1)
  • Migration status for autofill-forms (- to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating autofill-forms introduces new bugs: #899309
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autofill-forms.html
  • 1461 days old (needed 5 days)
• matita (- to 0.99.3-1)
  • Migration status for matita (- to 0.99.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • matita/armel has unsatisfiable dependency
  • matita/mips64el has unsatisfiable dependency
  • matita/mipsel has unsatisfiable dependency
  • Updating matita introduces new bugs: #913606
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matita.html
  • 1464 days old (needed 5 days)
• php-patchwork-utf8 (- to 1.3.1-1)
  • Migration status for php-patchwork-utf8 (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-patchwork-utf8 introduces new bugs: #935246
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-patchwork-utf8.html
  • 1468 days old (needed 5 days)
• php-sabre-xml (- to 1.4.2-1)
  • Migration status for php-sabre-xml (- to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-sabre-xml introduces new bugs: #882949
  • autopkgtest for php-sabre-xml/1.4.2-1: amd64: Regression ♻ , arm64: Regression ♻
  • Build-Depends(-Arch): php-sabre-xml php-sabre-uri
  • Depends: php-sabre-xml php-sabre-uri
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-xml.html
  • 1468 days old (needed 5 days)
• graxxia (- to 1.0~20150714-2)
  • Migration status for graxxia (- to 1.0~20150714-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graxxia.html
  • 1469 days old (needed 5 days)
• mandrill (- to 1.0.57-1)
  • Migration status for mandrill (- to 1.0.57-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-mandrill/amd64 has unsatisfiable dependency
  • python-mandrill/i386 has unsatisfiable dependency
  • Updating mandrill introduces new bugs: #936988
  • Not built on buildd: arch all binaries uploaded by lfaraone, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mandrill.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1473 days old (needed 5 days)
• tldp (- to 0.7.13-1)
  • Migration status for tldp (- to 0.7.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tldp introduces new bugs: #867261
  • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tldp.html
  • 1474 days old (needed 5 days)
• pybloomfiltermmap (- to 0.3.15-0.1)
  • Migration status for pybloomfiltermmap (- to 0.3.15-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pybloomfiltermmap introduces new bugs: #937392
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pybloomfiltermmap.html
  • 1478 days old (needed 5 days)
• libblkmaker (- to 0.5.3-1)
  • Migration status for libblkmaker (- to 0.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libblkmaker introduces new bugs: #858377, #899568
  • Not built on buildd: arch amd64 binaries uploaded by onlyjob@member.fsf.org
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libblkmaker.html
  • 1501 days old (needed 5 days)
• ruby-graffiti (- to 2.3.1-1)
  • Migration status for ruby-graffiti (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ruby-graffiti introduces new bugs: #952016
  • Not built on buildd: arch all binaries uploaded by angdraug, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-graffiti.html
  • 1501 days old (needed 5 days)
• fizmo (- to 0.7.10-2)
  • Migration status for fizmo (- to 0.7.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fizmo introduces new bugs: #877015
  • Not built on buildd: arch all binaries uploaded by pmatthaei, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fizmo.html
  • 1503 days old (needed 5 days)
• php-pimple (- to 3.0.2-2)
  • Migration status for php-pimple (- to 3.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-pimple introduces new bugs: #816756, #882902
  • autopkgtest for php-pimple/3.0.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-pimple.html
  • 1509 days old (needed 5 days)
• jalview (- to 2.7.dfsg-5)
  • Migration status for jalview (- to 2.7.dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jalview introduces new bugs: #849025
  • Not built on buildd: arch all binaries uploaded by apo@gambaru.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jalview.html
  • 1510 days old (needed 5 days)
• php-services-weather (- to 1.4.7-4)
  • Migration status for php-services-weather (- to 1.4.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by sathieu, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-services-weather.html
  • 1512 days old (needed 5 days)
• album-data (- to 4.05-7)
  • Migration status for album-data (- to 4.05-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • album-data/amd64 has unsatisfiable dependency
  • album-data/i386 has unsatisfiable dependency
  • Updating album-data introduces new bugs: #908694
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1513 days old (needed 5 days)
• fvwm-crystal (- to 3.4.1+dfsg-1)
  • Migration status for fvwm-crystal (- to 3.4.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fvwm-crystal introduces new bugs: #945673
  • Not built on buildd: arch all binaries uploaded by bernat, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fvwm-crystal.html
  • 1527 days old (needed 5 days)
• hearse (- to 1.5-8.3)
  • Migration status for hearse (- to 1.5-8.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: hearse nethack (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hearse.html
  • 1527 days old (needed 5 days)
• php-net-ldap3 (- to 1.0.4-1)
  • Migration status for php-net-ldap3 (- to 1.0.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: php-net-ldap3 php-net-ldap2 (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-ldap3.html
  • 1527 days old (needed 5 days)
• php-numbers-words (- to 0.18.1-2)
  • Migration status for php-numbers-words (- to 0.18.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-numbers-words introduces new bugs: #882901
  • autopkgtest for php-numbers-words/0.18.1-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-numbers-words.html
  • 1527 days old (needed 5 days)
• hidrd (- to 0.2.0-12)
  • Migration status for hidrd (- to 0.2.0-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hidrd introduces new bugs: #822379, #853443
  • Not built on buildd: arch amd64 binaries uploaded by klee@mit.edu
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • missing build on armel
  • missing build on armhf
  • missing build on ppc64el
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hidrd.html
  • 1531 days old (needed 5 days)
• php-http-request2 (- to 2.3.0-1)
  • Migration status for php-http-request2 (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-http-request2 introduces new bugs: #882910
  • autopkgtest for php-http-request2/2.3.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-http-request2.html
  • 1531 days old (needed 5 days)
• php-sabre-uri (- to 1.1.0-1)
  • Migration status for php-sabre-uri (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-sabre-uri introduces new bugs: #882923
  • autopkgtest for php-sabre-uri/1.1.0-1: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-uri.html
  • 1531 days old (needed 5 days)
• php-sabre-http (- to 4.2.1-3)
  • Migration status for php-sabre-http (- to 4.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-sabre-http introduces new bugs: #882935
  • autopkgtest for php-sabre-http/4.2.1-3: amd64: Regression ♻ , arm64: Regression ♻
  • Build-Depends(-Arch): php-sabre-http php-sabre-uri
  • Depends: php-sabre-http php-sabre-event
  • Depends: php-sabre-http php-sabre-uri
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-http.html
  • 1537 days old (needed 5 days)
• edgar (- to 1.23-1)
  • Migration status for edgar (- to 1.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating edgar introduces new bugs: #832116
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/edgar.html
  • 1538 days old (needed 5 days)
• hash-slinger (- to 2.7-1)
  • Migration status for hash-slinger (- to 2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • hash-slinger/amd64 has unsatisfiable dependency
  • hash-slinger/arm64 has unsatisfiable dependency
  • hash-slinger/armel has unsatisfiable dependency
  • hash-slinger/armhf has unsatisfiable dependency
  • hash-slinger/i386 has unsatisfiable dependency
  • hash-slinger/mips64el has unsatisfiable dependency
  • hash-slinger/mipsel has unsatisfiable dependency
  • hash-slinger/ppc64el has unsatisfiable dependency
  • hash-slinger/s390x has unsatisfiable dependency
  • Updating hash-slinger introduces new bugs: #899533, #927132, #945653, #953372
  • Not built on buildd: arch amd64 binaries uploaded by ondrej
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hash-slinger.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1538 days old (needed 5 days)
• php-sabre-event (- to 3.0.0~as2.0.2-2)
  • Migration status for php-sabre-event (- to 3.0.0~as2.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-sabre-event introduces new bugs: #882915
  • autopkgtest for php-sabre-event/3.0.0~as2.0.2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-event.html
  • 1545 days old (needed 5 days)
• cclive (- to 0.9.3-0.1)
  • Migration status for cclive (- to 0.9.3-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • cclive/amd64 has unsatisfiable dependency
  • cclive/arm64 has unsatisfiable dependency
  • cclive/armel has unsatisfiable dependency
  • cclive/armhf has unsatisfiable dependency
  • cclive/i386 has unsatisfiable dependency
  • cclive/mips64el has unsatisfiable dependency
  • cclive/mipsel has unsatisfiable dependency
  • cclive/ppc64el has unsatisfiable dependency
  • cclive/s390x has unsatisfiable dependency
  • Updating cclive introduces new bugs: #914056, #953544
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cclive.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1557 days old (needed 5 days)
• ikvm (- to 8.1.5717.0+ds-1)
  • Migration status for ikvm (- to 8.1.5717.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ikvm introduces new bugs: #806624, #894353
  • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by directhex
  • Build-Depends(-Arch): ikvm nant
  • Build-Depends-Indep: ikvm openjdk-8
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ikvm.html
  • 1559 days old (needed 5 days)
• brian (- to 1.4.3-1)
  • Migration status for brian (- to 1.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-brian/amd64 has unsatisfiable dependency
  • python-brian/i386 has unsatisfiable dependency
  • Updating brian introduces new bugs: #876920, #896426, #936239
  • brian unsatisfiable Build-Depends(-Arch) on amd64: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on amd64: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on amd64: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
  • brian unsatisfiable Build-Depends(-Arch) on arm64: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on arm64: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on arm64: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx
  • brian unsatisfiable Build-Depends(-Arch) on armel: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on armel: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on armel: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on armel: python-sphinx
  • brian unsatisfiable Build-Depends(-Arch) on armhf: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on armhf: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on armhf: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx
  • brian unsatisfiable Build-Depends(-Arch) on i386: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on i386: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on i386: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on i386: python-sphinx
  • brian unsatisfiable Build-Depends(-Arch) on mips64el: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on mips64el: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on mips64el: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx
  • brian unsatisfiable Build-Depends(-Arch) on mipsel: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on mipsel: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on mipsel: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx
  • brian unsatisfiable Build-Depends(-Arch) on ppc64el: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on ppc64el: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on ppc64el: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx
  • brian unsatisfiable Build-Depends(-Arch) on s390x: python-matplotlib (>= 0.90.1)
  • brian unsatisfiable Build-Depends(-Arch) on s390x: python-scipy (>= 0.7.0)
  • brian unsatisfiable Build-Depends(-Arch) on s390x: python-sympy
  • brian unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx
  • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Not built on buildd: arch amd64 binaries uploaded by yoh
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/brian.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1562 days old (needed 5 days)
• coinst (- to 1.9.3-1)
  • Migration status for coinst (- to 1.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • coinst/mips64el has unsatisfiable dependency
  • coinst-viewer/mips64el has unsatisfiable dependency
  • coinst/mipsel has unsatisfiable dependency
  • coinst-viewer/mipsel has unsatisfiable dependency
  • coinst/ppc64el has unsatisfiable dependency
  • coinst-viewer/ppc64el has unsatisfiable dependency
  • coinst/s390x has unsatisfiable dependency
  • coinst-viewer/s390x has unsatisfiable dependency
  • Updating coinst introduces new bugs: #956556
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coinst.html
  • 1565 days old (needed 5 days)
• vim-ultisnips (- to 3.1-3)
  • Migration status for vim-ultisnips (- to 3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vim-ultisnips introduces new bugs: #938777
  • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-ultisnips.html
  • 1566 days old (needed 5 days)
• virt-goodies (- to 0.4-2.1)
  • Migration status for virt-goodies (- to 0.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • virt-goodies/amd64 has unsatisfiable dependency
  • virt-goodies/i386 has unsatisfiable dependency
  • Updating virt-goodies introduces new bugs: #938782
  • Not built on buildd: arch all binaries uploaded by agx, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virt-goodies.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1567 days old (needed 5 days)
• doc-linux-fr (- to 2013.01-3)
  • Migration status for doc-linux-fr (- to 2013.01-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating doc-linux-fr introduces new bugs: #880786, #906953, #910813
  • doc-linux-fr unsatisfiable Build-Depends-Indep on amd64: lynx-cur
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doc-linux-fr.html
  • 1568 days old (needed 5 days)
• obexpushd (- to 0.11.2-1.1)
  • Migration status for obexpushd (- to 0.11.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating obexpushd introduces new bugs: #906496
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obexpushd.html
  • 1570 days old (needed 5 days)
• ircp-tray (- to 0.7.6-1.2)
  • Migration status for ircp-tray (- to 0.7.6-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • ircp-tray/amd64 has unsatisfiable dependency
  • ircp-tray/arm64 has unsatisfiable dependency
  • ircp-tray/armel has unsatisfiable dependency
  • ircp-tray/armhf has unsatisfiable dependency
  • ircp-tray/i386 has unsatisfiable dependency
  • ircp-tray/mips64el has unsatisfiable dependency
  • ircp-tray/mipsel has unsatisfiable dependency
  • ircp-tray/ppc64el has unsatisfiable dependency
  • ircp-tray/s390x has unsatisfiable dependency
  • Updating ircp-tray introduces new bugs: #906474
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ircp-tray.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1572 days old (needed 5 days)
• literki (- to 0.0.0+20100113.git1da40724-1.2)
  • Migration status for literki (- to 0.0.0+20100113.git1da40724-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating literki introduces new bugs: #892344, #899846
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/literki.html
  • 1578 days old (needed 5 days)
• gatling (- to 0.13-6)
  • Migration status for gatling (- to 0.13-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gatling introduces new bugs: #868190
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gatling.html
  • 1593 days old (needed 5 days)
• ufoai-data (- to 2.5-1)
  • Migration status for ufoai-data (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by apo@gambaru.de, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): ufoai-data ufoai
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ufoai-data.html
  • 1597 days old (needed 5 days)
• ufoai-maps (- to 2.5-1)
  • Migration status for ufoai-maps (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by apo@gambaru.de, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): ufoai-maps ufoai
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ufoai-maps.html
  • 1597 days old (needed 5 days)
• sshcommand (- to 0~20160110.1~2795f65-1)
  • Migration status for sshcommand (- to 0~20160110.1~2795f65-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sshcommand introduces new bugs: #952298
  • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sshcommand.html
  • 1599 days old (needed 5 days)
• closure-linter (- to 2.3.19-1)
  • Migration status for closure-linter (- to 2.3.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • closure-linter/amd64 has unsatisfiable dependency
  • closure-linter/i386 has unsatisfiable dependency
  • Updating closure-linter introduces new bugs: #936309
  • closure-linter unsatisfiable Build-Depends(-Arch) on amd64: python-gflags
  • Not built on buildd: arch all binaries uploaded by gcs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/closure-linter.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1602 days old (needed 5 days)
• meta-unison (- to 2.48+2)
  • Migration status for meta-unison (- to 2.48+2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating meta-unison introduces new bugs: #946046
  • Not built on buildd: arch all binaries uploaded by mehdi, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meta-unison.html
  • 1602 days old (needed 5 days)
• libapp-perlrdf-command-query-perl (- to 0.004-2)
  • Migration status for libapp-perlrdf-command-query-perl (- to 0.004-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libapp-perlrdf-command-query-perl perlrdf
  • Depends: libapp-perlrdf-command-query-perl perlrdf
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapp-perlrdf-command-query-perl.html
  • 1612 days old (needed 5 days)
• pythia8 (- to 8.1.86-1.2)
  • Migration status for pythia8 (- to 8.1.86-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by tobi, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): pythia8 hepmc
  • Depends: pythia8 hepmc
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pythia8.html
  • 1612 days old (needed 5 days)
• tinyca (- to 0.7.5-6)
  • Migration status for tinyca (- to 0.7.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tinyca introduces new bugs: #912889
  • Not built on buildd: arch all binaries uploaded by scholler@fnb.tu-darmstadt.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinyca.html
  • 1612 days old (needed 5 days)
• googlefontdirectory-tools (- to 20120309.1-1.1)
  • Migration status for googlefontdirectory-tools (- to 20120309.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating googlefontdirectory-tools introduces new bugs: #936638
  • Impossible Depends: googlefontdirectory-tools -> python-fontforge/1:20170731~dfsg-2/amd64
  • Impossible Depends: googlefontdirectory-tools -> python-fontforge/1:20170731~dfsg-2/i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/googlefontdirectory-tools.html
  • 1616 days old (needed 5 days)
• cduce (- to 0.6.0-5)
  • Migration status for cduce (- to 0.6.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • cduce/amd64 has unsatisfiable dependency
  • cduce/arm64 has unsatisfiable dependency
  • cduce/armel has unsatisfiable dependency
  • cduce/armhf has unsatisfiable dependency
  • cduce/i386 has unsatisfiable dependency
  • Updating cduce introduces new bugs: #878983
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/cduce.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1617 days old (needed 5 days)
• git-notifier (- to 1:0.6-25-1)
  • Migration status for git-notifier (- to 1:0.6-25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating git-notifier introduces new bugs: #945677
  • Not built on buildd: arch all binaries uploaded by edmonds, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-notifier.html
  • 1621 days old (needed 5 days)
• pinta (- to 1.6-2)
  • Migration status for pinta (- to 1.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pinta introduces new bugs: #877106
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pinta.html
  • 1625 days old (needed 5 days)
• py-asterisk (- to 0.5.3-1.1)
  • Migration status for py-asterisk (- to 0.5.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating py-asterisk introduces new bugs: #937387
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-asterisk.html
  • 1625 days old (needed 5 days)
• dvcs-autosync (- to 0.5+nmu1)
  • Migration status for dvcs-autosync (- to 0.5+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • dvcs-autosync/amd64 has unsatisfiable dependency
  • dvcs-autosync/i386 has unsatisfiable dependency
  • Updating dvcs-autosync introduces new bugs: #936459
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvcs-autosync.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1626 days old (needed 5 days)
• ntlmaps (- to 0.9.9.0.1-11.5)
  • Migration status for ntlmaps (- to 0.9.9.0.1-11.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ntlmaps introduces new bugs: #943133
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntlmaps.html
  • 1626 days old (needed 5 days)
• libfile-rsyncp-perl (- to 0.74-2.1)
  • Migration status for libfile-rsyncp-perl (- to 0.74-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libfile-rsyncp-perl introduces new bugs: #945242
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfile-rsyncp-perl.html
  • 1628 days old (needed 5 days)
• npgsql (- to 2.2.7+dfsg3-1)
  • Migration status for npgsql (- to 2.2.7+dfsg3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating npgsql introduces new bugs: #842693
  • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/npgsql.html
  • 1628 days old (needed 5 days)
• fsharp (- to 4.0.0.4+dfsg2-2)
  • Migration status for fsharp (- to 4.0.0.4+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fsharp introduces new bugs: #905449
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/fsharp.html
  • autopkgtest for fsharp/4.0.0.4+dfsg2-2: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Additional info:
  • 1630 days old (needed 5 days)
• courier-filter-perl (- to 0.200+ds-4)
  • Migration status for courier-filter-perl (- to 0.200+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • autopkgtest for courier-filter-perl/0.200+ds-4: amd64: Regression ♻ , arm64: Regression ♻
  • Depends: courier-filter-perl courier
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-filter-perl.html
  • 1642 days old (needed 5 days)
• python-ntlm (- to 1.1.0-1)
  • Migration status for python-ntlm (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-ntlm introduces new bugs: #937959
  • Not built on buildd: arch all binaries uploaded by gcs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ntlm.html
  • 1650 days old (needed 5 days)
• monobristol (- to 0.60.3-3)
  • Migration status for monobristol (- to 0.60.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating monobristol introduces new bugs: #881911
  • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monobristol.html
  • 1653 days old (needed 5 days)
• apt-clone (- to 0.4.1)
  • Migration status for apt-clone (- to 0.4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating apt-clone introduces new bugs: #952293
  • autopkgtest for apt-clone/0.4.1: amd64: Regression ♻ , arm64: Regression ♻
  • Not built on buildd: arch all binaries uploaded by mvo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-clone.html
  • 1657 days old (needed 5 days)
• servefile (- to 0.4.4-1)
  • Migration status for servefile (- to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating servefile introduces new bugs: #935209
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/servefile.html
  • 1659 days old (needed 5 days)
• sphinx-patchqueue (- to 0.5.0-2)
  • Migration status for sphinx-patchqueue (- to 0.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-sphinx-patchqueue/amd64 has unsatisfiable dependency
  • python-sphinx-patchqueue/i386 has unsatisfiable dependency
  • Updating sphinx-patchqueue introduces new bugs: #938544
  • sphinx-patchqueue unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
  • 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-patchqueue.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1662 days old (needed 5 days)
• broctl (- to 1.4-1)
  • Migration status for broctl (- to 1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating broctl introduces new bugs: #936241
  • broctl unsatisfiable Build-Depends(-Arch) on amd64: python-subnettree
  • Not built on buildd: arch all binaries uploaded by bengen, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): broctl bro
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/broctl.html
  • 1671 days old (needed 5 days)
• denyhosts (- to 2.10-2)
  • Migration status for denyhosts (- to 2.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating denyhosts introduces new bugs: #802917, #936385
  • Not built on buildd: arch all binaries uploaded by mnencia, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/denyhosts.html
  • 1680 days old (needed 5 days)
• vdr-plugin-infosatepg (- to 0.0.12-6)
  • Migration status for vdr-plugin-infosatepg (- to 0.0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • vdr-plugin-infosatepg/amd64 has unsatisfiable dependency
  • vdr-plugin-infosatepg/arm64 has unsatisfiable dependency
  • vdr-plugin-infosatepg/armel has unsatisfiable dependency
  • vdr-plugin-infosatepg/armhf has unsatisfiable dependency
  • vdr-plugin-infosatepg/i386 has unsatisfiable dependency
  • vdr-plugin-infosatepg/mips64el has unsatisfiable dependency
  • vdr-plugin-infosatepg/mipsel has unsatisfiable dependency
  • vdr-plugin-infosatepg/ppc64el has unsatisfiable dependency
  • vdr-plugin-infosatepg/s390x has unsatisfiable dependency
  • Updating vdr-plugin-infosatepg introduces new bugs: #872487
  • Not built on buildd: arch amd64 binaries uploaded by etobi
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vdr-plugin-infosatepg.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1709 days old (needed 5 days)
• vdr-plugin-remoteosd (- to 1.0.0-5)
  • Migration status for vdr-plugin-remoteosd (- to 1.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • vdr-plugin-remoteosd/amd64 has unsatisfiable dependency
  • vdr-plugin-remoteosd/arm64 has unsatisfiable dependency
  • vdr-plugin-remoteosd/armel has unsatisfiable dependency
  • vdr-plugin-remoteosd/armhf has unsatisfiable dependency
  • vdr-plugin-remoteosd/i386 has unsatisfiable dependency
  • vdr-plugin-remoteosd/mips64el has unsatisfiable dependency
  • vdr-plugin-remoteosd/mipsel has unsatisfiable dependency
  • vdr-plugin-remoteosd/ppc64el has unsatisfiable dependency
  • vdr-plugin-remoteosd/s390x has unsatisfiable dependency
  • Updating vdr-plugin-remoteosd introduces new bugs: #872495
  • Not built on buildd: arch amd64 binaries uploaded by etobi
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vdr-plugin-remoteosd.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1709 days old (needed 5 days)
• libmodule-starter-plugin-cgiapp-perl (- to 0.44-1)
  • Migration status for libmodule-starter-plugin-cgiapp-perl (- to 0.44-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libmodule-starter-plugin-cgiapp-perl introduces new bugs: #952169
  • Not built on buildd: arch all binaries uploaded by jaldhar, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmodule-starter-plugin-cgiapp-perl.html
  • 1711 days old (needed 5 days)
• doxypy (- to 0.4.2-1.1)
  • Migration status for doxypy (- to 0.4.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating doxypy introduces new bugs: #942999
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doxypy.html
  • 1726 days old (needed 5 days)
• purity-ng (- to 0.2.0-2.1)
  • Migration status for purity-ng (- to 0.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating purity-ng introduces new bugs: #937378
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purity-ng.html
  • 1727 days old (needed 5 days)
• cutter (- to 1.04-1)
  • Migration status for cutter (- to 1.04-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cutter introduces new bugs: #446343
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cutter.html
  • 1730 days old (needed 5 days)
• libusbtc08 (- to 1.7.2-5)
  • Migration status for libusbtc08 (- to 1.7.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libusbtc08 introduces new bugs: #811980
  • Not built on buildd: arch amd64 binaries uploaded by maxy
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libusbtc08.html
  • 1736 days old (needed 5 days)
• openopt (- to 0.38+svn1589-1.1)
  • Migration status for openopt (- to 0.38+svn1589-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-openopt/amd64 has unsatisfiable dependency
  • python-openopt/i386 has unsatisfiable dependency
  • Updating openopt introduces new bugs: #937209
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openopt.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1736 days old (needed 5 days)
• samizdat (- to 0.7.0-2)
  • Migration status for samizdat (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by miguel@miguel.cc, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): samizdat ruby-graffiti
  • Depends: samizdat ruby-graffiti
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/samizdat.html
  • 1741 days old (needed 5 days)
• woof (- to 20091227-2.1)
  • Migration status for woof (- to 20091227-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating woof introduces new bugs: #943268
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/woof.html
  • 1741 days old (needed 5 days)
• opencaster (- to 3.2.2+dfsg-1.1)
  • Migration status for opencaster (- to 3.2.2+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating opencaster introduces new bugs: #937194
  • opencaster unsatisfiable Build-Depends(-Arch) on amd64: python-dateutil
  • opencaster unsatisfiable Build-Depends(-Arch) on arm64: python-dateutil
  • opencaster unsatisfiable Build-Depends(-Arch) on armel: python-dateutil
  • opencaster unsatisfiable Build-Depends(-Arch) on armhf: python-dateutil
  • opencaster unsatisfiable Build-Depends(-Arch) on i386: python-dateutil
  • opencaster unsatisfiable Build-Depends(-Arch) on mips64el: python-dateutil
  • opencaster unsatisfiable Build-Depends(-Arch) on mipsel: python-dateutil
  • opencaster unsatisfiable Build-Depends(-Arch) on ppc64el: python-dateutil
  • opencaster unsatisfiable Build-Depends(-Arch) on s390x: python-dateutil
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencaster.html
  • 1742 days old (needed 5 days)
• pynifti (- to 0.20100607.1-4.1)
  • Migration status for pynifti (- to 0.20100607.1-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pynifti introduces new bugs: #937490
  • pynifti unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
  • pynifti unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx
  • pynifti unsatisfiable Build-Depends(-Arch) on armel: python-sphinx
  • pynifti unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx
  • pynifti unsatisfiable Build-Depends(-Arch) on i386: python-sphinx
  • pynifti unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx
  • pynifti unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx
  • pynifti unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx
  • pynifti unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynifti.html
  • 1744 days old (needed 5 days)
• opennebula-context (- to 4.14.0-1)
  • Migration status for opennebula-context (- to 4.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating opennebula-context introduces new bugs: #899908
  • 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:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opennebula-context.html
  • 1745 days old (needed 5 days)
• python-pysqlite2 (- to 2.7.0-1)
  • Migration status for python-pysqlite2 (- to 2.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-pysqlite2 introduces new bugs: #938099
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 0.6.1)
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx (>= 0.6.1)
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on armel: python-sphinx (>= 0.6.1)
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx (>= 0.6.1)
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on i386: python-sphinx (>= 0.6.1)
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx (>= 0.6.1)
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx (>= 0.6.1)
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx (>= 0.6.1)
  • python-pysqlite2 unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx (>= 0.6.1)
  • Not built on buildd: arch all binaries uploaded by joel, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pysqlite2.html
  • 1746 days old (needed 5 days)
• smtm (- to 1.6.11)
  • Migration status for smtm (- to 1.6.11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by edd, a new source-only upload is needed to allow migration
  • Build-Depends-Indep: smtm finance-yahooquote
  • Depends: smtm finance-yahooquote
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smtm.html
  • 1746 days old (needed 5 days)
• lua-apr (- to 0.23.2.dfsg-4)
  • Migration status for lua-apr (- to 0.23.2.dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lua-apr introduces new bugs: #935271
  • Not built on buildd: arch amd64 binaries uploaded by gareuselesinge
  • Not built on buildd: arch all binaries uploaded by gareuselesinge, a new source-only upload is needed to allow migration
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-apr.html
  • 1748 days old (needed 5 days)
• mirage (- to 0.9.5.2-1)
  • Migration status for mirage (- to 0.9.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • mirage/amd64 has unsatisfiable dependency
  • mirage/arm64 has unsatisfiable dependency
  • mirage/armel has unsatisfiable dependency
  • mirage/armhf has unsatisfiable dependency
  • mirage/i386 has unsatisfiable dependency
  • mirage/mips64el has unsatisfiable dependency
  • mirage/mipsel has unsatisfiable dependency
  • mirage/ppc64el has unsatisfiable dependency
  • mirage/s390x has unsatisfiable dependency
  • Updating mirage introduces new bugs: #885353, #937052
  • mirage unsatisfiable Build-Depends(-Arch) on amd64: python-gtk2-dev
  • mirage unsatisfiable Build-Depends(-Arch) on arm64: python-gtk2-dev
  • mirage unsatisfiable Build-Depends(-Arch) on armel: python-gtk2-dev
  • mirage unsatisfiable Build-Depends(-Arch) on armhf: python-gtk2-dev
  • mirage unsatisfiable Build-Depends(-Arch) on i386: python-gtk2-dev
  • mirage unsatisfiable Build-Depends(-Arch) on mips64el: python-gtk2-dev
  • mirage unsatisfiable Build-Depends(-Arch) on mipsel: python-gtk2-dev
  • mirage unsatisfiable Build-Depends(-Arch) on ppc64el: python-gtk2-dev
  • mirage unsatisfiable Build-Depends(-Arch) on s390x: python-gtk2-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mirage.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1748 days old (needed 5 days)
• python-cyclone (- to 1.1-2)
  • Migration status for python-cyclone (- to 1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-cyclone/amd64 has unsatisfiable dependency
  • python-cyclone/i386 has unsatisfiable dependency
  • Updating python-cyclone introduces new bugs: #937682
  • python-cyclone unsatisfiable Build-Depends(-Arch) on amd64: python-twisted
  • Not built on buildd: arch all binaries uploaded by lunar, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cyclone.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1754 days old (needed 5 days)
• mrtg-rrd (- to 0.7-5.1)
  • Migration status for mrtg-rrd (- to 0.7-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mrtg-rrd introduces new bugs: #799097
  • Not built on buildd: arch all binaries uploaded by dmn, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrtg-rrd.html
  • 1761 days old (needed 5 days)
• tcpcopy (- to 0.6.3-2.1)
  • Migration status for tcpcopy (- to 0.6.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tcpcopy introduces new bugs: #835591, #952570
  • Impossible Build-Depends(-Arch): tcpcopy -> iptables-dev/1.8.3-2/amd64
  • Impossible Build-Depends(-Arch): tcpcopy -> iptables-dev/1.8.3-2/armel
  • Impossible Build-Depends(-Arch): tcpcopy -> iptables-dev/1.8.3-2/armhf
  • Impossible Build-Depends(-Arch): tcpcopy -> iptables-dev/1.8.3-2/i386
  • Impossible Build-Depends(-Arch): tcpcopy -> iptables-dev/1.8.3-2/mips64el
  • Impossible Build-Depends(-Arch): tcpcopy -> iptables-dev/1.8.3-2/mipsel
  • Impossible Build-Depends(-Arch): tcpcopy -> iptables-dev/1.8.3-2/ppc64el
  • Impossible Build-Depends(-Arch): tcpcopy -> iptables-dev/1.8.3-2/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcpcopy.html
  • 1765 days old (needed 5 days)
• angband-audio (- to 1:3.1.0-1)
  • Migration status for angband-audio (- to 1:3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating angband-audio introduces new bugs: #793668
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 1770 days old (needed 5 days)
• syslinux-themes-debian (- to 12-4)
  • Migration status for syslinux-themes-debian (- to 12-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating syslinux-themes-debian introduces new bugs: #924221
  • Not built on buildd: arch all binaries uploaded by debian@abeckmann.de, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syslinux-themes-debian.html
  • uninstallable on arch arm64, not running autopkgtest there
  • 1775 days old (needed 5 days)
• yap (- to 6.2.2-6)
  • Migration status for yap (- to 6.2.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating yap introduces new bugs: #877034
  • Impossible Depends: yap -> libreadline7/7.0-5/i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yap.html
  • Required age reduced by 3 days because of autopkgtest
  • 1779 days old (needed 2 days)
• rainbow (- to 0.8.7-2)
  • Migration status for rainbow (- to 0.8.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating rainbow introduces new bugs: #938331
  • Not built on buildd: arch all binaries uploaded by lfaraone, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rainbow.html
  • 1782 days old (needed 5 days)
• zyne (- to 0.1.2-2)
  • Migration status for zyne (- to 0.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • zyne/amd64 has unsatisfiable dependency
  • zyne/i386 has unsatisfiable dependency
  • Updating zyne introduces new bugs: #807648, #938923
  • Not built on buildd: arch all binaries uploaded by tiago, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zyne.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1784 days old (needed 5 days)
• monotone-viz (- to 1.0.2-4)
  • Migration status for monotone-viz (- to 1.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • monotone-viz/mips64el has unsatisfiable dependency
  • monotone-viz/mipsel has unsatisfiable dependency
  • Updating monotone-viz introduces new bugs: #913607
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monotone-viz.html
  • 1785 days old (needed 5 days)
• lava-coordinator (- to 0.1.7-1)
  • Migration status for lava-coordinator (- to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • lava-coordinator/amd64 has unsatisfiable dependency
  • lava-coordinator/i386 has unsatisfiable dependency
  • Updating lava-coordinator introduces new bugs: #936818
  • Not built on buildd: arch all binaries uploaded by codehelp, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lava-coordinator.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1787 days old (needed 5 days)
• cgminer (- to 4.9.2-1)
  • Migration status for cgminer (- to 4.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating cgminer introduces new bugs: #899467, #900929
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cgminer.html
  • 1798 days old (needed 5 days)
• libxml-atom-microformats-perl (- to 0.004-3)
  • Migration status for libxml-atom-microformats-perl (- to 0.004-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by gregoa, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libxml-atom-microformats-perl librdf-rdfa-parser-perl
  • Depends: libxml-atom-microformats-perl libhtml-microformats-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxml-atom-microformats-perl.html
  • 1800 days old (needed 5 days)
• vncterm (- to 0.9.10-2)
  • Migration status for vncterm (- to 0.9.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vncterm introduces new bugs: #898453
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vncterm.html
  • 1813 days old (needed 5 days)
• pglistener (- to 4)
  • Migration status for pglistener (- to 4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • pglistener/amd64 has unsatisfiable dependency
  • pglistener/i386 has unsatisfiable dependency
  • Updating pglistener introduces new bugs: #943205
  • Not built on buildd: arch all binaries uploaded by tfheen, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pglistener.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 1814 days old (needed 5 days)
• libtitanium-perl (- to 1.04-4)
  • Migration status for libtitanium-perl (- to 1.04-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by ntyni, a new source-only upload is needed to allow migration
  • Depends: libtitanium-perl libmodule-starter-plugin-cgiapp-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtitanium-perl.html
  • Required age reduced by 3 days because of autopkgtest
  • 1818 days old (needed 2 days)
• flup (- to 1.0.2-5)
  • Migration status for flup (- to 1.0.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating flup introduces new bugs: #936535
  • Not built on buildd: arch all binaries uploaded by tmancill, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flup.html
  • 1829 days old (needed 5 days)
• python-sqlite (- to 1.0.1-12)
  • Migration status for python-sqlite (- to 1.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-sqlite introduces new bugs: #938192
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sqlite.html
  • 1834 days old (needed 5 days)
• gprename (- to 20140325-1)
  • Migration status for gprename (- to 20140325-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gprename introduces new bugs: #912880
  • Not built on buildd: arch all binaries uploaded by rmayorga, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gprename.html
  • 1847 days old (needed 5 days)
• finance-yahooquote (- to 0.25)
  • Migration status for finance-yahooquote (- to 0.25): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating finance-yahooquote introduces new bugs: #882305
  • Not built on buildd: arch all binaries uploaded by edd, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/finance-yahooquote.html
  • 1855 days old (needed 5 days)
• brebis (- to 0.10-1)
  • Migration status for brebis (- to 0.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating brebis introduces new bugs: #952354
  • Not built on buildd: arch all binaries uploaded by chaica@ohmytux.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/brebis.html
  • 1937 days old (needed 5 days)
• libapache2-mod-auth-pgsql (- to 2.0.3-6.1)
  • Migration status for libapache2-mod-auth-pgsql (- to 2.0.3-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libapache2-mod-auth-pgsql introduces new bugs: #947039
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-auth-pgsql.html
  • 1957 days old (needed 5 days)
• lightyears (- to 1.4-2)
  • Migration status for lightyears (- to 1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lightyears introduces new bugs: #936945, #942622
  • Not built on buildd: arch all binaries uploaded by sgevatter, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lightyears.html
  • 1984 days old (needed 5 days)
• libwebcam (- to 0.2.4-1.1)
  • Migration status for libwebcam (- to 0.2.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libwebcam introduces new bugs: #733094
  • Not built on buildd: arch all binaries uploaded by kraai, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwebcam.html
  • 2005 days old (needed 5 days)
• el-get (- to 3.1-1.1)
  • Migration status for el-get (- to 3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating el-get introduces new bugs: #912364, #916857
  • Not built on buildd: arch all binaries uploaded by eriberto, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/el-get.html
  • 2013 days old (needed 5 days)
• pdmenu (- to 1.3.4)
  • Migration status for pdmenu (- to 1.3.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pdmenu introduces new bugs: #862786
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdmenu.html
  • 2028 days old (needed 5 days)
• python-versuchung (- to 1.1-3)
  • Migration status for python-versuchung (- to 1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-versuchung introduces new bugs: #938248
  • python-versuchung unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
  • Not built on buildd: arch all binaries uploaded by christoph, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-versuchung.html
  • 2033 days old (needed 5 days)
• libmonitoring-availability-perl (- to 0.46-1)
  • Migration status for libmonitoring-availability-perl (- to 0.46-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libmonitoring-availability-perl introduces new bugs: #839432
  • Not built on buildd: arch all binaries uploaded by formorer, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmonitoring-availability-perl.html
  • 2041 days old (needed 5 days)
• srg (- to 1.3.6-2)
  • Migration status for srg (- to 1.3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating srg introduces new bugs: #846449, #912072
  • Not built on buildd: arch amd64 binaries uploaded by mattb
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Not built on buildd: arch ppc64el binaries uploaded by aba
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/srg.html
  • 2043 days old (needed 5 days)
• cuyo (- to 2.0.0brl1-3)
  • Migration status for cuyo (- to 2.0.0brl1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by brlink, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cuyo.html
  • 2048 days old (needed 5 days)
• piggyphoto (- to 0.1dev-git20141014)
  • Migration status for piggyphoto (- to 0.1dev-git20141014): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating piggyphoto introduces new bugs: #937288
  • Not built on buildd: arch all binaries uploaded by aigarius, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/piggyphoto.html
  • 2051 days old (needed 5 days)
• pam-pgsql (- to 0.7.3.2-1)
  • Migration status for pam-pgsql (- to 0.7.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pam-pgsql introduces new bugs: #863650
  • Not built on buildd: arch amd64 binaries uploaded by jandd
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-pgsql.html
  • 2060 days old (needed 5 days)
• googleearth-package (- to 1.2.2)
  • Migration status for googleearth-package (- to 1.2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating googleearth-package introduces new bugs: #881580
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 2062 days old (needed 5 days)
• arriero (- to 0.6-1)
  • Migration status for arriero (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • arriero/amd64 has unsatisfiable dependency
  • arriero/i386 has unsatisfiable dependency
  • Updating arriero introduces new bugs: #904118, #936150
  • Not built on buildd: arch all binaries uploaded by marga, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/arriero.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 2090 days old (needed 5 days)
• archivemail (- to 0.9.0-1.1)
  • Migration status for archivemail (- to 0.9.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating archivemail introduces new bugs: #936146
  • Not built on buildd: arch all binaries uploaded by jmtd, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/archivemail.html
  • 2100 days old (needed 5 days)
• emscripten (- to 1.22.1-1)
  • Migration status for emscripten (- to 1.22.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating emscripten introduces new bugs: #775147, #803028, #809997, #817810, #851109, #936481, #939477
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/emscripten.html
  • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Not built on buildd: arch all binaries uploaded by sylvestre, a new source-only upload is needed to allow migration
  • Additional info:
  • 2106 days old (needed 5 days)
• adanaxisgpl (- to 1.2.5.dfsg.1-6)
  • Migration status for adanaxisgpl (- to 1.2.5.dfsg.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating adanaxisgpl introduces new bugs: #697615
  • Not built on buildd: arch all binaries uploaded by Vincentc1208@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adanaxisgpl.html
  • 2142 days old (needed 5 days)
• primesense-nite-nonfree (- to 0.1.1)
  • Migration status for primesense-nite-nonfree (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating primesense-nite-nonfree introduces new bugs: #771187
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 2150 days old (needed 5 days)
• python-neuroshare (- to 0.9.2-1)
  • Migration status for python-neuroshare (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • python-neuroshare/amd64 has unsatisfiable dependency
  • python-neuroshare/arm64 has unsatisfiable dependency
  • python-neuroshare/armel has unsatisfiable dependency
  • python-neuroshare/armhf has unsatisfiable dependency
  • python-neuroshare/i386 has unsatisfiable dependency
  • python-neuroshare/mips64el has unsatisfiable dependency
  • python-neuroshare/mipsel has unsatisfiable dependency
  • python-neuroshare/ppc64el has unsatisfiable dependency
  • python-neuroshare/s390x has unsatisfiable dependency
  • Updating python-neuroshare introduces new bugs: #937945
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on amd64: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 1.0.7+dfsg)
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on arm64: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx (>= 1.0.7+dfsg)
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on armel: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on armel: python-sphinx (>= 1.0.7+dfsg)
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on armhf: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx (>= 1.0.7+dfsg)
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on i386: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on i386: python-sphinx (>= 1.0.7+dfsg)
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on mips64el: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx (>= 1.0.7+dfsg)
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on mipsel: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx (>= 1.0.7+dfsg)
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on ppc64el: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx (>= 1.0.7+dfsg)
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on s390x: python-h5py
  • python-neuroshare unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx (>= 1.0.7+dfsg)
  • Not built on buildd: arch all binaries uploaded by mih, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-neuroshare.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 2150 days old (needed 5 days)
• snetz (- to 0.1-1)
  • Migration status for snetz (- to 0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating snetz introduces new bugs: #943275
  • Not built on buildd: arch all binaries uploaded by dererk, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snetz.html
  • 2168 days old (needed 5 days)
• libhtml-html5-microdata-parser-perl (- to 0.100-2)
  • Migration status for libhtml-html5-microdata-parser-perl (- to 0.100-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libhtml-html5-microdata-parser-perl libhtml-html5-parser-perl
  • Depends: libhtml-html5-microdata-parser-perl libhtml-html5-parser-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhtml-html5-microdata-parser-perl.html
  • 2179 days old (needed 5 days)
• libhtml-html5-outline-perl (- to 0.006-2)
  • Migration status for libhtml-html5-outline-perl (- to 0.006-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libhtml-html5-outline-perl libhtml-html5-parser-perl
  • Depends: libhtml-html5-outline-perl libhtml-html5-parser-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhtml-html5-outline-perl.html
  • 2179 days old (needed 5 days)
• redmine-recaptcha (- to 0.1.0+git20121018-3)
  • Migration status for redmine-recaptcha (- to 0.1.0+git20121018-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating redmine-recaptcha introduces new bugs: #830916, #876621, #925269
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/redmine-recaptcha.html
  • Not built on buildd: arch all binaries uploaded by ender, a new source-only upload is needed to allow migration
  • Additional info:
  • 2179 days old (needed 5 days)
• crossfire-maps (- to 1.71.0-1)
  • Migration status for crossfire-maps (- to 1.71.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating crossfire-maps introduces new bugs: #936345
  • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crossfire-maps.html
  • 2205 days old (needed 5 days)
• scheme2c (- to 2012.10.14-1)
  • Migration status for scheme2c (- to 2012.10.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating scheme2c introduces new bugs: #778111
  • Not built on buildd: arch amd64 binaries uploaded by bap
  • Not built on buildd: arch all binaries uploaded by bap, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scheme2c.html
  • 2220 days old (needed 5 days)
• mingw-ocaml (- to 4.01.0~20140328-1)
  • Migration status for mingw-ocaml (- to 4.01.0~20140328-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mingw-ocaml introduces new bugs: #924764, #924816
  • Not built on buildd: arch all binaries uploaded by toots, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mingw-ocaml.html
  • uninstallable on arch arm64, not running autopkgtest there
  • 2251 days old (needed 5 days)
• libdispatch (- to 0~svn197-3.3)
  • Migration status for libdispatch (- to 0~svn197-3.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): libdispatch libpthread-workqueue (not considered)
  • Depends: libdispatch libpthread-workqueue (not considered)
  • Invalidated by build-dependency
  • Invalidated by dependency
  • Depends: libdispatch libkqueue
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdispatch.html
  • 2259 days old (needed 5 days)
• gettext-lint (- to 0.4-2.1)
  • Migration status for gettext-lint (- to 0.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gettext-lint introduces new bugs: #943098
  • Not built on buildd: arch all binaries uploaded by eric, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gettext-lint.html
  • 2265 days old (needed 5 days)
• am-utils (- to 6.2+rc20110530-3.2)
  • Migration status for am-utils (- to 6.2+rc20110530-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating am-utils introduces new bugs: #839785, #889070, #889148, #959451
  • Not built on buildd: arch all binaries uploaded by eric, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): am-utils linux
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/am-utils.html
  • 2268 days old (needed 5 days)
• libpthread-workqueue (- to 0.9.1-1)
  • Migration status for libpthread-workqueue (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libpthread-workqueue introduces new bugs: #835107
  • Not built on buildd: arch amd64 binaries uploaded by rbalint
  • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpthread-workqueue.html
  • 2272 days old (needed 5 days)
• fceux (- to 2.2.2+dfsg0-1)
  • Migration status for fceux (- to 2.2.2+dfsg0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating fceux introduces new bugs: #880770, #900599
  • fceux unsatisfiable Build-Depends(-Arch) on amd64: libgd2-xpm-dev
  • fceux unsatisfiable Build-Depends(-Arch) on arm64: libgd2-xpm-dev
  • fceux unsatisfiable Build-Depends(-Arch) on armel: libgd2-xpm-dev
  • fceux unsatisfiable Build-Depends(-Arch) on armhf: libgd2-xpm-dev
  • fceux unsatisfiable Build-Depends(-Arch) on i386: libgd2-xpm-dev
  • fceux unsatisfiable Build-Depends(-Arch) on mips64el: libgd2-xpm-dev
  • fceux unsatisfiable Build-Depends(-Arch) on mipsel: libgd2-xpm-dev
  • fceux unsatisfiable Build-Depends(-Arch) on ppc64el: libgd2-xpm-dev
  • fceux unsatisfiable Build-Depends(-Arch) on s390x: libgd2-xpm-dev
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fceux.html
  • 2278 days old (needed 5 days)
• prctl (- to 1.6-1)
  • Migration status for prctl (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating prctl introduces new bugs: #934482
  • Not built on buildd: arch amd64 binaries uploaded by khalid
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prctl.html
  • 2281 days old (needed 5 days)
• towitoko (- to 2.0.7-9)
  • Migration status for towitoko (- to 2.0.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating towitoko introduces new bugs: #903937, #903940
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/towitoko.html
  • 2310 days old (needed 5 days)
• couriergrey (- to 0.3.2-5)
  • Migration status for couriergrey (- to 0.3.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Depends: couriergrey courier (not considered)
  • Invalidated by dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/couriergrey.html
  • 2322 days old (needed 5 days)
• libapache2-mod-ruid2 (- to 0.9.8-3)
  • Migration status for libapache2-mod-ruid2 (- to 0.9.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libapache2-mod-ruid2 introduces new bugs: #866395
  • Not built on buildd: arch amd64 binaries uploaded by kobold
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-ruid2.html
  • 2375 days old (needed 5 days)
• tumgreyspf (- to 1.36-4.1)
  • Migration status for tumgreyspf (- to 1.36-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • tumgreyspf/amd64 has unsatisfiable dependency
  • tumgreyspf/i386 has unsatisfiable dependency
  • Updating tumgreyspf introduces new bugs: #927137, #938724
  • Not built on buildd: arch all binaries uploaded by kitterman, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tumgreyspf.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 2390 days old (needed 5 days)
• node-carto (- to 0.9.5-2)
  • Migration status for node-carto (- to 0.9.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating node-carto introduces new bugs: #826560
  • Not built on buildd: arch all binaries uploaded by kapouer@melix.org, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-carto.html
  • 2397 days old (needed 5 days)
• libpoe-loop-event-perl (- to 1.305-1)
  • Migration status for libpoe-loop-event-perl (- to 1.305-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libpoe-loop-event-perl introduces new bugs: #846667
  • Not built on buildd: arch all binaries uploaded by fsfs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpoe-loop-event-perl.html
  • 2398 days old (needed 5 days)
• hfsprogs (- to 332.25-11)
  • Migration status for hfsprogs (- to 332.25-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating hfsprogs introduces new bugs: #666707
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hfsprogs.html
  • 2408 days old (needed 5 days)
• ifupdown-multi (- to 0.1.1)
  • Migration status for ifupdown-multi (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating ifupdown-multi introduces new bugs: #943060
  • Not built on buildd: arch all binaries uploaded by edmonds, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifupdown-multi.html
  • 2412 days old (needed 5 days)
• sortsmill-tools (- to 0.4-2)
  • Migration status for sortsmill-tools (- to 0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sortsmill-tools introduces new bugs: #938516
  • Not built on buildd: arch all binaries uploaded by pabs, a new source-only upload is needed to allow migration
  • Impossible Depends: sortsmill-tools -> python-fontforge/1:20170731~dfsg-2/amd64
  • Impossible Depends: sortsmill-tools -> python-fontforge/1:20170731~dfsg-2/i386
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sortsmill-tools.html
  • 2436 days old (needed 5 days)
• kytea (- to 0.4.6+dfsg-2)
  • Migration status for kytea (- to 0.4.6+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libkytea0/amd64 has unsatisfiable dependency
  • libkytea0/arm64 has unsatisfiable dependency
  • libkytea0/armel has unsatisfiable dependency
  • libkytea0/armhf has unsatisfiable dependency
  • libkytea0/i386 has unsatisfiable dependency
  • libkytea0/mips64el has unsatisfiable dependency
  • libkytea0/mipsel has unsatisfiable dependency
  • libkytea0/ppc64el has unsatisfiable dependency
  • libkytea0/s390x has unsatisfiable dependency
  • Updating kytea introduces new bugs: #799805
  • Not built on buildd: arch amd64 binaries uploaded by osamu
  • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/kytea.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 2446 days old (needed 5 days)
• perlrdf (- to 0.004-3)
  • Migration status for perlrdf (- to 0.004-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): perlrdf librdf-rdfa-parser-perl
  • Depends: perlrdf librdf-rdfa-parser-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perlrdf.html
  • 2462 days old (needed 5 days)
• zeroc-ice-manual (- to 3.5.0-1)
  • Migration status for zeroc-ice-manual (- to 3.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating zeroc-ice-manual introduces new bugs: #864472
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 2475 days old (needed 5 days)
• mozplugger (- to 1.14.5-2)
  • Migration status for mozplugger (- to 1.14.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mozplugger introduces new bugs: #907767
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mozplugger.html
  • 2476 days old (needed 5 days)
• libhtml-embedded-turtle-perl (- to 0.404-1)
  • Migration status for libhtml-embedded-turtle-perl (- to 0.404-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libhtml-embedded-turtle-perl librdf-rdfa-parser-perl
  • Depends: libhtml-embedded-turtle-perl librdf-rdfa-parser-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhtml-embedded-turtle-perl.html
  • 2483 days old (needed 5 days)
• libwww-finger-perl (- to 0.105-1)
  • Migration status for libwww-finger-perl (- to 0.105-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libwww-finger-perl libhttp-lrdd-perl
  • Depends: libwww-finger-perl libhttp-lrdd-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwww-finger-perl.html
  • 2503 days old (needed 5 days)
• upnp-router-control (- to 0.2-1.2)
  • Migration status for upnp-router-control (- to 0.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating upnp-router-control introduces new bugs: #947805
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/amd64
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/arm64
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/armel
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/armhf
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/i386
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/mips64el
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/mipsel
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/ppc64el
  • Impossible Build-Depends(-Arch): upnp-router-control -> libgupnp-1.0-dev/1.0.3-3/s390x
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/amd64
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/arm64
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/armel
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/armhf
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/i386
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/mips64el
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/mipsel
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/ppc64el
  • Impossible Depends: upnp-router-control -> libgssdp-1.0-3/1.0.2-4/s390x
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/amd64
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/arm64
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/armel
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/armhf
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/i386
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/mips64el
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/mipsel
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/ppc64el
  • Impossible Depends: upnp-router-control -> libgupnp-1.0-4/1.0.3-3/s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/upnp-router-control.html
  • 2510 days old (needed 5 days)
• edb (- to 1.31-3)
  • Migration status for edb (- to 1.31-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating edb introduces new bugs: #840748, #904010
  • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/edb.html
  • edb unsatisfiable Build-Depends-Indep on amd64: emacs24 | emacs-snapshot
  • Not built on buildd: arch all binaries uploaded by tats, a new source-only upload is needed to allow migration
  • Additional info:
  • 2521 days old (needed 5 days)
• libxml-grddl-perl (- to 0.004-2)
  • Migration status for libxml-grddl-perl (- to 0.004-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libxml-grddl-perl librdf-rdfa-parser-perl
  • Depends: libxml-grddl-perl librdf-rdfa-parser-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxml-grddl-perl.html
  • 2522 days old (needed 5 days)
• libhttp-lrdd-perl (- to 0.106-2)
  • Migration status for libhttp-lrdd-perl (- to 0.106-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libhttp-lrdd-perl librdf-rdfa-parser-perl
  • Depends: libhttp-lrdd-perl libhtml-html5-parser-perl
  • Depends: libhttp-lrdd-perl librdf-rdfa-parser-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhttp-lrdd-perl.html
  • 2524 days old (needed 5 days)
• myodbc (- to 5.1.10-3)
  • Migration status for myodbc (- to 5.1.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • libmyodbc/amd64 has unsatisfiable dependency
  • libmyodbc/arm64 has unsatisfiable dependency
  • libmyodbc/armel has unsatisfiable dependency
  • libmyodbc/armhf has unsatisfiable dependency
  • libmyodbc/i386 has unsatisfiable dependency
  • libmyodbc/mips64el has unsatisfiable dependency
  • libmyodbc/mipsel has unsatisfiable dependency
  • libmyodbc/ppc64el has unsatisfiable dependency
  • libmyodbc/s390x has unsatisfiable dependency
  • Updating myodbc introduces new bugs: #835166, #841561, #849630, #852457, #868882
  • Not built on buildd: arch amd64 binaries uploaded by vorlon
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Build-Depends(-Arch): myodbc mysql-5.7
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/myodbc.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 2556 days old (needed 5 days)
• wiki2beamer (- to 0.9.5-1)
  • Migration status for wiki2beamer (- to 0.9.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating wiki2beamer introduces new bugs: #945745
  • Not built on buildd: arch all binaries uploaded by jhr, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wiki2beamer.html
  • 2558 days old (needed 5 days)
• libkiokux-model-perl (- to 0.02-1)
  • Migration status for libkiokux-model-perl (- to 0.02-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): libkiokux-model-perl libkiokudb-perl
  • Depends: libkiokux-model-perl libkiokudb-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkiokux-model-perl.html
  • 2568 days old (needed 5 days)
• mutextrace (- to 0.1.4-1)
  • Migration status for mutextrace (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mutextrace introduces new bugs: #743062
  • Not built on buildd: arch amd64 binaries uploaded by sjr
  • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • missing build on s390x
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mutextrace.html
  • 2578 days old (needed 5 days)
• thp (- to 0.4.6-10)
  • Migration status for thp (- to 0.4.6-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating thp introduces new bugs: #831952
  • Not built on buildd: arch all binaries uploaded by jfs, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thp.html
  • 2586 days old (needed 5 days)
• libphp-predis (- to 0.8.3-1)
  • Migration status for libphp-predis (- to 0.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libphp-predis introduces new bugs: #915069
  • Not built on buildd: arch amd64 binaries uploaded by cyb
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libphp-predis.html
  • 2602 days old (needed 5 days)
• sa-learn-cyrus (- to 0.3.5-1.1)
  • Migration status for sa-learn-cyrus (- to 0.3.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • sa-learn-cyrus/amd64 has unsatisfiable dependency
  • sa-learn-cyrus/i386 has unsatisfiable dependency
  • Updating sa-learn-cyrus introduces new bugs: #830596
  • Not built on buildd: arch all binaries uploaded by gregoa, a new source-only upload is needed to allow migration
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sa-learn-cyrus.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 2639 days old (needed 5 days)
• xmms2-scrobbler (- to 0.4.0-4)
  • Migration status for xmms2-scrobbler (- to 0.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xmms2-scrobbler introduces new bugs: #798099, #919037
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmms2-scrobbler.html
  • 2641 days old (needed 5 days)
• drbdlinks (- to 1.22-1)
  • Migration status for drbdlinks (- to 1.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating drbdlinks introduces new bugs: #945663
  • Not built on buildd: arch all binaries uploaded by thierry, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drbdlinks.html
  • 2771 days old (needed 5 days)
• python-fcgi (- to 19980130-1)
  • Migration status for python-fcgi (- to 19980130-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-fcgi introduces new bugs: #937749
  • Not built on buildd: arch all binaries uploaded by zugschlus, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fcgi.html
  • 2858 days old (needed 5 days)
• sdic (- to 2.1.3-22)
  • Migration status for sdic (- to 2.1.3-22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating sdic introduces new bugs: #754026, #916876
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - (no link yet)
  • 2879 days old (needed 5 days)
• masqmail (- to 0.3.4-1)
  • Migration status for masqmail (- to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating masqmail introduces new bugs: #678493
  • Not built on buildd: arch amd64 binaries uploaded by jhr
  • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/masqmail.html
  • 2899 days old (needed 5 days)
• storebackup (- to 3.2.1-1)
  • Migration status for storebackup (- to 3.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating storebackup introduces new bugs: #949393
  • Not built on buildd: arch all binaries uploaded by ryan, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/storebackup.html
  • 2902 days old (needed 5 days)
• librdf-rdfa-parser-perl (- to 1.097-1)
  • Migration status for librdf-rdfa-parser-perl (- to 1.097-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): librdf-rdfa-parser-perl libhtml-html5-parser-perl
  • Depends: librdf-rdfa-parser-perl libhtml-html5-parser-perl
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librdf-rdfa-parser-perl.html
  • 2904 days old (needed 5 days)
• msp430-libc (- to 20120224-1)
  • Migration status for msp430-libc (- to 20120224-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
  • Build-Depends(-Arch): msp430-libc binutils-msp430 (not considered)
  • Invalidated by build-dependency
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/msp430-libc.html
  • 2930 days old (needed 5 days)
• tolua++ (- to 1.0.93-3)
  • Migration status for tolua++ (- to 1.0.93-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating tolua++ introduces new bugs: #947583
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tolua++.html
  • 2938 days old (needed 5 days)
• vtkdata (- to 5.8.0-1)
  • Migration status for vtkdata (- to 5.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating vtkdata introduces new bugs: #864452
  • Not built on buildd: arch all binaries uploaded by bottoms, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vtkdata.html
  • 2942 days old (needed 5 days)
• navi2ch (- to 2.0.0~git20120331-1)
  • Migration status for navi2ch (- to 2.0.0~git20120331-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating navi2ch introduces new bugs: #952259
  • Not built on buildd: arch all binaries uploaded by knok, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/navi2ch.html
  • 2962 days old (needed 5 days)
• python-pymetar (- to 0.19-1)
  • Migration status for python-pymetar (- to 0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-pymetar introduces new bugs: #835340, #938076
  • Not built on buildd: arch all binaries uploaded by bzed, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pymetar.html
  • 2968 days old (needed 5 days)
• zemberek-ooo (- to 1.0~rc2-10.4)
  • Migration status for zemberek-ooo (- to 1.0~rc2-10.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating zemberek-ooo introduces new bugs: #802416
  • Not built on buildd: arch all binaries uploaded by rene, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zemberek-ooo.html
  • 2970 days old (needed 5 days)
• pstotext (- to 1.9-6)
  • Migration status for pstotext (- to 1.9-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pstotext introduces new bugs: #895513
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pstotext.html
  • 2972 days old (needed 5 days)
• mixer.app (- to 1.8.0-5)
  • Migration status for mixer.app (- to 1.8.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mixer.app introduces new bugs: #896580
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mixer.app.html
  • 2999 days old (needed 5 days)
• fonts-play (- to 1.002+20111215.1+ds2-1)
  • Migration status for fonts-play (- to 1.002+20111215.1+ds2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by pabs, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): fonts-play googlefontdirectory-tools
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-play.html
  • 3011 days old (needed 5 days)
• php-services-json (- to 1.0.3-1)
  • Migration status for php-services-json (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-services-json introduces new bugs: #823683
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-services-json.html
  • 3013 days old (needed 5 days)
• php-mime-type (- to 1.3.1-1)
  • Migration status for php-mime-type (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating php-mime-type introduces new bugs: #783420
  • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mime-type.html
  • 3014 days old (needed 5 days)
• jodreports (- to 2.4.0-3)
  • Migration status for jodreports (- to 2.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating jodreports introduces new bugs: #828781
  • Not built on buildd: arch all binaries uploaded by twerner, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jodreports.html
  • 3103 days old (needed 5 days)
• spd (- to 1.3.0-1)
  • Migration status for spd (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating spd introduces new bugs: #925834
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spd.html
  • 3121 days old (needed 5 days)
• pstack (- to 1.3.1-1)
  • Migration status for pstack (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating pstack introduces new bugs: #950168
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pstack.html
  • 3156 days old (needed 5 days)
• snmpkit (- to 0.9-16)
  • Migration status for snmpkit (- to 0.9-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating snmpkit introduces new bugs: #857299
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snmpkit.html
  • 3164 days old (needed 5 days)
• onetime (- to 1.122-1)
  • Migration status for onetime (- to 1.122-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating onetime introduces new bugs: #943198
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onetime.html
  • 3189 days old (needed 5 days)
• latrace (- to 0.5.11-1)
  • Migration status for latrace (- to 0.5.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating latrace introduces new bugs: #890457, #907308
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latrace.html
  • 3214 days old (needed 5 days)
• usbmount (- to 0.0.22)
  • Migration status for usbmount (- to 0.0.22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating usbmount introduces new bugs: #774149
  • Not built on buildd: arch all binaries uploaded by rbrito@ime.usp.br, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/usbmount.html
  • 3215 days old (needed 5 days)
• combat (- to 0.8.1-1)
  • Migration status for combat (- to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating combat introduces new bugs: #899479
  • Not built on buildd: arch all binaries uploaded by tgg, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/combat.html
  • 3219 days old (needed 5 days)
• coinor-flopc++ (- to 1.0.6-3.1)
  • Migration status for coinor-flopc++ (- to 1.0.6-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating coinor-flopc++ introduces new bugs: #897723
  • Not built on buildd: arch all binaries uploaded by luk, a new source-only upload is needed to allow migration
  • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coinor-flopc++.html
  • 3251 days old (needed 5 days)
• python-pmw (- to 1.3.2-6)
  • Migration status for python-pmw (- to 1.3.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-pmw introduces new bugs: #886617, #938036
  • Not built on buildd: arch all binaries uploaded by segre, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pmw.html
  • 3263 days old (needed 5 days)
• xevil (- to 2.02r2-10)
  • Migration status for xevil (- to 2.02r2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating xevil introduces new bugs: #831104
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xevil.html
  • 3330 days old (needed 5 days)
• qmail-tools (- to 0.1.0)
  • Migration status for qmail-tools (- to 0.1.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating qmail-tools introduces new bugs: #945702
  • Not built on buildd: arch all binaries uploaded by pape, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qmail-tools.html
  • 3344 days old (needed 5 days)
• beancounter (- to 0.8.10)
  • Migration status for beancounter (- to 0.8.10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by edd, a new source-only upload is needed to allow migration
  • Build-Depends-Indep: beancounter finance-yahooquote
  • Depends: beancounter finance-yahooquote
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beancounter.html
  • 3636 days old (needed 5 days)
• libinnodb (- to 1.0.6.6750-1)
  • Migration status for libinnodb (- to 1.0.6.6750-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating libinnodb introduces new bugs: #952290
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libinnodb.html
  • 3720 days old (needed 5 days)
• printfilters-ppd (- to 2.13-11.1)
  • Migration status for printfilters-ppd (- to 2.13-11.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • printfilters-ppd/amd64 has unsatisfiable dependency
  • printfilters-ppd/arm64 has unsatisfiable dependency
  • printfilters-ppd/armel has unsatisfiable dependency
  • printfilters-ppd/armhf has unsatisfiable dependency
  • printfilters-ppd/i386 has unsatisfiable dependency
  • printfilters-ppd/mips64el has unsatisfiable dependency
  • printfilters-ppd/mipsel has unsatisfiable dependency
  • printfilters-ppd/ppc64el has unsatisfiable dependency
  • printfilters-ppd/s390x has unsatisfiable dependency
  • Updating printfilters-ppd introduces new bugs: #876566
  • Additional info:
  • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/printfilters-ppd.html
  • uninstallable on arch amd64, not running autopkgtest there
  • uninstallable on arch arm64, not running autopkgtest there
  • 3726 days old (needed 5 days)
• linux-patch-debianlogo (- to 1.16)
  • Migration status for linux-patch-debianlogo (- to 1.16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Not built on buildd: arch all binaries uploaded by fst, a new source-only upload is needed to allow migration
  • Build-Depends(-Arch): linux-patch-debianlogo dh-kpatches
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-patch-debianlogo.html
  • 3770 days old (needed 5 days)
• gtkperf (- to 0.40+ds-2)
  • Migration status for gtkperf (- to 0.40+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gtkperf introduces new bugs: #932533
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkperf.html
  • 3887 days old (needed 5 days)
• gtrayicon (- to 1.1-1)
  • Migration status for gtrayicon (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating gtrayicon introduces new bugs: #941866
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtrayicon.html
  • 4023 days old (needed 5 days)
• mailplate (- to 0.2-1)
  • Migration status for mailplate (- to 0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating mailplate introduces new bugs: #945661
  • Not built on buildd: arch all binaries uploaded by madduck, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailplate.html
  • 4332 days old (needed 5 days)