opam-health-check diff

Home|Differences with the last checks|Previous runs

Differences between 418227c and 94675aa (git diff)

Packages now failing:

aws.1.0.0 on 5.0 had its build status changed: partially failing to failing
aws.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to failing
aws.1.0.1 on 5.0 had its build status changed: partially failing to failing
aws.1.0.1 on 5.0+alpha-repo had its build status changed: partially failing to failing
aws.1.0.2 on 5.0 had its build status changed: partially failing to failing
aws.1.0.2 on 5.0+alpha-repo had its build status changed: partially failing to failing
bechamel-notty.0.2.0.1~alpha-repo on 4.14+alpha-repo had its build status changed: passing to failing
bechamel-notty.0.2.0.1~alpha-repo on 5.0+alpha-repo had its build status changed: passing to failing
binsec.0.3 on 4.05 had its build status changed: passing 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
conf-libclang.12 on 4.12 had its build status changed: internal failure to failing
coq.8.6.1 on 4.02 had its build status changed: passing to failing
coq.8.7.1+2 on 4.06 had its build status changed: passing to failing
coq.8.8.0 on 4.03 had its build status changed: passing to failing
coq.8.8.2 on 4.09 had its build status changed: passing to failing
csvfields.v0.15.0 on 5.0 had its build status changed: not available to 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-httpaf.1.0.0.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
dream-httpaf.1.0.0.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
eio.0.3 on 5.0 had its build status changed: passing to failing
eio.0.3 on 5.0+alpha-repo had its build status changed: passing to failing
eio.0.4 on 5.0 had its build status changed: passing to failing
eio.0.4 on 5.0+alpha-repo had its build status changed: passing to failing
eio.0.5 on 5.0 had its build status changed: passing to failing
eio.0.5 on 5.0+alpha-repo had its build status changed: passing to failing
esperanto.0.0.1 on 4.14 is now installable. Current state is: failing
esperanto.0.0.1 on 4.14+alpha-repo is now installable. Current state is: failing
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
glpk.0.1.6 on 4.02 had its build status changed: internal failure 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: partially failing to failing
links.0.9.4 on 5.0+alpha-repo had its build status changed: partially failing to failing
links.0.9.5 on 5.0 had its build status changed: partially failing to failing
links.0.9.5 on 5.0+alpha-repo had its build status changed: partially failing to failing
links.0.9.6 on 5.0 had its build status changed: partially failing to failing
links.0.9.6 on 5.0+alpha-repo had its build status changed: partially failing to failing
liquidsoap.2.1.2 on 4.14+alpha-repo is now installable. Current state is: failing
lwt_domain.0.1.0 on 5.0 had its build status changed: passing to failing
lwt_domain.0.1.0 on 5.0+alpha-repo had its build status changed: passing to failing
lwt_domain.0.2.0 on 5.0 had its build status changed: passing to failing
lwt_domain.0.2.0 on 5.0+alpha-repo had its build status changed: passing to failing
mccs.1.1+3 on 4.05 had its build status changed: internal failure to failing
mccs.1.1+3 on 4.08 had its build status changed: internal failure to failing
mccs.1.1+5 on 4.09 had its build status changed: internal failure to failing
mccs.1.1+8 on 4.04 had its build status changed: internal failure to failing
mccs.1.1+9 on 4.08 had its build status changed: internal failure to failing
mirage-xen-minios.0.4.2 on 4.10 had its build status changed: internal failure to failing
mirage-xen-minios.0.5.0 on 4.07 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
mlgmpidl.1.2.11 on 5.0 had its build status changed: partially failing to failing
ocal.0.1.1 on 5.0 had its build status changed: partially failing to failing
ocal.0.1.1 on 5.0+alpha-repo had its build status changed: partially failing to failing
ocal.0.1.2 on 5.0 had its build status changed: partially failing to failing
ocal.0.1.2 on 5.0+alpha-repo had its build status changed: partially failing to failing
ocaml-monadic.0.3.2 on 5.0 had its build status changed: not available to failing
ocaml-monadic.0.3.2 on 5.0+alpha-repo had its build status changed: not available to failing
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
ocf.0.6.0 on 5.0 had its build status changed: not available to failing
ocf.0.6.0 on 5.0+alpha-repo had its build status changed: not available to failing
ocf.0.7.0 on 5.0 had its build status changed: not available to failing
ocf.0.7.0 on 5.0+alpha-repo had its build status changed: not available to failing
ocp-index-top.0.4.1 on 4.08 had its build status changed: passing to failing
ocp-index-top.0.4.1 on 4.09 had its build status changed: passing to failing
ocp-index-top.0.4.3 on 4.08 had its build status changed: passing to failing
ocp-index-top.0.4.3 on 4.09 had its build status changed: passing to failing
ocp-index-top.0.5.0 on 4.08 had its build status changed: passing to failing
ocp-index-top.0.5.0 on 4.09 had its build status changed: passing to failing
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
ojs-base.0.6.0 on 5.0+alpha-repo had its build status changed: not available to failing
oplsr.8.0.1 on 4.02 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.03 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.04 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.05 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.06 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.07 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.08 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.09 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.10 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.11 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.12 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.13 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.14 had its build status changed: internal failure to failing
oplsr.8.0.1 on 4.14+alpha-repo had its build status changed: internal failure to failing
orun.0.0.1 on 4.09 had its build status changed: passing to failing
orun.0.0.1 on 4.14+alpha-repo had its build status changed: passing to failing
pgocaml.2.2 on 5.0+alpha-repo had its build status changed: partially failing to failing
pgocaml.2.3 on 5.0 had its build status changed: partially failing to failing
pgocaml.2.3 on 5.0+alpha-repo had its build status changed: partially failing to failing
pgocaml.3.0 on 5.0 had its build status changed: partially failing to failing
pgocaml.3.0 on 5.0+alpha-repo had its build status changed: partially failing to failing
pgocaml.4.0 on 5.0 had its build status changed: partially failing to failing
pgocaml.4.0 on 5.0+alpha-repo had its build status changed: partially failing to failing
pgocaml.4.2 on 5.0 had its build status changed: partially failing to failing
pgocaml.4.2 on 5.0+alpha-repo had its build status changed: partially failing to failing
pgocaml.4.2.2 on 5.0 had its build status changed: partially failing to failing
pgocaml.4.2.2 on 5.0+alpha-repo had its build status changed: partially failing to failing
pgocaml.4.3.0 on 5.0 had its build status changed: partially failing to failing
pgocaml.4.3.0 on 5.0+alpha-repo had its build status changed: partially failing to failing
piqi.0.7.0 on 4.14 had its build status changed: not available to failing
piqi.0.7.0 on 4.14+alpha-repo had its build status changed: not available to failing
piqi.0.7.1 on 4.14 had its build status changed: not available to failing
piqi.0.7.1 on 4.14+alpha-repo had its build status changed: not available to failing
piqi.0.7.4 on 4.14 had its build status changed: not available to failing
piqi.0.7.4 on 4.14+alpha-repo had its build status changed: not available to failing
piqi.0.7.5 on 4.14 had its build status changed: not available to failing
piqi.0.7.5 on 4.14+alpha-repo had its build status changed: not available to failing
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
sphinxcontrib-ocaml.0.2.0 on 4.05 had its build status changed: partially failing to failing
srt.0.2.2 on 4.03 is now installable. Current state is: failing
srt.0.2.2 on 4.04 is now installable. Current state is: failing
srt.0.2.2 on 4.05 is now installable. Current state is: failing
srt.0.2.2 on 4.06 is now installable. Current state is: failing
srt.0.2.2 on 4.07 is now installable. Current state is: failing
syndic.1.2 on 5.0 had its build status changed: partially failing to failing
syndic.1.2 on 5.0+alpha-repo had its build status changed: partially failing to failing
syndic.1.3 on 5.0 had its build status changed: partially failing to failing
syndic.1.3 on 5.0+alpha-repo had its build status changed: partially failing to failing
syndic.1.3.1 on 5.0 had its build status changed: partially failing to failing
syndic.1.3.1 on 5.0+alpha-repo had its build status changed: partially failing to failing
syndic.1.4 on 5.0 had its build status changed: partially failing to failing
syndic.1.4 on 5.0+alpha-repo had its build status changed: partially failing to failing
tar.1.0.0 on 5.0 had its build status changed: not available to failing
tar.1.0.0 on 5.0+alpha-repo had its build status changed: not available to failing
tar.1.0.1 on 5.0 had its build status changed: not available to failing
tar.1.0.1 on 5.0+alpha-repo had its build status changed: not available to failing
tar.1.1.0 on 5.0 had its build status changed: not available to failing
tar.1.1.0 on 5.0+alpha-repo had its build status changed: not available to failing
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
torch.0.4 on 5.0 had its build status changed: not available to failing
torch.0.5 on 5.0 had its build status changed: not available to failing
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
ubpf.0.1 on 4.14 had its build status changed: passing 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 5.0 had its build status changed: partially failing to failing
webmachine.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to failing
z3.4.10.2 on 4.12 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.0 on 4.14 had its build status changed: passing to failing
z3.4.7.1 on 4.11 had its build status changed: passing to failing
z3.4.8.1 on 4.06 had its build status changed: passing to failing
z3.4.8.11 on 4.02 had its build status changed: passing to failing
z3.4.8.11 on 4.06 had its build status changed: passing to failing
z3.4.8.11 on 4.14 had its build status changed: passing to failing
z3.4.8.13 on 4.12 had its build status changed: passing to failing
z3.4.8.13 on 4.13 had its build status changed: passing to failing
z3.4.8.14 on 4.10 had its build status changed: passing to failing
z3.4.8.17 on 5.0 had its build status changed: passing to failing
z3.4.8.4 on 4.09 had its build status changed: passing to failing
z3.4.8.4 on 4.10 had its build status changed: passing to failing
z3.4.8.5 on 4.06 had its build status changed: passing to failing
z3.4.8.6 on 4.12 had its build status changed: passing to failing
z3.4.8.7 on 4.07 had its build status changed: passing to failing
z3.4.8.7 on 4.08 had its build status changed: passing to failing
z3.4.8.8 on 4.03 had its build status changed: passing to failing
z3.4.8.8 on 4.14 had its build status changed: passing to failing
z3.4.8.8 on 4.14+alpha-repo 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.05 had its build status changed: passing to failing
z3.4.8.9-1 on 4.06 had its build status changed: passing to failing
z3.4.9.1 on 4.12 had its build status changed: passing to failing
z3.4.9.1 on 4.13 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 5.0 had its build status changed: not available 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 5.0 had its build status changed: not available 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 5.0 had its build status changed: not available 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 5.0 had its build status changed: not available to partially failing
0install-gtk.2.18 on 5.0+alpha-repo had its build status changed: not available to partially failing
DrawGrammar.0.1.0 on 4.03 had its build status changed: failing to partially failing
DrawGrammar.0.2.0 on 4.02 had its build status changed: failing to partially failing
DrawGrammar.0.2.0 on 4.03 had its build status changed: failing to partially failing
FPauth-core.1.0.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
FPauth-responses.1.0.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
FPauth-strategies.1.0.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
FPauth.1.0.0 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-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 is now installable. Current state is: partially failing
aws-s3-async.4.8.0 on 5.0+alpha-repo is now installable. Current state is: partially failing
aws-s3-lwt.4.4.0 on 5.0 had its build status changed: not available to partially failing
aws-s3-lwt.4.4.1 on 5.0 had its build status changed: not available to partially failing
aws-s3-lwt.4.5.1 on 5.0 had its build status changed: not available to partially failing
aws-s3-lwt.4.6.0 on 5.0 had its build status changed: not available to partially failing
aws-s3-lwt.4.7.0 on 5.0 had its build status changed: not available to partially failing
aws-s3-lwt.4.8.0 on 5.0 is now installable. Current state is: partially failing
aws-s3-lwt.4.8.0 on 5.0+alpha-repo is now installable. Current state is: partially failing
aws-s3.4.4.0 on 5.0 had its build status changed: not available to partially failing
aws-s3.4.4.1 on 5.0 had its build status changed: not available to partially failing
aws-s3.4.5.1 on 5.0 had its build status changed: not available to partially failing
aws-s3.4.6.0 on 5.0 had its build status changed: not available to partially failing
aws-s3.4.7.0 on 5.0 had its build status changed: not available to partially failing
aws-s3.4.8.0 on 5.0 is now installable. Current state is: partially failing
aws-s3.4.8.0 on 5.0+alpha-repo is now installable. Current state is: partially failing
bap-frontc.1.2.0 on 4.02 had its build status changed: passing to partially failing
bap-objdump.1.3.0 on 4.02 had its build status changed: failing to partially failing
bap-taint.1.3.0 on 4.02 had its build status changed: passing to partially failing
bddrand.2.71.10 on 5.0 had its build status changed: not available to partially failing
bddrand.2.71.10 on 5.0+alpha-repo had its build status changed: not available to partially failing
bechamel-notty.0.1.0 on 5.0 had its build status changed: not available to partially failing
bechamel-notty.0.2.0 on 5.0 had its build status changed: not available to partially failing
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
cohttp-async.1.0.2 on 4.05 had its build status changed: passing to partially failing
cohttp-async.1.1.1 on 4.07 had its build status changed: passing to partially failing
cohttp-async.2.3.0 on 4.06 had its build status changed: passing to partially failing
cohttp-async.5.0.0 on 4.12 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.2.2.0 on 4.06 had its build status changed: passing to partially failing
cohttp-lwt-jsoo.2.5.2-1 on 4.06 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
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
coqide.8.12.0 on 4.11 had its build status changed: passing to partially failing
cordova-plugin-activity-indicator.1.0 on 4.11 had its build status changed: passing to partially failing
cordova-plugin-background-mode.1.0 on 4.10 had its build status changed: passing to partially failing
cow.1.3.0 on 4.02 had its build status changed: passing to partially failing
current_examples.0.6 on 5.0 had its build status changed: not available 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
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
dream-accept.0.1.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
dream-cli.0.2.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
dream-encoding.0.2.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
dream-htmx.0.1.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
dream-livereload.0.2.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
dream.1.0.0.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: partially failing
dream.1.0.0.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: partially failing
dream.1.0.0~alpha3 on 4.14+alpha-repo had its build status changed: passing to partially failing
dream.1.0.0~alpha4 on 4.14+alpha-repo had its build status changed: passing to partially failing
eio_linux.0.3 on 5.0 had its build status changed: passing to partially failing
eio_linux.0.3 on 5.0+alpha-repo had its build status changed: passing to partially failing
eio_linux.0.4 on 5.0 had its build status changed: passing to partially failing
eio_linux.0.4 on 5.0+alpha-repo had its build status changed: passing to partially failing
eio_linux.0.5 on 5.0 had its build status changed: passing to partially failing
eio_linux.0.5 on 5.0+alpha-repo had its build status changed: passing to partially failing
eio_luv.0.3 on 5.0 had its build status changed: passing to partially failing
eio_luv.0.3 on 5.0+alpha-repo had its build status changed: passing to partially failing
eio_luv.0.4 on 5.0 had its build status changed: passing to partially failing
eio_luv.0.4 on 5.0+alpha-repo had its build status changed: passing to partially failing
eio_luv.0.5 on 5.0 had its build status changed: passing to partially failing
eio_luv.0.5 on 5.0+alpha-repo had its build status changed: passing to partially failing
eio_main.0.3 on 5.0 had its build status changed: passing to partially failing
eio_main.0.3 on 5.0+alpha-repo had its build status changed: passing to partially failing
eio_main.0.4 on 5.0 had its build status changed: passing to partially failing
eio_main.0.4 on 5.0+alpha-repo had its build status changed: passing to partially failing
eio_main.0.5 on 5.0 had its build status changed: passing to partially failing
eio_main.0.5 on 5.0+alpha-repo had its build status changed: passing 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
gluten-mirage.0.2.1 on 5.0 had its build status changed: not available to 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
higlo.0.5 on 5.0+alpha-repo had its build status changed: not available to partially failing
higlo.0.6 on 5.0+alpha-repo had its build status changed: not available to partially failing
hyper.1.0.0~alpha1 on 4.14+alpha-repo had its build status changed: passing 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
jupyter.2.7.1 on 4.05 had its build status changed: passing to partially failing
jupyter.2.7.2 on 4.09 had its build status changed: passing to partially failing
jupyter.2.7.6 on 4.11 had its build status changed: passing to partially failing
jupyter.2.7.7 on 4.12 had its build status changed: passing to partially failing
jwto.0.1.4 on 4.06 had its build status changed: passing to partially failing
jwto.0.2.0 on 4.06 had its build status changed: passing to partially failing
jwto.0.2.1 on 4.09 had its build status changed: passing to partially failing
jwto.0.4.0 on 4.10 had its build status changed: passing to partially failing
kafka.0.3 on 4.11 had its build status changed: passing to partially failing
ledgerwallet-tezos.0.1.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ledgerwallet-tezos.0.2.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ledgerwallet-tezos.0.2.1 on 4.14+alpha-repo had its build status changed: passing to partially failing
ledgerwallet.0.1.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ledgerwallet.0.2.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
ledgerwallet.0.2.1 on 4.14+alpha-repo had its build status changed: passing to partially failing
lutin.2.71.10 on 5.0 had its build status changed: not available to partially failing
lutin.2.71.10 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 is now installable. Current state is: partially failing
mirage-monitoring.0.0.3 on 5.0+alpha-repo is now installable. Current state is: partially failing
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
pecu.0.1 on 4.05 had its build status changed: passing to partially failing
pfff.0.39.5 on 4.07 had its build status changed: passing to partially failing
pg_query.0.9.4 on 4.12 had its build status changed: passing to partially failing
pgocaml.2.3 on 4.03 had its build status changed: passing to partially failing
pgx_lwt_unix.2.0 on 4.14 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
prbnmcn-dagger-test.0.0.1 on 5.0 had its build status changed: internal failure to partially failing
prbnmcn-dagger-test.0.0.1 on 5.0+alpha-repo had its build status changed: internal failure to partially failing
prbnmcn-dagger-test.0.0.2 on 5.0 had its build status changed: internal failure to partially failing
prbnmcn-dagger-test.0.0.2 on 5.0+alpha-repo had its build status changed: internal failure 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 5.0 had its build status changed: not available to partially failing
tar-unix.1.0.1 on 5.0 had its build status changed: not available to partially failing
tar-unix.1.0.1 on 5.0+alpha-repo had its build status changed: not available to partially failing
tar-unix.1.1.0 on 5.0 had its build status changed: not available to partially failing
tar-unix.1.1.0 on 5.0+alpha-repo had its build status changed: not available to partially failing
tensorflow.0.0.5 on 4.02 had its build status changed: passing to partially failing
textutils.113.33.03 on 4.02 had its build status changed: passing to partially failing
tezos.14.0 on 4.14+alpha-repo had its build status changed: passing to partially failing
vchan-unix.4.0.2 on 5.0 had its build status changed: not available to partially failing
vchan-unix.4.0.2 on 5.0+alpha-repo had its build status changed: not available to partially failing
vchan-unix.4.0.3 on 5.0 had its build status changed: not available to partially failing
vchan-unix.4.0.3 on 5.0+alpha-repo had its build status changed: not available to partially failing
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.11.0 on 4.10 is now installable. Current state is: partially failing
z3_tptp.4.11.0 on 4.11 is now installable. Current state is: partially failing

Packages now 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
amqp-client.1.0.3 on 5.0 had its build status changed: partially failing to not available
amqp-client.1.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
amqp-client.1.0.4 on 5.0 had its build status changed: partially failing to not available
amqp-client.1.0.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
amqp-client.1.0.5 on 5.0 had its build status changed: partially failing to not available
amqp-client.1.0.5 on 5.0+alpha-repo had its build status changed: partially failing to not available
amqp-client.1.0.6 on 5.0 had its build status changed: partially failing to not available
amqp-client.1.0.6 on 5.0+alpha-repo had its build status changed: partially failing to not available
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
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.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
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
base.v0.15.1~5.0preview on 5.0 is not available anymore. Previous state was: passing
base.v0.15.1~5.0preview on 5.0+alpha-repo is not available anymore. Previous state was: passing
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
calendar.1.10 on 5.0 had its build status changed: failing to not available
calendar.1.10 on 5.0+alpha-repo had its build status changed: failing to not available
calendar.2.03.2 on 5.0 had its build status changed: failing to not available
calendar.2.03.2 on 5.0+alpha-repo had its build status changed: failing to not available
calendar.2.04 on 5.0 had its build status changed: failing to not available
calendar.2.04 on 5.0+alpha-repo had its build status changed: failing to not available
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
camyll.0.2.0 on 5.0 had its build status changed: partially failing to not available
camyll.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
camyll.0.3.0 on 5.0 had its build status changed: partially failing to not available
camyll.0.3.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
camyll.0.4.0 on 5.0 had its build status changed: partially failing to not available
camyll.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
caqti-driver-mariadb.1.0.0 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.1.0 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.2.0 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.2.1 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.2.3 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.3.0 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.4.0 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.5.0 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.5.1 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.6.0 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.7.0 on 5.0 had its build status changed: partially failing to not available
caqti-driver-mariadb.1.8.0 on 5.0 had its build status changed: partially failing to not available
clap.0.1.0 on 5.0+alpha-repo had its build status changed: passing to not available
cohttp-top.2.2.0 on 5.0 had its build status changed: partially failing to not available
cohttp-top.2.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
cohttp.2.1.3 on 5.0 had its build status changed: failing to not available
cohttp.2.1.3 on 5.0+alpha-repo had its build status changed: failing to not available
cohttp.2.2.0 on 5.0 had its build status changed: failing to not available
cohttp.2.2.0 on 5.0+alpha-repo had its build status changed: failing to not available
colombe.0.1.0 on 5.0 had its build status changed: partially failing to not available
colombe.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
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
conf-llvm.12.0.1 on 4.02 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.03 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.04 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.05 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.06 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.07 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.08 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.09 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.10 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.11 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.12 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.13 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.14 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 4.14+alpha-repo is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 5.0 is not available anymore. Previous state was: passing
conf-llvm.12.0.1 on 5.0+alpha-repo is not available anymore. Previous state was: passing
conjury.2.1 on 5.0 had its build status changed: partially failing to not available
conjury.2.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
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
cryptohash.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
cryptohash.0.1.1 on 5.0 had its build status changed: partially failing to not available
cryptohash.0.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
cryptohash.0.1.2 on 5.0 had its build status changed: partially failing to not available
cryptohash.0.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
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
depgraph.0.1.0 on 5.0 had its build status changed: partially failing to not available
depgraph.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
digestif.0.1 on 5.0 had its build status changed: failing to not available
digestif.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
digestif.0.2 on 5.0 had its build status changed: failing to not available
digestif.0.2 on 5.0+alpha-repo had its build status changed: failing to not available
digestif.0.3 on 5.0 had its build status changed: failing to not available
digestif.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
digestif.0.4 on 5.0 had its build status changed: failing to not available
digestif.0.4 on 5.0+alpha-repo had its build status changed: failing to not available
digestif.0.5 on 5.0 had its build status changed: failing to not available
digestif.0.5 on 5.0+alpha-repo had its build status changed: failing to not available
digestif.0.7 on 5.0 had its build status changed: failing to not available
digestif.0.7 on 5.0+alpha-repo had its build status changed: failing to not available
digestif.0.7.1 on 5.0 had its build status changed: failing to not available
digestif.0.7.1 on 5.0+alpha-repo had its build status changed: failing to not available
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.0.6.1 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
drom_lib.0.6.1 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
extprot.1.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
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_config.0.2.0 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
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
fiat-p256.0.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
fiat-p256.0.2.0 on 5.0 had its build status changed: failing to not available
fiat-p256.0.2.0 on 5.0+alpha-repo had its build status changed: failing to not available
genspir.1.0.0 on 5.0+alpha-repo had its build status changed: passing 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
hxd.0.1.0 on 5.0 had its build status changed: failing to not available
hxd.0.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
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
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
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
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
llvm.12.0.1 on 4.02 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.03 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.04 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.05 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.06 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.07 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.08 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.09 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.10 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.11 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.12 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.13 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.14 is not available anymore. Previous state was: passing
llvm.12.0.1 on 4.14+alpha-repo is not available anymore. Previous state was: passing
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
mariadb.1.1.5 on 5.0 had its build status changed: failing to not available
mariadb.1.1.5 on 5.0+alpha-repo had its build status changed: failing to not available
mariadb.1.1.6 on 5.0 had its build status changed: failing to not available
mariadb.1.1.6 on 5.0+alpha-repo had its build status changed: failing to not available
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
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
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
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
notty.0.2.2.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
notty.0.2.2.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
notty.0.2.2.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
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
omake.0.10.3 on 5.0 had its build status changed: failing to not available
omake.0.10.3 on 5.0+alpha-repo had its build status changed: failing to not available
omake.0.10.5 on 5.0 had its build status changed: failing to not available
omake.0.10.5 on 5.0+alpha-repo had its build status changed: failing to not available
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-dune-lint.0.2 on 5.0+alpha-repo had its build status changed: passing to not available
opam-sync-github-prs.1.0.0 on 4.04 had its build status changed: internal failure 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
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
orsetto.1.0.2 on 5.0 had its build status changed: partially failing to not available
orsetto.1.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
orsetto.1.0.3 on 5.0 had its build status changed: partially failing to not available
orsetto.1.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
orsetto.1.1 on 5.0 had its build status changed: partially failing to not available
orsetto.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
orsetto.1.1.1 on 5.0 had its build status changed: partially failing to not available
orsetto.1.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
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
pbs.0.2.0 on 5.0 had its build status changed: partially failing to not available
pbs.0.2.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
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
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
ppx_expect.v0.15.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
ppx_expect.v0.15.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
ppx_expect.v0.15.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
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
reason.3.8.1 on 5.0 had its build status changed: passing to not available
reason.3.8.1 on 5.0+alpha-repo had its build status changed: passing to not available
resto-json.0.2 on 5.0+alpha-repo had its build status changed: passing to not available
rtop.3.8.1 on 5.0 had its build status changed: passing to not available
rtop.3.8.1 on 5.0+alpha-repo had its build status changed: passing to not available
sendmail-lwt.0.1.0 on 5.0 had its build status changed: partially failing to not available
sendmail-lwt.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
sendmail.0.1.0 on 5.0 had its build status changed: partially failing to not available
sendmail.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
sexp_pretty.v0.15.0 on 5.0 had its build status changed: failing to not available
sexp_pretty.v0.15.0 on 5.0+alpha-repo had its build status changed: failing to not available
sexp_pretty.v0.15.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 4.14+alpha-repo is not available anymore. Previous state was: passing
sexp_pretty.v0.15.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
sexp_pretty.v0.15.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
sexplib.v0.15.0.1~alpha-repo on 4.02 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.03 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.04 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.05 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.06 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.07 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.08 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.09 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.10 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.11 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.12 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.13 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 4.14 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 5.0 is not available anymore. Previous state was: internal failure
sexplib.v0.15.0.1~alpha-repo on 5.0+alpha-repo is not available anymore. Previous state was: passing
sihl-queue.0.4.0 on 5.0 had its build status changed: partially failing to not available
sihl-queue.0.4.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.0.4.1 on 5.0 had its build status changed: partially failing to not available
sihl-queue.0.4.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.0.5.0 on 5.0 had its build status changed: partially failing to not available
sihl-queue.0.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.0.6.0~rc1 on 5.0 had its build status changed: partially failing to not available
sihl-queue.0.6.0~rc1 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.1.0.0 on 5.0 had its build status changed: partially failing to not available
sihl-queue.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.1.0.0~rc1 on 5.0 had its build status changed: partially failing to not available
sihl-queue.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.1.0.0~rc2 on 5.0 had its build status changed: partially failing to not available
sihl-queue.1.0.0~rc2 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.1.0.0~rc3 on 5.0 had its build status changed: partially failing to not available
sihl-queue.1.0.0~rc3 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.1.0.1 on 5.0 had its build status changed: partially failing to not available
sihl-queue.1.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.2.0.0 on 5.0 had its build status changed: partially failing to not available
sihl-queue.2.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.2.0.1 on 5.0 had its build status changed: partially failing to not available
sihl-queue.2.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.3.0.0 on 5.0 had its build status changed: partially failing to not available
sihl-queue.3.0.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.3.0.1 on 5.0 had its build status changed: partially failing to not available
sihl-queue.3.0.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.3.0.2 on 5.0 had its build status changed: partially failing to not available
sihl-queue.3.0.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl-queue.3.0.3 on 5.0 had its build status changed: partially failing to not available
sihl-queue.3.0.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl.0.0.56 on 5.0 had its build status changed: partially failing to not available
sihl.0.0.56 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl.0.1.0 on 5.0 had its build status changed: partially failing to not available
sihl.0.1.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl.0.1.1 on 5.0 had its build status changed: partially failing to not available
sihl.0.1.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl.0.1.2 on 5.0 had its build status changed: partially failing to not available
sihl.0.1.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
sihl.0.1.3 on 5.0 had its build status changed: partially failing to not available
sihl.0.1.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
spelll.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.3.0.0 on 5.0 had its build status changed: failing to not available
sqlite3.3.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.0.0 on 5.0 had its build status changed: failing to not available
sqlite3.4.0.0 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.0.1 on 5.0 had its build status changed: failing to not available
sqlite3.4.0.1 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.0.2 on 5.0 had its build status changed: failing to not available
sqlite3.4.0.2 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.0.3 on 5.0 had its build status changed: failing to not available
sqlite3.4.0.3 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.0.4 on 5.0 had its build status changed: failing to not available
sqlite3.4.0.4 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.0.6 on 5.0 had its build status changed: failing to not available
sqlite3.4.0.6 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.1.0 on 5.0 had its build status changed: failing to not available
sqlite3.4.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.1.2 on 5.0 had its build status changed: failing to not available
sqlite3.4.1.2 on 5.0+alpha-repo had its build status changed: failing to not available
sqlite3.4.1.3 on 5.0 had its build status changed: failing to not available
sqlite3.4.1.3 on 5.0+alpha-repo had its build status changed: failing to not available
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
syslog.2.0.0 on 5.0+alpha-repo had its build status changed: passing to not available
tezos-crypto.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-crypto.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-crypto.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-crypto.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-crypto.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-error-monad.7.0 on 5.0 had its build status changed: partially failing to not available
tezos-error-monad.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-error-monad.7.1 on 5.0 had its build status changed: partially failing to not available
tezos-error-monad.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-error-monad.7.2 on 5.0 had its build status changed: partially failing to not available
tezos-error-monad.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-error-monad.7.3 on 5.0 had its build status changed: partially failing to not available
tezos-error-monad.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-error-monad.7.4 on 5.0 had its build status changed: partially failing to not available
tezos-error-monad.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-event-logging.7.0 on 5.0 had its build status changed: partially failing to not available
tezos-event-logging.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-event-logging.7.1 on 5.0 had its build status changed: partially failing to not available
tezos-event-logging.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-event-logging.7.2 on 5.0 had its build status changed: partially failing to not available
tezos-event-logging.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-event-logging.7.3 on 5.0 had its build status changed: partially failing to not available
tezos-event-logging.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-event-logging.7.4 on 5.0 had its build status changed: partially failing to not available
tezos-event-logging.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-micheline.7.0 on 5.0 had its build status changed: partially failing to not available
tezos-micheline.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-micheline.7.1 on 5.0 had its build status changed: partially failing to not available
tezos-micheline.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-micheline.7.2 on 5.0 had its build status changed: partially failing to not available
tezos-micheline.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-micheline.7.3 on 5.0 had its build status changed: partially failing to not available
tezos-micheline.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-micheline.7.4 on 5.0 had its build status changed: partially failing to not available
tezos-micheline.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-rpc.7.0 on 5.0 had its build status changed: partially failing to not available
tezos-rpc.7.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-rpc.7.1 on 5.0 had its build status changed: partially failing to not available
tezos-rpc.7.1 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-rpc.7.2 on 5.0 had its build status changed: partially failing to not available
tezos-rpc.7.2 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-rpc.7.3 on 5.0 had its build status changed: partially failing to not available
tezos-rpc.7.3 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-rpc.7.4 on 5.0 had its build status changed: partially failing to not available
tezos-rpc.7.4 on 5.0+alpha-repo had its build status changed: partially failing to not available
tezos-stdlib.7.0 on 5.0 had its build status changed: failing to not available
tezos-stdlib.7.0 on 5.0+alpha-repo had its build status changed: failing to not available
tezos-stdlib.7.1 on 5.0 had its build status changed: failing to not available
tezos-stdlib.7.1 on 5.0+alpha-repo had its build status changed: failing to not available
tezos-stdlib.7.2 on 5.0 had its build status changed: failing to not available
tezos-stdlib.7.2 on 5.0+alpha-repo had its build status changed: failing to not available
tezos-stdlib.7.3 on 5.0 had its build status changed: failing to not available
tezos-stdlib.7.3 on 5.0+alpha-repo had its build status changed: failing to not available
tezos-stdlib.7.4 on 5.0 had its build status changed: failing to not available
tezos-stdlib.7.4 on 5.0+alpha-repo had its build status changed: failing to not available
tyxml-jsx.4.5.0 on 5.0 had its build status changed: partially failing to not available
tyxml-jsx.4.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tyxml-ppx.4.5.0 on 5.0 had its build status changed: partially failing to not available
tyxml-ppx.4.5.0 on 5.0+alpha-repo had its build status changed: partially failing to not available
tyxml-syntax.4.5.0 on 5.0 had its build status changed: failing to not available
tyxml-syntax.4.5.0 on 5.0+alpha-repo had its build status changed: failing to not available
uecc.0.2 on 5.0+alpha-repo had its build status changed: passing to not available
uint.1.2.1 on 5.0 had its build status changed: failing to not available
uint.1.2.1 on 5.0+alpha-repo had its build status changed: failing to not available
vhd-format-lwt.0.12.3 on 5.0 had its build status changed: passing to not available
vhd-format-lwt.0.12.3 on 5.0+alpha-repo had its build status changed: passing to not available
xenstore.2.1.0 on 5.0 had its build status changed: failing to not available
xenstore.2.1.0 on 5.0+alpha-repo had its build status changed: failing to not available
z3.4.8.13 on 5.0 had its build status changed: failing to not available
z3.4.8.13 on 5.0+alpha-repo had its build status changed: failing to not available
z3_tptp.4.8.13 on 5.0 had its build status changed: partially failing to not available
z3_tptp.4.8.13 on 5.0+alpha-repo had its build status changed: partially failing to not available

Packages now failing with an internal failure:

0install.2.16 on 4.03 had its build status changed: not available to internal failure
amf.0.1.0 on 4.03 had its build status changed: failing to internal failure
amf.0.1.0 on 4.04 had its build status changed: passing to internal failure
amf.0.1.0 on 4.05 had its build status changed: passing to internal failure
amf.0.1.2 on 4.04 had its build status changed: passing to internal failure
amf.0.1.2 on 4.05 had its build status changed: passing to internal failure
amf.0.1.2 on 4.06 had its build status changed: passing to internal failure
amf.0.1.2 on 4.07 had its build status changed: passing to internal failure
amf.0.1.2 on 4.08 had its build status changed: passing to internal failure
amf.0.1.2 on 4.09 had its build status changed: passing to internal failure
coccinelle.1.0.9 on 4.05 had its build status changed: passing to internal failure
cohttp-lwt-jsoo.2.5.4 on 4.11 had its build status changed: passing to internal failure
cohttp-lwt-jsoo.2.5.5 on 4.12 had its build status changed: passing to internal failure
cohttp-lwt-jsoo.2.5.6 on 5.0+alpha-repo had its build status changed: passing to internal failure
cohttp-lwt-jsoo.5.0.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
cohttp-lwt-unix.1.2.0 on 4.06 had its build status changed: passing to internal failure
cohttp-lwt-unix.2.2.0 on 4.07 had its build status changed: passing to internal failure
cohttp-lwt-unix.2.3.0 on 4.07 had its build status changed: passing to internal failure
cohttp-lwt-unix.2.4.0 on 4.11 had its build status changed: passing to internal failure
cohttp-lwt-unix.2.5.0 on 4.13 had its build status changed: passing to internal failure
cohttp-lwt-unix.2.5.2-1 on 5.0+alpha-repo had its build status changed: passing to internal failure
cohttp-lwt-unix.2.5.4 on 4.14+alpha-repo had its build status changed: passing to internal failure
cohttp-lwt-unix.2.5.5 on 4.14+alpha-repo had its build status changed: passing to internal failure
cohttp-lwt-unix.2.5.6 on 5.0+alpha-repo had its build status changed: passing to internal failure
cohttp-lwt-unix.5.0.0 on 5.0+alpha-repo had its build status changed: passing to internal failure
combine.0.6 on 4.06 had its build status changed: passing to internal failure
combine.0.6 on 4.09 had its build status changed: passing to internal failure
combine.0.6 on 4.13 had its build status changed: passing to internal failure
cowabloga.0.0.4 on 4.02 had its build status changed: partially failing to internal failure
dolmen.0.4 on 4.07 had its build status changed: passing to internal failure
dolog.0.3 on 4.04 had its build status changed: passing to internal failure
dolog.1.1 on 4.04 had its build status changed: passing to internal failure
dolog.2.0 on 4.05 had its build status changed: passing to internal failure
dolog.2.0 on 4.08 had its build status changed: passing to internal failure
dolog.4.0.0 on 5.0 had its build status changed: passing to internal failure
domain-name.0.1.1 on 4.10 had its build status changed: passing to internal failure
domain-name.0.1.1 on 4.13 had its build status changed: passing to internal failure
domain-name.0.2.0 on 4.10 had its build status changed: passing to internal failure
domain-name.0.2.0 on 4.14 had its build status changed: passing to internal failure
domain-name.0.2.0 on 5.0 had its build status changed: passing to internal failure
dune-build-info.2.8.2 on 4.11 had its build status changed: passing to internal failure
dune-rpc.3.3.0 on 5.0 had its build status changed: passing to internal failure
dune.1.7.2 on 4.04 had its build status changed: passing to internal failure
dune.1.7.3 on 4.03 had its build status changed: passing to internal failure
dune.1.7.3 on 4.05 had its build status changed: passing to internal failure
dune.1.7.3 on 4.06 had its build status changed: passing to internal failure
dune.1.7.3 on 4.07 had its build status changed: passing to internal failure
dune.1.8.0 on 4.02 had its build status changed: passing to internal failure
dune.1.8.0 on 4.04 had its build status changed: passing to internal failure
dune.1.8.0 on 4.05 had its build status changed: passing to internal failure
dune.1.8.0 on 4.08 had its build status changed: passing to internal failure
dune.1.8.1 on 4.03 had its build status changed: passing to internal failure
dune.1.8.1 on 4.04 had its build status changed: passing to internal failure
dune.1.8.1 on 4.06 had its build status changed: passing to internal failure
dune.1.8.1 on 4.07 had its build status changed: passing to internal failure
dune.1.8.1 on 4.08 had its build status changed: passing to internal failure
dune.1.8.2 on 4.02 had its build status changed: passing to internal failure
dune.1.8.2 on 4.03 had its build status changed: passing to internal failure
dune.1.8.2 on 4.04 had its build status changed: passing to internal failure
dune.1.8.2 on 4.05 had its build status changed: passing to internal failure
dune.1.8.2 on 4.06 had its build status changed: passing to internal failure
dune.1.8.2 on 4.07 had its build status changed: passing to internal failure
dune.1.8.2 on 4.08 had its build status changed: passing to internal failure
dune.1.9.0 on 4.02 had its build status changed: passing to internal failure
dune.1.9.0 on 4.04 had its build status changed: passing to internal failure
dune.1.9.0 on 4.05 had its build status changed: passing to internal failure
dune.1.9.0 on 4.08 had its build status changed: passing to internal failure
dune.1.9.1 on 4.02 had its build status changed: passing to internal failure
dune.1.9.1 on 4.03 had its build status changed: passing to internal failure
dune.1.9.1 on 4.04 had its build status changed: passing to internal failure
dune.1.9.1 on 4.05 had its build status changed: passing to internal failure
dune.1.9.1 on 4.07 had its build status changed: passing to internal failure
dune.1.9.1 on 4.08 had its build status changed: passing to internal failure
dyn.3.2.0 on 4.12 had its build status changed: passing to internal failure
earley-ocaml.1.1.0 on 4.05 had its build status changed: passing to internal failure
earley.1.0.2 on 4.10 had its build status changed: passing to internal failure
earley.2.0.0 on 4.06 had its build status changed: passing to internal failure
ffmpeg-av.1.0.0 on 4.13 had its build status changed: passing 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 on 5.0 had its build status changed: passing to internal failure
ffmpeg-av.1.0.0~rc1 on 4.10 had its build status changed: passing to internal failure
ffmpeg-avcodec.1.0.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
ffmpeg-avcodec.1.0.0 on 5.0+alpha-repo had its build status changed: passing to internal failure
ffmpeg-avdevice.1.0.0 on 4.14 had its build status changed: passing to internal failure
ffmpeg-avdevice.1.0.0 on 5.0+alpha-repo had its build status changed: passing to internal failure
ffmpeg-avdevice.1.0.0~rc1 on 4.08 had its build status changed: passing to internal failure
ffmpeg-avdevice.1.0.0~rc1 on 4.09 had its build status changed: passing to internal failure
ffmpeg-avfilter.1.0.0 on 4.12 had its build status changed: passing to internal failure
ffmpeg-avfilter.1.0.0 on 4.14 had its build status changed: passing to internal failure
ffmpeg-avfilter.1.0.0 on 5.0 had its build status changed: passing to internal failure
ffmpeg-avfilter.1.0.0~rc1 on 4.08 had its build status changed: passing to internal failure
ffmpeg-avutil.1.0.0 on 4.10 had its build status changed: passing to internal failure
ffmpeg-avutil.1.0.0 on 5.0 had its build status changed: passing to internal failure
ffmpeg-avutil.1.0.0~rc1 on 4.14+alpha-repo had its build status changed: passing to internal failure
ffmpeg-avutil.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: passing to internal failure
ffmpeg-swresample.1.0.0 on 4.09 had its build status changed: passing to internal failure
ffmpeg-swresample.1.0.0 on 4.10 had its build status changed: passing to internal failure
ffmpeg-swresample.1.0.0 on 4.12 had its build status changed: passing to internal failure
ffmpeg-swresample.1.0.0~rc1 on 4.13 had its build status changed: passing to internal failure
ffmpeg-swresample.1.0.0~rc1 on 4.14 had its build status changed: passing to internal failure
ffmpeg-swresample.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: passing to internal failure
ffmpeg-swscale.1.0.0 on 4.08 had its build status changed: passing to internal failure
ffmpeg-swscale.1.0.0 on 4.10 had its build status changed: passing to internal failure
ffmpeg-swscale.1.0.0~rc1 on 4.12 had its build status changed: passing to internal failure
ffmpeg-swscale.1.0.0~rc1 on 4.14 had its build status changed: passing to internal failure
ffmpeg-swscale.1.0.0~rc1 on 5.0 had its build status changed: passing to internal failure
ffmpeg-swscale.1.0.0~rc1 on 5.0+alpha-repo had its build status changed: passing to internal failure
ffmpeg.1.0.0 on 4.10 had its build status changed: passing to internal failure
ffmpeg.1.0.0 on 4.12 had its build status changed: passing to internal failure
ffmpeg.1.0.0 on 4.13 had its build status changed: passing to internal failure
ffmpeg.1.0.0~rc1 on 4.13 had its build status changed: passing to internal failure
glical.0.0.2 on 4.05 had its build status changed: passing to internal failure
glical.0.0.3 on 4.07 had its build status changed: passing to internal failure
glical.0.0.4 on 4.06 had its build status changed: passing to internal failure
glical.0.0.5 on 4.02 had its build status changed: passing to internal failure
glical.0.0.5 on 4.14 had its build status changed: passing to internal failure
glical.0.0.7 on 4.11 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
http-cookie.3.0.0 on 4.12 had its build status changed: passing to internal failure
integration1d.0.4 on 4.04 had its build status changed: passing to internal failure
integration1d.0.4.1 on 4.03 had its build status changed: passing to internal failure
irmin-mirage-git.2.3.0 on 4.09 had its build status changed: partially failing to internal failure
mirage-conduit.2.2.0 on 4.02 had its build status changed: passing to internal failure
mirage-git.1.6.0 on 4.04 had its build status changed: partially failing to internal failure
mparser.1.0.1 on 4.05 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
mparser.1.2.1 on 4.09 had its build status changed: passing to internal failure
mparser.1.2.1 on 4.14 had its build status changed: passing to internal failure
mpp.0.1.5 on 4.04 had its build status changed: passing to internal failure
mpp.0.3.0 on 4.05 had its build status changed: passing to internal failure
ocamlformat.0.3 on 4.06 had its build status changed: passing to internal failure
ocamlog.0.1 on 4.05 had its build status changed: passing to internal failure
ocamlog.0.1 on 4.06 had its build status changed: passing to internal failure
ocamlog.0.1 on 4.08 had its build status changed: passing to internal failure
ocamlog.0.1 on 4.09 had its build status changed: passing to internal failure
ocamlog.0.2 on 4.06 had its build status changed: passing to internal failure
ocamlog.0.2 on 4.07 had its build status changed: passing to internal failure
ocamlog.0.2 on 4.09 had its build status changed: passing to internal failure
ocamlog.0.2 on 4.10 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
omd.0.6.4 on 4.02 had its build status changed: passing to internal failure
opam-query.1.0 on 4.05 had its build status changed: passing to internal failure
opam-query.1.1 on 4.05 had its build status changed: passing to internal failure
opam-sync-github-prs.1.0.0 on 4.05 had its build status changed: not available to internal failure
opam2web.1.4.0 on 4.03 had its build status changed: partially failing to internal failure
osdp.0.5.4 on 4.03 had its build status changed: passing to internal failure
osdp.0.5.4 on 4.04 had its build status changed: passing to internal failure
osdp.0.5.4 on 4.05 had its build status changed: passing to internal failure
osdp.0.6.0 on 4.02 had its build status changed: passing to internal failure
osdp.0.6.0 on 4.07 had its build status changed: passing to internal failure
osdp.0.6.0 on 4.08 had its build status changed: passing to internal failure
osdp.0.6.0 on 4.09 had its build status changed: passing to internal failure
osdp.0.6.0 on 4.10 had its build status changed: passing to internal failure
osdp.0.6.0 on 4.11 had its build status changed: passing to internal failure
osdp.0.6.0 on 4.13 had its build status changed: passing 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.03 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
osdp.1.0.0 on 4.11 had its build status changed: passing to internal failure
osdp.1.0.0 on 4.12 had its build status changed: passing to internal failure
osdp.1.0.0 on 4.14 had its build status changed: passing to internal failure
osdp.1.0.0 on 5.0 had its build status changed: failing to internal failure
pa_comprehension.0.4 on 4.05 had its build status changed: passing to internal failure
pa_comprehension.0.4 on 4.06 had its build status changed: passing to internal failure
pa_comprehension.0.4 on 4.09 had its build status changed: passing to internal failure
pa_qualified.0.5 on 4.04 had its build status changed: passing to internal failure
pa_qualified.0.6 on 4.07 had its build status changed: passing to internal failure
pa_solution.0.6 on 4.02 had its build status changed: passing to internal failure
pa_solution.0.7 on 4.07 had its build status changed: passing to internal failure
pa_where.0.4 on 4.02 had its build status changed: passing to internal failure
pa_where.0.4 on 5.0+alpha-repo had its build status changed: failing to internal failure
pds.3.0.2 on 4.03 had its build status changed: passing to internal failure
pds.3.1.0 on 4.14 had its build status changed: passing to internal failure
pds.3.1.1 on 5.0+alpha-repo had its build status changed: passing to internal failure
pds.5.15 on 4.08 had its build status changed: passing to internal failure
pecu.0.6 on 4.10 had its build status changed: passing to internal failure
pf-qubes.0.1.0 on 4.04 had its build status changed: not available to internal failure
pfff.0.29 on 4.14 had its build status changed: not available to internal failure
pfff.0.37.4 on 4.04 had its build status changed: passing to internal failure
pgocaml.4.0 on 4.05 had its build status changed: not available to internal failure
pgx_async.1.0 on 4.10 had its build status changed: passing to internal failure
pgx_lwt.2.1 on 4.09 had its build status changed: passing to internal failure
pgx_lwt.2.2 on 5.0+alpha-repo is now installable. Current state is: internal failure
pgx_lwt_mirage.2.0 on 4.08 had its build status changed: passing to internal failure
pgx_lwt_mirage.2.1 on 4.14+alpha-repo had its build status changed: passing to internal failure
pgx_unix.0.1 on 4.09 had its build status changed: passing to internal failure
pgx_unix.2.1 on 4.06 had its build status changed: not available to internal failure
pgx_unix.2.2 on 4.10 is now installable. Current state is: internal failure
pgx_value_core.1.0 on 4.14+alpha-repo had its build status changed: passing to internal failure
pgx_value_core.2.1 on 4.04 had its build status changed: not available to internal failure
pla.1.4 on 4.06 had its build status changed: passing to internal failure
proverif.1.98 on 4.02 had its build status changed: passing 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
safepass.1.3 on 4.02 had its build status changed: passing to internal failure
slacko.0.10.0 on 4.05 had its build status changed: failing to internal failure
tcpip.2.8.1 on 4.04 had its build status changed: passing to internal failure
tcpip.3.7.4 on 4.05 had its build status changed: passing to internal failure
tcpip.3.7.4 on 4.07 had its build status changed: passing to internal failure
tezos-protocol-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to internal failure
tezos-protocol-007-PsDELPH1.9.3 on 4.10 had its build status changed: passing to internal failure
tezos-protocol-008-PtEdo2Zk.12.3 on 4.12 had its build status changed: passing to internal failure
torch.0.2 on 5.0 had its build status changed: not available to internal failure
torch.0.3 on 5.0 had its build status changed: not available to internal failure
z3.4.10.2 on 4.13 had its build status changed: passing to internal failure
z3.4.8.11 on 4.10 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.14 had its build status changed: passing to internal failure
z3.4.8.7 on 4.03 had its build status changed: passing to internal failure
z3.4.8.8 on 4.10 had its build status changed: passing to internal failure
z3.4.9.1 on 4.08 had its build status changed: passing to internal failure
z3_tptp.4.10.1 on 4.14+alpha-repo is now installable. Current state is: internal failure
z3_tptp.4.8.13 on 4.13 had its build status changed: passing to internal failure
z3_tptp.4.9.1 on 4.11 is now installable. Current state is: internal failure
zlist.0.1.2 on 4.09 had its build status changed: passing to internal failure
zlist.0.1.2 on 4.11 had its build status changed: passing to internal failure
zlist.0.1.2 on 4.14 had its build status changed: passing to internal failure
zlist.0.1.2 on 4.14+alpha-repo had its build status changed: passing to internal failure
zlist.0.4.0 on 4.03 had its build status changed: passing to internal failure
zlist.0.4.0 on 4.07 had its build status changed: passing to internal failure
zlist.0.4.0 on 4.12 had its build status changed: passing to internal failure
zlist.0.4.0 on 5.0+alpha-repo had its build status changed: passing to internal failure

Packages now 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
OCanren-ppx.0.3.0 on 5.0 had its build status changed: not available to 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 4.08 is now installable. Current state is: passing
SZXX.2.3.0 on 4.09 is now installable. Current state is: passing
SZXX.2.3.0 on 4.10 is now installable. Current state is: passing
SZXX.2.3.0 on 4.11 is now installable. Current state is: passing
SZXX.2.3.0 on 4.12 is now installable. Current state is: passing
SZXX.2.3.0 on 4.13 is now installable. Current state is: passing
SZXX.2.3.0 on 4.14 is now installable. Current state is: passing
SZXX.2.3.0 on 4.14+alpha-repo is now installable. Current state is: passing
SZXX.2.3.0 on 5.0 is now installable. Current state is: passing
SZXX.2.3.0 on 5.0+alpha-repo is now installable. Current state is: passing
Snowflake.0.02.03 on 4.13 is now installable. Current state is: passing
Snowflake.0.02.03 on 4.14 is now installable. Current state is: passing
Snowflake.0.02.03 on 4.14+alpha-repo is now installable. Current state is: passing
Snowflake.0.02.03 on 5.0 is now installable. Current state is: passing
Snowflake.0.02.03 on 5.0+alpha-repo is now installable. Current state is: passing
abstract_algebra.v0.15.0 on 5.0 had its build status changed: not available to passing
accessor.v0.15.0 on 5.0 had its build status changed: not available to passing
accessor_async.v0.15.0 on 5.0 had its build status changed: not available to passing
accessor_base.v0.15.0 on 5.0 had its build status changed: not available to passing
accessor_core.v0.15.0 on 5.0 had its build status changed: not available to passing
acgtk.1.5.1 on 5.0 had its build status changed: failing to passing
acgtk.1.5.1 on 5.0+alpha-repo had its build status changed: failing to passing
acgtk.1.5.2 on 5.0 had its build status changed: failing to passing
acgtk.1.5.2 on 5.0+alpha-repo had its build status changed: failing to passing
acgtk.1.5.3 on 5.0 had its build status changed: failing to passing
acgtk.1.5.3 on 5.0+alpha-repo had its build status changed: failing to passing
aches-lwt.1.0.0 on 4.08 is now installable. Current state is: passing
aches-lwt.1.0.0 on 4.09 is now installable. Current state is: passing
aches-lwt.1.0.0 on 4.10 is now installable. Current state is: passing
aches-lwt.1.0.0 on 4.11 is now installable. Current state is: passing
aches-lwt.1.0.0 on 4.12 is now installable. Current state is: passing
aches-lwt.1.0.0 on 4.13 is now installable. Current state is: passing
aches-lwt.1.0.0 on 4.14 is now installable. Current state is: passing
aches-lwt.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
aches-lwt.1.0.0 on 5.0 is now installable. Current state is: passing
aches-lwt.1.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
aches.1.0.0 on 4.08 is now installable. Current state is: passing
aches.1.0.0 on 4.09 is now installable. Current state is: passing
aches.1.0.0 on 4.10 is now installable. Current state is: passing
aches.1.0.0 on 4.11 is now installable. Current state is: passing
aches.1.0.0 on 4.12 is now installable. Current state is: passing
aches.1.0.0 on 4.13 is now installable. Current state is: passing
aches.1.0.0 on 4.14 is now installable. Current state is: passing
aches.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
aches.1.0.0 on 5.0 is now installable. Current state is: passing
aches.1.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
acpc.1.0 on 4.02 had its build status changed: internal failure to passing
acpc.1.0 on 4.03 had its build status changed: internal failure to passing
acpc.1.0 on 4.04 had its build status changed: internal failure to passing
acpc.1.0 on 4.05 had its build status changed: internal failure to passing
acpc.1.1 on 4.02 had its build status changed: internal failure to passing
acpc.1.1 on 4.03 had its build status changed: internal failure to passing
acpc.1.1 on 4.04 had its build status changed: internal failure to passing
acpc.1.1 on 4.05 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.02 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.03 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.04 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.05 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.06 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.07 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.08 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.09 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.10 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.11 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.12 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.13 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.14 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.14+alpha-repo had its build status changed: internal failure to passing
acpc.1.2 on 4.02 had its build status changed: internal failure to passing
acpc.1.2 on 4.03 had its build status changed: internal failure to passing
acpc.1.2 on 4.04 had its build status changed: internal failure to passing
acpc.1.2 on 4.05 had its build status changed: internal failure to passing
acpc.1.2.1 on 4.02 had its build status changed: internal failure to passing
acpc.1.2.1 on 4.03 had its build status changed: internal failure to passing
acpc.1.2.1 on 4.04 had its build status changed: internal failure to passing
acpc.1.2.1 on 4.05 had its build status changed: internal failure to passing
acpc.1.2.2 on 4.02 had its build status changed: internal failure to passing
acpc.1.2.2 on 4.03 had its build status changed: internal failure to passing
acpc.1.2.2 on 4.04 had its build status changed: internal failure to passing
acpc.1.2.2 on 4.05 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.02 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.03 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.04 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.05 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.06 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.07 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.08 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.09 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.10 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.11 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.12 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.13 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.14 had its build status changed: internal failure to passing
acpc.1.2.3 on 4.14+alpha-repo had its build status changed: internal failure 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
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
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.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.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 4.14+alpha-repo had its build status changed: internal failure to passing
archetype.1.3.4 on 4.08 is now installable. Current state is: passing
archetype.1.3.4 on 4.09 is now installable. Current state is: passing
archetype.1.3.4 on 4.10 is now installable. Current state is: passing
archetype.1.3.4 on 4.11 is now installable. Current state is: passing
archetype.1.3.4 on 4.12 is now installable. Current state is: passing
archetype.1.3.4 on 4.13 is now installable. Current state is: passing
archetype.1.3.4 on 4.14 is now installable. Current state is: passing
archetype.1.3.4 on 4.14+alpha-repo is now installable. Current state is: passing
archetype.1.3.4 on 5.0+alpha-repo is now installable. Current state is: passing
archetype.1.3.5 on 4.08 is now installable. Current state is: passing
archetype.1.3.5 on 4.09 is now installable. Current state is: passing
archetype.1.3.5 on 4.10 is now installable. Current state is: passing
archetype.1.3.5 on 4.11 is now installable. Current state is: passing
archetype.1.3.5 on 4.12 is now installable. Current state is: passing
archetype.1.3.5 on 4.13 is now installable. Current state is: passing
archetype.1.3.5 on 4.14 is now installable. Current state is: passing
archetype.1.3.5 on 4.14+alpha-repo is now installable. Current state is: passing
archetype.1.3.5 on 5.0+alpha-repo is now installable. Current state is: passing
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+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
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: partially failing to passing
aws-autoscaling.1.2 on 5.0 had its build status changed: partially failing to passing
aws-autoscaling.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-cloudformation.1.2 on 5.0 had its build status changed: partially failing to passing
aws-cloudformation.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-cloudtrail.1.2 on 5.0 had its build status changed: partially failing to passing
aws-cloudtrail.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-cloudwatch.1.2 on 5.0 had its build status changed: partially failing to passing
aws-cloudwatch.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-ec2.1.2 on 5.0 had its build status changed: partially failing to passing
aws-ec2.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-elasticache.1.2 on 5.0 had its build status changed: partially failing to passing
aws-elasticache.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-elasticloadbalancing.1.2 on 5.0 had its build status changed: partially failing to passing
aws-elasticloadbalancing.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-lwt.1.2 on 5.0 had its build status changed: partially failing to passing
aws-lwt.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-rds.1.2 on 5.0 had its build status changed: partially failing to passing
aws-rds.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-route53.1.2 on 5.0 had its build status changed: partially failing to passing
aws-route53.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-s3-async.4.8.0 on 4.08 is now installable. Current state is: passing
aws-s3-async.4.8.0 on 4.09 is now installable. Current state is: passing
aws-s3-async.4.8.0 on 4.10 is now installable. Current state is: passing
aws-s3-async.4.8.0 on 4.11 is now installable. Current state is: passing
aws-s3-async.4.8.0 on 4.12 is now installable. Current state is: passing
aws-s3-async.4.8.0 on 4.13 is now installable. Current state is: passing
aws-s3-async.4.8.0 on 4.14 is now installable. Current state is: passing
aws-s3-async.4.8.0 on 4.14+alpha-repo is now installable. Current state is: passing
aws-s3-lwt.4.8.0 on 4.08 is now installable. Current state is: passing
aws-s3-lwt.4.8.0 on 4.09 is now installable. Current state is: passing
aws-s3-lwt.4.8.0 on 4.10 is now installable. Current state is: passing
aws-s3-lwt.4.8.0 on 4.11 is now installable. Current state is: passing
aws-s3-lwt.4.8.0 on 4.12 is now installable. Current state is: passing
aws-s3-lwt.4.8.0 on 4.13 is now installable. Current state is: passing
aws-s3-lwt.4.8.0 on 4.14 is now installable. Current state is: passing
aws-s3-lwt.4.8.0 on 4.14+alpha-repo is now installable. Current state is: passing
aws-s3.4.8.0 on 4.08 is now installable. Current state is: passing
aws-s3.4.8.0 on 4.09 is now installable. Current state is: passing
aws-s3.4.8.0 on 4.10 is now installable. Current state is: passing
aws-s3.4.8.0 on 4.11 is now installable. Current state is: passing
aws-s3.4.8.0 on 4.12 is now installable. Current state is: passing
aws-s3.4.8.0 on 4.13 is now installable. Current state is: passing
aws-s3.4.8.0 on 4.14 is now installable. Current state is: passing
aws-s3.4.8.0 on 4.14+alpha-repo is now installable. Current state is: passing
aws-sdb.1.2 on 5.0 had its build status changed: partially failing to passing
aws-sdb.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-sqs.1.2 on 5.0 had its build status changed: partially failing to passing
aws-sqs.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-ssm.1.2 on 5.0 had its build status changed: partially failing to passing
aws-ssm.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws-sts.1.2 on 5.0 had its build status changed: partially failing to passing
aws-sts.1.2 on 5.0+alpha-repo had its build status changed: partially failing to passing
aws.1.2 on 5.0 had its build status changed: partially failing to passing
aws.1.2 on 5.0+alpha-repo had its build status changed: partially failing 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
bap-byteweight.1.3.0 on 4.02 had its build status changed: partially failing to passing
bap-demangle.1.4.0 on 4.05 had its build status changed: internal failure to passing
bap-demangle.1.5.0 on 4.05 had its build status changed: internal failure to passing
bap-demangle.1.6.0 on 4.07 had its build status changed: internal failure to passing
bap-demangle.2.1.0 on 4.09 had its build status changed: internal failure to passing
bap-phoenix.1.2.0 on 4.02 had its build status changed: partially failing to passing
bap-warn-unused.1.3.0 on 4.02 had its build status changed: partially failing to passing
base.v0.15.1 on 4.10 is now installable. Current state is: passing
base.v0.15.1 on 4.11 is now installable. Current state is: passing
base.v0.15.1 on 4.12 is now installable. Current state is: passing
base.v0.15.1 on 4.13 is now installable. Current state is: passing
base.v0.15.1 on 4.14 is now installable. Current state is: passing
base.v0.15.1 on 4.14+alpha-repo is now installable. Current state is: passing
base.v0.15.1 on 5.0 is now installable. Current state is: passing
base.v0.15.1 on 5.0+alpha-repo is now installable. Current state is: passing
base_bigstring.v0.15.0 on 5.0 had its build status changed: not available to passing
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
bechamel-notty.0.1.0 on 4.14 had its build status changed: not available to passing
bechamel-notty.0.1.0 on 4.14+alpha-repo had its build status changed: failing to passing
bechamel-notty.0.2.0 on 4.14 had its build status changed: not available to passing
bechamel-notty.0.2.0 on 4.14+alpha-repo had its build status changed: failing to passing
bechamel-notty.0.3.0 on 4.14 had its build status changed: not available to passing
bechamel-notty.0.3.0 on 4.14+alpha-repo had its build status changed: failing to passing
bechamel-notty.0.3.0 on 5.0 had its build status changed: not available to passing
bechamel-notty.0.3.0 on 5.0+alpha-repo had its build status changed: failing to passing
benchpress-server.0.1 on 4.03 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.04 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.05 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.06 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.07 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.08 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.09 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.10 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.11 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.12 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.13 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.14 had its build status changed: internal failure to passing
benchpress-server.0.1 on 4.14+alpha-repo had its build status changed: internal failure to passing
benchpress.0.1 on 4.03 had its build status changed: internal failure to passing
benchpress.0.1 on 4.04 had its build status changed: internal failure to passing
benchpress.0.1 on 4.05 had its build status changed: internal failure to passing
benchpress.0.1 on 4.06 had its build status changed: internal failure to passing
benchpress.0.1 on 4.07 had its build status changed: internal failure to passing
benchpress.0.1 on 4.08 had its build status changed: internal failure to passing
benchpress.0.1 on 4.09 had its build status changed: internal failure to passing
benchpress.0.1 on 4.10 had its build status changed: internal failure to passing
benchpress.0.1 on 4.11 had its build status changed: internal failure to passing
benchpress.0.1 on 4.12 had its build status changed: internal failure to passing
benchpress.0.1 on 4.13 had its build status changed: internal failure to passing
benchpress.0.1 on 4.14 had its build status changed: internal failure to passing
benchpress.0.1 on 4.14+alpha-repo had its build status changed: internal failure to passing
bigdecimal.v0.15.0 on 5.0 had its build status changed: not available 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
binaryen.0.16.0 on 4.12 had its build status changed: internal failure to passing
binsec.0.6.0 on 4.13 is now installable. Current state is: passing
binsec.0.6.0 on 4.14 is now installable. Current state is: passing
binsec.0.6.0 on 4.14+alpha-repo is now installable. Current state is: passing
binsec.0.6.1 on 4.09 is now installable. Current state is: passing
binsec.0.6.1 on 4.10 is now installable. Current state is: passing
binsec.0.6.1 on 4.11 is now installable. Current state is: passing
binsec.0.6.1 on 4.12 is now installable. Current state is: passing
binsec.0.6.1 on 4.13 is now installable. Current state is: passing
binsec.0.6.1 on 4.14 is now installable. Current state is: passing
binsec.0.6.1 on 4.14+alpha-repo is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 4.08 is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 4.09 is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 4.10 is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 4.11 is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 4.12 is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 4.13 is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 4.14 is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 4.14+alpha-repo is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 5.0 is now installable. Current state is: passing
bitpack_serializer.0.1.0 on 5.0+alpha-repo is now installable. Current state is: passing
blake3.0.3 on 4.09 is now installable. Current state is: passing
blake3.0.3 on 4.10 is now installable. Current state is: passing
blake3.0.3 on 4.11 is now installable. Current state is: passing
blake3.0.3 on 4.12 is now installable. Current state is: passing
blake3.0.3 on 4.13 is now installable. Current state is: passing
blake3.0.3 on 4.14 is now installable. Current state is: passing
blake3.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
bls12-381-hash.0.0.2 on 4.12 is now installable. Current state is: passing
bls12-381-hash.0.0.2 on 4.13 is now installable. Current state is: passing
bls12-381-hash.0.0.2 on 4.14 is now installable. Current state is: passing
bls12-381-hash.0.0.2 on 4.14+alpha-repo is now installable. Current state is: passing
bls12-381-hash.0.0.2 on 5.0 is now installable. Current state is: passing
bls12-381-hash.0.0.2 on 5.0+alpha-repo is now installable. Current state is: passing
bls12-381-hash.0.0.3 on 4.12 is now installable. Current state is: passing
bls12-381-hash.0.0.3 on 4.13 is now installable. Current state is: passing
bls12-381-hash.0.0.3 on 4.14 is now installable. Current state is: passing
bls12-381-hash.0.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
bls12-381-hash.0.0.3 on 5.0 is now installable. Current state is: passing
bls12-381-hash.0.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 4.08 is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 4.09 is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 4.10 is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 4.11 is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 4.12 is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 4.13 is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 4.14 is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 4.14+alpha-repo is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 5.0 is now installable. Current state is: passing
bls12-381-signature.1.0.0 on 5.0+alpha-repo is now installable. Current state is: passing
bogue.20221002 on 4.08 is now installable. Current state is: passing
bogue.20221002 on 4.09 is now installable. Current state is: passing
bogue.20221002 on 4.10 is now installable. Current state is: passing
bogue.20221002 on 4.11 is now installable. Current state is: passing
bogue.20221002 on 4.12 is now installable. Current state is: passing
bogue.20221002 on 4.13 is now installable. Current state is: passing
bogue.20221002 on 4.14 is now installable. Current state is: passing
bogue.20221002 on 4.14+alpha-repo is now installable. Current state is: passing
bogue.20221002 on 5.0 is now installable. Current state is: passing
bogue.20221002 on 5.0+alpha-repo is now installable. Current state is: passing
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 4.08 is now installable. Current state is: passing
box.1.2.0 on 4.09 is now installable. Current state is: passing
box.1.2.0 on 4.10 is now installable. Current state is: passing
box.1.2.0 on 4.11 is now installable. Current state is: passing
box.1.2.0 on 4.12 is now installable. Current state is: passing
box.1.2.0 on 4.13 is now installable. Current state is: passing
box.1.2.0 on 4.14 is now installable. Current state is: passing
box.1.2.0 on 4.14+alpha-repo is now installable. Current state is: passing
box.1.2.0 on 5.0 is now installable. Current state is: passing
box.1.2.0 on 5.0+alpha-repo is now installable. Current state is: passing
brr-lwd.0.3 on 4.08 is now installable. Current state is: passing
brr-lwd.0.3 on 4.09 is now installable. Current state is: passing
brr-lwd.0.3 on 4.10 is now installable. Current state is: passing
brr-lwd.0.3 on 4.11 is now installable. Current state is: passing
brr-lwd.0.3 on 4.12 is now installable. Current state is: passing
brr-lwd.0.3 on 4.13 is now installable. Current state is: passing
brr-lwd.0.3 on 4.14 is now installable. Current state is: passing
brr-lwd.0.3 on 4.14+alpha-repo is now installable. Current state is: passing
brr-lwd.0.3 on 5.0+alpha-repo is now installable. Current state is: passing
bsdowl.3.0.0-20150401 on 4.02 had its build status changed: internal failure to passing
bsdowl.3.0.0-20150401 on 4.07 had its build status changed: internal failure to passing
bson.0.89.0 on 4.02 had its build status changed: internal failure to passing
bson.0.89.1 on 4.05 had its build status changed: internal failure to passing
bson2.0.0.1 on 4.08 had its build status changed: internal failure to passing
bst.1.0.1 on 4.07 had its build status changed: internal failure 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
bytebuffer.0.0.2 on 5.0 had its build status changed: not available to passing
ca-certs-nss.3.57 on 4.14+alpha-repo had its build status changed: internal failure to passing
ca-certs-nss.3.59 on 5.0+alpha-repo had its build status changed: internal failure to passing
ca-certs-nss.3.63.1 on 4.08 had its build status changed: internal failure to passing
ca-certs-nss.3.64 on 4.08 had its build status changed: internal failure to passing
ca-certs-nss.3.64 on 4.10 had its build status changed: internal failure to passing
ca-certs-nss.3.64 on 4.14+alpha-repo had its build status changed: internal failure to passing
ca-certs-nss.3.64 on 5.0 had its build status changed: internal failure to passing
ca-certs-nss.3.64.0.1 on 4.13 had its build status changed: internal failure to passing
ca-certs-nss.3.64.0.1 on 4.14 had its build status changed: internal failure to passing
ca-certs-nss.3.64.0.1 on 5.0 had its build status changed: internal failure to passing
ca-certs-nss.3.66 on 4.13 had its build status changed: internal failure to passing
ca-certs-nss.3.71.0.1 on 4.13 had its build status changed: internal failure to passing
ca-certs-nss.3.74 on 4.14+alpha-repo had its build status changed: internal failure to passing
ca-certs-nss.3.83 on 4.08 is now installable. Current state is: passing
ca-certs-nss.3.83 on 4.09 is now installable. Current state is: passing
ca-certs-nss.3.83 on 4.10 is now installable. Current state is: passing
ca-certs-nss.3.83 on 4.11 is now installable. Current state is: passing
ca-certs-nss.3.83 on 4.12 is now installable. Current state is: passing
ca-certs-nss.3.83 on 4.13 is now installable. Current state is: passing
ca-certs-nss.3.83 on 4.14 is now installable. Current state is: passing
ca-certs-nss.3.83 on 4.14+alpha-repo is now installable. Current state is: passing
ca-certs-nss.3.83 on 5.0 is now installable. Current state is: passing
ca-certs-nss.3.83 on 5.0+alpha-repo is now installable. Current state is: passing
ca-certs.0.1.2 on 4.07 had its build status changed: internal failure to passing
ca-certs.0.1.3 on 4.07 had its build status changed: internal failure to passing
ca-certs.0.1.3 on 4.09 had its build status changed: internal failure to passing
ca-certs.0.1.3 on 4.14+alpha-repo had its build status changed: internal failure to passing
ca-certs.0.2.0 on 4.09 had its build status changed: internal failure to passing
ca-certs.0.2.0 on 4.11 had its build status changed: internal failure to passing
ca-certs.0.2.1 on 5.0 had its build status changed: internal failure to passing
ca-certs.0.2.3 on 4.08 is now installable. Current state is: passing
ca-certs.0.2.3 on 4.09 is now installable. Current state is: passing
ca-certs.0.2.3 on 4.10 is now installable. Current state is: passing
ca-certs.0.2.3 on 4.11 is now installable. Current state is: passing
ca-certs.0.2.3 on 4.12 is now installable. Current state is: passing
ca-certs.0.2.3 on 4.13 is now installable. Current state is: passing
ca-certs.0.2.3 on 4.14 is now installable. Current state is: passing
ca-certs.0.2.3 on 4.14+alpha-repo is now installable. Current state is: passing
ca-certs.0.2.3 on 5.0 is now installable. Current state is: passing
ca-certs.0.2.3 on 5.0+alpha-repo is now installable. Current state is: passing
cactus.1.0.0 on 4.14 had its build status changed: internal failure to passing
cactus.1.0.0 on 4.14+alpha-repo had its build status changed: internal failure 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 4.03 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.04 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.05 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.06 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.07 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.08 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.09 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.10 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.11 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.12 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.13 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.14 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 4.14+alpha-repo is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 5.0 is now installable. Current state is: passing
cairo2-gtk.0.6.4 on 5.0+alpha-repo is now installable. Current state is: 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 4.03 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.04 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.05 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.06 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.07 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.08 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.09 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.10 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.11 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.12 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.13 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.14 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 4.14+alpha-repo is now installable. Current state is: passing
cairo2-pango.0.6.4 on 5.0 is now installable. Current state is: passing
cairo2-pango.0.6.4 on 5.0+alpha-repo is now installable. Current state is: passing
cairo2.0.6.4 on 4.03 is now installable. Current state is: passing
cairo2.0.6.4 on 4.04 is now installable. Current state is: passing
cairo2.0.6.4 on 4.05 is now installable. Current state is: passing
cairo2.0.6.4 on 4.06 is now installable. Current state is: passing
cairo2.0.6.4 on 4.07 is now installable. Current state is: passing
cairo2.0.6.4 on 4.08 is now installable. Current state is: passing
cairo2.0.6.4 on 4.09 is now installable. Current state is: passing
cairo2.0.6.4 on 4.10 is now installable. Current state is: passing
cairo2.0.6.4 on 4.11 is now installable. Current state is: passing
cairo2.0.6.4 on 4.12 is now installable. Current state is: passing
cairo2.0.6.4 on 4.13 is now installable. Current state is: passing
cairo2.0.6.4 on 4.14 is now installable. Current state is: passing
cairo2.0.6.4 on 4.14+alpha-repo is now installable. Current state is: passing
cairo2.0.6.4 on 5.0 is now installable. Current state is: passing
cairo2.0.6.4 on 5.0+alpha-repo is now installable. Current state is: passing
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
camels.0.0.3 on 4.14 had its build status changed: not available to passing
camels.0.0.3 on 4.14+alpha-repo had its build status changed: failing to passing
camels.0.0.3 on 5.0 had its build status changed: not available to passing
camels.0.0.3 on 5.0+alpha-repo had its build status changed: failing to passing
camels.0.0.4 on 4.14 had its build status changed: not available to passing
camels.0.0.4 on 4.14+alpha-repo had its build status changed: failing to passing
camels.0.0.4 on 5.0 had its build status changed: not available to passing
camels.0.0.4 on 5.0+alpha-repo had its build status changed: failing to passing
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
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
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: partially failing 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 4.04 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.05 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.06 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.07 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.08 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.09 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.10 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.11 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.12 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.13 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.14 is now installable. Current state is: passing
caqti-async.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
caqti-async.1.9.0 on 5.0 is now installable. Current state is: passing
caqti-async.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.07 is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.08 is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.09 is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.10 is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.11 is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.12 is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.13 is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.14 is now installable. Current state is: passing
caqti-driver-mariadb.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 4.08 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 4.09 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 4.10 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 4.11 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 4.12 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 4.13 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 4.14 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 5.0 is now installable. Current state is: passing
caqti-driver-postgresql.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
caqti-driver-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-driver-sqlite3.1.9.0 on 4.04 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.05 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.06 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.07 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.08 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.09 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.10 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.11 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.12 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.13 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.14 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 5.0 is now installable. Current state is: passing
caqti-driver-sqlite3.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.04 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.05 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.06 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.07 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.08 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.09 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.10 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.11 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.12 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.13 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.14 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 4.14+alpha-repo is now installable. Current state is: passing
caqti-lwt.1.9.0 on 5.0 is now installable. Current state is: passing
caqti-lwt.1.9.0 on 5.0+alpha-repo is now installable. Current state is: passing
caqti-type-calendar.1.0.0 on 5.0 had its build status changed: partially failing to passing
caqti-type-calendar.1.0.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
caqti-type-calendar.1.2.0 on 5.0 had its build status changed: partially failing to passing
caqti-type-calendar.1.2.0 on 5.0+alpha-repo had its build status changed: partially failing to passing
caqti-type-calendar.1.9.0 on 4.04 is now installable. Current state is: passing
caqti-type-calendar.1.9.0 on 4.05 is now installable. Current state is: passing
caqti-type-calendar.1.9.0 on 4.06 is now installable. Current state is: