Home|Differences with the last checks|Previous runs

Differences between 3927b22 and b1c9c96 (git diff)

Packages now failing:

• DrawGrammar.0.2.0 on 4.05 had its build status changed: partially failing to failing
• aws-s3.4.1.0 on 4.05 had its build status changed: internal failure to failing
• aws-s3.4.1.0 on 4.06 had its build status changed: internal failure to failing
• aws-s3.4.1.0 on 4.07 had its build status changed: internal failure to failing
• aws-s3.4.2.0 on 4.05 had its build status changed: internal failure to failing
• aws-s3.4.2.0 on 4.07 had its build status changed: internal failure to failing
• aws-s3.4.3.0 on 4.05 had its build status changed: internal failure to failing
• aws-s3.4.3.0 on 4.07 had its build status changed: internal failure to failing
• aws.0.0.2 on 4.04 had its build status changed: internal failure to failing
• aws.0.0.3 on 4.05 had its build status changed: internal failure to failing
• bechamel-notty.0.2.0.1~alpha-repo on 4.14+alpha-repo had its build status changed: passing to failing
• bechamel-notty.0.2.0.1~alpha-repo on 5.0+alpha-repo had its build status changed: passing to failing
• coq.8.10.1 on 4.05 had its build status changed: passing to failing
• coq.8.12.0 on 4.08 had its build status changed: passing to failing
• coq.8.12.0 on 4.09 had its build status changed: passing to failing
• coq.8.13.1 on 4.13 had its build status changed: passing to failing
• coq.8.14.1 on 4.14+alpha-repo had its build status changed: passing to failing
• coq.8.15.1 on 4.12 had its build status changed: passing to failing
• coq.8.15.2 on 4.12 had its build status changed: passing to failing
• coq.8.16.0 on 4.09 is now installable. Current state is: failing
• eio.0.3 on 5.0 had its build status changed: passing to failing
• eio.0.3 on 5.0+alpha-repo had its build status changed: passing to failing
• eio.0.4 on 5.0 had its build status changed: passing to failing
• eio.0.4 on 5.0+alpha-repo had its build status changed: passing to failing
• eio.0.5 on 5.0 is now installable. Current state is: failing
• eio.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
• esperanto.0.0.1 on 4.14 is now installable. Current state is: failing
• esperanto.0.0.1 on 4.14+alpha-repo is now installable. Current state is: failing
• gsl.1.24.3 on 4.14 had its build status changed: passing to failing
• h2-async.0.8.0 on 4.06 had its build status changed: passing to failing
• h2-async.0.8.0 on 4.07 had its build status changed: passing to failing
• h2-async.0.8.0 on 4.08 had its build status changed: passing to failing
• h2-async.0.8.0 on 4.09 had its build status changed: passing to failing
• h2-async.0.8.0 on 4.10 had its build status changed: passing to failing
• h2-async.0.8.0 on 4.11 had its build status changed: passing to failing
• inquire.0.2.1 on 5.0 had its build status changed: not available to failing
• jupyter.2.1.0 on 4.02 had its build status changed: passing to failing
• jupyter.2.2.1 on 4.02 had its build status changed: passing to failing
• links.0.9.3 on 5.0 had its build status changed: not available to failing
• liquidsoap.2.1.1 on 4.14+alpha-repo is now installable. Current state is: failing
• liquidsoap.2.1.2 on 4.14+alpha-repo is now installable. Current state is: failing
• lwt_domain.0.1.0 on 5.0 had its build status changed: passing to failing
• lwt_domain.0.1.0 on 5.0+alpha-repo had its build status changed: passing to failing
• lwt_domain.0.2.0 on 5.0 had its build status changed: passing to failing
• lwt_domain.0.2.0 on 5.0+alpha-repo had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.05 had its build status changed: internal failure to failing
• obus.1.2.3 on 5.0 had its build status changed: not available to failing
• ocaml-monadic.0.3.2 on 5.0 had its build status changed: not available to failing
• ocaml-monadic.0.3.2 on 5.0+alpha-repo had its build status changed: not available to failing
• ocf.0.6.0 on 5.0 had its build status changed: not available to failing
• ocf.0.6.0 on 5.0+alpha-repo had its build status changed: not available to failing
• ocf.0.7.0 on 5.0 had its build status changed: not available to failing
• ocf.0.7.0 on 5.0+alpha-repo had its build status changed: not available to failing
• ocp-index-top.0.4.1 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.4.1 on 4.09 had its build status changed: passing to failing
• ocp-index-top.0.4.3 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.4.3 on 4.09 had its build status changed: passing to failing
• ocp-index-top.0.5.0 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.5.0 on 4.09 had its build status changed: passing to failing
• ojs-base.0.6.0 on 5.0+alpha-repo had its build status changed: not available to failing
• piqi.0.7.0 on 4.14 had its build status changed: not available to failing
• piqi.0.7.0 on 4.14+alpha-repo had its build status changed: not available to failing
• piqi.0.7.1 on 4.14 had its build status changed: not available to failing
• piqi.0.7.1 on 4.14+alpha-repo had its build status changed: not available to failing
• piqi.0.7.4 on 4.14 had its build status changed: not available to failing
• piqi.0.7.4 on 4.14+alpha-repo had its build status changed: not available to failing
• piqi.0.7.5 on 4.14 had its build status changed: not available to failing
• piqi.0.7.5 on 4.14+alpha-repo had its build status changed: not available to failing
• postgresql.3.2.1 on 4.02 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.03 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.04 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.05 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.06 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.07 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.08 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.09 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.10 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.11 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.12 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.13 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.14 had its build status changed: passing to failing
• postgresql.3.2.1 on 4.14+alpha-repo had its build status changed: passing to failing
• postgresql.4.0.0 on 4.02 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.03 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.04 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.05 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.06 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.07 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.08 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.09 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.10 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.11 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.12 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.13 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.14 had its build status changed: passing to failing
• postgresql.4.0.0 on 4.14+alpha-repo had its build status changed: passing to failing
• postgresql.4.0.1 on 4.02 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.03 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.04 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.05 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.06 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.07 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.08 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.09 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.10 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.11 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.12 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.13 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.14 had its build status changed: passing to failing
• postgresql.4.0.1 on 4.14+alpha-repo had its build status changed: passing to failing
• postgresql.4.1.0 on 4.04 had its build status changed: passing to failing
• postgresql.4.1.0 on 4.05 had its build status changed: passing to failing
• postgresql.4.1.0 on 4.06 had its build status changed: passing to failing
• postgresql.4.1.0 on 4.07 had its build status changed: passing to failing
• postgresql.4.1.0 on 4.08 had its build status changed: passing to failing
• postgresql.4.1.0 on 4.09 had its build status changed: passing to failing
• postgresql.4.1.0 on 4.10 had its build status changed: passing to failing
• postgresql.4.1.0 on 4.11 had its build status changed: passing to failing
• postgresql.4.2.0 on 4.04 had its build status changed: passing to failing
• postgresql.4.2.0 on 4.05 had its build status changed: passing to failing
• postgresql.4.2.0 on 4.06 had its build status changed: passing to failing
• postgresql.4.2.0 on 4.07 had its build status changed: passing to failing
• postgresql.4.2.0 on 4.08 had its build status changed: passing to failing
• postgresql.4.2.0 on 4.09 had its build status changed: passing to failing
• postgresql.4.2.0 on 4.10 had its build status changed: passing to failing
• postgresql.4.2.0 on 4.11 had its build status changed: passing to failing
• postgresql.4.2.1 on 4.04 had its build status changed: passing to failing
• postgresql.4.2.1 on 4.05 had its build status changed: passing to failing
• postgresql.4.2.1 on 4.06 had its build status changed: passing to failing
• postgresql.4.2.1 on 4.07 had its build status changed: passing to failing
• postgresql.4.2.1 on 4.08 had its build status changed: passing to failing
• postgresql.4.2.1 on 4.09 had its build status changed: passing to failing
• postgresql.4.2.1 on 4.10 had its build status changed: passing to failing
• postgresql.4.2.1 on 4.11 had its build status changed: passing to failing
• postgresql.4.3.0 on 4.04 had its build status changed: passing to failing
• postgresql.4.3.0 on 4.05 had its build status changed: passing to failing
• postgresql.4.3.0 on 4.06 had its build status changed: passing to failing
• postgresql.4.3.0 on 4.07 had its build status changed: passing to failing
• postgresql.4.3.0 on 4.08 had its build status changed: passing to failing
• postgresql.4.3.0 on 4.09 had its build status changed: passing to failing
• postgresql.4.3.0 on 4.10 had its build status changed: passing to failing
• postgresql.4.3.0 on 4.11 had its build status changed: passing to failing
• postgresql.4.4.0 on 4.04 had its build status changed: passing to failing
• postgresql.4.4.0 on 4.05 had its build status changed: passing to failing
• postgresql.4.4.0 on 4.06 had its build status changed: passing to failing
• postgresql.4.4.0 on 4.07 had its build status changed: passing to failing
• postgresql.4.4.0 on 4.08 had its build status changed: passing to failing
• postgresql.4.4.0 on 4.09 had its build status changed: passing to failing
• postgresql.4.4.0 on 4.10 had its build status changed: passing to failing
• postgresql.4.4.0 on 4.11 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.05 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.06 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.07 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.08 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.09 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.10 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.11 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.12 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.13 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.14 had its build status changed: passing to failing
• postgresql.4.4.1 on 4.14+alpha-repo had its build status changed: passing to failing
• postgresql.4.4.1 on 5.0 had its build status changed: passing to failing
• postgresql.4.4.1 on 5.0+alpha-repo had its build status changed: passing to failing
• postgresql.4.4.2 on 4.05 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.06 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.07 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.08 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.09 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.10 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.11 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.12 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.13 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.14 had its build status changed: passing to failing
• postgresql.4.4.2 on 4.14+alpha-repo had its build status changed: passing to failing
• postgresql.4.4.2 on 5.0 had its build status changed: passing to failing
• postgresql.4.4.2 on 5.0+alpha-repo had its build status changed: passing to failing
• postgresql.4.5.0 on 4.05 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.06 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.07 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.08 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.09 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.10 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.11 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.12 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.13 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.14 had its build status changed: passing to failing
• postgresql.4.5.0 on 4.14+alpha-repo had its build status changed: passing to failing
• postgresql.4.5.0 on 5.0 had its build status changed: passing to failing
• postgresql.4.5.0 on 5.0+alpha-repo had its build status changed: passing to failing
• qcow.0.10.0 on 4.08 had its build status changed: internal failure to failing
• resource-pooling.0.3.2 on 5.0 had its build status changed: not available to failing
• resource-pooling.0.5 on 5.0 had its build status changed: not available to failing
• resource-pooling.0.5.1 on 5.0 had its build status changed: not available to failing
• resource-pooling.0.5.2 on 5.0 had its build status changed: not available to failing
• resource-pooling.0.6 on 5.0 had its build status changed: not available to failing
• resource-pooling.0.7 on 5.0 had its build status changed: not available to failing
• resource-pooling.0.8 on 5.0 had its build status changed: not available to failing
• spf.1.0.0 on 4.02 had its build status changed: partially failing to failing
• spf.1.0.0 on 4.03 had its build status changed: partially failing to failing
• spf.1.0.0 on 4.04 had its build status changed: partially failing to failing
• spf.1.0.0 on 4.05 had its build status changed: partially failing to failing
• srt.0.2.2 on 4.03 is now installable. Current state is: failing
• srt.0.2.2 on 4.04 is now installable. Current state is: failing
• srt.0.2.2 on 4.05 is now installable. Current state is: failing
• srt.0.2.2 on 4.06 is now installable. Current state is: failing
• srt.0.2.2 on 4.07 is now installable. Current state is: failing
• tar.1.0.0 on 5.0 had its build status changed: not available to failing
• tar.1.0.0 on 5.0+alpha-repo had its build status changed: not available to failing
• tar.1.0.1 on 5.0 had its build status changed: not available to failing
• tar.1.0.1 on 5.0+alpha-repo had its build status changed: not available to failing
• tar.1.1.0 on 5.0 had its build status changed: not available to failing
• tar.1.1.0 on 5.0+alpha-repo had its build status changed: not available to failing
• torch.0.4 on 5.0 had its build status changed: not available to failing
• torch.0.5 on 5.0 had its build status changed: not available to failing
• ubpf.0.1 on 4.14+alpha-repo had its build status changed: passing to failing
• z3.4.10.1 on 4.11 had its build status changed: passing to failing
• z3.4.11.2 on 4.08 is now installable. Current state is: failing
• z3.4.8.1 on 4.05 had its build status changed: passing to failing
• z3.4.8.11 on 4.14+alpha-repo had its build status changed: passing to failing
• z3.4.8.17 on 5.0 had its build status changed: passing to failing
• z3.4.8.6 on 4.11 had its build status changed: passing to failing
• z3.4.8.8 on 4.04 had its build status changed: passing to failing
• z3.4.8.8-1 on 4.11 had its build status changed: passing to failing
• z3.4.9.1 on 4.09 had its build status changed: passing to failing

Packages now partially failing:

• 0install.2.15.2 on 5.0 had its build status changed: not available to partially failing
• 0install.2.16 on 5.0 had its build status changed: not available to partially failing
• 0install.2.17 on 5.0 had its build status changed: not available to partially failing
• 0install.2.18 on 5.0 is now installable. Current state is: partially failing
• 0install.2.18 on 5.0+alpha-repo is now installable. Current state is: partially failing
• DrawGrammar.0.2.0 on 4.04 had its build status changed: failing to partially failing
• amqp-client-lwt.2.0.3 on 5.0 had its build status changed: not available to partially failing
• amqp-client-lwt.2.1.0 on 5.0 had its build status changed: not available to partially failing
• amqp-client-lwt.2.2.0 on 5.0 had its build status changed: not available to partially failing
• amqp-client-lwt.2.2.1 on 5.0 had its build status changed: not available to partially failing
• amqp-client-lwt.2.2.2 on 5.0 had its build status changed: not available to partially failing
• aws-s3-async.4.1.0 on 4.06 had its build status changed: internal failure to partially failing
• aws-s3-async.4.3.0 on 4.06 had its build status changed: internal failure to partially failing
• aws-s3-async.4.8.0 on 5.0+alpha-repo is now installable. Current state is: partially failing
• aws-s3-lwt.2.0.0 on 4.06 had its build status changed: internal failure to partially failing
• aws-s3-lwt.4.1.0 on 4.06 had its build status changed: internal failure to partially failing
• aws-s3-lwt.4.3.0 on 4.05 had its build status changed: internal failure to partially failing
• aws-s3-lwt.4.4.0 on 4.07 had its build status changed: internal failure to partially failing
• aws-s3-lwt.4.4.0 on 5.0 had its build status changed: not available to partially failing
• aws-s3-lwt.4.4.1 on 5.0 had its build status changed: internal failure to partially failing
• aws-s3-lwt.4.5.1 on 5.0 had its build status changed: not available to partially failing
• aws-s3-lwt.4.5.1 on 5.0+alpha-repo had its build status changed: internal failure to partially failing
• aws-s3-lwt.4.6.0 on 5.0 had its build status changed: not available to partially failing
• aws-s3-lwt.4.7.0 on 5.0 had its build status changed: not available to partially failing
• aws-s3-lwt.4.7.0 on 5.0+alpha-repo had its build status changed: internal failure to partially failing
• aws-s3-lwt.4.8.0 on 5.0 is now installable. Current state is: partially failing
• aws-s3-lwt.4.8.0 on 5.0+alpha-repo is now installable. Current state is: partially failing
• aws-s3.0.9.0 on 4.04 had its build status changed: internal failure to partially failing
• aws-s3.1.1.0 on 4.04 had its build status changed: internal failure to partially failing
• aws-s3.1.1.1 on 4.04 had its build status changed: internal failure to partially failing
• aws-s3.4.4.0 on 5.0 had its build status changed: not available to partially failing
• aws-s3.4.4.1 on 5.0 had its build status changed: not available to partially failing
• aws-s3.4.4.1 on 5.0+alpha-repo had its build status changed: internal failure to partially failing
• aws-s3.4.5.1 on 5.0 had its build status changed: not available to partially failing
• aws-s3.4.6.0 on 5.0 had its build status changed: not available to partially failing
• aws-s3.4.7.0 on 5.0 had its build status changed: not available to partially failing
• aws-s3.4.8.0 on 5.0 is now installable. Current state is: partially failing
• aws-s3.4.8.0 on 5.0+alpha-repo is now installable. Current state is: partially failing
• bap-abi.1.0.0 on 4.04 had its build status changed: internal failure to partially failing
• bap-api.1.3.0 on 4.02 had its build status changed: passing to partially failing
• bechamel-notty.0.1.0 on 5.0 had its build status changed: not available to partially failing
• bechamel-notty.0.2.0 on 5.0 had its build status changed: not available to partially failing
• caqti-driver-postgresql.0.10.0 on 4.04 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.0 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.0 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.0 on 4.07 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.1 on 4.04 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.1 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.1 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.1 on 4.07 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.2 on 4.04 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.2 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.2 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.10.2 on 4.07 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.11.0 on 4.04 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.11.0 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.11.0 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.11.0 on 4.07 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.9.0 on 4.03 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.9.0 on 4.04 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.9.0 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.9.0 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.0.9.0 on 4.07 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.0.0 on 4.04 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.0.0 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.0.0 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.0.0 on 4.07 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.1.0 on 4.04 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.1.0 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.1.0 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.1.0 on 4.07 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.2.0 on 4.04 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.2.0 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.2.0 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.2.0 on 4.07 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.2.1 on 4.05 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.2.1 on 4.06 had its build status changed: passing to partially failing
• caqti-driver-postgresql.1.2.1 on 4.07 had its build status changed: passing to partially failing
• coq-serapi.8.15.0+0.15.0 on 4.10 had its build status changed: passing to partially failing
• coq-serapi.8.15.0+0.15.1 on 4.13 had its build status changed: passing to partially failing
• coq-serapi.8.15.0+0.15.1 on 4.14+alpha-repo had its build status changed: passing to partially failing
• coq-serapi.8.7.1+0.4.2 on 4.06 had its build status changed: passing to partially failing
• coq-serapi.8.8.0+0.5.3 on 4.06 had its build status changed: passing to partially failing
• coq-serapi.8.8.0+0.5.6 on 4.07 had its build status changed: passing to partially failing
• coq-serapi.8.9.0+0.6.0 on 4.08 had its build status changed: passing to partially failing
• coq.8.15.0 on 4.07 had its build status changed: passing to partially failing
• coq.8.15.1 on 4.05 had its build status changed: passing to partially failing
• coq.8.8.2 on 4.05 had its build status changed: passing to partially failing
• core_kernel.113.33.00 on 4.02 had its build status changed: passing to partially failing
• eio_linux.0.3 on 5.0 had its build status changed: passing to partially failing
• eio_linux.0.3 on 5.0+alpha-repo had its build status changed: passing to partially failing
• eio_linux.0.4 on 5.0 had its build status changed: passing to partially failing
• eio_linux.0.4 on 5.0+alpha-repo had its build status changed: passing to partially failing
• eio_linux.0.5 on 5.0 is now installable. Current state is: partially failing
• eio_linux.0.5 on 5.0+alpha-repo is now installable. Current state is: partially failing
• eio_luv.0.3 on 5.0 had its build status changed: passing to partially failing
• eio_luv.0.3 on 5.0+alpha-repo had its build status changed: passing to partially failing
• eio_luv.0.4 on 5.0 had its build status changed: passing to partially failing
• eio_luv.0.4 on 5.0+alpha-repo had its build status changed: passing to partially failing
• eio_luv.0.5 on 5.0 is now installable. Current state is: partially failing
• eio_luv.0.5 on 5.0+alpha-repo is now installable. Current state is: partially failing
• eio_main.0.3 on 5.0 had its build status changed: passing to partially failing
• eio_main.0.3 on 5.0+alpha-repo had its build status changed: passing to partially failing
• eio_main.0.4 on 5.0 had its build status changed: passing to partially failing
• eio_main.0.4 on 5.0+alpha-repo had its build status changed: passing to partially failing
• eio_main.0.5 on 5.0 is now installable. Current state is: partially failing
• eio_main.0.5 on 5.0+alpha-repo is now installable. Current state is: partially failing
• gpr.1.5.0 on 4.12 had its build status changed: passing to partially failing
• h2-lwt.0.8.0 on 5.0+alpha-repo had its build status changed: failing to partially failing
• higlo.0.5 on 5.0+alpha-repo had its build status changed: not available to partially failing
• higlo.0.6 on 5.0+alpha-repo had its build status changed: not available to partially failing
• links-mysql.0.9.3 on 5.0 had its build status changed: not available to partially failing
• links-postgresql.0.9 on 4.06 had its build status changed: passing to partially failing
• links-postgresql.0.9 on 4.07 had its build status changed: passing to partially failing
• links-postgresql.0.9.1 on 4.06 had its build status changed: passing to partially failing
• links-postgresql.0.9.1 on 4.07 had its build status changed: passing to partially failing
• links-postgresql.0.9.3 on 5.0 had its build status changed: not available to partially failing
• links-sqlite3.0.9.3 on 5.0 had its build status changed: not available to partially failing
• lwt_eio.0.1 on 5.0 had its build status changed: passing to partially failing
• lwt_eio.0.1 on 5.0+alpha-repo had its build status changed: passing to partially failing
• lwt_eio.0.2 on 5.0 had its build status changed: passing to partially failing
• lwt_eio.0.2 on 5.0+alpha-repo had its build status changed: passing to partially failing
• mirage-crypto-rng-eio.0.10.7 on 5.0 is now installable. Current state is: partially failing
• mirage-crypto-rng-eio.0.10.7 on 5.0+alpha-repo is now installable. Current state is: partially failing
• mirage-monitoring.0.0.3 on 5.0+alpha-repo is now installable. Current state is: partially failing
• mpris-clients.0.2.0 on 5.0 had its build status changed: not available to partially failing
• mpris.0.2.0 on 5.0 had its build status changed: not available to partially failing
• ocaml-freestanding.0.6.3 on 4.10 had its build status changed: failing to partially failing
• ocsigenserver.3.0.0 on 5.0 had its build status changed: not available to partially failing
• ocsigenserver.4.0.1 on 5.0 had its build status changed: not available to partially failing
• ocsigenserver.4.0.2 on 5.0 had its build status changed: not available to partially failing
• ocsigenserver.5.0.0 on 5.0 had its build status changed: not available to partially failing
• ocsigenserver.5.0.1 on 5.0 had its build status changed: not available to partially failing
• ocsipersist-dbm.1.0 on 5.0 had its build status changed: not available to partially failing
• ocsipersist-dbm.1.0.1 on 5.0 had its build status changed: not available to partially failing
• ocsipersist-dbm.1.1.0 on 5.0 had its build status changed: not available to partially failing
• ocsipersist-sqlite.1.0 on 5.0 had its build status changed: not available to partially failing
• ocsipersist-sqlite.1.1.0 on 5.0 had its build status changed: not available to partially failing
• ocsipersist.1.0 on 5.0 had its build status changed: not available to partially failing
• ocsipersist.1.0.1 on 5.0 had its build status changed: not available to partially failing
• ocsipersist.1.1.0 on 5.0 had its build status changed: not available to partially failing
• opentelemetry-cohttp-lwt.0.2 on 4.12 had its build status changed: passing to partially failing
• opentelemetry-cohttp-lwt.0.3 on 4.14 had its build status changed: passing to partially failing
• opium-graphql.0.20.0 on 4.11 had its build status changed: passing to partially failing
• pareto.0.3 on 4.14+alpha-repo had its build status changed: passing to partially failing
• phylogenetics.0.0.0 on 4.14 had its build status changed: passing to partially failing
• phylogenetics.0.1.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
• prc.0.1.0 on 4.13 had its build status changed: passing to partially failing
• prc.0.1.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
• rawlink-eio.2.1 on 5.0 is now installable. Current state is: partially failing
• rawlink-eio.2.1 on 5.0+alpha-repo is now installable. Current state is: partially failing
• session-postgresql-async.0.4.0 on 4.03 had its build status changed: failing to partially failing
• session-postgresql-async.0.4.0 on 4.04 had its build status changed: passing to partially failing
• session-postgresql-async.0.4.0 on 4.05 had its build status changed: passing to partially failing
• session-postgresql-async.0.4.0 on 4.06 had its build status changed: passing to partially failing
• session-postgresql-async.0.4.1 on 4.03 had its build status changed: failing to partially failing
• session-postgresql-async.0.4.1 on 4.04 had its build status changed: passing to partially failing
• session-postgresql-async.0.4.1 on 4.05 had its build status changed: passing to partially failing
• session-postgresql-async.0.4.1 on 4.06 had its build status changed: passing to partially failing
• session-postgresql-async.0.4.1 on 4.07 had its build status changed: passing to partially failing
• session-postgresql-async.0.5.0 on 4.07 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.0 on 4.03 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.0 on 4.04 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.0 on 4.05 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.0 on 4.06 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.0 on 4.07 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.1 on 4.03 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.1 on 4.04 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.1 on 4.05 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.1 on 4.06 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.4.1 on 4.07 had its build status changed: passing to partially failing
• session-postgresql-lwt.0.5.0 on 4.07 had its build status changed: passing to partially failing
• session-postgresql.0.4.0 on 4.03 had its build status changed: passing to partially failing
• session-postgresql.0.4.0 on 4.04 had its build status changed: passing to partially failing
• session-postgresql.0.4.0 on 4.05 had its build status changed: passing to partially failing
• session-postgresql.0.4.0 on 4.06 had its build status changed: passing to partially failing
• session-postgresql.0.4.0 on 4.07 had its build status changed: passing to partially failing
• session-postgresql.0.4.1 on 4.03 had its build status changed: passing to partially failing
• session-postgresql.0.4.1 on 4.04 had its build status changed: passing to partially failing
• session-postgresql.0.4.1 on 4.05 had its build status changed: passing to partially failing
• session-postgresql.0.4.1 on 4.06 had its build status changed: passing to partially failing
• session-postgresql.0.4.1 on 4.07 had its build status changed: passing to partially failing
• session-postgresql.0.5.0 on 4.07 had its build status changed: passing to partially failing
• spin.0.7.0 on 5.0 had its build status changed: not available to partially failing
• tar-unix.1.0.1 on 5.0 had its build status changed: not available to partially failing
• tar-unix.1.0.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
• tar-unix.1.1.0 on 5.0 had its build status changed: not available to partially failing
• tar-unix.1.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
• tls-eio.0.15.4 on 5.0 is now installable. Current state is: partially failing
• tls-eio.0.15.4 on 5.0+alpha-repo is now installable. Current state is: partially failing
• vchan-unix.4.0.2 on 5.0 had its build status changed: not available to partially failing
• vchan-unix.4.0.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
• vchan-unix.4.0.3 on 5.0 had its build status changed: not available to partially failing
• vchan-unix.4.0.3 on 5.0+alpha-repo had its build status changed: not available to partially failing
• z3_tptp.4.10.1 on 5.0 is now installable. Current state is: partially failing
• z3_tptp.4.11.0 on 4.14+alpha-repo is now installable. Current state is: partially failing

Packages now not available:

• amqp-client.1.0.3 on 5.0 had its build status changed: partially failing to not available
• amqp-client.1.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• amqp-client.1.0.4 on 5.0 had its build status changed: partially failing to not available
• amqp-client.1.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• amqp-client.1.0.5 on 5.0 had its build status changed: partially failing to not available
• amqp-client.1.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
• amqp-client.1.0.6 on 5.0 had its build status changed: partially failing to not available
• amqp-client.1.0.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-async.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-autoscaling.0.1.0 on 5.0 had its build status changed: partially failing to not available
• aws-autoscaling.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-autoscaling.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-autoscaling.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-cloudformation.0.1.0 on 5.0 had its build status changed: partially failing to not available
• aws-cloudformation.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-cloudformation.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-cloudformation.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-cloudtrail.0.1.0 on 5.0 had its build status changed: partially failing to not available
• aws-cloudtrail.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-cloudtrail.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-cloudtrail.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-cloudwatch.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-cloudwatch.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-ec2.0.1.0 on 5.0 had its build status changed: partially failing to not available
• aws-ec2.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-ec2.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-ec2.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-elasticache.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-elasticache.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-elasticloadbalancing.0.1.0 on 5.0 had its build status changed: partially failing to not available
• aws-elasticloadbalancing.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-elasticloadbalancing.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-elasticloadbalancing.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-lwt.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-lwt.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-rds.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-rds.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-route53.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-route53.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-s3-lwt.4.3.0 on 4.12 had its build status changed: internal failure to not available
• aws-s3-lwt.4.3.0 on 4.13 had its build status changed: internal failure to not available
• aws-sdb.0.1.0 on 5.0 had its build status changed: partially failing to not available
• aws-sdb.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-sdb.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-sdb.1.2 on 5.0+alpha-repo had its build status changed: internal failure to not available
• aws-sqs.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-sqs.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-ssm.0.1.0 on 5.0 had its build status changed: partially failing to not available
• aws-ssm.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-ssm.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-ssm.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-sts.0.1.0 on 5.0 had its build status changed: partially failing to not available
• aws-sts.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws-sts.1.2 on 5.0 had its build status changed: partially failing to not available
• aws-sts.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws.1.0.0 on 5.0 had its build status changed: internal failure to not available
• aws.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws.1.0.1 on 5.0 had its build status changed: partially failing to not available
• aws.1.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• aws.1.0.2 on 5.0 had its build status changed: partially failing to not available
• aws.1.0.2 on 5.0+alpha-repo had its build status changed: internal failure to not available
• aws.1.2 on 5.0 had its build status changed: partially failing to not available
• aws.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• bap-analyze.2.5.0 on 4.02 had its build status changed: internal failure to not available
• bap-analyze.2.5.0 on 4.03 had its build status changed: internal failure to not available
• bap-analyze.2.5.0 on 5.0 had its build status changed: internal failure to not available
• base.v0.15.1~5.0preview on 5.0 is not available anymore. Previous state was: passing
• base.v0.15.1~5.0preview on 5.0+alpha-repo is not available anymore. Previous state was: passing
• calendar.1.10 on 5.0 had its build status changed: failing to not available
• calendar.1.10 on 5.0+alpha-repo had its build status changed: failing to not available
• calendar.2.03.2 on 5.0 had its build status changed: failing to not available
• calendar.2.03.2 on 5.0+alpha-repo had its build status changed: failing to not available
• calendar.2.04 on 5.0 had its build status changed: failing to not available
• calendar.2.04 on 5.0+alpha-repo had its build status changed: failing to not available
• camyll.0.2.0 on 5.0 had its build status changed: partially failing to not available
• camyll.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• camyll.0.3.0 on 5.0 had its build status changed: partially failing to not available
• camyll.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• camyll.0.4.0 on 5.0 had its build status changed: partially failing to not available
• camyll.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• capnp.3.3.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.0.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.1.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.2.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.2.1 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.2.3 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.3.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.4.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.5.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.5.1 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.6.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.7.0 on 5.0 had its build status changed: partially failing to not available
• caqti-driver-mariadb.1.8.0 on 5.0 had its build status changed: partially failing to not available
• caqti-type-calendar.1.0.0 on 5.0 had its build status changed: partially failing to not available
• caqti-type-calendar.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• caqti-type-calendar.1.2.0 on 5.0 had its build status changed: partially failing to not available
• caqti-type-calendar.1.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• catala.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• catala.0.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• catala.0.6.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• cohttp-top.2.2.0 on 5.0 had its build status changed: partially failing to not available
• cohttp-top.2.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• cohttp.2.1.3 on 5.0 had its build status changed: failing to not available
• cohttp.2.1.3 on 5.0+alpha-repo had its build status changed: failing to not available
• cohttp.2.2.0 on 5.0 had its build status changed: failing to not available
• cohttp.2.2.0 on 5.0+alpha-repo had its build status changed: failing to not available
• colombe.0.1.0 on 5.0 had its build status changed: partially failing to not available
• colombe.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• conf-llvm.12.0.1 on 4.02 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.03 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.04 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.05 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.06 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.07 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.08 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.09 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.10 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.11 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.12 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.13 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.14 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 4.14+alpha-repo is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 5.0 is not available anymore. Previous state was: passing
• conf-llvm.12.0.1 on 5.0+alpha-repo is not available anymore. Previous state was: passing
• conjury.2.1 on 5.0 had its build status changed: partially failing to not available
• conjury.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• cryptohash.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• cryptohash.0.1.1 on 5.0 had its build status changed: partially failing to not available
• cryptohash.0.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• cryptohash.0.1.2 on 5.0 had its build status changed: partially failing to not available
• cryptohash.0.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• depgraph.0.1.0 on 5.0 had its build status changed: partially failing to not available
• depgraph.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• digestif.0.1 on 5.0 had its build status changed: failing to not available
• digestif.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
• digestif.0.2 on 5.0 had its build status changed: failing to not available
• digestif.0.2 on 5.0+alpha-repo had its build status changed: failing to not available
• digestif.0.3 on 5.0 had its build status changed: failing to not available
• digestif.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
• digestif.0.4 on 5.0 had its build status changed: failing to not available
• digestif.0.4 on 5.0+alpha-repo had its build status changed: failing to not available
• digestif.0.5 on 5.0 had its build status changed: failing to not available
• digestif.0.5 on 5.0+alpha-repo had its build status changed: failing to not available
• digestif.0.7 on 5.0 had its build status changed: failing to not available
• digestif.0.7 on 5.0+alpha-repo had its build status changed: failing to not available
• digestif.0.7.1 on 5.0 had its build status changed: failing to not available
• digestif.0.7.1 on 5.0+alpha-repo had its build status changed: failing to not available
• drom.0.6.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• drom_lib.0.6.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• easy_logging.0.6.0 on 5.0 had its build status changed: partially failing to not available
• easy_logging.0.6.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• easy_logging.0.6.2 on 5.0 had its build status changed: partially failing to not available
• easy_logging.0.6.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• easy_logging.0.7.1 on 5.0 had its build status changed: partially failing to not available
• easy_logging.0.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• easy_logging.0.8.1 on 5.0 had its build status changed: partially failing to not available
• easy_logging.0.8.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• easy_logging.0.8.2 on 5.0 had its build status changed: partially failing to not available
• easy_logging.0.8.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• easy_logging_yojson.0.8.1 on 5.0 had its build status changed: partially failing to not available
• easy_logging_yojson.0.8.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• easy_logging_yojson.0.8.2 on 5.0 had its build status changed: partially failing to not available
• easy_logging_yojson.0.8.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• extprot.1.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ez_config.0.2.0 on 5.0+alpha-repo had its build status changed: failing to not available
• ez_pgocaml.1.0.0 on 5.0 had its build status changed: partially failing to not available
• ez_pgocaml.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• fiat-p256.0.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
• fiat-p256.0.2.0 on 5.0 had its build status changed: failing to not available
• fiat-p256.0.2.0 on 5.0+alpha-repo had its build status changed: failing to not available
• graphql_ppx.1.2.2 on 5.0 had its build status changed: failing to not available
• graphql_ppx.1.2.2 on 5.0+alpha-repo had its build status changed: failing to not available
• hkdf.1.0.0 on 5.0 had its build status changed: failing to not available
• hkdf.1.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
• hxd.0.1.0 on 5.0 had its build status changed: failing to not available
• hxd.0.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
• inotify.2.1 on 5.0 had its build status changed: failing to not available
• inotify.2.1 on 5.0+alpha-repo had its build status changed: failing to not available
• inotify.2.2 on 5.0 had its build status changed: failing to not available
• inotify.2.2 on 5.0+alpha-repo had its build status changed: failing to not available
• inotify.2.3 on 5.0 had its build status changed: failing to not available
• inotify.2.3 on 5.0+alpha-repo had its build status changed: failing to not available
• links-mysql.0.9.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-mysql.0.9.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-mysql.0.9.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-mysql.0.9.7 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-postgresql.0.9.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-postgresql.0.9.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-postgresql.0.9.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-postgresql.0.9.7 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-sqlite3.0.9.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-sqlite3.0.9.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-sqlite3.0.9.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links-sqlite3.0.9.7 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links.0.9.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links.0.9.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links.0.9.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
• links.0.9.7 on 5.0+alpha-repo had its build status changed: partially failing to not available
• llvm.12.0.1 on 4.02 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.03 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.04 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.05 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.06 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.07 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.08 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.09 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.10 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.11 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.12 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.13 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.14 is not available anymore. Previous state was: passing
• llvm.12.0.1 on 4.14+alpha-repo is not available anymore. Previous state was: passing
• macaque.0.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• mariadb.1.1.5 on 5.0 had its build status changed: failing to not available
• mariadb.1.1.5 on 5.0+alpha-repo had its build status changed: failing to not available
• mariadb.1.1.6 on 5.0 had its build status changed: failing to not available
• mariadb.1.1.6 on 5.0+alpha-repo had its build status changed: failing to not available
• naboris.0.0.3 on 5.0 had its build status changed: failing to not available
• naboris.0.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
• naboris.0.0.4 on 5.0 had its build status changed: failing to not available
• naboris.0.0.4 on 5.0+alpha-repo had its build status changed: failing to not available
• naboris.0.1.0 on 5.0 had its build status changed: failing to not available
• naboris.0.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
• naboris.0.1.1 on 5.0 had its build status changed: failing to not available
• naboris.0.1.1 on 5.0+alpha-repo had its build status changed: failing to not available
• naboris.0.1.2 on 5.0 had its build status changed: failing to not available
• naboris.0.1.2 on 5.0+alpha-repo had its build status changed: failing to not available
• naboris.0.1.3 on 5.0 had its build status changed: failing to not available
• naboris.0.1.3 on 5.0+alpha-repo had its build status changed: failing to not available
• notty.0.2.2.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
• notty.0.2.2.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
• notty.0.2.2.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
• ocal.0.1.1 on 5.0 had its build status changed: partially failing to not available
• ocal.0.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocal.0.1.2 on 5.0 had its build status changed: partially failing to not available
• ocal.0.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocal.0.2.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsigen-toolkit.2.10.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsigen-toolkit.2.12.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsigen-toolkit.2.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsigen-toolkit.2.8.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsigen-toolkit.3.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsipersist-pgsql.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsipersist-pgsql.1.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsipersist-pgsql.1.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsipersist-pgsql.1.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsipersist-pgsql.1.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsipersist-pgsql.1.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ocsipersist-pgsql.1.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• omake.0.10.3 on 5.0 had its build status changed: failing to not available
• omake.0.10.3 on 5.0+alpha-repo had its build status changed: failing to not available
• omake.0.10.5 on 5.0 had its build status changed: failing to not available
• omake.0.10.5 on 5.0+alpha-repo had its build status changed: failing to not available
• orsetto.1.0.2 on 5.0 had its build status changed: partially failing to not available
• orsetto.1.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• orsetto.1.0.3 on 5.0 had its build status changed: partially failing to not available
• orsetto.1.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• orsetto.1.1 on 5.0 had its build status changed: partially failing to not available
• orsetto.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• orsetto.1.1.1 on 5.0 had its build status changed: partially failing to not available
• orsetto.1.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pbs.0.2.0 on 5.0 had its build status changed: partially failing to not available
• pbs.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pgocaml.2.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pgocaml.2.3 on 5.0 had its build status changed: partially failing to not available
• pgocaml.2.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pgocaml.3.0 on 5.0 had its build status changed: partially failing to not available
• pgocaml.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pgocaml.4.0 on 5.0 had its build status changed: partially failing to not available
• pgocaml.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pgocaml.4.2 on 5.0 had its build status changed: partially failing to not available
• pgocaml.4.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pgocaml.4.2.2 on 5.0 had its build status changed: partially failing to not available
• pgocaml.4.2.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pgocaml.4.3.0 on 5.0 had its build status changed: partially failing to not available
• pgocaml.4.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• pgocaml_ppx.4.3.0 on 5.0 had its build status changed: partially failing to not available
• pgocaml_ppx.4.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• ppx_expect.v0.15.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
• ppx_expect.v0.15.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
• ppx_expect.v0.15.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
• promise.1.1.0 on 5.0 had its build status changed: failing to not available
• promise.1.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
• promise.1.1.2 on 5.0 had its build status changed: failing to not available
• promise.1.1.2 on 5.0+alpha-repo had its build status changed: failing to not available
• reason.3.8.1 on 5.0 had its build status changed: passing to not available
• reason.3.8.1 on 5.0+alpha-repo had its build status changed: passing to not available
• rhythm.0.0.1 on 5.0 had its build status changed: failing to not available
• rhythm.0.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
• rtop.3.8.1 on 5.0 had its build status changed: passing to not available
• rtop.3.8.1 on 5.0+alpha-repo had its build status changed: passing to not available
• sendmail-lwt.0.1.0 on 5.0 had its build status changed: partially failing to not available
• sendmail-lwt.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sendmail.0.1.0 on 5.0 had its build status changed: partially failing to not available
• sendmail.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sexp_pretty.v0.15.0 on 5.0 had its build status changed: failing to not available
• sexp_pretty.v0.15.0 on 5.0+alpha-repo had its build status changed: failing to not available
• sexp_pretty.v0.15.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
• sexp_pretty.v0.15.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
• sexp_pretty.v0.15.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
• sexplib.v0.15.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
• sexplib.v0.15.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
• sihl-queue.0.4.0 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.0.4.1 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.0.4.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.0.5.0 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.0.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.0.6.0~rc1 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.0.6.0~rc1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.1.0.0 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.1.0.0~rc1 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.1.0.0~rc2 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.1.0.0~rc2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.1.0.0~rc3 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.1.0.0~rc3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.1.0.1 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.1.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.2.0.0 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.2.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.2.0.1 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.2.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.3.0.0 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.3.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.3.0.1 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.3.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.3.0.2 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.3.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl-queue.3.0.3 on 5.0 had its build status changed: partially failing to not available
• sihl-queue.3.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl.0.0.56 on 5.0 had its build status changed: partially failing to not available
• sihl.0.0.56 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl.0.1.0 on 5.0 had its build status changed: partially failing to not available
• sihl.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl.0.1.1 on 5.0 had its build status changed: partially failing to not available
• sihl.0.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl.0.1.2 on 5.0 had its build status changed: partially failing to not available
• sihl.0.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sihl.0.1.3 on 5.0 had its build status changed: partially failing to not available
• sihl.0.1.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• sqlite3.3.0.0 on 5.0 had its build status changed: failing to not available
• sqlite3.3.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.0.0 on 5.0 had its build status changed: failing to not available
• sqlite3.4.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.0.1 on 5.0 had its build status changed: failing to not available
• sqlite3.4.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.0.2 on 5.0 had its build status changed: failing to not available
• sqlite3.4.0.2 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.0.3 on 5.0 had its build status changed: failing to not available
• sqlite3.4.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.0.4 on 5.0 had its build status changed: failing to not available
• sqlite3.4.0.4 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.0.6 on 5.0 had its build status changed: failing to not available
• sqlite3.4.0.6 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.1.0 on 5.0 had its build status changed: failing to not available
• sqlite3.4.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.1.2 on 5.0 had its build status changed: failing to not available
• sqlite3.4.1.2 on 5.0+alpha-repo had its build status changed: failing to not available
• sqlite3.4.1.3 on 5.0 had its build status changed: failing to not available
• sqlite3.4.1.3 on 5.0+alpha-repo had its build status changed: failing to not available
• ssl.0.5.11 on 5.0 had its build status changed: passing to not available
• ssl.0.5.11 on 5.0+alpha-repo had its build status changed: passing to not available
• stdlib-diff.0.1.3 on 5.0 had its build status changed: failing to not available
• stdlib-diff.0.1.3 on 5.0+alpha-repo had its build status changed: failing to not available
• syndic.1.2 on 5.0 had its build status changed: partially failing to not available
• syndic.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• syndic.1.3 on 5.0 had its build status changed: partially failing to not available
• syndic.1.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• syndic.1.3.1 on 5.0 had its build status changed: partially failing to not available
• syndic.1.3.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• syndic.1.4 on 5.0 had its build status changed: partially failing to not available
• syndic.1.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-crypto.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-crypto.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-crypto.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-crypto.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-crypto.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-error-monad.7.0 on 5.0 had its build status changed: partially failing to not available
• tezos-error-monad.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-error-monad.7.1 on 5.0 had its build status changed: partially failing to not available
• tezos-error-monad.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-error-monad.7.2 on 5.0 had its build status changed: partially failing to not available
• tezos-error-monad.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-error-monad.7.3 on 5.0 had its build status changed: partially failing to not available
• tezos-error-monad.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-error-monad.7.4 on 5.0 had its build status changed: partially failing to not available
• tezos-error-monad.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-event-logging.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-event-logging.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-event-logging.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-event-logging.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-event-logging.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-micheline.7.0 on 5.0 had its build status changed: partially failing to not available
• tezos-micheline.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-micheline.7.1 on 5.0 had its build status changed: partially failing to not available
• tezos-micheline.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-micheline.7.2 on 5.0 had its build status changed: partially failing to not available
• tezos-micheline.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-micheline.7.3 on 5.0 had its build status changed: partially failing to not available
• tezos-micheline.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-micheline.7.4 on 5.0 had its build status changed: partially failing to not available
• tezos-micheline.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-rpc.7.0 on 5.0 had its build status changed: partially failing to not available
• tezos-rpc.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-rpc.7.1 on 5.0 had its build status changed: partially failing to not available
• tezos-rpc.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-rpc.7.2 on 5.0 had its build status changed: partially failing to not available
• tezos-rpc.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-rpc.7.3 on 5.0 had its build status changed: partially failing to not available
• tezos-rpc.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-rpc.7.4 on 5.0 had its build status changed: partially failing to not available
• tezos-rpc.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tezos-stdlib.7.0 on 5.0 had its build status changed: failing to not available
• tezos-stdlib.7.0 on 5.0+alpha-repo had its build status changed: failing to not available
• tezos-stdlib.7.1 on 5.0 had its build status changed: failing to not available
• tezos-stdlib.7.1 on 5.0+alpha-repo had its build status changed: failing to not available
• tezos-stdlib.7.2 on 5.0 had its build status changed: failing to not available
• tezos-stdlib.7.2 on 5.0+alpha-repo had its build status changed: failing to not available
• tezos-stdlib.7.3 on 5.0 had its build status changed: failing to not available
• tezos-stdlib.7.3 on 5.0+alpha-repo had its build status changed: failing to not available
• tezos-stdlib.7.4 on 5.0 had its build status changed: failing to not available
• tezos-stdlib.7.4 on 5.0+alpha-repo had its build status changed: failing to not available
• tyxml-jsx.4.5.0 on 5.0 had its build status changed: partially failing to not available
• tyxml-jsx.4.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tyxml-ppx.4.5.0 on 5.0 had its build status changed: partially failing to not available
• tyxml-ppx.4.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• tyxml-syntax.4.5.0 on 5.0 had its build status changed: failing to not available
• tyxml-syntax.4.5.0 on 5.0+alpha-repo had its build status changed: failing to not available
• uint.1.2.1 on 5.0 had its build status changed: failing to not available
• uint.1.2.1 on 5.0+alpha-repo had its build status changed: failing to not available
• vhd-format-lwt.0.12.3 on 5.0 had its build status changed: passing to not available
• vhd-format-lwt.0.12.3 on 5.0+alpha-repo had its build status changed: passing to not available
• webmachine.0.4.0 on 5.0 had its build status changed: partially failing to not available
• webmachine.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
• xenstore.2.1.0 on 5.0 had its build status changed: failing to not available
• xenstore.2.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
• z3.4.8.13 on 5.0 had its build status changed: failing to not available
• z3.4.8.13 on 5.0+alpha-repo had its build status changed: failing to not available
• z3_tptp.4.8.13 on 5.0 had its build status changed: partially failing to not available
• z3_tptp.4.8.13 on 5.0+alpha-repo had its build status changed: partially failing to not available

Packages now failing with an internal failure:

• amf.0.1.0 on 4.03 had its build status changed: failing to internal failure
• amf.0.1.0 on 4.04 had its build status changed: passing to internal failure
• amf.0.1.0 on 4.05 had its build status changed: passing to internal failure
• amf.0.1.2 on 4.04 had its build status changed: passing to internal failure
• amf.0.1.2 on 4.05 had its build status changed: passing to internal failure
• amf.0.1.2 on 4.06 had its build status changed: passing to internal failure
• amf.0.1.2 on 4.07 had its build status changed: passing to internal failure
• amf.0.1.2 on 4.08 had its build status changed: passing to internal failure
• amf.0.1.2 on 4.09 had its build status changed: passing to internal failure
• archetype.1.3.3 on 4.08 is now installable. Current state is: internal failure
• archetype.1.3.3 on 4.09 is now installable. Current state is: internal failure
• archetype.1.3.3 on 4.10 is now installable. Current state is: internal failure
• archetype.1.3.3 on 4.11 is now installable. Current state is: internal failure
• archetype.1.3.3 on 4.12 is now installable. Current state is: internal failure
• archetype.1.3.3 on 4.13 is now installable. Current state is: internal failure
• archetype.1.3.3 on 4.14 is now installable. Current state is: internal failure
• archetype.1.3.3 on 5.0+alpha-repo is now installable. Current state is: internal failure
• bigdecimal.v0.15.0 on 5.0+alpha-repo had its build status changed: passing to internal failure
• bimage.0.3.1 on 4.08 had its build status changed: passing to internal failure
• build_path_prefix_map.0.2 on 4.08 had its build status changed: passing to internal failure
• coclobas.0.0.2 on 4.03 had its build status changed: failing to internal failure
• cohttp-mirage.2.5.6 on 4.08 had its build status changed: passing to internal failure
• cohttp-mirage.5.0.0 on 4.10 had its build status changed: passing to internal failure
• cohttp-top.1.2.0 on 4.11 had its build status changed: passing to internal failure
• cohttp-top.2.0.0 on 4.06 had its build status changed: passing to internal failure
• cohttp-top.2.1.3 on 4.13 had its build status changed: passing to internal failure
• cohttp-top.2.4.0 on 4.07 had its build status changed: passing to internal failure
• cohttp-top.2.5.0 on 4.12 had its build status changed: passing to internal failure
• cohttp-top.2.5.1 on 4.13 had its build status changed: passing to internal failure
• cohttp-top.2.5.2-1 on 4.12 had its build status changed: passing to internal failure
• cohttp-top.2.5.4 on 4.14+alpha-repo had its build status changed: passing to internal failure
• cohttp-top.2.5.6 on 4.12 had its build status changed: passing to internal failure
• cohttp-top.4.0.0 on 4.09 had its build status changed: passing to internal failure
• cohttp-top.5.0.0 on 4.09 had its build status changed: passing to internal failure
• cohttp.0.11.0 on 4.03 had its build status changed: not available to internal failure
• cohttp.0.11.1 on 4.02 had its build status changed: passing to internal failure
• cohttp.0.11.2 on 4.12 had its build status changed: not available to internal failure
• cohttp.0.12.0 on 4.12 had its build status changed: not available to internal failure
• cohttp.0.13.0 on 4.12 had its build status changed: not available to internal failure
• cohttp.0.15.0 on 4.07 had its build status changed: not available to internal failure
• cohttp.0.15.2 on 4.02 had its build status changed: passing to internal failure
• cohttp.0.16.0 on 4.03 had its build status changed: not available to internal failure
• cohttp.0.16.0 on 5.0+alpha-repo had its build status changed: not available to internal failure
• cohttp.0.17.1 on 4.05 had its build status changed: not available to internal failure
• cohttp.0.17.2 on 4.06 had its build status changed: not available to internal failure
• cohttp_async_websocket.v0.15.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
• combinat.1.0 on 4.09 had its build status changed: passing to internal failure
• combine.0.6 on 4.05 had its build status changed: passing to internal failure
• combine.0.6 on 4.09 had its build status changed: passing to internal failure
• combine.0.6 on 5.0 had its build status changed: failing to internal failure
• comby-kernel.1.4.1 on 4.14 had its build status changed: passing to internal failure
• comby-kernel.1.7.0 on 4.13 had its build status changed: passing to internal failure
• comby-semantic.1.7.0 on 4.14 had its build status changed: passing to internal failure
• comby.1.4.0 on 4.12 had its build status changed: passing to internal failure
• comby.1.4.1 on 4.12 had its build status changed: passing to internal failure
• comby.1.7.0 on 4.14 had its build status changed: passing to internal failure
• command_rpc.v0.10.0 on 5.0 had its build status changed: not available to internal failure
• command_rpc.v0.12.0 on 4.08 had its build status changed: passing to internal failure
• command_rpc.v0.13.0 on 4.09 had its build status changed: passing to internal failure
• comparelib.108.00.02 on 4.06 had its build status changed: not available to internal failure
• conan-cli.0.0.1 on 5.0+alpha-repo had its build status changed: passing to internal failure
• conan-lwt.0.0.1 on 4.10 had its build status changed: passing to internal failure
• conan-lwt.0.0.2 on 4.14+alpha-repo had its build status changed: passing to internal failure
• conan-unix.0.0.2 on 4.13 had its build status changed: passing to internal failure
• cstruct-async.3.5.0 on 4.14 had its build status changed: passing to internal failure
• dolmen.0.4 on 4.09 had its build status changed: passing to internal failure
• dolmen.0.4 on 4.11 had its build status changed: passing to internal failure
• ffmpeg-av.1.0.0 on 5.0 had its build status changed: passing to internal failure
• ffmpeg-av.1.0.0~rc1 on 4.09 had its build status changed: passing to internal failure
• ffmpeg-av.1.0.0~rc1 on 4.14+alpha-repo had its build status changed: passing to internal failure
• ffmpeg-av.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: passing to internal failure
• ffmpeg-avcodec.1.0.0 on 4.13 had its build status changed: passing to internal failure
• ffmpeg-avcodec.1.0.0~rc1 on 4.10 had its build status changed: passing to internal failure
• ffmpeg-avcodec.1.0.0~rc1 on 4.11 had its build status changed: passing to internal failure
• ffmpeg-avcodec.1.0.0~rc1 on 4.14 had its build status changed: passing to internal failure
• ffmpeg-avdevice.1.0.0 on 4.08 had its build status changed: passing to internal failure
• ffmpeg-avdevice.1.0.0 on 5.0 had its build status changed: passing to internal failure
• ffmpeg-avdevice.1.0.0~rc1 on 4.09 had its build status changed: passing to internal failure
• ffmpeg-avfilter.1.0.0 on 4.08 had its build status changed: passing to internal failure
• ffmpeg-avfilter.1.0.0 on 4.09 had its build status changed: passing to internal failure
• ffmpeg-avfilter.1.0.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
• ffmpeg-avfilter.1.0.0~rc1 on 4.09 had its build status changed: passing to internal failure
• ffmpeg-avfilter.1.0.0~rc1 on 4.13 had its build status changed: passing to internal failure
• ffmpeg-avutil.1.0.0 on 4.13 had its build status changed: passing to internal failure
• ffmpeg-avutil.1.0.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
• ffmpeg-avutil.1.0.0~rc1 on 4.08 had its build status changed: passing to internal failure
• ffmpeg-swresample.1.0.0 on 4.11 had its build status changed: passing to internal failure
• ffmpeg-swresample.1.0.0 on 5.0+alpha-repo had its build status changed: passing to internal failure
• ffmpeg-swresample.1.0.0~rc1 on 4.11 had its build status changed: passing to internal failure
• ffmpeg-swresample.1.0.0~rc1 on 5.0 had its build status changed: passing to internal failure
• ffmpeg-swscale.1.0.0 on 5.0+alpha-repo had its build status changed: passing to internal failure
• ffmpeg-swscale.1.0.0~rc1 on 4.10 had its build status changed: passing to internal failure
• ffmpeg-swscale.1.0.0~rc1 on 4.12 had its build status changed: passing to internal failure
• ffmpeg-swscale.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: passing to internal failure
• ffmpeg.1.0.0 on 4.08 had its build status changed: passing to internal failure
• ffmpeg.1.0.0 on 4.10 had its build status changed: passing to internal failure
• ffmpeg.1.0.0 on 5.0+alpha-repo had its build status changed: passing to internal failure
• ffmpeg.1.0.0~rc1 on 4.11 had its build status changed: passing to internal failure
• ffmpeg.1.0.0~rc1 on 4.14 had its build status changed: passing to internal failure
• gadelac.0.6.1 on 4.12 had its build status changed: passing to internal failure
• glical.0.0.1 on 4.02 had its build status changed: passing to internal failure
• glical.0.0.3 on 4.11 had its build status changed: passing to internal failure
• glical.0.0.4 on 4.12 had its build status changed: passing to internal failure
• glical.0.0.5 on 4.13 had its build status changed: passing to internal failure
• glical.0.0.7 on 5.0 had its build status changed: passing to internal failure
• http-cookie.3.0.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
• javalib.2.3.4 on 4.06 had its build status changed: passing to internal failure
• javalib.2.3.5 on 4.08 had its build status changed: passing to internal failure
• message-switch.1.4.0 on 4.02 had its build status changed: partially failing to internal failure
• mirage-entropy-xen.0.1.6 on 4.03 had its build status changed: passing to internal failure
• mirage-xen-minios.0.6.0 on 4.05 had its build status changed: failing to internal failure
• mparser.1.2.1 on 4.02 had its build status changed: passing to internal failure
• mparser.1.2.1 on 4.08 had its build status changed: passing to internal failure
• mparser.1.2.1 on 4.10 had its build status changed: passing to internal failure
• mparser.1.2.1 on 5.0 had its build status changed: failing to internal failure
• mpp.0.1.0 on 4.02 had its build status changed: passing to internal failure
• mpp.0.1.1 on 4.05 had its build status changed: passing to internal failure
• mpp.0.1.5 on 4.02 had its build status changed: passing to internal failure
• mpp.0.3.0 on 4.04 had its build status changed: passing to internal failure
• ocamlformat.0.2 on 4.04 had its build status changed: failing to internal failure
• ocamlformat_support.0.2 on 4.06 had its build status changed: passing to internal failure
• ocamlog.0.1 on 4.04 had its build status changed: passing to internal failure
• ocamlog.0.1 on 4.07 had its build status changed: passing to internal failure
• ocamlog.0.2 on 4.05 had its build status changed: passing to internal failure
• ocamlog.0.2 on 4.06 had its build status changed: passing to internal failure
• ocamlog.0.2 on 4.08 had its build status changed: passing to internal failure
• omd.0.8.0 on 4.05 had its build status changed: passing to internal failure
• omd.1.0.1 on 4.05 had its build status changed: passing to internal failure
• omd.1.1.3 on 4.03 had its build status changed: passing to internal failure
• opam-publish.0.2.0 on 4.02 had its build status changed: failing to internal failure
• opentelemetry-lwt.0.2 on 4.14+alpha-repo had its build status changed: passing to internal failure
• operf-micro.1.1.1 on 4.11 had its build status changed: passing to internal failure
• opium.0.12.0 on 4.12 had its build status changed: not available to internal failure
• oraft.0.1.0 on 4.07 had its build status changed: passing to internal failure
• osdp.0.5.4 on 4.03 had its build status changed: passing to internal failure
• osdp.0.5.4 on 4.05 had its build status changed: passing to internal failure
• osdp.0.6.0 on 4.05 had its build status changed: passing to internal failure
• osdp.0.6.0 on 4.08 had its build status changed: passing to internal failure
• osdp.0.6.0 on 4.09 had its build status changed: passing to internal failure
• osdp.0.6.0 on 4.10 had its build status changed: passing to internal failure
• osdp.0.6.0 on 4.11 had its build status changed: passing to internal failure
• osdp.0.6.0 on 4.14 had its build status changed: passing to internal failure
• osdp.1.0.0 on 4.03 had its build status changed: passing to internal failure
• osdp.1.0.0 on 4.04 had its build status changed: passing to internal failure
• osdp.1.0.0 on 4.06 had its build status changed: passing to internal failure
• osdp.1.0.0 on 4.09 had its build status changed: passing to internal failure
• osdp.1.0.0 on 4.10 had its build status changed: passing to internal failure
• osdp.1.0.0 on 4.12 had its build status changed: passing to internal failure
• osdp.1.0.0 on 4.13 had its build status changed: passing to internal failure
• osdp.1.0.0 on 4.14 had its build status changed: passing to internal failure
• osdp.1.0.0 on 5.0 had its build status changed: failing to internal failure
• pa_comprehension.0.4 on 4.05 had its build status changed: passing to internal failure
• pa_comprehension.0.4 on 4.06 had its build status changed: passing to internal failure
• pa_qualified.0.6 on 4.04 had its build status changed: passing to internal failure
• pa_qualified.0.6 on 4.13 had its build status changed: passing to internal failure
• pa_solution.0.5 on 4.14+alpha-repo had its build status changed: passing to internal failure
• pa_solution.0.7 on 4.03 had its build status changed: passing to internal failure
• pa_solution.0.7 on 4.10 had its build status changed: passing to internal failure
• pla.1.4 on 4.05 had its build status changed: passing to internal failure
• pla.1.4 on 4.07 had its build status changed: passing to internal failure
• pla.1.4 on 4.08 had its build status changed: passing to internal failure
• plebeia.2.0.2 on 4.12 is now installable. Current state is: internal failure
• plebeia.2.0.2 on 4.13 is now installable. Current state is: internal failure
• plebeia.2.0.2 on 4.14+alpha-repo is now installable. Current state is: internal failure
• proverif.1.98 on 4.02 had its build status changed: passing to internal failure
• proverif.1.98 on 4.05 had its build status changed: passing to internal failure
• rfc1951.0.1 on 4.10 had its build status changed: passing to internal failure
• solo5-bindings-hvt.0.6.6 on 4.10 had its build status changed: failing to internal failure
• tezos-mockup-proxy.9.3 on 4.09 had its build status changed: passing to internal failure
• tls.0.10.6 on 4.09 had its build status changed: passing to internal failure
• tls.0.11.0 on 4.07 had its build status changed: passing to internal failure
• tls.0.13.1 on 4.10 had its build status changed: passing to internal failure
• tls.0.13.2 on 4.10 had its build status changed: passing to internal failure
• tls.0.14.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
• tls.0.14.1 on 4.08 had its build status changed: passing to internal failure
• tls.0.14.1 on 4.14 had its build status changed: passing to internal failure
• tls.0.15.0 on 4.13 had its build status changed: passing to internal failure
• tls.0.6.0 on 5.0+alpha-repo had its build status changed: not available to internal failure
• toml.1.0.0 on 4.03 had its build status changed: passing to internal failure
• toml.2.0.0 on 4.04 had its build status changed: passing to internal failure
• torch.0.10 on 4.08 had its build status changed: passing to internal failure
• torch.0.13 on 4.10 had its build status changed: passing to internal failure
• torch.0.2 on 5.0 had its build status changed: not available to internal failure
• torch.0.3 on 5.0 had its build status changed: not available to internal failure
• torch.0.4 on 4.06 had its build status changed: passing to internal failure
• torch.0.5 on 4.06 had its build status changed: passing to internal failure
• torch.0.6 on 4.14+alpha-repo had its build status changed: passing to internal failure
• torch.0.7 on 4.07 had its build status changed: passing to internal failure
• travesty.0.3.0 on 4.09 had its build status changed: passing to internal failure
• tsdl-mixer.0.3.2 on 4.12 had its build status changed: passing to internal failure
• tsdl-ttf.0.2 on 4.08 had its build status changed: passing to internal failure
• z3.4.10.1 on 4.14+alpha-repo had its build status changed: passing to internal failure
• z3.4.11.2 on 4.09 is now installable. Current state is: internal failure
• z3.4.8.1 on 4.06 had its build status changed: passing to internal failure
• z3.4.8.17 on 4.14 had its build status changed: passing to internal failure
• z3.4.8.5 on 4.05 had its build status changed: passing to internal failure
• z3.4.8.6 on 4.10 had its build status changed: passing to internal failure
• z3.4.8.8-1 on 4.07 had its build status changed: passing to internal failure
• z3.4.9.1 on 4.08 had its build status changed: passing to internal failure
• z3_tptp.4.10.1 on 4.14+alpha-repo is now installable. Current state is: internal failure
• z3_tptp.4.11.0 on 5.0+alpha-repo is now installable. Current state is: internal failure
• z3_tptp.4.8.14 on 4.06 had its build status changed: not available to internal failure
• zlist.0.1.2 on 4.05 had its build status changed: passing to internal failure
• zlist.0.1.2 on 4.08 had its build status changed: passing to internal failure
• zlist.0.1.2 on 4.14+alpha-repo had its build status changed: passing to internal failure
• zlist.0.4.0 on 4.02 had its build status changed: passing to internal failure
• zlist.0.4.0 on 4.03 had its build status changed: passing to internal failure
• zlist.0.4.0 on 4.10 had its build status changed: passing to internal failure
• zlist.0.4.0 on 4.12 had its build status changed: passing to internal failure
• zlist.0.4.0 on 4.13 had its build status changed: passing to internal failure

Packages now passing:

• 0install-gtk.2.16 on 4.11 had its build status changed: failing to passing
• 0install-gtk.2.18 on 4.08 is now installable. Current state is: passing
• 0install-gtk.2.18 on 4.09 is now installable. Current state is: passing
• 0install-gtk.2.18 on 4.10 is now installable. Current state is: passing
• 0install-gtk.2.18 on 4.11 is now installable. Current state is: passing
• 0install-gtk.2.18 on 4.12 is now installable. Current state is: passing
• 0install-gtk.2.18 on 4.13 is now installable. Current state is: passing
• 0install-gtk.2.18 on 4.14 is now installable. Current state is: passing
• 0install-gtk.2.18 on 4.14+alpha-repo is now installable. Current state is: passing
• 0install-solver.2.18 on 4.08 is now installable. Current state is: passing
• 0install-solver.2.18 on 4.09 is now installable. Current state is: passing
• 0install-solver.2.18 on 4.10 is now installable. Current state is: passing
• 0install-solver.2.18 on 4.11 is now installable. Current state is: passing
• 0install-solver.2.18 on 4.12 is now installable. Current state is: passing
• 0install-solver.2.18 on 4.13 is now installable. Current state is: passing
• 0install-solver.2.18 on 4.14 is now installable. Current state is: passing
• 0install-solver.2.18 on 4.14+alpha-repo is now installable. Current state is: passing
• 0install-solver.2.18 on 5.0 is now installable. Current state is: passing
• 0install-solver.2.18 on 5.0+alpha-repo is now installable. Current state is: passing
• 0install.2.18 on 4.08 is now installable. Current state is: passing
• 0install.2.18 on 4.09 is now installable. Current state is: passing
• 0install.2.18 on 4.10 is now installable. Current state is: passing
• 0install.2.18 on 4.11 is now installable. Current state is: passing
• 0install.2.18 on 4.12 is now installable. Current state is: passing
• 0install.2.18 on 4.13 is now installable. Current state is: passing
• 0install.2.18 on 4.14 is now installable. Current state is: passing
• 0install.2.18 on 4.14+alpha-repo is now installable. Current state is: passing
• OCanren-ppx.0.3.0 on 5.0 had its build status changed: not available to passing
• SZXX.2.3.0 on 4.08 is now installable. Current state is: passing
• SZXX.2.3.0 on 4.09 is now installable. Current state is: passing
• SZXX.2.3.0 on 4.10 is now installable. Current state is: passing
• SZXX.2.3.0 on 4.11 is now installable. Current state is: passing
• SZXX.2.3.0 on 4.12 is now installable. Current state is: passing
• SZXX.2.3.0 on 4.13 is now installable. Current state is: passing
• SZXX.2.3.0 on 4.14 is now installable. Current state is: passing
• SZXX.2.3.0 on 4.14+alpha-repo is now installable. Current state is: passing
• SZXX.2.3.0 on 5.0+alpha-repo is now installable. Current state is: passing
• Snowflake.0.02.03 on 4.13 is now installable. Current state is: passing
• Snowflake.0.02.03 on 4.14 is now installable. Current state is: passing
• Snowflake.0.02.03 on 4.14+alpha-repo is now installable. Current state is: passing
• Snowflake.0.02.03 on 5.0 is now installable. Current state is: passing
• Snowflake.0.02.03 on 5.0+alpha-repo is now installable. Current state is: passing
• abstract_algebra.v0.15.0 on 5.0 had its build status changed: not available to passing
• accessor.v0.15.0 on 5.0 had its build status changed: not available to passing
• accessor_base.v0.15.0 on 5.0 had its build status changed: not available to passing
• acgtk.1.5.1 on 5.0 had its build status changed: failing to passing
• acgtk.1.5.1 on 5.0+alpha-repo had its build status changed: failing to passing
• acgtk.1.5.2 on 5.0 had its build status changed: failing to passing
• acgtk.1.5.2 on 5.0+alpha-repo had its build status changed: failing to passing
• acgtk.1.5.3 on 5.0 had its build status changed: failing to passing
• acgtk.1.5.3 on 5.0+alpha-repo had its build status changed: failing to passing
• aches-lwt.1.0.0 on 4.08 is now installable. Current state is: passing
• aches-lwt.1.0.0 on 4.09 is now installable. Current state is: passing
• aches-lwt.1.0.0 on 4.10 is now installable. Current state is: passing
• aches-lwt.1.0.0 on 4.11 is now installable. Current state is: passing
• aches-lwt.1.0.0 on 4.12 is now installable. Current state is: passing
• aches-lwt.1.0.0 on 4.13 is now installable. Current state is: passing
• aches-lwt.1.0.0 on 4.14 is now installable. Current state is: passing
• aches-lwt.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• aches-lwt.1.0.0 on 5.0 is now installable. Current state is: passing
• aches-lwt.1.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• aches.1.0.0 on 4.08 is now installable. Current state is: passing
• aches.1.0.0 on 4.09 is now installable. Current state is: passing
• aches.1.0.0 on 4.10 is now installable. Current state is: passing
• aches.1.0.0 on 4.11 is now installable. Current state is: passing
• aches.1.0.0 on 4.12 is now installable. Current state is: passing
• aches.1.0.0 on 4.13 is now installable. Current state is: passing
• aches.1.0.0 on 4.14 is now installable. Current state is: passing
• aches.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• aches.1.0.0 on 5.0 is now installable. Current state is: passing
• aches.1.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• albatross.1.4.3 on 5.0+alpha-repo had its build status changed: partially failing to passing
• albatross.1.5.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• albatross.1.5.1 on 4.12 is now installable. Current state is: passing
• albatross.1.5.1 on 4.13 is now installable. Current state is: passing
• albatross.1.5.1 on 4.14 is now installable. Current state is: passing
• albatross.1.5.1 on 4.14+alpha-repo is now installable. Current state is: passing
• albatross.1.5.1 on 5.0+alpha-repo is now installable. Current state is: passing
• archetype.1.3.3 on 4.14+alpha-repo is now installable. Current state is: passing
• archetype.1.3.4 on 4.08 is now installable. Current state is: passing
• archetype.1.3.4 on 4.09 is now installable. Current state is: passing
• archetype.1.3.4 on 4.10 is now installable. Current state is: passing
• archetype.1.3.4 on 4.11 is now installable. Current state is: passing
• archetype.1.3.4 on 4.12 is now installable. Current state is: passing
• archetype.1.3.4 on 4.13 is now installable. Current state is: passing
• archetype.1.3.4 on 4.14 is now installable. Current state is: passing
• archetype.1.3.4 on 4.14+alpha-repo is now installable. Current state is: passing
• archetype.1.3.4 on 5.0+alpha-repo is now installable. Current state is: passing
• archetype.1.3.5 on 4.08 is now installable. Current state is: passing
• archetype.1.3.5 on 4.09 is now installable. Current state is: passing
• archetype.1.3.5 on 4.10 is now installable. Current state is: passing
• archetype.1.3.5 on 4.11 is now installable. Current state is: passing
• archetype.1.3.5 on 4.12 is now installable. Current state is: passing
• archetype.1.3.5 on 4.13 is now installable. Current state is: passing
• archetype.1.3.5 on 4.14 is now installable. Current state is: passing
• archetype.1.3.5 on 4.14+alpha-repo is now installable. Current state is: passing
• archetype.1.3.5 on 5.0+alpha-repo is now installable. Current state is: passing
• async-zmq.0.3.0 on 4.02 had its build status changed: partially failing to passing
• async_rpc_kernel.113.33.00 on 4.02 had its build status changed: partially failing to passing
• aws-s3-async.4.0.1 on 4.05 had its build status changed: internal failure to passing
• aws-s3-async.4.2.0 on 4.08 had its build status changed: internal failure to passing
• aws-s3-async.4.3.0 on 4.08 had its build status changed: internal failure to passing
• aws-s3-async.4.4.0 on 4.09 had its build status changed: internal failure to passing
• aws-s3-async.4.4.0 on 4.11 had its build status changed: internal failure to passing
• aws-s3-async.4.4.1 on 4.10 had its build status changed: internal failure to passing
• aws-s3-async.4.4.1 on 4.12 had its build status changed: internal failure to passing
• aws-s3-async.4.5.1 on 4.09 had its build status changed: internal failure to passing
• aws-s3-async.4.5.1 on 4.11 had its build status changed: internal failure to passing
• aws-s3-async.4.6.0 on 4.12 had its build status changed: internal failure to passing
• aws-s3-async.4.7.0 on 4.12 had its build status changed: internal failure to passing
• aws-s3-async.4.7.0 on 4.13 had its build status changed: internal failure to passing
• aws-s3-async.4.8.0 on 4.08 is now installable. Current state is: passing
• aws-s3-async.4.8.0 on 4.09 is now installable. Current state is: passing
• aws-s3-async.4.8.0 on 4.10 is now installable. Current state is: passing
• aws-s3-async.4.8.0 on 4.11 is now installable. Current state is: passing
• aws-s3-async.4.8.0 on 4.12 is now installable. Current state is: passing
• aws-s3-async.4.8.0 on 4.13 is now installable. Current state is: passing
• aws-s3-async.4.8.0 on 4.14 is now installable. Current state is: passing
• aws-s3-async.4.8.0 on 4.14+alpha-repo is now installable. Current state is: passing
• aws-s3-lwt.4.0.1 on 4.05 had its build status changed: internal failure to passing
• aws-s3-lwt.4.0.1 on 4.06 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.0 on 4.06 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.0 on 4.13 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.0 on 4.14 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.1 on 4.06 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.1 on 4.08 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.1 on 4.09 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.1 on 4.10 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.1 on 4.12 had its build status changed: internal failure to passing
• aws-s3-lwt.4.4.1 on 4.14+alpha-repo had its build status changed: internal failure to passing
• aws-s3-lwt.4.5.0 on 4.06 had its build status changed: internal failure to passing
• aws-s3-lwt.4.5.0 on 4.08 had its build status changed: internal failure to passing
• aws-s3-lwt.4.5.0 on 4.09 had its build status changed: internal failure to passing
• aws-s3-lwt.4.5.1 on 4.06 had its build status changed: internal failure to passing
• aws-s3-lwt.4.5.1 on 4.08 had its build status changed: internal failure to passing
• aws-s3-lwt.4.5.1 on 4.09 had its build status changed: internal failure to passing
• aws-s3-lwt.4.5.1 on 4.11 had its build status changed: internal failure to passing
• aws-s3-lwt.4.6.0 on 4.08 had its build status changed: internal failure to passing
• aws-s3-lwt.4.6.0 on 4.09 had its build status changed: internal failure to passing
• aws-s3-lwt.4.6.0 on 4.10 had its build status changed: internal failure to passing
• aws-s3-lwt.4.7.0 on 4.12 had its build status changed: internal failure to passing
• aws-s3-lwt.4.7.0 on 4.14+alpha-repo had its build status changed: internal failure to passing
• aws-s3-lwt.4.8.0 on 4.08 is now installable. Current state is: passing
• aws-s3-lwt.4.8.0 on 4.09 is now installable. Current state is: passing
• aws-s3-lwt.4.8.0 on 4.10 is now installable. Current state is: passing
• aws-s3-lwt.4.8.0 on 4.11 is now installable. Current state is: passing
• aws-s3-lwt.4.8.0 on 4.12 is now installable. Current state is: passing
• aws-s3-lwt.4.8.0 on 4.13 is now installable. Current state is: passing
• aws-s3-lwt.4.8.0 on 4.14 is now installable. Current state is: passing
• aws-s3-lwt.4.8.0 on 4.14+alpha-repo is now installable. Current state is: passing
• aws-s3.4.0.0 on 4.06 had its build status changed: internal failure to passing
• aws-s3.4.0.0 on 4.07 had its build status changed: internal failure to passing
• aws-s3.4.0.1 on 4.05 had its build status changed: internal failure to passing
• aws-s3.4.0.1 on 4.06 had its build status changed: internal failure to passing
• aws-s3.4.0.1 on 4.07 had its build status changed: internal failure to passing
• aws-s3.4.2.0 on 4.08 had its build status changed: internal failure to passing
• aws-s3.4.3.0 on 4.08 had its build status changed: internal failure to passing
• aws-s3.4.4.0 on 4.05 had its build status changed: internal failure to passing
• aws-s3.4.4.0 on 4.06 had its build status changed: internal failure to passing
• aws-s3.4.4.0 on 4.08 had its build status changed: internal failure to passing
• aws-s3.4.4.0 on 4.10 had its build status changed: internal failure to passing
• aws-s3.4.4.1 on 4.05 had its build status changed: internal failure to passing
• aws-s3.4.4.1 on 4.08 had its build status changed: internal failure to passing
• aws-s3.4.4.1 on 4.10 had its build status changed: internal failure to passing
• aws-s3.4.4.1 on 4.14 had its build status changed: internal failure to passing
• aws-s3.4.5.0 on 4.06 had its build status changed: internal failure to passing
• aws-s3.4.5.1 on 4.08 had its build status changed: internal failure to passing
• aws-s3.4.5.1 on 4.10 had its build status changed: internal failure to passing
• aws-s3.4.5.1 on 4.11 had its build status changed: internal failure to passing
• aws-s3.4.5.1 on 4.12 had its build status changed: internal failure to passing
• aws-s3.4.5.1 on 4.13 had its build status changed: internal failure to passing
• aws-s3.4.6.0 on 4.09 had its build status changed: internal failure to passing
• aws-s3.4.6.0 on 4.10 had its build status changed: internal failure to passing
• aws-s3.4.6.0 on 4.11 had its build status changed: internal failure to passing
• aws-s3.4.6.0 on 4.12 had its build status changed: internal failure to passing
• aws-s3.4.6.0 on 4.14 had its build status changed: internal failure to passing
• aws-s3.4.7.0 on 4.08 had its build status changed: internal failure to passing
• aws-s3.4.7.0 on 4.09 had its build status changed: internal failure to passing
• aws-s3.4.7.0 on 4.10 had its build status changed: internal failure to passing
• aws-s3.4.7.0 on 4.11 had its build status changed: internal failure to passing
• aws-s3.4.7.0 on 4.13 had its build status changed: internal failure to passing
• aws-s3.4.8.0 on 4.08 is now installable. Current state is: passing
• aws-s3.4.8.0 on 4.09 is now installable. Current state is: passing
• aws-s3.4.8.0 on 4.10 is now installable. Current state is: passing
• aws-s3.4.8.0 on 4.11 is now installable. Current state is: passing
• aws-s3.4.8.0 on 4.12 is now installable. Current state is: passing
• aws-s3.4.8.0 on 4.13 is now installable. Current state is: passing
• aws-s3.4.8.0 on 4.14 is now installable. Current state is: passing
• aws-s3.4.8.0 on 4.14+alpha-repo is now installable. Current state is: passing
• aws-sdb.0.1.0 on 4.03 had its build status changed: internal failure to passing
• aws-sdb.0.1.0 on 4.07 had its build status changed: internal failure to passing
• aws-sdb.0.1.0 on 4.08 had its build status changed: internal failure to passing
• aws-sdb.0.1.0 on 4.09 had its build status changed: internal failure to passing
• aws-sdb.0.1.0 on 4.10 had its build status changed: internal failure to passing
• aws-sdb.0.1.0 on 4.11 had its build status changed: internal failure to passing
• aws-sdb.1.2 on 4.07 had its build status changed: internal failure to passing
• aws-sdb.1.2 on 4.08 had its build status changed: internal failure to passing
• aws-sdb.1.2 on 4.10 had its build status changed: internal failure to passing
• aws-sdb.1.2 on 4.11 had its build status changed: internal failure to passing
• aws-sdb.1.2 on 4.12 had its build status changed: internal failure to passing
• aws-sqs.1.2 on 4.06 had its build status changed: internal failure to passing
• aws-sqs.1.2 on 4.07 had its build status changed: internal failure to passing
• aws-sqs.1.2 on 4.08 had its build status changed: internal failure to passing
• aws-sqs.1.2 on 4.10 had its build status changed: internal failure to passing
• aws-sqs.1.2 on 4.11 had its build status changed: internal failure to passing
• aws-ssm.0.1.0 on 4.02 had its build status changed: internal failure to passing
• aws-ssm.0.1.0 on 4.06 had its build status changed: internal failure to passing
• aws-ssm.0.1.0 on 4.07 had its build status changed: internal failure to passing
• aws-ssm.0.1.0 on 4.08 had its build status changed: internal failure to passing
• aws-ssm.0.1.0 on 4.11 had its build status changed: internal failure to passing
• aws-ssm.0.1.0 on 4.12 had its build status changed: internal failure to passing
• aws-ssm.1.2 on 4.07 had its build status changed: internal failure to passing
• aws-ssm.1.2 on 4.08 had its build status changed: internal failure to passing
• aws-ssm.1.2 on 4.09 had its build status changed: internal failure to passing
• aws-ssm.1.2 on 4.11 had its build status changed: internal failure to passing
• aws-ssm.1.2 on 4.12 had its build status changed: internal failure to passing
• aws-sts.0.1.0 on 4.04 had its build status changed: internal failure to passing
• aws-sts.0.1.0 on 4.08 had its build status changed: internal failure to passing
• aws-sts.0.1.0 on 4.09 had its build status changed: internal failure to passing
• aws-sts.0.1.0 on 4.10 had its build status changed: internal failure to passing
• aws-sts.0.1.0 on 4.12 had its build status changed: internal failure to passing
• aws-sts.0.1.0 on 4.13 had its build status changed: internal failure to passing
• aws-sts.1.2 on 4.07 had its build status changed: internal failure to passing
• aws-sts.1.2 on 4.08 had its build status changed: internal failure to passing
• aws-sts.1.2 on 4.09 had its build status changed: internal failure to passing
• aws-sts.1.2 on 4.11 had its build status changed: internal failure to passing
• aws-sts.1.2 on 4.13 had its build status changed: internal failure to passing
• aws.1.0.0 on 4.05 had its build status changed: internal failure to passing
• aws.1.0.0 on 4.10 had its build status changed: internal failure to passing
• aws.1.0.0 on 4.11 had its build status changed: internal failure to passing
• aws.1.0.0 on 4.12 had its build status changed: internal failure to passing
• aws.1.0.0 on 4.13 had its build status changed: internal failure to passing
• aws.1.0.1 on 4.05 had its build status changed: internal failure to passing
• aws.1.0.1 on 4.09 had its build status changed: internal failure to passing
• aws.1.0.1 on 4.10 had its build status changed: internal failure to passing
• aws.1.0.1 on 4.11 had its build status changed: internal failure to passing
• aws.1.0.1 on 4.12 had its build status changed: internal failure to passing
• aws.1.0.1 on 4.14 had its build status changed: internal failure to passing
• aws.1.0.2 on 4.04 had its build status changed: internal failure to passing
• aws.1.0.2 on 4.10 had its build status changed: internal failure to passing
• aws.1.0.2 on 4.11 had its build status changed: internal failure to passing
• aws.1.0.2 on 4.12 had its build status changed: internal failure to passing
• aws.1.0.2 on 4.13 had its build status changed: internal failure to passing
• aws.1.2 on 4.04 had its build status changed: internal failure to passing
• aws.1.2 on 4.11 had its build status changed: internal failure to passing
• aws.1.2 on 4.12 had its build status changed: internal failure to passing
• aws.1.2 on 4.13 had its build status changed: internal failure to passing
• aws.1.2 on 4.14+alpha-repo had its build status changed: internal failure to passing
• azblob-async.0.1.0 on 4.11 had its build status changed: internal failure to passing
• azblob-async.0.1.0 on 4.12 had its build status changed: internal failure to passing
• azblob-async.0.1.0 on 4.13 had its build status changed: internal failure to passing
• azblob-async.0.1.0 on 4.14+alpha-repo had its build status changed: internal failure to passing
• azblob.0.1.0 on 4.11 had its build status changed: internal failure to passing
• azblob.0.1.0 on 4.12 had its build status changed: internal failure to passing
• azblob.0.1.0 on 4.13 had its build status changed: internal failure to passing
• azblob.0.1.0 on 5.0 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.2 on 4.11 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.2 on 4.12 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.2 on 4.13 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.3 on 4.11 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.3 on 4.12 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.3 on 4.13 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.4 on 4.11 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.4 on 4.12 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.4 on 4.13 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.5 on 4.11 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.5 on 4.12 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.5 on 4.14 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.6 on 4.09 had its build status changed: internal failure to passing
• azure-cosmos-db.0.1.6 on 4.12 had its build status changed: internal failure to passing
• bag.1.0.0 on 4.12 had its build status changed: internal failure to passing
• balancer.1.0 on 4.08 had its build status changed: internal failure to passing
• bamboo.0.0.01 on 4.05 had its build status changed: internal failure to passing
• bamboo.0.0.01 on 4.06 had its build status changed: internal failure to passing
• bamboo.0.0.02 on 4.03 had its build status changed: internal failure to passing
• bamboo.0.0.02 on 4.04 had its build status changed: internal failure to passing
• bap-abi.1.1.0 on 4.02 had its build status changed: internal failure to passing
• bap-abi.1.1.0 on 4.03 had its build status changed: internal failure to passing
• bap-abi.1.2.0 on 4.04 had its build status changed: internal failure to passing
• bap-abi.1.3.0 on 4.02 had its build status changed: internal failure to passing
• bap-abi.2.0.0 on 4.06 had its build status changed: internal failure to passing
• bap-abi.2.0.0 on 4.07 had its build status changed: internal failure to passing
• bap-abi.2.2.0 on 4.14+alpha-repo had its build status changed: internal failure to passing
• bap-abi.2.3.0 on 4.12 had its build status changed: internal failure to passing
• bap-abi.2.3.0 on 4.14 had its build status changed: internal failure to passing
• bap-abi.2.4.0 on 4.11 had its build status changed: internal failure to passing
• bap-abi.2.4.0 on 4.12 had its build status changed: internal failure to passing
• bap-abi.2.4.0 on 4.13 had its build status changed: internal failure to passing
• bap-abi.2.5.0 on 4.09 had its build status changed: internal failure to passing
• bap-abi.2.5.0 on 4.10 had its build status changed: internal failure to passing
• bap-abi.2.5.0 on 4.11 had its build status changed: internal failure to passing
• bap-analyze.2.2.0 on 4.08 had its build status changed: internal failure to passing
• bap-analyze.2.2.0 on 4.09 had its build status changed: internal failure to passing
• bap-analyze.2.5.0 on 4.14+alpha-repo had its build status changed: internal failure to passing
• bap-symbol-reader.1.0.0 on 4.02 had its build status changed: partially failing to passing
• base.v0.15.1 on 4.10 is now installable. Current state is: passing
• base.v0.15.1 on 4.11 is now installable. Current state is: passing
• base.v0.15.1 on 4.12 is now installable. Current state is: passing
• base.v0.15.1 on 4.13 is now installable. Current state is: passing
• base.v0.15.1 on 4.14 is now installable. Current state is: passing
• base.v0.15.1 on 4.14+alpha-repo is now installable. Current state is: passing
• base.v0.15.1 on 5.0 is now installable. Current state is: passing
• base.v0.15.1 on 5.0+alpha-repo is now installable. Current state is: passing
• base_bigstring.v0.15.0 on 5.0 had its build status changed: not available to passing
• bechamel-notty.0.1.0 on 4.14 had its build status changed: not available to passing
• bechamel-notty.0.1.0 on 4.14+alpha-repo had its build status changed: failing to passing
• bechamel-notty.0.2.0 on 4.14 had its build status changed: not available to passing
• bechamel-notty.0.2.0 on 4.14+alpha-repo had its build status changed: failing to passing
• bechamel-notty.0.3.0 on 4.14 had its build status changed: not available to passing
• bechamel-notty.0.3.0 on 4.14+alpha-repo had its build status changed: failing to passing
• bechamel-notty.0.3.0 on 5.0 had its build status changed: not available to passing
• bechamel-notty.0.3.0 on 5.0+alpha-repo had its build status changed: failing to passing
• binsec.0.6.0 on 4.13 is now installable. Current state is: passing
• binsec.0.6.0 on 4.14 is now installable. Current state is: passing
• binsec.0.6.0 on 4.14+alpha-repo is now installable. Current state is: passing
• binsec.0.6.1 on 4.09 is now installable. Current state is: passing
• binsec.0.6.1 on 4.10 is now installable. Current state is: passing
• binsec.0.6.1 on 4.11 is now installable. Current state is: passing
• binsec.0.6.1 on 4.12 is now installable. Current state is: passing
• binsec.0.6.1 on 4.13 is now installable. Current state is: passing
• binsec.0.6.1 on 4.14 is now installable. Current state is: passing
• binsec.0.6.1 on 4.14+alpha-repo is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 4.08 is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 4.09 is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 4.10 is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 4.11 is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 4.12 is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 4.13 is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 4.14 is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 5.0 is now installable. Current state is: passing
• bitpack_serializer.0.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 4.08 is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 4.09 is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 4.10 is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 4.11 is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 4.12 is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 4.13 is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 4.14 is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 5.0 is now installable. Current state is: passing
• bitwuzla-c.1.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
• bitwuzla.1.0.3 on 4.08 is now installable. Current state is: passing
• bitwuzla.1.0.3 on 4.09 is now installable. Current state is: passing
• bitwuzla.1.0.3 on 4.10 is now installable. Current state is: passing
• bitwuzla.1.0.3 on 4.11 is now installable. Current state is: passing
• bitwuzla.1.0.3 on 4.12 is now installable. Current state is: passing
• bitwuzla.1.0.3 on 4.13 is now installable. Current state is: passing
• bitwuzla.1.0.3 on 4.14 is now installable. Current state is: passing
• bitwuzla.1.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• bitwuzla.1.0.3 on 5.0 is now installable. Current state is: passing
• bitwuzla.1.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
• blake3.0.3 on 4.09 is now installable. Current state is: passing
• blake3.0.3 on 4.10 is now installable. Current state is: passing
• blake3.0.3 on 4.11 is now installable. Current state is: passing
• blake3.0.3 on 4.12 is now installable. Current state is: passing
• blake3.0.3 on 4.13 is now installable. Current state is: passing
• blake3.0.3 on 4.14 is now installable. Current state is: passing
• blake3.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 4.08 is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 4.09 is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 4.10 is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 4.11 is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 4.12 is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 4.13 is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 4.14 is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 5.0 is now installable. Current state is: passing
• bls12-381-hash.0.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• bls12-381-hash.0.0.2 on 4.12 is now installable. Current state is: passing
• bls12-381-hash.0.0.2 on 4.13 is now installable. Current state is: passing
• bls12-381-hash.0.0.2 on 4.14 is now installable. Current state is: passing
• bls12-381-hash.0.0.2 on 4.14+alpha-repo is now installable. Current state is: passing
• bls12-381-hash.0.0.2 on 5.0 is now installable. Current state is: passing
• bls12-381-hash.0.0.2 on 5.0+alpha-repo is now installable. Current state is: passing
• bls12-381-hash.0.0.3 on 4.12 is now installable. Current state is: passing
• bls12-381-hash.0.0.3 on 4.13 is now installable. Current state is: passing
• bls12-381-hash.0.0.3 on 4.14 is now installable. Current state is: passing
• bls12-381-hash.0.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• bls12-381-hash.0.0.3 on 5.0 is now installable. Current state is: passing
• bls12-381-hash.0.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 4.08 is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 4.09 is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 4.10 is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 4.11 is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 4.12 is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 4.13 is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 4.14 is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 5.0 is now installable. Current state is: passing
• bls12-381-signature.0.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 4.08 is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 4.09 is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 4.10 is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 4.11 is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 4.12 is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 4.13 is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 4.14 is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 5.0 is now installable. Current state is: passing
• bls12-381-signature.1.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• bls12-381.5.0.0 on 4.08 is now installable. Current state is: passing
• bls12-381.5.0.0 on 4.09 is now installable. Current state is: passing
• bls12-381.5.0.0 on 4.10 is now installable. Current state is: passing
• bls12-381.5.0.0 on 4.11 is now installable. Current state is: passing
• bls12-381.5.0.0 on 4.12 is now installable. Current state is: passing
• bls12-381.5.0.0 on 4.13 is now installable. Current state is: passing
• bls12-381.5.0.0 on 4.14 is now installable. Current state is: passing
• bls12-381.5.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• bls12-381.5.0.0 on 5.0 is now installable. Current state is: passing
• bls12-381.5.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• bogue.20221002 on 4.08 is now installable. Current state is: passing
• bogue.20221002 on 4.09 is now installable. Current state is: passing
• bogue.20221002 on 4.10 is now installable. Current state is: passing
• bogue.20221002 on 4.11 is now installable. Current state is: passing
• bogue.20221002 on 4.12 is now installable. Current state is: passing
• bogue.20221002 on 4.13 is now installable. Current state is: passing
• bogue.20221002 on 4.14 is now installable. Current state is: passing
• bogue.20221002 on 4.14+alpha-repo is now installable. Current state is: passing
• bogue.20221002 on 5.0 is now installable. Current state is: passing
• bogue.20221002 on 5.0+alpha-repo is now installable. Current state is: passing
• box.1.2.0 on 4.08 is now installable. Current state is: passing
• box.1.2.0 on 4.09 is now installable. Current state is: passing
• box.1.2.0 on 4.10 is now installable. Current state is: passing
• box.1.2.0 on 4.11 is now installable. Current state is: passing
• box.1.2.0 on 4.12 is now installable. Current state is: passing
• box.1.2.0 on 4.13 is now installable. Current state is: passing
• box.1.2.0 on 4.14 is now installable. Current state is: passing
• box.1.2.0 on 4.14+alpha-repo is now installable. Current state is: passing
• brr-lwd.0.3 on 4.08 is now installable. Current state is: passing
• brr-lwd.0.3 on 4.09 is now installable. Current state is: passing
• brr-lwd.0.3 on 4.10 is now installable. Current state is: passing
• brr-lwd.0.3 on 4.11 is now installable. Current state is: passing
• brr-lwd.0.3 on 4.12 is now installable. Current state is: passing
• brr-lwd.0.3 on 4.13 is now installable. Current state is: passing
• brr-lwd.0.3 on 4.14 is now installable. Current state is: passing
• brr-lwd.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• brr-lwd.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
• bst.7.0.1 on 4.02 is now installable. Current state is: passing
• bst.7.0.1 on 4.03 is now installable. Current state is: passing
• bst.7.0.1 on 4.04 is now installable. Current state is: passing
• bst.7.0.1 on 4.05 is now installable. Current state is: passing
• bst.7.0.1 on 4.06 is now installable. Current state is: passing
• bst.7.0.1 on 4.07 is now installable. Current state is: passing
• bst.7.0.1 on 4.08 is now installable. Current state is: passing
• bst.7.0.1 on 4.09 is now installable. Current state is: passing
• bst.7.0.1 on 4.10 is now installable. Current state is: passing
• bst.7.0.1 on 4.11 is now installable. Current state is: passing
• bst.7.0.1 on 4.12 is now installable. Current state is: passing
• bst.7.0.1 on 4.13 is now installable. Current state is: passing
• bst.7.0.1 on 4.14 is now installable. Current state is: passing
• bst.7.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• builder.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• builder.0.1.1 on 5.0+alpha-repo had its build status changed: partially failing to passing
• builder.0.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
• builder.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• builder.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• builder.0.3.1 on 5.0+alpha-repo had its build status changed: partially failing to passing
• bytebuffer.0.0.2 on 5.0 had its build status changed: not available to passing
• ca-certs-nss.3.83 on 4.08 is now installable. Current state is: passing
• ca-certs-nss.3.83 on 4.09 is now installable. Current state is: passing
• ca-certs-nss.3.83 on 4.10 is now installable. Current state is: passing
• ca-certs-nss.3.83 on 4.11 is now installable. Current state is: passing
• ca-certs-nss.3.83 on 4.12 is now installable. Current state is: passing
• ca-certs-nss.3.83 on 4.13 is now installable. Current state is: passing
• ca-certs-nss.3.83 on 4.14 is now installable. Current state is: passing
• ca-certs-nss.3.83 on 4.14+alpha-repo is now installable. Current state is: passing
• ca-certs-nss.3.83 on 5.0 is now installable. Current state is: passing
• ca-certs-nss.3.83 on 5.0+alpha-repo is now installable. Current state is: passing
• ca-certs.0.2.3 on 4.08 is now installable. Current state is: passing
• ca-certs.0.2.3 on 4.09 is now installable. Current state is: passing
• ca-certs.0.2.3 on 4.10 is now installable. Current state is: passing
• ca-certs.0.2.3 on 4.11 is now installable. Current state is: passing
• ca-certs.0.2.3 on 4.12 is now installable. Current state is: passing
• ca-certs.0.2.3 on 4.13 is now installable. Current state is: passing
• ca-certs.0.2.3 on 4.14 is now installable. Current state is: passing
• ca-certs.0.2.3 on 4.14+alpha-repo is now installable. Current state is: passing
• ca-certs.0.2.3 on 5.0 is now installable. Current state is: passing
• ca-certs.0.2.3 on 5.0+alpha-repo is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.03 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.04 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.05 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.06 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.07 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.08 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.09 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.10 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.11 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.12 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.13 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.14 is now installable. Current state is: passing
• cairo2-gtk.0.6.4 on 4.14+alpha-repo is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.03 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.04 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.05 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.06 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.07 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.08 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.09 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.10 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.11 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.12 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.13 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.14 is now installable. Current state is: passing
• cairo2-pango.0.6.4 on 4.14+alpha-repo is now installable. Current state is: passing
• cairo2.0.6.4 on 4.03 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.04 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.05 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.06 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.07 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.08 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.09 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.10 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.11 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.12 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.13 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.14 is now installable. Current state is: passing
• cairo2.0.6.4 on 4.14+alpha-repo is now installable. Current state is: passing
• cairo2.0.6.4 on 5.0 is now installable. Current state is: passing
• cairo2.0.6.4 on 5.0+alpha-repo is now installable. Current state is: passing
• camels.0.0.3 on 4.14 had its build status changed: not available to passing
• camels.0.0.3 on 4.14+alpha-repo had its build status changed: failing to passing
• camels.0.0.3 on 5.0 had its build status changed: not available to passing
• camels.0.0.3 on 5.0+alpha-repo had its build status changed: failing to passing
• camels.0.0.4 on 4.14 had its build status changed: not available to passing
• camels.0.0.4 on 4.14+alpha-repo had its build status changed: failing to passing
• camels.0.0.4 on 5.0 had its build status changed: not available to passing
• camels.0.0.4 on 5.0+alpha-repo had its build status changed: failing to passing
• caqti-async.1.9.0 on 4.04 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.05 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.06 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.07 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.08 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.09 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.10 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.11 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.12 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.13 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.14 is now installable. Current state is: passing
• caqti-async.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• caqti-async.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.07 is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.08 is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.09 is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.10 is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.11 is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.12 is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.13 is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.14 is now installable. Current state is: passing
• caqti-driver-mariadb.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 4.08 is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 4.09 is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 4.10 is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 4.11 is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 4.12 is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 4.13 is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 4.14 is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 5.0 is now installable. Current state is: passing
• caqti-driver-postgresql.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.04 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.05 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.06 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.07 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.08 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.09 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.10 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.11 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.12 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.13 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.14 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 5.0 is now installable. Current state is: passing
• caqti-driver-sqlite3.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.04 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.05 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.06 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.07 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.08 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.09 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.10 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.11 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.12 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.13 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.14 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 5.0 is now installable. Current state is: passing
• caqti-lwt.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.04 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.05 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.06 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.07 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.08 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.09 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.10 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.11 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.12 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.13 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.14 is now installable. Current state is: passing
• caqti-type-calendar.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• caqti.1.9.0 on 4.04 is now installable. Current state is: passing
• caqti.1.9.0 on 4.05 is now installable. Current state is: passing
• caqti.1.9.0 on 4.06 is now installable. Current state is: passing
• caqti.1.9.0 on 4.07 is now installable. Current state is: passing
• caqti.1.9.0 on 4.08 is now installable. Current state is: passing
• caqti.1.9.0 on 4.09 is now installable. Current state is: passing
• caqti.1.9.0 on 4.10 is now installable. Current state is: passing
• caqti.1.9.0 on 4.11 is now installable. Current state is: passing
• caqti.1.9.0 on 4.12 is now installable. Current state is: passing
• caqti.1.9.0 on 4.13 is now installable. Current state is: passing
• caqti.1.9.0 on 4.14 is now installable. Current state is: passing
• caqti.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• caqti.1.9.0 on 5.0 is now installable. Current state is: passing
• caqti.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• carton-git.0.5.0 on 4.08 is now installable. Current state is: passing
• carton-git.0.5.0 on 4.09 is now installable. Current state is: passing
• carton-git.0.5.0 on 4.10 is now installable. Current state is: passing
• carton-git.0.5.0 on 4.11 is now installable. Current state is: passing
• carton-git.0.5.0 on 4.12 is now installable. Current state is: passing
• carton-git.0.5.0 on 4.13 is now installable. Current state is: passing
• carton-git.0.5.0 on 4.14 is now installable. Current state is: passing
• carton-git.0.5.0 on 4.14+alpha-repo is now installable. Current state is: passing
• carton-git.0.5.0 on 5.0 is now installable. Current state is: passing
• carton-git.0.5.0 on 5.0+alpha-repo is now installable. Current state is: passing
• carton-lwt.0.5.0 on 4.08 is now installable. Current state is: passing
• carton-lwt.0.5.0 on 4.09 is now installable. Current state is: passing
• carton-lwt.0.5.0 on 4.10 is now installable. Current state is: passing
• carton-lwt.0.5.0 on 4.11 is now installable. Current state is: passing
• carton-lwt.0.5.0 on 4.12 is now installable. Current state is: passing
• carton-lwt.0.5.0 on 4.13 is now installable. Current state is: passing
• carton-lwt.0.5.0 on 4.14 is now installable. Current state is: passing
• carton-lwt.0.5.0 on 4.14+alpha-repo is now installable. Current state is: passing
• carton-lwt.0.5.0 on 5.0 is now installable. Current state is: passing
• carton-lwt.0.5.0 on 5.0+alpha-repo is now installable. Current state is: passing
• carton.0.5.0 on 4.08 is now installable. Current state is: passing
• carton.0.5.0 on 4.09 is now installable. Current state is: passing
• carton.0.5.0 on 4.10 is now installable. Current state is: passing
• carton.0.5.0 on 4.11 is now installable. Current state is: passing
• carton.0.5.0 on 4.12 is now installable. Current state is: passing
• carton.0.5.0 on 4.13 is now installable. Current state is: passing
• carton.0.5.0 on 4.14 is now installable. Current state is: passing
• carton.0.5.0 on 4.14+alpha-repo is now installable. Current state is: passing
• carton.0.5.0 on 5.0 is now installable. Current state is: passing
• carton.0.5.0 on 5.0+alpha-repo is now installable. Current state is: passing
• cca.0.6.2 on 4.14 is now installable. Current state is: passing
• cca.0.6.2 on 4.14+alpha-repo is now installable. Current state is: passing
• checkseum.0.4.0 on 4.07 is now installable. Current state is: passing
• checkseum.0.4.0 on 4.08 is now installable. Current state is: passing
• checkseum.0.4.0 on 4.09 is now installable. Current state is: passing
• checkseum.0.4.0 on 4.10 is now installable. Current state is: passing
• checkseum.0.4.0 on 4.11 is now installable. Current state is: passing
• checkseum.0.4.0 on 4.12 is now installable. Current state is: passing
• checkseum.0.4.0 on 4.13 is now installable. Current state is: passing
• checkseum.0.4.0 on 4.14 is now installable. Current state is: passing
• checkseum.0.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• checkseum.0.4.0 on 5.0 is now installable. Current state is: passing
• checkseum.0.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• clangml.4.8.0 on 4.08 is now installable. Current state is: passing
• clangml.4.8.0 on 4.09 is now installable. Current state is: passing
• clangml.4.8.0 on 4.10 is now installable. Current state is: passing
• clangml.4.8.0 on 4.11 is now installable. Current state is: passing
• clangml.4.8.0 on 4.12 is now installable. Current state is: passing
• clangml.4.8.0 on 4.13 is now installable. Current state is: passing
• clangml.4.8.0 on 4.14 is now installable. Current state is: passing
• clangml.4.8.0 on 4.14+alpha-repo is now installable. Current state is: passing
• clangml.4.8.0 on 5.0 is now installable. Current state is: passing
• clangml.4.8.0 on 5.0+alpha-repo is now installable. Current state is: passing
• combinat.1.0 on 5.0 had its build status changed: not available to passing
• combine.0.6 on 4.13 had its build status changed: internal failure to passing
• conduit-async.6.0.0 on 4.11 is now installable. Current state is: passing
• conduit-async.6.0.0 on 4.12 is now installable. Current state is: passing
• conduit-async.6.0.0 on 4.13 is now installable. Current state is: passing
• conduit-async.6.0.0 on 4.14 is now installable. Current state is: passing
• conduit-async.6.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• conduit-async.6.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.07 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.08 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.09 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.10 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.11 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.12 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.13 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.14 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 5.0 is now installable. Current state is: passing
• conduit-lwt-unix.6.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.04 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.05 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.06 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.07 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.08 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.09 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.10 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.11 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.12 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.13 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.14 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 5.0 is now installable. Current state is: passing
• conduit-lwt.6.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 4.08 is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 4.09 is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 4.10 is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 4.11 is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 4.12 is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 4.13 is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 4.14 is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• conduit-mirage.6.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• conduit.6.0.0 on 4.04 is now installable. Current state is: passing
• conduit.6.0.0 on 4.05 is now installable. Current state is: passing
• conduit.6.0.0 on 4.06 is now installable. Current state is: passing
• conduit.6.0.0 on 4.07 is now installable. Current state is: passing
• conduit.6.0.0 on 4.08 is now installable. Current state is: passing
• conduit.6.0.0 on 4.09 is now installable. Current state is: passing
• conduit.6.0.0 on 4.10 is now installable. Current state is: passing
• conduit.6.0.0 on 4.11 is now installable. Current state is: passing
• conduit.6.0.0 on 4.12 is now installable. Current state is: passing
• conduit.6.0.0 on 4.13 is now installable. Current state is: passing
• conduit.6.0.0 on 4.14 is now installable. Current state is: passing
• conduit.6.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• conduit.6.0.0 on 5.0 is now installable. Current state is: passing
• conduit.6.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• conf-guile.1 on 4.02 is now installable. Current state is: passing
• conf-guile.1 on 4.03 is now installable. Current state is: passing
• conf-guile.1 on 4.04 is now installable. Current state is: passing
• conf-guile.1 on 4.05 is now installable. Current state is: passing
• conf-guile.1 on 4.06 is now installable. Current state is: passing
• conf-guile.1 on 4.07 is now installable. Current state is: passing
• conf-guile.1 on 4.08 is now installable. Current state is: passing
• conf-guile.1 on 4.09 is now installable. Current state is: passing
• conf-guile.1 on 4.10 is now installable. Current state is: passing
• conf-guile.1 on 4.11 is now installable. Current state is: passing
• conf-guile.1 on 4.12 is now installable. Current state is: passing
• conf-guile.1 on 4.13 is now installable. Current state is: passing
• conf-guile.1 on 4.14 is now installable. Current state is: passing
• conf-guile.1 on 4.14+alpha-repo is now installable. Current state is: passing
• conf-guile.1 on 5.0 is now installable. Current state is: passing
• conf-guile.1 on 5.0+alpha-repo is now installable. Current state is: passing
• conf-libclang.15 on 4.02 is now installable. Current state is: passing
• conf-libclang.15 on 4.03 is now installable. Current state is: passing
• conf-libclang.15 on 4.04 is now installable. Current state is: passing
• conf-libclang.15 on 4.05 is now installable. Current state is: passing
• conf-libclang.15 on 4.06 is now installable. Current state is: passing
• conf-libclang.15 on 4.07 is now installable. Current state is: passing
• conf-libclang.15 on 4.08 is now installable. Current state is: passing
• conf-libclang.15 on 4.09 is now installable. Current state is: passing
• conf-libclang.15 on 4.10 is now installable. Current state is: passing
• conf-libclang.15 on 4.11 is now installable. Current state is: passing
• conf-libclang.15 on 4.12 is now installable. Current state is: passing
• conf-libclang.15 on 4.13 is now installable. Current state is: passing
• conf-libclang.15 on 4.14 is now installable. Current state is: passing
• conf-libclang.15 on 4.14+alpha-repo is now installable. Current state is: passing
• conf-libclang.15 on 5.0 is now installable. Current state is: passing
• conf-libclang.15 on 5.0+alpha-repo is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.02 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.03 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.04 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.05 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.06 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.07 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.08 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.09 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.10 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.11 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.12 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.13 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.14 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 4.14+alpha-repo is now installable. Current state is: passing
• conf-srt-gnutls.1 on 5.0 is now installable. Current state is: passing
• conf-srt-gnutls.1 on 5.0+alpha-repo is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.02 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.03 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.04 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.05 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.06 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.07 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.08 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.09 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.10 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.11 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.12 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.13 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.14 is now installable. Current state is: passing
• conf-srt-openssl.1 on 4.14+alpha-repo is now installable. Current state is: passing
• conf-srt-openssl.1 on 5.0 is now installable. Current state is: passing
• conf-srt-openssl.1 on 5.0+alpha-repo is now installable. Current state is: passing
• conf-srt.2 on 4.02 is now installable. Current state is: passing
• conf-srt.2 on 4.03 is now installable. Current state is: passing
• conf-srt.2 on 4.04 is now installable. Current state is: passing
• conf-srt.2 on 4.05 is now installable. Current state is: passing
• conf-srt.2 on 4.06 is now installable. Current state is: passing
• conf-srt.2 on 4.07 is now installable. Current state is: passing
• conf-srt.2 on 4.08 is now installable. Current state is: passing
• conf-srt.2 on 4.09 is now installable. Current state is: passing
• conf-srt.2 on 4.10 is now installable. Current state is: passing
• conf-srt.2 on 4.11 is now installable. Current state is: passing
• conf-srt.2 on 4.12 is now installable. Current state is: passing
• conf-srt.2 on 4.13 is now installable. Current state is: passing
• conf-srt.2 on 4.14 is now installable. Current state is: passing
• conf-srt.2 on 4.14+alpha-repo is now installable. Current state is: passing
• conf-srt.2 on 5.0 is now installable. Current state is: passing
• conf-srt.2 on 5.0+alpha-repo is now installable. Current state is: passing
• conf-xxhash.1 on 4.02 is now installable. Current state is: passing
• conf-xxhash.1 on 4.03 is now installable. Current state is: passing
• conf-xxhash.1 on 4.04 is now installable. Current state is: passing
• conf-xxhash.1 on 4.05 is now installable. Current state is: passing
• conf-xxhash.1 on 4.06 is now installable. Current state is: passing
• conf-xxhash.1 on 4.07 is now installable. Current state is: passing
• conf-xxhash.1 on 4.08 is now installable. Current state is: passing
• conf-xxhash.1 on 4.09 is now installable. Current state is: passing
• conf-xxhash.1 on 4.10 is now installable. Current state is: passing
• conf-xxhash.1 on 4.11 is now installable. Current state is: passing
• conf-xxhash.1 on 4.12 is now installable. Current state is: passing
• conf-xxhash.1 on 4.13 is now installable. Current state is: passing
• conf-xxhash.1 on 4.14 is now installable. Current state is: passing
• conf-xxhash.1 on 4.14+alpha-repo is now installable. Current state is: passing
• conf-xxhash.1 on 5.0 is now installable. Current state is: passing
• conf-xxhash.1 on 5.0+alpha-repo is now installable. Current state is: passing
• conjury.2.1 on 4.08 had its build status changed: failing to passing
• conjury.2.1 on 4.09 had its build status changed: failing to passing
• conjury.2.1 on 4.10 had its build status changed: failing to passing
• conjury.2.1 on 4.11 had its build status changed: failing to passing
• conjury.2.1 on 4.12 had its build status changed: failing to passing
• conjury.2.1 on 4.13 had its build status changed: failing to passing
• conjury.2.1 on 4.14 had its build status changed: failing to passing
• conjury.2.1 on 4.14+alpha-repo had its build status changed: failing to passing
• conjury.2.1.1 on 4.08 is now installable. Current state is: passing
• conjury.2.1.1 on 4.09 is now installable. Current state is: passing
• conjury.2.1.1 on 4.10 is now installable. Current state is: passing
• conjury.2.1.1 on 4.11 is now installable. Current state is: passing
• conjury.2.1.1 on 4.12 is now installable. Current state is: passing
• conjury.2.1.1 on 4.13 is now installable. Current state is: passing
• conjury.2.1.1 on 4.14 is now installable. Current state is: passing
• conjury.2.1.1 on 4.14+alpha-repo is now installable. Current state is: passing
• coq-serapi.8.11.0+0.11.0 on 4.07 had its build status changed: partially failing to passing
• coq-serapi.8.13.0+0.13.0 on 4.08 had its build status changed: partially failing to passing
• coq-serapi.8.13.0+0.13.1 on 4.13 had its build status changed: partially failing to passing
• coq-serapi.8.15.0+0.15.1 on 4.07 had its build status changed: partially failing to passing
• coq-serapi.8.16.0+0.16.0 on 4.09 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.0 on 4.10 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.0 on 4.11 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.0 on 4.12 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.0 on 4.13 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.0 on 4.14 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.0 on 4.14+alpha-repo is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.1 on 4.09 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.1 on 4.10 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.1 on 4.11 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.1 on 4.12 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.1 on 4.13 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.1 on 4.14 is now installable. Current state is: passing
• coq-serapi.8.16.0+0.16.1 on 4.14+alpha-repo is now installable. Current state is: passing
• coq-serapi.8.7.1+0.4.12 on 4.06 had its build status changed: partially failing to passing
• coq-serapi.8.8.0+0.5.4 on 4.08 had its build status changed: partially failing to passing
• coq-serapi.8.8.0+0.5.6 on 4.09 had its build status changed: partially failing to passing
• coq.8.11.1 on 4.07 had its build status changed: failing to passing
• coq.8.12.2 on 4.07 had its build status changed: failing to passing
• coq.8.13.1 on 4.05 had its build status changed: failing to passing
• coq.8.14.1 on 4.10 had its build status changed: failing to passing
• coq.8.16.0 on 4.10 is now installable. Current state is: passing
• coq.8.16.0 on 4.11 is now installable. Current state is: passing
• coq.8.16.0 on 4.12 is now installable. Current state is: passing
• coq.8.16.0 on 4.13 is now installable. Current state is: passing
• coq.8.16.0 on 4.14 is now installable. Current state is: passing
• coq.8.16.0 on 4.14+alpha-repo is now installable. Current state is: passing
• coq.8.7.0 on 4.07 had its build status changed: partially failing to passing
• coq.8.7.2 on 4.06 had its build status changed: partially failing to passing
• coqide.8.16.0 on 4.09 is now installable. Current state is: passing
• coqide.8.16.0 on 4.10 is now installable. Current state is: passing
• coqide.8.16.0 on 4.11 is now installable. Current state is: passing
• coqide.8.16.0 on 4.12 is now installable. Current state is: passing
• coqide.8.16.0 on 4.13 is now installable. Current state is: passing
• coqide.8.16.0 on 4.14 is now installable. Current state is: passing
• coqide.8.16.0 on 4.14+alpha-repo is now installable. Current state is: passing
• cpm.12.1.2 on 4.02 is now installable. Current state is: passing
• cpm.12.1.2 on 4.03 is now installable. Current state is: passing
• cpm.12.1.2 on 4.04 is now installable. Current state is: passing
• cpm.12.1.2 on 4.05 is now installable. Current state is: passing
• cpm.12.1.2 on 4.06 is now installable. Current state is: passing
• cpm.12.1.2 on 4.07 is now installable. Current state is: passing
• cpm.12.1.2 on 4.08 is now installable. Current state is: passing
• cpm.12.1.2 on 4.09 is now installable. Current state is: passing
• cpm.12.1.2 on 4.10 is now installable. Current state is: passing
• cpm.12.1.2 on 4.11 is now installable. Current state is: passing
• cpm.12.1.2 on 4.12 is now installable. Current state is: passing
• cpm.12.1.2 on 4.13 is now installable. Current state is: passing
• cpm.12.1.2 on 4.14 is now installable. Current state is: passing
• cpm.12.1.2 on 4.14+alpha-repo is now installable. Current state is: passing
• dap.1.0.0 on 5.0 had its build status changed: not available to passing
• dap.1.0.1 on 5.0 had its build status changed: not available to passing
• dap.1.0.2 on 5.0 had its build status changed: not available to passing
• dap.1.0.3 on 5.0 had its build status changed: not available to passing
• dap.1.0.4 on 5.0 had its build status changed: not available to passing
• dap.1.0.5 on 5.0 had its build status changed: not available to passing
• dap.1.0.6 on 5.0 had its build status changed: not available to passing
• data-encoding.0.7 on 4.10 is now installable. Current state is: passing
• data-encoding.0.7 on 4.11 is now installable. Current state is: passing
• data-encoding.0.7 on 4.12 is now installable. Current state is: passing
• data-encoding.0.7 on 4.13 is now installable. Current state is: passing
• data-encoding.0.7 on 4.14 is now installable. Current state is: passing
• data-encoding.0.7 on 4.14+alpha-repo is now installable. Current state is: passing
• data-encoding.0.7 on 5.0 is now installable. Current state is: passing
• data-encoding.0.7 on 5.0+alpha-repo is now installable. Current state is: passing
• dates_calc.0.0.3 on 4.11 is now installable. Current state is: passing
• dates_calc.0.0.3 on 4.12 is now installable. Current state is: passing
• dates_calc.0.0.3 on 4.13 is now installable. Current state is: passing
• dates_calc.0.0.3 on 4.14 is now installable. Current state is: passing
• dates_calc.0.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• dates_calc.0.0.3 on 5.0 is now installable. Current state is: passing
• dates_calc.0.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
• dates_calc.0.0.4 on 4.11 is now installable. Current state is: passing
• dates_calc.0.0.4 on 4.12 is now installable. Current state is: passing
• dates_calc.0.0.4 on 4.13 is now installable. Current state is: passing
• dates_calc.0.0.4 on 4.14 is now installable. Current state is: passing
• dates_calc.0.0.4 on 4.14+alpha-repo is now installable. Current state is: passing
• dates_calc.0.0.4 on 5.0 is now installable. Current state is: passing
• dates_calc.0.0.4 on 5.0+alpha-repo is now installable. Current state is: passing
• decoders-jsonaf.1.0.0 on 5.0 had its build status changed: not available to passing
• decompress.1.5.0 on 4.08 is now installable. Current state is: passing
• decompress.1.5.0 on 4.09 is now installable. Current state is: passing
• decompress.1.5.0 on 4.10 is now installable. Current state is: passing
• decompress.1.5.0 on 4.11 is now installable. Current state is: passing
• decompress.1.5.0 on 4.12 is now installable. Current state is: passing
• decompress.1.5.0 on 4.13 is now installable. Current state is: passing
• decompress.1.5.0 on 4.14 is now installable. Current state is: passing
• decompress.1.5.0 on 4.14+alpha-repo is now installable. Current state is: passing
• decompress.1.5.0 on 5.0 is now installable. Current state is: passing
• decompress.1.5.0 on 5.0+alpha-repo is now installable. Current state is: passing
• decompress.1.5.1 on 4.08 is now installable. Current state is: passing
• decompress.1.5.1 on 4.09 is now installable. Current state is: passing
• decompress.1.5.1 on 4.10 is now installable. Current state is: passing
• decompress.1.5.1 on 4.11 is now installable. Current state is: passing
• decompress.1.5.1 on 4.12 is now installable. Current state is: passing
• decompress.1.5.1 on 4.13 is now installable. Current state is: passing
• decompress.1.5.1 on 4.14 is now installable. Current state is: passing
• decompress.1.5.1 on 4.14+alpha-repo is now installable. Current state is: passing
• decompress.1.5.1 on 5.0 is now installable. Current state is: passing
• decompress.1.5.1 on 5.0+alpha-repo is now installable. Current state is: passing
• delimited_parsing.v0.11.0 on 4.05 had its build status changed: partially failing to passing
• docker_hub.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• docteur-unix.0.0.3 on 4.14+alpha-repo had its build status changed: partially failing to passing
• docteur-unix.0.0.4 on 4.14+alpha-repo had its build status changed: partially failing to passing
• docteur-unix.0.0.5 on 4.14+alpha-repo had its build status changed: partially failing to passing
• docteur.0.0.3 on 4.14+alpha-repo had its build status changed: partially failing to passing
• docteur.0.0.4 on 4.14+alpha-repo had its build status changed: partially failing to passing
• docteur.0.0.5 on 4.14+alpha-repo had its build status changed: partially failing to passing
• domainslib.0.5.0 on 5.0 is now installable. Current state is: passing
• domainslib.0.5.0 on 5.0+alpha-repo is now installable. Current state is: passing
• duration.0.2.1 on 4.04 is now installable. Current state is: passing
• duration.0.2.1 on 4.05 is now installable. Current state is: passing
• duration.0.2.1 on 4.06 is now installable. Current state is: passing
• duration.0.2.1 on 4.07 is now installable. Current state is: passing
• duration.0.2.1 on 4.08 is now installable. Current state is: passing
• duration.0.2.1 on 4.09 is now installable. Current state is: passing
• duration.0.2.1 on 4.10 is now installable. Current state is: passing
• duration.0.2.1 on 4.11 is now installable. Current state is: passing
• duration.0.2.1 on 4.12 is now installable. Current state is: passing
• duration.0.2.1 on 4.13 is now installable. Current state is: passing
• duration.0.2.1 on 4.14 is now installable. Current state is: passing
• duration.0.2.1 on 4.14+alpha-repo is now installable. Current state is: passing
• duration.0.2.1 on 5.0 is now installable. Current state is: passing
• duration.0.2.1 on 5.0+alpha-repo is now installable. Current state is: passing
• equinoxe-hlc.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• equinoxe.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• esperanto-cosmopolitan.0.0.1 on 4.02 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.03 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.04 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.05 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.06 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.07 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.08 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.09 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.10 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.11 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.12 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.13 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.14 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 5.0 is now installable. Current state is: passing
• esperanto-cosmopolitan.0.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• esperanto.0.0.1 on 4.13 is now installable. Current state is: passing
• ez_cmdliner.0.2.0 on 5.0 had its build status changed: not available to passing
• ez_cmdliner.0.4.0 on 5.0 had its build status changed: not available to passing
• ez_cmdliner.0.4.3 on 5.0 had its build status changed: not available to passing
• ez_file.0.3.0 on 5.0 had its build status changed: not available to passing
• ez_hash.0.5.3 on 4.03 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.04 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.05 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.06 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.07 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.08 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.09 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.10 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.11 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.12 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.13 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.14 is now installable. Current state is: passing
• ez_hash.0.5.3 on 4.14+alpha-repo is now installable. Current state is: passing
• ez_hash.0.5.3 on 5.0 is now installable. Current state is: passing
• ez_hash.0.5.3 on 5.0+alpha-repo is now installable. Current state is: passing
• feather.0.2.0 on 5.0 had its build status changed: not available to passing
• feather.0.3.0 on 5.0 had its build status changed: not available to passing
• ffmpeg-av.1.0.0 on 4.14+alpha-repo had its build status changed: internal failure to passing
• ffmpeg-av.1.0.0~rc1 on 4.11 had its build status changed: internal failure to passing
• ffmpeg-av.1.1.5 on 4.08 is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 4.09 is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 4.10 is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 4.11 is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 4.12 is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 4.13 is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 4.14 is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 5.0 is now installable. Current state is: passing
• ffmpeg-av.1.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 4.08 is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 4.09 is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 4.10 is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 4.11 is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 4.12 is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 4.13 is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 4.14 is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 5.0 is now installable. Current state is: passing
• ffmpeg-av.1.1.6 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-avcodec.1.0.0 on 4.11 had its build status changed: internal failure to passing
• ffmpeg-avcodec.1.0.0~rc1 on 4.13 had its build status changed: internal failure to passing
• ffmpeg-avcodec.1.1.5 on 4.08 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 4.09 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 4.10 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 4.11 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 4.12 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 4.13 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 4.14 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 5.0 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 4.08 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 4.09 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 4.10 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 4.11 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 4.12 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 4.13 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 4.14 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 5.0 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.6 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-avdevice.1.0.0 on 4.10 had its build status changed: internal failure to passing
• ffmpeg-avdevice.1.0.0 on 4.14+alpha-repo had its build status changed: internal failure to passing
• ffmpeg-avdevice.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: internal failure to passing
• ffmpeg-avdevice.1.1.5 on 4.08 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 4.09 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 4.10 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 4.11 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 4.12 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 4.13 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 4.14 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 5.0 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 4.08 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 4.09 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 4.10 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 4.11 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 4.12 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 4.13 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 4.14 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 5.0 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.6 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-avfilter.1.0.0~rc1 on 4.14+alpha-repo had its build status changed: internal failure to passing
• ffmpeg-avfilter.1.1.5 on 4.08 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 4.09 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 4.10 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 4.11 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 4.12 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 4.13 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 4.14 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 5.0 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 4.08 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 4.09 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 4.10 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 4.11 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 4.12 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 4.13 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 4.14 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 5.0 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.6 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-avutil.1.0.0 on 4.12 had its build status changed: internal failure to passing
• ffmpeg-avutil.1.1.5 on 4.08 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 4.09 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 4.10 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 4.11 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 4.12 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 4.13 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 4.14 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 5.0 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 4.08 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 4.09 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 4.10 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 4.11 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 4.12 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 4.13 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 4.14 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 5.0 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.6 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 4.08 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 4.09 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 4.10 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 4.11 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 4.12 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 4.13 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 4.14 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 5.0 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 4.08 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 4.09 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 4.10 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 4.11 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 4.12 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 4.13 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 4.14 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 5.0 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.6 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-swscale.1.0.0 on 5.0 had its build status changed: internal failure to passing
• ffmpeg-swscale.1.1.5 on 4.08 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 4.09 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 4.10 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 4.11 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 4.12 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 4.13 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 4.14 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 5.0 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 4.08 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 4.09 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 4.10 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 4.11 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 4.12 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 4.13 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 4.14 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 5.0 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.6 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg.1.1.5 on 4.08 is now installable. Current state is: passing
• ffmpeg.1.1.5 on 4.09 is now installable. Current state is: passing
• ffmpeg.1.1.5 on 4.10 is now installable. Current state is: passing
• ffmpeg.1.1.5 on 4.11 is now installable. Current state is: passing
• ffmpeg.1.1.5 on 4.12 is now installable. Current state is: passing
• ffmpeg.1.1.5 on 4.13 is now installable. Current state is: passing
• ffmpeg.1.1.5 on 4.14 is now installable. Current state is: passing
• ffmpeg.1.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg.1.1.5 on 5.0 is now installable. Current state is: passing
• ffmpeg.1.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• ffmpeg.1.1.6 on 4.08 is now installable. Current state is: passing
• ffmpeg.1.1.6 on 4.09 is now installable. Current state is: passing
• ffmpeg.1.1.6 on 4.10 is now installable. Current state is: passing
• ffmpeg.1.1.6 on 4.11 is now installable. Current state is: passing
• ffmpeg.1.1.6 on 4.12 is now installable. Current state is: passing
• ffmpeg.1.1.6 on 4.13 is now installable. Current state is: passing
• ffmpeg.1.1.6 on 4.14 is now installable. Current state is: passing
• ffmpeg.1.1.6 on 4.14+alpha-repo is now installable. Current state is: passing
• ffmpeg.1.1.6 on 5.0 is now installable. Current state is: passing
• ffmpeg.1.1.6 on 5.0+alpha-repo is now installable. Current state is: passing
• frama-c-lannotate.0.2 on 4.08 is now installable. Current state is: passing
• frama-c-lannotate.0.2 on 4.09 is now installable. Current state is: passing
• frama-c-lannotate.0.2 on 4.10 is now installable. Current state is: passing
• frama-c-lannotate.0.2 on 4.11 is now installable. Current state is: passing
• frama-c-lannotate.0.2 on 4.12 is now installable. Current state is: passing
• frama-c-lannotate.0.2 on 4.13 is now installable. Current state is: passing
• frama-c-lannotate.0.2 on 4.14 is now installable. Current state is: passing
• frama-c-lannotate.0.2 on 4.14+alpha-repo is now installable. Current state is: passing
• frama-c-luncov.0.2 on 4.08 is now installable. Current state is: passing
• frama-c-luncov.0.2 on 4.09 is now installable. Current state is: passing
• frama-c-luncov.0.2 on 4.10 is now installable. Current state is: passing
• frama-c-luncov.0.2 on 4.11 is now installable. Current state is: passing
• frama-c-luncov.0.2 on 4.12 is now installable. Current state is: passing
• frama-c-luncov.0.2 on 4.13 is now installable. Current state is: passing
• frama-c-luncov.0.2 on 4.14 is now installable. Current state is: passing
• frama-c-luncov.0.2 on 4.14+alpha-repo is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 4.08 is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 4.09 is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 4.10 is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 4.11 is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 4.12 is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 4.13 is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 4.14 is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 4.14+alpha-repo is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 5.0 is now installable. Current state is: passing
• functoria-runtime.4.2.1 on 5.0+alpha-repo is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 4.08 is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 4.09 is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 4.10 is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 4.11 is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 4.12 is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 4.13 is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 4.14 is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 4.14+alpha-repo is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 5.0 is now installable. Current state is: passing
• functoria-runtime.4.3.0 on 5.0+alpha-repo is now installable. Current state is: passing
• functoria.4.2.1 on 4.08 is now installable. Current state is: passing
• functoria.4.2.1 on 4.09 is now installable. Current state is: passing
• functoria.4.2.1 on 4.10 is now installable. Current state is: passing
• functoria.4.2.1 on 4.11 is now installable. Current state is: passing
• functoria.4.2.1 on 4.12 is now installable. Current state is: passing
• functoria.4.2.1 on 4.13 is now installable. Current state is: passing
• functoria.4.2.1 on 4.14 is now installable. Current state is: passing
• functoria.4.2.1 on 4.14+alpha-repo is now installable. Current state is: passing
• functoria.4.2.1 on 5.0 is now installable. Current state is: passing
• functoria.4.2.1 on 5.0+alpha-repo is now installable. Current state is: passing
• functoria.4.3.0 on 4.08 is now installable. Current state is: passing
• functoria.4.3.0 on 4.09 is now installable. Current state is: passing
• functoria.4.3.0 on 4.10 is now installable. Current state is: passing
• functoria.4.3.0 on 4.11 is now installable. Current state is: passing
• functoria.4.3.0 on 4.12 is now installable. Current state is: passing
• functoria.4.3.0 on 4.13 is now installable. Current state is: passing
• functoria.4.3.0 on 4.14 is now installable. Current state is: passing
• functoria.4.3.0 on 4.14+alpha-repo is now installable. Current state is: passing
• functoria.4.3.0 on 5.0 is now installable. Current state is: passing
• functoria.4.3.0 on 5.0+alpha-repo is now installable. Current state is: passing
• fuzzy_compare.1.0.0 on 4.10 is now installable. Current state is: passing
• fuzzy_compare.1.0.0 on 4.11 is now installable. Current state is: passing
• fuzzy_compare.1.0.0 on 4.12 is now installable. Current state is: passing
• fuzzy_compare.1.0.0 on 4.13 is now installable. Current state is: passing
• fuzzy_compare.1.0.0 on 4.14 is now installable. Current state is: passing
• fuzzy_compare.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• gdbprofiler.0.4 on 5.0 had its build status changed: not available to passing
• genspir.1.0.1 on 4.02 is now installable. Current state is: passing
• genspir.1.0.1 on 4.03 is now installable. Current state is: passing
• genspir.1.0.1 on 4.04 is now installable. Current state is: passing
• genspir.1.0.1 on 4.05 is now installable. Current state is: passing
• genspir.1.0.1 on 4.06 is now installable. Current state is: passing
• genspir.1.0.1 on 4.07 is now installable. Current state is: passing
• genspir.1.0.1 on 4.08 is now installable. Current state is: passing
• genspir.1.0.1 on 4.09 is now installable. Current state is: passing
• genspir.1.0.1 on 4.10 is now installable. Current state is: passing
• genspir.1.0.1 on 4.11 is now installable. Current state is: passing
• genspir.1.0.1 on 4.12 is now installable. Current state is: passing
• genspir.1.0.1 on 4.13 is now installable. Current state is: passing
• genspir.1.0.1 on 4.14 is now installable. Current state is: passing
• genspir.1.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• genspir.1.0.1 on 5.0 is now installable. Current state is: passing
• genspir.1.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• git-mirage.3.7.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-mirage.3.8.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-mirage.3.9.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-mirage.3.9.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-paf.3.7.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-paf.3.8.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-paf.3.9.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-paf.3.9.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-unix.3.7.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-unix.3.8.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-unix.3.9.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• git-unix.3.9.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• gitlab_pipeline_notifier.0.1 on 4.08 is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 4.09 is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 4.10 is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 4.11 is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 4.12 is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 4.13 is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 4.14 is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 5.0 is now installable. Current state is: passing
• gitlab_pipeline_notifier.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.02 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.03 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.04 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.05 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.06 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.07 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.08 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.09 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.10 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.11 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.12 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.13 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.14 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 4.14+alpha-repo is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 5.0 is now installable. Current state is: passing
• glfw-ocaml.3.3.1-2 on 5.0+alpha-repo is now installable. Current state is: passing
• globlon.1.0 on 4.02 is now installable. Current state is: passing
• globlon.1.0 on 4.03 is now installable. Current state is: passing
• globlon.1.0 on 4.04 is now installable. Current state is: passing
• globlon.1.0 on 4.05 is now installable. Current state is: passing
• globlon.1.0 on 4.06 is now installable. Current state is: passing
• globlon.1.0 on 4.07 is now installable. Current state is: passing
• globlon.1.0 on 4.08 is now installable. Current state is: passing
• globlon.1.0 on 4.09 is now installable. Current state is: passing
• globlon.1.0 on 4.10 is now installable. Current state is: passing
• globlon.1.0 on 4.11 is now installable. Current state is: passing
• globlon.1.0 on 4.12 is now installable. Current state is: passing
• globlon.1.0 on 4.13 is now installable. Current state is: passing
• globlon.1.0 on 4.14 is now installable. Current state is: passing
• globlon.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
• globlon.1.0 on 5.0 is now installable. Current state is: passing
• globlon.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.02 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.03 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.04 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.05 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.06 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.07 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.08 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.09 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.10 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.11 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.12 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.13 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.14 is now installable. Current state is: passing
• gmp.6.2.1-3 on 4.14+alpha-repo is now installable. Current state is: passing
• gmp.6.2.1-3 on 5.0 is now installable. Current state is: passing
• gmp.6.2.1-3 on 5.0+alpha-repo is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.02 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.03 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.04 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.05 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.06 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.07 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.08 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.09 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.10 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.11 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.12 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.13 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.14 is now installable. Current state is: passing
• gmp.6.2.1-4 on 4.14+alpha-repo is now installable. Current state is: passing
• gmp.6.2.1-4 on 5.0 is now installable. Current state is: passing
• gmp.6.2.1-4 on 5.0+alpha-repo is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.05 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.06 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.07 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.08 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.09 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.10 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.11 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.12 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.13 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.14 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• goblint-cil.2.0.0 on 5.0 is now installable. Current state is: passing
• goblint-cil.2.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• goblint.1.0.0 on 4.05 had its build status changed: failing to passing
• goblint.1.0.0 on 4.06 had its build status changed: failing to passing
• goblint.2.0.0 on 4.10 is now installable. Current state is: passing
• goblint.2.0.0 on 4.11 is now installable. Current state is: passing
• goblint.2.0.0 on 4.12 is now installable. Current state is: passing
• goblint.2.0.0 on 4.13 is now installable. Current state is: passing
• goblint.2.0.0 on 4.14 is now installable. Current state is: passing
• goblint.2.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• goblint.2.0.1 on 4.10 is now installable. Current state is: passing
• goblint.2.0.1 on 4.11 is now installable. Current state is: passing
• goblint.2.0.1 on 4.12 is now installable. Current state is: passing
• goblint.2.0.1 on 4.13 is now installable. Current state is: passing
• goblint.2.0.1 on 4.14 is now installable. Current state is: passing
• goblint.2.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• gsl.1.24.3 on 4.08 had its build status changed: failing to passing
• gsl.1.24.3 on 4.14+alpha-repo had its build status changed: failing to passing
• guile.1.0 on 4.08 is now installable. Current state is: passing
• guile.1.0 on 4.09 is now installable. Current state is: passing
• guile.1.0 on 4.10 is now installable. Current state is: passing
• guile.1.0 on 4.11 is now installable. Current state is: passing
• guile.1.0 on 4.12 is now installable. Current state is: passing
• guile.1.0 on 4.13 is now installable. Current state is: passing
• guile.1.0 on 4.14 is now installable. Current state is: passing
• guile.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
• guile.1.0 on 5.0 is now installable. Current state is: passing
• guile.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
• h1_parser.0.0.2 on 5.0 had its build status changed: not available to passing
• h2-lwt-unix.0.6.1 on 5.0 had its build status changed: partially failing to passing
• h2-lwt-unix.0.6.1 on 5.0+alpha-repo had its build status changed: partially failing to passing
• h2-lwt-unix.0.8.0 on 5.0 had its build status changed: partially failing to passing
• h2-lwt-unix.0.8.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• h2-lwt-unix.0.9.0 on 4.06 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.07 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.08 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.09 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.10 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.11 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.12 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.13 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.14 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 5.0 is now installable. Current state is: passing
• h2-lwt-unix.0.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.06 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.07 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.08 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.09 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.10 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.11 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.12 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.13 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.14 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• h2-lwt.0.9.0 on 5.0 is now installable. Current state is: passing
• h2-lwt.0.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• h2-mirage.0.9.0 on 4.08 is now installable. Current state is: passing
• h2-mirage.0.9.0 on 4.09 is now installable. Current state is: passing
• h2-mirage.0.9.0 on 4.10 is now installable. Current state is: passing
• h2-mirage.0.9.0 on 4.11 is now installable. Current state is: passing
• h2-mirage.0.9.0 on 4.12 is now installable. Current state is: passing
• h2-mirage.0.9.0 on 4.13 is now installable. Current state is: passing
• h2-mirage.0.9.0 on 4.14 is now installable. Current state is: passing
• h2-mirage.0.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• h2-mirage.0.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• h2.0.9.0 on 4.06 is now installable. Current state is: passing
• h2.0.9.0 on 4.07 is now installable. Current state is: passing
• h2.0.9.0 on 4.08 is now installable. Current state is: passing
• h2.0.9.0 on 4.09 is now installable. Current state is: passing
• h2.0.9.0 on 4.10 is now installable. Current state is: passing
• h2.0.9.0 on 4.11 is now installable. Current state is: passing
• h2.0.9.0 on 4.12 is now installable. Current state is: passing
• h2.0.9.0 on 4.13 is now installable. Current state is: passing
• h2.0.9.0 on 4.14 is now installable. Current state is: passing
• h2.0.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• h2.0.9.0 on 5.0 is now installable. Current state is: passing
• h2.0.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 4.08 is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 4.09 is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 4.10 is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 4.11 is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 4.12 is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 4.13 is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 4.14 is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 4.14+alpha-repo is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 5.0 is now installable. Current state is: passing
• hacl-star-raw.0.5.0 on 5.0+alpha-repo is now installable. Current state is: passing
• hacl-star.0.5.0 on 4.08 is now installable. Current state is: passing
• hacl-star.0.5.0 on 4.09 is now installable. Current state is: passing
• hacl-star.0.5.0 on 4.10 is now installable. Current state is: passing
• hacl-star.0.5.0 on 4.11 is now installable. Current state is: passing
• hacl-star.0.5.0 on 4.12 is now installable. Current state is: passing
• hacl-star.0.5.0 on 4.13 is now installable. Current state is: passing
• hacl-star.0.5.0 on 4.14 is now installable. Current state is: passing
• hacl-star.0.5.0 on 4.14+alpha-repo is now installable. Current state is: passing
• hacl-star.0.5.0 on 5.0 is now installable. Current state is: passing
• hacl-star.0.5.0 on 5.0+alpha-repo is now installable. Current state is: passing
• hardcaml.v0.15.0 on 5.0 had its build status changed: not available to passing
• hardcaml_circuits.v0.15.0 on 5.0 had its build status changed: not available to passing
• hardcaml_fixed_point.v0.15.0 on 5.0 had its build status changed: not available to passing
• hardcaml_verify.v0.15.0 on 4.14 had its build status changed: not available to passing
• hardcaml_verify.v0.15.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• hardcaml_verify.v0.15.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
• hardcaml_waveterm.v0.14.0 on 4.14 had its build status changed: not available to passing
• hardcaml_waveterm.v0.14.0 on 4.14+alpha-repo had its build status changed: failing to passing
• hardcaml_waveterm.v0.15.0 on 4.14 had its build status changed: not available to passing
• hardcaml_waveterm.v0.15.0 on 4.14+alpha-repo had its build status changed: failing to passing
• hardcaml_waveterm.v0.15.0 on 5.0+alpha-repo had its build status changed: failing to passing
• hardcaml_xilinx.v0.15.0 on 5.0 had its build status changed: not available to passing
• higher_kinded.v0.15.0 on 5.0 had its build status changed: not available to passing
• hpack.0.9.0 on 4.04 is now installable. Current state is: passing
• hpack.0.9.0 on 4.05 is now installable. Current state is: passing
• hpack.0.9.0 on 4.06 is now installable. Current state is: passing
• hpack.0.9.0 on 4.07 is now installable. Current state is: passing
• hpack.0.9.0 on 4.08 is now installable. Current state is: passing
• hpack.0.9.0 on 4.09 is now installable. Current state is: passing
• hpack.0.9.0 on 4.10 is now installable. Current state is: passing
• hpack.0.9.0 on 4.11 is now installable. Current state is: passing
• hpack.0.9.0 on 4.12 is now installable. Current state is: passing
• hpack.0.9.0 on 4.13 is now installable. Current state is: passing
• hpack.0.9.0 on 4.14 is now installable. Current state is: passing
• hpack.0.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
• hpack.0.9.0 on 5.0 is now installable. Current state is: passing
• hpack.0.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 4.08 is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 4.09 is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 4.10 is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 4.11 is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 4.12 is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 4.13 is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 4.14 is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 4.14+alpha-repo is now installable. Current state is: passing
• http-lwt-client.0.0.7 on 5.0+alpha-repo is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 4.08 is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 4.09 is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 4.10 is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 4.11 is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 4.12 is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 4.13 is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 4.14 is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 4.14+alpha-repo is now installable. Current state is: passing
• http-lwt-client.0.0.8 on 5.0+alpha-repo is now installable. Current state is: passing
• http_async.0.0.4 on 4.11 is now installable. Current state is: passing
• http_async.0.0.4 on 4.12 is now installable. Current state is: passing
• http_async.0.0.4 on 4.13 is now installable. Current state is: passing
• http_async.0.0.4 on 4.14 is now installable. Current state is: passing
• http_async.0.0.4 on 4.14+alpha-repo is now installable. Current state is: passing
• http_async.0.0.4 on 5.0+alpha-repo is now installable. Current state is: passing
• idd.0.1 on 5.0 had its build status changed: not available to passing
• influxdb-lwt.0.2.0 on 5.0 had its build status changed: not available to passing
• influxdb-lwt.0.3.0 on 5.0 had its build status changed: not available to passing
• influxdb.0.2.0 on 5.0 had its build status changed: not available to passing
• influxdb.0.3.0 on 5.0 had its build status changed: not available to passing
• int_repr.v0.15.0 on 5.0 had its build status changed: not available to passing
• irmin-bench.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-bench.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-bench.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-bench.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-bench.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-bench.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-bench.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-bench.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-bench.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-bench.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-bench.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-bench.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-bench.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-bench.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-bench.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-bench.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-bench.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-bench.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-bench.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-bench.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-bench.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-chunk.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-chunk.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-chunk.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-chunk.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-chunk.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-chunk.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-chunk.3.4.0 on 5.0 is now installable. Current state is: passing
• irmin-chunk.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-chunk.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-chunk.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-chunk.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-chunk.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-chunk.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-chunk.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-chunk.3.4.1 on 5.0 is now installable. Current state is: passing
• irmin-chunk.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-chunk.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-chunk.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-chunk.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-chunk.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-chunk.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-chunk.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-chunk.3.4.2 on 5.0 is now installable. Current state is: passing
• irmin-chunk.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-cli.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-cli.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-cli.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-cli.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-cli.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-cli.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-cli.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-cli.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-cli.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-cli.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-cli.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-cli.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-cli.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-cli.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-cli.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-cli.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-cli.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-cli.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-cli.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-cli.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-cli.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-containers.2.10.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.2.10.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.2.10.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.0.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.1.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.2.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.2.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.2.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.3.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.3.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.3.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-containers.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-containers.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-containers.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-containers.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-containers.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-containers.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-containers.3.4.0 on 5.0 is now installable. Current state is: passing
• irmin-containers.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-containers.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-containers.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-containers.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-containers.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-containers.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-containers.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-containers.3.4.1 on 5.0 is now installable. Current state is: passing
• irmin-containers.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-containers.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-containers.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-containers.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-containers.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-containers.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-containers.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-containers.3.4.2 on 5.0 is now installable. Current state is: passing
• irmin-containers.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-fs.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-fs.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-fs.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-fs.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-fs.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-fs.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-fs.3.4.0 on 5.0 is now installable. Current state is: passing
• irmin-fs.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-fs.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-fs.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-fs.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-fs.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-fs.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-fs.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-fs.3.4.1 on 5.0 is now installable. Current state is: passing
• irmin-fs.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-fs.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-fs.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-fs.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-fs.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-fs.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-fs.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-fs.3.4.2 on 5.0 is now installable. Current state is: passing
• irmin-fs.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-git.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-git.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-git.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-git.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-git.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-git.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-git.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-git.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-git.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-git.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-git.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-git.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-git.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-git.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-git.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-git.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-git.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-git.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-git.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-git.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-git.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-graphql.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-graphql.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-graphql.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-graphql.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-graphql.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-graphql.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-graphql.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-graphql.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-graphql.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-graphql.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-graphql.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-graphql.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-graphql.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-graphql.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-graphql.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-graphql.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-graphql.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-graphql.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-graphql.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-graphql.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-graphql.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-http.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-http.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-http.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-http.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-http.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-http.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-http.3.4.0 on 5.0 is now installable. Current state is: passing
• irmin-http.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-http.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-http.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-http.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-http.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-http.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-http.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-http.3.4.1 on 5.0 is now installable. Current state is: passing
• irmin-http.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-http.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-http.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-http.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-http.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-http.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-http.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-http.3.4.2 on 5.0 is now installable. Current state is: passing
• irmin-http.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage-git.2.10.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-mirage-git.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-mirage-git.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-mirage-git.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-mirage-git.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-mirage-git.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-mirage-git.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage-git.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage-git.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-mirage-git.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-mirage-git.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-mirage-git.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-mirage-git.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-mirage-git.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage-git.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage-git.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-mirage-git.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-mirage-git.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-mirage-git.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-mirage-git.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-mirage-git.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage-git.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage-graphql.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-mirage.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-mirage.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-mirage.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-mirage.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-mirage.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage.3.4.0 on 5.0 is now installable. Current state is: passing
• irmin-mirage.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-mirage.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-mirage.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-mirage.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-mirage.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-mirage.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage.3.4.1 on 5.0 is now installable. Current state is: passing
• irmin-mirage.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-mirage.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-mirage.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-mirage.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-mirage.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-mirage.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-mirage.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-mirage.3.4.2 on 5.0 is now installable. Current state is: passing
• irmin-mirage.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-pack.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-pack.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-pack.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-pack.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-pack.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-pack.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-pack.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-pack.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-pack.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-pack.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-pack.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-pack.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-pack.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-pack.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-pack.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-pack.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-pack.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-pack.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-pack.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-pack.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-pack.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-test.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-test.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-test.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-test.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-test.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-test.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-test.3.4.0 on 5.0 is now installable. Current state is: passing
• irmin-test.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-test.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-test.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-test.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-test.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-test.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-test.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-test.3.4.1 on 5.0 is now installable. Current state is: passing
• irmin-test.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-test.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-test.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-test.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-test.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-test.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-test.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-test.3.4.2 on 5.0 is now installable. Current state is: passing
• irmin-test.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-tezos-utils.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-tezos-utils.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-tezos-utils.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-tezos-utils.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-tezos-utils.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-tezos-utils.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-tezos-utils.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-tezos.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin-tezos.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin-tezos.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin-tezos.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin-tezos.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin-tezos.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-tezos.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-tezos.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin-tezos.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin-tezos.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin-tezos.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin-tezos.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin-tezos.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-tezos.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-tezos.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin-tezos.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin-tezos.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin-tezos.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin-tezos.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin-tezos.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin-tezos.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin-unix.2.10.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.2.10.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.2.10.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.3.0.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.3.1.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.3.2.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.3.2.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.3.2.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.3.3.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.3.3.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin-unix.3.3.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• irmin.3.4.0 on 4.10 is now installable. Current state is: passing
• irmin.3.4.0 on 4.11 is now installable. Current state is: passing
• irmin.3.4.0 on 4.12 is now installable. Current state is: passing
• irmin.3.4.0 on 4.13 is now installable. Current state is: passing
• irmin.3.4.0 on 4.14 is now installable. Current state is: passing
• irmin.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin.3.4.0 on 5.0 is now installable. Current state is: passing
• irmin.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin.3.4.1 on 4.10 is now installable. Current state is: passing
• irmin.3.4.1 on 4.11 is now installable. Current state is: passing
• irmin.3.4.1 on 4.12 is now installable. Current state is: passing
• irmin.3.4.1 on 4.13 is now installable. Current state is: passing
• irmin.3.4.1 on 4.14 is now installable. Current state is: passing
• irmin.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin.3.4.1 on 5.0 is now installable. Current state is: passing
• irmin.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• irmin.3.4.2 on 4.10 is now installable. Current state is: passing
• irmin.3.4.2 on 4.11 is now installable. Current state is: passing
• irmin.3.4.2 on 4.12 is now installable. Current state is: passing
• irmin.3.4.2 on 4.13 is now installable. Current state is: passing
• irmin.3.4.2 on 4.14 is now installable. Current state is: passing
• irmin.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• irmin.3.4.2 on 5.0 is now installable. Current state is: passing
• irmin.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• json-data-encoding-browser.0.12 on 4.10 is now installable. Current state is: passing
• json-data-encoding-browser.0.12 on 4.11 is now installable. Current state is: passing
• json-data-encoding-browser.0.12 on 4.12 is now installable. Current state is: passing
• json-data-encoding-browser.0.12 on 4.13 is now installable. Current state is: passing
• json-data-encoding-browser.0.12 on 4.14 is now installable. Current state is: passing
• json-data-encoding-browser.0.12 on 4.14+alpha-repo is now installable. Current state is: passing
• json-data-encoding-browser.0.12 on 5.0+alpha-repo is now installable. Current state is: passing
• json-data-encoding-browser.0.12.1 on 4.10 is now installable. Current state is: passing
• json-data-encoding-browser.0.12.1 on 4.11 is now installable. Current state is: passing
• json-data-encoding-browser.0.12.1 on 4.12 is now installable. Current state is: passing
• json-data-encoding-browser.0.12.1 on 4.13 is now installable. Current state is: passing
• json-data-encoding-browser.0.12.1 on 4.14 is now installable. Current state is: passing
• json-data-encoding-browser.0.12.1 on 4.14+alpha-repo is now installable. Current state is: passing
• json-data-encoding-browser.0.12.1 on 5.0+alpha-repo is now installable. Current state is: passing
• json-data-encoding-bson.0.12 on 4.10 is now installable. Current state is: passing
• json-data-encoding-bson.0.12 on 4.11 is now installable. Current state is: passing
• json-data-encoding-bson.0.12 on 4.12 is now installable. Current state is: passing
• json-data-encoding-bson.0.12 on 4.13 is now installable. Current state is: passing
• json-data-encoding-bson.0.12 on 4.14 is now installable. Current state is: passing
• json-data-encoding-bson.0.12 on 4.14+alpha-repo is now installable. Current state is: passing
• json-data-encoding-bson.0.12 on 5.0 is now installable. Current state is: passing
• json-data-encoding-bson.0.12 on 5.0+alpha-repo is now installable. Current state is: passing
• json-data-encoding-bson.0.12.1 on 4.10 is now installable. Current state is: passing
• json-data-encoding-bson.0.12.1 on 4.11 is now installable. Current state is: passing
• json-data-encoding-bson.0.12.1 on 4.12 is now installable. Current state is: passing
• json-data-encoding-bson.0.12.1 on 4.13 is now installable. Current state is: passing
• json-data-encoding-bson.0.12.1 on 4.14 is now installable. Current state is: passing
• json-data-encoding-bson.0.12.1 on 4.14+alpha-repo is now installable. Current state is: passing
• json-data-encoding-bson.0.12.1 on 5.0 is now installable. Current state is: passing
• json-data-encoding-bson.0.12.1 on 5.0+alpha-repo is now installable. Current state is: passing
• json-data-encoding.0.12 on 4.10 is now installable. Current state is: passing
• json-data-encoding.0.12 on 4.11 is now installable. Current state is: passing
• json-data-encoding.0.12 on 4.12 is now installable. Current state is: passing
• json-data-encoding.0.12 on 4.13 is now installable. Current state is: passing
• json-data-encoding.0.12 on 4.14 is now installable. Current state is: passing
• json-data-encoding.0.12 on 4.14+alpha-repo is now installable. Current state is: passing
• json-data-encoding.0.12 on 5.0 is now installable. Current state is: passing
• json-data-encoding.0.12 on 5.0+alpha-repo is now installable. Current state is: passing
• json-data-encoding.0.12.1 on 4.10 is now installable. Current state is: passing
• json-data-encoding.0.12.1 on 4.11 is now installable. Current state is: passing
• json-data-encoding.0.12.1 on 4.12 is now installable. Current state is: passing
• json-data-encoding.0.12.1 on 4.13 is now installable. Current state is: passing
• json-data-encoding.0.12.1 on 4.14 is now installable. Current state is: passing
• json-data-encoding.0.12.1 on 4.14+alpha-repo is now installable. Current state is: passing
• json-data-encoding.0.12.1 on 5.0 is now installable. Current state is: passing
• json-data-encoding.0.12.1 on 5.0+alpha-repo is now installable. Current state is: passing
• jsonaf.v0.15.0 on 5.0 had its build status changed: not available to passing
• kdl.0.1.0 on 4.08 is now installable. Current state is: passing
• kdl.0.1.0 on 4.09 is now installable. Current state is: passing
• kdl.0.1.0 on 4.10 is now installable. Current state is: passing
• kdl.0.1.0 on 4.11 is now installable. Current state is: passing
• kdl.0.1.0 on 4.12 is now installable. Current state is: passing
• kdl.0.1.0 on 4.13 is now installable. Current state is: passing
• kdl.0.1.0 on 4.14 is now installable. Current state is: passing
• kdl.0.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
• kdl.0.1.0 on 5.0 is now installable. Current state is: passing
• kdl.0.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
• kinetic-client.0.0.11 on 5.0 had its build status changed: not available to passing
• kinetic-client.0.0.11 on 5.0+alpha-repo had its build status changed: not available to passing
• knights_tour.0.0.1 on 5.0 had its build status changed: not available to passing
• knights_tour.0.0.2 on 5.0 had its build status changed: not available to passing
• knights_tour.0.0.3 on 5.0 had its build status changed: not available to passing
• knights_tour.0.0.4 on 5.0 had its build status changed: not available to passing
• letters.0.3.1 on 4.08 is now installable. Current state is: passing
• letters.0.3.1 on 4.09 is now installable. Current state is: passing
• letters.0.3.1 on 4.10 is now installable. Current state is: passing
• letters.0.3.1 on 4.11 is now installable. Current state is: passing
• letters.0.3.1 on 4.12 is now installable. Current state is: passing
• letters.0.3.1 on 4.13 is now installable. Current state is: passing
• letters.0.3.1 on 4.14 is now installable. Current state is: passing
• letters.0.3.1 on 4.14+alpha-repo is now installable. Current state is: passing
• letters.0.3.1 on 5.0 is now installable. Current state is: passing
• letters.0.3.1 on 5.0+alpha-repo is now installable. Current state is: passing
• libirmin.3.1.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• libirmin.3.2.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• libirmin.3.2.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• libirmin.3.2.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• libirmin.3.3.0 on 4.14+alpha-repo had its build status changed: partially failing to passing
• libirmin.3.3.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• libirmin.3.3.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• libirmin.3.4.0 on 4.10 is now installable. Current state is: passing
• libirmin.3.4.0 on 4.11 is now installable. Current state is: passing
• libirmin.3.4.0 on 4.12 is now installable. Current state is: passing
• libirmin.3.4.0 on 4.13 is now installable. Current state is: passing
• libirmin.3.4.0 on 4.14 is now installable. Current state is: passing
• libirmin.3.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• libirmin.3.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• libirmin.3.4.1 on 4.10 is now installable. Current state is: passing
• libirmin.3.4.1 on 4.11 is now installable. Current state is: passing
• libirmin.3.4.1 on 4.12 is now installable. Current state is: passing
• libirmin.3.4.1 on 4.13 is now installable. Current state is: passing
• libirmin.3.4.1 on 4.14 is now installable. Current state is: passing
• libirmin.3.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• libirmin.3.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
• libirmin.3.4.2 on 4.10 is now installable. Current state is: passing
• libirmin.3.4.2 on 4.11 is now installable. Current state is: passing
• libirmin.3.4.2 on 4.12 is now installable. Current state is: passing
• libirmin.3.4.2 on 4.13 is now installable. Current state is: passing
• libirmin.3.4.2 on 4.14 is now installable. Current state is: passing
• libirmin.3.4.2 on 4.14+alpha-repo is now installable. Current state is: passing
• libirmin.3.4.2 on 5.0+alpha-repo is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.02 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.03 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.04 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.05 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.06 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.07 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.08 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.09 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.10 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.11 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.12 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.13 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.14 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 4.14+alpha-repo is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 5.0 is now installable. Current state is: passing
• libtorch.1.12.0+linux-x86_64 on 5.0+alpha-repo is now installable. Current state is: passing
• linenoise.1.4.0 on 4.03 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.04 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.05 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.06 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.07 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.08 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.09 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.10 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.11 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.12 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.13 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.14 is now installable. Current state is: passing
• linenoise.1.4.0 on 4.14+alpha-repo is now installable. Current state is: passing
• linenoise.1.4.0 on 5.0 is now installable. Current state is: passing
• linenoise.1.4.0 on 5.0+alpha-repo is now installable. Current state is: passing
• liquidsoap.2.1.1 on 4.12 is now installable. Current state is: passing
• liquidsoap.2.1.1 on 4.13 is now installable. Current state is: passing
• liquidsoap.2.1.1 on 4.14 is now installable. Current state is: passing
• liquidsoap.2.1.2 on 4.12 is now installable. Current state is: passing
• liquidsoap.2.1.2 on 4.13 is now installable. Current state is: passing
• liquidsoap.2.1.2 on 4.14 is now installable. Current state is: passing
• lsp.1.11.3 on 5.0 had its build status changed: not available to passing
• lsp.1.11.4 on 5.0 had its build status changed: not available to passing
• lsp.1.11.5 on 5.0 had its build status changed: not available to passing
• lsp.1.11.6 on 5.0 had its build status changed: not available to passing
• lsp.1.12.0 on 5.0 had its build status changed: not available to passing
• lsp.1.12.1 on 5.0 had its build status changed: not available to passing
• lua_parser.1.0.0 on 5.0 had its build status changed: partially failing to passing
• lua_parser.1.0.2 on 5.0 had its build status changed: partially failing to passing
• lucid.0.1.5 on 4.13 is now installable. Current state is: passing
• lucid.0.1.5 on 4.14 is now installable. Current state is: passing
• lucid.0.1.5 on 4.14+alpha-repo is now installable. Current state is: passing
• lucid.0.1.5 on 5.0 is now installable. Current state is: passing
• lucid.0.1.5 on 5.0+alpha-repo is now installable. Current state is: passing
• lwd.0.3 on 4.03 is now installable. Current state is: passing
• lwd.0.3 on 4.04 is now installable. Current state is: passing
• lwd.0.3 on 4.05 is now installable. Current state is: passing
• lwd.0.3 on 4.06 is now installable. Current state is: passing
• lwd.0.3 on 4.07 is now installable. Current state is: passing
• lwd.0.3 on 4.08 is now installable. Current state is: passing
• lwd.0.3 on 4.09 is now installable. Current state is: passing
• lwd.0.3 on 4.10 is now installable. Current state is: passing
• lwd.0.3 on 4.11 is now installable. Current state is: passing
• lwd.0.3 on 4.12 is now installable. Current state is: passing
• lwd.0.3 on 4.13 is now installable. Current state is: passing
• lwd.0.3 on 4.14 is now installable. Current state is: passing
• lwd.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• lwd.0.3 on 5.0 is now installable. Current state is: passing
• lwd.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.03 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.04 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.05 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.06 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.07 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.08 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.09 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.10 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.11 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.12 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.13 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.14 is now installable. Current state is: passing
• lwt_log.1.1.2 on 4.14+alpha-repo is now installable. Current state is: passing
• lwt_log.1.1.2 on 5.0 is now installable. Current state is: passing
• lwt_log.1.1.2 on 5.0+alpha-repo is now installable. Current state is: passing
• malfunction.0.4.1 on 4.04 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.05 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.06 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.07 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.08 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.09 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.10 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.11 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.12 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.13 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.14 is now installable. Current state is: passing
• malfunction.0.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
• mbr-format.1.0.0 on 4.08 is now installable. Current state is: passing
• mbr-format.1.0.0 on 4.09 is now installable. Current state is: passing
• mbr-format.1.0.0 on 4.10 is now installable. Current state is: passing
• mbr-format.1.0.0 on 4.11 is now installable. Current state is: passing
• mbr-format.1.0.0 on 4.12 is now installable. Current state is: passing
• mbr-format.1.0.0 on 4.13 is now installable. Current state is: passing
• mbr-format.1.0.0 on 4.14 is now installable. Current state is: passing
• mbr-format.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• mbr-format.1.0.0 on 5.0 is now installable. Current state is: passing
• mbr-format.1.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• md2mld.0.6 on 4.08 is now installable. Current state is: passing
• md2mld.0.6 on 4.09 is now installable. Current state is: passing
• md2mld.0.6 on 4.10 is now installable. Current state is: passing
• md2mld.0.6 on 4.11 is now installable. Current state is: passing
• md2mld.0.6 on 4.12 is now installable. Current state is: passing
• md2mld.0.6 on 4.13 is now installable. Current state is: passing
• md2mld.0.6 on 4.14 is now installable. Current state is: passing
• md2mld.0.6 on 4.14+alpha-repo is now installable. Current state is: passing
• md2mld.0.6 on 5.0 is now installable. Current state is: passing
• md2mld.0.6 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 4.08 is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 4.09 is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 4.10 is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 4.11 is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 4.12 is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 4.13 is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 4.14 is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 5.0 is now installable. Current state is: passing
• mirage-block-combinators.3.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 4.08 is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 4.09 is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 4.10 is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 4.11 is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 4.12 is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 4.13 is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 4.14 is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 5.0 is now installable. Current state is: passing
• mirage-block-partition.0.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.06 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.07 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.08 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.09 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.10 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.11 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.12 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.13 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.14 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 5.0 is now installable. Current state is: passing
• mirage-block-unix.2.14.2 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-block.3.0.1 on 4.08 is now installable. Current state is: passing
• mirage-block.3.0.1 on 4.09 is now installable. Current state is: passing
• mirage-block.3.0.1 on 4.10 is now installable. Current state is: passing
• mirage-block.3.0.1 on 4.11 is now installable. Current state is: passing
• mirage-block.3.0.1 on 4.12 is now installable. Current state is: passing
• mirage-block.3.0.1 on 4.13 is now installable. Current state is: passing
• mirage-block.3.0.1 on 4.14 is now installable. Current state is: passing
• mirage-block.3.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-block.3.0.1 on 5.0 is now installable. Current state is: passing
• mirage-block.3.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-clock-xen.1.0.0 on 5.0 had its build status changed: failing to passing
• mirage-clock-xen.1.0.0 on 5.0+alpha-repo had its build status changed: failing to passing
• mirage-clock-xen.1.1 on 5.0 had its build status changed: failing to passing
• mirage-clock-xen.1.1 on 5.0+alpha-repo had its build status changed: failing to passing
• mirage-crypto-ec.0.10.7 on 4.08 is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 4.09 is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 4.10 is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 4.11 is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 4.12 is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 4.13 is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 4.14 is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 5.0 is now installable. Current state is: passing
• mirage-crypto-ec.0.10.7 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 4.08 is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 4.09 is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 4.10 is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 4.11 is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 4.12 is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 4.13 is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 4.14 is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 5.0 is now installable. Current state is: passing
• mirage-crypto-pk.0.10.7 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 4.08 is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 4.09 is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 4.10 is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 4.11 is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 4.12 is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 4.13 is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 4.14 is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-crypto-rng-async.0.10.7 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 4.08 is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 4.09 is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 4.10 is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 4.11 is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 4.12 is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 4.13 is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 4.14 is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 5.0 is now installable. Current state is: passing
• mirage-crypto-rng-mirage.0.10.7 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 4.08 is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 4.09 is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 4.10 is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 4.11 is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 4.12 is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 4.13 is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 4.14 is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 5.0 is now installable. Current state is: passing
• mirage-crypto-rng.0.10.7 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 4.08 is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 4.09 is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 4.10 is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 4.11 is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 4.12 is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 4.13 is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 4.14 is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 5.0 is now installable. Current state is: passing
• mirage-crypto.0.10.7 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-kv.5.0.0 on 4.08 is now installable. Current state is: passing
• mirage-kv.5.0.0 on 4.09 is now installable. Current state is: passing
• mirage-kv.5.0.0 on 4.10 is now installable. Current state is: passing
• mirage-kv.5.0.0 on 4.11 is now installable. Current state is: passing
• mirage-kv.5.0.0 on 4.12 is now installable. Current state is: passing
• mirage-kv.5.0.0 on 4.13 is now installable. Current state is: passing
• mirage-kv.5.0.0 on 4.14 is now installable. Current state is: passing
• mirage-kv.5.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-kv.5.0.0 on 5.0 is now installable. Current state is: passing
• mirage-kv.5.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-monitoring.0.0.3 on 4.11 is now installable. Current state is: passing
• mirage-monitoring.0.0.3 on 4.12 is now installable. Current state is: passing
• mirage-monitoring.0.0.3 on 4.13 is now installable. Current state is: passing
• mirage-monitoring.0.0.3 on 4.14 is now installable. Current state is: passing
• mirage-monitoring.0.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-nat.3.0.0 on 4.08 is now installable. Current state is: passing
• mirage-nat.3.0.0 on 4.09 is now installable. Current state is: passing
• mirage-nat.3.0.0 on 4.10 is now installable. Current state is: passing
• mirage-nat.3.0.0 on 4.11 is now installable. Current state is: passing
• mirage-nat.3.0.0 on 4.12 is now installable. Current state is: passing
• mirage-nat.3.0.0 on 4.13 is now installable. Current state is: passing
• mirage-nat.3.0.0 on 4.14 is now installable. Current state is: passing
• mirage-nat.3.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-nat.3.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 4.08 is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 4.09 is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 4.10 is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 4.11 is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 4.12 is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 4.13 is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 4.14 is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-qubes-ipv4.0.9.3 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 4.08 is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 4.09 is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 4.10 is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 4.11 is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 4.12 is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 4.13 is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 4.14 is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 5.0 is now installable. Current state is: passing
• mirage-qubes.0.9.3 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 4.08 is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 4.09 is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 4.10 is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 4.11 is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 4.12 is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 4.13 is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 4.14 is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 5.0 is now installable. Current state is: passing
• mirage-runtime.4.2.1 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 4.08 is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 4.09 is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 4.10 is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 4.11 is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 4.12 is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 4.13 is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 4.14 is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 5.0 is now installable. Current state is: passing
• mirage-runtime.4.3.0 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage-unix.5.0.1 on 4.08 is now installable. Current state is: passing
• mirage-unix.5.0.1 on 4.09 is now installable. Current state is: passing
• mirage-unix.5.0.1 on 4.10 is now installable. Current state is: passing
• mirage-unix.5.0.1 on 4.11 is now installable. Current state is: passing
• mirage-unix.5.0.1 on 4.12 is now installable. Current state is: passing
• mirage-unix.5.0.1 on 4.13 is now installable. Current state is: passing
• mirage-unix.5.0.1 on 4.14 is now installable. Current state is: passing
• mirage-unix.5.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage-unix.5.0.1 on 5.0 is now installable. Current state is: passing
• mirage-unix.5.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• mirage.4.2.1 on 4.10 is now installable. Current state is: passing
• mirage.4.2.1 on 4.11 is now installable. Current state is: passing
• mirage.4.2.1 on 4.12 is now installable. Current state is: passing
• mirage.4.2.1 on 4.13 is now installable. Current state is: passing
• mirage.4.2.1 on 4.14 is now installable. Current state is: passing
• mirage.4.2.1 on 4.14+alpha-repo is now installable. Current state is: passing
• mirage.4.3.0 on 4.10 is now installable. Current state is: passing
• mirage.4.3.0 on 4.11 is now installable. Current state is: passing
• mirage.4.3.0 on 4.12 is now installable. Current state is: passing
• mirage.4.3.0 on 4.13 is now installable. Current state is: passing
• mirage.4.3.0 on 4.14 is now installable. Current state is: passing
• mirage.4.3.0 on 4.14+alpha-repo is now installable. Current state is: passing
• monaco_jsoo.1.0.1 on 4.12 is now installable. Current state is: passing
• monaco_jsoo.1.0.1 on 4.13 is now installable. Current state is: passing
• monaco_jsoo.1.0.1 on 4.14 is now installable. Current state is: passing
• monaco_jsoo.1.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• monaco_jsoo.1.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• mparser.1.1 on 4.03 had its build status changed: internal failure to passing
• mparser.1.2.1 on 4.05 had its build status changed: internal failure to passing
• nbd-tool.6.0.0 on 4.08 is now installable. Current state is: passing
• nbd-tool.6.0.0 on 4.09 is now installable. Current state is: passing
• nbd-tool.6.0.0 on 4.10 is now installable. Current state is: passing
• nbd-tool.6.0.0 on 4.11 is now installable. Current state is: passing
• nbd-tool.6.0.0 on 4.12 is now installable. Current state is: passing
• nbd-tool.6.0.0 on 4.13 is now installable. Current state is: passing
• nbd-tool.6.0.0 on 4.14 is now installable. Current state is: passing
• nbd-tool.6.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• nbd-tool.6.0.0 on 5.0 is now installable. Current state is: passing
• nbd-tool.6.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• nbd-tool.6.0.1 on 4.08 is now installable. Current state is: passing
• nbd-tool.6.0.1 on 4.09 is now installable. Current state is: passing
• nbd-tool.6.0.1 on 4.10 is now installable. Current state is: passing
• nbd-tool.6.0.1 on 4.11 is now installable. Current state is: passing
• nbd-tool.6.0.1 on 4.12 is now installable. Current state is: passing
• nbd-tool.6.0.1 on 4.13 is now installable. Current state is: passing
• nbd-tool.6.0.1 on 4.14 is now installable. Current state is: passing
• nbd-tool.6.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• nbd-tool.6.0.1 on 5.0 is now installable. Current state is: passing
• nbd-tool.6.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• nbd-unix.6.0.0 on 4.08 is now installable. Current state is: passing
• nbd-unix.6.0.0 on 4.09 is now installable. Current state is: passing
• nbd-unix.6.0.0 on 4.10 is now installable. Current state is: passing
• nbd-unix.6.0.0 on 4.11 is now installable. Current state is: passing
• nbd-unix.6.0.0 on 4.12 is now installable. Current state is: passing
• nbd-unix.6.0.0 on 4.13 is now installable. Current state is: passing
• nbd-unix.6.0.0 on 4.14 is now installable. Current state is: passing
• nbd-unix.6.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• nbd-unix.6.0.0 on 5.0 is now installable. Current state is: passing
• nbd-unix.6.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• nbd-unix.6.0.1 on 4.08 is now installable. Current state is: passing
• nbd-unix.6.0.1 on 4.09 is now installable. Current state is: passing
• nbd-unix.6.0.1 on 4.10 is now installable. Current state is: passing
• nbd-unix.6.0.1 on 4.11 is now installable. Current state is: passing
• nbd-unix.6.0.1 on 4.12 is now installable. Current state is: passing
• nbd-unix.6.0.1 on 4.13 is now installable. Current state is: passing
• nbd-unix.6.0.1 on 4.14 is now installable. Current state is: passing
• nbd-unix.6.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• nbd-unix.6.0.1 on 5.0 is now installable. Current state is: passing
• nbd-unix.6.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• nbd.2.1.0 on 4.02 had its build status changed: partially failing to passing
• nbd.4.0.3 on 5.0 had its build status changed: not available to passing
• nbd.6.0.0 on 4.08 is now installable. Current state is: passing
• nbd.6.0.0 on 4.09 is now installable. Current state is: passing
• nbd.6.0.0 on 4.10 is now installable. Current state is: passing
• nbd.6.0.0 on 4.11 is now installable. Current state is: passing
• nbd.6.0.0 on 4.12 is now installable. Current state is: passing
• nbd.6.0.0 on 4.13 is now installable. Current state is: passing
• nbd.6.0.0 on 4.14 is now installable. Current state is: passing
• nbd.6.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
• nbd.6.0.0 on 5.0 is now installable. Current state is: passing
• nbd.6.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
• nbd.6.0.1 on 4.08 is now installable. Current state is: passing
• nbd.6.0.1 on 4.09 is now installable. Current state is: passing
• nbd.6.0.1 on 4.10 is now installable. Current state is: passing
• nbd.6.0.1 on 4.11 is now installable. Current state is: passing
• nbd.6.0.1 on 4.12 is now installable. Current state is: passing
• nbd.6.0.1 on 4.13 is now installable. Current state is: passing
• nbd.6.0.1 on 4.14 is now installable. Current state is: passing
• nbd.6.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
• nbd.6.0.1 on 5.0 is now installable. Current state is: passing
• nbd.6.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
• nottui-lwt.0.1 on 4.14 had its build status changed: not available to passing
• nottui-lwt.0.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• nottui-lwt.0.1 on 5.0 had its build status changed: not available to passing
• nottui-lwt.0.1 on 5.0+alpha-repo had its build status changed: partially failing to passing
• nottui-lwt.0.2 on 4.03 had its build status changed: partially failing to passing
• nottui-lwt.0.2 on 4.04 had its build status changed: partially failing to passing
• nottui-lwt.0.2 on 4.14 had its build status changed: not available to passing
• nottui-lwt.0.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• nottui-lwt.0.2 on 5.0 had its build status changed: not available to passing
• nottui-lwt.0.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
• nottui-lwt.0.3 on 4.03 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.04 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.05 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.06 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.07 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.08 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.09 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.10 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.11 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.12 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.13 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.14 is now installable. Current state is: passing
• nottui-lwt.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• nottui-lwt.0.3 on 5.0 is now installable. Current state is: passing
• nottui-lwt.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
• nottui-pretty.0.1 on 4.14 had its build status changed: not available to passing
• nottui-pretty.0.1 on 4.14+alpha-repo had its build status changed: partially failing to passing
• nottui-pretty.0.1 on 5.0 had its build status changed: not available to passing
• nottui-pretty.0.1 on 5.0+alpha-repo had its build status changed: partially failing to passing
• nottui-pretty.0.2 on 4.14 had its build status changed: not available to passing
• nottui-pretty.0.2 on 4.14+alpha-repo had its build status changed: partially failing to passing
• nottui-pretty.0.2 on 5.0 had its build status changed: not available to passing
• nottui-pretty.0.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
• nottui-pretty.0.3 on 4.03 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.04 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.05 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.06 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.07 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.08 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.09 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.10 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.11 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.12 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.13 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.14 is now installable. Current state is: passing
• nottui-pretty.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
• nottui-pretty.0.3 on 5.0 is now installable. Current state is: passing
• nottui-pretty.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
• nottui.0.1 on 4.14 had its build status changed: not available to passing
• nottui.0.1 on 4.14+alpha-repo had its build status changed: failing to passing
• nottui.0.1 on 5.0 had its build status changed: not available to passing
• nottui.0.1 on 5.0+alpha-repo had its build status changed: failing to passing
• nottui.0.2 on 4.14 had its build status changed: not available to passing
• nottui.0.2 on 4.14+alpha-repo had its build status changed: failing to passing
• nottui.0.2 on 5.0 had its build status changed: not available to passing
• nottui.0.2 on 5.0+alpha-repo had its build status changed: failing to passing
• nottui.0.3 on 4.03 is now installable. Current state is: passing
• nottui.0.3 on 4.04 is now installable. Current state is: passing
• nottui.0.3 on 4.05 is now installable. Current state is: passing
• nottui.0.3 on 4.06 is now installable. Current