opam-health-check diff

Home|Differences with the last checks|Previous runs

Differences between 94675aa and 9b339ea (git diff)

Packages now failing:

alt-ergo-parsers.2.3.0 on 4.08 had its build status changed: passing to failing
alt-ergo-parsers.2.3.0 on 4.09 had its build status changed: passing to failing
alt-ergo-parsers.2.3.0 on 4.10 had its build status changed: passing to failing
alt-ergo-parsers.2.3.0 on 4.11 had its build status changed: passing to failing
alt-ergo-parsers.2.3.0 on 4.12 had its build status changed: passing to failing
alt-ergo-parsers.2.3.0 on 4.13 had its build status changed: passing to failing
alt-ergo-parsers.2.3.0 on 4.14 had its build status changed: passing to failing
alt-ergo-parsers.2.3.1 on 4.08 had its build status changed: passing to failing
alt-ergo-parsers.2.3.1 on 4.09 had its build status changed: passing to failing
alt-ergo-parsers.2.3.1 on 4.10 had its build status changed: passing to failing
alt-ergo-parsers.2.3.1 on 4.11 had its build status changed: passing to failing
alt-ergo-parsers.2.3.1 on 4.12 had its build status changed: passing to failing
alt-ergo-parsers.2.3.1 on 4.13 had its build status changed: passing to failing
alt-ergo-parsers.2.3.1 on 4.14 had its build status changed: passing to failing
alt-ergo-parsers.2.3.2 on 4.08 had its build status changed: passing to failing
alt-ergo-parsers.2.3.2 on 4.09 had its build status changed: passing to failing
alt-ergo-parsers.2.3.2 on 4.10 had its build status changed: passing to failing
alt-ergo-parsers.2.3.2 on 4.11 had its build status changed: passing to failing
alt-ergo-parsers.2.3.2 on 4.12 had its build status changed: passing to failing
alt-ergo-parsers.2.3.2 on 4.13 had its build status changed: passing to failing
alt-ergo-parsers.2.3.2 on 4.14 had its build status changed: passing to failing
alt-ergo-parsers.2.3.3 on 4.08 had its build status changed: passing to failing
alt-ergo-parsers.2.3.3 on 4.09 had its build status changed: passing to failing
alt-ergo-parsers.2.3.3 on 4.10 had its build status changed: passing to failing
alt-ergo-parsers.2.3.3 on 4.11 had its build status changed: passing to failing
alt-ergo-parsers.2.3.3 on 4.12 had its build status changed: passing to failing
alt-ergo-parsers.2.3.3 on 4.13 had its build status changed: passing to failing
alt-ergo-parsers.2.3.3 on 4.14 had its build status changed: passing to failing
alt-ergo-parsers.2.4.0 on 4.08 had its build status changed: passing to failing
alt-ergo-parsers.2.4.0 on 4.09 had its build status changed: passing to failing
alt-ergo-parsers.2.4.0 on 4.10 had its build status changed: passing to failing
alt-ergo-parsers.2.4.0 on 4.11 had its build status changed: passing to failing
alt-ergo-parsers.2.4.0 on 4.12 had its build status changed: passing to failing
alt-ergo-parsers.2.4.0 on 4.13 had its build status changed: passing to failing
alt-ergo-parsers.2.4.0 on 4.14 had its build status changed: passing to failing
alt-ergo-parsers.2.4.1 on 4.08 had its build status changed: passing to failing
alt-ergo-parsers.2.4.1 on 4.09 had its build status changed: passing to failing
alt-ergo-parsers.2.4.1 on 4.10 had its build status changed: passing to failing
alt-ergo-parsers.2.4.1 on 4.11 had its build status changed: passing to failing
alt-ergo-parsers.2.4.1 on 4.12 had its build status changed: passing to failing
alt-ergo-parsers.2.4.1 on 4.13 had its build status changed: passing to failing
alt-ergo-parsers.2.4.1 on 4.14 had its build status changed: passing to failing
alt-ergo.1.30 on 4.08 had its build status changed: passing to failing
alt-ergo.1.30 on 4.09 had its build status changed: passing to failing
alt-ergo.1.30 on 4.10 had its build status changed: passing to failing
alt-ergo.1.30 on 4.11 had its build status changed: passing to failing
alt-ergo.1.30 on 4.12 had its build status changed: passing to failing
alt-ergo.1.30 on 4.13 had its build status changed: passing to failing
alt-ergo.1.30 on 4.14 had its build status changed: passing to failing
balancer.1.0 on 4.08 had its build status changed: passing to failing
balancer.1.0 on 4.09 had its build status changed: passing to failing
balancer.1.0 on 4.10 had its build status changed: passing to failing
balancer.1.0 on 4.11 had its build status changed: passing to failing
binaryen.0.3.0 on 4.08 had its build status changed: passing to failing
binaryen.0.3.0 on 4.09 had its build status changed: passing to failing
binaryen.0.3.0 on 4.10 had its build status changed: passing to failing
binaryen.0.3.0 on 4.11 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 4.08 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 4.09 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 4.10 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 4.11 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 4.12 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 4.13 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 4.14 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 5.0 had its build status changed: passing to failing
bitwuzla-bin.1.0.0 on 5.1 is now installable. Current state is: failing
camlmix.1.3.0 on 5.1 is now installable. Current state is: failing
camlp4.4.08+1 on 4.08 had its build status changed: passing to failing
camlp4.4.09+1 on 4.09 had its build status changed: passing to failing
camlp4.4.10+1 on 4.10 had its build status changed: passing to failing
camlp4.4.11+1 on 4.11 had its build status changed: passing to failing
camlp4.4.12+1 on 4.12 had its build status changed: passing to failing
camlp4.4.13+1 on 4.13 had its build status changed: passing to failing
camlp4.4.14+1 on 4.14 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.08 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.09 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.10 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.11 had its build status changed: passing to failing
conf-libclang.12 on 5.1 is now installable. Current state is: failing
conf-libclang.15 on 4.08 had its build status changed: passing to failing
conf-libclang.15 on 4.09 had its build status changed: passing to failing
conf-libclang.15 on 4.10 had its build status changed: passing to failing
conf-libclang.15 on 4.11 had its build status changed: passing to failing
conf-libclang.15 on 4.12 had its build status changed: passing to failing
conf-libclang.15 on 4.13 had its build status changed: passing to failing
conf-libclang.15 on 4.14 had its build status changed: passing to failing
conf-libclang.15 on 5.0 had its build status changed: passing to failing
conf-libclang.15 on 5.1 is now installable. Current state is: failing
conf-trexio.0.1 on 5.1 is now installable. Current state is: failing
datalog.0.1 on 5.1 is now installable. Current state is: failing
datalog.0.2 on 5.1 is now installable. Current state is: failing
datalog.0.3 on 5.1 is now installable. Current state is: failing
datalog.0.3.1 on 5.1 is now installable. Current state is: failing
dune.3.12.1 on 4.08 is now installable. Current state is: failing
dune.3.12.1 on 4.09 is now installable. Current state is: failing
dune.3.12.1 on 4.10 is now installable. Current state is: failing
dune.3.12.1 on 4.11 is now installable. Current state is: failing
dune.3.12.1 on 4.12 is now installable. Current state is: failing
dune.3.12.1 on 4.13 is now installable. Current state is: failing
dune.3.12.1 on 4.14 is now installable. Current state is: failing
dune.3.12.1 on 5.0 is now installable. Current state is: failing
dune.3.12.1 on 5.1 is now installable. Current state is: failing
fm-simplex-plugin.1.01 on 4.08 had its build status changed: passing to failing
gammu.0.9.3 on 5.1 is now installable. Current state is: failing
hweak.1.1 on 5.1 is now installable. Current state is: failing
labltk.8.06.11 on 4.14 had its build status changed: passing to failing
labltk.8.06.11 on 5.1 is now installable. Current state is: failing
labltk.8.06.12 on 4.14 had its build status changed: passing to failing
labltk.8.06.12 on 5.1 is now installable. Current state is: failing
learn-ocaml.0.13.0 on 4.12 had its build status changed: passing to failing
learn-ocaml.0.13.1 on 4.12 had its build status changed: passing to failing
learn-ocaml.0.14.0 on 4.12 had its build status changed: passing to failing
learn-ocaml.0.14.1 on 4.12 is now installable. Current state is: failing
learn-ocaml.0.15.0 on 4.12 is now installable. Current state is: failing
lem.2020-06-03 on 4.08 had its build status changed: passing to failing
lem.2020-06-03 on 4.09 had its build status changed: passing to failing
lem.2020-06-03 on 4.10 had its build status changed: passing to failing
lem.2020-06-03 on 4.11 had its build status changed: passing to failing
lem.2020-06-03 on 4.12 had its build status changed: passing to failing
lem.2020-06-03 on 4.13 had its build status changed: passing to failing
lem.2020-06-03 on 4.14 had its build status changed: passing to failing
lem.2022-12-10 on 4.08 is now installable. Current state is: failing
lem.2022-12-10 on 4.09 is now installable. Current state is: failing
lem.2022-12-10 on 4.10 is now installable. Current state is: failing
lem.2022-12-10 on 4.11 is now installable. Current state is: failing
lem.2022-12-10 on 4.12 is now installable. Current state is: failing
lem.2022-12-10 on 4.13 is now installable. Current state is: failing
lem.2022-12-10 on 4.14 is now installable. Current state is: failing
lem.2022-12-10 on 5.0 is now installable. Current state is: failing
lem.2022-12-10 on 5.1 is now installable. Current state is: failing
minios-xen.0.7 on 5.1 is now installable. Current state is: failing
mirage-qubes.0.6 on 4.08 had its build status changed: passing to failing
mirage-qubes.0.6 on 4.09 had its build status changed: passing to failing
mirage-qubes.0.6 on 4.10 had its build status changed: passing to failing
mirage-qubes.0.6 on 4.11 had its build status changed: passing to failing
mirage-xen-minios.0.2 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.3 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.4 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.4.1 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.4.2 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.5.0 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.6.0 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.7.0 on 5.1 is now installable. Current state is: failing
msat.0.5 on 4.08 had its build status changed: passing to failing
msat.0.5 on 4.09 had its build status changed: passing to failing
msat.0.5 on 4.10 had its build status changed: passing to failing
msat.0.5 on 4.11 had its build status changed: passing to failing
msat.0.5 on 4.12 had its build status changed: passing to failing
msat.0.5 on 4.13 had its build status changed: passing to failing
msat.0.5 on 4.14 had its build status changed: passing to failing
msat.0.5.1 on 4.08 had its build status changed: passing to failing
msat.0.5.1 on 4.09 had its build status changed: passing to failing
msat.0.5.1 on 4.10 had its build status changed: passing to failing
msat.0.5.1 on 4.11 had its build status changed: passing to failing
msat.0.5.1 on 4.12 had its build status changed: passing to failing
msat.0.5.1 on 4.13 had its build status changed: passing to failing
msat.0.5.1 on 4.14 had its build status changed: passing to failing
msat.0.6 on 4.08 had its build status changed: passing to failing
msat.0.6 on 4.09 had its build status changed: passing to failing
msat.0.6 on 4.10 had its build status changed: passing to failing
msat.0.6 on 4.11 had its build status changed: passing to failing
msat.0.6 on 4.12 had its build status changed: passing to failing
msat.0.6 on 4.13 had its build status changed: passing to failing
msat.0.6 on 4.14 had its build status changed: passing to failing
obuild.0.1.10 on 4.08 had its build status changed: passing to failing
obuild.0.1.10 on 4.09 had its build status changed: passing to failing
obuild.0.1.10 on 4.10 had its build status changed: passing to failing
obuild.0.1.10 on 4.11 had its build status changed: passing to failing
obuild.0.1.10 on 4.12 had its build status changed: passing to failing
obuild.0.1.10 on 4.13 had its build status changed: passing to failing
obuild.0.1.10 on 4.14 had its build status changed: passing to failing
obuild.0.1.11 on 4.08 is now installable. Current state is: failing
obuild.0.1.11 on 4.09 is now installable. Current state is: failing
obuild.0.1.11 on 4.10 is now installable. Current state is: failing
obuild.0.1.11 on 4.11 is now installable. Current state is: failing
obuild.0.1.11 on 4.12 is now installable. Current state is: failing
obuild.0.1.11 on 4.13 is now installable. Current state is: failing
obuild.0.1.11 on 4.14 is now installable. Current state is: failing
obuild.0.1.11 on 5.0 is now installable. Current state is: failing
obuild.0.1.11 on 5.1 is now installable. Current state is: failing
obuild.0.1.9 on 4.08 had its build status changed: passing to failing
obuild.0.1.9 on 4.09 had its build status changed: passing to failing
obuild.0.1.9 on 4.10 had its build status changed: passing to failing
obuild.0.1.9 on 4.11 had its build status changed: passing to failing
obuild.0.1.9 on 4.12 had its build status changed: passing to failing
obuild.0.1.9 on 4.13 had its build status changed: passing to failing
obuild.0.1.9 on 4.14 had its build status changed: passing to failing
ocaml-makefile.6.37.0 on 5.1 is now installable. Current state is: failing
ocaml-makefile.6.38.0 on 5.1 is now installable. Current state is: failing
ocaml-makefile.6.39.0 on 5.1 is now installable. Current state is: failing
ocamldiff.1.1 on 5.1 is now installable. Current state is: failing
ocamlnet.4.1.6 on 4.08 had its build status changed: passing to failing
ocamlnet.4.1.6 on 4.09 had its build status changed: passing to failing
ocamlnet.4.1.7 on 4.08 had its build status changed: passing to failing
ocamlnet.4.1.7 on 4.09 had its build status changed: passing to failing
ocamlnet.4.1.7 on 4.10 had its build status changed: passing to failing
ocamlnet.4.1.8 on 4.08 had its build status changed: passing to failing
ocamlnet.4.1.8 on 4.09 had its build status changed: passing to failing
ocamlnet.4.1.8 on 4.10 had its build status changed: passing to failing
ocamlnet.4.1.8 on 4.11 had its build status changed: passing to failing
ocamlnet.4.1.8 on 4.12 had its build status changed: passing to failing
ocamlnet.4.1.8 on 4.13 had its build status changed: passing to failing
ocamlnet.4.1.8 on 4.14 had its build status changed: passing to failing
ocamlnet.4.1.9 on 4.08 had its build status changed: passing to failing
ocamlnet.4.1.9 on 4.09 had its build status changed: passing to failing
ocamlnet.4.1.9 on 4.10 had its build status changed: passing to failing
ocamlnet.4.1.9 on 4.11 had its build status changed: passing to failing
ocamlnet.4.1.9 on 4.12 had its build status changed: passing to failing
ocamlnet.4.1.9 on 4.13 had its build status changed: passing to failing
ocamlnet.4.1.9 on 4.14 had its build status changed: passing to failing
ocamlnet.4.1.9-1 on 4.08 had its build status changed: passing to failing
ocamlnet.4.1.9-1 on 4.09 had its build status changed: passing to failing
ocamlnet.4.1.9-1 on 4.10 had its build status changed: passing to failing
ocamlnet.4.1.9-1 on 4.11 had its build status changed: passing to failing
ocamlnet.4.1.9-1 on 4.12 had its build status changed: passing to failing
ocamlnet.4.1.9-1 on 4.13 had its build status changed: passing to failing
ocamlnet.4.1.9-1 on 4.14 had its build status changed: passing to failing
ocamlnet.4.1.9-2 on 4.08 had its build status changed: passing to failing
ocamlnet.4.1.9-2 on 4.09 had its build status changed: passing to failing
ocamlnet.4.1.9-2 on 4.10 had its build status changed: passing to failing
ocamlnet.4.1.9-2 on 4.11 had its build status changed: passing to failing
ocamlnet.4.1.9-2 on 4.12 had its build status changed: passing to failing
ocamlnet.4.1.9-2 on 4.13 had its build status changed: passing to failing
ocamlnet.4.1.9-2 on 4.14 had its build status changed: passing to failing
ocamlrss.2.0 on 4.08 had its build status changed: passing to failing
ocamlrss.2.0 on 4.09 had its build status changed: passing to failing
ocamlrss.2.0 on 4.10 had its build status changed: passing to failing
ocamlrss.2.0 on 4.11 had its build status changed: passing to failing
ocamlrss.2.0 on 4.12 had its build status changed: passing to failing
ocamlrss.2.0 on 4.13 had its build status changed: passing to failing
ocamlrss.2.0 on 4.14 had its build status changed: passing to failing
ocp-pack-split.1.0.1 on 5.1 is now installable. Current state is: failing
ocplib-simplex.0.3 on 5.1 is now installable. Current state is: failing
ott.0.27 on 4.08 had its build status changed: passing to failing
ott.0.27 on 4.09 had its build status changed: passing to failing
ott.0.27 on 4.10 had its build status changed: passing to failing
ott.0.27 on 4.11 had its build status changed: passing to failing
ott.0.27 on 4.12 had its build status changed: passing to failing
ott.0.27 on 4.13 had its build status changed: passing to failing
ott.0.27 on 4.14 had its build status changed: passing to failing
ott.0.31 on 4.08 had its build status changed: passing to failing
ott.0.31 on 4.09 had its build status changed: passing to failing
ott.0.31 on 4.10 had its build status changed: passing to failing
ott.0.31 on 4.11 had its build status changed: passing to failing
ott.0.31 on 4.12 had its build status changed: passing to failing
ott.0.31 on 4.13 had its build status changed: passing to failing
ott.0.31 on 4.14 had its build status changed: passing to failing
ott.0.32 on 4.08 had its build status changed: passing to failing
ott.0.32 on 4.09 had its build status changed: passing to failing
ott.0.32 on 4.10 had its build status changed: passing to failing
ott.0.32 on 4.11 had its build status changed: passing to failing
ott.0.32 on 4.12 had its build status changed: passing to failing
ott.0.32 on 4.13 had its build status changed: passing to failing
ott.0.32 on 4.14 had its build status changed: passing to failing
rml.1.09.06 on 5.1 is now installable. Current state is: failing
rml.1.09.07 on 5.1 is now installable. Current state is: failing
sail_sv_backend.0.17.1 on 4.08 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.5 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.5 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.5 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.5 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-bindings-xen.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-xen.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-xen.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 5.1 is now installable. Current state is: failing
solo5.0.7.0 on 5.1 is now installable. Current state is: failing
solo5.0.7.1 on 5.1 is now installable. Current state is: failing
statverif.1.97pl1.1 on 4.08 had its build status changed: passing to failing
statverif.1.97pl1.1 on 4.09 had its build status changed: passing to failing
statverif.1.97pl1.1 on 4.10 had its build status changed: passing to failing
statverif.1.97pl1.1 on 4.11 had its build status changed: passing to failing
statverif.1.97pl1.1 on 4.12 had its build status changed: passing to failing
statverif.1.97pl1.1 on 4.13 had its build status changed: passing to failing
statverif.1.97pl1.1 on 4.14 had its build status changed: passing to failing
statverif.1.97pl1.2 on 4.08 had its build status changed: passing to failing
statverif.1.97pl1.2 on 4.09 had its build status changed: passing to failing
statverif.1.97pl1.2 on 4.10 had its build status changed: passing to failing
statverif.1.97pl1.2 on 4.11 had its build status changed: passing to failing
statverif.1.97pl1.2 on 4.12 had its build status changed: passing to failing
statverif.1.97pl1.2 on 4.13 had its build status changed: passing to failing
statverif.1.97pl1.2 on 4.14 had its build status changed: passing to failing
stdcompat.10 on 4.08 had its build status changed: passing to failing
stdcompat.10 on 4.09 had its build status changed: passing to failing
stdcompat.11 on 4.08 had its build status changed: passing to failing
stdcompat.11 on 4.09 had its build status changed: passing to failing
stdcompat.12 on 4.08 had its build status changed: passing to failing
stdcompat.12 on 4.09 had its build status changed: passing to failing
stdcompat.12 on 4.10 had its build status changed: passing to failing
stdcompat.13 on 4.08 had its build status changed: passing to failing
stdcompat.13 on 4.09 had its build status changed: passing to failing
stdcompat.13 on 4.10 had its build status changed: passing to failing
stdcompat.14 on 4.08 had its build status changed: passing to failing
stdcompat.14 on 4.09 had its build status changed: passing to failing
stdcompat.14 on 4.10 had its build status changed: passing to failing
stdcompat.14 on 4.11 had its build status changed: passing to failing
stdcompat.15 on 4.08 had its build status changed: passing to failing
stdcompat.15 on 4.09 had its build status changed: passing to failing
stdcompat.15 on 4.10 had its build status changed: passing to failing
stdcompat.15 on 4.11 had its build status changed: passing to failing
stdcompat.15 on 4.12 had its build status changed: passing to failing
stdcompat.15 on 4.13 had its build status changed: passing to failing
stdcompat.15 on 4.14 had its build status changed: passing to failing
stdcompat.16 on 4.08 had its build status changed: passing to failing
stdcompat.16 on 4.09 had its build status changed: passing to failing
stdcompat.16 on 4.10 had its build status changed: passing to failing
stdcompat.16 on 4.11 had its build status changed: passing to failing
stdcompat.16 on 4.12 had its build status changed: passing to failing
stdcompat.16 on 4.13 had its build status changed: passing to failing
stdcompat.16 on 4.14 had its build status changed: passing to failing
stdcompat.17 on 4.08 had its build status changed: passing to failing
stdcompat.17 on 4.09 had its build status changed: passing to failing
stdcompat.17 on 4.10 had its build status changed: passing to failing
stdcompat.17 on 4.11 had its build status changed: passing to failing
stdcompat.17 on 4.12 had its build status changed: passing to failing
stdcompat.17 on 4.13 had its build status changed: passing to failing
stdcompat.17 on 4.14 had its build status changed: passing to failing
stdcompat.18 on 4.08 had its build status changed: passing to failing
stdcompat.18 on 4.09 had its build status changed: passing to failing
stdcompat.18 on 4.10 had its build status changed: passing to failing
stdcompat.18 on 4.11 had its build status changed: passing to failing
stdcompat.18 on 4.12 had its build status changed: passing to failing
stdcompat.18 on 4.13 had its build status changed: passing to failing
stdcompat.18 on 4.14 had its build status changed: passing to failing
stdcompat.7 on 4.08 had its build status changed: passing to failing
stdcompat.9 on 4.08 had its build status changed: passing to failing
sundialsml.5.8.0p0 on 4.08 had its build status changed: passing to failing
sundialsml.5.8.0p0 on 4.09 had its build status changed: passing to failing
sundialsml.5.8.0p0 on 4.10 had its build status changed: passing to failing
sundialsml.5.8.0p0 on 4.11 had its build status changed: passing to failing
sundialsml.5.8.0p0 on 4.12 had its build status changed: passing to failing
sundialsml.5.8.0p0 on 4.13 had its build status changed: passing to failing
sundialsml.6.0.0p0 on 4.08 had its build status changed: passing to failing
sundialsml.6.0.0p0 on 4.09 had its build status changed: passing to failing
sundialsml.6.0.0p0 on 4.10 had its build status changed: passing to failing
sundialsml.6.0.0p0 on 4.11 had its build status changed: passing to failing
sundialsml.6.0.0p0 on 4.12 had its build status changed: passing to failing
sundialsml.6.0.0p0 on 4.13 had its build status changed: passing to failing
sundialsml.6.1.0p0 on 4.08 had its build status changed: passing to failing
sundialsml.6.1.0p0 on 4.09 had its build status changed: passing to failing
sundialsml.6.1.0p0 on 4.10 had its build status changed: passing to failing
sundialsml.6.1.0p0 on 4.11 had its build status changed: passing to failing
sundialsml.6.1.0p0 on 4.12 had its build status changed: passing to failing
sundialsml.6.1.0p0 on 4.13 had its build status changed: passing to failing
sundialsml.6.1.1p0 on 4.08 had its build status changed: passing to failing
sundialsml.6.1.1p0 on 4.09 had its build status changed: passing to failing
sundialsml.6.1.1p0 on 4.10 had its build status changed: passing to failing
sundialsml.6.1.1p0 on 4.11 had its build status changed: passing to failing
sundialsml.6.1.1p0 on 4.12 had its build status changed: passing to failing
sundialsml.6.1.1p0 on 4.13 had its build status changed: passing to failing
sundialsml.6.1.1p1 on 4.08 had its build status changed: passing to failing
sundialsml.6.1.1p1 on 4.09 had its build status changed: passing to failing
sundialsml.6.1.1p1 on 4.10 had its build status changed: passing to failing
sundialsml.6.1.1p1 on 4.11 had its build status changed: passing to failing
sundialsml.6.1.1p1 on 4.12 had its build status changed: passing to failing
sundialsml.6.1.1p1 on 4.13 had its build status changed: passing to failing
sundialsml.6.1.1p1 on 4.14 had its build status changed: passing to failing
topiary.0.2.0 on 4.12 is now installable. Current state is: failing
topiary.0.2.0 on 5.0 is now installable. Current state is: failing
topiary.0.2.0 on 5.1 is now installable. Current state is: failing
topiary.0.2.1 on 5.1 is now installable. Current state is: failing
topiary.0.2.3 on 4.10 is now installable. Current state is: failing
tplib.1.3 on 5.1 is now installable. Current state is: failing
tuareg.2.0.10 on 4.08 had its build status changed: passing to failing
tuareg.2.0.10 on 4.09 had its build status changed: passing to failing
tuareg.2.0.10 on 4.10 had its build status changed: passing to failing
tuareg.2.0.10 on 4.11 had its build status changed: passing to failing
tuareg.2.0.10 on 4.12 had its build status changed: passing to failing
tuareg.2.0.10 on 4.13 had its build status changed: passing to failing
tuareg.2.0.10 on 4.14 had its build status changed: passing to failing
tuareg.2.0.10 on 5.0 had its build status changed: passing to failing
tuareg.2.0.10 on 5.1 is now installable. Current state is: failing
tuareg.2.0.7 on 4.08 had its build status changed: passing to failing
tuareg.2.0.7 on 4.09 had its build status changed: passing to failing
tuareg.2.0.7 on 4.10 had its build status changed: passing to failing
tuareg.2.0.7 on 4.11 had its build status changed: passing to failing
tuareg.2.0.7 on 4.12 had its build status changed: passing to failing
tuareg.2.0.7 on 4.13 had its build status changed: passing to failing
tuareg.2.0.7 on 4.14 had its build status changed: passing to failing
tuareg.2.0.7 on 5.0 had its build status changed: passing to failing
tuareg.2.0.7 on 5.1 is now installable. Current state is: failing
tuareg.2.1.0 on 4.10 had its build status changed: passing to failing
tuareg.2.1.0 on 4.11 had its build status changed: passing to failing
tuareg.2.2.0 on 4.08 had its build status changed: passing to failing
z3.4.10.1 on 4.13 had its build status changed: passing to failing
z3.4.10.1 on 5.0 had its build status changed: passing to failing
z3.4.10.2 on 4.08 had its build status changed: passing to failing
z3.4.10.2 on 5.0 had its build status changed: passing to failing
z3.4.12.2 on 4.08 is now installable. Current state is: failing
z3.4.12.2 on 4.09 is now installable. Current state is: failing
z3.4.12.2 on 4.10 is now installable. Current state is: failing
z3.4.12.2 on 4.11 is now installable. Current state is: failing
z3.4.12.2 on 4.12 is now installable. Current state is: failing
z3.4.12.2 on 4.13 is now installable. Current state is: failing
z3.4.12.2 on 4.14 is now installable. Current state is: failing
z3.4.12.2 on 5.0 is now installable. Current state is: failing
z3.4.12.2 on 5.1 is now installable. Current state is: failing
z3.4.8.14 on 5.0 had its build status changed: passing to failing
z3.4.8.14 on 5.1 is now installable. Current state is: failing
z3.4.8.17 on 5.1 is now installable. Current state is: failing
z3.4.9.1 on 4.08 had its build status changed: internal failure to failing

Packages now partially failing:

0install-gtk.2.15.2 on 4.08 had its build status changed: passing to partially failing
0install-gtk.2.15.2 on 4.09 had its build status changed: passing to partially failing
0install-gtk.2.15.2 on 4.10 had its build status changed: passing to partially failing
0install-gtk.2.15.2 on 4.11 had its build status changed: passing to partially failing
0install-gtk.2.15.2 on 4.12 had its build status changed: passing to partially failing
0install-gtk.2.15.2 on 4.13 had its build status changed: passing to partially failing
0install-gtk.2.15.2 on 4.14 had its build status changed: passing to partially failing
0install-gtk.2.16 on 4.08 had its build status changed: passing to partially failing
0install-gtk.2.16 on 4.09 had its build status changed: passing to partially failing
0install-gtk.2.16 on 4.10 had its build status changed: passing to partially failing
0install-gtk.2.16 on 4.11 had its build status changed: passing to partially failing
0install-gtk.2.16 on 4.12 had its build status changed: passing to partially failing
0install-gtk.2.16 on 4.13 had its build status changed: passing to partially failing
0install-gtk.2.16 on 4.14 had its build status changed: passing to partially failing
0install-gtk.2.17 on 4.08 had its build status changed: passing to partially failing
0install-gtk.2.17 on 4.09 had its build status changed: passing to partially failing
0install-gtk.2.17 on 4.10 had its build status changed: passing to partially failing
0install-gtk.2.17 on 4.11 had its build status changed: passing to partially failing
0install-gtk.2.17 on 4.12 had its build status changed: passing to partially failing
0install-gtk.2.17 on 4.13 had its build status changed: passing to partially failing
0install-gtk.2.17 on 4.14 had its build status changed: passing to partially failing
0install-gtk.2.18 on 4.08 had its build status changed: passing to partially failing
0install-gtk.2.18 on 4.09 had its build status changed: passing to partially failing
0install-gtk.2.18 on 4.10 had its build status changed: passing to partially failing
0install-gtk.2.18 on 4.11 had its build status changed: passing to partially failing
0install-gtk.2.18 on 4.12 had its build status changed: passing to partially failing
0install-gtk.2.18 on 4.13 had its build status changed: passing to partially failing
0install-gtk.2.18 on 4.14 had its build status changed: passing to partially failing
0install-solver.2.17 on 4.08 had its build status changed: passing to partially failing
0install-solver.2.17 on 4.09 had its build status changed: passing to partially failing
0install-solver.2.17 on 4.10 had its build status changed: passing to partially failing
0install-solver.2.17 on 4.11 had its build status changed: passing to partially failing
0install-solver.2.17 on 4.12 had its build status changed: passing to partially failing
0install-solver.2.17 on 4.13 had its build status changed: passing to partially failing
0install-solver.2.17 on 4.14 had its build status changed: passing to partially failing
0install-solver.2.17 on 5.0 had its build status changed: passing to partially failing
0install-solver.2.17 on 5.1 is now installable. Current state is: partially failing
0install-solver.2.18 on 4.08 had its build status changed: passing to partially failing
0install-solver.2.18 on 4.09 had its build status changed: passing to partially failing
0install-solver.2.18 on 4.10 had its build status changed: passing to partially failing
0install-solver.2.18 on 4.11 had its build status changed: passing to partially failing
0install-solver.2.18 on 4.12 had its build status changed: passing to partially failing
0install-solver.2.18 on 4.13 had its build status changed: passing to partially failing
0install-solver.2.18 on 4.14 had its build status changed: passing to partially failing
0install-solver.2.18 on 5.0 had its build status changed: passing to partially failing
0install-solver.2.18 on 5.1 is now installable. Current state is: partially failing
0install.2.15.1 on 4.08 had its build status changed: passing to partially failing
0install.2.15.1 on 4.09 had its build status changed: passing to partially failing
0install.2.15.1 on 4.10 had its build status changed: passing to partially failing
0install.2.15.1 on 4.11 had its build status changed: passing to partially failing
0install.2.15.1 on 4.12 had its build status changed: passing to partially failing
0install.2.15.1 on 4.13 had its build status changed: passing to partially failing
0install.2.15.1 on 4.14 had its build status changed: passing to partially failing
0install.2.15.1 on 5.0 had its build status changed: passing to partially failing
0install.2.15.1 on 5.1 is now installable. Current state is: partially failing
0install.2.15.2 on 4.08 had its build status changed: passing to partially failing
0install.2.15.2 on 4.09 had its build status changed: passing to partially failing
0install.2.15.2 on 4.10 had its build status changed: passing to partially failing
0install.2.15.2 on 4.11 had its build status changed: passing to partially failing
0install.2.15.2 on 4.12 had its build status changed: passing to partially failing
0install.2.15.2 on 4.13 had its build status changed: passing to partially failing
0install.2.15.2 on 4.14 had its build status changed: passing to partially failing
0install.2.16 on 4.08 had its build status changed: passing to partially failing
0install.2.16 on 4.09 had its build status changed: passing to partially failing
0install.2.16 on 4.10 had its build status changed: passing to partially failing
0install.2.16 on 4.11 had its build status changed: passing to partially failing
0install.2.16 on 4.12 had its build status changed: passing to partially failing
0install.2.16 on 4.13 had its build status changed: passing to partially failing
0install.2.16 on 4.14 had its build status changed: passing to partially failing
0install.2.17 on 4.08 had its build status changed: passing to partially failing
0install.2.17 on 4.09 had its build status changed: passing to partially failing
0install.2.17 on 4.10 had its build status changed: passing to partially failing
0install.2.17 on 4.11 had its build status changed: passing to partially failing
0install.2.17 on 4.12 had its build status changed: passing to partially failing
0install.2.17 on 4.13 had its build status changed: passing to partially failing
0install.2.17 on 4.14 had its build status changed: passing to partially failing
0install.2.18 on 4.08 had its build status changed: passing to partially failing
0install.2.18 on 4.09 had its build status changed: passing to partially failing
0install.2.18 on 4.10 had its build status changed: passing to partially failing
0install.2.18 on 4.11 had its build status changed: passing to partially failing
0install.2.18 on 4.12 had its build status changed: passing to partially failing
0install.2.18 on 4.13 had its build status changed: passing to partially failing
0install.2.18 on 4.14 had its build status changed: passing to partially failing
ANSITerminal.0.8.1 on 4.08 had its build status changed: passing to partially failing
ANSITerminal.0.8.1 on 4.09 had its build status changed: passing to partially failing
ANSITerminal.0.8.1 on 4.10 had its build status changed: passing to partially failing
ANSITerminal.0.8.1 on 4.11 had its build status changed: passing to partially failing
ANSITerminal.0.8.1 on 4.12 had its build status changed: passing to partially failing
ANSITerminal.0.8.1 on 4.13 had its build status changed: passing to partially failing
ANSITerminal.0.8.1 on 4.14 had its build status changed: passing to partially failing
ANSITerminal.0.8.2 on 4.08 had its build status changed: passing to partially failing
ANSITerminal.0.8.2 on 4.09 had its build status changed: passing to partially failing
ANSITerminal.0.8.2 on 4.10 had its build status changed: passing to partially failing
ANSITerminal.0.8.2 on 4.11 had its build status changed: passing to partially failing
ANSITerminal.0.8.2 on 4.12 had its build status changed: passing to partially failing
ANSITerminal.0.8.2 on 4.13 had its build status changed: passing to partially failing
ANSITerminal.0.8.2 on 4.14 had its build status changed: passing to partially failing
ANSITerminal.0.8.3 on 4.08 had its build status changed: passing to partially failing
ANSITerminal.0.8.3 on 4.09 had its build status changed: passing to partially failing
ANSITerminal.0.8.3 on 4.10 had its build status changed: passing to partially failing
ANSITerminal.0.8.3 on 4.11 had its build status changed: passing to partially failing
ANSITerminal.0.8.3 on 4.12 had its build status changed: passing to partially failing
ANSITerminal.0.8.3 on 4.13 had its build status changed: passing to partially failing
ANSITerminal.0.8.3 on 4.14 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 4.08 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 4.09 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 4.10 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 4.11 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 4.12 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 4.13 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 4.14 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 5.0 had its build status changed: passing to partially failing
ANSITerminal.0.8.4 on 5.1 is now installable. Current state is: partially failing
ANSITerminal.0.8.5 on 4.08 had its build status changed: passing to partially failing
ANSITerminal.0.8.5 on 4.09 had its build status changed: passing to partially failing
ANSITerminal.0.8.5 on 4.10 had its build status changed: passing to partially failing
ANSITerminal.0.8.5 on 4.11 had its build status changed: passing to partially failing
ANSITerminal.0.8.5 on 4.12 had its build status changed: passing to partially failing
ANSITerminal.0.8.5 on 4.13 had its build status changed: passing to partially failing
ANSITerminal.0.8.5 on 4.14 had its build status changed: passing to partially failing
ANSITerminal.0.8.5 on 5.0 had its build status changed: passing to partially failing
ANSITerminal.0.8.5 on 5.1 is now installable. Current state is: partially failing
BetterErrors.0.0.1 on 4.08 had its build status changed: passing to partially failing
BetterErrors.0.0.1 on 4.09 had its build status changed: passing to partially failing
BetterErrors.0.0.1 on 4.10 had its build status changed: passing to partially failing
BetterErrors.0.0.1 on 4.11 had its build status changed: passing to partially failing
BetterErrors.0.0.1 on 4.12 had its build status changed: passing to partially failing
BetterErrors.0.0.1 on 4.13 had its build status changed: passing to partially failing
BetterErrors.0.0.1 on 4.14 had its build status changed: passing to partially failing
DAGaml.0.01 on 4.08 had its build status changed: passing to partially failing
DAGaml.0.01 on 4.09 had its build status changed: passing to partially failing
DAGaml.0.01 on 4.10 had its build status changed: passing to partially failing
DAGaml.0.01 on 4.11 had its build status changed: passing to partially failing
DAGaml.0.01 on 4.12 had its build status changed: passing to partially failing
DAGaml.0.01 on 4.13 had its build status changed: passing to partially failing
DAGaml.0.01 on 4.14 had its build status changed: passing to partially failing
DAGaml.0.02 on 4.08 had its build status changed: passing to partially failing
DAGaml.0.02 on 4.09 had its build status changed: passing to partially failing
DAGaml.0.02 on 4.10 had its build status changed: passing to partially failing
DAGaml.0.02 on 4.11 had its build status changed: passing to partially failing
DAGaml.0.02 on 4.12 had its build status changed: passing to partially failing
DAGaml.0.02 on 4.13 had its build status changed: passing to partially failing
DAGaml.0.02 on 4.14 had its build status changed: passing to partially failing
DkSDKFFIOCaml_Std.1.0.0~1 on 4.14 is now installable. Current state is: partially failing
FPauth-core.1.0.0 on 4.12 had its build status changed: passing to partially failing
FPauth-core.1.0.0 on 4.13 had its build status changed: passing to partially failing
FPauth-core.1.0.0 on 4.14 had its build status changed: passing to partially failing
FPauth-responses.1.0.0 on 4.12 had its build status changed: passing to partially failing
FPauth-responses.1.0.0 on 4.13 had its build status changed: passing to partially failing
FPauth-responses.1.0.0 on 4.14 had its build status changed: passing to partially failing
FrontC.4.0.0 on 4.08 had its build status changed: passing to partially failing
FrontC.4.0.0 on 4.09 had its build status changed: passing to partially failing
FrontC.4.0.0 on 4.10 had its build status changed: passing to partially failing
FrontC.4.0.0 on 4.11 had its build status changed: passing to partially failing
FrontC.4.0.0 on 4.12 had its build status changed: passing to partially failing
FrontC.4.0.0 on 4.13 had its build status changed: passing to partially failing
FrontC.4.0.0 on 4.14 had its build status changed: passing to partially failing
FrontC.4.0.0 on 5.0 had its build status changed: passing to partially failing
FrontC.4.0.0 on 5.1 is now installable. Current state is: partially failing
FrontC.4.1.0 on 4.08 had its build status changed: passing to partially failing
FrontC.4.1.0 on 4.09 had its build status changed: passing to partially failing
FrontC.4.1.0 on 4.10 had its build status changed: passing to partially failing
FrontC.4.1.0 on 4.11 had its build status changed: passing to partially failing
FrontC.4.1.0 on 4.12 had its build status changed: passing to partially failing
FrontC.4.1.0 on 4.13 had its build status changed: passing to partially failing
FrontC.4.1.0 on 4.14 had its build status changed: passing to partially failing
FrontC.4.1.0 on 5.0 had its build status changed: passing to partially failing
FrontC.4.1.0 on 5.1 is now installable. Current state is: partially failing
GT.0.3.0 on 4.10 had its build status changed: passing to partially failing
GT.0.3.0 on 4.11 had its build status changed: passing to partially failing
GT.0.4.0 on 4.10 had its build status changed: passing to partially failing
GT.0.4.0 on 4.11 had its build status changed: passing to partially failing
GT.0.4.1 on 4.10 had its build status changed: passing to partially failing
GT.0.4.1 on 4.11 had its build status changed: passing to partially failing
GT.0.4.1 on 4.12 had its build status changed: passing to partially failing
GT.0.4.1 on 4.13 had its build status changed: passing to partially failing
GT.0.4.2 on 4.10 had its build status changed: passing to partially failing
GT.0.4.2 on 4.11 had its build status changed: passing to partially failing
GT.0.4.2 on 4.12 had its build status changed: passing to partially failing
GT.0.4.2 on 4.13 had its build status changed: passing to partially failing
GT.0.5.0 on 4.10 had its build status changed: passing to partially failing
GT.0.5.0 on 4.11 had its build status changed: passing to partially failing
GT.0.5.0 on 4.12 had its build status changed: passing to partially failing
GT.0.5.0 on 4.13 had its build status changed: passing to partially failing
GT.0.5.0 on 4.14 had its build status changed: passing to partially failing
GT.0.5.1 on 4.10 had its build status changed: passing to partially failing
GT.0.5.1 on 4.11 had its build status changed: passing to partially failing
GT.0.5.1 on 4.12 had its build status changed: passing to partially failing
GT.0.5.1 on 4.13 had its build status changed: passing to partially failing
GT.0.5.1 on 4.14 had its build status changed: passing to partially failing
GT.0.5.1 on 5.0 had its build status changed: not available to partially failing
GT.0.5.2 on 4.13 is now installable. Current state is: partially failing
GT.0.5.2 on 4.14 is now installable. Current state is: partially failing
GT.0.5.2 on 5.0 is now installable. Current state is: partially failing
General.0.7.0 on 4.08 had its build status changed: passing to partially failing
General.0.7.0 on 4.09 had its build status changed: passing to partially failing
General.0.7.0 on 4.10 had its build status changed: passing to partially failing
General.0.7.0 on 4.11 had its build status changed: passing to partially failing
ISO3166.0.1.0 on 4.08 is now installable. Current state is: partially failing
ISO3166.0.1.0 on 4.09 is now installable. Current state is: partially failing
ISO3166.0.1.0 on 4.10 is now installable. Current state is: partially failing
ISO3166.0.1.0 on 4.11 is now installable. Current state is: partially failing
ISO3166.0.1.0 on 4.12 is now installable. Current state is: partially failing
ISO3166.0.1.0 on 4.13 is now installable. Current state is: partially failing
ISO3166.0.1.0 on 4.14 is now installable. Current state is: partially failing
ISO3166.0.1.0 on 5.0 is now installable. Current state is: partially failing
ISO3166.0.1.0 on 5.1 is now installable. Current state is: partially failing
ISO8601.0.2.6 on 4.08 had its build status changed: passing to partially failing
ISO8601.0.2.6 on 4.09 had its build status changed: passing to partially failing
ISO8601.0.2.6 on 4.10 had its build status changed: passing to partially failing
ISO8601.0.2.6 on 4.11 had its build status changed: passing to partially failing
ISO8601.0.2.6 on 4.12 had its build status changed: passing to partially failing
ISO8601.0.2.6 on 4.13 had its build status changed: passing to partially failing
ISO8601.0.2.6 on 4.14 had its build status changed: passing to partially failing
ISO8601.0.2.6 on 5.0 had its build status changed: passing to partially failing
ISO8601.0.2.6 on 5.1 is now installable. Current state is: partially failing
OCADml.0.1.0 on 4.13 had its build status changed: passing to partially failing
OCADml.0.1.0 on 4.14 had its build status changed: passing to partially failing
OCADml.0.1.0 on 5.0 had its build status changed: passing to partially failing
OCADml.0.1.0 on 5.1 is now installable. Current state is: partially failing
OCADml.0.1.1 on 4.13 is now installable. Current state is: partially failing
OCADml.0.1.1 on 4.14 is now installable. Current state is: partially failing
OCADml.0.1.1 on 5.0 is now installable. Current state is: partially failing
OCADml.0.1.1 on 5.1 is now installable. Current state is: partially failing
OCADml.0.1.2 on 4.13 is now installable. Current state is: partially failing
OCADml.0.1.2 on 4.14 is now installable. Current state is: partially failing
OCADml.0.1.2 on 5.0 is now installable. Current state is: partially failing
OCADml.0.1.2 on 5.1 is now installable. Current state is: partially failing
OCADml.0.2.0 on 4.13 is now installable. Current state is: partially failing
OCADml.0.2.0 on 4.14 is now installable. Current state is: partially failing
OCADml.0.2.0 on 5.0 is now installable. Current state is: partially failing
OCADml.0.2.0 on 5.1 is now installable. Current state is: partially failing
OCADml.0.2.1 on 4.14 is now installable. Current state is: partially failing
OCADml.0.2.1 on 5.0 is now installable. Current state is: partially failing
OCADml.0.2.1 on 5.1 is now installable. Current state is: partially failing
OCADml.0.2.2 on 4.14 is now installable. Current state is: partially failing
OCADml.0.2.2 on 5.0 is now installable. Current state is: partially failing
OCADml.0.2.2 on 5.1 is now installable. Current state is: partially failing
OCADml.0.3.1 on 4.14 is now installable. Current state is: partially failing
OCADml.0.3.1 on 5.0 is now installable. Current state is: partially failing
OCADml.0.3.1 on 5.1 is now installable. Current state is: partially failing
OCADml.0.3.2 on 4.14 is now installable. Current state is: partially failing
OCADml.0.3.2 on 5.0 is now installable. Current state is: partially failing
OCADml.0.3.2 on 5.1 is now installable. Current state is: partially failing
OCADml.0.4.0 on 4.14 is now installable. Current state is: partially failing
OCADml.0.4.0 on 5.0 is now installable. Current state is: partially failing
OCADml.0.4.0 on 5.1 is now installable. Current state is: partially failing
OCADml.0.4.1 on 4.14 is now installable. Current state is: partially failing
OCADml.0.4.1 on 5.0 is now installable. Current state is: partially failing
OCADml.0.4.1 on 5.1 is now installable. Current state is: partially failing
OCADml.0.5.0 on 4.14 is now installable. Current state is: partially failing
OCADml.0.5.0 on 5.0 is now installable. Current state is: partially failing
OCADml.0.5.0 on 5.1 is now installable. Current state is: partially failing
OCADml.0.6.0 on 4.14 is now installable. Current state is: partially failing
OCADml.0.6.0 on 5.0 is now installable. Current state is: partially failing
OCADml.0.6.0 on 5.1 is now installable. Current state is: partially failing
OCanren-ppx.0.1.0 on 4.08 had its build status changed: passing to partially failing
OCanren-ppx.0.1.0 on 4.09 had its build status changed: passing to partially failing
OCanren-ppx.0.1.0 on 4.10 had its build status changed: passing to partially failing
OCanren-ppx.0.1.0 on 4.11 had its build status changed: passing to partially failing
OCanren-ppx.0.1.0 on 4.12 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 4.08 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 4.09 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 4.10 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 4.11 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 4.12 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 4.13 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 4.14 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 5.0 had its build status changed: passing to partially failing
OCanren-ppx.0.2.0 on 5.1 is now installable. Current state is: partially failing
OCanren-ppx.0.3.0 on 4.10 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0 on 4.11 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0 on 4.12 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0 on 4.13 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0 on 4.14 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0 on 5.0 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0 on 5.1 is now installable. Current state is: partially failing
OCanren-ppx.0.3.0~alpha1 on 4.10 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0~alpha1 on 4.11 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0~alpha1 on 4.12 had its build status changed: passing to partially failing
OCanren-ppx.0.3.0~alpha1 on 4.13 had its build status changed: passing to partially failing
OCanren.0.1.0 on 4.10 had its build status changed: passing to partially failing
OCanren.0.1.0 on 4.11 had its build status changed: passing to partially failing
OCanren.0.1.0 on 4.12 had its build status changed: passing to partially failing
OCanren.0.1.0 on 4.13 had its build status changed: passing to partially failing
OCanren.0.2.0 on 4.10 had its build status changed: passing to partially failing
OCanren.0.2.0 on 4.11 had its build status changed: passing to partially failing
OCanren.0.2.0 on 4.12 had its build status changed: passing to partially failing
OCanren.0.2.0 on 4.13 had its build status changed: passing to partially failing
OCanren.0.3.0 on 4.10 had its build status changed: passing to partially failing
OCanren.0.3.0 on 4.11 had its build status changed: passing to partially failing
OCanren.0.3.0 on 4.12 had its build status changed: passing to partially failing
OCanren.0.3.0 on 4.13 had its build status changed: passing to partially failing
OCanren.0.3.0 on 4.14 had its build status changed: passing to partially failing
OCanren.0.3.0 on 5.0 had its build status changed: not available to partially failing
OCanren.0.3.0~alpha1 on 4.10 had its build status changed: passing to partially failing
OCanren.0.3.0~alpha1 on 4.11 had its build status changed: passing to partially failing
OCanren.0.3.0~alpha1 on 4.12 had its build status changed: passing to partially failing
OCanren.0.3.0~alpha1 on 4.13 had its build status changed: passing to partially failing
OCanren.0.3.0~alpha1 on 4.14 had its build status changed: passing to partially failing
OCanren.0.3.0~alpha1 on 5.0 had its build status changed: not available to partially failing
OSCADml.0.1.0 on 4.13 had its build status changed: passing to partially failing
OSCADml.0.1.0 on 4.14 had its build status changed: passing to partially failing
OSCADml.0.1.0 on 5.0 had its build status changed: passing to partially failing
OSCADml.0.1.0 on 5.1 is now installable. Current state is: partially failing
OSCADml.0.1.1 on 4.14 had its build status changed: passing to partially failing
OSCADml.0.1.1 on 5.0 had its build status changed: passing to partially failing
OSCADml.0.1.1 on 5.1 is now installable. Current state is: partially failing
OSCADml.0.2.0 on 4.14 is now installable. Current state is: partially failing
OSCADml.0.2.0 on 5.0 is now installable. Current state is: partially failing
OSCADml.0.2.0 on 5.1 is now installable. Current state is: partially failing
OSCADml.0.2.1 on 4.14 is now installable. Current state is: partially failing
OSCADml.0.2.1 on 5.0 is now installable. Current state is: partially failing
OSCADml.0.2.1 on 5.1 is now installable. Current state is: partially failing
OSCADml.0.2.2 on 4.14 is now installable. Current state is: partially failing
OSCADml.0.2.2 on 5.0 is now installable. Current state is: partially failing
OSCADml.0.2.2 on 5.1 is now installable. Current state is: partially failing
OSCADml.0.2.3 on 4.14 is now installable. Current state is: partially failing
OSCADml.0.2.3 on 5.0 is now installable. Current state is: partially failing
OSCADml.0.2.3 on 5.1 is now installable. Current state is: partially failing
SZXX.0.1.0 on 4.08 had its build status changed: passing to partially failing
SZXX.0.1.0 on 4.09 had its build status changed: passing to partially failing
SZXX.0.1.0 on 4.10 had its build status changed: passing to partially failing
SZXX.0.1.0 on 4.11 had its build status changed: passing to partially failing
SZXX.0.1.0 on 4.12 had its build status changed: passing to partially failing
SZXX.0.1.0 on 4.13 had its build status changed: passing to partially failing
SZXX.0.1.0 on 4.14 had its build status changed: passing to partially failing
SZXX.0.1.0 on 5.0 had its build status changed: passing to partially failing
SZXX.0.1.0 on 5.1 is now installable. Current state is: partially failing
SZXX.1.0.0 on 4.08 had its build status changed: passing to partially failing
SZXX.1.0.0 on 4.09 had its build status changed: passing to partially failing
SZXX.1.0.0 on 4.10 had its build status changed: passing to partially failing
SZXX.1.0.0 on 4.11 had its build status changed: passing to partially failing
SZXX.1.0.0 on 4.12 had its build status changed: passing to partially failing
SZXX.1.0.0 on 4.13 had its build status changed: passing to partially failing
SZXX.1.0.0 on 4.14 had its build status changed: passing to partially failing
SZXX.1.0.0 on 5.0 had its build status changed: passing to partially failing
SZXX.1.0.0 on 5.1 is now installable. Current state is: partially failing
SZXX.1.1.0 on 4.08 had its build status changed: passing to partially failing
SZXX.1.1.0 on 4.09 had its build status changed: passing to partially failing
SZXX.1.1.0 on 4.10 had its build status changed: passing to partially failing
SZXX.1.1.0 on 4.11 had its build status changed: passing to partially failing
SZXX.1.1.0 on 4.12 had its build status changed: passing to partially failing
SZXX.1.1.0 on 4.13 had its build status changed: passing to partially failing
SZXX.1.1.0 on 4.14 had its build status changed: passing to partially failing
SZXX.1.1.0 on 5.0 had its build status changed: passing to partially failing
SZXX.1.1.0 on 5.1 is now installable. Current state is: partially failing
SZXX.2.0.0 on 4.08 had its build status changed: passing to partially failing
SZXX.2.0.0 on 4.09 had its build status changed: passing to partially failing
SZXX.2.0.0 on 4.10 had its build status changed: passing to partially failing
SZXX.2.0.0 on 4.11 had its build status changed: passing to partially failing
SZXX.2.0.0 on 4.12 had its build status changed: passing to partially failing
SZXX.2.0.0 on 4.13 had its build status changed: passing to partially failing
SZXX.2.0.0 on 4.14 had its build status changed: passing to partially failing
SZXX.2.0.0 on 5.0 had its build status changed: passing to partially failing
SZXX.2.1.0 on 4.08 had its build status changed: passing to partially failing
SZXX.2.1.0 on 4.09 had its build status changed: passing to partially failing
SZXX.2.1.0 on 4.10 had its build status changed: passing to partially failing
SZXX.2.1.0 on 4.11 had its build status changed: passing to partially failing
SZXX.2.1.0 on 4.12 had its build status changed: passing to partially failing
SZXX.2.1.0 on 4.13 had its build status changed: passing to partially failing
SZXX.2.1.0 on 4.14 had its build status changed: passing to partially failing
SZXX.2.1.0 on 5.0 had its build status changed: passing to partially failing
SZXX.2.1.1 on 4.08 had its build status changed: passing to partially failing
SZXX.2.1.1 on 4.09 had its build status changed: passing to partially failing
SZXX.2.1.1 on 4.10 had its build status changed: passing to partially failing
SZXX.2.1.1 on 4.11 had its build status changed: passing to partially failing
SZXX.2.1.1 on 4.12 had its build status changed: passing to partially failing
SZXX.2.1.1 on 4.13 had its build status changed: passing to partially failing
SZXX.2.1.1 on 4.14 had its build status changed: passing to partially failing
SZXX.2.1.1 on 5.0 had its build status changed: passing to partially failing
SZXX.2.1.2 on 4.08 had its build status changed: passing to partially failing
SZXX.2.1.2 on 4.09 had its build status changed: passing to partially failing
SZXX.2.1.2 on 4.10 had its build status changed: passing to partially failing
SZXX.2.1.2 on 4.11 had its build status changed: passing to partially failing
SZXX.2.1.2 on 4.12 had its build status changed: passing to partially failing
SZXX.2.1.2 on 4.13 had its build status changed: passing to partially failing
SZXX.2.1.2 on 4.14 had its build status changed: passing to partially failing
SZXX.2.1.2 on 5.0 had its build status changed: passing to partially failing
SZXX.2.2.0 on 4.08 had its build status changed: passing to partially failing
SZXX.2.2.0 on 4.09 had its build status changed: passing to partially failing
SZXX.2.2.0 on 4.10 had its build status changed: passing to partially failing
SZXX.2.2.0 on 4.11 had its build status changed: passing to partially failing
SZXX.2.2.0 on 4.12 had its build status changed: passing to partially failing
SZXX.2.2.0 on 4.13 had its build status changed: passing to partially failing
SZXX.2.2.0 on 4.14 had its build status changed: passing to partially failing
SZXX.2.2.0 on 5.0 had its build status changed: passing to partially failing
SZXX.2.3.0 on 4.08 had its build status changed: passing to partially failing
SZXX.2.3.0 on 4.09 had its build status changed: passing to partially failing
SZXX.2.3.0 on 4.10 had its build status changed: passing to partially failing
SZXX.2.3.0 on 4.11 had its build status changed: passing to partially failing
SZXX.2.3.0 on 4.12 had its build status changed: passing to partially failing
SZXX.2.3.0 on 4.13 had its build status changed: passing to partially failing
SZXX.2.3.0 on 4.14 had its build status changed: passing to partially failing
SZXX.2.3.0 on 5.0 had its build status changed: passing to partially failing
SZXX.3.0.0 on 4.11 is now installable. Current state is: partially failing
SZXX.3.0.0 on 4.12 is now installable. Current state is: partially failing
SZXX.3.0.0 on 4.13 is now installable. Current state is: partially failing
SZXX.3.0.0 on 4.14 is now installable. Current state is: partially failing
SZXX.3.0.0 on 5.0 is now installable. Current state is: partially failing
SZXX.3.0.1 on 4.11 is now installable. Current state is: partially failing
SZXX.3.0.1 on 4.12 is now installable. Current state is: partially failing
SZXX.3.0.1 on 4.13 is now installable. Current state is: partially failing
SZXX.3.0.1 on 4.14 is now installable. Current state is: partially failing
SZXX.3.0.1 on 5.0 is now installable. Current state is: partially failing
SZXX.3.0.1 on 5.1 is now installable. Current state is: partially failing
SZXX.4.0.0 on 5.0 is now installable. Current state is: partially failing
SZXX.4.0.0 on 5.1 is now installable. Current state is: partially failing
SZXX.4.0.1 on 5.0 is now installable. Current state is: partially failing
SZXX.4.0.1 on 5.1 is now installable. Current state is: partially failing
SZXX.4.1.0 on 5.0 is now installable. Current state is: partially failing
SZXX.4.1.0 on 5.1 is now installable. Current state is: partially failing
Snowflake.0.01 on 4.08 had its build status changed: passing to partially failing
Snowflake.0.01 on 4.09 had its build status changed: passing to partially failing
Snowflake.0.01 on 4.10 had its build status changed: passing to partially failing
Snowflake.0.01 on 4.11 had its build status changed: passing to partially failing
Snowflake.0.01 on 4.12 had its build status changed: passing to partially failing
Snowflake.0.01 on 4.13 had its build status changed: passing to partially failing
Snowflake.0.01 on 4.14 had its build status changed: passing to partially failing
Snowflake.0.02 on 4.08 had its build status changed: passing to partially failing
Snowflake.0.02 on 4.09 had its build status changed: passing to partially failing
Snowflake.0.02 on 4.10 had its build status changed: passing to partially failing
Snowflake.0.02 on 4.11 had its build status changed: passing to partially failing
Snowflake.0.02 on 4.12 had its build status changed: passing to partially failing
Snowflake.0.02 on 4.13 had its build status changed: passing to partially failing
Snowflake.0.02 on 4.14 had its build status changed: passing to partially failing
Snowflake.0.02.01 on 4.08 had its build status changed: passing to partially failing
Snowflake.0.02.01 on 4.09 had its build status changed: passing to partially failing
Snowflake.0.02.01 on 4.10 had its build status changed: passing to partially failing
Snowflake.0.02.01 on 4.11 had its build status changed: passing to partially failing
Snowflake.0.02.01 on 4.12 had its build status changed: passing to partially failing
Snowflake.0.02.01 on 4.13 had its build status changed: passing to partially failing
Snowflake.0.02.01 on 4.14 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 4.08 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 4.09 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 4.10 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 4.11 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 4.12 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 4.13 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 4.14 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 5.0 had its build status changed: passing to partially failing
Snowflake.0.02.02 on 5.1 is now installable. Current state is: partially failing
Snowflake.0.02.03 on 4.13 had its build status changed: passing to partially failing
Snowflake.0.02.03 on 4.14 had its build status changed: passing to partially failing
Snowflake.0.02.03 on 5.0 had its build status changed: passing to partially failing
Snowflake.0.02.03 on 5.1 is now installable. Current state is: partially failing
TCSLib.0.2 on 4.08 had its build status changed: passing to partially failing
TCSLib.0.2 on 4.09 had its build status changed: passing to partially failing
TCSLib.0.2 on 4.10 had its build status changed: passing to partially failing
TCSLib.0.2 on 4.11 had its build status changed: passing to partially failing
TCSLib.0.2 on 4.12 had its build status changed: passing to partially failing
TCSLib.0.2 on 4.13 had its build status changed: passing to partially failing
TCSLib.0.2 on 4.14 had its build status changed: passing to partially failing
TCSLib.0.3 on 4.08 had its build status changed: passing to partially failing
TCSLib.0.3 on 4.09 had its build status changed: passing to partially failing
TCSLib.0.3 on 4.10 had its build status changed: passing to partially failing
TCSLib.0.3 on 4.11 had its build status changed: passing to partially failing
TCSLib.0.3 on 4.12 had its build status changed: passing to partially failing
TCSLib.0.3 on 4.13 had its build status changed: passing to partially failing
TCSLib.0.3 on 4.14 had its build status changed: passing to partially failing
abella.2.0.8 on 4.12 is now installable. Current state is: partially failing
abella.2.0.8 on 4.13 is now installable. Current state is: partially failing
abella.2.0.8 on 4.14 is now installable. Current state is: partially failing
abella.2.0.8 on 5.0 is now installable. Current state is: partially failing
abella.2.0.8 on 5.1 is now installable. Current state is: partially failing
absolute.0.1 on 4.08 had its build status changed: passing to partially failing
absolute.0.1 on 4.09 had its build status changed: passing to partially failing
absolute.0.1 on 4.10 had its build status changed: passing to partially failing
absolute.0.1 on 4.11 had its build status changed: passing to partially failing
absolute.0.1 on 4.12 had its build status changed: passing to partially failing
absolute.0.1 on 4.13 had its build status changed: passing to partially failing
absolute.0.1 on 4.14 had its build status changed: passing to partially failing
absolute.0.1 on 5.0 had its build status changed: not available to partially failing
absolute.0.1 on 5.1 is now installable. Current state is: partially failing
absolute.0.2 on 4.11 is now installable. Current state is: partially failing
absolute.0.2 on 4.12 is now installable. Current state is: partially failing
absolute.0.2 on 4.13 is now installable. Current state is: partially failing
absolute.0.2 on 4.14 is now installable. Current state is: partially failing
absolute.0.2 on 5.0 is now installable. Current state is: partially failing
absolute.0.2 on 5.1 is now installable. Current state is: partially failing
absolute.0.3 on 4.11 is now installable. Current state is: partially failing
absolute.0.3 on 4.12 is now installable. Current state is: partially failing
absolute.0.3 on 4.13 is now installable. Current state is: partially failing
absolute.0.3 on 4.14 is now installable. Current state is: partially failing
absolute.0.3 on 5.0 is now installable. Current state is: partially failing
absolute.0.3 on 5.1 is now installable. Current state is: partially failing
abstract_algebra.v0.15.0 on 4.10 had its build status changed: passing to partially failing
abstract_algebra.v0.15.0 on 4.11 had its build status changed: passing to partially failing
abstract_algebra.v0.15.0 on 4.12 had its build status changed: passing to partially failing
abstract_algebra.v0.15.0 on 4.13 had its build status changed: passing to partially failing
abstract_algebra.v0.15.0 on 4.14 had its build status changed: passing to partially failing
abstract_algebra.v0.15.0 on 5.0 had its build status changed: passing to partially failing
abstract_algebra.v0.15.0 on 5.1 is now installable. Current state is: partially failing
abstract_algebra.v0.16.0 on 4.14 is now installable. Current state is: partially failing
abstract_algebra.v0.16.0 on 5.0 is now installable. Current state is: partially failing
abstract_algebra.v0.16.0 on 5.1 is now installable. Current state is: partially failing
accessor.v0.14.0 on 4.09 had its build status changed: passing to partially failing
accessor.v0.14.0 on 4.10 had its build status changed: passing to partially failing
accessor.v0.14.0 on 4.11 had its build status changed: passing to partially failing
accessor.v0.14.0 on 4.12 had its build status changed: passing to partially failing
accessor.v0.14.0 on 4.13 had its build status changed: passing to partially failing
accessor.v0.14.0 on 4.14 had its build status changed: passing to partially failing
accessor.v0.14.0 on 5.0 had its build status changed: passing to partially failing
accessor.v0.14.0 on 5.1 is now installable. Current state is: partially failing
accessor.v0.14.1 on 4.09 had its build status changed: passing to partially failing
accessor.v0.14.1 on 4.10 had its build status changed: passing to partially failing
accessor.v0.14.1 on 4.11 had its build status changed: passing to partially failing
accessor.v0.14.1 on 4.12 had its build status changed: passing to partially failing
accessor.v0.14.1 on 4.13 had its build status changed: passing to partially failing
accessor.v0.14.1 on 4.14 had its build status changed: passing to partially failing
accessor.v0.15.0 on 4.10 had its build status changed: passing to partially failing
accessor.v0.15.0 on 4.11 had its build status changed: passing to partially failing
accessor.v0.15.0 on 4.12 had its build status changed: passing to partially failing
accessor.v0.15.0 on 4.13 had its build status changed: passing to partially failing
accessor.v0.15.0 on 4.14 had its build status changed: passing to partially failing
accessor.v0.15.0 on 5.0 had its build status changed: passing to partially failing
accessor.v0.15.0 on 5.1 is now installable. Current state is: partially failing
accessor.v0.16.0 on 4.14 is now installable. Current state is: partially failing
accessor.v0.16.0 on 5.0 is now installable. Current state is: partially failing
accessor.v0.16.0 on 5.1 is now installable. Current state is: partially failing
accessor_async.v0.14.0 on 4.09 had its build status changed: passing to partially failing
accessor_async.v0.14.0 on 4.10 had its build status changed: passing to partially failing
accessor_async.v0.14.0 on 4.11 had its build status changed: passing to partially failing
accessor_async.v0.14.0 on 4.12 had its build status changed: passing to partially failing
accessor_async.v0.14.0 on 4.13 had its build status changed: passing to partially failing
accessor_async.v0.14.0 on 4.14 had its build status changed: passing to partially failing
accessor_async.v0.14.0 on 5.0 had its build status changed: passing to partially failing
accessor_async.v0.14.0 on 5.1 is now installable. Current state is: partially failing
accessor_async.v0.14.1 on 4.09 had its build status changed: passing to partially failing
accessor_async.v0.14.1 on 4.10 had its build status changed: passing to partially failing
accessor_async.v0.14.1 on 4.11 had its build status changed: passing to partially failing
accessor_async.v0.15.0 on 4.11 had its build status changed: passing to partially failing
accessor_async.v0.15.0 on 4.12 had its build status changed: passing to partially failing
accessor_async.v0.15.0 on 4.13 had its build status changed: passing to partially failing
accessor_async.v0.15.0 on 4.14 had its build status changed: passing to partially failing
accessor_async.v0.15.0 on 5.0 had its build status changed: passing to partially failing
accessor_async.v0.16.0 on 4.14 is now installable. Current state is: partially failing
accessor_async.v0.16.0 on 5.0 is now installable. Current state is: partially failing
accessor_async.v0.16.0 on 5.1 is now installable. Current state is: partially failing
accessor_base.v0.14.0 on 4.09 had its build status changed: passing to partially failing
accessor_base.v0.14.0 on 4.10 had its build status changed: passing to partially failing
accessor_base.v0.14.0 on 4.11 had its build status changed: passing to partially failing
accessor_base.v0.14.0 on 4.12 had its build status changed: passing to partially failing
accessor_base.v0.14.0 on 4.13 had its build status changed: passing to partially failing
accessor_base.v0.14.0 on 4.14 had its build status changed: passing to partially failing
accessor_base.v0.14.0 on 5.0 had its build status changed: passing to partially failing
accessor_base.v0.14.0 on 5.1 is now installable. Current state is: partially failing
accessor_base.v0.14.1 on 4.09 had its build status changed: passing to partially failing
accessor_base.v0.14.1 on 4.10 had its build status changed: passing to partially failing
accessor_base.v0.14.1 on 4.11 had its build status changed: passing to partially failing
accessor_base.v0.14.1 on 4.12 had its build status changed: passing to partially failing
accessor_base.v0.14.1 on 4.13 had its build status changed: passing to partially failing
accessor_base.v0.14.1 on 4.14 had its build status changed: passing to partially failing
accessor_base.v0.15.0 on 4.10 had its build status changed: passing to partially failing
accessor_base.v0.15.0 on 4.11 had its build status changed: passing to partially failing
accessor_base.v0.15.0 on 4.12 had its build status changed: passing to partially failing
accessor_base.v0.15.0 on 4.13 had its build status changed: passing to partially failing
accessor_base.v0.15.0 on 4.14 had its build status changed: passing to partially failing
accessor_base.v0.15.0 on 5.0 had its build status changed: passing to partially failing
accessor_base.v0.16.0 on 4.14 is now installable. Current state is: partially failing
accessor_base.v0.16.0 on 5.0 is now installable. Current state is: partially failing
accessor_base.v0.16.0 on 5.1 is now installable. Current state is: partially failing
accessor_core.v0.14.0 on 4.09 had its build status changed: passing to partially failing
accessor_core.v0.14.0 on 4.10 had its build status changed: passing to partially failing
accessor_core.v0.14.0 on 4.11 had its build status changed: passing to partially failing
accessor_core.v0.14.0 on 4.12 had its build status changed: passing to partially failing
accessor_core.v0.14.0 on 4.13 had its build status changed: passing to partially failing
accessor_core.v0.14.0 on 4.14 had its build status changed: passing to partially failing
accessor_core.v0.14.0 on 5.0 had its build status changed: passing to partially failing
accessor_core.v0.14.0 on 5.1 is now installable. Current state is: partially failing
accessor_core.v0.14.1 on 4.09 had its build status changed: passing to partially failing
accessor_core.v0.14.1 on 4.10 had its build status changed: passing to partially failing
accessor_core.v0.14.1 on 4.11 had its build status changed: passing to partially failing
accessor_core.v0.15.0 on 4.11 had its build status changed: passing to partially failing
accessor_core.v0.15.0 on 4.12 had its build status changed: passing to partially failing
accessor_core.v0.15.0 on 4.13 had its build status changed: passing to partially failing
accessor_core.v0.15.0 on 4.14 had its build status changed: passing to partially failing
accessor_core.v0.15.0 on 5.0 had its build status changed: passing to partially failing
accessor_core.v0.16.0 on 4.14 is now installable. Current state is: partially failing
accessor_core.v0.16.0 on 5.0 is now installable. Current state is: partially failing
accessor_core.v0.16.0 on 5.1 is now installable. Current state is: partially failing
acgtk.1.5.0 on 4.12 had its build status changed: passing to partially failing
acgtk.1.5.0 on 4.13 had its build status changed: passing to partially failing
acgtk.1.5.0 on 4.14 had its build status changed: passing to partially failing
acgtk.1.5.1 on 4.08 had its build status changed: passing to partially failing
acgtk.1.5.1 on 4.09 had its build status changed: passing to partially failing
acgtk.1.5.1 on 4.10 had its build status changed: passing to partially failing
acgtk.1.5.1 on 4.11 had its build status changed: passing to partially failing
acgtk.1.5.1 on 4.12 had its build status changed: passing to partially failing
acgtk.1.5.1 on 4.13 had its build status changed: passing to partially failing
acgtk.1.5.1 on 4.14 had its build status changed: passing to partially failing
acgtk.1.5.1 on 5.0 had its build status changed: passing to partially failing
acgtk.2.0.0 on 4.14 is now installable. Current state is: partially failing
acgtk.2.0.0 on 5.0 is now installable. Current state is: partially failing
acgtk.2.0.0 on 5.1 is now installable. Current state is: partially failing
aches-lwt.1.0.0 on 4.08 had its build status changed: passing to partially failing
aches-lwt.1.0.0 on 4.09 had its build status changed: passing to partially failing
aches-lwt.1.0.0 on 4.10 had its build status changed: passing to partially failing
aches-lwt.1.0.0 on 4.11 had its build status changed: passing to partially failing
aches-lwt.1.0.0 on 4.12 had its build status changed: passing to partially failing
aches-lwt.1.0.0 on 4.13 had its build status changed: passing to partially failing
aches-lwt.1.0.0 on 4.14 had its build status changed: passing to partially failing
aches-lwt.1.0.0 on 5.0 had its build status changed: passing to partially failing
aches-lwt.1.0.0 on 5.1 is now installable. Current state is: partially failing
aches.1.0.0 on 4.08 had its build status changed: passing to partially failing
aches.1.0.0 on 4.09 had its build status changed: passing to partially failing
aches.1.0.0 on 4.10 had its build status changed: passing to partially failing
aches.1.0.0 on 4.11 had its build status changed: passing to partially failing
aches.1.0.0 on 4.12 had its build status changed: passing to partially failing
aches.1.0.0 on 4.13 had its build status changed: passing to partially failing
aches.1.0.0 on 4.14 had its build status changed: passing to partially failing
aches.1.0.0 on 5.0 had its build status changed: passing to partially failing
aches.1.0.0 on 5.1 is now installable. Current state is: partially failing
acp4.1.0.1 on 4.08 is now installable. Current state is: partially failing
acp4.1.0.1 on 4.09 is now installable. Current state is: partially failing
acp4.1.0.1 on 4.10 is now installable. Current state is: partially failing
acp4.1.0.1 on 4.11 is now installable. Current state is: partially failing
acp4.1.0.1 on 4.12 is now installable. Current state is: partially failing
acp4.1.0.1 on 4.13 is now installable. Current state is: partially failing
acp4.1.0.1 on 4.14 is now installable. Current state is: partially failing
acp4.1.0.1 on 5.0 is now installable. Current state is: partially failing
acp4.1.0.1 on 5.1 is now installable. Current state is: partially failing
acpc.1.1.1 on 4.08 had its build status changed: passing to partially failing
acpc.1.1.1 on 4.09 had its build status changed: passing to partially failing
acpc.1.1.1 on 4.10 had its build status changed: passing to partially failing
acpc.1.1.1 on 4.11 had its build status changed: passing to partially failing
acpc.1.1.1 on 4.12 had its build status changed: passing to partially failing
acpc.1.1.1 on 4.13 had its build status changed: passing to partially failing
acpc.1.1.1 on 4.14 had its build status changed: passing to partially failing
acpc.1.2.3 on 4.08 had its build status changed: passing to partially failing
acpc.1.2.3 on 4.09 had its build status changed: passing to partially failing
acpc.1.2.3 on 4.10 had its build status changed: passing to partially failing
acpc.1.2.3 on 4.11 had its build status changed: passing to partially failing
acpc.1.2.3 on 4.12 had its build status changed: passing to partially failing
acpc.1.2.3 on 4.13 had its build status changed: passing to partially failing
acpc.1.2.3 on 4.14 had its build status changed: passing to partially failing
acpc.2.0.0 on 5.0 is now installable. Current state is: partially failing
acpc.2.0.0 on 5.1 is now installable. Current state is: partially failing
advi.2.0.0 on 4.11 had its build status changed: passing to partially failing
advi.2.0.0 on 4.12 had its build status changed: passing to partially failing
advi.2.0.0 on 4.13 had its build status changed: passing to partially failing
advi.2.0.0 on 4.14 had its build status changed: passing to partially failing
afl-persistent.1.4 on 4.08 is now installable. Current state is: partially failing
afl-persistent.1.4 on 4.09 is now installable. Current state is: partially failing
afl-persistent.1.4 on 4.10 is now installable. Current state is: partially failing
afl-persistent.1.4 on 4.11 is now installable. Current state is: partially failing
afl-persistent.1.4 on 4.12 is now installable. Current state is: partially failing
afl-persistent.1.4 on 4.13 is now installable. Current state is: partially failing
afl-persistent.1.4 on 4.14 is now installable. Current state is: partially failing
afl-persistent.1.4 on 5.0 is now installable. Current state is: partially failing
afl-persistent.1.4 on 5.1 is now installable. Current state is: partially failing
agrid.0.1 on 4.08 had its build status changed: passing to partially failing
agrid.0.1 on 4.09 had its build status changed: passing to partially failing
agrid.0.1 on 4.10 had its build status changed: passing to partially failing
agrid.0.1 on 4.11 had its build status changed: passing to partially failing
agrid.0.1 on 4.12 had its build status changed: passing to partially failing
agrid.0.1 on 4.13 had its build status changed: passing to partially failing
agrid.0.1 on 4.14 had its build status changed: passing to partially failing
agrid.0.1 on 5.0 had its build status changed: passing to partially failing
agrid.0.1 on 5.1 is now installable. Current state is: partially failing
ahrocksdb.0.2.0 on 4.08 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.0 on 4.09 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.0 on 4.10 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.0 on 4.11 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.0 on 4.12 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.0 on 4.13 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.0 on 4.14 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.0 on 5.0 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.0 on 5.1 is now installable. Current state is: partially failing
ahrocksdb.0.2.1 on 4.08 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.1 on 4.09 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.1 on 4.10 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.1 on 4.11 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.1 on 4.12 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.1 on 4.13 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.1 on 4.14 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.1 on 5.0 had its build status changed: internal failure to partially failing
ahrocksdb.0.2.1 on 5.1 is now installable. Current state is: partially failing
ahrocksdb.0.2.2 on 4.08 had its build status changed: failing to partially failing
ahrocksdb.0.2.2 on 4.09 had its build status changed: failing to partially failing
ahrocksdb.0.2.2 on 4.10 had its build status changed: failing to partially failing
ahrocksdb.0.2.2 on 4.11 had its build status changed: failing to partially failing
ahrocksdb.0.2.2 on 4.12 had its build status changed: failing to partially failing
ahrocksdb.0.2.2 on 4.13 had its build status changed: failing to partially failing
ahrocksdb.0.2.2 on 4.14 had its build status changed: failing to partially failing
ahrocksdb.0.2.2 on 5.0 had its build status changed: failing to partially failing
ahrocksdb.0.2.2 on 5.1 is now installable. Current state is: partially failing
aifad.2.1.0 on 4.08 had its build status changed: passing to partially failing
aifad.2.1.0 on 4.09 had its build status changed: passing to partially failing
aifad.2.1.0 on 4.10 had its build status changed: passing to partially failing
aifad.2.1.0 on 4.11 had its build status changed: passing to partially failing
aifad.2.1.0 on 4.12 had its build status changed: passing to partially failing
aifad.2.1.0 on 4.13 had its build status changed: passing to partially failing
aifad.2.1.0 on 4.14 had its build status changed: passing to partially failing
aifad.2.2.1 on 4.08 had its build status changed: passing to partially failing
aifad.2.2.1 on 4.09 had its build status changed: passing to partially failing
aifad.2.2.1 on 4.10 had its build status changed: passing to partially failing
aifad.2.2.1 on 4.11 had its build status changed: passing to partially failing
aifad.2.2.1 on 4.12 had its build status changed: passing to partially failing
aifad.2.2.1 on 4.13 had its build status changed: passing to partially failing
aifad.2.2.1 on 4.14 had its build status changed: passing to partially failing
aifad.2.2.1 on 5.0 had its build status changed: passing to partially failing
aifad.2.2.1 on 5.1 is now installable. Current state is: partially failing
aifad.2.2.2 on 4.08 had its build status changed: passing to partially failing
aifad.2.2.2 on 4.09 had its build status changed: passing to partially failing
aifad.2.2.2 on 4.10 had its build status changed: passing to partially failing
aifad.2.2.2 on 4.11 had its build status changed: passing to partially failing
aifad.2.2.2 on 4.12 had its build status changed: passing to partially failing
aifad.2.2.2 on 4.13 had its build status changed: passing to partially failing
aifad.2.2.2 on 4.14 had its build status changed: passing to partially failing
aifad.2.2.2 on 5.0 had its build status changed: passing to partially failing
aifad.2.2.2 on 5.1 is now installable. Current state is: partially failing
aifad.2.3.0 on 4.08 had its build status changed: passing to partially failing
aifad.2.3.0 on 4.09 had its build status changed: passing to partially failing
aifad.2.3.0 on 4.10 had its build status changed: passing to partially failing
aifad.2.3.0 on 4.11 had its build status changed: passing to partially failing
aifad.2.3.0 on 4.12 had its build status changed: passing to partially failing
aifad.2.3.0 on 4.13 had its build status changed: passing to partially failing
aifad.2.3.0 on 4.14 had its build status changed: passing to partially failing
aifad.2.3.0 on 5.0 had its build status changed: passing to partially failing
aifad.2.3.0 on 5.1 is now installable. Current state is: partially failing
alba.0.4.0 on 4.08 had its build status changed: passing to partially failing
alba.0.4.0 on 4.09 had its build status changed: passing to partially failing
alba.0.4.0 on 4.10 had its build status changed: passing to partially failing
alba.0.4.0 on 4.11 had its build status changed: passing to partially failing
alba.0.4.0 on 4.12 had its build status changed: passing to partially failing
alba.0.4.0 on 4.13 had its build status changed: passing to partially failing
alba.0.4.0 on 4.14 had its build status changed: passing to partially failing
alba.0.4.1 on 4.08 had its build status changed: passing to partially failing
alba.0.4.1 on 4.09 had its build status changed: passing to partially failing
alba.0.4.1 on 4.10 had its build status changed: passing to partially failing
alba.0.4.1 on 4.11 had its build status changed: passing to partially failing
alba.0.4.1 on 4.12 had its build status changed: passing to partially failing
alba.0.4.1 on 4.13 had its build status changed: passing to partially failing
alba.0.4.1 on 4.14 had its build status changed: passing to partially failing
alba.0.4.2 on 4.08 had its build status changed: passing to partially failing
alba.0.4.2 on 4.09 had its build status changed: passing to partially failing
alba.0.4.2 on 4.10 had its build status changed: passing to partially failing
alba.0.4.2 on 4.11 had its build status changed: passing to partially failing
alba.0.4.2 on 4.12 had its build status changed: passing to partially failing
alba.0.4.2 on 4.13 had its build status changed: passing to partially failing
alba.0.4.2 on 4.14 had its build status changed: passing to partially failing
alba.0.4.3 on 4.08 had its build status changed: passing to partially failing
alba.0.4.3 on 4.09 had its build status changed: passing to partially failing
alba.0.4.3 on 4.10 had its build status changed: passing to partially failing
alba.0.4.3 on 4.11 had its build status changed: passing to partially failing
alba.0.4.3 on 4.12 had its build status changed: passing to partially failing
alba.0.4.3 on 4.13 had its build status changed: passing to partially failing
alba.0.4.3 on 4.14 had its build status changed: passing to partially failing
alba.0.4.4 on 4.08 had its build status changed: passing to partially failing
alba.0.4.4 on 4.09 had its build status changed: passing to partially failing
alba.0.4.4 on 4.10 had its build status changed: passing to partially failing
alba.0.4.4 on 4.11 had its build status changed: passing to partially failing
alba.0.4.4 on 4.12 had its build status changed: passing to partially failing
alba.0.4.4 on 4.13 had its build status changed: passing to partially failing
alba.0.4.4 on 4.14 had its build status changed: passing to partially failing
alba.0.4.4 on 5.0 had its build status changed: not available to partially failing
alba.0.4.4 on 5.1 is now installable. Current state is: partially failing
albatross.1.0.1 on 4.08 had its build status changed: passing to partially failing
albatross.1.0.1 on 4.09 had its build status changed: passing to partially failing
albatross.1.0.1 on 4.10 had its build status changed: passing to partially failing
albatross.1.0.1 on 4.11 had its build status changed: passing to partially failing
albatross.1.0.1 on 4.12 had its build status changed: passing to partially failing
albatross.1.0.1 on 4.13 had its build status changed: passing to partially failing
albatross.1.0.1 on 4.14 had its build status changed: passing to partially failing
albatross.1.0.1 on 5.0 had its build status changed: passing to partially failing
albatross.1.0.1 on 5.1 is now installable. Current state is: partially failing
albatross.1.1.0 on 4.08 had its build status changed: passing to partially failing
albatross.1.1.0 on 4.09 had its build status changed: passing to partially failing
albatross.1.1.0 on 4.10 had its build status changed: passing to partially failing
albatross.1.1.0 on 4.11 had its build status changed: passing to partially failing
albatross.1.1.0 on 4.12 had its build status changed: passing to partially failing
albatross.1.1.0 on 4.13 had its build status changed: passing to partially failing
albatross.1.1.0 on 4.14 had its build status changed: passing to partially failing
albatross.1.1.0 on 5.0 had its build status changed: passing to partially failing
albatross.1.1.0 on 5.1 is now installable. Current state is: partially failing
albatross.1.1.1 on 4.08 had its build status changed: passing to partially failing
albatross.1.1.1 on 4.09 had its build status changed: passing to partially failing
albatross.1.1.1 on 4.10 had its build status changed: passing to partially failing
albatross.1.1.1 on 4.11 had its build status changed: passing to partially failing
albatross.1.1.1 on 4.12 had its build status changed: passing to partially failing
albatross.1.1.1 on 4.13 had its build status changed: passing to partially failing
albatross.1.1.1 on 4.14 had its build status changed: passing to partially failing
albatross.1.1.1 on 5.0 had its build status changed: passing to partially failing
albatross.1.1.1 on 5.1 is now installable. Current state is: partially failing
albatross.1.2.0 on 4.08 had its build status changed: passing to partially failing
albatross.1.2.0 on 4.09 had its build status changed: passing to partially failing
albatross.1.2.0 on 4.10 had its build status changed: passing to partially failing
albatross.1.2.0 on 4.11 had its build status changed: passing to partially failing
albatross.1.2.0 on 4.12 had its build status changed: passing to partially failing
albatross.1.2.0 on 4.13 had its build status changed: passing to partially failing
albatross.1.2.0 on 4.14 had its build status changed: passing to partially failing
albatross.1.2.0 on 5.0 had its build status changed: passing to partially failing
albatross.1.2.0 on 5.1 is now installable. Current state is: partially failing
albatross.1.3.0 on 4.10 had its build status changed: passing to partially failing
albatross.1.3.0 on 4.11 had its build status changed: passing to partially failing
albatross.1.3.0 on 4.12 had its build status changed: passing to partially failing
albatross.1.3.0 on 4.13 had its build status changed: passing to partially failing
albatross.1.3.0 on 4.14 had its build status changed: passing to partially failing
albatross.1.3.1 on 4.10 had its build status changed: passing to partially failing
albatross.1.3.1 on 4.11 had its build status changed: passing to partially failing
albatross.1.3.1 on 4.12 had its build status changed: passing to partially failing
albatross.1.3.1 on 4.13 had its build status changed: passing to partially failing
albatross.1.3.1 on 4.14 had its build status changed: passing to partially failing
albatross.1.4.0 on 4.10 had its build status changed: passing to partially failing
albatross.1.4.0 on 4.11 had its build status changed: passing to partially failing
albatross.1.4.0 on 4.12 had its build status changed: passing to partially failing
albatross.1.4.0 on 4.13 had its build status changed: passing to partially failing
albatross.1.4.0 on 4.14 had its build status changed: passing to partially failing
albatross.1.4.1 on 4.10 had its build status changed: passing to partially failing
albatross.1.4.1 on 4.11 had its build status changed: passing to partially failing
albatross.1.4.1 on 4.12 had its build status changed: passing to partially failing
albatross.1.4.1 on 4.13 had its build status changed: passing to partially failing
albatross.1.4.1 on 4.14 had its build status changed: passing to partially failing
albatross.1.4.2 on 4.10 had its build status changed: passing to partially failing
albatross.1.4.2 on 4.11 had its build status changed: passing to partially failing
albatross.1.4.2 on 4.12 had its build status changed: passing to partially failing
albatross.1.4.2 on 4.13 had its build status changed: passing to partially failing
albatross.1.4.2 on 4.14 had its build status changed: passing to partially failing
albatross.1.4.3 on 4.10 had its build status changed: passing to partially failing
albatross.1.4.3 on 4.11 had its build status changed: passing to partially failing
albatross.1.4.3 on 4.12 had its build status changed: passing to partially failing
albatross.1.4.3 on 4.13 had its build status changed: passing to partially failing
albatross.1.4.3 on 4.14 had its build status changed: passing to partially failing
albatross.1.4.3 on 5.0 had its build status changed: passing to partially failing
albatross.1.4.3 on 5.1 is now installable. Current state is: partially failing
albatross.1.5.0 on 4.12 had its build status changed: passing to partially failing
albatross.1.5.0 on 4.13 had its build status changed: passing to partially failing
albatross.1.5.0 on 4.14 had its build status changed: passing to partially failing
albatross.1.5.0 on 5.0 had its build status changed: passing to partially failing
albatross.1.5.0 on 5.1 is now installable. Current state is: partially failing
albatross.1.5.1 on 4.12 had its build status changed: passing to partially failing
albatross.1.5.1 on 4.13 had its build status changed: passing to partially failing
albatross.1.5.1 on 4.14 had its build status changed: passing to partially failing
albatross.1.5.1 on 5.0 had its build status changed: passing to partially failing
albatross.1.5.1 on 5.1 is now installable. Current state is: partially failing
albatross.1.5.2 on 4.12 had its build status changed: passing to partially failing
albatross.1.5.2 on 4.13 had its build status changed: passing to partially failing
albatross.1.5.2 on 4.14 had its build status changed: passing to partially failing
albatross.1.5.2 on 5.0 had its build status changed: passing to partially failing
albatross.1.5.2 on 5.1 is now installable. Current state is: partially failing
albatross.1.5.3 on 4.12 is now installable. Current state is: partially failing
albatross.1.5.3 on 4.13 is now installable. Current state is: partially failing
albatross.1.5.3 on 4.14 is now installable. Current state is: partially failing
albatross.1.5.3 on 5.0 is now installable. Current state is: partially failing
albatross.1.5.3 on 5.1 is now installable. Current state is: partially failing
albatross.1.5.4 on 4.12 is now installable. Current state is: partially failing
albatross.1.5.4 on 4.13 is now installable. Current state is: partially failing
albatross.1.5.4 on 4.14 is now installable. Current state is: partially failing
albatross.1.5.4 on 5.0 is now installable. Current state is: partially failing
albatross.1.5.4 on 5.1 is now installable. Current state is: partially failing
albatross.1.5.5 on 4.12 is now installable. Current state is: partially failing
albatross.1.5.5 on 4.13 is now installable. Current state is: partially failing
albatross.1.5.5 on 4.14 is now installable. Current state is: partially failing
albatross.1.5.5 on 5.0 is now installable. Current state is: partially failing
albatross.1.5.5 on 5.1 is now installable. Current state is: partially failing
albatross.1.5.6 on 4.12 is now installable. Current state is: partially failing
albatross.1.5.6 on 4.13 is now installable. Current state is: partially failing
albatross.1.5.6 on 4.14 is now installable. Current state is: partially failing
albatross.1.5.6 on 5.0 is now installable. Current state is: partially failing
albatross.1.5.6 on 5.1 is now installable. Current state is: partially failing
albatross.2.0.0 on 4.12 is now installable. Current state is: partially failing
albatross.2.0.0 on 4.13 is now installable. Current state is: partially failing
albatross.2.0.0 on 4.14 is now installable. Current state is: partially failing
albatross.2.0.0 on 5.0 is now installable. Current state is: partially failing
albatross.2.0.0 on 5.1 is now installable. Current state is: partially failing
alcotest-async.0.8.2 on 4.12 had its build status changed: passing to partially failing
alcotest-async.0.8.2 on 4.13 had its build status changed: passing to partially failing
alcotest-async.0.8.2 on 4.14 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 4.08 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 4.09 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 4.10 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 4.11 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 4.12 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 4.13 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 4.14 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 5.0 had its build status changed: passing to partially failing
alcotest-async.0.8.5 on 5.1 is now installable. Current state is: partially failing
alcotest-async.1.0.0 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.0.0 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.0.0 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.0.0 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.0.0 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.0.0 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.0.0 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.0.1 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.0.1 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.0.1 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.0.1 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.0.1 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.0.1 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.0.1 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.1.0 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.1.0 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.1.0 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.1.0 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.1.0 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.1.0 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.1.0 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.2.0 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.2.0 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.2.0 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.2.0 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.2.0 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.2.0 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.2.0 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.2.1 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.2.1 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.2.1 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.2.1 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.2.1 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.2.1 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.2.1 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.2.2 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.2.2 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.2.2 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.2.2 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.2.2 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.2.2 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.2.2 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.2.3 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.2.3 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.2.3 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.2.3 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.2.3 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.2.3 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.2.3 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.3.0 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.3.0 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.3.0 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.3.0 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.3.0 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.3.0 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.3.0 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.4.0 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.4.0 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.4.0 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.4.0 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.4.0 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.4.0 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.4.0 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.5.0 on 4.08 had its build status changed: passing to partially failing
alcotest-async.1.5.0 on 4.09 had its build status changed: passing to partially failing
alcotest-async.1.5.0 on 4.10 had its build status changed: passing to partially failing
alcotest-async.1.5.0 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.5.0 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.5.0 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.5.0 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.6.0 on 4.11 had its build status changed: passing to partially failing
alcotest-async.1.6.0 on 4.12 had its build status changed: passing to partially failing
alcotest-async.1.6.0 on 4.13 had its build status changed: passing to partially failing
alcotest-async.1.6.0 on 4.14 had its build status changed: passing to partially failing
alcotest-async.1.6.0 on 5.0 had its build status changed: passing to partially failing
alcotest-async.1.7.0 on 4.11 is now installable. Current state is: partially failing
alcotest-async.1.7.0 on 4.12 is now installable. Current state is: partially failing
alcotest-async.1.7.0 on 4.13 is now installable. Current state is: partially failing
alcotest-async.1.7.0 on 4.14 is now installable. Current state is: partially failing
alcotest-async.1.7.0 on 5.0 is now installable. Current state is: partially failing
alcotest-js.1.5.0 on 4.08 had its build status changed: passing to partially failing
alcotest-js.1.5.0 on 4.09 had its build status changed: passing to partially failing
alcotest-js.1.5.0 on 4.10 had its build status changed: passing to partially failing
alcotest-js.1.5.0 on 4.11 had its build status changed: passing to partially failing
alcotest-js.1.5.0 on 4.12 had its build status changed: passing to partially failing
alcotest-js.1.5.0 on 4.13 had its build status changed: passing to partially failing
alcotest-js.1.5.0 on 4.14 had its build status changed: passing to partially failing
alcotest-js.1.5.0 on 5.0 had its build status changed: not available to partially failing
alcotest-js.1.5.0 on 5.1 is now installable. Current state is: partially failing
alcotest-js.1.6.0 on 4.08 had its build status changed: passing to partially failing
alcotest-js.1.6.0 on 4.09 had its build status changed: passing to partially failing
alcotest-js.1.6.0 on 4.10 had its build status changed: passing to partially failing
alcotest-js.1.6.0 on 4.11 had its build status changed: passing to partially failing
alcotest-js.1.6.0 on 4.12 had its build status changed: passing to partially failing
alcotest-js.1.6.0 on 4.13 had its build status changed: passing to partially failing
alcotest-js.1.6.0 on 4.14 had its build status changed: passing to partially failing
alcotest-js.1.6.0 on 5.0 had its build status changed: not available to partially failing
alcotest-js.1.6.0 on 5.1 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 4.08 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 4.09 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 4.10 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 4.11 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 4.12 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 4.13 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 4.14 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 5.0 is now installable. Current state is: partially failing
alcotest-js.1.7.0 on 5.1 is now installable. Current state is: partially failing
alcotest-lwt.0.8.0 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.0.8.0 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.0.8.0 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 5.0 had its build status changed: passing to partially failing
alcotest-lwt.0.8.5 on 5.1 is now installable. Current state is: partially failing
alcotest-lwt.1.0.0 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.0.0 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.0.0 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.0.0 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.0.0 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.0.0 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.0.0 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.0.0 on 5.0 had its build status changed: passing to partially failing
alcotest-lwt.1.0.0 on 5.1 is now installable. Current state is: partially failing
alcotest-lwt.1.0.1 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.0.1 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.0.1 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.0.1 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.0.1 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.0.1 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.0.1 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.0.1 on 5.0 had its build status changed: passing to partially failing
alcotest-lwt.1.0.1 on 5.1 is now installable. Current state is: partially failing
alcotest-lwt.1.1.0 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.1.0 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.1.0 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.1.0 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.1.0 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.1.0 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.1.0 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.2.0 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.2.0 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.2.0 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.2.0 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.2.0 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.2.0 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.2.0 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.2.1 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.2.1 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.2.1 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.2.1 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.2.1 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.2.1 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.2.1 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.2.2 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.2.2 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.2.2 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.2.2 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.2.2 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.2.2 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.2.2 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.2.3 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.2.3 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.2.3 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.2.3 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.2.3 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.2.3 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.2.3 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 5.0 had its build status changed: passing to partially failing
alcotest-lwt.1.3.0 on 5.1 is now installable. Current state is: partially failing
alcotest-lwt.1.4.0 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.4.0 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.4.0 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.4.0 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.4.0 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.4.0 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.4.0 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.4.0 on 5.0 had its build status changed: passing to partially failing
alcotest-lwt.1.4.0 on 5.1 is now installable. Current state is: partially failing
alcotest-lwt.1.5.0 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.5.0 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.5.0 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.5.0 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.5.0 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.5.0 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.5.0 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.5.0 on 5.0 had its build status changed: passing to partially failing
alcotest-lwt.1.5.0 on 5.1 is now installable. Current state is: partially failing
alcotest-lwt.1.6.0 on 4.08 had its build status changed: passing to partially failing
alcotest-lwt.1.6.0 on 4.09 had its build status changed: passing to partially failing
alcotest-lwt.1.6.0 on 4.10 had its build status changed: passing to partially failing
alcotest-lwt.1.6.0 on 4.11 had its build status changed: passing to partially failing
alcotest-lwt.1.6.0 on 4.12 had its build status changed: passing to partially failing
alcotest-lwt.1.6.0 on 4.13 had its build status changed: passing to partially failing
alcotest-lwt.1.6.0 on 4.14 had its build status changed: passing to partially failing
alcotest-lwt.1.6.0 on 5.0 had its build status changed: passing to partially failing
alcotest-lwt.1.6.0 on 5.1 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 4.08 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 4.09 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 4.10 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 4.11 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 4.12 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 4.13 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 4.14 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 5.0 is now installable. Current state is: partially failing
alcotest-lwt.1.7.0 on 5.1 is now installable. Current state is: partially failing
alcotest-mirage.1.2.0 on 4.08 had its build status changed: passing to partially failing
alcotest-mirage.1.2.0 on 4.09 had its build status changed: passing to partially failing
alcotest-mirage.1.2.0 on 4.10 had its build status changed: passing to partially failing
alcotest-mirage.1.2.0 on 4.11 had its build status changed: passing to partially failing
alcotest-mirage.1.2.0 on 4.12 had its build status changed: passing to partially failing
alcotest-mirage.1.2.0 on 4.13 had its build status changed: passing to partially failing
alcotest-mirage.1.2.0 on 4.14 had its build status changed: passing to partially failing
alcotest-mirage.1.2.1 on 4.08 had its build status changed: passing to partially failing
alcotest-mirage.1.2.1 on 4.09 had its build status changed: passing to partially failing
alcotest-mirage.1.2.1 on 4.10 had its build status changed: passing to partially failing
alcotest-mirage.1.2.1 on 4.11 had its build status changed: passing to partially failing
alcotest-mirage.1.2.1 on 4.12 had its build status changed: passing to partially failing
alcotest-mirage.1.2.1 on 4.13 had its build status changed: passing to partially failing
alcotest-mirage.1.2.1 on 4.14 had its build status changed: passing to partially failing
alcotest-mirage.1.2.2 on 4.08 had its build status changed: passing to partially failing
alcotest-mirage.1.2.2 on 4.09 had its build status changed: passing to partially failing
alcotest-mirage.1.2.2 on 4.10 had its build status changed: passing to partially failing
alcotest-mirage.1.2.2 on 4.11 had its build status changed: passing to partially failing
alcotest-mirage.1.2.2 on 4.12 had its build status changed: passing to partially failing
alcotest-mirage.1.2.2 on 4.13 had its build status changed: passing to partially failing
alcotest-mirage.1.2.2 on 4.14 had its build status changed: passing to partially failing
alcotest-mirage.1.2.3 on 4.08 had its build status changed: passing to partially failing
alcotest-mirage.1.2.3 on 4.09 had its build status changed: passing to partially failing
alcotest-mirage.1.2.3 on 4.10 had its build status changed: passing to partially failing
alcotest-mirage.1.2.3 on 4.11 had its build status changed: passing to partially failing
alcotest-mirage.1.2.3 on 4.12 had its build status changed: passing to partially failing
alcotest-mirage.1.2.3 on 4.13 had its build status changed: passing to partially failing
alcotest-mirage.1.2.3 on 4.14 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 4.08 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 4.09 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 4.10 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 4.11 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 4.12 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 4.13 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 4.14 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 5.0 had its build status changed: passing to partially failing
alcotest-mirage.1.3.0 on 5.1 is now installable. Current state is: partially failing
alcotest-mirage.1.4.0 on 4.08 had its build status changed: passing to partially failing
alcotest-mirage.1.4.0 on 4.09 had its build status changed: passing to partially failing
alcotest-mirage.1.4.0 on 4.10 had its build status changed: passing to partially failing
alcotest-mirage.1.4.0 on 4.11 had its build status changed: passing to partially failing
alcotest-mirage.1.4.0 on 4.12 had its build status changed: passing to partially failing
alcotest-mirage.1.4.0 on 4.13 had its build status changed: passing to partially failing
alcotest-mirage.1.4.0 on 4.14 had its build status changed: passing to partially failing
alcotest-mirage.1.4.0 on 5.0 had its build status changed: passing to partially failing
alcotest-mirage.1.4.0 on 5.1 is now installable. Current state is: partially failing
alcotest-mirage.1.5.0 on 4.08 had its build status changed: passing to partially failing
alcotest-mirage.1.5.0 on 4.09 had its build status changed: passing to partially failing
alcotest-mirage.1.5.0 on 4.10 had its build status changed: passing to partially failing
alcotest-mirage.1.5.0 on 4.11 had its build status changed: passing to partially failing
alcotest-mirage.1.5.0 on 4.12 had its build status changed: passing to partially failing
alcotest-mirage.1.5.0 on 4.13 had its build status changed: passing to partially failing
alcotest-mirage.1.5.0 on 4.14 had its build status changed: passing to partially failing
alcotest-mirage.1.5.0 on 5.0 had its build status changed: passing to partially failing
alcotest-mirage.1.5.0 on 5.1 is now installable. Current state is: partially failing
alcotest-mirage.1.6.0 on 4.08 had its build status changed: passing to partially failing
alcotest-mirage.1.6.0 on 4.09 had its build status changed: passing to partially failing
alcotest-mirage.1.6.0 on 4.10 had its build status changed: passing to partially failing
alcotest-mirage.1.6.0 on 4.11 had its build status changed: passing to partially failing
alcotest-mirage.1.6.0 on 4.12 had its build status changed: passing to partially failing
alcotest-mirage.1.6.0 on 4.13 had its build status changed: passing to partially failing
alcotest-mirage.1.6.0 on 4.14 had its build status changed: passing to partially failing
alcotest-mirage.1.6.0 on 5.0 had its build status changed: passing to partially failing
alcotest-mirage.1.6.0 on 5.1 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 4.08 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 4.09 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 4.10 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 4.11 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 4.12 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 4.13 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 4.14 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 5.0 is now installable. Current state is: partially failing
alcotest-mirage.1.7.0 on 5.1 is now installable. Current state is: partially failing
alcotest.0.8.0 on 4.12 had its build status changed: passing to partially failing
alcotest.0.8.0 on 4.13 had its build status changed: passing to partially failing
alcotest.0.8.1 on 4.12 had its build status changed: passing to partially failing
alcotest.0.8.1 on 4.13 had its build status changed: passing to partially failing
alcotest.0.8.3 on 4.12 had its build status changed: passing to partially failing
alcotest.0.8.3 on 4.13 had its build status changed: passing to partially failing
alcotest.0.8.4 on 4.12 had its build status changed: passing to partially failing
alcotest.0.8.4 on 4.13 had its build status changed: passing to partially failing
alcotest.0.8.5 on 4.08 had its build status changed: passing to partially failing
alcotest.0.8.5 on 4.09 had its build status changed: passing to partially failing
alcotest.0.8.5 on 4.10 had its build status changed: passing to partially failing
alcotest.0.8.5 on 4.11 had its build status changed: passing to partially failing
alcotest.0.8.5 on 4.12 had its build status changed: passing to partially failing
alcotest.0.8.5 on 4.13 had its build status changed: passing to partially failing
alcotest.1.0.0 on 4.08 had its build status changed: passing to partially failing
alcotest.1.0.0 on 4.09 had its build status changed: passing to partially failing
alcotest.1.0.0 on 4.10 had its build status changed: passing to partially failing
alcotest.1.0.0 on 4.11 had its build status changed: passing to partially failing
alcotest.1.0.0 on 4.12 had its build status changed: passing to partially failing
alcotest.1.0.0 on 4.13 had its build status changed: passing to partially failing
alcotest.1.0.0 on 4.14 had its build status changed: passing to partially failing
alcotest.1.0.0 on 5.0 had its build status changed: passing to partially failing
alcotest.1.0.0 on 5.1 is now installable. Current state is: partially failing
alcotest.1.0.1 on 4.08 had its build status changed: passing to partially failing
alcotest.1.0.1 on 4.09 had its build status changed: passing to partially failing
alcotest.1.0.1 on 4.10 had its build status changed: passing to partially failing
alcotest.1.0.1 on 4.11 had its build status changed: passing to partially failing
alcotest.1.0.1 on 4.12 had its build status changed: passing to partially failing
alcotest.1.0.1 on 4.13 had its build status changed: passing to partially failing
alcotest.1.0.1 on 4.14 had its build status changed: passing to partially failing
alcotest.1.0.1 on 5.0 had its build status changed: passing to partially failing
alcotest.1.0.1 on 5.1 is now installable. Current state is: partially failing
alcotest.1.1.0 on 4.08 had its build status changed: passing to partially failing
alcotest.1.1.0 on 4.09 had its build status changed: passing to partially failing
alcotest.1.1.0 on 4.10 had its build status changed: passing to partially failing
alcotest.1.1.0 on 4.11 had its build status changed: passing to partially failing
alcotest.1.1.0 on 4.12 had its build status changed: passing to partially failing
alcotest.1.1.0 on 4.13 had its build status changed: passing to partially failing
alcotest.1.1.0 on 4.14 had its build status changed: passing to partially failing
alcotest.1.2.0 on 4.08 had its build status changed: passing to partially failing
alcotest.1.2.0 on 4.09 had its build status changed: passing to partially failing
alcotest.1.2.0 on 4.10 had its build status changed: passing to partially failing
alcotest.1.2.0 on 4.11 had its build status changed: passing to partially failing
alcotest.1.2.0 on 4.12 had its build status changed: passing to partially failing
alcotest.1.2.0 on 4.13 had its build status changed: passing to partially failing
alcotest.1.2.0 on 4.14 had its build status changed: passing to partially failing
alcotest.1.2.1 on 4.08 had its build status changed: passing to partially failing
alcotest.1.2.1 on 4.09 had its build status changed: passing to partially failing
alcotest.1.2.1 on 4.10 had its build status changed: passing to partially failing
alcotest.1.2.1 on 4.11 had its build status changed: passing to partially failing
alcotest.1.2.1 on 4.12 had its build status changed: passing to partially failing
alcotest.1.2.1 on 4.13 had its build status changed: passing to partially failing
alcotest.1.2.1 on 4.14 had its build status changed: passing to partially failing
alcotest.1.2.2 on 4.08 had its build status changed: passing to partially failing
alcotest.1.2.2 on 4.09 had its build status changed: passing to partially failing
alcotest.1.2.2 on 4.10 had its build status changed: passing to partially failing
alcotest.1.2.2 on 4.11 had its build status changed: passing to partially failing
alcotest.1.2.2 on 4.12 had its build status changed: passing to partially failing
alcotest.1.2.2 on 4.13 had its build status changed: passing to partially failing
alcotest.1.2.2 on 4.14 had its build status changed: passing to partially failing
alcotest.1.2.3 on 4.08 had its build status changed: passing to partially failing
alcotest.1.2.3 on 4.09 had its build status changed: passing to partially failing
alcotest.1.2.3 on 4.10 had its build status changed: passing to partially failing
alcotest.1.2.3 on 4.11 had its build status changed: passing to partially failing
alcotest.1.2.3 on 4.12 had its build status changed: passing to partially failing
alcotest.1.2.3 on 4.13 had its build status changed: passing to partially failing
alcotest.1.2.3 on 4.14 had its build status changed: passing to partially failing
alcotest.1.3.0 on 4.08 had its build status changed: passing to partially failing
alcotest.1.3.0 on 4.09 had its build status changed: passing to partially failing
alcotest.1.3.0 on 4.10 had its build status changed: passing to partially failing
alcotest.1.3.0 on 4.11 had its build status changed: passing to partially failing
alcotest.1.3.0 on 4.12 had its build status changed: passing to partially failing
alcotest.1.3.0 on 4.13 had its build status changed: passing to partially failing
alcotest.1.3.0 on 4.14 had its build status changed: passing to partially failing
alcotest.1.3.0 on 5.0 had its build status changed: passing to partially failing
alcotest.1.3.0 on 5.1 is now installable. Current state is: partially failing
alcotest.1.4.0 on 4.08 had its build status changed: passing to partially failing
alcotest.1.4.0 on 4.09 had its build status changed: passing to partially failing
alcotest.1.4.0 on 4.10 had its build status changed: passing to partially failing
alcotest.1.4.0 on 4.11 had its build status changed: passing to partially failing
alcotest.1.4.0 on 4.12 had its build status changed: passing to partially failing
alcotest.1.4.0 on 4.13 had its build status changed: passing to partially failing
alcotest.1.4.0 on 4.14 had its build status changed: passing to partially failing
alcotest.1.4.0 on 5.0 had its build status changed: passing to partially failing
alcotest.1.4.0 on 5.1 is now installable. Current state is: partially failing
alcotest.1.5.0 on 4.08 had its build status changed: passing to partially failing
alcotest.1.5.0 on 4.09 had its build status changed: passing to partially failing
alcotest.1.5.0 on 4.10 had its build status changed: passing to partially failing
alcotest.1.5.0 on 4.11 had its build status changed: passing to partially failing
alcotest.1.5.0 on 4.12 had its build status changed: passing to partially failing
alcotest.1.5.0 on 4.13 had its build status changed: passing to partially failing
alcotest.1.5.0 on 4.14 had its build status changed: passing to partially failing
alcotest.1.5.0 on 5.0 had its build status changed: passing to partially failing
alcotest.1.5.0 on 5.1 is now installable. Current state is: partially failing
alcotest.1.6.0 on 4.08 had its build status changed: passing to partially failing
alcotest.1.6.0 on 4.09 had its build status changed: passing to partially failing
alcotest.1.6.0 on 4.10 had its build status changed: passing to partially failing
alcotest.1.6.0 on 4.11 had its build status changed: passing to partially failing
alcotest.1.6.0 on 4.12 had its build status changed: passing to partially failing
alcotest.1.6.0 on 4.13 had its build status changed: passing to partially failing
alcotest.1.6.0 on 4.14 had its build status changed: passing to partially failing
alcotest.1.6.0 on 5.0 had its build status changed: passing to partially failing
alcotest.1.6.0 on 5.1 is now installable. Current state is: partially failing
alcotest.1.7.0 on 4.08 is now installable. Current state is: partially failing
alcotest.1.7.0 on 4.09 is now installable. Current state is: partially failing
alcotest.1.7.0 on 4.10 is now installable. Current state is: partially failing
alcotest.1.7.0 on 4.11 is now installable. Current state is: partially failing
alcotest.1.7.0 on 4.12 is now installable. Current state is: partially failing
alcotest.1.7.0 on 4.13 is now installable. Current state is: partially failing
alcotest.1.7.0 on 4.14 is now installable. Current state is: partially failing
alcotest.1.7.0 on 5.0 is now installable. Current state is: partially failing
alcotest.1.7.0 on 5.1 is now installable. Current state is: partially failing
alg_structs.0.1.3 on 4.08 had its build status changed: passing to partially failing
alg_structs.0.1.3 on 4.09 had its build status changed: passing to partially failing
alg_structs.0.1.3 on 4.10 had its build status changed: passing to partially failing
alg_structs.0.1.3 on 4.11 had its build status changed: passing to partially failing
alg_structs.0.1.3 on 4.12 had its build status changed: passing to partially failing
alg_structs.0.1.3 on 4.13 had its build status changed: passing to partially failing
alg_structs.0.1.3 on 4.14 had its build status changed: passing to partially failing
alg_structs.0.1.3 on 5.0 had its build status changed: passing to partially failing
alg_structs.0.1.3 on 5.1 is now installable. Current state is: partially failing
alg_structs_qcheck.0.1.3 on 4.08 had its build status changed: passing to partially failing
alg_structs_qcheck.0.1.3 on 4.09 had its build status changed: passing to partially failing
alg_structs_qcheck.0.1.3 on 4.10 had its build status changed: passing to partially failing
alg_structs_qcheck.0.1.3 on 4.11 had its build status changed: passing to partially failing
alg_structs_qcheck.0.1.3 on 4.12 had its build status changed: passing to partially failing
alg_structs_qcheck.0.1.3 on 4.13 had its build status changed: passing to partially failing
alg_structs_qcheck.0.1.3 on 4.14 had its build status changed: passing to partially failing
alg_structs_qcheck.0.1.3 on 5.0 had its build status changed: passing to partially failing
alg_structs_qcheck.0.1.3 on 5.1 is now installable. Current state is: partially failing
algaeff.0.1.0 on 5.0 had its build status changed: passing to partially failing
algaeff.0.1.0 on 5.1 is now installable. Current state is: partially failing
algaeff.0.2.0 on 5.0 had its build status changed: passing to partially failing
algaeff.0.2.0 on 5.1 is now installable. Current state is: partially failing
algaeff.0.2.1 on 5.0 is now installable. Current state is: partially failing
algaeff.0.2.1 on 5.1 is now installable. Current state is: partially failing
algaeff.1.0.0 on 5.0 is now installable. Current state is: partially failing
algaeff.1.0.0 on 5.1 is now installable. Current state is: partially failing
algaeff.1.1.0 on 5.0 is now installable. Current state is: partially failing
algaeff.1.1.0 on 5.1 is now installable. Current state is: partially failing
algaeff.2.0.0 on 5.0 is now installable. Current state is: partially failing
algaeff.2.0.0 on 5.1 is now installable. Current state is: partially failing
alonzo.0.4.0 on 4.14 had its build status changed: passing to partially failing
alonzo.0.4.0 on 5.0 had its build status changed: passing to partially failing
alonzo.0.4.0 on 5.1 is now installable. Current state is: partially failing
alsa.0.3.0 on 4.08 had its build status changed: passing to partially failing
alsa.0.3.0 on 4.09 had its build status changed: passing to partially failing
alsa.0.3.0 on 4.10 had its build status changed: passing to partially failing
alsa.0.3.0 on 4.11 had its build status changed: passing to partially failing
alsa.0.3.0 on 4.12 had its build status changed: passing to partially failing
alsa.0.3.0 on 4.13 had its build status changed: passing to partially failing
alsa.0.3.0 on 4.14 had its build status changed: passing to partially failing
alsa.0.3.0 on 5.0 had its build status changed: passing to partially failing
alsa.0.3.0 on 5.1 is now installable. Current state is: partially failing
alt-ergo-free.2.0.0 on 4.08 had its build status changed: passing to partially failing
alt-ergo-free.2.0.0 on 4.09 had its build status changed: passing to partially failing
alt-ergo-free.2.0.0 on 4.10 had its build status changed: passing to partially failing
alt-ergo-free.2.0.0 on 4.11 had its build status changed: passing to partially failing
alt-ergo-free.2.0.0 on 4.12 had its build status changed: passing to partially failing
alt-ergo-free.2.0.0 on 4.13 had its build status changed: passing to partially failing
alt-ergo-free.2.0.0 on 4.14 had its build status changed: passing to partially failing
alt-ergo-free.2.2.0 on 4.08 had its build status changed: passing to partially failing
alt-ergo-free.2.2.0 on 4.09 had its build status changed: passing to partially failing
alt-ergo-free.2.2.0 on 4.10 had its build status changed: passing to partially failing
alt-ergo-free.2.2.0 on 4.11 had its build status changed: passing to partially failing
alt-ergo-free.2.2.0 on 4.12 had its build status changed: passing to partially failing
alt-ergo-free.2.2.0 on 4.13 had its build status changed: passing to partially failing
alt-ergo-free.2.2.0 on 4.14 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 4.08 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 4.09 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 4.10 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 4.11 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 4.12 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 4.13 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 4.14 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 5.0 had its build status changed: passing to partially failing
alt-ergo-lib.2.4.2 on 5.1 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 4.08 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 4.09 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 4.10 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 4.11 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 4.12 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 4.13 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 4.14 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 5.0 is now installable. Current state is: partially failing
alt-ergo-lib.2.4.3 on 5.1 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 4.08 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 4.09 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 4.10 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 4.11 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 4.12 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 4.13 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 4.14 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 5.0 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.0 on 5.1 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 4.08 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 4.09 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 4.10 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 4.11 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 4.12 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 4.13 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 4.14 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 5.0 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.1 on 5.1 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 4.08 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 4.09 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 4.10 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 4.11 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 4.12 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 4.13 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 4.14 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 5.0 is now installable. Current state is: partially failing
alt-ergo-lib.2.5.2 on 5.1 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.2 on 4.08 had its build status changed: passing to partially failing
alt-ergo-parsers.2.4.2 on 4.09 had its build status changed: passing to partially failing
alt-ergo-parsers.2.4.2 on 4.10 had its build status changed: passing to partially failing
alt-ergo-parsers.2.4.2 on 4.11 had its build status changed: passing to partially failing
alt-ergo-parsers.2.4.2 on 4.12 had its build status changed: passing to partially failing
alt-ergo-parsers.2.4.2 on 4.13 had its build status changed: passing to partially failing
alt-ergo-parsers.2.4.2 on 4.14 had its build status changed: passing to partially failing
alt-ergo-parsers.2.4.2 on 5.0 had its build status changed: passing to partially failing
alt-ergo-parsers.2.4.2 on 5.1 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 4.08 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 4.09 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 4.10 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 4.11 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 4.12 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 4.13 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 4.14 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 5.0 is now installable. Current state is: partially failing
alt-ergo-parsers.2.4.3 on 5.1 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 4.08 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 4.09 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 4.10 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 4.11 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 4.12 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 4.13 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 4.14 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 5.0 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.0 on 5.1 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 4.08 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 4.09 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 4.10 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 4.11 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 4.12 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 4.13 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 4.14 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 5.0 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.1 on 5.1 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 4.08 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 4.09 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 4.10 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 4.11 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 4.12 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 4.13 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 4.14 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 5.0 is now installable. Current state is: partially failing
alt-ergo-parsers.2.5.2 on 5.1 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 4.08 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 4.09 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 4.10 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 4.11 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 4.12 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 4.13 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 4.14 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 5.0 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.0 on 5.1 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 4.08 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 4.09 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 4.10 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 4.11 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 4.12 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 4.13 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 4.14 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 5.0 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.1 on 5.1 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 4.08 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 4.09 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 4.10 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 4.11 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 4.12 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 4.13 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 4.14 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 5.0 is now installable. Current state is: partially failing
alt-ergo-plugin-ab-why3.2.5.2 on 5.1 is now installable. Current state is: partially failing
alt-ergo.0.95.2 on 4.08 had its build status changed: passing to partially failing
alt-ergo.0.95.2 on 4.09 had its build status changed: passing to partially failing
alt-ergo.0.95.2 on 4.10 had its build status changed: passing to partially failing
alt-ergo.0.95.2 on 4.11 had its build status changed: passing to partially failing
alt-ergo.0.95.2 on 4.12 had its build status changed: passing to partially failing
alt-ergo.0.95.2 on 4.13 had its build status changed: passing to partially failing
alt-ergo.0.95.2 on 4.14 had its build status changed: passing to partially failing
alt-ergo.0.99.1 on 4.08 had its build status changed: passing to partially failing
alt-ergo.0.99.1 on 4.09 had its build status changed: passing to partially failing
alt-ergo.0.99.1 on 4.10 had its build status changed: passing to partially failing
alt-ergo.0.99.1 on 4.11 had its build status changed: passing to partially failing
alt-ergo.0.99.1 on 4.12 had its build status changed: passing to partially failing
alt-ergo.0.99.1 on 4.13 had its build status changed: passing to partially failing
alt-ergo.0.99.1 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.0.0 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.0.0 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.0.0 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.0.0 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.0.0 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.0.0 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.0.0 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.1.0 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.1.0 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.1.0 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.1.0 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.1.0 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.1.0 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.1.0 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.2.0 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.2.0 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.2.0 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.2.0 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.2.0 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.2.0 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.2.0 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.3.0 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.3.0 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.3.0 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.3.0 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.3.0 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.3.0 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.3.0 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.3.1 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.3.1 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.3.1 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.3.1 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.3.1 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.3.1 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.3.1 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.3.2 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.3.2 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.3.2 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.3.2 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.3.2 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.3.2 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.3.2 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.3.3 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.3.3 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.3.3 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.3.3 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.3.3 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.3.3 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.3.3 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.4.0 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.4.0 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.4.0 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.4.0 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.4.0 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.4.0 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.4.0 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.4.1 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.4.1 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.4.1 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.4.1 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.4.1 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.4.1 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.4.1 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 4.08 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 4.09 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 4.10 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 4.11 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 4.12 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 4.13 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 4.14 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 5.0 had its build status changed: passing to partially failing
alt-ergo.2.4.2 on 5.1 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 4.08 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 4.09 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 4.10 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 4.11 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 4.12 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 4.13 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 4.14 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 5.0 is now installable. Current state is: partially failing
alt-ergo.2.4.3 on 5.1 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 4.08 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 4.09 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 4.10 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 4.11 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 4.12 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 4.13 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 4.14 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 5.0 is now installable. Current state is: partially failing
alt-ergo.2.5.0 on 5.1 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 4.08 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 4.09 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 4.10 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 4.11 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 4.12 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 4.13 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 4.14 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 5.0 is now installable. Current state is: partially failing
alt-ergo.2.5.1 on 5.1 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 4.08 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 4.09 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 4.10 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 4.11 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 4.12 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 4.13 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 4.14 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 5.0 is now installable. Current state is: partially failing
alt-ergo.2.5.2 on 5.1 is now installable. Current state is: partially failing
altgr-ergo.2.4.2 on 4.08 had its build status changed: passing to partially failing
altgr-ergo.2.4.2 on 4.09 had its build status changed: passing to partially failing
altgr-ergo.2.4.2 on 4.10 had its build status changed: passing to partially failing
altgr-ergo.2.4.2 on 4.11 had its build status changed: passing to partially failing
altgr-ergo.2.4.2 on 4.12 had its build status changed: passing to partially failing
altgr-ergo.2.4.2 on 4.13 had its build status changed: passing to partially failing
altgr-ergo.2.4.2 on 4.14 had its build status changed: passing to partially failing
altgr-ergo.2.4.2 on 5.0 had its build status changed: passing to partially failing
altgr-ergo.2.4.2 on 5.1 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 4.08 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 4.09 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 4.10 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 4.11 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 4.12 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 4.13 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 4.14 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 5.0 is now installable. Current state is: partially failing
altgr-ergo.2.4.3 on 5.1 is now installable. Current state is: partially failing
ambient-context-eio.0.1.0 on 5.0 is now installable. Current state is: partially failing
ambient-context-eio.0.1.0 on 5.1 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 4.08 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 4.09 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 4.10 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 4.11 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 4.12 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 4.13 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 4.14 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 5.0 is now installable. Current state is: partially failing
ambient-context-lwt.0.1.0 on 5.1 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 4.08 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 4.09 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 4.10 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 4.11 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 4.12 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 4.13 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 4.14 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 5.0 is now installable. Current state is: partially failing
ambient-context.0.1.0 on 5.1 is now installable. Current state is: partially failing
amqp-client-async.2.0.3 on 4.08 had its build status changed: passing to partially failing
amqp-client-async.2.0.3 on 4.09 had its build status changed: passing to partially failing
amqp-client-async.2.0.3 on 4.10 had its build status changed: passing to partially failing
amqp-client-async.2.0.3 on 4.11 had its build status changed: passing to partially failing
amqp-client-async.2.0.3 on 4.12 had its build status changed: passing to partially failing
amqp-client-async.2.0.3 on 4.13 had its build status changed: passing to partially failing
amqp-client-async.2.0.3 on 4.14 had its build status changed: passing to partially failing
amqp-client-async.2.1.0 on 4.08 had its build status changed: passing to partially failing
amqp-client-async.2.1.0 on 4.09 had its build status changed: passing to partially failing
amqp-client-async.2.1.0 on 4.10 had its build status changed: passing to partially failing
amqp-client-async.2.1.0 on 4.11 had its build status changed: passing to partially failing
amqp-client-async.2.1.0 on 4.12 had its build status changed: passing to partially failing
amqp-client-async.2.1.0 on 4.13 had its build status changed: passing to partially failing
amqp-client-async.2.1.0 on 4.14 had its build status changed: passing to partially failing
amqp-client-async.2.2.0 on 4.08 had its build status changed: passing to partially failing
amqp-client-async.2.2.0 on 4.09 had its build status changed: passing to partially failing
amqp-client-async.2.2.0 on 4.10 had its build status changed: passing to partially failing
amqp-client-async.2.2.0 on 4.11 had its build status changed: passing to partially failing
amqp-client-async.2.2.0 on 4.12 had its build status changed: passing to partially failing
amqp-client-async.2.2.0 on 4.13 had its build status changed: passing to partially failing
amqp-client-async.2.2.0 on 4.14 had its build status changed: passing to partially failing
amqp-client-async.2.2.1 on 4.08 had its build status changed: passing to partially failing
amqp-client-async.2.2.1 on 4.09 had its build status changed: passing to partially failing
amqp-client-async.2.2.1 on 4.10 had its build status changed: passing to partially failing
amqp-client-async.2.2.1 on 4.11 had its build status changed: passing to partially failing
amqp-client-async.2.2.1 on 4.12 had its build status changed: passing to partially failing
amqp-client-async.2.2.1 on 4.13 had its build status changed: passing to partially failing
amqp-client-async.2.2.1 on 4.14 had its build status changed: passing to partially failing
amqp-client-async.2.2.2 on 4.08 had its build status changed: passing to partially failing
amqp-client-async.2.2.2 on 4.09 had its build status changed: passing to partially failing
amqp-client-async.2.2.2 on 4.10 had its build status changed: passing to partially failing
amqp-client-async.2.2.2 on 4.11 had its build status changed: passing to partially failing
amqp-client-async.2.2.2 on 4.12 had its build status changed: passing to partially failing
amqp-client-async.2.2.2 on 4.13 had its build status changed: passing to partially failing
amqp-client-async.2.2.2 on 4.14 had its build status changed: passing to partially failing
amqp-client-lwt.2.0.3 on 4.08 had its build status changed: passing to partially failing
amqp-client-lwt.2.0.3 on 4.09 had its build status changed: passing to partially failing
amqp-client-lwt.2.0.3 on 4.10 had its build status changed: passing to partially failing
amqp-client-lwt.2.0.3 on 4.11 had its build status changed: passing to partially failing
amqp-client-lwt.2.0.3 on 4.12 had its build status changed: passing to partially failing
amqp-client-lwt.2.0.3 on 4.13 had its build status changed: passing to partially failing
amqp-client-lwt.2.0.3 on 4.14 had its build status changed: passing to partially failing
amqp-client-lwt.2.0.3 on 5.1 is now installable. Current state is: partially failing
amqp-client-lwt.2.1.0 on 4.08 had its build status changed: passing to partially failing
amqp-client-lwt.2.1.0 on 4.09 had its build status changed: passing to partially failing
amqp-client-lwt.2.1.0 on 4.10 had its build status changed: passing to partially failing
amqp-client-lwt.2.1.0 on 4.11 had its build status changed: passing to partially failing
amqp-client-lwt.2.1.0 on 4.12 had its build status changed: passing to partially failing
amqp-client-lwt.2.1.0 on 4.13 had its build status changed: passing to partially failing
amqp-client-lwt.2.1.0 on 4.14 had its build status changed: passing to partially failing
amqp-client-lwt.2.1.0 on 5.1 is now installable. Current state is: partially failing
amqp-client-lwt.2.2.0 on 4.08 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.0 on 4.09 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.0 on 4.10 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.0 on 4.11 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.0 on 4.12 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.0 on 4.13 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.0 on 4.14 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.0 on 5.1 is now installable. Current state is: partially failing
amqp-client-lwt.2.2.1 on 4.08 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.1 on 4.09 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.1 on 4.10 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.1 on 4.11 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.1 on 4.12 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.1 on 4.13 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.1 on 4.14 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.1 on 5.1 is now installable. Current state is: partially failing
amqp-client-lwt.2.2.2 on 4.08 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.2 on 4.09 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.2 on 4.10 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.2 on 4.11 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.2 on 4.12 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.2 on 4.13 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.2 on 4.14 had its build status changed: passing to partially failing
amqp-client-lwt.2.2.2 on 5.1 is now installable. Current state is: partially failing
amqp-client.1.0.3 on 4.08 had its build status changed: passing to partially failing
amqp-client.1.0.3 on 4.09 had its build status changed: passing to partially failing
amqp-client.1.0.3 on 4.10 had its build status changed: passing to partially failing
amqp-client.1.0.3 on 4.11 had its build status changed: passing to partially failing
amqp-client.1.0.3 on 4.12 had its build status changed: passing to partially failing
amqp-client.1.0.3 on 4.13 had its build status changed: passing to partially failing
amqp-client.1.0.3 on 4.14 had its build status changed: passing to partially failing
amqp-client.1.0.3 on 5.0 had its build status changed: not available to partially failing
amqp-client.1.0.3 on 5.1 is now installable. Current state is: partially failing
amqp-client.1.0.4 on 4.08 had its build status changed: passing to partially failing
amqp-client.1.0.4 on 4.09 had its build status changed: passing to partially failing
amqp-client.1.0.4 on 4.10 had its build status changed: passing to partially failing
amqp-client.1.0.4 on 4.11 had its build status changed: passing to partially failing
amqp-client.1.0.4 on 4.12 had its build status changed: passing to partially failing
amqp-client.1.0.4 on 4.13 had its build status changed: passing to partially failing
amqp-client.1.0.4 on 4.14 had its build status changed: passing to partially failing
amqp-client.1.0.4 on 5.0 had its build status changed: not available to partially failing
amqp-client.1.0.4 on 5.1 is now installable. Current state is: partially failing
amqp-client.1.0.5 on 4.08 had its build status changed: passing to partially failing
amqp-client.1.0.5 on 4.09 had its build status changed: passing to partially failing
amqp-client.1.0.5 on 4.10 had its build status changed: passing to partially failing
amqp-client.1.0.5 on 4.11 had its build status changed: passing to partially failing
amqp-client.1.0.5 on 4.12 had its build status changed: passing to partially failing
amqp-client.1.0.5 on 4.13 had its build status changed: passing to partially failing
amqp-client.1.0.5 on 4.14 had its build status changed: passing to partially failing
amqp-client.1.0.5 on 5.0 had its build status changed: not available to partially failing
amqp-client.1.0.5 on 5.1 is now installable. Current state is: partially failing
amqp-client.1.0.6 on 4.08 had its build status changed: passing to partially failing
amqp-client.1.0.6 on 4.09 had its build status changed: passing to partially failing
amqp-client.1.0.6 on 4.10 had its build status changed: passing to partially failing
amqp-client.1.0.6 on 4.11 had its build status changed: passing to partially failing
amqp-client.1.0.6 on 4.12 had its build status changed: passing to partially failing
amqp-client.1.0.6 on 4.13 had its build status changed: passing to partially failing
amqp-client.1.0.6 on 4.14 had its build status changed: passing to partially failing
amqp-client.1.0.6 on 5.0 had its build status changed: not available to partially failing
amqp-client.1.0.6 on 5.1 is now installable. Current state is: partially failing
amqp-client.1.1.0 on 4.12 had its build status changed: passing to partially failing
amqp-client.1.1.0 on 4.13 had its build status changed: passing to partially failing
amqp-client.1.1.0 on 4.14 had its build status changed: passing to partially failing
amqp-client.1.1.2 on 4.12 had its build status changed: passing to partially failing
amqp-client.1.1.2 on 4.13 had its build status changed: passing to partially failing
amqp-client.1.1.2 on 4.14 had its build status changed: passing to partially failing
amqp-client.1.1.3 on 4.12 had its build status changed: passing to partially failing
amqp-client.1.1.3 on 4.13 had its build status changed: passing to partially failing
amqp-client.1.1.3 on 4.14 had its build status changed: passing to partially failing
amqp-client.1.1.4 on 4.12 had its build status changed: passing to partially failing
amqp-client.1.1.4 on 4.13 had its build status changed: passing to partially failing
amqp-client.1.1.4 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.0.0 on 4.12 had its build status changed: passing to partially failing
amqp-client.2.0.0 on 4.13 had its build status changed: passing to partially failing
amqp-client.2.0.0 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.0.1 on 4.12 had its build status changed: passing to partially failing
amqp-client.2.0.1 on 4.13 had its build status changed: passing to partially failing
amqp-client.2.0.1 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.0.2 on 4.12 had its build status changed: passing to partially failing
amqp-client.2.0.2 on 4.13 had its build status changed: passing to partially failing
amqp-client.2.0.2 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.0.3 on 4.08 had its build status changed: passing to partially failing
amqp-client.2.0.3 on 4.09 had its build status changed: passing to partially failing
amqp-client.2.0.3 on 4.10 had its build status changed: passing to partially failing
amqp-client.2.0.3 on 4.11 had its build status changed: passing to partially failing
amqp-client.2.0.3 on 4.12 had its build status changed: passing to partially failing
amqp-client.2.0.3 on 4.13 had its build status changed: passing to partially failing
amqp-client.2.0.3 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.0.3 on 5.1 is now installable. Current state is: partially failing
amqp-client.2.1.0 on 4.08 had its build status changed: passing to partially failing
amqp-client.2.1.0 on 4.09 had its build status changed: passing to partially failing
amqp-client.2.1.0 on 4.10 had its build status changed: passing to partially failing
amqp-client.2.1.0 on 4.11 had its build status changed: passing to partially failing
amqp-client.2.1.0 on 4.12 had its build status changed: passing to partially failing
amqp-client.2.1.0 on 4.13 had its build status changed: passing to partially failing
amqp-client.2.1.0 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.1.0 on 5.1 is now installable. Current state is: partially failing
amqp-client.2.2.0 on 4.08 had its build status changed: passing to partially failing
amqp-client.2.2.0 on 4.09 had its build status changed: passing to partially failing
amqp-client.2.2.0 on 4.10 had its build status changed: passing to partially failing
amqp-client.2.2.0 on 4.11 had its build status changed: passing to partially failing
amqp-client.2.2.0 on 4.12 had its build status changed: passing to partially failing
amqp-client.2.2.0 on 4.13 had its build status changed: passing to partially failing
amqp-client.2.2.0 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.2.0 on 5.1 is now installable. Current state is: partially failing
amqp-client.2.2.1 on 4.08 had its build status changed: passing to partially failing
amqp-client.2.2.1 on 4.09 had its build status changed: passing to partially failing
amqp-client.2.2.1 on 4.10 had its build status changed: passing to partially failing
amqp-client.2.2.1 on 4.11 had its build status changed: passing to partially failing
amqp-client.2.2.1 on 4.12 had its build status changed: passing to partially failing
amqp-client.2.2.1 on 4.13 had its build status changed: passing to partially failing
amqp-client.2.2.1 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.2.1 on 5.1 is now installable. Current state is: partially failing
amqp-client.2.2.2 on 4.08 had its build status changed: passing to partially failing
amqp-client.2.2.2 on 4.09 had its build status changed: passing to partially failing
amqp-client.2.2.2 on 4.10 had its build status changed: passing to partially failing
amqp-client.2.2.2 on 4.11 had its build status changed: passing to partially failing
amqp-client.2.2.2 on 4.12 had its build status changed: passing to partially failing
amqp-client.2.2.2 on 4.13 had its build status changed: passing to partially failing
amqp-client.2.2.2 on 4.14 had its build status changed: passing to partially failing
amqp-client.2.2.2 on 5.0 had its build status changed: passing to partially failing
amqp-client.2.2.2 on 5.1 is now installable. Current state is: partially failing
anders.0.12.1 on 4.10 had its build status changed: passing to partially failing
anders.0.12.1 on 4.11 had its build status changed: passing to partially failing
anders.0.12.1 on 4.12 had its build status changed: passing to partially failing
anders.0.12.1 on 4.13 had its build status changed: passing to partially failing
anders.0.12.1 on 4.14 had its build status changed: passing to partially failing
anders.0.12.1 on 5.0 had its build status changed: passing to partially failing
anders.0.12.1 on 5.1 is now installable. Current state is: partially failing
anders.0.7.1 on 4.10 had its build status changed: passing to partially failing
anders.0.7.1 on 4.11 had its build status changed: passing to partially failing
anders.0.7.1 on 4.12 had its build status changed: passing to partially failing
anders.0.7.1 on 4.13 had its build status changed: passing to partially failing
anders.0.7.1 on 4.14 had its build status changed: passing to partially failing
anders.0.7.1 on 5.0 had its build status changed: passing to partially failing
anders.0.7.1 on 5.1 is now installable. Current state is: partially failing
anders.0.7.2 on 4.10 had its build status changed: passing to partially failing
anders.0.7.2 on 4.11 had its build status changed: passing to partially failing
anders.0.7.2 on 4.12 had its build status changed: passing to partially failing
anders.0.7.2 on 4.13 had its build status changed: passing to partially failing
anders.0.7.2 on 4.14 had its build status changed: passing to partially failing
anders.0.7.2 on 5.0 had its build status changed: passing to partially failing
anders.0.7.2 on 5.1 is now installable. Current state is: partially failing
anders.1.1.1 on 4.10 had its build status changed: passing to partially failing
anders.1.1.1 on 4.11 had its build status changed: passing to partially failing
anders.1.1.1 on 4.12 had its build status changed: passing to partially failing
anders.1.1.1 on 4.13 had its build status changed: passing to partially failing
anders.1.1.1 on 4.14 had its build status changed: passing to partially failing
anders.1.1.1 on 5.0 had its build status changed: passing to partially failing
anders.1.1.1 on 5.1 is now installable. Current state is: partially failing
angstrom-async.0.10.0 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.10.0 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.10.0 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.11.0 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.11.0 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.11.0 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 4.08 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 4.09 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 4.10 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 4.11 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 5.0 had its build status changed: passing to partially failing
angstrom-async.0.11.1 on 5.1 is now installable. Current state is: partially failing
angstrom-async.0.11.2 on 4.08 had its build status changed: passing to partially failing
angstrom-async.0.11.2 on 4.09 had its build status changed: passing to partially failing
angstrom-async.0.11.2 on 4.10 had its build status changed: passing to partially failing
angstrom-async.0.11.2 on 4.11 had its build status changed: passing to partially failing
angstrom-async.0.11.2 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.11.2 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.11.2 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.11.2 on 5.0 had its build status changed: passing to partially failing
angstrom-async.0.11.2 on 5.1 is now installable. Current state is: partially failing
angstrom-async.0.12.1 on 4.08 had its build status changed: passing to partially failing
angstrom-async.0.12.1 on 4.09 had its build status changed: passing to partially failing
angstrom-async.0.12.1 on 4.10 had its build status changed: passing to partially failing
angstrom-async.0.12.1 on 4.11 had its build status changed: passing to partially failing
angstrom-async.0.12.1 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.12.1 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.12.1 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.12.1 on 5.0 had its build status changed: passing to partially failing
angstrom-async.0.12.1 on 5.1 is now installable. Current state is: partially failing
angstrom-async.0.13.0 on 4.08 had its build status changed: passing to partially failing
angstrom-async.0.13.0 on 4.09 had its build status changed: passing to partially failing
angstrom-async.0.13.0 on 4.10 had its build status changed: passing to partially failing
angstrom-async.0.13.0 on 4.11 had its build status changed: passing to partially failing
angstrom-async.0.13.0 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.13.0 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.13.0 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.13.0 on 5.0 had its build status changed: passing to partially failing
angstrom-async.0.13.0 on 5.1 is now installable. Current state is: partially failing
angstrom-async.0.14.0 on 4.08 had its build status changed: passing to partially failing
angstrom-async.0.14.0 on 4.09 had its build status changed: passing to partially failing
angstrom-async.0.14.0 on 4.10 had its build status changed: passing to partially failing
angstrom-async.0.14.0 on 4.11 had its build status changed: passing to partially failing
angstrom-async.0.14.0 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.14.0 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.14.0 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.14.0 on 5.0 had its build status changed: passing to partially failing
angstrom-async.0.14.0 on 5.1 is now installable. Current state is: partially failing
angstrom-async.0.14.1 on 4.08 had its build status changed: passing to partially failing
angstrom-async.0.14.1 on 4.09 had its build status changed: passing to partially failing
angstrom-async.0.14.1 on 4.10 had its build status changed: passing to partially failing
angstrom-async.0.14.1 on 4.11 had its build status changed: passing to partially failing
angstrom-async.0.14.1 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.14.1 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.14.1 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.14.1 on 5.0 had its build status changed: passing to partially failing
angstrom-async.0.14.1 on 5.1 is now installable. Current state is: partially failing
angstrom-async.0.15.0 on 4.08 had its build status changed: passing to partially failing
angstrom-async.0.15.0 on 4.09 had its build status changed: passing to partially failing
angstrom-async.0.15.0 on 4.10 had its build status changed: passing to partially failing
angstrom-async.0.15.0 on 4.11 had its build status changed: passing to partially failing
angstrom-async.0.15.0 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.15.0 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.15.0 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.15.0 on 5.0 had its build status changed: passing to partially failing
angstrom-async.0.15.0 on 5.1 is now installable. Current state is: partially failing
angstrom-async.0.7.0 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.7.0 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.7.0 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.8.0 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.8.0 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.8.0 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.8.1 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.8.1 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.8.1 on 4.14 had its build status changed: passing to partially failing
angstrom-async.0.9.0 on 4.12 had its build status changed: passing to partially failing
angstrom-async.0.9.0 on 4.13 had its build status changed: passing to partially failing
angstrom-async.0.9.0 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.10.0 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.10.0 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.10.0 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.0 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.0 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.0 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 4.08 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 4.09 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 4.10 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 4.11 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 5.0 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.1 on 5.1 is now installable. Current state is: partially failing
angstrom-lwt-unix.0.11.2 on 4.08 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.2 on 4.09 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.2 on 4.10 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.2 on 4.11 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.2 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.2 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.2 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.2 on 5.0 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.11.2 on 5.1 is now installable. Current state is: partially failing
angstrom-lwt-unix.0.12.1 on 4.08 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.12.1 on 4.09 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.12.1 on 4.10 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.12.1 on 4.11 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.12.1 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.12.1 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.12.1 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.12.1 on 5.0 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.12.1 on 5.1 is now installable. Current state is: partially failing
angstrom-lwt-unix.0.13.0 on 4.08 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.13.0 on 4.09 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.13.0 on 4.10 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.13.0 on 4.11 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.13.0 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.13.0 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.13.0 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.13.0 on 5.0 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.13.0 on 5.1 is now installable. Current state is: partially failing
angstrom-lwt-unix.0.14.0 on 4.08 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.0 on 4.09 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.0 on 4.10 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.0 on 4.11 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.0 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.0 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.0 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.0 on 5.0 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.0 on 5.1 is now installable. Current state is: partially failing
angstrom-lwt-unix.0.14.1 on 4.08 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.1 on 4.09 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.1 on 4.10 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.1 on 4.11 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.1 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.1 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.1 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.1 on 5.0 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.14.1 on 5.1 is now installable. Current state is: partially failing
angstrom-lwt-unix.0.15.0 on 4.08 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.15.0 on 4.09 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.15.0 on 4.10 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.15.0 on 4.11 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.15.0 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.15.0 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.15.0 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.15.0 on 5.0 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.15.0 on 5.1 is now installable. Current state is: partially failing
angstrom-lwt-unix.0.8.0 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.8.0 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.8.0 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.8.1 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.8.1 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.8.1 on 4.14 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.9.0 on 4.12 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.9.0 on 4.13 had its build status changed: passing to partially failing
angstrom-lwt-unix.0.9.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.10.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.10.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.10.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.11.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.11.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.11.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 4.08 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 4.09 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 4.10 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 4.11 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 5.0 had its build status changed: passing to partially failing
angstrom-unix.0.11.1 on 5.1 is now installable. Current state is: partially failing
angstrom-unix.0.11.2 on 4.08 had its build status changed: passing to partially failing
angstrom-unix.0.11.2 on 4.09 had its build status changed: passing to partially failing
angstrom-unix.0.11.2 on 4.10 had its build status changed: passing to partially failing
angstrom-unix.0.11.2 on 4.11 had its build status changed: passing to partially failing
angstrom-unix.0.11.2 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.11.2 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.11.2 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.11.2 on 5.0 had its build status changed: passing to partially failing
angstrom-unix.0.11.2 on 5.1 is now installable. Current state is: partially failing
angstrom-unix.0.12.1 on 4.08 had its build status changed: passing to partially failing
angstrom-unix.0.12.1 on 4.09 had its build status changed: passing to partially failing
angstrom-unix.0.12.1 on 4.10 had its build status changed: passing to partially failing
angstrom-unix.0.12.1 on 4.11 had its build status changed: passing to partially failing
angstrom-unix.0.12.1 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.12.1 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.12.1 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.12.1 on 5.0 had its build status changed: passing to partially failing
angstrom-unix.0.12.1 on 5.1 is now installable. Current state is: partially failing
angstrom-unix.0.13.0 on 4.08 had its build status changed: passing to partially failing
angstrom-unix.0.13.0 on 4.09 had its build status changed: passing to partially failing
angstrom-unix.0.13.0 on 4.10 had its build status changed: passing to partially failing
angstrom-unix.0.13.0 on 4.11 had its build status changed: passing to partially failing
angstrom-unix.0.13.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.13.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.13.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.13.0 on 5.0 had its build status changed: passing to partially failing
angstrom-unix.0.13.0 on 5.1 is now installable. Current state is: partially failing
angstrom-unix.0.14.0 on 4.08 had its build status changed: passing to partially failing
angstrom-unix.0.14.0 on 4.09 had its build status changed: passing to partially failing
angstrom-unix.0.14.0 on 4.10 had its build status changed: passing to partially failing
angstrom-unix.0.14.0 on 4.11 had its build status changed: passing to partially failing
angstrom-unix.0.14.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.14.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.14.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.14.0 on 5.0 had its build status changed: passing to partially failing
angstrom-unix.0.14.0 on 5.1 is now installable. Current state is: partially failing
angstrom-unix.0.14.1 on 4.08 had its build status changed: passing to partially failing
angstrom-unix.0.14.1 on 4.09 had its build status changed: passing to partially failing
angstrom-unix.0.14.1 on 4.10 had its build status changed: passing to partially failing
angstrom-unix.0.14.1 on 4.11 had its build status changed: passing to partially failing
angstrom-unix.0.14.1 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.14.1 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.14.1 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.14.1 on 5.0 had its build status changed: passing to partially failing
angstrom-unix.0.14.1 on 5.1 is now installable. Current state is: partially failing
angstrom-unix.0.15.0 on 4.08 had its build status changed: passing to partially failing
angstrom-unix.0.15.0 on 4.09 had its build status changed: passing to partially failing
angstrom-unix.0.15.0 on 4.10 had its build status changed: passing to partially failing
angstrom-unix.0.15.0 on 4.11 had its build status changed: passing to partially failing
angstrom-unix.0.15.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.15.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.15.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.15.0 on 5.0 had its build status changed: passing to partially failing
angstrom-unix.0.15.0 on 5.1 is now installable. Current state is: partially failing
angstrom-unix.0.6.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.6.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.6.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.7.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.7.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.7.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.8.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.8.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.8.0 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.8.1 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.8.1 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.8.1 on 4.14 had its build status changed: passing to partially failing
angstrom-unix.0.9.0 on 4.12 had its build status changed: passing to partially failing
angstrom-unix.0.9.0 on 4.13 had its build status changed: passing to partially failing
angstrom-unix.0.9.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.10.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.10.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.10.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.11.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.11.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.11.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.11.1 on 4.08 had its build status changed: passing to partially failing
angstrom.0.11.1 on 4.09 had its build status changed: passing to partially failing
angstrom.0.11.1 on 4.10 had its build status changed: passing to partially failing
angstrom.0.11.1 on 4.11 had its build status changed: passing to partially failing
angstrom.0.11.1 on 4.12 had its build status changed: passing to partially failing
angstrom.0.11.1 on 4.13 had its build status changed: passing to partially failing
angstrom.0.11.1 on 4.14 had its build status changed: passing to partially failing
angstrom.0.11.1 on 5.0 had its build status changed: passing to partially failing
angstrom.0.11.1 on 5.1 is now installable. Current state is: partially failing
angstrom.0.11.2 on 4.08 had its build status changed: passing to partially failing
angstrom.0.11.2 on 4.09 had its build status changed: passing to partially failing
angstrom.0.11.2 on 4.10 had its build status changed: passing to partially failing
angstrom.0.11.2 on 4.11 had its build status changed: passing to partially failing
angstrom.0.11.2 on 4.12 had its build status changed: passing to partially failing
angstrom.0.11.2 on 4.13 had its build status changed: passing to partially failing
angstrom.0.11.2 on 4.14 had its build status changed: passing to partially failing
angstrom.0.11.2 on 5.0 had its build status changed: passing to partially failing
angstrom.0.11.2 on 5.1 is now installable. Current state is: partially failing
angstrom.0.12.1 on 4.08 had its build status changed: passing to partially failing
angstrom.0.12.1 on 4.09 had its build status changed: passing to partially failing
angstrom.0.12.1 on 4.10 had its build status changed: passing to partially failing
angstrom.0.12.1 on 4.11 had its build status changed: passing to partially failing
angstrom.0.12.1 on 4.12 had its build status changed: passing to partially failing
angstrom.0.12.1 on 4.13 had its build status changed: passing to partially failing
angstrom.0.12.1 on 4.14 had its build status changed: passing to partially failing
angstrom.0.12.1 on 5.0 had its build status changed: passing to partially failing
angstrom.0.12.1 on 5.1 is now installable. Current state is: partially failing
angstrom.0.13.0 on 4.08 had its build status changed: passing to partially failing
angstrom.0.13.0 on 4.09 had its build status changed: passing to partially failing
angstrom.0.13.0 on 4.10 had its build status changed: passing to partially failing
angstrom.0.13.0 on 4.11 had its build status changed: passing to partially failing
angstrom.0.13.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.13.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.13.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.13.0 on 5.0 had its build status changed: passing to partially failing
angstrom.0.13.0 on 5.1 is now installable. Current state is: partially failing
angstrom.0.14.0 on 4.08 had its build status changed: passing to partially failing
angstrom.0.14.0 on 4.09 had its build status changed: passing to partially failing
angstrom.0.14.0 on 4.10 had its build status changed: passing to partially failing
angstrom.0.14.0 on 4.11 had its build status changed: passing to partially failing
angstrom.0.14.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.14.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.14.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.14.0 on 5.0 had its build status changed: passing to partially failing
angstrom.0.14.0 on 5.1 is now installable. Current state is: partially failing
angstrom.0.14.1 on 4.08 had its build status changed: passing to partially failing
angstrom.0.14.1 on 4.09 had its build status changed: passing to partially failing
angstrom.0.14.1 on 4.10 had its build status changed: passing to partially failing
angstrom.0.14.1 on 4.11 had its build status changed: passing to partially failing
angstrom.0.14.1 on 4.12 had its build status changed: passing to partially failing
angstrom.0.14.1 on 4.13 had its build status changed: passing to partially failing
angstrom.0.14.1 on 4.14 had its build status changed: passing to partially failing
angstrom.0.14.1 on 5.0 had its build status changed: passing to partially failing
angstrom.0.14.1 on 5.1 is now installable. Current state is: partially failing
angstrom.0.15.0 on 4.08 had its build status changed: passing to partially failing
angstrom.0.15.0 on 4.09 had its build status changed: passing to partially failing
angstrom.0.15.0 on 4.10 had its build status changed: passing to partially failing
angstrom.0.15.0 on 4.11 had its build status changed: passing to partially failing
angstrom.0.15.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.15.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.15.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.15.0 on 5.0 had its build status changed: passing to partially failing
angstrom.0.15.0 on 5.1 is now installable. Current state is: partially failing
angstrom.0.6.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.6.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.6.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.7.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.7.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.7.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.8.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.8.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.8.0 on 4.14 had its build status changed: passing to partially failing
angstrom.0.8.1 on 4.12 had its build status changed: passing to partially failing
angstrom.0.8.1 on 4.13 had its build status changed: passing to partially failing
angstrom.0.8.1 on 4.14 had its build status changed: passing to partially failing
angstrom.0.9.0 on 4.12 had its build status changed: passing to partially failing
angstrom.0.9.0 on 4.13 had its build status changed: passing to partially failing
angstrom.0.9.0 on 4.14 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 4.08 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 4.09 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 4.10 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 4.11 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 4.12 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 4.13 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 4.14 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 5.0 had its build status changed: passing to partially failing
ansi-parse.0.4.0 on 5.1 is now installable. Current state is: partially failing
ansi.0.5.0 on 4.10 had its build status changed: passing to partially failing
ansi.0.5.0 on 4.11 had its build status changed: passing to partially failing
ansi.0.5.0 on 4.12 had its build status changed: passing to partially failing
ansi.0.5.0 on 4.13 had its build status changed: passing to partially failing
ansi.0.5.0 on 4.14 had its build status changed: passing to partially failing
ansi.0.5.0 on 5.0 had its build status changed: passing to partially failing
ansi.0.5.0 on 5.1 is now installable. Current state is: partially failing
ansi.0.6.0 on 4.10 is now installable. Current state is: partially failing
ansi.0.6.0 on 4.11 is now installable. Current state is: partially failing
ansi.0.6.0 on 4.12 is now installable. Current state is: partially failing
ansi.0.6.0 on 4.13 is now installable. Current state is: partially failing
ansi.0.6.0 on 4.14 is now installable. Current state is: partially failing
ansi.0.6.0 on 5.0 is now installable. Current state is: partially failing
ansi.0.6.0 on 5.1 is now installable. Current state is: partially failing
ansi.0.7.0 on 4.10 is now installable. Current state is: partially failing
ansi.0.7.0 on 4.11 is now installable. Current state is: partially failing
ansi.0.7.0 on 4.12 is now installable. Current state is: partially failing
ansi.0.7.0 on 4.13 is now installable. Current state is: partially failing
ansi.0.7.0 on 4.14 is now installable. Current state is: partially failing
ansi.0.7.0 on 5.0 is now installable. Current state is: partially failing
ansi.0.7.0 on 5.1 is now installable. Current state is: partially failing
anthill.0.1 on 4.08 had its build status changed: passing to partially failing
anthill.0.1 on 4.09 had its build status changed: passing to partially failing
anthill.0.1 on 4.10 had its build status changed: passing to partially failing
anthill.0.1 on 4.11 had its build status changed: passing to partially failing
antic.0.3.2 on 4.10 is now installable. Current state is: partially failing
antic.0.3.2 on 4.11 is now installable. Current state is: partially failing
antic.0.3.2 on 4.12 is now installable. Current state is: partially failing
antic.0.3.2 on 4.13 is now installable. Current state is: partially failing
antic.0.3.2 on 4.14 is now installable. Current state is: partially failing
antic.0.3.2 on 5.0 is now installable. Current state is: partially failing
antic.0.3.2 on 5.1 is now installable. Current state is: partially failing
anycache-lwt.0.7.4 on 4.12 had its build status changed: passing to partially failing
anycache-lwt.0.7.4 on 4.13 had its build status changed: passing to partially failing
anycache-lwt.0.7.4 on 4.14 had its build status changed: passing to partially failing
anycache.0.6.0 on 4.08 had its build status changed: passing to partially failing
anycache.0.6.0 on 4.09 had its build status changed: passing to partially failing
anycache.0.6.0 on 4.10 had its build status changed: passing to partially failing
anycache.0.6.0 on 4.11 had its build status changed: passing to partially failing
anycache.0.6.0 on 4.12 had its build status changed: passing to partially failing
anycache.0.6.0 on 4.13 had its build status changed: passing to partially failing
anycache.0.6.0 on 4.14 had its build status changed: passing to partially failing
anycache.0.6.0 on 5.0 had its build status changed: passing to partially failing
anycache.0.6.0 on 5.1 is now installable. Current state is: partially failing
anycache.0.7.4 on 4.12 had its build status changed: passing to partially failing
anycache.0.7.4 on 4.13 had its build status changed: passing to partially failing
anycache.0.7.4 on 4.14 had its build status changed: passing to partially failing
ao.0.2.2 on 4.08 had its build status changed: passing to partially failing
ao.0.2.2 on 4.09 had its build status changed: passing to partially failing
ao.0.2.2 on 4.10 had its build status changed: passing to partially failing
ao.0.2.2 on 4.11 had its build status changed: passing to partially failing
ao.0.2.2 on 4.12 had its build status changed: passing to partially failing
ao.0.2.2 on 4.13 had its build status changed: passing to partially failing
ao.0.2.2 on 4.14 had its build status changed: passing to partially failing
ao.0.2.2 on 5.0 had its build status changed: passing to partially failing
ao.0.2.2 on 5.1 is now installable. Current state is: partially failing
ao.0.2.3 on 4.08 had its build status changed: passing to partially failing
ao.0.2.3 on 4.09 had its build status changed: passing to partially failing
ao.0.2.3 on 4.10 had its build status changed: passing to partially failing
ao.0.2.3 on 4.11 had its build status changed: passing to partially failing
ao.0.2.3 on 4.12 had its build status changed: passing to partially failing
ao.0.2.3 on 4.13 had its build status changed: passing to partially failing
ao.0.2.3 on 4.14 had its build status changed: passing to partially failing
ao.0.2.3 on 5.0 had its build status changed: passing to partially failing
ao.0.2.3 on 5.1 is now installable. Current state is: partially failing
ao.0.2.4 on 4.08 had its build status changed: passing to partially failing
ao.0.2.4 on 4.09 had its build status changed: passing to partially failing
ao.0.2.4 on 4.10 had its build status changed: passing to partially failing
ao.0.2.4 on 4.11 had its build status changed: passing to partially failing
ao.0.2.4 on 4.12 had its build status changed: passing to partially failing
ao.0.2.4 on 4.13 had its build status changed: passing to partially failing
ao.0.2.4 on 4.14 had its build status changed: passing to partially failing
ao.0.2.4 on 5.0 had its build status changed: passing to partially failing
ao.0.2.4 on 5.1 is now installable. Current state is: partially failing
apron.0.9.14 on 4.08 is now installable. Current state is: partially failing
apron.0.9.14 on 4.09 is now installable. Current state is: partially failing
apron.0.9.14 on 4.10 is now installable. Current state is: partially failing
apron.0.9.14 on 4.11 is now installable. Current state is: partially failing
apron.0.9.14 on 4.12 is now installable. Current state is: partially failing
apron.0.9.14 on 4.13 is now installable. Current state is: partially failing
apron.0.9.14 on 4.14 is now installable. Current state is: partially failing
apron.0.9.14 on 5.0 is now installable. Current state is: partially failing
apron.0.9.14 on 5.1 is now installable. Current state is: partially failing
apron.20150820 on 4.08 had its build status changed: passing to partially failing
apron.20150820 on 4.09 had its build status changed: passing to partially failing
apron.20150820 on 4.10 had its build status changed: passing to partially failing
apron.20150820 on 4.11 had its build status changed: passing to partially failing
apron.20150820 on 4.12 had its build status changed: passing to partially failing
apron.20150820 on 4.13 had its build status changed: passing to partially failing
apron.20150820 on 4.14 had its build status changed: passing to partially failing
apron.20150930 on 4.08 had its build status changed: passing to partially failing
apron.20150930 on 4.09 had its build status changed: passing to partially failing
apron.20150930 on 4.10 had its build status changed: passing to partially failing
apron.20150930 on 4.11 had its build status changed: passing to partially failing
apron.20150930 on 4.12 had its build status changed: passing to partially failing
apron.20150930 on 4.13 had its build status changed: passing to partially failing
apron.20150930 on 4.14 had its build status changed: passing to partially failing
apron.20151015 on 4.08 had its build status changed: passing to partially failing
apron.20151015 on 4.09 had its build status changed: passing to partially failing
apron.20151015 on 4.10 had its build status changed: passing to partially failing
apron.20151015 on 4.11 had its build status changed: passing to partially failing
apron.20151015 on 4.12 had its build status changed: passing to partially failing
apron.20151015 on 4.13 had its build status changed: passing to partially failing
apron.20151015 on 4.14 had its build status changed: passing to partially failing
apron.20160108 on 4.08 had its build status changed: passing to partially failing
apron.20160108 on 4.09 had its build status changed: passing to partially failing
apron.20160108 on 4.10 had its build status changed: passing to partially failing
apron.20160108 on 4.11 had its build status changed: passing to partially failing
apron.20160108 on 4.12 had its build status changed: passing to partially failing
apron.20160108 on 4.13 had its build status changed: passing to partially failing
apron.20160108 on 4.14 had its build status changed: passing to partially failing
apron.20160125 on 4.08 had its build status changed: passing to partially failing
apron.20160125 on 4.09 had its build status changed: passing to partially failing
apron.20160125 on 4.10 had its build status changed: passing to partially failing
apron.20160125 on 4.11 had its build status changed: passing to partially failing
apron.20160125 on 4.12 had its build status changed: passing to partially failing
apron.20160125 on 4.13 had its build status changed: passing to partially failing
apron.20160125 on 4.14 had its build status changed: passing to partially failing
apron.v0.9.12 on 4.08 had its build status changed: passing to partially failing
apron.v0.9.12 on 4.09 had its build status changed: passing to partially failing
apron.v0.9.12 on 4.10 had its build status changed: passing to partially failing
apron.v0.9.12 on 4.11 had its build status changed: passing to partially failing
apron.v0.9.12 on 4.12 had its build status changed: passing to partially failing
apron.v0.9.12 on 4.13 had its build status changed: passing to partially failing
apron.v0.9.12 on 4.14 had its build status changed: passing to partially failing
apron.v0.9.13 on 4.08 had its build status changed: passing to partially failing
apron.v0.9.13 on 4.09 had its build status changed: passing to partially failing
apron.v0.9.13 on 4.10 had its build status changed: passing to partially failing
apron.v0.9.13 on 4.11 had its build status changed: passing to partially failing
apron.v0.9.13 on 4.12 had its build status changed: passing to partially failing
apron.v0.9.13 on 4.13 had its build status changed: passing to partially failing
apron.v0.9.13 on 4.14 had its build status changed: passing to partially failing
apron.v0.9.14 on 4.08 is now installable. Current state is: partially failing
apron.v0.9.14 on 4.09 is now installable. Current state is: partially failing
apron.v0.9.14 on 4.10 is now installable. Current state is: partially failing
apron.v0.9.14 on 4.11 is now installable. Current state is: partially failing
apron.v0.9.14 on 4.12 is now installable. Current state is: partially failing
apron.v0.9.14 on 4.13 is now installable. Current state is: partially failing
apron.v0.9.14 on 4.14 is now installable. Current state is: partially failing
apron.v0.9.14 on 5.0 is now installable. Current state is: partially failing
apron.v0.9.14 on 5.1 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 4.08 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 4.09 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 4.10 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 4.11 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 4.12 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 4.13 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 4.14 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 5.0 is now installable. Current state is: partially failing
apron.v0.9.14~beta.2 on 5.1 is now installable. Current state is: partially failing
apronext.1.0 on 4.08 had its build status changed: passing to partially failing
apronext.1.0 on 4.09 had its build status changed: passing to partially failing
apronext.1.0 on 4.10 had its build status changed: passing to partially failing
apronext.1.0 on 4.11 had its build status changed: passing to partially failing
apronext.1.0 on 4.12 had its build status changed: passing to partially failing
apronext.1.0 on 4.13 had its build status changed: passing to partially failing
apronext.1.0 on 4.14 had its build status changed: passing to partially failing
apronext.1.0 on 5.0 had its build status changed: not available to partially failing
apronext.1.0 on 5.1 is now installable. Current state is: partially failing
apronext.1.0.1 on 4.08 had its build status changed: passing to partially failing
apronext.1.0.1 on 4.09 had its build status changed: passing to partially failing
apronext.1.0.1 on 4.10 had its build status changed: passing to partially failing
apronext.1.0.1 on 4.11 had its build status changed: passing to partially failing
apronext.1.0.1 on 4.12 had its build status changed: passing to partially failing
apronext.1.0.1 on 4.13 had its build status changed: passing to partially failing
apronext.1.0.1 on 4.14 had its build status changed: passing to partially failing
apronext.1.0.1 on 5.0 had its build status changed: not available to partially failing
apronext.1.0.1 on 5.1 is now installable. Current state is: partially failing
apronext.1.0.2 on 4.08 had its build status changed: passing to partially failing
apronext.1.0.2 on 4.09 had its build status changed: passing to partially failing
apronext.1.0.2 on 4.10 had its build status changed: passing to partially failing
apronext.1.0.2 on 4.11 had its build status changed: passing to partially failing
apronext.1.0.2 on 4.12 had its build status changed: passing to partially failing
apronext.1.0.2 on 4.13 had its build status changed: passing to partially failing
apronext.1.0.2 on 4.14 had its build status changed: passing to partially failing
apronext.1.0.2 on 5.0 had its build status changed: not available to partially failing
apronext.1.0.2 on 5.1 is now installable. Current state is: partially failing
apronext.1.0.3 on 4.08 had its build status changed: passing to partially failing
apronext.1.0.3 on 4.09 had its build status changed: passing to partially failing
apronext.1.0.3 on 4.10 had its build status changed: passing to partially failing
apronext.1.0.3 on 4.11 had its build status changed: passing to partially failing
apronext.1.0.3 on 4.12 had its build status changed: passing to partially failing
apronext.1.0.3 on 4.13 had its build status changed: passing to partially failing
apronext.1.0.3 on 4.14 had its build status changed: passing to partially failing
apronext.1.0.3 on 5.0 had its build status changed: not available to partially failing
apronext.1.0.3 on 5.1 is now installable. Current state is: partially failing
apronext.1.0.4 on 4.08 had its build status changed: passing to partially failing
apronext.1.0.4 on 4.09 had its build status changed: passing to partially failing
apronext.1.0.4 on 4.10 had its build status changed: passing to partially failing
apronext.1.0.4 on 4.11 had its build status changed: passing to partially failing
apronext.1.0.4 on 4.12 had its build status changed: passing to partially failing
apronext.1.0.4 on 4.13 had its build status changed: passing to partially failing
apronext.1.0.4 on 4.14 had its build status changed: passing to partially failing
apronext.1.0.4 on 5.0 had its build status changed: not available to partially failing
apronext.1.0.4 on 5.1 is now installable. Current state is: partially failing
arb.0.3.2 on 4.10 is now installable. Current state is: partially failing
arb.0.3.2 on 4.11 is now installable. Current state is: partially failing
arb.0.3.2 on 4.12 is now installable. Current state is: partially failing
arb.0.3.2 on 4.13 is now installable. Current state is: partially failing
arb.0.3.2 on 4.14 is now installable. Current state is: partially failing
arb.0.3.2 on 5.0 is now installable. Current state is: partially failing
arb.0.3.2 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.10 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.10 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.10 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.10 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.10 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.10 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.10 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.10 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.10 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.11 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.11 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.11 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.11 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.11 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.11 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.11 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.11 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.11 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.12 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.12 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.12 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.12 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.12 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.12 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.12 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.12 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.12 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.13 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.13 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.13 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.13 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.13 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.13 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.13 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.13 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.13 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.14 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.14 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.14 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.14 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.14 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.14 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.14 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.14 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.14 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.3 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.3 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.3 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.3 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.3 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.3 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.3 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.4 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.4 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.4 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.4 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.4 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.4 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.4 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.4 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.4 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.5 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.5 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.5 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.5 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.5 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.5 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.5 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.5 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.5 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.6 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.6 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.6 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.6 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.6 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.6 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.6 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.6 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.6 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.8 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.8 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.8 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.8 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.8 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.8 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.8 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.8 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.8 on 5.1 is now installable. Current state is: partially failing
archetype.0.1.9 on 4.08 had its build status changed: passing to partially failing
archetype.0.1.9 on 4.09 had its build status changed: passing to partially failing
archetype.0.1.9 on 4.10 had its build status changed: passing to partially failing
archetype.0.1.9 on 4.11 had its build status changed: passing to partially failing
archetype.0.1.9 on 4.12 had its build status changed: passing to partially failing
archetype.0.1.9 on 4.13 had its build status changed: passing to partially failing
archetype.0.1.9 on 4.14 had its build status changed: passing to partially failing
archetype.0.1.9 on 5.0 had its build status changed: passing to partially failing
archetype.0.1.9 on 5.1 is now installable. Current state is: partially failing
archetype.1.0.0 on 4.08 had its build status changed: passing to partially failing
archetype.1.0.0 on 4.09 had its build status changed: passing to partially failing
archetype.1.0.0 on 4.10 had its build status changed: passing to partially failing
archetype.1.0.0 on 4.11 had its build status changed: passing to partially failing
archetype.1.0.0 on 4.12 had its build status changed: passing to partially failing
archetype.1.0.0 on 4.13 had its build status changed: passing to partially failing
archetype.1.0.0 on 4.14 had its build status changed: passing to partially failing
archetype.1.0.0 on 5.0 had its build status changed: passing to partially failing
archetype.1.0.0 on 5.1 is now installable. Current state is: partially failing
archetype.1.1.0 on 4.08 had its build status changed: passing to partially failing
archetype.1.1.0 on 4.09 had its build status changed: passing to partially failing
archetype.1.1.0 on 4.10 had its build status changed: passing to partially failing
archetype.1.1.0 on 4.11 had its build status changed: passing to partially failing
archetype.1.1.0 on 4.12 had its build status changed: passing to partially failing
archetype.1.1.0 on 4.13 had its build status changed: passing to partially failing
archetype.1.1.0 on 4.14 had its build status changed: passing to partially failing
archetype.1.1.0 on 5.0 had its build status changed: passing to partially failing
archetype.1.1.0 on 5.1 is now installable. Current state is: partially failing
archetype.1.1.1 on 4.08 had its build status changed: passing to partially failing
archetype.1.1.1 on 4.09 had its build status changed: passing to partially failing
archetype.1.1.1 on 4.10 had its build status changed: passing to partially failing
archetype.1.1.1 on 4.11 had its build status changed: passing to partially failing
archetype.1.1.1 on 4.12 had its build status changed: passing to partially failing
archetype.1.1.1 on 4.13 had its build status changed: passing to partially failing
archetype.1.1.1 on 4.14 had its build status changed: passing to partially failing
archetype.1.1.1 on 5.0 had its build status changed: passing to partially failing
archetype.1.1.1 on 5.1 is now installable. Current state is: partially failing
archetype.1.1.2 on 4.08 had its build status changed: passing to partially failing
archetype.1.1.2 on 4.09 had its build status changed: passing to partially failing
archetype.1.1.2 on 4.10 had its build status changed: passing to partially failing
archetype.1.1.2 on 4.11 had its build status changed: passing to partially failing
archetype.1.1.2 on 4.12 had its build status changed: passing to partially failing
archetype.1.1.2 on 4.13 had its build status changed: passing to partially failing
archetype.1.1.2 on 4.14 had its build status changed: passing to partially failing
archetype.1.1.2 on 5.0 had its build status changed: passing to partially failing
archetype.1.1.2 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.0 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.0 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.0 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.0 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.0 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.0 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.0 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.0 on 5.0 had its build status changed: passing to partially failing
archetype.1.2.0 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.1 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.1 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.1 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.1 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.1 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.1 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.1 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.1 on 5.0 had its build status changed: passing to partially failing
archetype.1.2.1 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.10 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.10 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.10 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.10 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.10 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.10 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.10 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.10 on 5.0 had its build status changed: not available to partially failing
archetype.1.2.10 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.11 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.11 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.11 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.11 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.11 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.11 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.11 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.11 on 5.0 had its build status changed: not available to partially failing
archetype.1.2.11 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.12 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.12 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.12 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.12 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.12 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.12 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.12 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.12 on 5.0 had its build status changed: not available to partially failing
archetype.1.2.12 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.13 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.13 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.13 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.13 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.13 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.13 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.13 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.13 on 5.0 had its build status changed: not available to partially failing
archetype.1.2.13 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.14 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.14 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.14 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.14 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.14 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.14 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.14 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.14 on 5.0 had its build status changed: not available to partially failing
archetype.1.2.14 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.15 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.15 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.15 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.15 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.15 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.15 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.15 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.15 on 5.0 had its build status changed: not available to partially failing
archetype.1.2.15 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.16 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.16 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.16 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.16 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.16 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.16 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.16 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.16 on 5.0 had its build status changed: not available to partially failing
archetype.1.2.16 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.2 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.2 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.2 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.2 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.2 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.2 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.2 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.2 on 5.0 had its build status changed: passing to partially failing
archetype.1.2.2 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.3 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.3 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.3 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.3 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.3 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.3 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.3 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.3 on 5.0 had its build status changed: passing to partially failing
archetype.1.2.3 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.4 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.4 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.4 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.4 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.4 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.4 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.4 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.4 on 5.0 had its build status changed: passing to partially failing
archetype.1.2.4 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.5 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.5 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.5 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.5 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.5 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.5 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.5 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.5 on 5.0 had its build status changed: passing to partially failing
archetype.1.2.5 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.6 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.6 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.6 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.6 on 4.11 had its build status changed: passing to partially failing
archetype.1.2.6 on 4.12 had its build status changed: passing to partially failing
archetype.1.2.6 on 4.13 had its build status changed: passing to partially failing
archetype.1.2.6 on 4.14 had its build status changed: passing to partially failing
archetype.1.2.6 on 5.0 had its build status changed: passing to partially failing
archetype.1.2.6 on 5.1 is now installable. Current state is: partially failing
archetype.1.2.7 on 4.08 had its build status changed: passing to partially failing
archetype.1.2.7 on 4.09 had its build status changed: passing to partially failing
archetype.1.2.7 on 4.10 had its build status changed: passing to partially failing
archetype.1.2.7 on 4.