opam-health-check diff

Home|Differences with the last checks|Previous runs

Differences between b1c9c96 and 06dca81 (git diff)

Packages now failing:

alba.0.4.1 on 5.0 had its build status changed: not available to failing
alba.0.4.2 on 5.0 had its build status changed: not available to failing
alba.0.4.3 on 5.0 had its build status changed: not available to failing
aws.1.0.0 on 5.0 had its build status changed: not available to failing
aws.1.0.0 on 5.0+alpha-repo had its build status changed: not available to failing
aws.1.0.1 on 5.0 had its build status changed: not available to failing
aws.1.0.1 on 5.0+alpha-repo had its build status changed: not available to failing
aws.1.0.2 on 5.0 had its build status changed: not available to failing
aws.1.0.2 on 5.0+alpha-repo had its build status changed: not available to failing
cfstream.1.3.1 on 5.0 had its build status changed: not available to failing
charrua-unix.1.2.2 on 5.0 had its build status changed: not available to failing
charrua-unix.1.3.0 on 5.0 had its build status changed: not available to failing
charrua-unix.1.4.0 on 5.0 had its build status changed: not available to failing
charrua-unix.1.4.1 on 5.0 had its build status changed: not available to failing
coccinelle.1.0.8 on 5.0 had its build status changed: partially failing to failing
coccinelle.1.0.8 on 5.0+alpha-repo had its build status changed: partially failing to failing
coccinelle.1.0.9 on 5.0 had its build status changed: partially failing to failing
coccinelle.1.0.9 on 5.0+alpha-repo had its build status changed: partially failing to failing
coccinelle.1.1.0 on 5.0 had its build status changed: partially failing to failing
coccinelle.1.1.0 on 5.0+alpha-repo had its build status changed: partially failing to failing
coccinelle.1.1.1 on 5.0 had its build status changed: partially failing to failing
coccinelle.1.1.1 on 5.0+alpha-repo had its build status changed: partially failing to failing
coclobas.0.0.2 on 4.03 had its build status changed: internal failure to failing
coq.8.10.0 on 4.05 had its build status changed: passing to failing
coq.8.10.1 on 4.08 had its build status changed: passing to failing
coq.8.10.2 on 4.05 had its build status changed: passing to failing
coq.8.11.1 on 4.10 had its build status changed: passing to failing
coq.8.11.1 on 4.11 had its build status changed: passing to failing
coq.8.11.2 on 4.08 had its build status changed: passing to failing
coq.8.12.0 on 4.06 had its build status changed: passing to failing
coq.8.12.2 on 4.10 had its build status changed: passing to failing
coq.8.13.0 on 4.05 had its build status changed: passing to failing
coq.8.13.1 on 4.09 had its build status changed: passing to failing
coq.8.13.1 on 4.10 had its build status changed: passing to failing
coq.8.13.1 on 4.12 had its build status changed: passing to failing
coq.8.14.0 on 4.08 had its build status changed: passing to failing
coq.8.14.1 on 4.11 had its build status changed: passing to failing
coq.8.15.0 on 4.05 had its build status changed: passing to failing
csvfields.v0.15.0 on 5.0 had its build status changed: not available to failing
dkml-component-staging-opam64.2.2.0~alpha0~20221104 on 5.0+alpha-repo is now installable. Current state is: failing
dns.4.1.0 on 5.0 had its build status changed: not available to failing
dns.4.2.0 on 5.0 had its build status changed: not available to failing
dns.4.3.0 on 5.0 had its build status changed: not available to failing
dns.4.3.1 on 5.0 had its build status changed: not available to failing
dns.4.4.0 on 5.0 had its build status changed: not available to failing
dns.4.4.1 on 5.0 had its build status changed: not available to failing
dns.4.5.0 on 5.0 had its build status changed: not available to failing
dns.4.6.0 on 5.0 had its build status changed: not available to failing
dns.4.6.1 on 5.0 had its build status changed: not available to failing
dns.4.6.2 on 5.0 had its build status changed: not available to failing
dns.4.6.3 on 5.0 had its build status changed: not available to failing
dream.1.0.0~alpha3 on 5.0+alpha-repo had its build status changed: partially failing to failing
gbddml.2.71.10 on 5.0 had its build status changed: partially failing to failing
gettext.0.3.8 on 5.0+alpha-repo had its build status changed: not available to failing
git.2.1.0 on 5.0 had its build status changed: not available to failing
gopcaml-mode.0.0.6 on 5.0 had its build status changed: not available to failing
hidapi.1.1.1.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
hidapi.1.1.1.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
kind2.1.3.0 on 5.0 had its build status changed: not available to failing
kind2.1.3.1 on 5.0 had its build status changed: not available to failing
kind2.1.4.0 on 5.0 had its build status changed: not available to failing
links.0.9.4 on 5.0 had its build status changed: not available to failing
links.0.9.4 on 5.0+alpha-repo had its build status changed: not available to failing
links.0.9.5 on 5.0 had its build status changed: not available to failing
links.0.9.5 on 5.0+alpha-repo had its build status changed: not available to failing
links.0.9.6 on 5.0 had its build status changed: not available to failing
links.0.9.6 on 5.0+alpha-repo had its build status changed: not available to failing
mirage-xen-minios.0.6.0 on 4.05 had its build status changed: internal failure to failing
mlcuddidl.3.0.6 on 5.0 had its build status changed: partially failing to failing
mlcuddidl.3.0.7 on 5.0 had its build status changed: partially failing to failing
obus.1.2.3.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
obus.1.2.3.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
ocal.0.1.1 on 5.0 had its build status changed: not available to failing
ocal.0.1.1 on 5.0+alpha-repo had its build status changed: not available to failing
ocal.0.1.2 on 5.0 had its build status changed: not available to failing
ocal.0.1.2 on 5.0+alpha-repo had its build status changed: not available to failing
ocaml-xdg-basedir.0.0.3 on 5.0 had its build status changed: not available to failing
ocaml-xdg-basedir.0.0.3 on 5.0+alpha-repo had its build status changed: not available to failing
ocamlfuse.2.7.1-cvs on 5.0 had its build status changed: partially failing to failing
ocamlfuse.2.7.1-cvs2 on 5.0 had its build status changed: partially failing to failing
ocamlfuse.2.7.1-cvs3 on 5.0 had its build status changed: partially failing to failing
ocamlfuse.2.7.1-cvs4 on 5.0 had its build status changed: partially failing to failing
ocamlfuse.2.7.1-cvs5 on 5.0 had its build status changed: partially failing to failing
ocamlfuse.2.7.1-cvs7 on 5.0 had its build status changed: partially failing to failing
ocsigen-toolkit.2.10.1 on 4.14+alpha-repo had its build status changed: passing to failing
ocsigen-toolkit.2.12.2 on 4.14+alpha-repo had its build status changed: passing to failing
ocsigen-toolkit.2.7.0 on 4.14+alpha-repo had its build status changed: passing to failing
ocsigen-toolkit.2.8.0 on 4.14+alpha-repo had its build status changed: passing to failing
ocsigen-toolkit.3.2.0 on 4.14+alpha-repo had its build status changed: passing to failing
osdp.0.6.0 on 5.0 had its build status changed: internal failure to failing
osdp.1.0.0 on 5.0+alpha-repo had its build status changed: internal failure to failing
pgocaml.2.2 on 5.0+alpha-repo had its build status changed: not available to failing
pgocaml.2.3 on 5.0 had its build status changed: not available to failing
pgocaml.2.3 on 5.0+alpha-repo had its build status changed: not available to failing
pgocaml.3.0 on 5.0 had its build status changed: not available to failing
pgocaml.3.0 on 5.0+alpha-repo had its build status changed: not available to failing
pgocaml.4.0 on 5.0 had its build status changed: not available to failing
pgocaml.4.0 on 5.0+alpha-repo had its build status changed: not available to failing
pgocaml.4.2 on 5.0 had its build status changed: not available to failing
pgocaml.4.2 on 5.0+alpha-repo had its build status changed: not available to failing
pgocaml.4.2.2 on 5.0 had its build status changed: not available to failing
pgocaml.4.2.2 on 5.0+alpha-repo had its build status changed: not available to failing
pgocaml.4.3.0 on 5.0 had its build status changed: not available to failing
pgocaml.4.3.0 on 5.0+alpha-repo had its build status changed: not available to failing
plist.0.1 on 5.0+alpha-repo had its build status changed: partially failing to failing
proverif.2.00 on 5.0 had its build status changed: not available to failing
proverif.2.00 on 5.0+alpha-repo had its build status changed: not available to failing
randoml.0.1.5 on 5.0 had its build status changed: not available to failing
session-postgresql-async.0.4.0 on 4.03 had its build status changed: partially failing to failing
session-postgresql-async.0.4.1 on 4.03 had its build status changed: partially failing to failing
solo5-bindings-hvt.0.6.6 on 4.10 had its build status changed: internal failure to failing
syndic.1.2 on 5.0 had its build status changed: not available to failing
syndic.1.2 on 5.0+alpha-repo had its build status changed: not available to failing
syndic.1.3 on 5.0 had its build status changed: not available to failing
syndic.1.3 on 5.0+alpha-repo had its build status changed: not available to failing
syndic.1.3.1 on 5.0 had its build status changed: not available to failing
syndic.1.3.1 on 5.0+alpha-repo had its build status changed: not available to failing
syndic.1.4 on 5.0 had its build status changed: not available to failing
syndic.1.4 on 5.0+alpha-repo had its build status changed: not available to failing
toplevel_backend.v0.15.0 on 5.0 had its build status changed: not available to failing
toplevel_expect_test.v0.15.0 on 5.0 had its build status changed: not available to failing
toplevel_expect_test.v0.15.0 on 5.0+alpha-repo had its build status changed: partially failing to failing
touist.3.0.0 on 5.0 had its build status changed: not available to failing
touist.3.0.0 on 5.0+alpha-repo had its build status changed: not available to failing
touist.3.1.0 on 5.0 had its build status changed: not available to failing
touist.3.1.0 on 5.0+alpha-repo had its build status changed: not available to failing
touist.3.2.0 on 5.0 had its build status changed: not available to failing
touist.3.2.0 on 5.0+alpha-repo had its build status changed: not available to failing
touist.3.2.1 on 5.0 had its build status changed: not available to failing
touist.3.2.1 on 5.0+alpha-repo had its build status changed: not available to failing
unison.2.51.4 on 5.0 had its build status changed: not available to failing
unison.2.51.4 on 5.0+alpha-repo had its build status changed: not available to failing
unison.2.51.5 on 5.0 had its build status changed: not available to failing
unison.2.51.5 on 5.0+alpha-repo had its build status changed: not available to failing
unison.2.52.0 on 5.0 had its build status changed: not available to failing
unison.2.52.0 on 5.0+alpha-repo had its build status changed: not available to failing
webmachine.0.4.0 on 4.08 had its build status changed: passing to failing
webmachine.0.4.0 on 4.09 had its build status changed: passing to failing
webmachine.0.4.0 on 4.10 had its build status changed: passing to failing
webmachine.0.4.0 on 4.11 had its build status changed: passing to failing
webmachine.0.4.0 on 4.12 had its build status changed: passing to failing
webmachine.0.4.0 on 4.13 had its build status changed: passing to failing
webmachine.0.4.0 on 4.14 had its build status changed: passing to failing
webmachine.0.4.0 on 4.14+alpha-repo had its build status changed: passing to failing
webmachine.0.4.0 on 5.0 had its build status changed: not available to failing
webmachine.0.4.0 on 5.0+alpha-repo had its build status changed: not available to failing
z3.4.10.1 on 4.10 had its build status changed: passing to failing
z3.4.10.2 on 4.10 had its build status changed: passing to failing
z3.4.10.2 on 4.14+alpha-repo had its build status changed: passing to failing
z3.4.11.0 on 4.09 had its build status changed: passing to failing
z3.4.11.2 on 4.14 had its build status changed: passing to failing
z3.4.11.2 on 4.14+alpha-repo had its build status changed: passing to failing
z3.4.7.1 on 4.13 had its build status changed: passing to failing
z3.4.7.1 on 4.14+alpha-repo had its build status changed: passing to failing
z3.4.8.1 on 4.06 had its build status changed: internal failure to failing
z3.4.8.1 on 4.08 had its build status changed: passing to failing
z3.4.8.1 on 4.14 had its build status changed: passing to failing
z3.4.8.13 on 4.04 had its build status changed: passing to failing
z3.4.8.14 on 4.14+alpha-repo had its build status changed: passing to failing
z3.4.8.4 on 4.09 had its build status changed: passing to failing
z3.4.8.5 on 4.13 had its build status changed: passing to failing
z3.4.8.6 on 4.02 had its build status changed: passing to failing
z3.4.8.7 on 4.13 had its build status changed: passing to failing
z3.4.8.8-1 on 4.03 had its build status changed: passing to failing
z3.4.8.8-1 on 4.10 had its build status changed: passing to failing
z3.4.8.9-1 on 4.03 had its build status changed: passing to failing
z3.4.8.9-1 on 4.05 had its build status changed: passing to failing
z3.4.8.9-1 on 4.08 had its build status changed: passing to failing
z3.4.9.1 on 4.14 had its build status changed: passing to failing
z3.4.9.1 on 4.14+alpha-repo had its build status changed: passing to failing
zmq.4.0-8 on 5.0 had its build status changed: not available to failing

Packages now partially failing:

0install-gtk.2.15.2 on 4.14+alpha-repo had its build status changed: passing to partially failing
0install-gtk.2.15.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
0install-gtk.2.16 on 4.14+alpha-repo had its build status changed: passing to partially failing
0install-gtk.2.16 on 5.0+alpha-repo had its build status changed: not available to partially failing
0install-gtk.2.17 on 4.14+alpha-repo had its build status changed: passing to partially failing
0install-gtk.2.17 on 5.0+alpha-repo had its build status changed: not available to partially failing
0install-gtk.2.18 on 4.14+alpha-repo had its build status changed: passing to partially failing
0install-gtk.2.18 on 5.0+alpha-repo had its build status changed: not available to partially failing
0install.2.15.2 on 4.14+alpha-repo had its build status changed: passing to partially failing
0install.2.16 on 4.14+alpha-repo had its build status changed: passing to partially failing
0install.2.17 on 4.14+alpha-repo had its build status changed: passing to partially failing
0install.2.18 on 4.14+alpha-repo had its build status changed: passing to partially failing
amqp-client-async.2.0.3 on 5.0 had its build status changed: not available to partially failing
amqp-client-async.2.1.0 on 5.0 had its build status changed: not available to partially failing
amqp-client-async.2.2.0 on 5.0 had its build status changed: not available to partially failing
amqp-client-async.2.2.1 on 5.0 had its build status changed: not available to partially failing
amqp-client-async.2.2.2 on 5.0 had its build status changed: not available to partially failing
aws-autoscaling.0.1.0 on 5.0 had its build status changed: not available to partially failing
aws-autoscaling.0.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
aws-cloudformation.0.1.0 on 5.0 had its build status changed: not available to partially failing
aws-cloudformation.0.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
aws-cloudtrail.0.1.0 on 5.0 had its build status changed: not available to partially failing
aws-cloudtrail.0.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
aws-ec2.0.1.0 on 5.0 had its build status changed: not available to partially failing
aws-ec2.0.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
aws-elasticloadbalancing.0.1.0 on 5.0 had its build status changed: not available to partially failing
aws-elasticloadbalancing.0.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
aws-s3-async.4.6.0 on 5.0 had its build status changed: not available to partially failing
aws-s3-async.4.7.0 on 5.0 had its build status changed: not available to partially failing
aws-s3-async.4.8.0 on 5.0 had its build status changed: not available to partially failing
aws-sdb.0.1.0 on 5.0 had its build status changed: not available to partially failing
aws-sdb.0.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
aws-ssm.0.1.0 on 5.0 had its build status changed: not available to partially failing
aws-ssm.0.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
aws-sts.0.1.0 on 5.0 had its build status changed: not available to partially failing
aws-sts.0.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
bap-objdump.1.0.0 on 4.02 had its build status changed: failing to partially failing
biocaml.0.11.0 on 5.0 had its build status changed: not available to partially failing
biocaml.0.11.1 on 5.0 had its build status changed: not available to partially failing
biocaml.0.11.2 on 5.0 had its build status changed: not available to partially failing
catala.0.3.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
catala.0.5.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
catala.0.6.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
cohttp-async.2.1.1 on 4.04 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.2.3.0 on 4.06 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.2.3.0 on 4.07 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.2.4.0 on 4.08 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.2.5.0 on 4.07 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.2.5.5 on 4.12 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.2.5.6 on 4.08 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.5.0.0 on 4.09 had its build status changed: passing to partially failing
cohttp-mirage.2.4.0 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.2.5.0 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.2.5.1 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.2.5.2 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.2.5.2-1 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.2.5.3 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.2.5.4 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.2.5.5 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.2.5.6 on 5.0 had its build status changed: not available to partially failing
cohttp-mirage.4.0.0 on 5.0 had its build status changed: not available to partially failing
cohttp-top.1.0.0 on 4.05 had its build status changed: passing to partially failing
cohttp-top.2.5.4 on 4.10 had its build status changed: passing to partially failing
cohttp-top.2.5.5 on 4.05 had its build status changed: passing to partially failing
cohttp-top.2.5.6 on 4.13 had its build status changed: passing to partially failing
colibrics.0.3.3 on 5.0 had its build status changed: not available to partially failing
conduit-mirage.2.1.0 on 5.0 had its build status changed: not available to partially failing
conduit-mirage.2.2.1 on 5.0 had its build status changed: not available to partially failing
conduit-mirage.2.3.0 on 5.0 had its build status changed: not available to partially failing
coq-serapi.8.12.0+0.12.1 on 4.09 had its build status changed: passing to partially failing
coq-serapi.8.15.0+0.15.1 on 4.08 had its build status changed: passing to partially failing
coq-serapi.8.15.0+0.15.2 on 4.11 had its build status changed: passing to partially failing
coq-serapi.8.8.0+0.5.4 on 4.09 had its build status changed: passing to partially failing
coq-serapi.8.9.0+0.6.0 on 4.07 had its build status changed: passing to partially failing
deadlock.1.0 on 5.0 had its build status changed: not available to partially failing
deadlock.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
dkim-mirage.0.1.0 on 5.0 had its build status changed: not available to partially failing
dkim.0.1.0 on 5.0 had its build status changed: not available to partially failing
dkml-component-offline-opam.2.2.0~alpha0~20221104 on 5.0+alpha-repo is now installable. Current state is: partially failing
dns-certify.4.4.0 on 5.0 had its build status changed: not available to partially failing
dns-certify.4.4.1 on 5.0 had its build status changed: not available to partially failing
dns-certify.4.5.0 on 5.0 had its build status changed: not available to partially failing
dns-certify.4.6.0 on 5.0 had its build status changed: not available to partially failing
dns-certify.4.6.1 on 5.0 had its build status changed: not available to partially failing
dns-certify.4.6.2 on 5.0 had its build status changed: not available to partially failing
dns-certify.4.6.3 on 5.0 had its build status changed: not available to partially failing
dns-cli.4.4.0 on 5.0 had its build status changed: not available to partially failing
dns-cli.4.4.1 on 5.0 had its build status changed: not available to partially failing
dns-cli.4.5.0 on 5.0 had its build status changed: not available to partially failing
dns-cli.4.6.1 on 5.0 had its build status changed: not available to partially failing
dns-cli.4.6.2 on 5.0 had its build status changed: not available to partially failing
dns-cli.4.6.3 on 5.0 had its build status changed: not available to partially failing
dns-client.4.1.0 on 5.0 had its build status changed: not available to partially failing
dns-client.4.2.0 on 5.0 had its build status changed: not available to partially failing
dns-client.4.3.0 on 5.0 had its build status changed: not available to partially failing
dns-client.4.3.1 on 5.0 had its build status changed: not available to partially failing
dns-client.4.4.0 on 5.0 had its build status changed: not available to partially failing
dns-client.4.4.1 on 5.0 had its build status changed: not available to partially failing
dns-client.4.5.0 on 5.0 had its build status changed: not available to partially failing
dns-client.4.6.0 on 5.0 had its build status changed: not available to partially failing
dns-client.4.6.1 on 5.0 had its build status changed: not available to partially failing
dns-client.4.6.2 on 5.0 had its build status changed: not available to partially failing
dns-client.4.6.3 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.1.0 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.2.0 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.3.0 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.3.1 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.4.0 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.4.1 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.5.0 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.6.0 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.6.1 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.6.2 on 5.0 had its build status changed: not available to partially failing
dns-mirage.4.6.3 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.1.0 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.2.0 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.3.0 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.3.1 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.4.0 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.4.1 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.5.0 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.6.0 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.6.1 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.6.2 on 5.0 had its build status changed: not available to partially failing
dns-resolver.4.6.3 on 5.0 had its build status changed: not available to partially failing
dns-server.4.1.0 on 5.0 had its build status changed: not available to partially failing
dns-server.4.2.0 on 5.0 had its build status changed: not available to partially failing
dns-server.4.3.0 on 5.0 had its build status changed: not available to partially failing
dns-server.4.3.1 on 5.0 had its build status changed: not available to partially failing
dns-server.4.4.0 on 5.0 had its build status changed: not available to partially failing
dns-server.4.4.1 on 5.0 had its build status changed: not available to partially failing
dns-server.4.5.0 on 5.0 had its build status changed: not available to partially failing
dns-server.4.6.0 on 5.0 had its build status changed: not available to partially failing
dns-server.4.6.1 on 5.0 had its build status changed: not available to partially failing
dns-server.4.6.2 on 5.0 had its build status changed: not available to partially failing
dns-server.4.6.3 on 5.0 had its build status changed: not available to partially failing
dns-stub.4.4.0 on 5.0 had its build status changed: not available to partially failing
dns-stub.4.4.1 on 5.0 had its build status changed: not available to partially failing
dns-stub.4.5.0 on 5.0 had its build status changed: not available to partially failing
dns-stub.4.6.0 on 5.0 had its build status changed: not available to partially failing
dns-stub.4.6.1 on 5.0 had its build status changed: not available to partially failing
dns-stub.4.6.2 on 5.0 had its build status changed: not available to partially failing
dns-stub.4.6.3 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.1.0 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.2.0 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.3.0 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.3.1 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.4.0 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.4.1 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.5.0 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.6.0 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.6.1 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.6.2 on 5.0 had its build status changed: not available to partially failing
dns-tsig.4.6.3 on 5.0 had its build status changed: not available to partially failing
eliom.10.0.0 on 5.0 had its build status changed: not available to partially failing
eliom.8.9.0 on 5.0 had its build status changed: not available to partially failing
eliom.9.0.0 on 5.0 had its build status changed: not available to partially failing
eliom.9.2.1 on 5.0 had its build status changed: not available to partially failing
eliom.9.3.0 on 5.0 had its build status changed: not available to partially failing
eliom.9.4.0 on 5.0 had its build status changed: not available to partially failing
ez_pgocaml.1.0.0 on 5.0 had its build status changed: not available to partially failing
ez_pgocaml.1.0.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
ezjs_timeline.0.1 on 4.14+alpha-repo had its build status changed: passing to partially failing
ezjs_timeline.0.1.1 on 4.14+alpha-repo had its build status changed: passing to partially failing
fmlib.0.5.0 on 5.0 had its build status changed: not available to partially failing
fmlib.0.5.1 on 5.0 had its build status changed: not available to partially failing
frama-c-lannotate.0.1 on 5.0 had its build status changed: not available to partially failing
frama-c-lannotate.0.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c-lannotate.0.2 on 5.0 had its build status changed: not available to partially failing
frama-c-lannotate.0.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c-luncov.0.1 on 5.0 had its build status changed: not available to partially failing
frama-c-luncov.0.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c-luncov.0.2 on 5.0 had its build status changed: not available to partially failing
frama-c-luncov.0.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c-metacsl.0.1 on 5.0 had its build status changed: not available to partially failing
frama-c-metacsl.0.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c-metacsl.0.2 on 5.0 had its build status changed: not available to partially failing
frama-c-metacsl.0.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c-metacsl.0.3 on 5.0 had its build status changed: not available to partially failing
frama-c-metacsl.0.3 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c.22.0 on 5.0 had its build status changed: not available to partially failing
frama-c.22.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c.24.0 on 5.0 had its build status changed: not available to partially failing
frama-c.24.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c.25.0 on 5.0 had its build status changed: not available to partially failing
frama-c.25.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
frama-c.25.0~beta on 5.0 had its build status changed: not available to partially failing
frama-c.25.0~beta on 5.0+alpha-repo had its build status changed: not available to partially failing
git-mirage.2.1.3 on 5.0 had its build status changed: not available to partially failing
git.1.7.1 on 4.02 had its build status changed: passing to partially failing
gluten-mirage.0.2.1 on 5.0 had its build status changed: not available to partially failing
guardian.0.0.4 on 5.0+alpha-repo is now installable. Current state is: partially failing
guardian.0.0.5 on 5.0+alpha-repo is now installable. Current state is: partially failing
h2-mirage.0.6.1 on 5.0 had its build status changed: not available to partially failing
h2-mirage.0.8.0 on 5.0 had its build status changed: not available to partially failing
irmin-mirage-git.2.0.0 on 5.0 had its build status changed: not available to partially failing
irmin-mirage-git.2.2.0 on 5.0 had its build status changed: not available to partially failing
irmin-mirage-graphql.2.0.0 on 5.0 had its build status changed: not available to partially failing
irmin-mirage-graphql.2.2.0 on 5.0 had its build status changed: not available to partially failing
libres3.1.0 on 4.02 had its build status changed: internal failure to partially failing
links-mysql.0.9.4 on 5.0 had its build status changed: not available to partially failing
links-mysql.0.9.4 on 5.0+alpha-repo had its build status changed: not available to partially failing
links-mysql.0.9.5 on 5.0 had its build status changed: not available to partially failing
links-mysql.0.9.5 on 5.0+alpha-repo had its build status changed: not available to partially failing
links-mysql.0.9.6 on 5.0 had its build status changed: not available to partially failing
links-mysql.0.9.6 on 5.0+alpha-repo had its build status changed: not available to partially failing
links-postgresql.0.9.4 on 5.0 had its build status changed: not available to partially failing
links-postgresql.0.9.4 on 5.0+alpha-repo had its build status changed: not available to partially failing
links-postgresql.0.9.5 on 5.0 had its build status changed: not available to partially failing
links-postgresql.0.9.5 on 5.0+alpha-repo had its build status changed: not available to partially failing
links-postgresql.0.9.6 on 5.0 had its build status changed: not available to partially failing
links-postgresql.0.9.6 on 5.0+alpha-repo had its build status changed: not available to partially failing
links-sqlite3.0.9.4 on 5.0 had its build status changed: not available to partially failing
links-sqlite3.0.9.4 on 5.0+alpha-repo had its build status changed: not available to partially failing
links-sqlite3.0.9.5 on 5.0 had its build status changed: not available to partially failing
links-sqlite3.0.9.5 on 5.0+alpha-repo had its build status changed: not available to partially failing
links-sqlite3.0.9.6 on 5.0 had its build status changed: not available to partially failing
links-sqlite3.0.9.6 on 5.0+alpha-repo had its build status changed: not available to partially failing
macaque.0.7.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
mirage-monitoring.0.0.2 on 5.0 had its build status changed: not available to partially failing
mirage-monitoring.0.0.3 on 5.0 had its build status changed: not available to partially failing
mpris-clients.0.2.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
mpris.0.2.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocaml-option-address-sanitizer.1 on 5.0 is now installable. Current state is: partially failing
ocaml-option-address-sanitizer.1 on 5.0+alpha-repo is now installable. Current state is: partially failing
ocplib-json-typed-browser.0.7 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocplib-json-typed-browser.0.7.1 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.4.1.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.4.3.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.4.4.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.4.5.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.4.6.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.4.7.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.5.0.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.6.0.1 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-start.6.1.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ocsigen-toolkit.2.10.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsigen-toolkit.2.12.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsigen-toolkit.2.7.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsigen-toolkit.2.8.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsigen-toolkit.3.2.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0 on 5.0 had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.1 on 5.0 had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.2 on 5.0 had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.3 on 5.0 had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.3 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.4 on 5.0 had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.4 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.5 on 5.0 had its build status changed: not available to partially failing
ocsipersist-pgsql.1.0.5 on 5.0+alpha-repo had its build status changed: not available to partially failing
ocsipersist-pgsql.1.1.0 on 5.0 had its build status changed: not available to partially failing
ocsipersist-pgsql.1.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
orpie.1.6.1 on 4.12 had its build status changed: passing to partially failing
pgocaml_ppx.4.3.0 on 5.0 had its build status changed: not available to partially failing
pgocaml_ppx.4.3.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
phylogenetics.0.0.0 on 4.12 had its build status changed: passing to partially failing
pilat.1.6 on 5.0 had its build status changed: not available to partially failing
pilat.1.6 on 5.0+alpha-repo had its build status changed: not available to partially failing
prc.0.0.0 on 4.12 had its build status changed: passing to partially failing
prc.0.0.0 on 5.0 had its build status changed: not available to partially failing
prc.0.1.0 on 4.12 had its build status changed: passing to partially failing
prc.0.1.0 on 5.0 had its build status changed: not available to partially failing
regular.1.4.0 on 4.03 had its build status changed: passing to partially failing
spatial_index.0.0.1 on 4.02 had its build status changed: passing to partially failing
why3-coq.1.3.1 on 4.07 had its build status changed: passing to partially failing
why3-coq.1.3.2 on 4.05 had its build status changed: passing to partially failing
why3-coq.1.3.3 on 4.10 had its build status changed: passing to partially failing
why3-coq.1.4.1 on 4.07 had its build status changed: passing to partially failing
why3-coq.1.5.0 on 4.05 had its build status changed: passing to partially failing
why3-ide.1.3.0 on 5.0 had its build status changed: not available to partially failing
why3-ide.1.3.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
why3-ide.1.3.1 on 5.0 had its build status changed: not available to partially failing
why3-ide.1.3.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
why3-ide.1.3.2 on 5.0 had its build status changed: not available to partially failing
why3-ide.1.3.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
why3-ide.1.3.3 on 5.0 had its build status changed: not available to partially failing
why3-ide.1.3.3 on 5.0+alpha-repo had its build status changed: not available to partially failing
why3-ide.1.4.0 on 5.0 had its build status changed: not available to partially failing
why3-ide.1.4.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
why3-ide.1.4.1 on 5.0 had its build status changed: not available to partially failing
why3-ide.1.4.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
why3-ide.1.5.0 on 5.0 had its build status changed: not available to partially failing
why3-ide.1.5.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
z3_tptp.4.10.2 on 4.08 had its build status changed: passing to partially failing
z3_tptp.4.10.2 on 4.14+alpha-repo had its build status changed: passing to partially failing
z3_tptp.4.8.13 on 4.03 had its build status changed: passing to partially failing
z3_tptp.4.8.17 on 4.10 had its build status changed: passing to partially failing
z3_tptp.4.9.1 on 4.14 had its build status changed: passing to partially failing
zarith-ppx.0.1 on 4.12 had its build status changed: passing to partially failing
zmq-async.5.1.1 on 5.0 had its build status changed: not available to partially failing
zmq-async.5.1.5 on 5.0 had its build status changed: not available to partially failing
zxcvbn.2.0+2 on 4.05 had its build status changed: passing to partially failing

Packages now not available:

0install.2.15.2 on 5.0 had its build status changed: partially failing to not available
0install.2.16 on 5.0 had its build status changed: partially failing to not available
0install.2.17 on 5.0 had its build status changed: partially failing to not available
0install.2.18 on 5.0 had its build status changed: partially failing to not available
absolute.0.1 on 5.0 had its build status changed: partially failing to not available
absolute.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
alt-ergo-lib.2.3.0 on 5.0+alpha-repo had its build status changed: failing to not available
alt-ergo-lib.2.3.1 on 5.0+alpha-repo had its build status changed: failing to not available
alt-ergo-lib.2.3.2 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo-lib.2.3.3 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo-lib.2.4.0 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo-lib.2.4.1 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo-parsers.2.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
alt-ergo-parsers.2.3.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
alt-ergo-parsers.2.3.2 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo-parsers.2.3.3 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo-parsers.2.4.0 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo-parsers.2.4.1 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo.2.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
alt-ergo.2.3.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
alt-ergo.2.3.2 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo.2.3.3 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo.2.4.0 on 5.0+alpha-repo had its build status changed: passing to not available
alt-ergo.2.4.1 on 5.0+alpha-repo had its build status changed: passing to not available
apron.20150820 on 5.0 had its build status changed: partially failing to not available
apron.20150820 on 5.0+alpha-repo had its build status changed: partially failing to not available
apron.20150930 on 5.0 had its build status changed: partially failing to not available
apron.20150930 on 5.0+alpha-repo had its build status changed: partially failing to not available
apron.20151015 on 5.0 had its build status changed: partially failing to not available
apron.20151015 on 5.0+alpha-repo had its build status changed: partially failing to not available
apron.20160108 on 5.0 had its build status changed: partially failing to not available
apron.20160108 on 5.0+alpha-repo had its build status changed: partially failing to not available
apron.20160125 on 5.0 had its build status changed: partially failing to not available
apron.20160125 on 5.0+alpha-repo had its build status changed: partially failing to not available
apron.v0.9.12 on 5.0 had its build status changed: partially failing to not available
apron.v0.9.12 on 5.0+alpha-repo had its build status changed: partially failing to not available
apron.v0.9.13 on 5.0 had its build status changed: partially failing to not available
apron.v0.9.13 on 5.0+alpha-repo had its build status changed: partially failing to not available
apronext.1.0 on 5.0 had its build status changed: partially failing to not available
apronext.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
apronext.1.0.1 on 5.0 had its build status changed: partially failing to not available
apronext.1.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
apronext.1.0.2 on 5.0 had its build status changed: partially failing to not available
apronext.1.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
apronext.1.0.3 on 5.0 had its build status changed: partially failing to not available
apronext.1.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
apronext.1.0.4 on 5.0 had its build status changed: partially failing to not available
apronext.1.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
asli.0.1 on 5.0 had its build status changed: partially failing to not available
asli.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
asli.0.2.0 on 5.0 had its build status changed: partially failing to not available
asli.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
atd.2.2.1 on 5.0 had its build status changed: failing to not available
atd.2.2.1 on 5.0+alpha-repo had its build status changed: failing to not available
atd.2.2.1.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
atd.2.2.1.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
atdgen-codec-runtime.2.2.1.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
atdgen-runtime.2.2.1.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
atdgen.2.2.1 on 5.0 had its build status changed: partially failing to not available
atdgen.2.2.1.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
atdgen.2.2.1.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
atdj.2.2.1 on 5.0 had its build status changed: partially failing to not available
atds.2.2.1 on 5.0 had its build status changed: partially failing to not available
atds.2.2.1.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
atds.2.2.1.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
bechamel-js.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
bechamel-js.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
bechamel-js.0.2.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
bechamel-js.0.2.0.1~alpha-repo on 5.0+alpha-repo had its build status changed: failing to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
bechamel-notty.0.2.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
bechamel.0.2.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
biniou.1.2.1.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
bisect_ppx.2.8.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
blake2.0.3 on 5.0+alpha-repo had its build status changed: passing to not available
bz2.0.7.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
bz2.0.7.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
calculon-web.0.7 on 5.0 had its build status changed: partially failing to not available
calculon-web.0.8 on 5.0 had its build status changed: partially failing to not available
camlbz2.transition on 4.02 had its build status changed: internal failure to not available
camlbz2.transition on 4.03 had its build status changed: internal failure to not available
camlbz2.transition on 4.04 had its build status changed: internal failure to not available
camlbz2.transition on 4.05 had its build status changed: internal failure to not available
camlbz2.transition on 4.06 had its build status changed: internal failure to not available
camlbz2.transition on 4.07 had its build status changed: internal failure to not available
camlbz2.transition on 4.08 had its build status changed: internal failure to not available
camlbz2.transition on 4.09 had its build status changed: internal failure to not available
camlbz2.transition on 4.10 had its build status changed: internal failure to not available
camlbz2.transition on 4.11 had its build status changed: internal failure to not available
camlbz2.transition on 4.12 had its build status changed: internal failure to not available
camlbz2.transition on 4.13 had its build status changed: internal failure to not available
camlbz2.transition on 4.14 had its build status changed: internal failure to not available
camlbz2.transition on 5.0 had its build status changed: internal failure to not available
camlidl.1.05 on 5.0 had its build status changed: failing to not available
camlidl.1.05 on 5.0+alpha-repo had its build status changed: failing to not available
camlidl.1.07 on 5.0 had its build status changed: failing to not available
camlidl.1.07 on 5.0+alpha-repo had its build status changed: failing to not available
camlidl.1.09 on 5.0 had its build status changed: failing to not available
camlidl.1.09 on 5.0+alpha-repo had its build status changed: failing to not available
camlidl.1.09.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
camlidl.1.09.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
camlidl.1.09.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
camlon.3.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
camlp4.5.0+1~alpha-repo on 4.02 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.03 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.04 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.05 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.06 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.07 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.08 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.09 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.10 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.11 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.12 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.13 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 4.14 had its build status changed: internal failure to not available
camlp4.5.0+1~alpha-repo on 5.0 had its build status changed: internal failure to not available
camlpdf.2.3 on 5.0 had its build status changed: failing to not available
camlpdf.2.3 on 5.0+alpha-repo had its build status changed: failing to not available
camlpdf.2.4 on 5.0 had its build status changed: failing to not available
camlpdf.2.4 on 5.0+alpha-repo had its build status changed: failing to not available
camlpdf.2.5 on 5.0 had its build status changed: failing to not available
camlpdf.2.5 on 5.0+alpha-repo had its build status changed: failing to not available
camomile.1.0.2.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
camomile.1.0.2.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
clap.0.1.0 on 5.0+alpha-repo had its build status changed: passing to not available
cohttp.0.11.0 on 4.03 had its build status changed: internal failure to not available
cohttp.0.11.2 on 4.12 had its build status changed: internal failure to not available
cohttp.0.12.0 on 4.12 had its build status changed: internal failure to not available
cohttp.0.13.0 on 4.12 had its build status changed: internal failure to not available
cohttp.0.15.0 on 4.07 had its build status changed: internal failure to not available
cohttp.0.16.0 on 4.03 had its build status changed: internal failure to not available
cohttp.0.16.0 on 5.0+alpha-repo had its build status changed: internal failure to not available
cohttp.0.17.1 on 4.05 had its build status changed: internal failure to not available
cohttp.0.17.2 on 4.06 had its build status changed: internal failure to not available
command_rpc.v0.10.0 on 5.0 had its build status changed: internal failure to not available
comparelib.108.00.02 on 4.06 had its build status changed: internal failure to not available
conduit-mirage.4.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
conduit-mirage.4.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
conduit-mirage.4.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
conduit-mirage.6.0.0 on 4.08 is not available anymore. Previous state was: passing
conduit-mirage.6.0.0 on 4.09 is not available anymore. Previous state was: passing
conduit-mirage.6.0.0 on 4.10 is not available anymore. Previous state was: passing
conduit-mirage.6.0.0 on 4.11 is not available anymore. Previous state was: passing
conduit-mirage.6.0.0 on 4.12 is not available anymore. Previous state was: passing
conduit-mirage.6.0.0 on 4.13 is not available anymore. Previous state was: passing
conduit-mirage.6.0.0 on 4.14 is not available anymore. Previous state was: passing
conduit-mirage.6.0.0 on 4.14+alpha-repo is not available anymore. Previous state was: passing
conduit-mirage.6.0.0 on 5.0+alpha-repo is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.02 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.03 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.04 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.05 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.06 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.07 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.08 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.09 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.10 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.11 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.12 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.13 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.14 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 4.14+alpha-repo is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 5.0 is not available anymore. Previous state was: passing
conf-llvm.11.0.0 on 5.0+alpha-repo is not available anymore. Previous state was: passing
core.v0.15.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
core.v0.15.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
core_unix.v0.15.0 on 5.0+alpha-repo had its build status changed: passing to not available
core_unix.v0.15.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
core_unix.v0.15.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
core_unix.v0.15.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
cpdf.2.3 on 5.0 had its build status changed: partially failing to not available
cpdf.2.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
cpdf.2.4 on 5.0 had its build status changed: partially failing to not available
cpdf.2.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
cpdf.2.5 on 5.0 had its build status changed: partially failing to not available
cpdf.2.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
current_gitlab.0.6 on 5.0 had its build status changed: partially failing to not available
data-encoding.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
data-encoding.0.1.1 on 5.0+alpha-repo had its build status changed: failing to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
datakit-client-9p.1.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
datakit-client.1.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
dkim-mirage.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dkim.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-certify.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-certify.5.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-cli.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-cli.5.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-client.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-client.5.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-mirage.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-mirage.5.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-resolver.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-resolver.5.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-server.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-server.5.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-stub.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-stub.5.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-tsig.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns-tsig.5.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
dns.5.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
dns.5.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
dokeysto.3.0.1 on 5.0+alpha-repo had its build status changed: passing to not available
dokeysto_camltc.3.0.1 on 5.0+alpha-repo had its build status changed: passing to not available
dream-livereload.0.1.0 on 5.0 had its build status changed: partially failing to not available
dream-livereload.0.2.0 on 5.0 had its build status changed: partially failing to not available
dream-serve.1.0.0 on 5.0 had its build status changed: partially failing to not available
drom.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
drom.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
drom.0.6.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
drom_lib.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
drom_lib.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
drom_lib.0.6.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
dune.2.9.3.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
dune.2.9.3.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
dune.2.9.3.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
dune.3.2.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
dune.3.2.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
dune.3.2.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
dune.3.2.0.2~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
dune.3.2.0.2~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
dune.3.2.0.2~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
easy-format.1.3.2.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
easy-format.1.3.2.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
elina.1.0 on 5.0 had its build status changed: partially failing to not available
elina.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
elina.1.1 on 5.0 had its build status changed: partially failing to not available
elina.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
elina.1.3 on 5.0 had its build status changed: internal failure to not available
elina.1.3 on 5.0+alpha-repo had its build status changed: internal failure to not available
elina.1.3.1 on 5.0 had its build status changed: partially failing to not available
elina.1.3.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
elina.1.3.2 on 5.0 had its build status changed: partially failing to not available
elina.1.3.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
extlib.1.7.8.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
extlib.1.7.8.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
extlib.1.7.8.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
ez_cmdliner.0.1.1 on 5.0+alpha-repo had its build status changed: passing to not available
ez_config.0.1.1 on 5.0+alpha-repo had its build status changed: failing to not available
ez_file.0.1.2 on 5.0+alpha-repo had its build status changed: passing to not available
ez_file.0.2.0 on 5.0+alpha-repo had its build status changed: passing to not available
ez_hash.0.2.0 on 5.0+alpha-repo had its build status changed: passing to not available
ezjs_timeline.0.1 on 5.0+alpha-repo had its build status changed: passing to not available
ezjs_timeline.0.1.1 on 5.0+alpha-repo had its build status changed: passing to not available
ezresto.0.2 on 5.0+alpha-repo had its build status changed: passing to not available
fd-send-recv.2.0.1 on 5.0 had its build status changed: passing to not available
fd-send-recv.2.0.1 on 5.0+alpha-repo had its build status changed: passing to not available
ffmpeg.0.1.0 on 5.0 had its build status changed: internal failure to not available
ffmpeg.0.1.0 on 5.0+alpha-repo had its build status changed: internal failure to not available
ffmpeg.0.1.1 on 5.0 had its build status changed: internal failure to not available
ffmpeg.0.1.1 on 5.0+alpha-repo had its build status changed: internal failure to not available
ffmpeg.0.1.2 on 5.0 had its build status changed: passing to not available
ffmpeg.0.1.2 on 5.0+alpha-repo had its build status changed: passing to not available
ffmpeg.0.2.0 on 5.0 had its build status changed: internal failure to not available
ffmpeg.0.2.0 on 5.0+alpha-repo had its build status changed: internal failure to not available
ffmpeg.0.2.1 on 5.0 had its build status changed: internal failure to not available
ffmpeg.0.2.1 on 5.0+alpha-repo had its build status changed: internal failure to not available
ffmpeg.0.3.0 on 5.0 had its build status changed: internal failure to not available
ffmpeg.0.3.0 on 5.0+alpha-repo had its build status changed: internal failure to not available
ffmpeg.0.4.0 on 5.0 had its build status changed: internal failure to not available
ffmpeg.0.4.0 on 5.0+alpha-repo had its build status changed: internal failure to not available
ffmpeg.0.4.1 on 5.0 had its build status changed: internal failure to not available
ffmpeg.0.4.1 on 5.0+alpha-repo had its build status changed: internal failure to not available
ffmpeg.0.4.2 on 5.0 had its build status changed: failing to not available
ffmpeg.0.4.2 on 5.0+alpha-repo had its build status changed: failing to not available
ffmpeg.0.4.3 on 5.0 had its build status changed: failing to not available
ffmpeg.0.4.3 on 5.0+alpha-repo had its build status changed: failing to not available
genspir.1.0.0 on 5.0+alpha-repo had its build status changed: passing to not available
gitlab-unix.0.1.0 on 5.0 had its build status changed: partially failing to not available
gitlab-unix.0.1.1 on 5.0 had its build status changed: partially failing to not available
gitlab-unix.0.1.2 on 5.0 had its build status changed: partially failing to not available
gitlab.0.1.0 on 5.0 had its build status changed: partially failing to not available
gitlab.0.1.1 on 5.0 had its build status changed: partially failing to not available
gitlab.0.1.2 on 5.0 had its build status changed: partially failing to not available
h2-lwt-unix.0.1.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt-unix.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt-unix.0.2.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt-unix.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt-unix.0.3.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt-unix.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt-unix.0.4.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt-unix.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt-unix.0.5.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt-unix.0.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt-unix.0.6.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt-unix.0.6.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt.0.1.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt.0.2.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt.0.3.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt.0.4.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt.0.5.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt.0.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt.0.6.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt.0.6.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-lwt.0.8.0 on 5.0 had its build status changed: partially failing to not available
h2-lwt.0.8.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-mirage.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2-mirage.0.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
h2.0.1.0 on 5.0 had its build status changed: failing to not available
h2.0.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
h2.0.2.0 on 5.0 had its build status changed: failing to not available
h2.0.2.0 on 5.0+alpha-repo had its build status changed: failing to not available
h2.0.3.0 on 5.0 had its build status changed: failing to not available
h2.0.3.0 on 5.0+alpha-repo had its build status changed: failing to not available
h2.0.4.0 on 5.0 had its build status changed: failing to not available
h2.0.4.0 on 5.0+alpha-repo had its build status changed: failing to not available
h2.0.5.0 on 5.0 had its build status changed: failing to not available
h2.0.5.0 on 5.0+alpha-repo had its build status changed: failing to not available
h2.0.6.0 on 5.0 had its build status changed: failing to not available
h2.0.6.0 on 5.0+alpha-repo had its build status changed: failing to not available
h2.0.7.0 on 5.0 had its build status changed: failing to not available
h2.0.7.0 on 5.0+alpha-repo had its build status changed: failing to not available
h2.0.8.0 on 5.0 had its build status changed: failing to not available
h2.0.8.0 on 5.0+alpha-repo had its build status changed: failing to not available
h2.0.8.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
h2.0.8.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
hacl.0.3 on 5.0+alpha-repo had its build status changed: passing to not available
happy-eyeballs-lwt.0.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-lwt.0.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-lwt.0.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-lwt.0.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-lwt.0.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-lwt.0.0.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-lwt.0.0.7 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-mirage.0.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-mirage.0.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-mirage.0.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-mirage.0.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-mirage.0.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-mirage.0.0.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
happy-eyeballs-mirage.0.0.7 on 5.0+alpha-repo had its build status changed: partially failing to not available
hashcons.1.0.1 on 5.0 had its build status changed: failing to not available
hashcons.1.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
hidapi.1.1.1 on 5.0 had its build status changed: failing to not available
hidapi.1.1.1 on 5.0+alpha-repo had its build status changed: failing to not available
iter.1.2.1 on 5.0+alpha-repo had its build status changed: failing to not available
iter.1.3 on 5.0+alpha-repo had its build status changed: failing to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
js_of_ocaml-compiler.4.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
js_of_ocaml-lwt.4.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
js_of_ocaml-ppx.4.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
js_of_ocaml-ppx_deriving_json.4.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
js_of_ocaml-toplevel.4.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
js_of_ocaml-tyxml.4.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
js_of_ocaml.4.0.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
lab.0.1.0 on 5.0 had its build status changed: partially failing to not available
lab.0.1.1 on 5.0 had its build status changed: partially failing to not available
lab.0.1.2 on 5.0 had its build status changed: partially failing to not available
lablgl.1.06.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
lablgl.1.06.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
labrys.0.1 on 4.04 is not available anymore. Previous state was: passing
labrys.0.1 on 4.05 is not available anymore. Previous state was: passing
labrys.0.1 on 4.06 is not available anymore. Previous state was: passing
labrys.0.1 on 4.07 is not available anymore. Previous state was: passing
labrys.0.1 on 4.08 is not available anymore. Previous state was: passing
labrys.0.1 on 4.09 is not available anymore. Previous state was: passing
labrys.0.1 on 4.10 is not available anymore. Previous state was: passing
labrys.0.1 on 4.11 is not available anymore. Previous state was: passing
labrys.0.1 on 4.12 is not available anymore. Previous state was: passing
labrys.0.1 on 4.13 is not available anymore. Previous state was: passing
labrys.0.1 on 4.14 is not available anymore. Previous state was: passing
labrys.0.1 on 4.14+alpha-repo is not available anymore. Previous state was: passing
lambdasoup.0.5 on 5.0 had its build status changed: failing to not available
lambdasoup.0.5 on 5.0+alpha-repo had its build status changed: failing to not available
lambdasoup.0.5.1 on 5.0 had its build status changed: failing to not available
lambdasoup.0.5.1 on 5.0+alpha-repo had its build status changed: failing to not available
lambdasoup.0.6 on 5.0 had its build status changed: failing to not available
lambdasoup.0.6 on 5.0+alpha-repo had its build status changed: failing to not available
lambdasoup.0.6.1 on 5.0 had its build status changed: failing to not available
lambdasoup.0.6.1 on 5.0+alpha-repo had its build status changed: failing to not available
lambdasoup.0.6.4 on 5.0 had its build status changed: failing to not available
lambdasoup.0.6.4 on 5.0+alpha-repo had its build status changed: failing to not available
lambdasoup.0.7.0 on 5.0 had its build status changed: failing to not available
lambdasoup.0.7.0 on 5.0+alpha-repo had its build status changed: failing to not available
lambdasoup.0.7.1 on 5.0 had its build status changed: failing to not available
lambdasoup.0.7.1 on 5.0+alpha-repo had its build status changed: failing to not available
lambdasoup.0.7.2 on 5.0 had its build status changed: failing to not available
lambdasoup.0.7.2 on 5.0+alpha-repo had its build status changed: failing to not available
lambdasoup.0.7.3 on 5.0 had its build status changed: failing to not available
lambdasoup.0.7.3 on 5.0+alpha-repo had its build status changed: failing to not available
lem.2020-06-03 on 5.0 had its build status changed: failing to not available
lem.2020-06-03 on 5.0+alpha-repo had its build status changed: failing to not available
libbinaryen.105.1.0 on 5.0+alpha-repo had its build status changed: passing to not available
libbinaryen.106.0.0 on 5.0+alpha-repo had its build status changed: passing to not available
libbinaryen.107.0.0 on 5.0+alpha-repo had its build status changed: passing to not available
linksem.0.7 on 5.0 had its build status changed: partially failing to not available
linksem.0.7 on 5.0+alpha-repo had its build status changed: partially failing to not available
llvm.11.0.0 on 4.02 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.03 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.04 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.05 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.06 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.07 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.08 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.09 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.10 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.11 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.12 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.13 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.14 is not available anymore. Previous state was: passing
llvm.11.0.0 on 4.14+alpha-repo is not available anymore. Previous state was: passing
lru.0.3.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
lru.0.3.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
lustre-v6.1.737 on 4.14 had its build status changed: passing to not available
lustre-v6.1.737 on 4.14+alpha-repo had its build status changed: passing to not available
lutils.1.44 on 4.14 had its build status changed: passing to not available
lutils.1.44 on 4.14+alpha-repo had its build status changed: passing to not available
lutils.1.44 on 5.0+alpha-repo had its build status changed: failing to not available
lutils.1.49.5 on 4.14 had its build status changed: passing to not available
lutils.1.49.5 on 4.14+alpha-repo had its build status changed: passing to not available
lutils.1.49.5 on 5.0 had its build status changed: failing to not available
lutils.1.49.5 on 5.0+alpha-repo had its build status changed: failing to not available
lutils.1.51.2 on 4.14 had its build status changed: passing to not available
lutils.1.51.2 on 4.14+alpha-repo had its build status changed: passing to not available
lutils.1.51.2 on 5.0 had its build status changed: failing to not available
lutils.1.51.2 on 5.0+alpha-repo had its build status changed: failing to not available
lwt-canceler.0.1 on 5.0+alpha-repo had its build status changed: passing to not available
lwt-pipe.0.1 on 5.0+alpha-repo had its build status changed: passing to not available
lwt-pipeline.0.2 on 5.0+alpha-repo had its build status changed: passing to not available
lwt-watcher.0.1 on 5.0+alpha-repo had its build status changed: passing to not available
lwt_log.1.1.1.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
lwt_log.1.1.1.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
lwt_log.1.1.1.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
lz4_chans.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
lz4_chans.2.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
lz4_chans.3.0.0 on 5.0+alpha-repo had its build status changed: passing to not available
mariadb.1.1.4.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
mariadb.1.1.4.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
markup.1.0.2.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
mastodon-archive-viewer.0.2 on 5.0 had its build status changed: partially failing to not available
mastodon-archive-viewer.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
mastodon-archive-viewer.0.3 on 5.0 had its build status changed: partially failing to not available
mastodon-archive-viewer.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
mechaml.1.2.0 on 5.0 had its build status changed: partially failing to not available
mechaml.1.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
mechaml.1.2.1 on 5.0 had its build status changed: partially failing to not available
memtrace.0.2.2.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
memtrace.0.2.2.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
merlin.4.6.1~5.0preview on 5.0 is not available anymore. Previous state was: passing
merlin.4.6.1~5.0preview on 5.0+alpha-repo is not available anymore. Previous state was: passing
metapp.0.4.2.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
metapp.0.4.2.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
metaquot.0.5.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
minima-theme.1.0.0 on 5.0 had its build status changed: partially failing to not available
mirage-unix.3.0.3 on 5.0 had its build status changed: failing to not available
mirage-unix.3.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
mirage-unix.3.0.4 on 5.0 had its build status changed: failing to not available
mirage-unix.3.0.4 on 5.0+alpha-repo had its build status changed: failing to not available
mlgmpidl.1.2.11 on 5.0 had its build status changed: partially failing to not available
mlgmpidl.1.2.11 on 5.0+alpha-repo had its build status changed: failing to not available
mlgmpidl.1.2.12 on 5.0 had its build status changed: partially failing to not available
mlgmpidl.1.2.12 on 5.0+alpha-repo had its build status changed: failing to not available
mlgmpidl.1.2.13 on 5.0 had its build status changed: partially failing to not available
mlgmpidl.1.2.13 on 5.0+alpha-repo had its build status changed: failing to not available
mlgmpidl.1.2.14 on 5.0 had its build status changed: partially failing to not available
mlgmpidl.1.2.14 on 5.0+alpha-repo had its build status changed: failing to not available
monomorphic.1.2 on 5.0 had its build status changed: failing to not available
monomorphic.1.2 on 5.0+alpha-repo had its build status changed: failing to not available
monomorphic.1.3 on 5.0 had its build status changed: partially failing to not available
monomorphic.1.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
monomorphic.1.4 on 5.0 had its build status changed: partially failing to not available
monomorphic.1.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
monomorphic.2.0 on 5.0 had its build status changed: failing to not available
monomorphic.2.0 on 5.0+alpha-repo had its build status changed: failing to not available
mpris-clients.0.2.0 on 5.0 had its build status changed: partially failing to not available
mpris.0.2.0 on 5.0 had its build status changed: partially failing to not available
msgpck-repr.1.5 on 5.0+alpha-repo had its build status changed: passing to not available
msgpck-repr.1.6 on 5.0+alpha-repo had its build status changed: passing to not available
msgpck-repr.1.7 on 5.0+alpha-repo had its build status changed: passing to not available
obus.1.2.3 on 5.0 had its build status changed: failing to not available
obus.1.2.3 on 5.0+alpha-repo had its build status changed: failing to not available
ocaml-freestanding.0.7.1 on 4.02 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.03 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.04 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.05 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.06 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.07 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.08 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.09 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.10 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.11 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.12 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.13 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 4.14 had its build status changed: internal failure to not available
ocaml-freestanding.0.7.1 on 5.0 had its build status changed: internal failure to not available
ocamlbuild-pkg.0.1 on 5.0 had its build status changed: failing to not available
ocamlbuild-pkg.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
ocamlbuild-pkg.0.2 on 5.0 had its build status changed: failing to not available
ocamlbuild-pkg.0.2 on 5.0+alpha-repo had its build status changed: failing to not available
ocamlbuild-pkg.0.2.1 on 5.0 had its build status changed: failing to not available
ocamlbuild-pkg.0.2.1 on 5.0+alpha-repo had its build status changed: failing to not available
ocamlformat.0.21.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
ocamlformat.0.21.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
ocplib-json-typed-browser.0.7 on 5.0+alpha-repo had its build status changed: passing to not available
ocplib-json-typed-browser.0.7.1 on 5.0+alpha-repo had its build status changed: passing to not available
ocplib-json-typed-bson.0.7 on 5.0+alpha-repo had its build status changed: passing to not available
ocplib-json-typed-bson.0.7.1 on 5.0+alpha-repo had its build status changed: passing to not available
ocplib-json-typed.0.7 on 5.0+alpha-repo had its build status changed: passing to not available
ocplib-json-typed.0.7.1 on 5.0+alpha-repo had its build status changed: passing to not available
ocplib_stuff.0.2.0 on 5.0+alpha-repo had its build status changed: passing to not available
opam-bin.0.9.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-bin.0.9.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-bin.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-bin.1.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-core.2.0.2 on 5.0 had its build status changed: failing to not available
opam-core.2.0.2 on 5.0+alpha-repo had its build status changed: failing to not available
opam-core.2.0.3 on 5.0 had its build status changed: failing to not available
opam-core.2.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
opam-core.2.0.4 on 5.0 had its build status changed: failing to not available
opam-core.2.0.4 on 5.0+alpha-repo had its build status changed: failing to not available
opam-core.2.0.5 on 5.0 had its build status changed: failing to not available
opam-core.2.0.5 on 5.0+alpha-repo had its build status changed: failing to not available
opam-core.2.0.6 on 5.0 had its build status changed: failing to not available
opam-core.2.0.6 on 5.0+alpha-repo had its build status changed: failing to not available
opam-dune-lint.0.2 on 5.0+alpha-repo had its build status changed: passing to not available
opam-format.2.0.2 on 5.0 had its build status changed: partially failing to not available
opam-format.2.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-format.2.0.3 on 5.0 had its build status changed: partially failing to not available
opam-format.2.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-format.2.0.4 on 5.0 had its build status changed: partially failing to not available
opam-format.2.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-format.2.0.5 on 5.0 had its build status changed: partially failing to not available
opam-format.2.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-format.2.0.6 on 5.0 had its build status changed: partially failing to not available
opam-format.2.0.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-installer.2.0.2 on 5.0 had its build status changed: partially failing to not available
opam-installer.2.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-installer.2.0.3 on 5.0 had its build status changed: partially failing to not available
opam-installer.2.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-installer.2.0.4 on 5.0 had its build status changed: partially failing to not available
opam-installer.2.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-installer.2.0.5 on 5.0 had its build status changed: partially failing to not available
opam-installer.2.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-installer.2.0.6 on 5.0 had its build status changed: partially failing to not available
opam-installer.2.0.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-repository.2.0.2 on 5.0 had its build status changed: partially failing to not available
opam-repository.2.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-repository.2.0.3 on 5.0 had its build status changed: partially failing to not available
opam-repository.2.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-repository.2.0.4 on 5.0 had its build status changed: partially failing to not available
opam-repository.2.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-repository.2.0.5 on 5.0 had its build status changed: partially failing to not available
opam-repository.2.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-repository.2.0.6 on 5.0 had its build status changed: partially failing to not available
opam-repository.2.0.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-state.2.0.2 on 5.0 had its build status changed: partially failing to not available
opam-state.2.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-state.2.0.3 on 5.0 had its build status changed: partially failing to not available
opam-state.2.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-state.2.0.4 on 5.0 had its build status changed: partially failing to not available
opam-state.2.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-state.2.0.5 on 5.0 had its build status changed: partially failing to not available
opam-state.2.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam-state.2.0.6 on 5.0 had its build status changed: partially failing to not available
opam-state.2.0.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam_bin_lib.0.9.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam_bin_lib.0.9.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam_bin_lib.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
opam_bin_lib.1.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
opium.0.12.0 on 4.12 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
ordma.0.0.5.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
ott.0.26 on 5.0 had its build status changed: failing to not available
ott.0.26 on 5.0+alpha-repo had its build status changed: failing to not available
ott.0.27 on 5.0 had its build status changed: failing to not available
ott.0.27 on 5.0+alpha-repo had its build status changed: failing to not available
ott.0.28 on 5.0 had its build status changed: failing to not available
ott.0.28 on 5.0+alpha-repo had its build status changed: failing to not available
ott.0.29 on 5.0 had its build status changed: failing to not available
ott.0.29 on 5.0+alpha-repo had its build status changed: failing to not available
ott.0.30 on 5.0 had its build status changed: failing to not available
ott.0.30 on 5.0+alpha-repo had its build status changed: failing to not available
ott.0.31 on 5.0 had its build status changed: failing to not available
ott.0.31 on 5.0+alpha-repo had its build status changed: failing to not available
ott.0.32 on 5.0 had its build status changed: failing to not available
ott.0.32 on 5.0+alpha-repo had its build status changed: failing to not available
paf-cohttp.0.0.7 on 5.0 had its build status changed: partially failing to not available
paf-le.0.0.7 on 5.0 had its build status changed: partially failing to not available
paf.0.0.7 on 5.0 had its build status changed: partially failing to not available
paf.0.0.9.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
paf.0.0.9.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
papi.0.1.1.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
pgsolver.4.1 on 4.03 had its build status changed: passing to not available
pgsolver.4.1 on 4.04 had its build status changed: passing to not available
pgsolver.4.1 on 5.0 had its build status changed: partially failing to not available
pgsolver.4.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx.1.0 on 5.0 had its build status changed: failing to not available
pgx.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
pgx.2.0 on 5.0 had its build status changed: failing to not available
pgx.2.0 on 5.0+alpha-repo had its build status changed: failing to not available
pgx.2.1 on 5.0 had its build status changed: failing to not available
pgx.2.1 on 5.0+alpha-repo had its build status changed: failing to not available
pgx_async.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_async.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_async.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt.1.0 on 5.0 had its build status changed: partially failing to not available
pgx_lwt.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt.2.0 on 5.0 had its build status changed: partially failing to not available
pgx_lwt.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt.2.1 on 5.0 had its build status changed: partially failing to not available
pgx_lwt.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt_mirage.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt_mirage.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt_mirage.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt_unix.1.0 on 5.0 had its build status changed: partially failing to not available
pgx_lwt_unix.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt_unix.2.0 on 5.0 had its build status changed: partially failing to not available
pgx_lwt_unix.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_lwt_unix.2.1 on 5.0 had its build status changed: partially failing to not available
pgx_lwt_unix.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_unix.1.0 on 5.0 had its build status changed: partially failing to not available
pgx_unix.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_unix.2.0 on 5.0 had its build status changed: partially failing to not available
pgx_unix.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_unix.2.1 on 5.0 had its build status changed: partially failing to not available
pgx_unix.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_value_core.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_value_core.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_value_core.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
pgx_value_ptime.2.1 on 5.0 had its build status changed: partially failing to not available
pgx_value_ptime.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
picasso.0.2.0 on 5.0 had its build status changed: partially failing to not available
picasso.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
picasso.0.3.0 on 5.0 had its build status changed: partially failing to not available
picasso.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
plebeia.1.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
plist.0.1 on 5.0 had its build status changed: partially failing to not available
polka.2.71.10 on 5.0 had its build status changed: partially failing to not available
polka.2.71.10 on 5.0+alpha-repo had its build status changed: partially failing to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
ppx_deriving.5.2.1.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
printbox-text.0.6 on 5.0+alpha-repo had its build status changed: passing to not available
pyml.20161224 on 5.0 had its build status changed: passing to not available
pyml.20161224 on 5.0+alpha-repo had its build status changed: passing to not available
pyml.20170730 on 5.0 had its build status changed: failing to not available
pyml.20170730 on 5.0+alpha-repo had its build status changed: failing to not available
pyml.20170807 on 5.0 had its build status changed: failing to not available
pyml.20170807 on 5.0+alpha-repo had its build status changed: failing to not available
pyml.20200518 on 5.0 had its build status changed: failing to not available
pyml.20200518 on 5.0+alpha-repo had its build status changed: failing to not available
pyml.20210226 on 5.0 had its build status changed: failing to not available
pyml.20210226 on 5.0+alpha-repo had its build status changed: failing to not available
pyml.20210924 on 5.0 had its build status changed: failing to not available
pyml.20210924 on 5.0+alpha-repo had its build status changed: failing to not available
pyml.20211015 on 5.0 had its build status changed: failing to not available
pyml.20211015 on 5.0+alpha-repo had its build status changed: failing to not available
qcow.0.11.0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
qcow.0.11.0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
range.0.3 on 5.0+alpha-repo had its build status changed: passing to not available
range.0.4 on 5.0+alpha-repo had its build status changed: passing to not available
range.0.6 on 5.0+alpha-repo had its build status changed: passing to not available
range.0.7 on 5.0+alpha-repo had its build status changed: passing to not available
re.1.10.3.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
re.1.10.3.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
reactiveData.0.2.2.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
resto-json.0.2 on 5.0+alpha-repo had its build status changed: passing to not available
sail.0.13 on 5.0 had its build status changed: partially failing to not available
sail.0.13 on 5.0+alpha-repo had its build status changed: partially failing to not available
sail.0.14 on 5.0 had its build status changed: partially failing to not available
sail.0.14 on 5.0+alpha-repo had its build status changed: partially failing to not available
secp256k1.0.4.1 on 5.0 had its build status changed: passing to not available
secp256k1.0.4.1 on 5.0+alpha-repo had its build status changed: passing to not available
secp256k1.0.4.4 on 5.0 had its build status changed: passing to not available
secp256k1.0.4.4 on 5.0+alpha-repo had its build status changed: passing to not available
sha.1.10 on 5.0 had its build status changed: failing to not available
sha.1.10 on 5.0+alpha-repo had its build status changed: failing to not available
sha.1.11 on 5.0 had its build status changed: failing to not available
sha.1.11 on 5.0+alpha-repo had its build status changed: failing to not available
sha.1.15.1 on 5.0 had its build status changed: failing to not available
sha.1.15.1 on 5.0+alpha-repo had its build status changed: failing to not available
spelll.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
stdint.0.7.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
stdint.0.7.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
stdint.0.7.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
sundialsml.6.1.1p0.1~alpha-repo on 4.02 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.03 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.04 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.05 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.06 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.07 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.08 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.09 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.10 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.11 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.12 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.13 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 4.14 had its build status changed: internal failure to not available
sundialsml.6.1.1p0.1~alpha-repo on 5.0 had its build status changed: internal failure to not available
swagger.0.2.0 on 5.0 had its build status changed: partially failing to not available
syslog.2.0.0 on 5.0+alpha-repo had its build status changed: passing to not available
tar-mirage.2.0.0 on 5.0 had its build status changed: partially failing to not available
tar-mirage.2.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tar-unix.1.0.1 on 5.0 had its build status changed: partially failing to not available
tar-unix.1.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
tar-unix.1.1.0 on 5.0 had its build status changed: partially failing to not available
tar-unix.1.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tar-unix.2.0.0 on 5.0 had its build status changed: partially failing to not available
tar-unix.2.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tar.1.0.0 on 5.0 had its build status changed: failing to not available
tar.1.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
tar.1.0.1 on 5.0 had its build status changed: failing to not available
tar.1.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
tar.1.1.0 on 5.0 had its build status changed: failing to not available
tar.1.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
tar.2.0.0 on 5.0 had its build status changed: failing to not available
tar.2.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
tls.0.6.0 on 5.0+alpha-repo had its build status changed: internal failure to not available
topkg-care.1.0.4 on 5.0 had its build status changed: passing to not available
topkg-care.1.0.4 on 5.0+alpha-repo had its build status changed: passing to not available
topkg-care.1.0.5 on 5.0 had its build status changed: passing to not available
topkg-care.1.0.5 on 5.0+alpha-repo had its build status changed: passing to not available
topkg.1.0.3 on 5.0 had its build status changed: passing to not available
topkg.1.0.3 on 5.0+alpha-repo had its build status changed: passing to not available
topkg.1.0.4 on 5.0 had its build status changed: passing to not available
topkg.1.0.4 on 5.0+alpha-repo had its build status changed: passing to not available
topkg.1.0.5 on 5.0 had its build status changed: passing to not available
topkg.1.0.5 on 5.0+alpha-repo had its build status changed: passing to not available
uecc.0.2 on 5.0+alpha-repo had its build status changed: passing to not available
vchan-unix.4.0.2 on 5.0 had its build status changed: partially failing to not available
vchan-unix.4.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
vchan-unix.4.0.3 on 5.0 had its build status changed: partially failing to not available
vchan-unix.4.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
vchan-unix.5.0.0 on 5.0 had its build status changed: partially failing to not available
vchan-unix.5.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
vchan-unix.6.0.0 on 5.0 had its build status changed: partially failing to not available
vchan-unix.6.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
vchan-unix.6.0.1 on 5.0 had its build status changed: partially failing to not available
vchan-unix.6.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
xen-gnt-unix.3.1.0 on 5.0 had its build status changed: failing to not available
xen-gnt-unix.3.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
xen-gnt-unix.4.0.0 on 5.0 had its build status changed: failing to not available
xen-gnt-unix.4.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
xen-gnt-unix.4.0.1 on 5.0 had its build status changed: failing to not available
xen-gnt-unix.4.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
z3_tptp.4.8.14 on 4.06 had its build status changed: internal failure to not available

Packages now failing with an internal failure:

bap-elf.1.0.0 on 4.02 had its build status changed: passing to internal failure
bap-elf.1.0.0 on 4.03 had its build status changed: passing to internal failure
bap-elf.1.0.0 on 4.04 had its build status changed: partially failing to internal failure
bap-elf.1.1.0 on 4.02 had its build status changed: passing to internal failure
bap-elf.1.1.0 on 4.03 had its build status changed: passing to internal failure
bap-elf.1.1.0 on 4.04 had its build status changed: partially failing to internal failure
bap-elf.1.2.0 on 4.02 had its build status changed: passing to internal failure
bap-elf.1.2.0 on 4.03 had its build status changed: passing to internal failure
bap-elf.1.2.0 on 4.04 had its build status changed: passing to internal failure
bap-elf.1.3.0 on 4.02 had its build status changed: passing to internal failure
bap-elf.1.3.0 on 4.03 had its build status changed: passing to internal failure
bap-elf.1.3.0 on 4.04 had its build status changed: passing to internal failure
beluga.0.8.1 on 4.04 had its build status changed: passing to internal failure
beluga.0.8.1 on 4.06 had its build status changed: passing to internal failure
beluga.0.8.1 on 4.07 had its build status changed: passing to internal failure
beluga.0.8.1 on 4.09 had its build status changed: passing to internal failure
beluga.0.8.1 on 4.10 had its build status changed: passing to internal failure
beluga.0.8.1 on 4.12 had its build status changed: passing to internal failure
beluga.0.8.1 on 4.13 had its build status changed: passing to internal failure
beluga.0.8.1 on 4.14 had its build status changed: passing to internal failure
beluga.0.8.2 on 4.03 had its build status changed: passing to internal failure
beluga.0.8.2 on 4.06 had its build status changed: passing to internal failure
beluga.0.8.2 on 4.07 had its build status changed: passing to internal failure
beluga.0.8.2 on 4.08 had its build status changed: passing to internal failure
beluga.0.8.2 on 4.12 had its build status changed: passing to internal failure
beluga.0.8.2 on 4.13 had its build status changed: passing to internal failure
beluga.0.8.2 on 4.14 had its build status changed: passing to internal failure
bitcoinml.0.2 on 4.03 had its build status changed: passing to internal failure
bitcoinml.0.2 on 4.04 had its build status changed: passing to internal failure
bitcoinml.0.2 on 4.05 had its build status changed: passing to internal failure
bitcoinml.0.2.4 on 4.03 had its build status changed: passing to internal failure
bitcoinml.0.2.4 on 4.04 had its build status changed: passing to internal failure
bitcoinml.0.2.4 on 4.05 had its build status changed: passing to internal failure
bitcoinml.0.3.0 on 4.03 had its build status changed: passing to internal failure
bitcoinml.0.3.0 on 4.04 had its build status changed: passing to internal failure
bitcoinml.0.3.0 on 4.05 had its build status changed: passing to internal failure
bitcoinml.0.3.1 on 4.03 had its build status changed: passing to internal failure
bitcoinml.0.3.1 on 4.04 had its build status changed: passing to internal failure
bitcoinml.0.3.1 on 4.05 had its build status changed: passing to internal failure
bitstring.2.1.0 on 4.02 had its build status changed: passing to internal failure
bitstring.2.1.0 on 4.03 had its build status changed: passing to internal failure
bitstring.2.1.0 on 4.04 had its build status changed: passing to internal failure
bitstring.2.1.0 on 4.05 had its build status changed: passing to internal failure
bitstring.2.1.1 on 4.02 had its build status changed: passing to internal failure
bitstring.2.1.1 on 4.03 had its build status changed: passing to internal failure
bitstring.2.1.1 on 4.04 had its build status changed: passing to internal failure
bitstring.2.1.1 on 4.05 had its build status changed: passing to internal failure
bitstring.3.0.0 on 4.05 had its build status changed: passing to internal failure
bitstring.3.0.0 on 4.11 had its build status changed: passing to internal failure
bitstring.3.1.0 on 4.02 had its build status changed: passing to internal failure
bitstring.3.1.0 on 4.03 had its build status changed: passing to internal failure
bitstring.3.1.0 on 4.10 had its build status changed: passing to internal failure
bitstring.3.1.1 on 4.10 had its build status changed: passing to internal failure
cohttp-async.2.5.0 on 4.11 had its build status changed: passing to internal failure
cohttp-async.2.5.2-1 on 4.10 had its build status changed: passing to internal failure
cohttp-async.2.5.4 on 4.11 had its build status changed: passing to internal failure
cohttp-curl-async.6.0.0~alpha0 on 5.0 is now installable. Current state is: internal failure
cohttp-lwt-jsoo.2.5.1 on 4.05 had its build status changed: passing to internal failure
cohttp-lwt-jsoo.2.5.2-1 on 4.05 had its build status changed: passing to internal failure
cohttp-lwt-jsoo.2.5.4 on 4.05 had its build status changed: passing to internal failure
cohttp-lwt-jsoo.2.5.5 on 4.08 had its build status changed: passing to internal failure
cohttp-lwt-jsoo.2.5.6 on 4.07 had its build status changed: passing to internal failure
cohttp-lwt-jsoo.5.0.0 on 4.10 had its build status changed: passing to internal failure
cohttp-lwt-unix.2.3.0 on 4.12 had its build status changed: passing to internal failure
cohttp-lwt-unix.2.5.6 on 4.06 had its build status changed: passing to internal failure
cohttp-lwt-unix.6.0.0~alpha0 on 4.07 is now installable. Current state is: internal failure
cohttp-lwt.0.99.0 on 4.07 had its build status changed: not available to internal failure
cohttp-lwt.1.0.2 on 4.08 had its build status changed: passing to internal failure
cohttp-lwt.1.2.0 on 5.0+alpha-repo had its build status changed: not available to internal failure
cohttp-lwt.2.3.0 on 4.11 had its build status changed: passing to internal failure
cohttp-top.2.1.3 on 4.04 had its build status changed: passing to internal failure
cohttp-top.4.0.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
cohttp.0.17.1 on 4.02 had its build status changed: passing to internal failure
cohttp.0.18.0 on 4.14+alpha-repo had its build status changed: not available to internal failure
cohttp.0.19.0 on 4.02 had its build status changed: passing to internal failure
cohttp.0.19.0 on 5.0+alpha-repo had its build status changed: not available to internal failure
cohttp.0.20.0 on 4.06 had its build status changed: not available to internal failure
cohttp.0.20.2 on 4.05 had its build status changed: passing to internal failure
combine.0.6 on 4.13 had its build status changed: passing to internal failure
ezjs_fetch.0.1 on 5.0 had its build status changed: not available to internal failure
ffmpeg-av.1.0.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
ffmpeg-av.1.0.0~rc1 on 4.11 had its build status changed: passing to internal failure
ffmpeg-avcodec.1.0.0 on 4.11 had its build status changed: passing to internal failure
ffmpeg-avcodec.1.0.0~rc1 on 4.13 had its build status changed: passing to internal failure
ffmpeg-avdevice.1.0.0 on 4.10 had its build status changed: passing to internal failure
ffmpeg-avdevice.1.0.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
ffmpeg-avdevice.1.0.0~rc1 on 4.14 had its build status changed: passing to internal failure
ffmpeg-avdevice.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: passing to internal failure
ffmpeg-avfilter.1.0.0~rc1 on 4.14+alpha-repo had its build status changed: passing to internal failure
ffmpeg-avutil.1.0.0 on 4.12 had its build status changed: passing to internal failure
ffmpeg-avutil.1.0.0~rc1 on 5.0 had its build status changed: passing to internal failure
ffmpeg-swscale.1.0.0 on 5.0 had its build status changed: passing to internal failure
hdfs.0.1 on 5.0 had its build status changed: partially failing to internal failure
hdfs.0.3 on 5.0 had its build status changed: partially failing to internal failure
hdfs.0.4 on 5.0 had its build status changed: partially failing to internal failure
incr_dom_keyboard.v0.13.0 on 4.09 had its build status changed: passing to internal failure
mparser.1.1 on 4.03 had its build status changed: passing to internal failure
mparser.1.2.1 on 4.05 had its build status changed: passing to internal failure
mysql_protocol.0.8 on 4.02 had its build status changed: passing to internal failure
mysql_protocol.0.8 on 4.03 had its build status changed: passing to internal failure
mysql_protocol.0.8 on 4.04 had its build status changed: passing to internal failure
mysql_protocol.0.8 on 4.05 had its build status changed: passing to internal failure
mysql_protocol.0.9 on 4.02 had its build status changed: passing to internal failure
mysql_protocol.0.9 on 4.03 had its build status changed: passing to internal failure
mysql_protocol.0.9 on 4.04 had its build status changed: passing to internal failure
mysql_protocol.0.9 on 4.05 had its build status changed: passing to internal failure
mysql_protocol.1.0 on 4.02 had its build status changed: passing to internal failure
mysql_protocol.1.0 on 4.03 had its build status changed: passing to internal failure
mysql_protocol.1.0 on 4.04 had its build status changed: passing to internal failure
mysql_protocol.1.0 on 4.05 had its build status changed: passing to internal failure
mysql_protocol.1.1 on 4.02 had its build status changed: passing to internal failure
mysql_protocol.1.1 on 4.03 had its build status changed: passing to internal failure
mysql_protocol.1.1 on 4.04 had its build status changed: passing to internal failure
mysql_protocol.1.1 on 4.05 had its build status changed: passing to internal failure
mysql_protocol.2.0 on 4.02 had its build status changed: passing to internal failure
mysql_protocol.2.0 on 4.03 had its build status changed: passing to internal failure
mysql_protocol.2.0 on 4.04 had its build status changed: passing to internal failure
mysql_protocol.2.0 on 4.05 had its build status changed: passing to internal failure
netml.0.1.0 on 4.03 had its build status changed: failing to internal failure
netml.0.1.0 on 4.04 had its build status changed: failing to internal failure
netml.0.1.0 on 4.05 had its build status changed: failing to internal failure
obeam.0.0.3 on 4.11 had its build status changed: passing to internal failure
obeam.0.0.4 on 4.05 had its build status changed: passing to internal failure
obeam.0.1.0 on 4.10 had its build status changed: passing to internal failure
obeam.0.1.1 on 4.06 had its build status changed: passing to internal failure
obeam.0.1.1 on 4.12 had its build status changed: passing to internal failure
obeam.0.1.2 on 4.07 had its build status changed: passing to internal failure
obeam.0.1.3 on 4.11 had its build status changed: passing to internal failure
obeam.0.1.5 on 4.09 had its build status changed: passing to internal failure
ocaml-r.0.4.0 on 4.11 had its build status changed: failing to internal failure
ocamlog.0.1 on 4.11 had its build status changed: passing to internal failure
ocamlog.0.1 on 5.0 had its build status changed: passing to internal failure
ocamlog.0.2 on 4.10 had its build status changed: passing to internal failure
ocamlog.0.2 on 4.14 had its build status changed: passing to internal failure
ocamlyices.0.7.0 on 5.0 had its build status changed: partially failing to internal failure
ocamlyices.0.7.1 on 5.0 had its build status changed: partially failing to internal failure
opass.1.0.2 on 4.02 had its build status changed: failing to internal failure
oraft.0.2.0 on 4.05 had its build status changed: not available to internal failure
orakuda.1.0.1 on 4.05 had its build status changed: passing to internal failure
orakuda.1.1.0 on 4.04 had its build status changed: passing to internal failure
oranger.3.0.1 on 4.08 had its build status changed: passing to internal failure
oranger.4.2.0 on 4.10 had its build status changed: passing to internal failure
oranger.4.3.3 on 4.12 had its build status changed: passing to internal failure
oranger.4.3.4 on 4.14+alpha-repo had its build status changed: passing to internal failure
order-i3-xfce.0.1 on 4.14+alpha-repo had its build status changed: passing to internal failure
ordering.3.0.2 on 4.14+alpha-repo had its build status changed: passing to internal failure
ordering.3.0.3 on 4.11 had its build status changed: passing to internal failure
ordering.3.1.0 on 4.14 had its build status changed: passing to internal failure
ordering.3.6.0 on 4.03 is now installable. Current state is: internal failure
osdp.0.6.0 on 4.02 had its build status changed: passing to internal failure
osdp.0.6.0 on 4.04 had its build status changed: passing to internal failure
osdp.0.6.0 on 5.0+alpha-repo had its build status changed: failing to internal failure
osdp.1.0.0 on 4.02 had its build status changed: passing to internal failure
osdp.1.0.0 on 4.07 had its build status changed: passing to internal failure
pixel_pusher.1.0 on 4.11 had its build status changed: passing to internal failure
pixel_pusher.1.1 on 4.09 had its build status changed: passing to internal failure
pla.1.4 on 4.11 had its build status changed: passing to internal failure
ppx_bitstring.1.0.0 on 4.02 had its build status changed: failing to internal failure
ppx_bitstring.1.0.1 on 4.03 had its build status changed: failing to internal failure
ppx_bitstring.1.1.0 on 4.03 had its build status changed: failing to internal failure
ppx_bitstring.1.1.0 on 4.04 had its build status changed: passing to internal failure
ppx_bitstring.1.1.0 on 4.05 had its build status changed: passing to internal failure
ppx_bitstring.1.2.0 on 4.03 had its build status changed: failing to internal failure
ppx_bitstring.1.3.0 on 4.03 had its build status changed: passing to internal failure
ppx_bitstring.1.3.1 on 4.03 had its build status changed: passing to internal failure
ppx_bitstring.1.3.2 on 4.03 had its build status changed: passing to internal failure
ppx_bitstring.1.3.3 on 4.03 had its build status changed: passing to internal failure
ppx_bitstring.1.3.3 on 4.04 had its build status changed: passing to internal failure
ppx_bitstring.2.0.0 on 4.03 had its build status changed: failing to internal failure
ppx_bitstring.2.0.0 on 4.04 had its build status changed: failing to internal failure
ppx_bitstring.2.0.0 on 4.05 had its build status changed: failing to internal failure
ppx_bitstring.2.0.1 on 4.03 had its build status changed: failing to internal failure
ppx_bitstring.2.0.1 on 4.04 had its build status changed: failing to internal failure
ppx_bitstring.2.0.1 on 4.05 had its build status changed: failing to internal failure
ppx_bitstring.2.0.2 on 4.03 had its build status changed: passing to internal failure
ppx_bitstring.2.0.2 on 4.04 had its build status changed: passing to internal failure
ppx_bitstring.2.0.2 on 4.05 had its build status changed: passing to internal failure
prob-cache.1.0.0 on 4.04 had its build status changed: partially failing to internal failure
proverif.1.98 on 5.0 had its build status changed: not available to internal failure
proverif.1.98 on 5.0+alpha-repo had its build status changed: not available to internal failure
proverif.1.98pl1 on 5.0 had its build status changed: not available to internal failure
proverif.1.98pl1 on 5.0+alpha-repo had its build status changed: not available to internal failure
riakc_ppx.3.1.1 on 4.03 had its build status changed: failing to internal failure
riakc_ppx.3.1.3 on 4.02 had its build status changed: failing to internal failure
solo5.0.7.0 on 4.04 had its build status changed: failing to internal failure
solo5.0.7.1 on 4.06 had its build status changed: failing to internal failure
toml.2.1.0 on 4.03 had its build status changed: passing to internal failure
ws.0.1 on 4.07 had its build status changed: passing to internal failure
ws.0.1 on 4.09 had its build status changed: passing to internal failure
z3.4.11.0 on 4.14 had its build status changed: passing to internal failure
z3.4.11.0 on 5.0+alpha-repo had its build status changed: passing to internal failure
z3.4.11.2 on 4.11 had its build status changed: passing to internal failure
z3.4.8.1 on 4.13 had its build status changed: passing to internal failure
z3.4.8.11 on 4.08 had its build status changed: passing to internal failure
z3.4.8.11 on 4.09 had its build status changed: passing to internal failure
z3.4.8.13 on 4.03 had its build status changed: passing to internal failure
z3.4.8.13 on 4.09 had its build status changed: passing to internal failure
z3.4.8.13 on 4.12 had its build status changed: passing to internal failure
z3.4.8.14 on 4.10 had its build status changed: passing to internal failure
z3.4.8.17 on 4.12 had its build status changed: passing to internal failure
z3.4.8.4 on 4.06 had its build status changed: passing to internal failure
z3.4.8.4 on 4.07 had its build status changed: passing to internal failure
z3.4.8.5 on 4.08 had its build status changed: passing to internal failure
z3.4.8.5 on 4.11 had its build status changed: passing to internal failure
z3.4.8.6 on 4.03 had its build status changed: passing to internal failure
z3.4.8.6 on 4.08 had its build status changed: passing to internal failure
z3.4.8.6 on 4.14+alpha-repo had its build status changed: passing to internal failure
z3.4.8.7 on 4.05 had its build status changed: passing to internal failure
z3.4.8.7 on 4.14 had its build status changed: passing to internal failure
z3.4.8.8 on 4.07 had its build status changed: passing to internal failure
z3.4.8.9-1 on 4.07 had its build status changed: passing to internal failure
z3.4.8.9-1 on 4.10 had its build status changed: passing to internal failure
z3_tptp.4.10.1 on 4.10 had its build status changed: passing to internal failure
z3_tptp.4.10.1 on 4.13 had its build status changed: passing to internal failure
z3_tptp.4.10.1 on 5.0+alpha-repo had its build status changed: passing to internal failure
z3_tptp.4.11.0 on 5.0 had its build status changed: passing to internal failure
z3_tptp.4.8.13 on 4.14 had its build status changed: passing to internal failure
zlist.0.1.2 on 4.03 had its build status changed: passing to internal failure
zlist.0.4.0 on 4.04 had its build status changed: passing to internal failure
zlist.0.4.0 on 4.05 had its build status changed: passing to internal failure
zlist.0.4.0 on 4.11 had its build status changed: passing to internal failure
zmq-async.5.1.3 on 4.07 had its build status changed: passing to internal failure
zstandard.v0.12.0 on 4.08 had its build status changed: passing to internal failure

Packages now passing:

ISO3166.0.1.0 on 4.03 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.04 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.05 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.06 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.07 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.08 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.09 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.10 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.11 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.12 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.13 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.14 is now installable. Current state is: passing
ISO3166.0.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
ISO3166.0.1.0 on 5.0 is now installable. Current state is: passing
ISO3166.0.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
OCADml.0.1.0 on 4.13 is now installable. Current state is: passing
OCADml.0.1.0 on 4.14 is now installable. Current state is: passing
OCADml.0.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
OCADml.0.1.0 on 5.0 is now installable. Current state is: passing
OCADml.0.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
OCADml.0.1.1 on 4.13 is now installable. Current state is: passing
OCADml.0.1.1 on 4.14 is now installable. Current state is: passing
OCADml.0.1.1 on 4.14+alpha-repo is now installable. Current state is: passing
OCADml.0.1.1 on 5.0 is now installable. Current state is: passing
OCADml.0.1.1 on 5.0+alpha-repo is now installable. Current state is: passing
OCADml.0.1.2 on 4.13 is now installable. Current state is: passing
OCADml.0.1.2 on 4.14 is now installable. Current state is: passing
OCADml.0.1.2 on 4.14+alpha-repo is now installable. Current state is: passing
OCADml.0.1.2 on 5.0 is now installable. Current state is: passing
OCADml.0.1.2 on 5.0+alpha-repo is now installable. Current state is: passing
OSCADml.0.1.0 on 4.13 is now installable. Current state is: passing
OSCADml.0.1.0 on 4.14 is now installable. Current state is: passing
OSCADml.0.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
OSCADml.0.1.0 on 5.0 is now installable. Current state is: passing
OSCADml.0.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
OSCADml.0.1.1 on 4.14 is now installable. Current state is: passing
OSCADml.0.1.1 on 4.14+alpha-repo is now installable. Current state is: passing
OSCADml.0.1.1 on 5.0 is now installable. Current state is: passing
OSCADml.0.1.1 on 5.0+alpha-repo is now installable. Current state is: passing
SZXX.0.1.0 on 5.0 had its build status changed: not available to passing
SZXX.1.0.0 on 5.0 had its build status changed: not available to passing
SZXX.1.1.0 on 5.0 had its build status changed: not available to passing
SZXX.2.0.0 on 5.0 had its build status changed: not available to passing
SZXX.2.1.0 on 5.0 had its build status changed: not available to passing
SZXX.2.1.1 on 5.0 had its build status changed: not available to passing
SZXX.2.1.2 on 5.0 had its build status changed: not available to passing
SZXX.2.2.0 on 5.0 had its build status changed: not available to passing
SZXX.2.3.0 on 5.0 had its build status changed: not available to passing
SZXX.3.0.0 on 4.11 is now installable. Current state is: passing
SZXX.3.0.0 on 4.12 is now installable. Current state is: passing
SZXX.3.0.0 on 4.13 is now installable. Current state is: passing
SZXX.3.0.0 on 4.14 is now installable. Current state is: passing
SZXX.3.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
SZXX.3.0.0 on 5.0 is now installable. Current state is: passing
SZXX.3.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
accessor_async.v0.15.0 on 5.0 had its build status changed: not available to passing
accessor_core.v0.15.0 on 5.0 had its build status changed: not available to passing
alba.0.4.4 on 5.0 had its build status changed: not available to passing
albatross.1.4.3 on 5.0 had its build status changed: not available to passing
albatross.1.5.0 on 5.0 had its build status changed: not available to passing
albatross.1.5.1 on 5.0 had its build status changed: not available to passing
albatross.1.5.2 on 4.12 is now installable. Current state is: passing
albatross.1.5.2 on 4.13 is now installable. Current state is: passing
albatross.1.5.2 on 4.14 is now installable. Current state is: passing
albatross.1.5.2 on 4.14+alpha-repo is now installable. Current state is: passing
albatross.1.5.2 on 5.0 is now installable. Current state is: passing
albatross.1.5.2 on 5.0+alpha-repo is now installable. Current state is: passing
albatross.1.5.3 on 4.12 is now installable. Current state is: passing
albatross.1.5.3 on 4.13 is now installable. Current state is: passing
albatross.1.5.3 on 4.14 is now installable. Current state is: passing
albatross.1.5.3 on 4.14+alpha-repo is now installable. Current state is: passing
albatross.1.5.3 on 5.0 is now installable. Current state is: passing
albatross.1.5.3 on 5.0+alpha-repo is now installable. Current state is: passing
alcotest-async.0.8.5 on 5.0 had its build status changed: not available to passing
alcotest-async.1.6.0 on 5.0 had its build status changed: not available to passing
alcotest-js.1.5.0 on 5.0 had its build status changed: not available to passing
alcotest-js.1.6.0 on 5.0 had its build status changed: not available to passing
altgr-ergo.2.4.2 on 5.0 had its build status changed: not available to passing
altgr-ergo.2.4.2 on 5.0+alpha-repo had its build status changed: not available to passing
angstrom-async.0.11.1 on 5.0 had its build status changed: not available to passing
angstrom-async.0.11.2 on 5.0 had its build status changed: not available to passing
angstrom-async.0.12.1 on 5.0 had its build status changed: not available to passing
angstrom-async.0.13.0 on 5.0 had its build status changed: not available to passing
angstrom-async.0.14.0 on 5.0 had its build status changed: not available to passing
angstrom-async.0.14.1 on 5.0 had its build status changed: not available to passing
angstrom-async.0.15.0 on 5.0 had its build status changed: not available to passing
archetype.1.2.10 on 5.0 had its build status changed: not available to passing
archetype.1.2.11 on 5.0 had its build status changed: not available to passing
archetype.1.2.12 on 5.0 had its build status changed: not available to passing
archetype.1.2.13 on 5.0 had its build status changed: not available to passing
archetype.1.2.14 on 5.0 had its build status changed: not available to passing
archetype.1.2.15 on 5.0 had its build status changed: not available to passing
archetype.1.2.16 on 5.0 had its build status changed: not available to passing
archetype.1.2.7 on 5.0 had its build status changed: not available to passing
archetype.1.2.8 on 5.0 had its build status changed: not available to passing
archetype.1.2.9 on 5.0 had its build status changed: not available to passing
archetype.1.3.0 on 5.0 had its build status changed: not available to passing
archetype.1.3.1 on 5.0 had its build status changed: not available to passing
archetype.1.3.2 on 5.0 had its build status changed: not available to passing
archetype.1.3.3 on 4.08 had its build status changed: internal failure to passing
archetype.1.3.3 on 4.09 had its build status changed: internal failure to passing
archetype.1.3.3 on 4.10 had its build status changed: internal failure to passing
archetype.1.3.3 on 4.11 had its build status changed: internal failure to passing
archetype.1.3.3 on 4.12 had its build status changed: internal failure to passing
archetype.1.3.3 on 4.13 had its build status changed: internal failure to passing
archetype.1.3.3 on 4.14 had its build status changed: internal failure to passing
archetype.1.3.3 on 5.0 had its build status changed: not available to passing
archetype.1.3.3 on 5.0+alpha-repo had its build status changed: internal failure to passing
archetype.1.3.4 on 5.0 had its build status changed: not available to passing
archetype.1.3.5 on 5.0 had its build status changed: not available to passing
archetype.1.3.6 on 4.08 is now installable. Current state is: passing
archetype.1.3.6 on 4.09 is now installable. Current state is: passing
archetype.1.3.6 on 4.10 is now installable. Current state is: passing
archetype.1.3.6 on 4.11 is now installable. Current state is: passing
archetype.1.3.6 on 4.12 is now installable. Current state is: passing
archetype.1.3.6 on 4.13 is now installable. Current state is: passing
archetype.1.3.6 on 4.14 is now installable. Current state is: passing
archetype.1.3.6 on 4.14+alpha-repo is now installable. Current state is: passing
archetype.1.3.6 on 5.0 is now installable. Current state is: passing
archetype.1.3.6 on 5.0+alpha-repo is now installable. Current state is: passing
archi-async.0.1.0 on 5.0 had its build status changed: not available to passing
archi-async.0.2.0 on 5.0 had its build status changed: not available to passing
async.v0.15.0 on 5.0 had its build status changed: not available to passing
async_durable.v0.15.0 on 5.0 had its build status changed: not available to passing
async_extra.v0.15.0 on 5.0 had its build status changed: not available to passing
async_find.v0.15.0 on 5.0 had its build status changed: not available to passing
async_inotify.v0.15.0 on 5.0 had its build status changed: not available to passing
async_interactive.v0.15.0 on 5.0 had its build status changed: not available to passing
async_js.v0.15.1 on 4.11 is now installable. Current state is: passing
async_js.v0.15.1 on 4.12 is now installable. Current state is: passing
async_js.v0.15.1 on 4.13 is now installable. Current state is: passing
async_js.v0.15.1 on 4.14 is now installable. Current state is: passing
async_js.v0.15.1 on 4.14+alpha-repo is now installable. Current state is: passing
async_js.v0.15.1 on 5.0 is now installable. Current state is: passing
async_js.v0.15.1 on 5.0+alpha-repo is now installable. Current state is: passing
async_kernel.v0.15.0 on 5.0 had its build status changed: not available to passing
async_rpc_kernel.v0.15.0 on 5.0 had its build status changed: not available to passing
async_rpc_websocket.v0.15.0 on 5.0 had its build status changed: not available to passing
async_sendfile.v0.15.0 on 5.0 had its build status changed: not available to passing
async_shell.v0.15.0 on 5.0 had its build status changed: not available to passing
async_smtp.v0.15.0 on 5.0 had its build status changed: not available to passing
async_ssl.v0.15.0 on 5.0 had its build status changed: not available to passing
async_udp.v0.15.0 on 5.0 had its build status changed: not available to passing
async_unix.v0.15.0 on 5.0 had its build status changed: not available to passing
async_websocket.v0.15.0 on 5.0 had its build status changed: not available to passing
atable.0.1 on 5.0 had its build status changed: not available to passing
aws-async.1.2 on 5.0 had its build status changed: not available to passing
aws-async.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-autoscaling.1.2 on 5.0 had its build status changed: not available to passing
aws-autoscaling.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-cloudformation.1.2 on 5.0 had its build status changed: not available to passing
aws-cloudformation.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-cloudtrail.1.2 on 5.0 had its build status changed: not available to passing
aws-cloudtrail.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-cloudwatch.1.2 on 5.0 had its build status changed: not available to passing
aws-cloudwatch.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-ec2.1.2 on 5.0 had its build status changed: not available to passing
aws-ec2.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-elasticache.1.2 on 5.0 had its build status changed: not available to passing
aws-elasticache.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-elasticloadbalancing.1.2 on 5.0 had its build status changed: not available to passing
aws-elasticloadbalancing.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-lwt.1.2 on 5.0 had its build status changed: not available to passing
aws-lwt.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-rds.1.2 on 5.0 had its build status changed: not available to passing
aws-rds.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-route53.1.2 on 5.0 had its build status changed: not available to passing
aws-route53.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-sdb.1.2 on 5.0 had its build status changed: not available to passing
aws-sdb.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-sqs.1.2 on 5.0 had its build status changed: not available to passing
aws-sqs.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-ssm.1.2 on 5.0 had its build status changed: not available to passing
aws-ssm.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws-sts.1.2 on 5.0 had its build status changed: not available to passing
aws-sts.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
aws.1.2 on 5.0 had its build status changed: not available to passing
aws.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
azure-cosmos-db.0.2.0 on 4.08 is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 4.09 is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 4.10 is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 4.11 is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 4.12 is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 4.13 is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 4.14 is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 4.14+alpha-repo is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 5.0 is now installable. Current state is: passing
azure-cosmos-db.0.2.0 on 5.0+alpha-repo is now installable. Current state is: passing
baguette_sharp.2.1.1 on 4.13 is now installable. Current state is: passing
baguette_sharp.2.1.1 on 4.14 is now installable. Current state is: passing
baguette_sharp.2.1.1 on 4.14+alpha-repo is now installable. Current state is: passing
baguette_sharp.2.1.1 on 5.0 is now installable. Current state is: passing
baguette_sharp.2.1.1 on 5.0+alpha-repo is now installable. Current state is: passing
bap-api.1.3.0 on 4.02 had its build status changed: partially failing to passing
bastet_async.0.1.0 on 5.0 had its build status changed: not available to passing
bddrand.2.71.10 on 4.05 had its build status changed: not available to passing
bddrand.2.71.15 on 4.05 is now installable. Current state is: passing
bddrand.2.71.15 on 4.06 is now installable. Current state is: passing
bddrand.2.71.15 on 4.07 is now installable. Current state is: passing
bddrand.2.71.15 on 4.08 is now installable. Current state is: passing
bddrand.2.71.15 on 4.09 is now installable. Current state is: passing
bddrand.2.71.15 on 4.10 is now installable. Current state is: passing
bddrand.2.71.15 on 4.11 is now installable. Current state is: passing
bddrand.2.71.15 on 4.12 is now installable. Current state is: passing
bddrand.2.71.15 on 4.13 is now installable. Current state is: passing
bddrand.2.71.15 on 4.14 is now installable. Current state is: passing
bddrand.2.71.15 on 4.14+alpha-repo is now installable. Current state is: passing
bigdecimal.v0.15.0 on 5.0 had its build status changed: not available to passing
bigdecimal.v0.15.0 on 5.0+alpha-repo had its build status changed: internal failure to passing
bignum.v0.15.0 on 5.0 had its build status changed: not available to passing
bimage-gtk.0.1 on 5.0 had its build status changed: not available to passing
bimage-gtk.0.1 on 5.0+alpha-repo had its build status changed: not available to passing
bimage-gtk.0.1.1 on 5.0 had its build status changed: not available to passing
bimage-gtk.0.1.1 on 5.0+alpha-repo had its build status changed: not available to passing
bimage-gtk.0.1.2 on 5.0 had its build status changed: not available to passing
bimage-gtk.0.1.2 on 5.0+alpha-repo had its build status changed: not available to passing
bimage-gtk.0.2.1 on 5.0 had its build status changed: not available to passing
bimage-gtk.0.2.1 on 5.0+alpha-repo had its build status changed: not available to passing
bimage.0.3.1 on 4.08 had its build status changed: internal failure to passing
binaryen.0.10.0 on 5.0 had its build status changed: not available to passing
binaryen.0.11.0 on 5.0 had its build status changed: not available to passing
binaryen.0.11.1 on 5.0 had its build status changed: not available to passing
binaryen.0.11.2 on 5.0 had its build status changed: not available to passing
binaryen.0.12.0 on 5.0 had its build status changed: not available to passing
binaryen.0.17.1 on 5.0 had its build status changed: not available to passing
binaryen.0.18.0 on 5.0 had its build status changed: not available to passing
binaryen.0.19.0 on 4.12 is now installable. Current state is: passing
binaryen.0.19.0 on 4.13 is now installable. Current state is: passing
binaryen.0.19.0 on 4.14 is now installable. Current state is: passing
binaryen.0.19.0 on 4.14+alpha-repo is now installable. Current state is: passing
binaryen.0.19.0 on 5.0 is now installable. Current state is: passing
binaryen.0.19.0 on 5.0+alpha-repo is now installable. Current state is: passing
binaryen.0.4.0 on 5.0 had its build status changed: not available to passing
binaryen.0.5.0 on 5.0 had its build status changed: not available to passing
binaryen.0.6.0 on 5.0 had its build status changed: not available to passing
binaryen.0.7.0 on 5.0 had its build status changed: not available to passing
binaryen.0.8.0 on 5.0 had its build status changed: not available to passing
binaryen.0.8.1 on 5.0 had its build status changed: not available to passing
binaryen.0.9.0 on 5.0 had its build status changed: not available to passing
binaryen.0.9.1 on 5.0 had its build status changed: not available to passing
binsec.0.6.2 on 4.09 is now installable. Current state is: passing
binsec.0.6.2 on 4.10 is now installable. Current state is: passing
binsec.0.6.2 on 4.11 is now installable. Current state is: passing
binsec.0.6.2 on 4.12 is now installable. Current state is: passing
binsec.0.6.2 on 4.13 is now installable. Current state is: passing
binsec.0.6.2 on 4.14 is now installable. Current state is: passing
binsec.0.6.2 on 4.14+alpha-repo is now installable. Current state is: passing
bls12-381-hash.0.0.4 on 4.12 is now installable. Current state is: passing
bls12-381-hash.0.0.4 on 4.13 is now installable. Current state is: passing
bls12-381-hash.0.0.4 on 4.14 is now installable. Current state is: passing
bls12-381-hash.0.0.4 on 4.14+alpha-repo is now installable. Current state is: passing
bls12-381-hash.0.0.4 on 5.0 is now installable. Current state is: passing
bls12-381-hash.0.0.4 on 5.0+alpha-repo is now installable. Current state is: passing
bls12-381-hash.0.0.5 on 4.12 is now installable. Current state is: passing
bls12-381-hash.0.0.5 on 4.13 is now installable. Current state is: passing
bls12-381-hash.0.0.5 on 4.14 is now installable. Current state is: passing
bls12-381-hash.0.0.5 on 4.14+alpha-repo is now installable. Current state is: passing
bls12-381-hash.0.0.5 on 5.0 is now installable. Current state is: passing
bls12-381-hash.0.0.5 on 5.0+alpha-repo is now installable. Current state is: passing
bls12-381-hash.1.0.0 on 4.12 is now installable. Current state is: passing
bls12-381-hash.1.0.0 on 4.13 is now installable. Current state is: passing
bls12-381-hash.1.0.0 on 4.14 is now installable. Current state is: passing
bls12-381-hash.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
bls12-381-hash.1.0.0 on 5.0 is now installable. Current state is: passing
bls12-381-hash.1.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
bls12-381-js-gen.0.4.1 on 5.0 had its build status changed: not available to passing
bls12-381-js-gen.0.4.2 on 5.0 had its build status changed: not available to passing
bls12-381-js-gen.0.4.3 on 5.0 had its build status changed: not available to passing
bls12-381-js-gen.0.5.0 on 5.0 had its build status changed: not available to passing
bls12-381-js.0.4.1 on 5.0 had its build status changed: not available to passing
bls12-381-js.0.4.2 on 5.0 had its build status changed: not available to passing
bls12-381-js.0.4.3 on 5.0 had its build status changed: not available to passing
bls12-381-js.0.5.0 on 5.0 had its build status changed: not available to passing
bls12-381.3.0.0 on 5.0 had its build status changed: not available to passing
bls12-381.3.0.1 on 5.0 had its build status changed: not available to passing
bogue.20221112 on 4.08 is now installable. Current state is: passing
bogue.20221112 on 4.09 is now installable. Current state is: passing
bogue.20221112 on 4.10 is now installable. Current state is: passing
bogue.20221112 on 4.11 is now installable. Current state is: passing
bogue.20221112 on 4.12 is now installable. Current state is: passing
bogue.20221112 on 4.13 is now installable. Current state is: passing
bogue.20221112 on 4.14 is now installable. Current state is: passing
bogue.20221112 on 4.14+alpha-repo is now installable. Current state is: passing
bogue.20221112 on 5.0 is now installable. Current state is: passing
bogue.20221112 on 5.0+alpha-repo is now installable. Current state is: passing
bonsai.v0.15.1 on 4.11 is now installable. Current state is: passing
bonsai.v0.15.1 on 4.12 is now installable. Current state is: passing
bonsai.v0.15.1 on 4.13 is now installable. Current state is: passing
bonsai.v0.15.1 on 4.14 is now installable. Current state is: passing
bonsai.v0.15.1 on 4.14+alpha-repo is now installable. Current state is: passing
bonsai.v0.15.1 on 5.0+alpha-repo is now installable. Current state is: passing
box.1.2.0 on 5.0 had its build status changed: not available to passing
box.1.2.0 on 5.0+alpha-repo had its build status changed: not available to passing
build_path_prefix_map.0.2 on 4.04 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.05 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.06 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.07 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.08 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.09 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.10 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.11 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.12 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.13 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.14 had its build status changed: internal failure to passing
build_path_prefix_map.0.2 on 4.14+alpha-repo had its build status changed: internal failure to passing
build_path_prefix_map.0.3 on 4.04 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.05 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.06 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.07 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.08 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.09 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.10 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.11 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.12 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.13 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.14 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
build_path_prefix_map.0.3 on 5.0 is now installable. Current state is: passing
build_path_prefix_map.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
builder.0.1.0 on 5.0 had its build status changed: not available to passing
builder.0.1.1 on 5.0 had its build status changed: not available to passing
builder.0.1.2 on 5.0 had its build status changed: not available to passing
builder.0.2.0 on 5.0 had its build status changed: not available to passing
builder.0.3.0 on 5.0 had its build status changed: not available to passing
builder.0.3.1 on 5.0 had its build status changed: not available to passing
cactus.1.0.0 on 5.0 had its build status changed: not available to passing
cairo2-gtk.0.6 on 5.0 had its build status changed: not available to passing
cairo2-gtk.0.6 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-gtk.0.6.1 on 5.0 had its build status changed: not available to passing
cairo2-gtk.0.6.1 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-gtk.0.6.2 on 5.0 had its build status changed: not available to passing
cairo2-gtk.0.6.2 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-gtk.0.6.3 on 5.0 had its build status changed: not available to passing
cairo2-gtk.0.6.3 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-gtk.0.6.4 on 5.0 had its build status changed: not available to passing
cairo2-gtk.0.6.4 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-pango.0.6 on 5.0 had its build status changed: not available to passing
cairo2-pango.0.6 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-pango.0.6.1 on 5.0 had its build status changed: not available to passing
cairo2-pango.0.6.1 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-pango.0.6.2 on 5.0 had its build status changed: not available to passing
cairo2-pango.0.6.2 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-pango.0.6.3 on 5.0 had its build status changed: not available to passing
cairo2-pango.0.6.3 on 5.0+alpha-repo had its build status changed: not available to passing
cairo2-pango.0.6.4 on 5.0 had its build status changed: not available to passing
cairo2-pango.0.6.4 on 5.0+alpha-repo had its build status changed: not available to passing
calculon-web.0.7 on 5.0+alpha-repo had its build status changed: partially failing to passing
calculon-web.0.8 on 5.0+alpha-repo had its build status changed: partially failing to passing
caldav.0.2.0 on 4.08 is now installable. Current state is: passing
caldav.0.2.0 on 4.09 is now installable. Current state is: passing
caldav.0.2.0 on 4.10 is now installable. Current state is: passing
caldav.0.2.0 on 4.11 is now installable. Current state is: passing
caldav.0.2.0 on 4.12 is now installable. Current state is: passing
caldav.0.2.0 on 4.13 is now installable. Current state is: passing
caldav.0.2.0 on 4.14 is now installable. Current state is: passing
caldav.0.2.0 on 4.14+alpha-repo is now installable. Current state is: passing
caldav.0.2.0 on 5.0 is now installable. Current state is: passing
caldav.0.2.0 on 5.0+alpha-repo is now installable. Current state is: passing
calendar.3.0.0 on 4.03 is now installable. Current state is: passing
calendar.3.0.0 on 4.04 is now installable. Current state is: passing
calendar.3.0.0 on 4.05 is now installable. Current state is: passing
calendar.3.0.0 on 4.06 is now installable. Current state is: passing
calendar.3.0.0 on 4.07 is now installable. Current state is: passing
calendar.3.0.0 on 4.08 is now installable. Current state is: passing
calendar.3.0.0 on 4.09 is now installable. Current state is: passing
calendar.3.0.0 on 4.10 is now installable. Current state is: passing
calendar.3.0.0 on 4.11 is now installable. Current state is: passing
calendar.3.0.0 on 4.12 is now installable. Current state is: passing
calendar.3.0.0 on 4.13 is now installable. Current state is: passing
calendar.3.0.0 on 4.14 is now installable. Current state is: passing
calendar.3.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
calendar.3.0.0 on 5.0 is now installable. Current state is: passing
calendar.3.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
camlidl.1.10 on 4.05 is now installable. Current state is: passing
camlidl.1.10 on 4.06 is now installable. Current state is: passing
camlidl.1.10 on 4.07 is now installable. Current state is: passing
camlidl.1.10 on 4.08 is now installable. Current state is: passing
camlidl.1.10 on 4.09 is now installable. Current state is: passing
camlidl.1.10 on 4.10 is now installable. Current state is: passing
camlidl.1.10 on 4.11 is now installable. Current state is: passing
camlidl.1.10 on 4.12 is now installable. Current state is: passing
camlidl.1.10 on 4.13 is now installable. Current state is: passing
camlidl.1.10 on 4.14 is now installable. Current state is: passing
camlidl.1.10 on 4.14+alpha-repo is now installable. Current state is: passing
camlidl.1.10 on 5.0 is now installable. Current state is: passing
camlidl.1.10 on 5.0+alpha-repo is now installable. Current state is: passing
camlidl.1.11 on 4.05 is now installable. Current state is: passing
camlidl.1.11 on 4.06 is now installable. Current state is: passing
camlidl.1.11 on 4.07 is now installable. Current state is: passing
camlidl.1.11 on 4.08 is now installable. Current state is: passing
camlidl.1.11 on 4.09 is now installable. Current state is: passing
camlidl.1.11 on 4.10 is now installable. Current state is: passing
camlidl.1.11 on 4.11 is now installable. Current state is: passing
camlidl.1.11 on 4.12 is now installable. Current state is: passing
camlidl.1.11 on 4.13 is now installable. Current state is: passing
camlidl.1.11 on 4.14 is now installable. Current state is: passing
camlidl.1.11 on 4.14+alpha-repo is now installable. Current state is: passing
camlidl.1.11 on 5.0 is now installable. Current state is: passing
camlidl.1.11 on 5.0+alpha-repo is now installable. Current state is: passing
camlix.0.1 on 5.0 had its build status changed: not available to passing
camlpdf.2.5.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: passing
camlpdf.2.5.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: passing
camlpdf.2.5.3 on 4.10 is now installable. Current state is: passing
camlpdf.2.5.3 on 4.11 is now installable. Current state is: passing
camlpdf.2.5.3 on 4.12 is now installable. Current state is: passing
camlpdf.2.5.3 on 4.13 is now installable. Current state is: passing
camlpdf.2.5.3 on 4.14 is now installable. Current state is: passing
camlpdf.2.5.3 on 4.14+alpha-repo is now installable. Current state is: passing
camlpdf.2.5.3 on 5.0 is now installable. Current state is: passing
camlpdf.2.5.3 on 5.0+alpha-repo is now installable. Current state is: passing
camyll.0.4.0 on 5.0+alpha-repo had its build status changed: not available to passing
camyll.0.4.1 on 4.13 is now installable. Current state is: passing
camyll.0.4.1 on 4.14 is now installable. Current state is: passing
camyll.0.4.1 on 4.14+alpha-repo is now installable. Current state is: passing
camyll.0.4.1 on 5.0+alpha-repo is now installable. Current state is: passing
capnp-rpc-lwt.1.2.2 on 5.0 had its build status changed: not available to passing
capnp-rpc-mirage.1.2.2 on 5.0 had its build status changed: not available to passing
capnp-rpc-net.1.2.2 on 5.0 had its build status changed: not available to passing
capnp-rpc-unix.1.2.2 on 5.0 had its build status changed: not available to passing
capnp-rpc.1.2.2 on 5.0 had its build status changed: not available to passing
capnp.3.3.0 on 5.0 had its build status changed: not available to passing
capnp.3.4.0 on 5.0 had its build status changed: not available to passing
capnp.3.5.0 on 5.0 had its build status changed: not available to passing
caqti-async.1.3.0 on 5.0 had its build status changed: not available to passing
caqti-async.1.6.0 on 5.0 had its build status changed: not available to passing
caqti-async.1.7.0 on 5.0 had its build status changed: not available to passing
caqti-async.1.8.0 on 5.0 had its build status changed: not available to passing
caqti-async.1.9.0 on 5.0 had its build status changed: not available to passing
caqti-driver-postgresql.0.10.0 on 4.04 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.0 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.0 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.0 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.1 on 4.04 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.1 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.1 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.1 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.2 on 4.04 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.2 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.2 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.10.2 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.11.0 on 4.04 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.11.0 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.11.0 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.11.0 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.9.0 on 4.03 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.9.0 on 4.04 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.9.0 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.9.0 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.0.9.0 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.0.0 on 4.04 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.0.0 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.0.0 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.0.0 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.1.0 on 4.04 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.1.0 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.1.0 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.1.0 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.2.0 on 4.04 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.2.0 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.2.0 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.2.0 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.2.1 on 4.05 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.2.1 on 4.06 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.2.1 on 4.07 had its build status changed: partially failing to passing
caqti-driver-postgresql.1.9.1 on 4.08 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 4.09 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 4.10 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 4.11 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 4.12 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 4.13 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 4.14 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 4.14+alpha-repo is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 5.0 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.1 on 5.0+alpha-repo is now installable. Current state is: passing
caqti-type-calendar.1.0.0 on 5.0 had its build status changed: not available to passing
caqti-type-calendar.1.0.0 on 5.0+alpha-repo had its build status changed: not available to passing
caqti-type-calendar.1.2.0 on 5.0 had its build status changed: not available to passing
caqti-type-calendar.1.2.0 on 5.0+alpha-repo had its build status changed: not available to passing
caqti-type-calendar.1.9.0 on 5.0 had its build status changed: not available to passing
caqti-type-calendar.1.9.0 on 5.0+alpha-repo had its build status changed: not available to passing
carton-git.0.6.0 on 4.08 is now installable. Current state is: passing
carton-git.0.6.0 on 4.09 is now installable. Current state is: passing
carton-git.0.6.0 on 4.10 is now installable. Current state is: passing
carton-git.0.6.0 on 4.11 is now installable. Current state is: passing
carton-git.0.6.0 on 4.12 is now installable. Current state is: passing
carton-git.0.6.0 on 4.13 is now installable. Current state is: passing
carton-git.0.6.0 on 4.14 is now installable. Current state is: passing
carton-git.0.6.0 on 4.14+alpha-repo is now installable. Current state is: passing
carton-git.0.6.0 on 5.0 is now installable. Current state is: passing
carton-git.0.6.0 on 5.0+alpha-repo is now installable. Current state is: passing
carton-lwt.0.6.0 on 4.08 is now installable. Current state is: passing
carton-lwt.0.6.0 on 4.09 is now installable. Current state is: passing
carton-lwt.0.6.0 on 4.10 is now installable. Current state is: passing
carton-lwt.0.6.0 on 4.11 is now installable. Current state is: passing
carton-lwt.0.6.0 on 4.12 is now installable. Current state is: passing
carton-lwt.0.6.0 on 4.13 is now installable. Current state is: passing
carton-lwt.0.6.0 on 4.14 is now installable. Current state is: passing
carton-lwt.0.6.0 on 4.14+alpha-repo is now installable. Current state is: passing
carton-lwt.0.6.0 on 5.0 is now installable. Current state is: passing
carton-lwt.0.6.0 on 5.0+alpha-repo is now installable. Current state is: passing
carton.0.6.0 on 4.08 is now installable. Current state is: passing
carton.0.6.0 on 4.09 is now installable. Current state is: passing
carton.0.6.0 on 4.10 is now installable. Current state is: passing
carton.0.6.0 on 4.11 is now installable. Current state is: passing
carton.0.6.0 on 4.12 is now installable. Current state is: passing
carton.0.6.0 on 4.13 is now installable. Current state is: passing
carton.0.6.0 on 4.14 is now installable. Current state is: passing
carton.0.6.0 on 4.14+alpha-repo is now installable. Current state is: passing
carton.0.6.0 on 5.0 is now installable. Current state is: passing
carton.0.6.0 on 5.0+alpha-repo is now installable. Current state is: passing
catala.0.7.0 on 5.0 had its build status changed: not available to passing
catala.0.7.0 on 5.0+alpha-repo had its build status changed: not available to passing
catapult-client.0.1 on 5.0 had its build status changed: not available to passing
catapult-client.0.1.1 on 5.0 had its build status changed: not available to passing
catapult-daemon.0.1 on 5.0 had its build status changed: not available to passing
catapult-daemon.0.1.1 on 5.0 had its build status changed: not available to passing
chamo.3.0 on 5.0 had its build status changed: not available to passing
chamo.3.0 on 5.0+alpha-repo had its build status changed: not available to passing
charrua-client-lwt.1.2.2 on 5.0 had its build status changed: not available to passing
charrua-client-mirage.1.2.2 on 5.0 had its build status changed: not available to passing
charrua-client.1.2.2 on 5.0 had its build status changed: not available to passing
charrua-client.1.3.0 on 5.0 had its build status changed: not available to passing
charrua-client.1.4.0 on 5.0 had its build status changed: not available to passing
charrua-client.1.4.1 on 5.0 had its build status changed: not available to passing
charrua-client.1.5.0 on 5.0 had its build status changed: not available to passing
charrua-server.1.2.2 on 5.0 had its build status changed: not available to passing
charrua-server.1.3.0 on 5.0 had its build status changed: not available to passing
charrua-server.1.4.0 on 5.0 had its build status changed: not available to passing
charrua-server.1.4.1 on 5.0 had its build status changed: not available to passing
charrua-server.1.5.0 on 5.0 had its build status changed: not available to passing
charrua-unix.1.5.0 on 5.0 had its build status changed: not available to passing
charrua.1.2.2 on 5.0 had its build status changed: not available to passing
charrua.1.3.0 on 5.0 had its build status changed: not available to passing
charrua.1.4.0 on 5.0 had its build status changed: not available to passing
charrua.1.4.1 on 5.0 had its build status changed: not available to passing
charrua.1.5.0 on 5.0 had its build status changed: not available to passing
chartjs-annotation.0.2.2 on 5.0 had its build status changed: not available to passing
chartjs-colorschemes.0.2.2 on 5.0 had its build status changed: not available to passing
chartjs-datalabels.0.2.2 on 5.0 had its build status changed: not available to passing
chartjs-streaming.0.2.2 on 5.0 had its build status changed: not available to passing
chartjs.0.2.2 on 5.0 had its build status changed: not available to passing
chrome-trace.3.5.0 on 4.08 is now installable. Current state is: passing
chrome-trace.3.5.0 on 4.09 is now installable. Current state is: passing
chrome-trace.3.5.0 on 4.10 is now installable. Current state is: passing
chrome-trace.3.5.0 on 4.11 is now installable. Current state is: passing
chrome-trace.3.5.0 on 4.12 is now installable. Current state is: passing
chrome-trace.3.5.0 on 4.13 is now installable. Current state is: passing
chrome-trace.3.5.0 on 4.14 is now installable. Current state is: passing
chrome-trace.3.5.0 on 4.14+alpha-repo is now installable. Current state is: passing
chrome-trace.3.5.0 on 5.0 is now installable. Current state is: passing
chrome-trace.3.5.0 on 5.0+alpha-repo is now installable. Current state is: passing
chrome-trace.3.6.0 on 4.08 is now installable. Current state is: passing
chrome-trace.3.6.0 on 4.09 is now installable. Current state is: passing
chrome-trace.3.6.0 on 4.10 is now installable. Current state is: passing
chrome-trace.3.6.0 on 4.11 is now installable. Current state is: passing
chrome-trace.3.6.0 on 4.12 is now installable. Current state is: passing
chrome-trace.3.6.0 on 4.13 is now installable. Current state is: passing
chrome-trace.3.6.0 on 4.14 is now installable. Current state is: passing
chrome-trace.3.6.0 on 4.14+alpha-repo is now installable. Current state is: passing
chrome-trace.3.6.0 on 5.0 is now installable. Current state is: passing
chrome-trace.3.6.0 on 5.0+alpha-repo is now installable. Current state is: passing
chrome-trace.3.6.1 on 4.08 is now installable. Current state is: passing
chrome-trace.3.6.1 on 4.09 is now installable. Current state is: passing
chrome-trace.3.6.1 on 4.10 is now installable. Current state is: passing
chrome-trace.3.6.1 on 4.11 is now installable. Current state is: passing
chrome-trace.3.6.1 on 4.12 is now installable. Current state is: passing
chrome-trace.3.6.1 on 4.13 is now installable. Current state is: passing
chrome-trace.3.6.1 on 4.14 is now installable. Current state is: passing
chrome-trace.3.6.1 on 4.14+alpha-repo is now installable. Current state is: passing
chrome-trace.3.6.1 on 5.0 is now installable. Current state is: passing
chrome-trace.3.6.1 on 5.0+alpha-repo is now installable. Current state is: passing
cloudi.2.0.5 on 4.06 is now installable. Current state is: passing
cloudi.2.0.5 on 4.07 is now installable. Current state is: passing
cloudi.2.0.5 on 4.08 is now installable. Current state is: passing
cloudi.2.0.5 on 4.09 is now installable. Current state is: passing
cloudi.2.0.5 on 4.10 is now installable. Current state is: passing
cloudi.2.0.5 on 4.11 is now installable. Current state is: passing
cloudi.2.0.5 on 4.12 is now installable. Current state is: passing
cloudi.2.0.5 on 4.13 is now installable. Current state is: passing
cloudi.2.0.5 on 4.14 is now installable. Current state is: passing
cloudi.2.0.5 on 4.14+alpha-repo is now installable. Current state is: passing
cloudi.2.0.5 on 5.0 is now installable. Current state is: passing
cloudi.2.0.5 on 5.0+alpha-repo is now installable. Current state is: passing
codept.0.11.1 on 5.0 had its build status changed: not available to passing
codept.0.11.1 on 5.0+alpha-repo had its build status changed: not available to passing
cohttp-async.2.5.6 on 5.0 had its build status changed: not available to passing
cohttp-async.5.0.0 on 5.0 had its build status changed: not available to passing
cohttp-async.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-async.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-curl-lwt.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-curl.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-eio.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-eio.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-lwt-jsoo.2.5.0 on 5.0 had its build status changed: not available to passing
cohttp-lwt-jsoo.2.5.1 on 5.0 had its build status changed: not available to passing
cohttp-lwt-jsoo.2.5.2-1 on 5.0 had its build status changed: not available to passing
cohttp-lwt-jsoo.2.5.4 on 5.0 had its build status changed: not available to passing
cohttp-lwt-jsoo.2.5.5 on 5.0 had its build status changed: not available to passing
cohttp-lwt-jsoo.2.5.6 on 5.0 had its build status changed: not available to passing
cohttp-lwt-jsoo.4.0.0 on 5.0 had its build status changed: not available to passing
cohttp-lwt-jsoo.5.0.0 on 5.0 had its build status changed: not available to passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-lwt-jsoo.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-lwt-unix.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-lwt.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-mirage.2.5.6 on 4.08 had its build status changed: internal failure to passing
cohttp-mirage.5.0.0 on 4.10 had its build status changed: internal failure to passing
cohttp-mirage.5.0.0 on 5.0 had its build status changed: not available to passing
cohttp-mirage.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-mirage.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-server-lwt-unix.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp-top.1.2.0 on 4.11 had its build status changed: internal failure to passing
cohttp-top.2.0.0 on 4.06 had its build status changed: internal failure to passing
cohttp-top.2.1.3 on 4.13 had its build status changed: internal failure to passing
cohttp-top.2.4.0 on 4.07 had its build status changed: internal failure to passing
cohttp-top.2.5.0 on 4.12 had its build status changed: internal failure to passing
cohttp-top.2.5.1 on 4.13 had its build status changed: internal failure to passing
cohttp-top.2.5.2-1 on 4.12 had its build status changed: internal failure to passing
cohttp-top.2.5.4 on 4.14+alpha-repo had its build status changed: internal failure to passing
cohttp-top.2.5.6 on 4.12 had its build status changed: internal failure to passing
cohttp-top.4.0.0 on 4.09 had its build status changed: internal failure to passing
cohttp-top.5.0.0 on 4.09 had its build status changed: internal failure to passing
cohttp-top.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp-top.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp.0.11.1 on 4.02 had its build status changed: internal failure to passing
cohttp.0.15.2 on 4.02 had its build status changed: internal failure to passing
cohttp.6.0.0~alpha0 on 4.08 is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 4.09 is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 4.10 is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 4.11 is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 4.12 is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 4.13 is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 4.14 is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 4.14+alpha-repo is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 5.0 is now installable. Current state is: passing
cohttp.6.0.0~alpha0 on 5.0+alpha-repo is now installable. Current state is: passing
cohttp_async_websocket.v0.15.0 on 4.14+alpha-repo had its build status changed: internal failure to passing
cohttp_async_websocket.v0.15.0 on 5.0 had its build status changed: not available to passing
cohttp_static_handler.v0.15.0 on 5.0 had its build status changed: not available to passing
colombe.0.7.0 on 4.05 is now installable. Current state is: passing
colombe.0.7.0 on 4.06 is now installable. Current state is: passing
colombe.0.7.0 on 4.07 is now installable. Current state is: passing
colombe.0.7.0 on 4.08 is now installable. Current state is: passing
colombe.0.7.0 on 4.09 is now installable. Current state is: passing
colombe.0.7.0 on 4.10 is now installable. Current state is: passing
colombe.0.7.0 on 4.11 is now installable. Current state is: passing
colombe.0.7.0 on 4.12 is now installable. Current state is: passing
colombe.0.7.0 on 4.13 is now installable. Current state is: passing
colombe.0.7.0 on 4.14 is now installable. Current state is: passing
colombe.0.7.0 on 4.14+alpha-repo is now installable. Current state is: passing
colombe.0.7.0 on 5.0 is now installable. Current state is: passing
colombe.0.7.0 on 5.0+alpha-repo is now installable. Current state is: passing
combinat.1.0 on 4.09 had its build status changed: internal failure to passing
comby-kernel.1.4.1 on 4.14 had its build status changed: internal failure to passing
comby-kernel.1.7.0 on 4.13 had its build status changed: internal failure to passing
comby-semantic.1.7.0 on 4.14 had its build status changed: internal failure to passing
comby-semantic.1.7.0 on 5.0 had its build status changed: not available to passing
comby.1.4.0 on 4.12 had its build status changed: internal failure to passing
comby.1.4.1 on 4.12 had its build status changed: internal failure to passing
comby.1.7.0 on 4.14 had its build status changed: internal failure to passing
command_rpc.v0.12.0 on 4.08 had its build status changed: internal failure to passing
command_rpc.v0.13.0 on 4.09 had its build status changed: internal failure to passing
command_rpc.v0.15.0 on 5.0 had its build status changed: not available to passing
conan-cli.0.0.1 on 5.0+alpha-repo had its build status changed: internal failure to passing
conan-lwt.0.0.1 on 4.10 had its build status changed: internal failure to passing
conan-lwt.0.0.2 on 4.14+alpha-repo had its build status changed: internal failure to passing
conan-unix.0.0.2 on 4.13 had its build status changed: internal failure to passing
conduit-async.1.5.0 on 5.0 had its build status changed: not available to passing
conduit-async.2.0.0 on 5.0 had its build status changed: not available to passing
conduit-async.2.0.1 on 5.0 had its build status changed: not available to passing
conduit-async.2.0.2 on 5.0 had its build status changed: not available to passing
conduit-async.2.1.0 on 5.0 had its build status changed: not available to passing
conduit-async.2.3.0 on 5.0 had its build status changed: not available to passing
conduit-async.4.0.0 on 5.0 had its build status changed: not available to passing
conduit-async.4.0.1 on 5.0 had its build status changed: not available to passing
conduit-async.4.0.2 on 5.0 had its build status changed: not available to passing
conduit-async.5.0.0 on 5.0 had its build status changed: not available to passing
conduit-async.5.1.0 on 5.0 had its build status changed: not available to passing
conduit-async.5.1.1 on 5.0 had its build status changed: not available to passing
conduit-async.6.0.0 on 5.0 had its build status changed: not available to passing
conduit-async.6.0.1 on 4.11 is now installable. Current state is: passing
conduit-async.6.0.1 on 4.12 is now installable. Current state is: passing
conduit-async.6.0.1 on 4.13 is now installable. Current state is: passing
conduit-async.6.0.1 on 4.14 is now installable. Current state is: passing
conduit-async.6.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
conduit-async.6.0.1 on 5.0 is now installable. Current state is: passing
conduit-async.6.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.07 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.08 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.09 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.10 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.11 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.12 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.13 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.14 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 5.0 is now installable. Current state is: passing
conduit-lwt-unix.6.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.04 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.05 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.06 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.07 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.08 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.09 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.10 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.11 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.12 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.13 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.14 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
conduit-lwt.6.0.1 on 5.0 is now installable. Current state is: passing
conduit-lwt.6.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
conduit-mirage.5.0.0 on 5.0 had its build status changed: not available to passing
conduit-mirage.5.1.0 on 5.0 had its build status changed: not available to passing
conduit-mirage.5.1.1 on 5.0 had its build status changed: not available to passing
conduit-mirage.6.0.1 on 4.08 is now installable. Current state is: passing
conduit-mirage.6.0.1 on 4.09 is now installable. Current state is: passing
conduit-mirage.6.0.1 on 4.10 is now installable. Current state is: passing
conduit-mirage.6.0.1 on 4.11 is now installable. Current state is: passing
conduit-mirage.6.0.1 on 4.12 is now installable. Current state is: passing
conduit-mirage.6.0.1 on 4.13 is now installable. Current state is: passing
conduit-mirage.6.0.1 on 4.14 is now installable. Current state is: passing
conduit-mirage.6.0.1 on 4.14+alpha-repo is now installable. Current state is: passing
conduit-mirage.6.0.1 on 5.0 is now installable. Current state is: passing
conduit-mirage.6.0.1 on 5.0+alpha-repo is now installable. Current state is: passing
conduit.6.0.1 on 4.04 is now installable. Current state is: passing
conduit.6.0.1 on 4.05 is now installable. Current state is: passing
conduit.6.0.1 on 4.06 is now installable. Current state is: passing
conduit.6.0.1 on 4.07 is now installable. Current state is: passing
conduit.6.0.1 on 4.08 is now installable. Current state is: passing
conduit.6.0.1 on 4.09 is now installable. Current state is: passing
conduit.6.0.1 on 4.10 is now installable. Current state is: passing
conduit.6.0.1 on 4.11 is now installable. Current state is: passing
conduit.6.0.1 on 4.12 is now installable. Current state is: passing
conduit.6.0.1 on 4.13 is now installable. Current state is: passing
conduit.6.0.1 on 4.14 is now installable. Current state is: