opam-health-check diff

Home|Differences with the last checks|Previous runs

Differences between 3d81474 and cbef5a5 (git diff)

Packages now failing:

advi.2.0.0 on 5.0 had its build status changed: not available to failing
advi.2.0.0 on 5.1 had its build status changed: not available to failing
alt-ergo.2.0.0 on 4.08 had its build status changed: passing to failing
alt-ergo.2.0.0 on 4.12 had its build status changed: passing to failing
alt-ergo.2.0.0 on 4.13 had its build status changed: passing to failing
alt-ergo.2.1.0 on 4.08 had its build status changed: passing to failing
alt-ergo.2.1.0 on 4.09 had its build status changed: passing to failing
alt-ergo.2.2.0 on 4.10 had its build status changed: passing to failing
alt-ergo.2.2.0 on 4.13 had its build status changed: passing to failing
alt-ergo.2.2.0 on 4.14 had its build status changed: passing to failing
archimedes.0.4.18 on 5.0 had its build status changed: partially failing to failing
bisect.1.3.1 on 5.0 had its build status changed: partially failing to failing
calculon.0.3 on 4.08 had its build status changed: partially failing to failing
calculon.0.3 on 4.09 had its build status changed: partially failing to failing
calculon.0.3 on 4.10 had its build status changed: partially failing to failing
calculon.0.3 on 4.11 had its build status changed: partially failing to failing
calculon.0.4 on 4.08 had its build status changed: partially failing to failing
calculon.0.4 on 4.09 had its build status changed: partially failing to failing
calculon.0.4 on 4.10 had its build status changed: partially failing to failing
calculon.0.4 on 4.11 had its build status changed: partially failing to failing
cca.0.1 on 4.11 had its build status changed: partially failing to failing
cca.0.1 on 4.12 had its build status changed: partially failing to failing
cca.0.2 on 4.11 had its build status changed: partially failing to failing
cca.0.2 on 4.12 had its build status changed: partially failing to failing
cca.0.2 on 4.13 had its build status changed: partially failing to failing
cca.0.2 on 4.14 had its build status changed: partially failing to failing
cca.0.4 on 4.11 had its build status changed: partially failing to failing
cca.0.4 on 4.12 had its build status changed: partially failing to failing
cca.0.4 on 4.13 had its build status changed: partially failing to failing
cca.0.4 on 4.14 had its build status changed: partially failing to failing
cca.0.5 on 4.11 had its build status changed: partially failing to failing
cca.0.5 on 4.12 had its build status changed: partially failing to failing
cca.0.5 on 4.13 had its build status changed: partially failing to failing
cca.0.5 on 4.14 had its build status changed: partially failing to failing
cca.0.6.2 on 4.14 had its build status changed: partially failing to failing
coin.0.1.0 on 4.08 had its build status changed: partially failing to failing
conf-arb.1 on 4.08 had its build status changed: passing to failing
conf-arb.1 on 4.09 had its build status changed: passing to failing
conf-arb.1 on 4.10 had its build status changed: passing to failing
conf-arb.1 on 4.11 had its build status changed: passing to failing
conf-arb.1 on 4.12 had its build status changed: passing to failing
conf-arb.1 on 4.13 had its build status changed: passing to failing
conf-arb.1 on 4.14 had its build status changed: passing to failing
conf-arb.1 on 5.0 had its build status changed: passing to failing
conf-arb.1 on 5.1 had its build status changed: passing to failing
config-file.1.1 on 5.0 had its build status changed: partially failing to failing
config-file.1.2 on 5.0 had its build status changed: partially failing to failing
config-file.1.2.1 on 5.0 had its build status changed: partially failing to failing
cryptohash.0.1 on 5.0 had its build status changed: partially failing to failing
devkit.0.6 on 4.08 had its build status changed: partially failing to failing
devkit.0.6 on 4.09 had its build status changed: partially failing to failing
devkit.0.6 on 4.10 had its build status changed: partially failing to failing
devkit.0.6 on 4.11 had its build status changed: partially failing to failing
devkit.0.7 on 4.08 had its build status changed: partially failing to failing
devkit.0.7 on 4.09 had its build status changed: partially failing to failing
devkit.0.7 on 4.10 had its build status changed: partially failing to failing
devkit.0.7 on 4.11 had its build status changed: partially failing to failing
devkit.1.0 on 4.08 had its build status changed: partially failing to failing
devkit.1.0 on 4.09 had its build status changed: partially failing to failing
devkit.1.0 on 4.10 had its build status changed: partially failing to failing
devkit.1.0 on 4.11 had its build status changed: partially failing to failing
eliom.6.11.0 on 4.08 had its build status changed: partially failing to failing
eliom.6.11.0 on 4.09 had its build status changed: partially failing to failing
eliom.6.11.0 on 4.10 had its build status changed: partially failing to failing
eliom.6.12.0 on 4.08 had its build status changed: partially failing to failing
eliom.6.12.0 on 4.09 had its build status changed: partially failing to failing
eliom.6.12.0 on 4.10 had its build status changed: partially failing to failing
eliom.6.12.1 on 4.08 had its build status changed: partially failing to failing
eliom.6.12.1 on 4.09 had its build status changed: partially failing to failing
eliom.6.12.1 on 4.10 had its build status changed: partially failing to failing
eliom.6.12.1 on 4.11 had its build status changed: partially failing to failing
eliom.6.12.4 on 4.08 had its build status changed: partially failing to failing
eliom.6.12.4 on 4.09 had its build status changed: partially failing to failing
eliom.6.12.4 on 4.10 had its build status changed: partially failing to failing
eliom.6.12.4 on 4.11 had its build status changed: partially failing to failing
eliom.6.13.1 on 4.08 had its build status changed: partially failing to failing
eliom.6.13.1 on 4.09 had its build status changed: partially failing to failing
eliom.6.13.1 on 4.10 had its build status changed: partially failing to failing
eliom.6.13.1 on 4.11 had its build status changed: partially failing to failing
eliom.7.0.0 on 4.08 had its build status changed: partially failing to failing
eliom.7.0.0 on 4.09 had its build status changed: partially failing to failing
eliom.7.0.0 on 4.10 had its build status changed: partially failing to failing
eliom.7.0.0 on 4.11 had its build status changed: partially failing to failing
eliom.7.0.0 on 4.12 had its build status changed: partially failing to failing
esperanto.0.0.1 on 4.13 had its build status changed: passing to failing
extprot.1.7.0 on 5.0 had its build status changed: partially failing to failing
fm-simplex-plugin.1.01 on 4.09 had its build status changed: passing to failing
fm-simplex-plugin.1.01 on 4.12 had its build status changed: passing to failing
format.0.1 on 5.0 had its build status changed: partially failing to failing
functoria-runtime.2.1.0 on 4.11 had its build status changed: partially failing to failing
hacl-star-raw.0.1 on 4.08 had its build status changed: passing to failing
hacl-star-raw.0.1 on 4.14 had its build status changed: passing to failing
hacl-star-raw.0.1.1 on 4.08 had its build status changed: passing to failing
hacl-star-raw.0.1.1 on 4.10 had its build status changed: passing to failing
hacl-star-raw.0.2.0 on 4.11 had its build status changed: passing to failing
hacl-star-raw.0.2.0 on 4.14 had its build status changed: passing to failing
hacl-star-raw.0.2.2 on 4.12 had its build status changed: passing to failing
hacl-star-raw.0.2.2 on 4.13 had its build status changed: passing to failing
heptagon.1.03.03 on 5.0 had its build status changed: partially failing to failing
heptagon.1.03.04 on 5.0 had its build status changed: partially failing to failing
heptagon.1.04.00 on 5.0 had its build status changed: partially failing to failing
heptagon.1.05.00 on 5.0 had its build status changed: partially failing to failing
javalib.3.1 on 5.0 had its build status changed: partially failing to failing
jhupllib.0.1 on 4.08 had its build status changed: internal failure to failing
jhupllib.0.1 on 4.09 had its build status changed: internal failure to failing
jhupllib.0.1.1 on 4.08 had its build status changed: internal failure to failing
jhupllib.0.1.1 on 4.09 had its build status changed: internal failure to failing
jhupllib.0.2.1 on 4.08 had its build status changed: internal failure to failing
lascar.0.5 on 5.0 had its build status changed: partially failing to failing
lbvs_consent.2.1.1 on 4.08 had its build status changed: partially failing to failing
lbvs_consent.2.1.1 on 4.09 had its build status changed: partially failing to failing
lbvs_consent.2.1.1 on 4.10 had its build status changed: partially failing to failing
lbvs_consent.2.1.1 on 4.11 had its build status changed: partially failing to failing
lbvs_consent.2.1.1 on 4.12 had its build status changed: partially failing to failing
lbvs_consent.2.1.1 on 4.13 had its build status changed: partially failing to failing
lbvs_consent.2.1.1 on 4.14 had its build status changed: partially failing to failing
lbvs_consent.2.1.2 on 4.08 had its build status changed: partially failing to failing
lbvs_consent.2.1.2 on 4.09 had its build status changed: partially failing to failing
lbvs_consent.2.1.2 on 4.10 had its build status changed: partially failing to failing
lbvs_consent.2.1.2 on 4.11 had its build status changed: partially failing to failing
lbvs_consent.2.1.2 on 4.12 had its build status changed: partially failing to failing
lbvs_consent.2.1.2 on 4.13 had its build status changed: partially failing to failing
lbvs_consent.2.1.2 on 4.14 had its build status changed: partially failing to failing
mldonkey.3.1.7-2 on 4.08 had its build status changed: partially failing to failing
mldonkey.3.1.7-2 on 4.09 had its build status changed: partially failing to failing
objsize.0.18 on 5.0 had its build status changed: partially failing to failing
ocaml-protoc-plugin.0.9 on 4.08 had its build status changed: passing to failing
ocaml-protoc-plugin.0.9 on 4.09 had its build status changed: passing to failing
ocaml-protoc-plugin.0.9 on 4.10 had its build status changed: passing to failing
ocaml-protoc-plugin.0.9 on 4.11 had its build status changed: passing to failing
ocamldsort.0.15.0 on 4.14 had its build status changed: partially failing to failing
ocamldsort.0.15.0 on 5.0 had its build status changed: partially failing to failing
ocamldsort.0.16.0 on 5.0 had its build status changed: partially failing to failing
ocamlscript.2.0.2 on 5.0 had its build status changed: partially failing to failing
ocamlscript.2.0.4 on 5.0 had its build status changed: partially failing to failing
ocsigen-start.2.15.1 on 4.08 had its build status changed: partially failing to failing
ocsigen-start.2.15.1 on 4.09 had its build status changed: partially failing to failing
ocsigen-start.2.15.1 on 4.10 had its build status changed: partially failing to failing
ocsigen-start.2.16.0 on 4.08 had its build status changed: partially failing to failing
ocsigen-start.2.16.0 on 4.09 had its build status changed: partially failing to failing
ocsigen-start.2.16.0 on 4.10 had its build status changed: partially failing to failing
ocsigen-start.2.16.1 on 4.08 had its build status changed: partially failing to failing
ocsigen-start.2.16.1 on 4.09 had its build status changed: partially failing to failing
ocsigen-start.2.16.1 on 4.10 had its build status changed: partially failing to failing
owl-symbolic.0.1.0 on 4.08 had its build status changed: passing to failing
owl-symbolic.0.1.0 on 4.09 had its build status changed: passing to failing
owl-symbolic.0.1.0 on 4.10 had its build status changed: passing to failing
owl-symbolic.0.1.0 on 4.11 had its build status changed: passing to failing
owl-symbolic.0.1.0 on 4.12 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.08 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.09 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.10 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.11 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.12 had its build status changed: passing to failing
pa_comprehension.0.4 on 5.0 had its build status changed: partially failing to failing
pa_monad_custom.v6.0.0 on 5.0 had its build status changed: partially failing to failing
pa_ppx_ag.0.07.02 on 4.10 had its build status changed: partially failing to failing
pa_ppx_ag.0.07.02 on 4.11 had its build status changed: partially failing to failing
pa_ppx_ag.0.07.02 on 4.12 had its build status changed: partially failing to failing
pa_ppx_hashcons.0.07.02 on 4.10 had its build status changed: partially failing to failing
pa_ppx_hashcons.0.07.02 on 4.11 had its build status changed: partially failing to failing
pa_ppx_hashcons.0.07.02 on 4.12 had its build status changed: partially failing to failing
pa_ppx_migrate.0.07.02 on 4.10 had its build status changed: partially failing to failing
pa_ppx_migrate.0.07.02 on 4.11 had its build status changed: partially failing to failing
pa_ppx_migrate.0.07.02 on 4.12 had its build status changed: partially failing to failing
pa_ppx_unique.0.07.02 on 4.10 had its build status changed: partially failing to failing
pa_ppx_unique.0.07.02 on 4.11 had its build status changed: partially failing to failing
pa_ppx_unique.0.07.02 on 4.12 had its build status changed: partially failing to failing
pa_qualified.0.5 on 5.0 had its build status changed: partially failing to failing
pa_qualified.0.6 on 5.0 had its build status changed: partially failing to failing
pa_where.0.4 on 5.0 had its build status changed: partially failing to failing
portia.1.1 on 4.09 had its build status changed: passing to failing
portia.1.1 on 4.12 had its build status changed: passing to failing
portia.1.3 on 4.13 had its build status changed: passing to failing
portia.1.3 on 4.14 had its build status changed: passing to failing
portia.1.5 on 4.12 had its build status changed: passing to failing
portia.1.5 on 5.1 had its build status changed: internal failure to failing
proverif.1.98 on 5.0 had its build status changed: not available to failing
proverif.1.98 on 5.1 had its build status changed: not available to failing
proverif.1.98pl1 on 5.0 had its build status changed: not available to failing
proverif.1.98pl1 on 5.1 had its build status changed: not available to failing
proverif.2.00 on 5.0 had its build status changed: not available to failing
proverif.2.00 on 5.1 had its build status changed: not available to failing
solo5-cross-aarch64.0.7.1 on 4.08 had its build status changed: partially failing to failing
solo5.0.7.0 on 4.14 had its build status changed: internal failure to failing
stog.0.19.0 on 4.12 had its build status changed: partially failing to failing
tuareg.2.0.10 on 4.14 had its build status changed: passing to failing
tuareg.2.1.0 on 4.08 had its build status changed: passing to failing
tuareg.2.1.0 on 4.11 had its build status changed: passing to failing
type_conv.113.00.02 on 5.0 had its build status changed: partially failing to failing
uri.1.9.7 on 4.12 had its build status changed: passing to failing
uuuu.0.1.0 on 4.08 had its build status changed: partially failing to failing
volt.1.4 on 5.0 had its build status changed: partially failing to failing
z3.4.11.0 on 4.12 had its build status changed: passing to failing
z3.4.8.5-1 on 4.14 had its build status changed: passing to failing

Packages now partially failing:

arb.0.3.1 on 4.10 had its build status changed: passing to partially failing
arb.0.3.1 on 4.11 had its build status changed: passing to partially failing
arb.0.3.1 on 4.12 had its build status changed: passing to partially failing
arb.0.3.1 on 4.13 had its build status changed: passing to partially failing
arb.0.3.1 on 4.14 had its build status changed: passing to partially failing
arb.0.3.1 on 5.0 had its build status changed: passing to partially failing
arb.0.3.1 on 5.1 had its build status changed: passing to partially failing
arb.0.3.2 on 4.10 had its build status changed: passing to partially failing
arb.0.3.2 on 4.11 had its build status changed: passing to partially failing
arb.0.3.2 on 4.12 had its build status changed: passing to partially failing
arb.0.3.2 on 4.13 had its build status changed: passing to partially failing
arb.0.3.2 on 4.14 had its build status changed: passing to partially failing
arb.0.3.2 on 5.0 had its build status changed: passing to partially failing
arb.0.3.2 on 5.1 had its build status changed: passing to partially failing
fm-simplex-plugin.1.30 on 4.12 had its build status changed: passing to partially failing
hacl-star.0.1 on 4.08 had its build status changed: passing to partially failing
hacl-star.0.1.1 on 4.09 had its build status changed: passing to partially failing
hacl-star.0.1.1 on 4.10 had its build status changed: passing to partially failing
hacl-star.0.2.0 on 4.09 had its build status changed: passing to partially failing
hacl-star.0.2.1 on 4.12 had its build status changed: passing to partially failing
hacl-star.0.2.1 on 4.13 had its build status changed: passing to partially failing
lambdapi.2.0.0 on 4.11 had its build status changed: passing to partially failing
lambdapi.2.0.0 on 4.14 had its build status changed: passing to partially failing
links-mysql.0.9.8 on 4.14 is now installable. Current state is: partially failing
links-mysql.0.9.8 on 5.0 is now installable. Current state is: partially failing
links-mysql.0.9.8 on 5.1 is now installable. Current state is: partially failing
mirage-nat.2.0.0 on 4.08 had its build status changed: passing to partially failing
mirage-nat.2.0.0 on 4.09 had its build status changed: passing to partially failing
mirage-nat.2.0.0 on 4.10 had its build status changed: passing to partially failing
mirage-nat.2.0.0 on 4.11 had its build status changed: passing to partially failing
oplot.0.71 on 4.11 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.08 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.09 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.11 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.12 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.14 had its build status changed: passing to partially failing
satML-plugin.1.30 on 4.11 had its build status changed: passing to partially failing
why3-coq.1.3.3 on 4.11 had its build status changed: passing to partially failing

Packages now not available:

antic.0.3.1 on 4.10 is not available anymore. Previous state was: passing
antic.0.3.1 on 4.11 is not available anymore. Previous state was: passing
antic.0.3.1 on 4.12 is not available anymore. Previous state was: passing
antic.0.3.1 on 4.13 is not available anymore. Previous state was: passing
antic.0.3.1 on 4.14 is not available anymore. Previous state was: passing
antic.0.3.1 on 5.0 is not available anymore. Previous state was: passing
antic.0.3.1 on 5.1 is not available anymore. Previous state was: passing
antic.0.3.2 on 4.10 is not available anymore. Previous state was: passing
antic.0.3.2 on 4.11 is not available anymore. Previous state was: passing
antic.0.3.2 on 4.12 is not available anymore. Previous state was: passing
antic.0.3.2 on 4.13 is not available anymore. Previous state was: passing
antic.0.3.2 on 4.14 is not available anymore. Previous state was: passing
antic.0.3.2 on 5.0 is not available anymore. Previous state was: passing
antic.0.3.2 on 5.1 is not available anymore. Previous state was: passing
beluga.0.8.1 on 5.0 had its build status changed: partially failing to not available
beluga.0.8.2 on 5.0 had its build status changed: partially failing to not available
caisar.0.2 on 5.0 had its build status changed: partially failing to not available
caisar.0.2.1 on 5.0 had its build status changed: partially failing to not available
calcium.0.3.1 on 4.10 is not available anymore. Previous state was: passing
calcium.0.3.1 on 4.11 is not available anymore. Previous state was: passing
calcium.0.3.1 on 4.12 is not available anymore. Previous state was: passing
calcium.0.3.1 on 4.13 is not available anymore. Previous state was: passing
calcium.0.3.1 on 4.14 is not available anymore. Previous state was: passing
calcium.0.3.1 on 5.0 is not available anymore. Previous state was: passing
calcium.0.3.1 on 5.1 is not available anymore. Previous state was: passing
calcium.0.3.2 on 4.10 is not available anymore. Previous state was: passing
calcium.0.3.2 on 4.11 is not available anymore. Previous state was: passing
calcium.0.3.2 on 4.12 is not available anymore. Previous state was: passing
calcium.0.3.2 on 4.13 is not available anymore. Previous state was: passing
calcium.0.3.2 on 4.14 is not available anymore. Previous state was: passing
calcium.0.3.2 on 5.0 is not available anymore. Previous state was: passing
calcium.0.3.2 on 5.1 is not available anymore. Previous state was: passing
camlidl.1.10 on 5.0 had its build status changed: passing to not available
camlidl.1.10 on 5.1 had its build status changed: passing to not available
camlidl.1.11 on 5.0 had its build status changed: passing to not available
camlidl.1.11 on 5.1 had its build status changed: passing to not available
conf-antic.1 on 4.08 is not available anymore. Previous state was: passing
conf-antic.1 on 4.09 is not available anymore. Previous state was: passing
conf-antic.1 on 4.10 is not available anymore. Previous state was: passing
conf-antic.1 on 4.11 is not available anymore. Previous state was: passing
conf-antic.1 on 4.12 is not available anymore. Previous state was: passing
conf-antic.1 on 4.13 is not available anymore. Previous state was: passing
conf-antic.1 on 4.14 is not available anymore. Previous state was: passing
conf-antic.1 on 5.0 is not available anymore. Previous state was: passing
conf-antic.1 on 5.1 is not available anymore. Previous state was: passing
conf-calcium.1 on 4.08 is not available anymore. Previous state was: passing
conf-calcium.1 on 4.09 is not available anymore. Previous state was: passing
conf-calcium.1 on 4.10 is not available anymore. Previous state was: passing
conf-calcium.1 on 4.11 is not available anymore. Previous state was: passing
conf-calcium.1 on 4.12 is not available anymore. Previous state was: passing
conf-calcium.1 on 4.13 is not available anymore. Previous state was: passing
conf-calcium.1 on 4.14 is not available anymore. Previous state was: passing
conf-calcium.1 on 5.0 is not available anymore. Previous state was: passing
conf-calcium.1 on 5.1 is not available anymore. Previous state was: passing
containers-data.3.10 on 5.1 had its build status changed: passing to not available
containers-data.3.9 on 5.1 had its build status changed: passing to not available
ctypes-zarith.0.1.0 on 5.1 had its build status changed: partially failing to not available
ctypes-zarith.0.2.0 on 5.1 had its build status changed: partially failing to not available
dirsp-ps2ocaml.0.1.0 on 5.0 had its build status changed: partially failing to not available
docker-api.0.2 on 5.0 had its build status changed: failing to not available
docker-api.0.2 on 5.1 had its build status changed: failing to not available
docker-api.0.2.1 on 5.0 had its build status changed: failing to not available
docker-api.0.2.1 on 5.1 had its build status changed: failing to not available
docker-api.0.2.2 on 5.0 had its build status changed: failing to not available
docker-api.0.2.2 on 5.1 had its build status changed: failing to not available
higlo.0.1 on 5.0 had its build status changed: partially failing to not available
higlo.0.2 on 5.0 had its build status changed: partially failing to not available
higlo.0.4 on 5.0 had its build status changed: partially failing to not available
higlo.0.5 on 5.0 had its build status changed: partially failing to not available
higlo.0.6 on 5.0 had its build status changed: partially failing to not available
kinetic-client.0.0.1 on 5.0 had its build status changed: partially failing to not available
kinetic-client.0.0.9 on 5.0 had its build status changed: partially failing to not available
let-if.0.1.0 on 4.08 is not available anymore. Previous state was: passing
let-if.0.1.0 on 4.09 is not available anymore. Previous state was: passing
let-if.0.2.0 on 4.08 is not available anymore. Previous state was: passing
let-if.0.2.0 on 4.09 is not available anymore. Previous state was: passing
let-if.0.2.0 on 4.10 is not available anymore. Previous state was: passing
let-if.0.2.0 on 4.11 is not available anymore. Previous state was: passing
let-if.0.2.0 on 4.12 is not available anymore. Previous state was: passing
let-if.0.2.0 on 4.13 is not available anymore. Previous state was: passing
let-if.0.2.0 on 4.14 is not available anymore. Previous state was: passing
let-if.0.2.0 on 5.0 is not available anymore. Previous state was: passing
let-if.0.2.0 on 5.1 is not available anymore. Previous state was: passing
let-if.0.3.0 on 4.08 is not available anymore. Previous state was: passing
let-if.0.3.0 on 4.09 is not available anymore. Previous state was: passing
let-if.0.3.0 on 4.10 is not available anymore. Previous state was: passing
let-if.0.3.0 on 4.11 is not available anymore. Previous state was: passing
let-if.0.3.0 on 4.12 is not available anymore. Previous state was: passing
let-if.0.3.0 on 4.13 is not available anymore. Previous state was: passing
let-if.0.3.0 on 4.14 is not available anymore. Previous state was: passing
let-if.0.3.0 on 5.0 is not available anymore. Previous state was: passing
let-if.0.3.0 on 5.1 is not available anymore. Previous state was: passing
octez-node.15.1 on 4.13 had its build status changed: internal failure to not available
octez-node.17.3 on 4.08 had its build status changed: internal failure to not available
octez-proxy-server.16.1 on 5.0 had its build status changed: internal failure to not available
octez-shell-libs.18.0 on 5.1 had its build status changed: internal failure to not available
octez-smart-rollup-node-Proxford.18.0 on 4.08 had its build status changed: internal failure to not available
octez-smart-rollup-node-PtMumbai.16.1 on 4.12 had its build status changed: internal failure to not available
octez-smart-rollup-wasm-debugger.16.0 on 4.08 had its build status changed: internal failure to not available
octez-smart-rollup-wasm-debugger.17.3 on 4.09 had its build status changed: internal failure to not available
octez-tx-rollup-client-PtKathma.15.0 on 4.10 had its build status changed: internal failure to not available
octez-tx-rollup-client-PtLimaPt.15.0 on 4.12 had its build status changed: internal failure to not available
octez-tx-rollup-client-PtLimaPt.16.0 on 5.0 had its build status changed: internal failure to not available
octez-tx-rollup-node-PtKathma.15.1 on 4.11 had its build status changed: internal failure to not available
octez-tx-rollup-node-PtLimaPt.15.1 on 5.1 had its build status changed: internal failure to not available
octez-validator.15.0 on 4.11 had its build status changed: internal failure to not available
octez.16.1 on 4.08 had its build status changed: internal failure to not available
octez.18.0 on 4.10 had its build status changed: internal failure to not available
ocurl.0.7.6 on 5.0 had its build status changed: passing to not available
ocurl.0.7.6 on 5.1 had its build status changed: passing to not available
piqi.0.7.6 on 5.0 had its build status changed: partially failing to not available
piqi.0.7.7 on 5.0 had its build status changed: partially failing to not available
piqi.0.7.8 on 5.0 had its build status changed: partially failing to not available
piqilib.0.6.14 on 5.0 had its build status changed: partially failing to not available
pkcs11-driver.1.0.1 on 5.1 had its build status changed: failing to not available
pkcs11-rev.1.0.1 on 5.1 had its build status changed: partially failing to not available
ppx_cstubs.0.7.0 on 5.1 had its build status changed: failing to not available
qcheck-alcotest.0.10 on 5.0 had its build status changed: passing to not available
qcheck-alcotest.0.10 on 5.1 had its build status changed: passing to not available
qcheck-alcotest.0.9 on 5.0 had its build status changed: passing to not available
qcheck-alcotest.0.9 on 5.1 had its build status changed: passing to not available
qcheck-ounit.0.10 on 5.0 had its build status changed: passing to not available
qcheck-ounit.0.10 on 5.1 had its build status changed: passing to not available
qcheck-ounit.0.9 on 5.0 had its build status changed: passing to not available
qcheck-ounit.0.9 on 5.1 had its build status changed: passing to not available
qcheck.0.10 on 5.0 had its build status changed: passing to not available
qcheck.0.10 on 5.1 had its build status changed: passing to not available
qcheck.0.9 on 5.0 had its build status changed: passing to not available
qcheck.0.9 on 5.1 had its build status changed: passing to not available
raygui.0.3.1 on 5.1 had its build status changed: partially failing to not available
raygui.0.3.2 on 5.1 had its build status changed: partially failing to not available
raygui.0.5.1 on 5.1 had its build status changed: partially failing to not available
raylib.0.1.0 on 5.1 had its build status changed: partially failing to not available
raylib.0.2.2 on 5.1 had its build status changed: partially failing to not available
raylib.0.3.1 on 5.1 had its build status changed: partially failing to not available
raylib.0.3.2 on 5.1 had its build status changed: partially failing to not available
raylib.0.4.0 on 5.1 had its build status changed: partially failing to not available
raylib.0.5.1 on 5.1 had its build status changed: partially failing to not available
ssh-agent-unix.0.2.0 on 4.08 is not available anymore. Previous state was: passing
ssh-agent-unix.0.2.0 on 4.09 is not available anymore. Previous state was: passing
ssh-agent-unix.0.2.0 on 4.10 is not available anymore. Previous state was: passing
ssh-agent-unix.0.2.0 on 4.11 is not available anymore. Previous state was: passing
ssh-agent-unix.0.2.0 on 4.12 is not available anymore. Previous state was: passing
ssh-agent-unix.0.2.0 on 4.13 is not available anymore. Previous state was: passing
ssh-agent-unix.0.2.0 on 4.14 is not available anymore. Previous state was: passing
ssh-agent-unix.0.2.0 on 5.0 is not available anymore. Previous state was: passing
ssh-agent-unix.0.2.0 on 5.1 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 4.08 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 4.09 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 4.10 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 4.11 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 4.12 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 4.13 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 4.14 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 5.0 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.0 on 5.1 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 4.08 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 4.09 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 4.10 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 4.11 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 4.12 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 4.13 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 4.14 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 5.0 is not available anymore. Previous state was: passing
ssh-agent-unix.0.3.1 on 5.1 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 4.08 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 4.09 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 4.10 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 4.11 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 4.12 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 4.13 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 4.14 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 5.0 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.0 on 5.1 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 4.08 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 4.09 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 4.10 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 4.11 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 4.12 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 4.13 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 4.14 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 5.0 is not available anymore. Previous state was: passing
ssh-agent-unix.0.4.1 on 5.1 is not available anymore. Previous state was: passing
ulex.1.2 on 5.0 had its build status changed: partially failing to not available
yices2_bindings.0.2 on 5.1 had its build status changed: partially failing to not available

Packages now failing with an internal failure:

base32.1.0.0 on 4.09 had its build status changed: passing to internal failure
base32.1.0.0 on 4.10 had its build status changed: passing to internal failure
base32.1.0.0 on 4.11 had its build status changed: passing to internal failure
base32.1.0.0 on 4.13 had its build status changed: passing to internal failure
base32.1.0.0 on 5.0 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 4.08 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 4.09 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 4.10 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 4.11 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 4.12 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 4.13 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 4.14 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 5.0 had its build status changed: passing to internal failure
conf-pandoc.0.1 on 5.1 had its build status changed: passing to internal failure
monocypher.0.1.0 on 4.08 had its build status changed: passing to internal failure
monocypher.0.1.0 on 4.10 had its build status changed: passing to internal failure
monocypher.0.1.0 on 4.12 had its build status changed: passing to internal failure
monocypher.0.1.0 on 4.14 had its build status changed: passing to internal failure
monocypher.0.1.0 on 5.0 had its build status changed: passing to internal failure
monocypher.0.1.0 on 5.1 had its build status changed: passing to internal failure
ocaml-manual.5.1.0 on 5.1 had its build status changed: passing to internal failure
ocamlregextkit.1.0.0 on 4.14 had its build status changed: passing to internal failure
pancake.2.0.0 on 5.1 is now installable. Current state is: internal failure
uuseg.1.0.1 on 4.08 had its build status changed: passing to internal failure
uuseg.1.0.1 on 4.09 had its build status changed: passing to internal failure
ws-server.0.1 on 4.08 had its build status changed: passing to internal failure
ws-server.0.1 on 4.10 had its build status changed: passing to internal failure
ws-server.0.1 on 4.13 had its build status changed: passing to internal failure
ws-server.0.1 on 5.0 had its build status changed: passing to internal failure
wseg.0.3.0 on 4.13 had its build status changed: passing to internal failure
wseg.0.3.0 on 5.1 had its build status changed: not available to internal failure
yara.0.1 on 4.11 had its build status changed: passing to internal failure
yara.0.1 on 4.12 had its build status changed: passing to internal failure
yara.0.2 on 4.10 had its build status changed: passing to internal failure
yara.0.2 on 4.11 had its build status changed: passing to internal failure
yojson-bench.2.0.0 on 4.08 had its build status changed: passing to internal failure
yojson-bench.2.0.0 on 4.09 had its build status changed: passing to internal failure
yojson-bench.2.0.0 on 5.1 had its build status changed: passing to internal failure
yojson-bench.2.0.1 on 4.12 had its build status changed: passing to internal failure
yojson-bench.2.0.1 on 4.13 had its build status changed: passing to internal failure
yojson-bench.2.0.1 on 5.0 had its build status changed: passing to internal failure
yojson-bench.2.0.2 on 4.08 had its build status changed: passing to internal failure
yojson-bench.2.0.2 on 4.09 had its build status changed: passing to internal failure
yojson-bench.2.0.2 on 4.12 had its build status changed: passing to internal failure
yojson-bench.2.0.2 on 4.14 had its build status changed: passing to internal failure
z3.4.10.1 on 4.09 had its build status changed: passing to internal failure
z3.4.10.1 on 4.13 had its build status changed: failing to internal failure
z3.4.10.1 on 4.14 had its build status changed: passing to internal failure
z3.4.10.2 on 4.10 had its build status changed: passing to internal failure
z3.4.10.2 on 4.13 had its build status changed: passing to internal failure
z3.4.11.0 on 4.08 had its build status changed: passing to internal failure
z3.4.11.0 on 4.10 had its build status changed: passing to internal failure
z3.4.11.0 on 5.1 had its build status changed: passing to internal failure
z3.4.11.2 on 4.10 had its build status changed: passing to internal failure
z3.4.11.2 on 4.11 had its build status changed: passing to internal failure
z3.4.11.2 on 4.12 had its build status changed: passing to internal failure
z3.4.12.2-1 on 4.09 had its build status changed: passing to internal failure
z3.4.12.2-1 on 4.12 had its build status changed: passing to internal failure
z3.4.12.2-1 on 4.14 had its build status changed: passing to internal failure
z3.4.12.2-1 on 5.0 had its build status changed: passing to internal failure
z3.4.12.3 on 4.08 is now installable. Current state is: internal failure
z3.4.12.3 on 4.12 is now installable. Current state is: internal failure
z3.4.12.3 on 5.1 is now installable. Current state is: internal failure
z3.4.12.4 on 4.08 is now installable. Current state is: internal failure
z3.4.12.4 on 4.09 is now installable. Current state is: internal failure
z3.4.12.4 on 4.10 is now installable. Current state is: internal failure
z3.4.12.4 on 4.11 is now installable. Current state is: internal failure
z3.4.12.4 on 4.12 is now installable. Current state is: internal failure
z3.4.12.4 on 4.13 is now installable. Current state is: internal failure
z3.4.12.4 on 4.14 is now installable. Current state is: internal failure
z3.4.8.13 on 4.08 had its build status changed: passing to internal failure
z3.4.8.13 on 4.09 had its build status changed: passing to internal failure
z3.4.8.13 on 4.11 had its build status changed: passing to internal failure
z3.4.8.13 on 4.12 had its build status changed: passing to internal failure
z3.4.8.13 on 4.13 had its build status changed: passing to internal failure
z3.4.8.13 on 4.14 had its build status changed: passing to internal failure
z3.4.8.14 on 4.08 had its build status changed: passing to internal failure
z3.4.8.14 on 4.12 had its build status changed: passing to internal failure
z3.4.8.14 on 4.13 had its build status changed: passing to internal failure
z3.4.8.17 on 4.08 had its build status changed: passing to internal failure
z3.4.8.17 on 4.09 had its build status changed: passing to internal failure
z3.4.8.17 on 4.10 had its build status changed: passing to internal failure
z3.4.8.5-1 on 4.08 had its build status changed: passing to internal failure
z3.4.8.5-1 on 4.09 had its build status changed: passing to internal failure
z3.4.8.5-1 on 4.11 had its build status changed: passing to internal failure
z3.4.8.5-1 on 4.13 had its build status changed: passing to internal failure
z3.4.9.1 on 4.08 had its build status changed: passing to internal failure
z3.4.9.1 on 4.10 had its build status changed: passing to internal failure
z3.4.9.1 on 4.12 had its build status changed: passing to internal failure
z3_tptp.4.10.1 on 4.09 had its build status changed: passing to internal failure
z3_tptp.4.10.1 on 4.10 had its build status changed: passing to internal failure
z3_tptp.4.10.2 on 4.08 had its build status changed: passing to internal failure
z3_tptp.4.10.2 on 4.09 had its build status changed: passing to internal failure
z3_tptp.4.10.2 on 4.11 had its build status changed: passing to internal failure
z3_tptp.4.10.2 on 4.12 had its build status changed: passing to internal failure
z3_tptp.4.10.2 on 4.13 had its build status changed: passing to internal failure
z3_tptp.4.10.2 on 4.14 had its build status changed: passing to internal failure
z3_tptp.4.11.0 on 4.10 had its build status changed: passing to internal failure
z3_tptp.4.11.0 on 4.11 had its build status changed: passing to internal failure
z3_tptp.4.11.2 on 4.09 had its build status changed: passing to internal failure
z3_tptp.4.11.2 on 4.10 had its build status changed: passing to internal failure
z3_tptp.4.11.2 on 4.11 had its build status changed: passing to internal failure
z3_tptp.4.11.2 on 4.12 had its build status changed: passing to internal failure
z3_tptp.4.8.13 on 4.12 had its build status changed: passing to internal failure
z3_tptp.4.8.13 on 4.14 had its build status changed: passing to internal failure
z3_tptp.4.8.14 on 4.08 had its build status changed: passing to internal failure
z3_tptp.4.8.14 on 4.09 had its build status changed: passing to internal failure
z3_tptp.4.8.14 on 4.11 had its build status changed: passing to internal failure
z3_tptp.4.8.14 on 4.12 had its build status changed: passing to internal failure
z3_tptp.4.8.14 on 4.13 had its build status changed: passing to internal failure
z3_tptp.4.8.14 on 4.14 had its build status changed: passing to internal failure
z3_tptp.4.8.17 on 4.08 had its build status changed: passing to internal failure
z3_tptp.4.8.17 on 4.09 had its build status changed: passing to internal failure
z3_tptp.4.8.17 on 4.13 had its build status changed: passing to internal failure
z3_tptp.4.9.1 on 4.09 had its build status changed: passing to internal failure
zanuda.1.0.0 on 4.14 had its build status changed: passing to internal failure
zar.0.9.1 on 5.1 had its build status changed: passing to internal failure
zarith-freestanding.1.10 on 4.09 had its build status changed: partially failing to internal failure
zarith-freestanding.1.10 on 4.10 had its build status changed: partially failing to internal failure
zarith-freestanding.1.10 on 4.12 had its build status changed: partially failing to internal failure
zarith-freestanding.1.11 on 4.10 had its build status changed: partially failing to internal failure
zarith-freestanding.1.11 on 4.11 had its build status changed: partially failing to internal failure
zarith-freestanding.1.12 on 4.08 had its build status changed: partially failing to internal failure
zarith-freestanding.1.4 on 4.09 had its build status changed: partially failing to internal failure
zarith-freestanding.1.7-1 on 4.10 had its build status changed: partially failing to internal failure
zarith-freestanding.1.7-2 on 4.11 had its build status changed: partially failing to internal failure
zarith-ppx.0.1 on 4.10 had its build status changed: passing to internal failure
zed.2.0.2 on 5.0 had its build status changed: not available to internal failure
zed.2.0.3 on 4.10 had its build status changed: passing to internal failure
zed.2.0.3 on 4.12 had its build status changed: passing to internal failure
zed.2.0.3 on 4.13 had its build status changed: passing to internal failure
zed.2.0.4 on 4.08 had its build status changed: passing to internal failure
zed.2.0.4 on 4.09 had its build status changed: passing to internal failure
zed.2.0.4 on 4.12 had its build status changed: passing to internal failure
zed.2.0.4 on 4.14 had its build status changed: not available to internal failure
zed.2.0.4 on 5.1 had its build status changed: not available to internal failure
zed.2.0.5 on 4.09 had its build status changed: passing to internal failure
zed.2.0.5 on 4.11 had its build status changed: passing to internal failure
zed.2.0.5 on 4.13 had its build status changed: passing to internal failure
zed.3.0.0 on 4.09 had its build status changed: passing to internal failure
zed.3.0.0 on 4.11 had its build status changed: passing to internal failure
zed.3.0.0 on 4.13 had its build status changed: passing to internal failure
zed.3.0.0 on 4.14 had its build status changed: passing to internal failure
zed.3.0.0 on 5.1 had its build status changed: not available to internal failure
zed.3.0.1 on 4.08 had its build status changed: passing to internal failure
zed.3.0.1 on 4.09 had its build status changed: passing to internal failure
zed.3.0.1 on 4.13 had its build status changed: passing to internal failure
zed.3.0.1 on 5.1 had its build status changed: not available to internal failure
zed.3.2.1 on 4.09 had its build status changed: passing to internal failure
zed.3.2.1 on 4.11 had its build status changed: passing to internal failure
zed.3.2.2 on 4.09 had its build status changed: passing to internal failure
zed.3.2.2 on 4.10 had its build status changed: passing to internal failure
zed.3.2.3 on 4.12 had its build status changed: passing to internal failure
zed.3.2.3 on 4.14 had its build status changed: passing to internal failure
zeit.0.1.0 on 4.08 had its build status changed: passing to internal failure
zelus.2.2 on 4.14 had its build status changed: failing to internal failure
zipc.0.1.0 on 4.09 is now installable. Current state is: internal failure
zipc.0.1.0 on 4.11 is now installable. Current state is: internal failure
zipc.0.1.0 on 4.13 is now installable. Current state is: internal failure
zipperposition-tools.1.6 on 4.08 had its build status changed: passing to internal failure
zipperposition-tools.1.6 on 4.10 had its build status changed: passing to internal failure
zipperposition-tools.1.6 on 4.11 had its build status changed: passing to internal failure
zipperposition-tools.2.0 on 4.09 had its build status changed: passing to internal failure
zipperposition-tools.2.0 on 4.10 had its build status changed: passing to internal failure
zmq-async.5.0.0 on 4.09 had its build status changed: passing to internal failure
zmq-async.5.0.0 on 4.11 had its build status changed: passing to internal failure
zmq-async.5.1.0 on 4.08 had its build status changed: passing to internal failure
zmq-async.5.1.0 on 4.10 had its build status changed: passing to internal failure
zmq-async.5.1.0 on 4.11 had its build status changed: passing to internal failure
zmq-async.5.1.0 on 4.13 had its build status changed: passing to internal failure
zmq-async.5.1.0 on 5.1 had its build status changed: passing to internal failure
zmq-async.5.1.1 on 4.09 had its build status changed: passing to internal failure
zmq-async.5.1.1 on 4.10 had its build status changed: passing to internal failure
zmq-async.5.1.1 on 4.13 had its build status changed: passing to internal failure
zmq-async.5.1.1 on 4.14 had its build status changed: passing to internal failure
zmq-async.5.1.1 on 5.1 had its build status changed: passing to internal failure
zmq-async.5.1.2 on 4.09 had its build status changed: passing to internal failure
zmq-async.5.1.2 on 4.13 had its build status changed: passing to internal failure
zmq-async.5.1.2 on 4.14 had its build status changed: passing to internal failure
zmq-async.5.1.2 on 5.1 had its build status changed: passing to internal failure
zmq-async.5.1.3 on 4.08 had its build status changed: passing to internal failure
zmq-async.5.1.3 on 4.09 had its build status changed: passing to internal failure
zmq-async.5.1.3 on 4.10 had its build status changed: passing to internal failure
zmq-async.5.1.3 on 4.12 had its build status changed: passing to internal failure
zmq-async.5.1.3 on 4.14 had its build status changed: passing to internal failure
zmq-async.5.1.3 on 5.0 had its build status changed: passing to internal failure
zmq-async.5.1.4 on 4.09 had its build status changed: passing to internal failure
zmq-async.5.1.4 on 4.11 had its build status changed: passing to internal failure
zmq-async.5.1.4 on 4.13 had its build status changed: passing to internal failure
zmq-async.5.1.5 on 4.11 had its build status changed: passing to internal failure
zmq-async.5.1.5 on 4.14 had its build status changed: passing to internal failure
zmq-async.5.2.1 on 4.08 had its build status changed: passing to internal failure
zmq-lwt.5.1.0 on 5.1 had its build status changed: not available to internal failure
zmq-lwt.5.1.1 on 5.1 had its build status changed: not available to internal failure
zmq-lwt.5.1.2 on 4.09 had its build status changed: passing to internal failure
zmq-lwt.5.1.2 on 4.10 had its build status changed: passing to internal failure

Packages now passing:

SZXX.3.0.2 on 4.11 is now installable. Current state is: passing
SZXX.3.0.2 on 4.12 is now installable. Current state is: passing
SZXX.3.0.2 on 4.13 is now installable. Current state is: passing
SZXX.3.0.2 on 4.14 is now installable. Current state is: passing
SZXX.3.0.2 on 5.0 is now installable. Current state is: passing
SZXX.3.0.2 on 5.1 is now installable. Current state is: passing
SZXX.4.1.1 on 5.0 is now installable. Current state is: passing
SZXX.4.1.1 on 5.1 is now installable. Current state is: passing
aarch64-esperanto.0.0.5 on 4.13 is now installable. Current state is: passing
aarch64-esperanto.0.0.5 on 4.14 is now installable. Current state is: passing
acgtk.1.5.2 on 4.08 had its build status changed: internal failure to passing
acgtk.1.5.2 on 4.09 had its build status changed: internal failure to passing
acgtk.1.5.2 on 4.10 had its build status changed: internal failure to passing
acgtk.1.5.2 on 4.11 had its build status changed: internal failure to passing
acgtk.1.5.2 on 4.12 had its build status changed: internal failure to passing
acgtk.1.5.2 on 4.13 had its build status changed: internal failure to passing
acgtk.1.5.2 on 4.14 had its build status changed: internal failure to passing
acgtk.1.5.2 on 5.0 had its build status changed: internal failure to passing
acgtk.1.5.2 on 5.1 had its build status changed: internal failure to passing
acgtk.1.5.3 on 4.08 had its build status changed: internal failure to passing
acgtk.1.5.3 on 4.09 had its build status changed: internal failure to passing
acgtk.1.5.3 on 4.10 had its build status changed: internal failure to passing
acgtk.1.5.3 on 4.11 had its build status changed: internal failure to passing
acgtk.1.5.3 on 4.12 had its build status changed: internal failure to passing
acgtk.1.5.3 on 4.13 had its build status changed: internal failure to passing
acgtk.1.5.3 on 4.14 had its build status changed: internal failure to passing
acgtk.1.5.3 on 5.0 had its build status changed: internal failure to passing
acgtk.1.5.3 on 5.1 had its build status changed: internal failure to passing
acpc.1.1.1 on 4.08 had its build status changed: partially failing to passing
acpc.1.1.1 on 4.09 had its build status changed: partially failing to passing
acpc.1.1.1 on 4.10 had its build status changed: partially failing to passing
acpc.1.1.1 on 4.11 had its build status changed: partially failing to passing
acpc.1.1.1 on 4.12 had its build status changed: partially failing to passing
acpc.1.1.1 on 4.13 had its build status changed: partially failing to passing
acpc.1.1.1 on 4.14 had its build status changed: partially failing to passing
acpc.1.2.3 on 4.08 had its build status changed: partially failing to passing
acpc.1.2.3 on 4.09 had its build status changed: partially failing to passing
acpc.1.2.3 on 4.10 had its build status changed: partially failing to passing
acpc.1.2.3 on 4.11 had its build status changed: partially failing to passing
acpc.1.2.3 on 4.12 had its build status changed: partially failing to passing
acpc.1.2.3 on 4.13 had its build status changed: partially failing to passing
acpc.1.2.3 on 4.14 had its build status changed: partially failing to passing
algaeff.2.0.0 on 5.0 is now installable. Current state is: passing
algaeff.2.0.0 on 5.1 is now installable. Current state is: passing
alt-ergo-free.2.0.0 on 4.09 had its build status changed: failing to passing
alt-ergo-free.2.0.0 on 4.11 had its build status changed: failing to passing
alt-ergo-parsers.2.3.0 on 4.08 had its build status changed: failing to passing
alt-ergo-parsers.2.3.0 on 4.09 had its build status changed: failing to passing
alt-ergo-parsers.2.3.0 on 4.10 had its build status changed: failing to passing
alt-ergo-parsers.2.3.0 on 4.11 had its build status changed: failing to passing
alt-ergo-parsers.2.3.0 on 4.12 had its build status changed: failing to passing
alt-ergo-parsers.2.3.0 on 4.13 had its build status changed: failing to passing
alt-ergo-parsers.2.3.0 on 4.14 had its build status changed: failing to passing
alt-ergo-parsers.2.3.1 on 4.08 had its build status changed: failing to passing
alt-ergo-parsers.2.3.1 on 4.09 had its build status changed: failing to passing
alt-ergo-parsers.2.3.1 on 4.10 had its build status changed: failing to passing
alt-ergo-parsers.2.3.1 on 4.11 had its build status changed: failing to passing
alt-ergo-parsers.2.3.1 on 4.12 had its build status changed: failing to passing
alt-ergo-parsers.2.3.1 on 4.13 had its build status changed: failing to passing
alt-ergo-parsers.2.3.1 on 4.14 had its build status changed: failing to passing
alt-ergo-parsers.2.3.2 on 4.08 had its build status changed: failing to passing
alt-ergo-parsers.2.3.2 on 4.09 had its build status changed: failing to passing
alt-ergo-parsers.2.3.2 on 4.10 had its build status changed: failing to passing
alt-ergo-parsers.2.3.2 on 4.11 had its build status changed: failing to passing
alt-ergo-parsers.2.3.2 on 4.12 had its build status changed: failing to passing
alt-ergo-parsers.2.3.2 on 4.13 had its build status changed: failing to passing
alt-ergo-parsers.2.3.2 on 4.14 had its build status changed: failing to passing
alt-ergo-parsers.2.3.3 on 4.08 had its build status changed: failing to passing
alt-ergo-parsers.2.3.3 on 4.09 had its build status changed: failing to passing
alt-ergo-parsers.2.3.3 on 4.10 had its build status changed: failing to passing
alt-ergo-parsers.2.3.3 on 4.11 had its build status changed: failing to passing
alt-ergo-parsers.2.3.3 on 4.12 had its build status changed: failing to passing
alt-ergo-parsers.2.3.3 on 4.13 had its build status changed: failing to passing
alt-ergo-parsers.2.3.3 on 4.14 had its build status changed: failing to passing
alt-ergo-parsers.2.4.0 on 4.08 had its build status changed: failing to passing
alt-ergo-parsers.2.4.0 on 4.09 had its build status changed: failing to passing
alt-ergo-parsers.2.4.0 on 4.10 had its build status changed: failing to passing
alt-ergo-parsers.2.4.0 on 4.11 had its build status changed: failing to passing
alt-ergo-parsers.2.4.0 on 4.12 had its build status changed: failing to passing
alt-ergo-parsers.2.4.0 on 4.13 had its build status changed: failing to passing
alt-ergo-parsers.2.4.0 on 4.14 had its build status changed: failing to passing
alt-ergo-parsers.2.4.1 on 4.08 had its build status changed: failing to passing
alt-ergo-parsers.2.4.1 on 4.09 had its build status changed: failing to passing
alt-ergo-parsers.2.4.1 on 4.10 had its build status changed: failing to passing
alt-ergo-parsers.2.4.1 on 4.11 had its build status changed: failing to passing
alt-ergo-parsers.2.4.1 on 4.12 had its build status changed: failing to passing
alt-ergo-parsers.2.4.1 on 4.13 had its build status changed: failing to passing
alt-ergo-parsers.2.4.1 on 4.14 had its build status changed: failing to passing
alt-ergo.2.0.0 on 4.10 had its build status changed: failing to passing
alt-ergo.2.1.0 on 4.13 had its build status changed: failing to passing
alt-ergo.2.1.0 on 4.14 had its build status changed: failing to passing
alt-ergo.2.2.0 on 4.08 had its build status changed: failing to passing
alt-ergo.2.3.0 on 4.08 had its build status changed: partially failing to passing
alt-ergo.2.3.0 on 4.09 had its build status changed: partially failing to passing
alt-ergo.2.3.0 on 4.10 had its build status changed: partially failing to passing
alt-ergo.2.3.0 on 4.11 had its build status changed: partially failing to passing
alt-ergo.2.3.0 on 4.12 had its build status changed: partially failing to passing
alt-ergo.2.3.0 on 4.13 had its build status changed: partially failing to passing
alt-ergo.2.3.0 on 4.14 had its build status changed: partially failing to passing
alt-ergo.2.3.1 on 4.08 had its build status changed: partially failing to passing
alt-ergo.2.3.1 on 4.09 had its build status changed: partially failing to passing
alt-ergo.2.3.1 on 4.10 had its build status changed: partially failing to passing
alt-ergo.2.3.1 on 4.11 had its build status changed: partially failing to passing
alt-ergo.2.3.1 on 4.12 had its build status changed: partially failing to passing
alt-ergo.2.3.1 on 4.13 had its build status changed: partially failing to passing
alt-ergo.2.3.1 on 4.14 had its build status changed: partially failing to passing
alt-ergo.2.3.2 on 4.08 had its build status changed: partially failing to passing
alt-ergo.2.3.2 on 4.09 had its build status changed: partially failing to passing
alt-ergo.2.3.2 on 4.10 had its build status changed: partially failing to passing
alt-ergo.2.3.2 on 4.11 had its build status changed: partially failing to passing
alt-ergo.2.3.2 on 4.12 had its build status changed: partially failing to passing
alt-ergo.2.3.2 on 4.13 had its build status changed: partially failing to passing
alt-ergo.2.3.2 on 4.14 had its build status changed: partially failing to passing
alt-ergo.2.3.3 on 4.08 had its build status changed: partially failing to passing
alt-ergo.2.3.3 on 4.09 had its build status changed: partially failing to passing
alt-ergo.2.3.3 on 4.10 had its build status changed: partially failing to passing
alt-ergo.2.3.3 on 4.11 had its build status changed: partially failing to passing
alt-ergo.2.3.3 on 4.12 had its build status changed: partially failing to passing
alt-ergo.2.3.3 on 4.13 had its build status changed: partially failing to passing
alt-ergo.2.3.3 on 4.14 had its build status changed: partially failing to passing
alt-ergo.2.4.0 on 4.08 had its build status changed: partially failing to passing
alt-ergo.2.4.0 on 4.09 had its build status changed: partially failing to passing
alt-ergo.2.4.0 on 4.10 had its build status changed: partially failing to passing
alt-ergo.2.4.0 on 4.11 had its build status changed: partially failing to passing
alt-ergo.2.4.0 on 4.12 had its build status changed: partially failing to passing
alt-ergo.2.4.0 on 4.13 had its build status changed: partially failing to passing
alt-ergo.2.4.0 on 4.14 had its build status changed: partially failing to passing
alt-ergo.2.4.1 on 4.08 had its build status changed: partially failing to passing
alt-ergo.2.4.1 on 4.09 had its build status changed: partially failing to passing
alt-ergo.2.4.1 on 4.10 had its build status changed: partially failing to passing
alt-ergo.2.4.1 on 4.11 had its build status changed: partially failing to passing
alt-ergo.2.4.1 on 4.12 had its build status changed: partially failing to passing
alt-ergo.2.4.1 on 4.13 had its build status changed: partially failing to passing
alt-ergo.2.4.1 on 4.14 had its build status changed: partially failing to passing
amqp-client-async.2.3.0 on 4.14 is now installable. Current state is: passing
amqp-client-async.2.3.0 on 5.0 is now installable. Current state is: passing
amqp-client-async.2.3.0 on 5.1 is now installable. Current state is: passing
amqp-client-lwt.2.3.0 on 4.14 is now installable. Current state is: passing
amqp-client-lwt.2.3.0 on 5.0 is now installable. Current state is: passing
amqp-client-lwt.2.3.0 on 5.1 is now installable. Current state is: passing
amqp-client.2.3.0 on 4.14 is now installable. Current state is: passing
amqp-client.2.3.0 on 5.0 is now installable. Current state is: passing
amqp-client.2.3.0 on 5.1 is now installable. Current state is: passing
angstrom-async.0.16.0 on 4.08 is now installable. Current state is: passing
angstrom-async.0.16.0 on 4.09 is now installable. Current state is: passing
angstrom-async.0.16.0 on 4.10 is now installable. Current state is: passing
angstrom-async.0.16.0 on 4.11 is now installable. Current state is: passing
angstrom-async.0.16.0 on 4.12 is now installable. Current state is: passing
angstrom-async.0.16.0 on 4.13 is now installable. Current state is: passing
angstrom-async.0.16.0 on 4.14 is now installable. Current state is: passing
angstrom-async.0.16.0 on 5.0 is now installable. Current state is: passing
angstrom-async.0.16.0 on 5.1 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 4.08 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 4.09 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 4.10 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 4.11 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 4.12 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 4.13 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 4.14 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 5.0 is now installable. Current state is: passing
angstrom-lwt-unix.0.16.0 on 5.1 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 4.08 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 4.09 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 4.10 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 4.11 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 4.12 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 4.13 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 4.14 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 5.0 is now installable. Current state is: passing
angstrom-unix.0.16.0 on 5.1 is now installable. Current state is: passing
angstrom.0.16.0 on 4.08 is now installable. Current state is: passing
angstrom.0.16.0 on 4.09 is now installable. Current state is: passing
angstrom.0.16.0 on 4.10 is now installable. Current state is: passing
angstrom.0.16.0 on 4.11 is now installable. Current state is: passing
angstrom.0.16.0 on 4.12 is now installable. Current state is: passing
angstrom.0.16.0 on 4.13 is now installable. Current state is: passing
angstrom.0.16.0 on 4.14 is now installable. Current state is: passing
angstrom.0.16.0 on 5.0 is now installable. Current state is: passing
angstrom.0.16.0 on 5.1 is now installable. Current state is: passing
archetype.1.5.0 on 4.08 is now installable. Current state is: passing
archetype.1.5.0 on 4.09 is now installable. Current state is: passing
archetype.1.5.0 on 4.10 is now installable. Current state is: passing
archetype.1.5.0 on 4.11 is now installable. Current state is: passing
archetype.1.5.0 on 4.12 is now installable. Current state is: passing
archetype.1.5.0 on 4.13 is now installable. Current state is: passing
archetype.1.5.0 on 4.14 is now installable. Current state is: passing
archetype.1.5.0 on 5.0 is now installable. Current state is: passing
archetype.1.5.0 on 5.1 is now installable. Current state is: passing
archimedes.0.4.18 on 4.08 had its build status changed: partially failing to passing
archimedes.0.4.18 on 4.09 had its build status changed: partially failing to passing
archimedes.0.4.18 on 4.10 had its build status changed: partially failing to passing
archimedes.0.4.18 on 4.11 had its build status changed: partially failing to passing
archimedes.0.4.18 on 4.12 had its build status changed: partially failing to passing
archimedes.0.4.18 on 4.13 had its build status changed: partially failing to passing
archimedes.0.4.18 on 4.14 had its build status changed: partially failing to passing
argsh.0.1.0 on 4.13 is now installable. Current state is: passing
argsh.0.1.0 on 4.14 is now installable. Current state is: passing
argsh.0.1.0 on 5.0 is now installable. Current state is: passing
argsh.0.1.0 on 5.1 is now installable. Current state is: passing
asai.0.3.0 on 5.0 is now installable. Current state is: passing
asai.0.3.0 on 5.1 is now installable. Current state is: passing
atacama.0.0.1 on 5.1 is now installable. Current state is: passing
atacama.0.0.2 on 5.1 is now installable. Current state is: passing
atacama.0.0.3 on 5.1 is now installable. Current state is: passing
atacama.0.0.4 on 5.1 is now installable. Current state is: passing
azure-cosmos-db.0.1.2 on 4.08 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.2 on 4.09 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.2 on 4.10 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.2 on 4.11 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.2 on 4.12 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.2 on 4.13 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.2 on 4.14 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.3 on 4.08 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.3 on 4.09 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.3 on 4.10 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.3 on 4.11 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.3 on 4.12 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.3 on 4.13 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.3 on 4.14 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.4 on 4.08 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.4 on 4.09 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.4 on 4.10 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.4 on 4.11 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.4 on 4.12 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.4 on 4.13 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.4 on 4.14 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.5 on 4.08 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.5 on 4.09 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.5 on 4.10 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.5 on 4.11 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.5 on 4.12 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.5 on 4.13 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.5 on 4.14 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.6 on 4.08 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.6 on 4.09 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.6 on 4.10 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.6 on 4.11 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.6 on 4.12 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.6 on 4.13 had its build status changed: partially failing to passing
azure-cosmos-db.0.1.6 on 4.14 had its build status changed: partially failing to passing
balancer.1.0 on 4.08 had its build status changed: failing to passing
balancer.1.0 on 4.09 had its build status changed: failing to passing
balancer.1.0 on 4.10 had its build status changed: failing to passing
balancer.1.0 on 4.11 had its build status changed: failing to passing
balancer.1.0 on 4.12 had its build status changed: failing to passing
balancer.1.0 on 4.13 had its build status changed: failing to passing
balancer.1.0 on 4.14 had its build status changed: failing to passing
batteries.3.7.2 on 4.08 is now installable. Current state is: passing
batteries.3.7.2 on 4.09 is now installable. Current state is: passing
batteries.3.7.2 on 4.10 is now installable. Current state is: passing
batteries.3.7.2 on 4.11 is now installable. Current state is: passing
batteries.3.7.2 on 4.12 is now installable. Current state is: passing
batteries.3.7.2 on 4.13 is now installable. Current state is: passing
batteries.3.7.2 on 4.14 is now installable. Current state is: passing
batteries.3.7.2 on 5.0 is now installable. Current state is: passing
batteries.3.7.2 on 5.1 is now installable. Current state is: passing
bdd.0.3 on 4.08 had its build status changed: partially failing to passing
bdd.0.3 on 4.09 had its build status changed: partially failing to passing
bdd.0.3 on 4.10 had its build status changed: partially failing to passing
bdd.0.3 on 4.11 had its build status changed: partially failing to passing
bdd.0.3 on 4.12 had its build status changed: partially failing to passing
bdd.0.3 on 4.13 had its build status changed: partially failing to passing
bdd.0.3 on 4.14 had its build status changed: partially failing to passing
bechamel-js.0.5.0 on 4.08 is now installable. Current state is: passing
bechamel-js.0.5.0 on 4.09 is now installable. Current state is: passing
bechamel-js.0.5.0 on 4.10 is now installable. Current state is: passing
bechamel-js.0.5.0 on 4.11 is now installable. Current state is: passing
bechamel-js.0.5.0 on 4.12 is now installable. Current state is: passing
bechamel-js.0.5.0 on 4.13 is now installable. Current state is: passing
bechamel-js.0.5.0 on 4.14 is now installable. Current state is: passing
bechamel-js.0.5.0 on 5.0 is now installable. Current state is: passing
bechamel-js.0.5.0 on 5.1 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 4.08 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 4.09 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 4.10 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 4.11 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 4.12 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 4.13 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 4.14 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 5.0 is now installable. Current state is: passing
bechamel-notty.0.5.0 on 5.1 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 4.08 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 4.09 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 4.10 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 4.11 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 4.12 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 4.13 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 4.14 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 5.0 is now installable. Current state is: passing
bechamel-perf.0.5.0 on 5.1 is now installable. Current state is: passing
bechamel.0.5.0 on 4.08 is now installable. Current state is: passing
bechamel.0.5.0 on 4.09 is now installable. Current state is: passing
bechamel.0.5.0 on 4.10 is now installable. Current state is: passing
bechamel.0.5.0 on 4.11 is now installable. Current state is: passing
bechamel.0.5.0 on 4.12 is now installable. Current state is: passing
bechamel.0.5.0 on 4.13 is now installable. Current state is: passing
bechamel.0.5.0 on 4.14 is now installable. Current state is: passing
bechamel.0.5.0 on 5.0 is now installable. Current state is: passing
bechamel.0.5.0 on 5.1 is now installable. Current state is: passing
beluga.0.8.1 on 4.08 had its build status changed: partially failing to passing
beluga.0.8.1 on 4.09 had its build status changed: partially failing to passing
beluga.0.8.1 on 4.10 had its build status changed: partially failing to passing
beluga.0.8.1 on 4.11 had its build status changed: partially failing to passing
beluga.0.8.1 on 4.12 had its build status changed: partially failing to passing
beluga.0.8.1 on 4.13 had its build status changed: partially failing to passing
beluga.0.8.1 on 4.14 had its build status changed: partially failing to passing
beluga.0.8.2 on 4.08 had its build status changed: partially failing to passing
beluga.0.8.2 on 4.09 had its build status changed: partially failing to passing
beluga.0.8.2 on 4.10 had its build status changed: partially failing to passing
beluga.0.8.2 on 4.11 had its build status changed: partially failing to passing
beluga.0.8.2 on 4.12 had its build status changed: partially failing to passing
beluga.0.8.2 on 4.13 had its build status changed: partially failing to passing
beluga.0.8.2 on 4.14 had its build status changed: partially failing to passing
beluga.1.0 on 4.08 had its build status changed: failing to passing
beluga.1.0 on 4.09 had its build status changed: failing to passing
beluga.1.0 on 4.10 had its build status changed: failing to passing
beluga.1.0 on 4.11 had its build status changed: failing to passing
beluga.1.0 on 4.12 had its build status changed: failing to passing
beluga.1.0 on 4.13 had its build status changed: failing to passing
beluga.1.0 on 4.14 had its build status changed: failing to passing
beluga.1.1 on 4.14 had its build status changed: failing to passing
beluga.1.1 on 5.0 had its build status changed: failing to passing
beluga.1.1 on 5.1 had its build status changed: failing to passing
beluga.1.1.1 on 4.14 had its build status changed: failing to passing
beluga.1.1.1 on 5.0 had its build status changed: failing to passing
beluga.1.1.1 on 5.1 had its build status changed: failing to passing
bheap.1.0.0 on 4.08 had its build status changed: partially failing to passing
bheap.1.0.0 on 4.09 had its build status changed: partially failing to passing
bheap.1.0.0 on 4.10 had its build status changed: partially failing to passing
bheap.1.0.0 on 4.11 had its build status changed: partially failing to passing
bheap.1.0.0 on 4.12 had its build status changed: partially failing to passing
bheap.1.0.0 on 4.13 had its build status changed: partially failing to passing
bheap.1.0.0 on 4.14 had its build status changed: partially failing to passing
bimage-gtk.0.1 on 5.0 had its build status changed: not available to passing
bimage-gtk.0.1 on 5.1 had its build status changed: not available to passing
biotk.0.0.0 on 4.11 had its build status changed: partially failing to passing
biotk.0.0.0 on 4.12 had its build status changed: partially failing to passing
biotk.0.0.0 on 4.13 had its build status changed: partially failing to passing
biotk.0.0.0 on 4.14 had its build status changed: partially failing to passing
biotk.0.1.0 on 4.11 had its build status changed: partially failing to passing
biotk.0.1.0 on 4.12 had its build status changed: partially failing to passing
biotk.0.1.0 on 4.13 had its build status changed: partially failing to passing
biotk.0.1.0 on 4.14 had its build status changed: partially failing to passing
biotk.0.2.0 on 5.0 had its build status changed: not available to passing
bip32.0.1 on 4.08 is now installable. Current state is: passing
bip32.0.1 on 4.09 is now installable. Current state is: passing
bip32.0.1 on 4.10 is now installable. Current state is: passing
bip32.0.1 on 4.11 is now installable. Current state is: passing
bip32.0.2 on 4.08 is now installable. Current state is: passing
bip32.0.2 on 4.09 is now installable. Current state is: passing
bip32.0.2 on 4.10 is now installable. Current state is: passing
bip32.0.2 on 4.11 is now installable. Current state is: passing
bip32.0.2 on 4.12 is now installable. Current state is: passing
bip32.0.2 on 4.13 is now installable. Current state is: passing
bip32.0.2 on 4.14 is now installable. Current state is: passing
bisect.1.3.1 on 4.08 had its build status changed: partially failing to passing
bisect.1.3.1 on 4.09 had its build status changed: partially failing to passing
bisect.1.3.1 on 4.10 had its build status changed: partially failing to passing
bisect.1.3.1 on 4.11 had its build status changed: partially failing to passing
bisect.1.3.1 on 4.12 had its build status changed: partially failing to passing
bisect.1.3.1 on 4.13 had its build status changed: partially failing to passing
bisect.1.3.1 on 4.14 had its build status changed: partially failing to passing
bistro-bio.0.6.0 on 4.11 had its build status changed: partially failing to passing
bistro-bio.0.6.0 on 4.12 had its build status changed: partially failing to passing
bistro-bio.0.6.0 on 4.13 had its build status changed: partially failing to passing
bistro-bio.0.6.0 on 4.14 had its build status changed: partially failing to passing
bitwuzla-cxx.0.3.0 on 4.12 is now installable. Current state is: passing
bitwuzla-cxx.0.3.0 on 4.13 is now installable. Current state is: passing
bitwuzla-cxx.0.3.0 on 4.14 is now installable. Current state is: passing
bitwuzla.1.0.0 on 4.08 had its build status changed: failing to passing
bitwuzla.1.0.0 on 4.09 had its build status changed: failing to passing
bitwuzla.1.0.0 on 4.10 had its build status changed: failing to passing
bitwuzla.1.0.0 on 4.11 had its build status changed: failing to passing
bitwuzla.1.0.0 on 4.12 had its build status changed: failing to passing
bitwuzla.1.0.0 on 4.13 had its build status changed: failing to passing
bitwuzla.1.0.0 on 4.14 had its build status changed: failing to passing
bitwuzla.1.0.0 on 5.0 had its build status changed: failing to passing
bitwuzla.1.0.0 on 5.1 had its build status changed: failing to passing
bitwuzla.1.0.1 on 4.08 had its build status changed: failing to passing
bitwuzla.1.0.1 on 4.09 had its build status changed: failing to passing
bitwuzla.1.0.1 on 4.10 had its build status changed: failing to passing
bitwuzla.1.0.1 on 4.11 had its build status changed: failing to passing
bitwuzla.1.0.1 on 4.12 had its build status changed: failing to passing
bitwuzla.1.0.1 on 4.13 had its build status changed: failing to passing
bitwuzla.1.0.1 on 4.14 had its build status changed: failing to passing
bitwuzla.1.0.1 on 5.0 had its build status changed: failing to passing
bitwuzla.1.0.1 on 5.1 had its build status changed: failing to passing
bls12-381.18.1 on 4.14 is now installable. Current state is: passing
bls12-381.18.1 on 5.0 is now installable. Current state is: passing
bls12-381.18.1 on 5.1 is now installable. Current state is: passing
bogue.20190717 on 4.08 had its build status changed: partially failing to passing
bogue.20190717 on 4.09 had its build status changed: partially failing to passing
bogue.20190717 on 4.10 had its build status changed: partially failing to passing
bogue.20190717 on 4.11 had its build status changed: partially failing to passing
bogue.20190717 on 4.12 had its build status changed: partially failing to passing
bogue.20190717 on 4.13 had its build status changed: partially failing to passing
bogue.20190920 on 4.08 had its build status changed: partially failing to passing
bogue.20190920 on 4.09 had its build status changed: partially failing to passing
bogue.20190920 on 4.10 had its build status changed: partially failing to passing
bogue.20190920 on 4.11 had its build status changed: partially failing to passing
bogue.20190920 on 4.12 had its build status changed: partially failing to passing
bogue.20190920 on 4.13 had its build status changed: partially failing to passing
bogue.20200630 on 4.08 had its build status changed: partially failing to passing
bogue.20200630 on 4.09 had its build status changed: partially failing to passing
bogue.20200630 on 4.10 had its build status changed: partially failing to passing
bogue.20200630 on 4.11 had its build status changed: partially failing to passing
bogue.20200630 on 4.12 had its build status changed: partially failing to passing
bogue.20200630 on 4.13 had its build status changed: partially failing to passing
bogue.20210514 on 4.08 had its build status changed: partially failing to passing
bogue.20210514 on 4.09 had its build status changed: partially failing to passing
bogue.20210514 on 4.10 had its build status changed: partially failing to passing
bogue.20210514 on 4.11 had its build status changed: partially failing to passing
bogue.20210514 on 4.12 had its build status changed: partially failing to passing
bogue.20210514 on 4.13 had its build status changed: partially failing to passing
bogue.20210514 on 4.14 had its build status changed: partially failing to passing
bogue.20231209 on 4.08 is now installable. Current state is: passing
bogue.20231209 on 4.09 is now installable. Current state is: passing
bogue.20231209 on 4.10 is now installable. Current state is: passing
bogue.20231209 on 4.11 is now installable. Current state is: passing
bogue.20231209 on 4.12 is now installable. Current state is: passing
bogue.20231209 on 4.13 is now installable. Current state is: passing
bogue.20231209 on 4.14 is now installable. Current state is: passing
bogue.20231209 on 5.0 is now installable. Current state is: passing
bogue.20231209 on 5.1 is now installable. Current state is: passing
boltzgen.0.9 on 5.0 had its build status changed: failing to passing
boltzgen.0.9 on 5.1 had its build status changed: failing to passing
boltzgen.0.9.2 on 5.0 had its build status changed: failing to passing
boltzgen.0.9.2 on 5.1 had its build status changed: failing to passing
boltzgen.0.9.3 on 5.0 had its build status changed: failing to passing
boltzgen.0.9.3 on 5.1 had its build status changed: failing to passing
bookaml.2.1 on 4.08 had its build status changed: partially failing to passing
bookaml.2.1 on 4.09 had its build status changed: partially failing to passing
bookaml.2.1 on 4.10 had its build status changed: partially failing to passing
bookaml.2.1 on 4.11 had its build status changed: partially failing to passing
bookaml.2.1 on 4.12 had its build status changed: partially failing to passing
bookaml.2.1 on 4.13 had its build status changed: partially failing to passing
bookaml.2.1 on 4.14 had its build status changed: partially failing to passing
bookaml.4.0 on 4.08 had its build status changed: partially failing to passing
bookaml.4.0 on 4.09 had its build status changed: partially failing to passing
bookaml.4.0 on 4.10 had its build status changed: partially failing to passing
bookaml.4.0 on 4.11 had its build status changed: partially failing to passing
bookaml.4.0 on 4.12 had its build status changed: partially failing to passing
bookaml.4.0 on 4.13 had its build status changed: partially failing to passing
bookaml.4.0 on 4.14 had its build status changed: partially failing to passing
ca-certs-nss.3.95 on 4.08 is now installable. Current state is: passing
ca-certs-nss.3.95 on 4.09 is now installable. Current state is: passing
ca-certs-nss.3.95 on 4.10 is now installable. Current state is: passing
ca-certs-nss.3.95 on 4.11 is now installable. Current state is: passing
ca-certs-nss.3.95 on 4.12 is now installable. Current state is: passing
ca-certs-nss.3.95 on 4.13 is now installable. Current state is: passing
ca-certs-nss.3.95 on 4.14 is now installable. Current state is: passing
ca-certs-nss.3.95 on 5.0 is now installable. Current state is: passing
ca-certs-nss.3.95 on 5.1 is now installable. Current state is: passing
cairo2-gtk.0.6 on 5.0 had its build status changed: not available to passing
cairo2-gtk.0.6 on 5.1 had its build status changed: not available to passing
cairo2-gtk.0.6.4 on 5.0 had its build status changed: not available to passing
cairo2-gtk.0.6.4 on 5.1 had its build status changed: not available to passing
cairo2-pango.0.6 on 5.0 had its build status changed: not available to passing
cairo2-pango.0.6 on 5.1 had its build status changed: not available to passing
cairo2-pango.0.6.4 on 5.0 had its build status changed: not available to passing
cairo2-pango.0.6.4 on 5.1 had its build status changed: not available to passing
caisar.1.0 on 4.13 is now installable. Current state is: passing
caisar.1.0 on 4.14 is now installable. Current state is: passing
calculon-redis.0.6 on 4.13 had its build status changed: internal failure to passing
calli.0.1 on 4.13 is now installable. Current state is: passing
calli.0.1 on 4.14 is now installable. Current state is: passing
calli.0.1 on 5.0 is now installable. Current state is: passing
calli.0.1 on 5.1 is now installable. Current state is: passing
calli.0.2 on 4.13 is now installable. Current state is: passing
calli.0.2 on 4.14 is now installable. Current state is: passing
calli.0.2 on 5.0 is now installable. Current state is: passing
calli.0.2 on 5.1 is now installable. Current state is: passing
camlidl.1.12 on 4.08 is now installable. Current state is: passing
camlidl.1.12 on 4.09 is now installable. Current state is: passing
camlidl.1.12 on 4.10 is now installable. Current state is: passing
camlidl.1.12 on 4.11 is now installable. Current state is: passing
camlidl.1.12 on 4.12 is now installable. Current state is: passing
camlidl.1.12 on 4.13 is now installable. Current state is: passing
camlidl.1.12 on 4.14 is now installable. Current state is: passing
camlidl.1.12 on 5.0 is now installable. Current state is: passing
camlidl.1.12 on 5.1 is now installable. Current state is: passing
camlimages.5.0.5 on 4.12 is now installable. Current state is: passing
camlimages.5.0.5 on 4.13 is now installable. Current state is: passing
camlimages.5.0.5 on 4.14 is now installable. Current state is: passing
camlimages.5.0.5 on 5.0 is now installable. Current state is: passing
camlimages.5.0.5 on 5.1 is now installable. Current state is: passing
camlp4.4.08+1 on 4.08 had its build status changed: failing to passing
camlp4.4.09+1 on 4.09 had its build status changed: failing to passing
camlp4.4.10+1 on 4.10 had its build status changed: failing to passing
camlp4.4.11+1 on 4.11 had its build status changed: failing to passing
camlp4.4.12+1 on 4.12 had its build status changed: failing to passing
camlp4.4.13+1 on 4.13 had its build status changed: failing to passing
camlp4.4.14+1 on 4.14 had its build status changed: failing to passing
camlp4.5.0 on 5.0 had its build status changed: failing to passing
capnp-rpc-lwt.0.3.1 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.1 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.1 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.1 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.2 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.2 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.2 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.2 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.3 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.3 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.3 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.3.3 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.4.0 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.4.0 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.4.0 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-lwt.0.4.0 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.1 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.1 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.1 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.1 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.2 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.2 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.2 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.2 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.3 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.3 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.3 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.3.3 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.4.0 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.4.0 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.4.0 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.4.0 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.5.0 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.5.0 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.5.0 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-mirage.0.5.0 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-net.0.5.0 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-net.0.5.0 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-net.0.5.0 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-net.0.5.0 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.1 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.1 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.1 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.1 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.2 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.2 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.2 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.2 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.3 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.3 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.3 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-unix.0.3.3 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-unix.0.4.0 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-unix.0.4.0 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-unix.0.4.0 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-unix.0.4.0 on 4.11 had its build status changed: partially failing to passing
capnp-rpc-unix.0.5.0 on 4.08 had its build status changed: partially failing to passing
capnp-rpc-unix.0.5.0 on 4.09 had its build status changed: partially failing to passing
capnp-rpc-unix.0.5.0 on 4.10 had its build status changed: partially failing to passing
capnp-rpc-unix.0.5.0 on 4.11 had its build status changed: partially failing to passing
castore.0.0.1 on 5.1 is now installable. Current state is: passing
castore.0.0.2 on 5.1 is now installable. Current state is: passing
cca.0.7 on 4.14 had its build status changed: partially failing to passing
cdrom.0.9.1 on 4.08 had its build status changed: partially failing to passing
cdrom.0.9.1 on 4.09 had its build status changed: partially failing to passing
cdrom.0.9.1 on 4.10 had its build status changed: partially failing to passing
cdrom.0.9.1 on 4.11 had its build status changed: partially failing to passing
cdrom.0.9.1 on 4.12 had its build status changed: partially failing to passing
cdrom.0.9.1 on 4.13 had its build status changed: partially failing to passing
cdrom.0.9.1 on 4.14 had its build status changed: partially failing to passing
cdrom.0.9.1 on 5.0 had its build status changed: partially failing to passing
cdrom.0.9.1 on 5.1 had its build status changed: partially failing to passing
cgi.0.9 on 4.13 had its build status changed: failing to passing
chrome-trace.3.12.1 on 4.08 is now installable. Current state is: passing
chrome-trace.3.12.1 on 4.09 is now installable. Current state is: passing
chrome-trace.3.12.1 on 4.10 is now installable. Current state is: passing
chrome-trace.3.12.1 on 4.11 is now installable. Current state is: passing
chrome-trace.3.12.1 on 4.12 is now installable. Current state is: passing
chrome-trace.3.12.1 on 4.13 is now installable. Current state is: passing
chrome-trace.3.12.1 on 4.14 is now installable. Current state is: passing
chrome-trace.3.12.1 on 5.0 is now installable. Current state is: passing
chrome-trace.3.12.1 on 5.1 is now installable. Current state is: passing
cll.0.2.0 on 4.08 is now installable. Current state is: passing
cll.0.2.0 on 4.09 is now installable. Current state is: passing
cll.0.2.0 on 4.10 is now installable. Current state is: passing
cll.0.2.0 on 4.11 is now installable. Current state is: passing
cll.0.2.0 on 4.12 is now installable. Current state is: passing
cll.0.2.0 on 4.13 is now installable. Current state is: passing
cll.0.2.0 on 4.14 is now installable. Current state is: passing
cll.0.2.0 on 5.0 is now installable. Current state is: passing
cll.0.2.0 on 5.1 is now installable. Current state is: passing
cloudi.2.0.7 on 4.08 is now installable. Current state is: passing
cloudi.2.0.7 on 4.09 is now installable. Current state is: passing
cloudi.2.0.7 on 4.10 is now installable. Current state is: passing
cloudi.2.0.7 on 4.11 is now installable. Current state is: passing
cloudi.2.0.7 on 4.12 is now installable. Current state is: passing
cloudi.2.0.7 on 4.13 is now installable. Current state is: passing
cloudi.2.0.7 on 4.14 is now installable. Current state is: passing
cloudi.2.0.7 on 5.0 is now installable. Current state is: passing
cloudi.2.0.7 on 5.1 is now installable. Current state is: passing
cmarkit.0.3.0 on 4.14 is now installable. Current state is: passing
cmarkit.0.3.0 on 5.0 is now installable. Current state is: passing
cmarkit.0.3.0 on 5.1 is now installable. Current state is: passing
cohttp-curl-async.6.0.0~alpha1 on 4.11 had its build status changed: internal failure to passing
cohttp-lwt.5.2.0 on 4.12 had its build status changed: partially failing to passing
cohttp-mirage.1.0.0 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.1.0.0 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.1.0.0 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.1.0.0 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.1.0.1 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.1.0.1 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.1.0.1 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.1.0.1 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.1.0.2 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.1.0.2 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.1.0.2 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.1.0.2 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.1.1.0 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.1.1.0 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.1.1.0 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.1.1.0 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.1.1.1 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.1.1.1 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.1.1.1 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.1.1.1 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.1.2.0 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.1.2.0 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.1.2.0 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.1.2.0 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.2.0.0 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.2.0.0 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.2.0.0 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.2.0.0 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.2.1.0 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.2.1.0 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.2.1.0 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.2.1.0 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.2.1.1 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.2.1.1 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.2.1.1 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.2.1.1 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.2.1.3 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.2.1.3 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.2.1.3 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.2.1.3 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.2.2.0 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.2.2.0 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.2.2.0 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.2.2.0 on 4.11 had its build status changed: partially failing to passing
cohttp-mirage.2.3.0 on 4.08 had its build status changed: partially failing to passing
cohttp-mirage.2.3.0 on 4.09 had its build status changed: partially failing to passing
cohttp-mirage.2.3.0 on 4.10 had its build status changed: partially failing to passing
cohttp-mirage.2.3.0 on 4.11 had its build status changed: partially failing to passing
cohttp.5.3.1 on 4.08 is now installable. Current state is: passing
cohttp.5.3.1 on 4.09 is now installable. Current state is: passing
cohttp.5.3.1 on 4.10 is now installable. Current state is: passing
cohttp.5.3.1 on 4.11 is now installable. Current state is: passing
cohttp.5.3.1 on 4.12 is now installable. Current state is: passing
cohttp.5.3.1 on 4.13 is now installable. Current state is: passing
cohttp.5.3.1 on 4.14 is now installable. Current state is: passing
cohttp.5.3.1 on 5.0 is now installable. Current state is: passing
cohttp.5.3.1 on 5.1 is now installable. Current state is: passing
coin.0.1.0 on 4.09 had its build status changed: partially failing to passing
coin.0.1.0 on 4.10 had its build status changed: partially failing to passing
coin.0.1.0 on 4.11 had its build status changed: partially failing to passing
colors.0.0.1 on 4.13 is now installable. Current state is: passing
colors.0.0.1 on 4.14 is now installable. Current state is: passing
colors.0.0.1 on 5.0 is now installable. Current state is: passing
colors.0.0.1 on 5.1 is now installable. Current state is: passing
conduit-async.6.2.1 on 4.11 is now installable. Current state is: passing
conduit-async.6.2.1 on 4.12 is now installable. Current state is: passing
conduit-async.6.2.1 on 4.13 is now installable. Current state is: passing
conduit-async.6.2.1 on 4.14 is now installable. Current state is: passing
conduit-async.6.2.1 on 5.0 is now installable. Current state is: passing
conduit-async.6.2.1 on 5.1 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 4.08 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 4.09 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 4.10 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 4.11 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 4.12 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 4.13 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 4.14 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 5.0 is now installable. Current state is: passing
conduit-lwt-unix.6.2.1 on 5.1 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 4.08 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 4.09 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 4.10 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 4.11 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 4.12 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 4.13 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 4.14 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 5.0 is now installable. Current state is: passing
conduit-lwt.6.2.1 on 5.1 is now installable. Current state is: passing
conduit-mirage.2.0.0 on 4.08 had its build status changed: partially failing to passing
conduit-mirage.2.0.0 on 4.09 had its build status changed: partially failing to passing
conduit-mirage.2.0.0 on 4.10 had its build status changed: partially failing to passing
conduit-mirage.2.0.0 on 4.11 had its build status changed: partially failing to passing
conduit-mirage.2.0.1 on 4.08 had its build status changed: partially failing to passing
conduit-mirage.2.0.1 on 4.09 had its build status changed: partially failing to passing
conduit-mirage.2.0.1 on 4.10 had its build status changed: partially failing to passing
conduit-mirage.2.0.1 on 4.11 had its build status changed: partially failing to passing
conduit-mirage.2.0.2 on 4.08 had its build status changed: partially failing to passing
conduit-mirage.2.0.2 on 4.09 had its build status changed: partially failing to passing
conduit-mirage.2.0.2 on 4.10 had its build status changed: partially failing to passing
conduit-mirage.2.0.2 on 4.11 had its build status changed: partially failing to passing
conduit-mirage.6.2.1 on 4.08 is now installable. Current state is: passing
conduit-mirage.6.2.1 on 4.09 is now installable. Current state is: passing
conduit-mirage.6.2.1 on 4.10 is now installable. Current state is: passing
conduit-mirage.6.2.1 on 4.11 is now installable. Current state is: passing
conduit-mirage.6.2.1 on 4.12 is now installable. Current state is: passing
conduit-mirage.6.2.1 on 4.13 is now installable. Current state is: passing
conduit-mirage.6.2.1 on 4.14 is now installable. Current state is: passing
conduit-mirage.6.2.1 on 5.0 is now installable. Current state is: passing
conduit-mirage.6.2.1 on 5.1 is now installable. Current state is: passing
conduit.6.2.1 on 4.08 is now installable. Current state is: passing
conduit.6.2.1 on 4.09 is now installable. Current state is: passing
conduit.6.2.1 on 4.10 is now installable. Current state is: passing
conduit.6.2.1 on 4.11 is now installable. Current state is: passing
conduit.6.2.1 on 4.12 is now installable. Current state is: passing
conduit.6.2.1 on 4.13 is now installable. Current state is: passing
conduit.6.2.1 on 4.14 is now installable. Current state is: passing
conduit.6.2.1 on 5.0 is now installable. Current state is: passing
conduit.6.2.1 on 5.1 is now installable. Current state is: passing
conex-mirage-crypto.0.11.1 on 4.08 had its build status changed: failing to passing
conex-mirage-crypto.0.11.1 on 4.09 had its build status changed: failing to passing
conex-mirage-crypto.0.11.1 on 4.10 had its build status changed: failing to passing
conex-mirage-crypto.0.11.1 on 4.11 had its build status changed: failing to passing
conex-mirage-crypto.0.11.1 on 4.12 had its build status changed: failing to passing
conex-mirage-crypto.0.11.1 on 4.13 had its build status changed: failing to passing
conex-mirage-crypto.0.11.1 on 4.14 had its build status changed: failing to passing
conex-mirage-crypto.0.11.1 on 5.0 had its build status changed: failing to passing
conex-mirage-crypto.0.11.1 on 5.1 had its build status changed: failing to passing
conf-freetype.1 on 4.08 had its build status changed: internal failure to passing
conf-freetype.1 on 4.09 had its build status changed: internal failure to passing
conf-freetype.1 on 4.10 had its build status changed: internal failure to passing
conf-freetype.1 on 4.11 had its build status changed: internal failure to passing
conf-freetype.1 on 4.12 had its build status changed: internal failure to passing
conf-freetype.1 on 4.13 had its build status changed: internal failure to passing
conf-freetype.1 on 4.14 had its build status changed: internal failure to passing
conf-freetype.1 on 5.0 had its build status changed: internal failure to passing
conf-freetype.1 on 5.1 had its build status changed: internal failure to passing
conf-libgccjit.1 on 4.08 is now installable. Current state is: passing
conf-libgccjit.1 on 4.09 is now installable. Current state is: passing
conf-libgccjit.1 on 4.10 is now installable. Current state is: passing
conf-libgccjit.1 on 4.11 is now installable. Current state is: passing
conf-libgccjit.1 on 4.12 is now installable. Current state is: passing
conf-libgccjit.1 on 4.13 is now installable. Current state is: passing
conf-libgccjit.1 on 4.14 is now installable. Current state is: passing
conf-libgccjit.1 on 5.0 is now installable. Current state is: passing
conf-libgccjit.1 on 5.1 is now installable. Current state is: passing
conf-scdoc.1 on 4.08 is now installable. Current state is: passing
conf-scdoc.1 on 4.09 is now installable. Current state is: passing
conf-scdoc.1 on 4.10 is now installable. Current state is: passing
conf-scdoc.1 on 4.11 is now installable. Current state is: passing
conf-scdoc.1 on 4.12 is now installable. Current state is: passing
conf-scdoc.1 on 4.13 is now installable. Current state is: passing
conf-scdoc.1 on 4.14 is now installable. Current state is: passing
conf-scdoc.1 on 5.0 is now installable. Current state is: passing
conf-scdoc.1 on 5.1 is now installable. Current state is: passing
conf-secp256k1.2 on 4.08 is now installable. Current state is: passing
conf-secp256k1.2 on 4.09 is now installable. Current state is: passing
conf-secp256k1.2 on 4.10 is now installable. Current state is: passing
conf-secp256k1.2 on 4.11 is now installable. Current state is: passing
conf-secp256k1.2 on 4.12 is now installable. Current state is: passing
conf-secp256k1.2 on 4.13 is now installable. Current state is: passing
conf-secp256k1.2 on 4.14 is now installable. Current state is: passing
conf-secp256k1.2 on 5.0 is now installable. Current state is: passing
conf-secp256k1.2 on 5.1 is now installable. Current state is: passing
config-file.1.1 on 4.08 had its build status changed: partially failing to passing
config-file.1.1 on 4.09 had its build status changed: partially failing to passing
config-file.1.1 on 4.10 had its build status changed: partially failing to passing
config-file.1.1 on 4.11 had its build status changed: partially failing to passing
config-file.1.1 on 4.12 had its build status changed: partially failing to passing
config-file.1.1 on 4.13 had its build status changed: partially failing to passing
config-file.1.1 on 4.14 had its build status changed: partially failing to passing
config-file.1.2 on 4.08 had its build status changed: partially failing to passing
config-file.1.2 on 4.09 had its build status changed: partially failing to passing
config-file.1.2 on 4.10 had its build status changed: partially failing to passing
config-file.1.2 on 4.11 had its build status changed: partially failing to passing
config-file.1.2 on 4.12 had its build status changed: partially failing to passing
config-file.1.2 on 4.13 had its build status changed: partially failing to passing
config-file.1.2 on 4.14 had its build status changed: partially failing to passing
config-file.1.2.1 on 4.08 had its build status changed: partially failing to passing
config-file.1.2.1 on 4.09 had its build status changed: partially failing to passing
config-file.1.2.1 on 4.10 had its build status changed: partially failing to passing
config-file.1.2.1 on 4.11 had its build status changed: partially failing to passing
config-file.1.2.1 on 4.12 had its build status changed: partially failing to passing
config-file.1.2.1 on 4.13 had its build status changed: partially failing to passing
config-file.1.2.1 on 4.14 had its build status changed: partially failing to passing
containers-data.3.13 on 4.08 is now installable. Current state is: passing
containers-data.3.13 on 4.09 is now installable. Current state is: passing
containers-data.3.13 on 4.10 is now installable. Current state is: passing
containers-data.3.13 on 4.11 is now installable. Current state is: passing
containers-data.3.13 on 4.12 is now installable. Current state is: passing
containers-data.3.13 on 4.13 is now installable. Current state is: passing
containers-data.3.13 on 4.14 is now installable. Current state is: passing
containers-data.3.13 on 5.0 is now installable. Current state is: passing
containers-data.3.13 on 5.1 is now installable. Current state is: passing
containers-data.3.13.1 on 4.08 is now installable. Current state is: passing
containers-data.3.13.1 on 4.09 is now installable. Current state is: passing
containers-data.3.13.1 on 4.10 is now installable. Current state is: passing
containers-data.3.13.1 on 4.11 is now installable. Current state is: passing
containers-data.3.13.1 on 4.12 is now installable. Current state is: passing
containers-data.3.13.1 on 4.13 is now installable. Current state is: passing
containers-data.3.13.1 on 4.14 is now installable. Current state is: passing
containers-data.3.13.1 on 5.0 is now installable. Current state is: passing
containers-data.3.13.1 on 5.1 is now installable. Current state is: passing
containers.3.13 on 4.08 is now installable. Current state is: passing
containers.3.13 on 4.09 is now installable. Current state is: passing
containers.3.13 on 4.10 is now installable. Current state is: passing
containers.3.13 on 4.11 is now installable. Current state is: passing
containers.3.13 on 4.12 is now installable. Current state is: passing
containers.3.13 on 4.13 is now installable. Current state is: passing
containers.3.13 on 4.14 is now installable. Current state is: passing
containers.3.13 on 5.0 is now installable. Current state is: passing
containers.3.13 on 5.1 is now installable. Current state is: passing
containers.3.13.1 on 4.08 is now installable. Current state is: passing
containers.3.13.1 on 4.09 is now installable. Current state is: passing
containers.3.13.1 on 4.10 is now installable. Current state is: passing
containers.3.13.1 on 4.11 is now installable. Current state is: passing
containers.3.13.1 on 4.12 is now installable. Current state is: passing
containers.3.13.1 on 4.13 is now installable. Current state is: passing
containers.3.13.1 on 4.14 is now installable. Current state is: passing
containers.3.13.1 on 5.0 is now installable. Current state is: passing
containers.3.13.1 on 5.1 is now installable. Current state is: passing
coq-waterproof.2.1.0+8.17 on 4.14 is now installable. Current state is: passing
coq-waterproof.2.1.0+8.17 on 5.0 is now installable. Current state is: passing
coq-waterproof.2.1.0+8.17 on 5.1 is now installable. Current state is: passing
cordova.1.0 on 5.0 had its build status changed: internal failure to passing
cow.2.5.0 on 4.08 is now installable. Current state is: passing
cow.2.5.0 on 4.09 is now installable. Current state is: passing
cow.2.5.0 on 4.10 is now installable. Current state is: passing
cow.2.5.0 on 4.11 is now installable. Current state is: passing
cow.2.5.0 on 4.12 is now installable. Current state is: passing
cow.2.5.0 on 4.13 is now installable. Current state is: passing
cow.2.5.0 on 4.14 is now installable. Current state is: passing
cow.2.5.0 on 5.0 is now installable. Current state is: passing
cow.2.5.0 on 5.1 is now installable. Current state is: passing
cpm.1.0.0 on 4.08 had its build status changed: partially failing to passing
cpm.1.0.0 on 4.09 had its build status changed: partially failing to passing
cpm.1.0.0 on 4.10 had its build status changed: partially failing to passing
cpm.1.0.0 on 4.11 had its build status changed: partially failing to passing
cpm.1.0.0 on 4.12 had its build status changed: partially failing to passing
cpm.1.0.0 on 4.13 had its build status changed: partially failing to passing
cpm.1.0.0 on 4.14 had its build status changed: partially failing to passing
cpm.1.0.0 on 5.0 had its build status changed: partially failing to passing
cpm.2.0.0 on 4.08 had its build status changed: partially failing to passing
cpm.2.0.0 on 4.09 had its build status changed: partially failing to passing
cpm.2.0.0 on 4.10 had its build status changed: partially failing to passing
cpm.2.0.0 on 4.11 had its build status changed: partially failing to passing
cpm.2.0.0 on 4.12 had its build status changed: partially failing to passing
cpm.2.0.0 on 4.13 had its build status changed: partially failing to passing
cpm.2.0.0 on 4.14 had its build status changed: partially failing to passing
cpm.2.0.0 on 5.0 had its build status changed: partially failing to passing
cpm.3.0.0 on 4.08 had its build status changed: partially failing to passing
cpm.3.0.0 on 4.09 had its build status changed: partially failing to passing
cpm.3.0.0 on 4.10 had its build status changed: partially failing to passing
cpm.3.0.0 on 4.11 had its build status changed: partially failing to passing
cpm.3.0.0 on 4.12 had its build status changed: partially failing to passing
cpm.3.0.0 on 4.13 had its build status changed: partially failing to passing
cpm.3.0.0 on 4.14 had its build status changed: partially failing to passing
cpm.3.0.0 on 5.0 had its build status changed: partially failing to passing
cppffigen.0.002 on 4.12 had its build status changed: failing to passing
cppffigen.0.002 on 4.13 had its build status changed: failing to passing
cppffigen.0.002 on 4.14 had its build status changed: failing to passing
cppffigen.0.002 on 5.0 had its build status changed: failing to passing
cppffigen.0.002 on 5.1 had its build status changed: failing to passing
cryptohash.0.1 on 4.08 had its build status changed: partially failing to passing
cryptohash.0.1 on 4.09 had its build status changed: partially failing to passing
cryptohash.0.1 on 4.10 had its build status changed: partially failing to passing
cryptohash.0.1 on 4.11 had its build status changed: partially failing to passing
cryptohash.0.1 on 4.12 had its build status changed: partially failing to passing
cryptohash.0.1 on 4.13 had its build status changed: partially failing to passing
cryptohash.0.1 on 4.14 had its build status changed: partially failing to passing
cryptokit.1.19 on 4.08 is now installable. Current state is: passing
cryptokit.1.19 on 4.09 is now installable. Current state is: passing
cryptokit.1.19 on 4.10 is now installable. Current state is: passing
cryptokit.1.19 on 4.11 is now installable. Current state is: passing
cryptokit.1.19 on 4.12 is now installable. Current state is: passing
cryptokit.1.19 on 4.13 is now installable. Current state is: passing
cryptokit.1.19 on 4.14 is now installable. Current state is: passing
cryptokit.1.19 on 5.0 is now installable. Current state is: passing
cryptokit.1.19 on 5.1 is now installable. Current state is: passing
cryptoverif.2.08 on 4.08 is now installable. Current state is: passing
cryptoverif.2.08 on 4.09 is now installable. Current state is: passing
cryptoverif.2.08 on 4.10 is now installable. Current state is: passing
cryptoverif.2.08 on 4.11 is now installable. Current state is: passing
cryptoverif.2.08 on 4.12 is now installable. Current state is: passing
cryptoverif.2.08 on 4.13 is now installable. Current state is: passing
cryptoverif.2.08 on 4.14 is now installable. Current state is: passing
cryptoverif.2.08 on 5.0 is now installable. Current state is: passing
cryptoverif.2.08 on 5.1 is now installable. Current state is: passing
cudf.0.7 on 4.08 had its build status changed: partially failing to passing
cudf.0.7 on 4.09 had its build status changed: partially failing to passing
cudf.0.7 on 4.10 had its build status changed: partially failing to passing
cudf.0.7 on 4.11 had its build status changed: partially failing to passing
cudf.0.7 on 4.12 had its build status changed: partially failing to passing
cudf.0.7 on 4.13 had its build status changed: partially failing to passing
cudf.0.7 on 4.14 had its build status changed: partially failing to passing
cudf.0.8 on 4.08 had its build status changed: partially failing to passing
cudf.0.8 on 4.09 had its build status changed: partially failing to passing
cudf.0.8 on 4.10 had its build status changed: partially failing to passing
cudf.0.8 on 4.11 had its build status changed: partially failing to passing
cudf.0.8 on 4.12 had its build status changed: partially failing to passing
cudf.0.8 on 4.13 had its build status changed: partially failing to passing
cudf.0.8 on 4.14 had its build status changed: partially failing to passing
current_examples.0.1 on 4.08 had its build status changed: partially failing to passing
current_examples.0.1 on 4.09 had its build status changed: partially failing to passing
current_examples.0.1 on 4.10 had its build status changed: partially failing to passing
current_examples.0.1 on 4.11 had its build status changed: partially failing to passing
current_github.0.1 on 4.08 had its build status changed: partially failing to passing
current_github.0.1 on 4.09 had its build status changed: partially failing to passing
current_github.0.1 on 4.10 had its build status changed: partially failing to passing
current_github.0.1 on 4.11 had its build status changed: partially failing to passing
daft.0.0.3 on 4.08 had its build status changed: partially failing to passing
daft.0.0.3 on 4.09 had its build status changed: partially failing to passing
daft.0.0.3 on 4.10 had its build status changed: partially failing to passing
daft.0.0.3 on 4.11 had its build status changed: partially failing to passing
daft.0.0.3 on 4.12 had its build status changed: partially failing to passing
daft.0.0.3 on 4.13 had its build status changed: partially failing to passing
daft.0.0.3 on 4.14 had its build status changed: partially failing to passing
daft.0.0.3 on 5.0 had its build status changed: partially failing to passing
dates_calc.0.0.5 on 4.11 is now installable. Current state is: passing
dates_calc.0.0.5 on 4.12 is now installable. Current state is: passing
dates_calc.0.0.5 on 4.13 is now installable. Current state is: passing
dates_calc.0.0.5 on 4.14 is now installable. Current state is: passing
dates_calc.0.0.5 on 5.0 is now installable. Current state is: passing
dates_calc.0.0.5 on 5.1 is now installable. Current state is: passing
dedukti.2.6.0 on 4.08 had its build status changed: failing to passing
dedukti.2.6.0 on 4.09 had its build status changed: failing to passing
dedukti.2.6.0 on 4.10 had its build status changed: failing to passing
dedukti.2.6.0 on 4.11 had its build status changed: failing to passing
dedukti.2.6.0 on 4.12 had its build status changed: failing to passing
dedukti.2.6.0 on 4.13 had its build status changed: failing to passing
dedukti.2.6.0 on 4.14 had its build status changed: failing to passing
dedukti.2.6.0 on 5.0 had its build status changed: failing to passing
dedukti.2.6.0 on 5.1 had its build status changed: failing to passing
deriving.0.8.1 on 4.08 had its build status changed: partially failing to passing
deriving.0.8.1 on 4.09 had its build status changed: partially failing to passing
deriving.0.8.1 on 4.10 had its build status changed: partially failing to passing
deriving.0.8.1 on 4.11 had its build status changed: partially failing to passing
deriving.0.8.1 on 4.12 had its build status changed: partially failing to passing
deriving.0.8.1 on 4.13 had its build status changed: partially failing to passing
deriving.0.8.1 on 4.14 had its build status changed: partially failing to passing
devkit.1.2 on 4.08 had its build status changed: partially failing to passing
devkit.1.2 on 4.09 had its build status changed: partially failing to passing
devkit.1.2 on 4.10 had its build status changed: partially failing to passing
devkit.1.2 on 4.11 had its build status changed: partially failing to passing
devkit.1.2 on 4.12 had its build status changed: partially failing to passing
devkit.1.2 on 4.13 had its build status changed: partially failing to passing
devkit.1.2 on 4.14 had its build status changed: partially failing to passing
devkit.1.20210120 on 4.08 had its build status changed: partially failing to passing
devkit.1.20210120 on 4.09 had its build status changed: partially failing to passing
devkit.1.20210120 on 4.10 had its build status changed: partially failing to passing
devkit.1.20210120 on 4.11 had its build status changed: partially failing to passing
devkit.1.20210120 on 4.12 had its build status changed: partially failing to passing
devkit.1.20210120 on 4.13 had its build status changed: partially failing to passing
devkit.1.20210120 on 4.14 had its build status changed: partially failing to passing
devkit.1.20210517 on 4.08 had its build status changed: partially failing to passing
devkit.1.20210517 on 4.09 had its build status changed: partially failing to passing
devkit.1.20210517 on 4.10 had its build status changed: partially failing to passing
devkit.1.20210517 on 4.11 had its build status changed: partially failing to passing
devkit.1.20210517 on 4.12 had its build status changed: partially failing to passing
devkit.1.20210517 on 4.13 had its build status changed: partially failing to passing
devkit.1.20210517 on 4.14 had its build status changed: partially failing to passing
devkit.1.3 on 4.08 had its build status changed: partially failing to passing
devkit.1.3 on 4.09 had its build status changed: partially failing to passing
devkit.1.3 on 4.10 had its build status changed: partially failing to passing
devkit.1.3 on 4.11 had its build status changed: partially failing to passing
devkit.1.3 on 4.12 had its build status changed: partially failing to passing
devkit.1.3 on 4.13 had its build status changed: partially failing to passing
devkit.1.3 on 4.14 had its build status changed: partially failing to passing
dirsp-ps2ocaml.0.1.0 on 4.08 had its build status changed: partially failing to passing
dirsp-ps2ocaml.0.1.0 on 4.09 had its build status changed: partially failing to passing
dirsp-ps2ocaml.0.1.0 on 4.10 had its build status changed: partially failing to passing
dirsp-ps2ocaml.0.1.0 on 4.11 had its build status changed: partially failing to passing
dirsp-ps2ocaml.0.1.0 on 4.12 had its build status changed: partially failing to passing
dirsp-ps2ocaml.0.1.0 on 4.13 had its build status changed: partially failing to passing
dirsp-ps2ocaml.0.1.0 on 4.14 had its build status changed: partially failing to passing
dkml-install-installer.0.5.2 on 4.10 is now installable. Current state is: passing
dkml-install-installer.0.5.2 on 4.11 is now installable. Current state is: passing
dkml-install-installer.0.5.2 on 4.12 is now installable. Current state is: passing
dkml-install-installer.0.5.2 on 4.13 is now installable. Current state is: passing
dkml-install-installer.0.5.2 on 4.14 is now installable. Current state is: passing
dkml-install-installer.0.5.2 on 5.0 is now installable. Current state is: passing
dkml-install-installer.0.5.2 on 5.1 is now installable. Current state is: passing
dkml-install-runner.0.5.2 on 4.10 is now installable. Current state is: passing
dkml-install-runner.0.5.2 on 4.11 is now installable. Current state is: passing
dkml-install-runner.0.5.2 on 4.12 is now installable. Current state is: passing
dkml-install-runner.0.5.2 on 4.13 is now installable. Current state is: passing
dkml-install-runner.0.5.2 on 4.14 is now installable. Current state is: passing
dkml-install-runner.0.5.2 on 5.0 is now installable. Current state is: passing
dkml-install-runner.0.5.2 on 5.1 is now installable. Current state is: passing
dkml-install.0.5.2 on 4.08 is now installable. Current state is: passing
dkml-install.0.5.2 on 4.09 is now installable. Current state is: passing
dkml-install.0.5.2 on 4.10 is now installable. Current state is: passing
dkml-install.0.5.2 on 4.11 is now installable. Current state is: passing
dkml-install.0.5.2 on 4.12 is now installable. Current state is: passing
dkml-install.0.5.2 on 4.13 is now installable. Current state is: passing
dkml-install.0.5.2 on 4.14 is now installable. Current state is: passing
dkml-install.0.5.2 on 5.0 is now installable. Current state is: passing
dkml-install.0.5.2 on 5.1 is now installable. Current state is: passing
dkml-package-console.0.5.2 on 4.10 is now installable. Current state is: passing
dkml-package-console.0.5.2 on 4.11 is now installable. Current state is: passing
dkml-package-console.0.5.2 on 4.12 is now installable. Current state is: passing
dkml-package-console.0.5.2 on 4.13 is now installable. Current state is: passing
dkml-package-console.0.5.2 on 4.14 is now installable. Current state is: passing
dkml-package-console.0.5.2 on 5.0 is now installable. Current state is: passing
dkml-package-console.0.5.2 on 5.1 is now installable. Current state is: passing
dns-certify.4.0.0 on 4.08 had its build status changed: partially failing to passing
dns-certify.4.0.0 on 4.09 had its build status changed: partially failing to passing
dns-certify.4.0.0 on 4.10 had its build status changed: partially failing to passing
dns-certify.4.0.0 on 4.11 had its build status changed: partially failing to passing
dns-certify.4.1.0 on 4.08 had its build status changed: partially failing to passing
dns-certify.4.1.0 on 4.09 had its build status changed: partially failing to passing
dns-certify.4.1.0 on 4.10 had its build status changed: partially failing to passing
dns-certify.4.1.0 on 4.11 had its build status changed: partially failing to passing
dns-certify.4.2.0 on 4.08 had its build status changed: partially failing to passing
dns-certify.4.2.0 on 4.09 had its build status changed: partially failing to passing
dns-certify.4.2.0 on 4.10 had its build status changed: partially failing to passing
dns-certify.4.2.0 on 4.11 had its build status changed: partially failing to passing
dns-certify.4.3.0 on 4.08 had its build status changed: partially failing to passing
dns-certify.4.3.0 on 4.09 had its build status changed: partially failing to passing
dns-certify.4.3.0 on 4.10 had its build status changed: partially failing to passing
dns-certify.4.3.0 on 4.11 had its build status changed: partially failing to passing
dns-certify.4.3.1 on 4.08 had its build status changed: partially failing to passing
dns-certify.4.3.1 on 4.09 had its build status changed: partially failing to passing
dns-certify.4.3.1 on 4.10 had its build status changed: partially failing to passing
dns-certify.4.3.1 on 4.11 had its build status changed: partially failing to passing
dns-cli.4.0.0 on 4.08 had its build status changed: partially failing to passing
dns-cli.4.0.0 on 4.09 had its build status changed: partially failing to passing
dns-cli.4.0.0 on 4.10 had its build status changed: partially failing to passing
dns-cli.4.0.0 on 4.11 had its build status changed: partially failing to passing
dns-cli.4.1.0 on 4.08 had its build status changed: partially failing to passing
dns-cli.4.1.0 on 4.09 had its build status changed: partially failing to passing
dns-cli.4.1.0 on 4.10 had its build status changed: partially failing to passing
dns-cli.4.1.0 on 4.11 had its build status changed: partially failing to passing
dns-cli.4.2.0 on 4.08 had its build status changed: partially failing to passing
dns-cli.4.2.0 on 4.09 had its build status changed: partially failing to passing
dns-cli.4.2.0 on 4.10 had its build status changed: partially failing to passing
dns-cli.4.2.0 on 4.11 had its build status changed: partially failing to passing
dns-cli.4.3.0 on 4.08 had its build status changed: partially failing to passing
dns-cli.4.3.0 on 4.09 had its build status changed: partially failing to passing
dns-cli.4.3.0 on 4.10 had its build status changed: partially failing to passing
dns-cli.4.3.0 on 4.11 had its build status changed: partially failing to passing
dns-cli.4.3.1 on 4.08 had its build status changed: partially failing to passing
dns-cli.4.3.1 on 4.09 had its build status changed: partially failing to passing
dns-cli.4.3.1 on 4.10 had its build status changed: partially failing to passing
dns-cli.4.3.1 on 4.11 had its build status changed: partially failing to passing
dns-server.6.1.3 on 5.1 had its build status changed: internal failure to passing
dokeysto_lz4.3.0.0 on 4.08 had its build status changed: partially failing to passing
dokeysto_lz4.3.0.0 on 4.09 had its build status changed: partially failing to passing
dokeysto_lz4.3.0.0 on 4.10 had its build status changed: partially failing to passing
dokeysto_lz4.3.0.0 on 4.11 had its build status changed: partially failing to passing
dream-html.1.2.0 on 4.08 is now installable. Current state is: passing
dream-html.1.2.0 on 4.09 is now installable. Current state is: passing
dream-html.1.2.0 on 4.10 is now installable. Current state is: passing
dream-html.1.2.0 on 4.11 is now installable. Current state is: passing
dream-html.1.2.0 on 4.12 is now installable. Current state is: passing
dream-html.1.2.0 on 4.13 is now installable. Current state is: passing
dream-html.1.2.0 on 4.14 is now installable. Current state is: passing
dream-html.1.2.0 on 5.0 is now installable. Current state is: passing
dream-html.1.2.0 on 5.1 is now installable. Current state is: passing
dream-html.2.0.0 on 4.08 is now installable. Current state is: passing
dream-html.2.0.0 on 4.09 is now installable. Current state is: passing
dream-html.2.0.0 on 4.10 is now installable. Current state is: passing
dream-html.2.0.0 on 4.11 is now installable. Current state is: passing
dream-html.2.0.0 on 4.12 is now installable. Current state is: passing
dream-html.2.0.0 on 4.13 is now installable. Current state is: passing
dream-html.2.0.0 on 4.14 is now installable. Current state is: passing
dream-html.2.0.0 on 5.0 is now installable. Current state is: passing
dream-html.2.0.0 on 5.1 is now installable. Current state is: passing
dscheck.0.3.0 on 5.0 is now installable. Current state is: passing
dscheck.0.3.0 on 5.1 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 4.08 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 4.09 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 4.10 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 4.11 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 4.12 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 4.13 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 4.14 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 5.0 is now installable. Current state is: passing
dune-action-plugin.3.12.1 on 5.1 is now installable. Current state is: passing
dune-build-info.3.12.1 on 4.08 is now installable. Current state is: passing
dune-build-info.3.12.1 on 4.09 is now installable. Current state is: passing
dune-build-info.3.12.1 on 4.10 is now installable. Current state is: passing
dune-build-info.3.12.1 on 4.11 is now installable. Current state is: passing
dune-build-info.3.12.1 on 4.12 is now installable. Current state is: passing
dune-build-info.3.12.1 on 4.13 is now installable. Current state is: passing
dune-build-info.3.12.1 on 4.14 is now installable. Current state is: passing
dune-build-info.3.12.1 on 5.0 is now installable. Current state is: passing
dune-build-info.3.12.1 on 5.1 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 4.08 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 4.09 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 4.10 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 4.11 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 4.12 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 4.13 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 4.14 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 5.0 is now installable. Current state is: passing
dune-compiledb.0.5.0 on 5.1 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 4.08 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 4.09 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 4.10 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 4.11 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 4.12 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 4.13 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 4.14 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 5.0 is now installable. Current state is: passing
dune-compiledb.0.6.0 on 5.1 is now installable. Current state is: passing
dune-configurator.3.12.1 on 4.08 is now installable. Current state is: passing
dune-configurator.3.12.1 on 4.09 is now installable. Current state is: passing
dune-configurator.3.12.1 on 4.10 is now installable. Current state is: passing
dune-configurator.3.12.1 on 4.11 is now installable. Current state is: passing
dune-configurator.3.12.1 on 4.12 is now installable. Current state is: passing
dune-configurator.3.12.1 on 4.13 is now installable. Current state is: passing
dune-configurator.3.12.1 on 4.14 is now installable. Current state is: passing
dune-configurator.3.12.1 on 5.0 is now installable. Current state is: passing
dune-configurator.3.12.1 on 5.1 is now installable. Current state is: passing
dune-glob.3.12.1 on 4.08 is now installable. Current state is: passing
dune-glob.3.12.1 on 4.09 is now installable. Current state is: passing
dune-glob.3.12.1 on 4.10 is now installable. Current state is: passing
dune-glob.3.12.1 on 4.11 is now installable. Current state is: passing
dune-glob.3.12.1 on 4.12 is now installable. Current state is: passing
dune-glob.3.12.1 on 4.13 is now installable. Current state is: passing
dune-glob.3.12.1 on 4.14 is now installable. Current state is: passing
dune-glob.3.12.1 on 5.0 is now installable. Current state is: passing
dune-glob.3.12.1 on 5.1 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 4.08 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 4.09 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 4.10 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 4.11 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 4.12 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 4.13 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 4.14 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 5.0 is now installable. Current state is: passing
dune-private-libs.3.12.1 on 5.1 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 4.08 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 4.09 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 4.10 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 4.11 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 4.12 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 4.13 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 4.14 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 5.0 is now installable. Current state is: passing
dune-rpc-lwt.3.12.1 on 5.1 is now installable. Current state is: passing
dune-rpc.3.12.1 on 4.08 is now installable. Current state is: passing
dune-rpc.3.12.1 on 4.09 is now installable. Current state is: passing
dune-rpc.3.12.1 on 4.10 is now installable. Current state is: passing
dune-rpc.3.12.1 on 4.11 is now installable. Current state is: passing
dune-rpc.3.12.1 on 4.12 is now installable. Current state is: passing
dune-rpc.3.12.1 on 4.13 is now installable. Current state is: passing
dune-rpc.3.12.1 on 4.14 is now installable. Current state is: passing
dune-rpc.3.12.1 on 5.0 is now installable. Current state is: passing
dune-rpc.3.12.1 on 5.1 is now installable. Current state is: passing
dune-site.3.12.1 on 4.08 is now installable. Current state is: passing
dune-site.3.12.1 on 4.09 is now installable. Current state is: passing
dune-site.3.12.1 on 4.10 is now installable. Current state is: passing
dune-site.3.12.1 on 4.11 is now installable. Current state is: passing
dune-site.3.12.1 on 4.12 is now installable. Current state is: passing
dune-site.3.12.1 on 4.13 is now installable. Current state is: passing
dune-site.3.12.1 on 4.14 is now installable. Current state is: passing
dune-site.3.12.1 on 5.0 is now installable. Current state is: passing
dune-site.3.12.1 on 5.1 is now installable. Current state is: passing
dune-site.3.6.1 on 4.12 had its build status changed: internal failure to passing
dune.3.12.1 on 4.08 is now installable. Current state is: passing
dune.3.12.1 on 4.09 is now installable. Current state is: passing
dune.3.12.1 on 4.10 is now installable. Current state is: passing
dune.3.12.1 on 4.11 is now installable. Current state is: passing
dune.3.12.1 on 4.12 is now installable. Current state is: passing
dune.3.12.1 on 4.13 is now installable. Current state is: passing
dune.3.12.1 on 4.14 is now installable. Current state is: passing
dune.3.12.1 on 5.0 is now installable. Current state is: passing
dune.3.12.1 on 5.1 is now installable. Current state is: passing
duppy.0.7.0 on 4.08 had its build status changed: partially failing to passing
duppy.0.7.0 on 4.09 had its build status changed: partially failing to passing
duppy.0.7.0 on 4.10 had its build status changed: partially failing to passing
duppy.0.7.0 on 4.11 had its build status changed: partially failing to passing
duppy.0.7.0 on 4.12 had its build status changed: partially failing to passing
duppy.0.7.0 on 4.13 had its build status changed: partially failing to passing
duppy.0.7.0 on 4.14 had its build status changed: partially failing to passing
duppy.0.7.0 on 5.0 had its build status changed: partially failing to passing
duppy.0.7.1 on 4.08 had its build status changed: partially failing to passing
duppy.0.7.1 on 4.09 had its build status changed: partially failing to passing
duppy.0.7.1 on 4.10 had its build status changed: partially failing to passing
duppy.0.7.1 on 4.11 had its build status changed: partially failing to passing
duppy.0.7.1 on 4.12 had its build status changed: partially failing to passing
duppy.0.7.1 on 4.13 had its build status changed: partially failing to passing
duppy.0.7.1 on 4.14 had its build status changed: partially failing to passing
duppy.0.7.1 on 5.0 had its build status changed: partially failing to passing
duppy.0.7.3 on 4.08 had its build status changed: partially failing to passing
duppy.0.7.3 on 4.09 had its build status changed: partially failing to passing
duppy.0.7.3 on 4.10 had its build status changed: partially failing to passing
duppy.0.7.3 on 4.11 had its build status changed: partially failing to passing
duppy.0.7.3 on 4.12 had its build status changed: partially failing to passing
duppy.0.7.3 on 4.13 had its build status changed: partially failing to passing
duppy.0.7.3 on 4.14 had its build status changed: partially failing to passing
duppy.0.7.3 on 5.0 had its build status changed: partially failing to passing
dyn.3.12.1 on 4.08 is now installable. Current state is: passing
dyn.3.12.1 on 4.09 is now installable. Current state is: passing
dyn.3.12.1 on 4.10 is now installable. Current state is: passing
dyn.3.12.1 on 4.11 is now installable. Current state is: passing
dyn.3.12.1 on 4.12 is now installable. Current state is: passing
dyn.3.12.1 on 4.13 is now installable. Current state is: passing
dyn.3.12.1 on 4.14 is now installable. Current state is: passing
dyn.3.12.1 on 5.0 is now installable. Current state is: passing
dyn.3.12.1 on 5.1 is now installable. Current state is: passing
dyntype.0.9.0 on 4.08 had its build status changed: partially failing to passing
dyntype.0.9.0 on 4.09 had its build status changed: partially failing to passing
dyntype.0.9.0 on 4.10 had its build status changed: partially failing to passing
dyntype.0.9.0 on 4.11 had its build status changed: partially failing to passing
dyntype.0.9.0 on 4.12 had its build status changed: partially failing to passing
dyntype.0.9.0 on 4.13 had its build status changed: partially failing to passing
dyntype.0.9.0 on 4.14 had its build status changed: partially failing to passing
earlybird.1.0.2 on 4.11 had its build status changed: internal failure to passing
elasticsearch-cli.0.5 on 4.08 had its build status changed: partially failing to passing
elasticsearch-cli.0.5 on 4.09 had its build status changed: partially failing to passing
elasticsearch-cli.0.5 on 4.10 had its build status changed: partially failing to passing
elasticsearch-cli.0.5 on 4.11 had its build status changed: partially failing to passing
elasticsearch-cli.0.5 on 4.12 had its build status changed: partially failing to passing
elasticsearch-cli.0.5 on 4.13 had its build status changed: partially failing to passing
elasticsearch-cli.0.5 on 4.14 had its build status changed: partially failing to passing
elasticsearch-cli.1.0 on 4.08 had its build status changed: partially failing to passing
elasticsearch-cli.1.0 on 4.09 had its build status changed: partially failing to passing
elasticsearch-cli.1.0 on 4.10 had its build status changed: partially failing to passing
elasticsearch-cli.1.0 on 4.11 had its build status changed: partially failing to passing
elasticsearch-cli.1.0 on 4.12 had its build status changed: partially failing to passing
elasticsearch-cli.1.0 on 4.13 had its build status changed: partially failing to passing
elasticsearch-cli.1.0 on 4.14 had its build status changed: partially failing to passing
elasticsearch-cli.1.1 on 4.08 had its build status changed: partially failing to passing
elasticsearch-cli.1.1 on 4.09 had its build status changed: partially failing to passing
elasticsearch-cli.1.1 on 4.10 had its build status changed: partially failing to passing
elasticsearch-cli.1.1 on 4.11 had its build status changed: partially failing to passing
elasticsearch-cli.1.1 on 4.12 had its build status changed: partially failing to passing
elasticsearch-cli.1.1 on 4.13 had its build status changed: partially failing to passing
elasticsearch-cli.1.1 on 4.14 had its build status changed: partially failing to passing
elasticsearch-cli.1.2 on 4.08 had its build status changed: partially failing to passing
elasticsearch-cli.1.2 on 4.09 had its build status changed: partially failing to passing
elasticsearch-cli.1.2 on 4.10 had its build status changed: partially failing to passing
elasticsearch-cli.1.2 on 4.11 had its build status changed: partially failing to passing
elasticsearch-cli.1.2 on 4.12 had its build status changed: partially failing to passing
elasticsearch-cli.1.2 on 4.13 had its build status changed: partially failing to passing
elasticsearch-cli.1.2 on 4.14 had its build status changed: partially failing to passing
eliom.10.2.0 on 4.08 is now installable. Current state is: passing
eliom.10.2.0 on 4.09 is now installable. Current state is: passing
eliom.10.2.0 on 4.10 is now installable. Current state is: passing
eliom.10.2.0 on 4.11 is now installable. Current state is: passing
eliom.10.2.0 on 4.12 is now installable. Current state is: passing
eliom.10.2.0 on 4.13 is now installable. Current state is: passing
eliom.10.2.0 on 4.14 is now installable. Current state is: passing
eliom.10.2.0 on 5.0 is now installable. Current state is: passing
eliom.10.2.0 on 5.1 is now installable. Current state is: passing
eliom.6.10.1 on 4.08 had its build status changed: partially failing to passing
eliom.6.10.1 on 4.09 had its build status changed: partially failing to passing
eliom.6.10.1 on 4.10 had its build status changed: partially failing to passing
eliom.6.8.0 on 4.08 had its build status changed: partially failing to passing
eliom.6.8.1 on 4.08 had its build status changed: partially failing to passing
eliom.6.9.1 on 4.08 had its build status changed: partially failing to passing
eliom.6.9.2 on 4.08 had its build status changed: partially failing to passing
eliom.6.9.3 on 4.08 had its build status changed: partially failing to passing
elpi.1.18.1 on 4.08 is now installable. Current state is: passing
elpi.1.18.1 on 4.09 is now installable. Current state is: passing
elpi.1.18.1 on 4.10 is now installable. Current state is: passing
elpi.1.18.1 on 4.11 is now installable. Current state is: passing
elpi.1.18.1 on 4.12 is now installable. Current state is: passing
elpi.1.18.1 on 4.13 is now installable. Current state is: passing
elpi.1.18.1 on 4.14 is now installable. Current state is: passing
elpi.1.18.1 on 5.0 is now installable. Current state is: passing
elpi.1.18.1 on 5.1 is now installable. Current state is: passing
encoding.0.0.1 on 5.1 is now installable. Current state is: passing
eprover.3.0 on 4.08 is now installable. Current state is: passing
eprover.3.0 on 4.09 is now installable. Current state is: passing
eprover.3.0 on 4.10 is now installable. Current state is: passing
eprover.3.0 on 4.11 is now installable. Current state is: passing
eprover.3.0 on 4.12 is now installable. Current state is: passing
eprover.3.0 on 4.13 is now installable. Current state is: passing
eprover.3.0 on 4.14 is now installable. Current state is: passing
eprover.3.0 on 5.0 is now installable. Current state is: passing
eprover.3.0 on 5.1 is now installable. Current state is: passing
errpy.0.0.10 on 4.08 is now installable. Current state is: passing
errpy.0.0.10 on 4.09 is now installable. Current state is: passing
errpy.0.0.10 on 4.10 is now installable. Current state is: passing
errpy.0.0.10 on 4.11 is now installable. Current state is: passing
errpy.0.0.10 on 4.12 is now installable. Current state is: passing
errpy.0.0.10 on 4.13 is now installable. Current state is: passing
errpy.0.0.10 on 4.14 is now installable. Current state is: passing
errpy.0.0.10 on 5.0 is now installable. Current state is: passing
errpy.0.0.10 on 5.1 is now installable. Current state is: passing
esperanto-cosmopolitan.0.0.5 on 4.13 is now installable. Current state is: passing
esperanto-cosmopolitan.0.0.5 on 4.14 is now installable. Current state is: passing
esperanto-cosmopolitan.0.0.5 on 5.0 is now installable. Current state is: passing
esperanto-cosmopolitan.0.0.5 on 5.1 is now installable. Current state is: passing
extprot.1.6.0 on 4.08 had its build status changed: partially failing to passing
extprot.1.6.0 on 4.09 had its build status changed: partially failing to passing
extprot.1.6.0 on 4.10 had its build status changed: partially failing to passing
extprot.1.6.0 on 4.11 had its build status changed: partially failing to passing
extprot.1.6.0 on 4.12 had its build status changed: partially failing to passing
extprot.1.6.0 on 4.13 had its build status changed: partially failing to passing
extprot.1.6.0 on 4.14 had its build status changed: partially failing to passing
extprot.1.7.0 on 4.08 had its build status changed: partially failing to passing
extprot.1.7.0 on 4.09 had its build status changed: partially failing to passing
extprot.1.7.0 on 4.10 had its build status changed: partially failing to passing
extprot.1.7.0 on 4.11 had its build status changed: partially failing to passing
extprot.1.7.0 on 4.12 had its build status changed: partially failing to passing
extprot.1.7.0 on 4.13 had its build status changed: partially failing to passing
extprot.1.7.0 on 4.14 had its build status changed: partially failing to passing
extunix.0.1.4 on 4.08 had its build status changed: partially failing to passing
extunix.0.1.4 on 4.09 had its build status changed: partially failing to passing
extunix.0.1.4 on 4.10 had its build status changed: partially failing to passing
extunix.0.1.4 on 4.11 had its build status changed: partially failing to passing
extunix.0.1.4 on 4.12 had its build status changed: partially failing to passing
extunix.0.1.4 on 4.13 had its build status changed: partially failing to passing
extunix.0.1.4 on 4.14 had its build status changed: partially failing to passing
extunix.0.1.5 on 4.08 had its build status changed: partially failing to passing
extunix.0.1.5 on 4.09 had its build status changed: partially failing to passing
extunix.0.1.5 on 4.10 had its build status changed: partially failing to passing
extunix.0.1.5 on 4.11 had its build status changed: partially failing to passing
extunix.0.1.5 on 4.12 had its build status changed: partially failing to passing
extunix.0.1.5 on 4.13 had its build status changed: partially failing to passing
extunix.0.1.5 on 4.14 had its build status changed: partially failing to passing
extunix.0.1.6 on 4.08 had its build status changed: partially failing to passing
extunix.0.1.6 on 4.09 had its build status changed: partially failing to passing
extunix.0.1.6 on 4.10 had its build status changed: partially failing to passing
extunix.0.1.6 on 4.11 had its build status changed: partially failing to passing
extunix.0.1.6 on 4.12 had its build status changed: partially failing to passing
extunix.0.1.6 on 4.13 had its build status changed: partially failing to passing
extunix.0.1.6 on 4.14 had its build status changed: partially failing to passing
ezcurl-lwt.0.2.4 on 4.08 is now installable. Current state is: passing
ezcurl-lwt.0.2.4 on 4.09 is now installable. Current state is: passing
ezcurl-lwt.0.2.4 on 4.10 is now installable. Current state is: passing
ezcurl-lwt.0.2.4 on 4.11 is now installable. Current state is: passing
ezcurl-lwt.0.2.4 on 4.12 is now installable. Current state is: passing
ezcurl-lwt.0.2.4 on 4.13 is now installable. Current state is: passing
ezcurl-lwt.0.2.4 on 4.14 is now installable. Current state is: passing
ezcurl-lwt.0.2.4 on 5.0 is now installable. Current state is: passing
ezcurl-lwt.0.2.4 on 5.1 is now installable. Current state is: passing
ezcurl.0.2.4 on 4.08 is now installable. Current state is: passing
ezcurl.0.2.4 on 4.09 is now installable. Current state is: passing
ezcurl.0.2.4 on 4.10 is now installable. Current state is: passing
ezcurl.0.2.4 on 4.11 is now installable. Current state is: passing
ezcurl.0.2.4 on 4.12 is now installable. Current state is: passing
ezcurl.0.2.4 on 4.13 is now installable. Current state is: passing
ezcurl.0.2.4 on 4.14 is now installable. Current state is: passing
ezcurl.0.2.4 on 5.0 is now installable. Current state is: passing
ezcurl.0.2.4 on 5.1 is now installable. Current state is: passing
facteur.0.1.0 on 4.08 had its build status changed: partially failing to passing
facteur.0.1.0 on 4.09 had its build status changed: partially failing to passing
facteur.0.1.0 on 4.10 had its build status changed: partially failing to passing
facteur.0.1.0 on 4.11 had its build status changed: partially failing to passing
ffmpeg-av.1.0.1 on 4.09 had its build status changed: internal failure to passing
ffmpeg-avfilter.1.0.0 on 5.1 had its build status changed: internal failure to passing
fit.1.2.0 on 4.08 is now installable. Current state is: passing
fit.1.2.0 on 4.09 is now installable. Current state is: passing
fit.1.2.0 on 4.10 is now installable. Current state is: passing
fit.1.2.0 on 4.11 is now installable. Current state is: passing
fit.1.2.0 on 4.12 is now installable. Current state is: passing
fit.1.2.0 on 4.13 is now installable. Current state is: passing
fit.1.2.0 on 4.14 is now installable. Current state is: passing
fit.1.2.0 on 5.0 is now installable. Current state is: passing
fit.1.2.0 on 5.1 is now installable. Current state is: passing
flow_parser.0.159.0 on 4.11 had its build status changed: partially failing to passing
flow_parser.0.159.0 on 4.12 had its build status changed: partially failing to passing
fm-simplex-plugin.1.30 on 4.10 had its build status changed: partially failing to passing
fm-simplex-plugin.1.30 on 4.11 had its build status changed: partially failing to passing
fmlib.0.5.7 on 4.08 is now installable. Current state is: passing
fmlib.0.5.7 on 4.09 is now installable. Current state is: passing
fmlib.0.5.7 on 4.10 is now installable. Current state is: passing
fmlib.0.5.7 on 4.11 is now installable. Current state is: passing
fmlib.0.5.7 on 4.12 is now installable. Current state is: passing
fmlib.0.5.7 on 4.13 is now installable. Current state is: passing
fmlib.0.5.7 on 4.14 is now installable. Current state is: passing
fmlib.0.5.7 on 5.0 is now installable. Current state is: passing
fmlib.0.5.7 on 5.1 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 4.08 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 4.09 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 4.10 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 4.11 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 4.12 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 4.13 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 4.14 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 5.0 is now installable. Current state is: passing
fmlib_browser.0.5.7 on 5.1 is now installable. Current state is: passing
fmlib_js.0.5.7 on 4.08 is now installable. Current state is: passing
fmlib_js.0.5.7 on 4.09 is now installable. Current state is: passing
fmlib_js.0.5.7 on 4.10 is now installable. Current state is: passing
fmlib_js.0.5.7 on 4.11 is now installable. Current state is: passing
fmlib_js.0.5.7 on 4.12 is now installable. Current state is: passing
fmlib_js.0.5.7 on 4.13 is now installable. Current state is: passing
fmlib_js.0.5.7 on 4.14 is now installable. Current state is: passing
fmlib_js.0.5.7 on 5.0 is now installable. Current state is: passing
fmlib_js.0.5.7 on 5.1 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 4.08 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 4.09 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 4.10 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 4.11 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 4.12 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 4.13 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 4.14 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 5.0 is now installable. Current state is: passing
fmlib_parse.0.5.7 on 5.1 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 4.08 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 4.09 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 4.10 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 4.11 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 4.12 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 4.13 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 4.14 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 5.0 is now installable. Current state is: passing
fmlib_pretty.0.5.7 on 5.1 is now installable. Current state is: passing
fmlib_std.0.5.7 on 4.08 is now installable. Current state is: passing
fmlib_std.0.5.7 on 4.09 is now installable. Current state is: passing
fmlib_std.0.5.7 on 4.10 is now installable. Current state is: passing
fmlib_std.0.5.7 on 4.11 is now installable. Current state is: passing
fmlib_std.0.5.7 on 4.12 is now installable. Current state is: passing
fmlib_std.0.5.7 on 4.13 is now installable. Current state is: passing
fmlib_std.0.5.7 on 4.14 is now installable. Current state is: passing
fmlib_std.0.5.7 on 5.0 is now installable. Current state is: passing
fmlib_std.0.5.7 on 5.1 is now installable. Current state is: passing
forester.3.0.0 on 5.1 is now installable. Current state is: passing
format.0.1 on 4.08 had its build status changed: partially failing to passing
format.0.1 on 4.09 had its build status changed: partially failing to passing
format.0.1 on 4.10 had its build status changed: partially failing to passing
format.0.1 on 4.11 had its build status changed: partially failing to passing
format.0.1 on 4.12 had its build status changed: partially failing to passing
format.0.1 on 4.13 had its build status changed: partially failing to passing
format.0.1 on 4.14 had its build status changed: partially failing to passing
frama-c-metacsl.0.5 on 4.11 is now installable. Current state is: passing
frama-c-metacsl.0.5 on 4.12 is now installable. Current state is: passing
frama-c-metacsl.0.5 on 4.13 is now installable. Current state is: passing
frama-c-metacsl.0.5 on 4.14 is now installable. Current state is: passing
frama-c-metacsl.0.5 on 5.0 is now installable. Current state is: passing
frama-c-metacsl.0.5 on 5.1 is now installable. Current state is: passing
frama-c.28.0 on 4.13 is now installable. Current state is: passing
frama-c.28.0 on 4.14 is now installable. Current state is: passing
frama-c.28.0 on 5.0 is now installable. Current state is: passing
frama-c.28.0 on 5.1 is now installable. Current state is: passing
frenetic.5.0.5 on 4.11 had its build status changed: failing to passing
frenetic.5.0.5 on 4.12 had its build status changed: failing to passing
frenetic.5.0.5 on 4.13 had its build status changed: failing to passing
frenetic.5.0.5 on 4.14 had its build status changed: failing to passing
functoria-runtime.4.4.1 on 4.08 is now installable. Current state is: passing
functoria-runtime.4.4.1 on 4.09 is now installable. Current state is: passing
functoria-runtime.4.4.1 on 4.10 is now installable. Current state is: passing
functoria-runtime.4.4.1 on 4.11 is now installable. Current state is: passing
functoria-runtime.4.4.1 on 4.12 is now installable. Current state is: passing
functoria-runtime.4.4.1 on 4.13 is now installable. Current state is: passing
functoria-runtime.4.4.1 on 4.14 is now installable. Current state is: passing
functoria-runtime.4.4.1 on 5.0 is now installable. Current state is: passing
functoria-runtime.4.4.1 on 5.1 is now installable. Current state is: passing
functoria.4.4.1 on 4.08 is now installable. Current state is: passing
functoria.4.4.1 on 4.09 is now installable. Current state is: passing
functoria.4.4.1 on 4.10 is now installable. Current state is: passing
functoria.4.4.1 on 4.11 is now installable. Current state is: passing
functoria.4.4.1 on 4.12 is now installable. Current state is: passing
functoria.4.4.1 on 4.13 is now installable. Current state is: passing
functoria.4.4.1 on 4.14 is now installable. Current state is: passing
functoria.4.4.1 on 5.0 is now installable. Current state is: passing
functoria.4.4.1 on 5.1 is now installable. Current state is: passing
functory.0.6 on 4.10 had its build status changed: failing to passing
gapi-ocaml.0.3.10 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.10 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.10 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.10 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.10 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.10 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.10 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.11 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.11 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.11 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.11 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.11 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.11 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.11 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.12 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.12 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.12 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.12 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.12 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.12 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.12 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.13 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.13 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.13 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.13 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.13 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.13 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.13 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.14 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.14 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.14 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.14 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.14 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.14 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.14 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.15 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.15 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.15 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.15 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.15 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.15 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.15 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.16 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.16 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.16 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.16 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.16 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.16 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.16 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.17 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.17 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.17 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.17 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.17 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.17 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.17 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.18 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.18 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.18 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.18 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.18 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.18 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.18 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.19 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.19 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.19 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.19 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.19 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.19 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.19 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.5 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.5 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.5 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.5 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.5 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.5 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.5 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.6 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.6 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.6 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.6 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.6 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.6 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.6 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.7 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.7 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.7 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.7 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.7 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.7 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.7 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.8 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.8 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.8 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.8 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.8 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.8 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.8 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.3.9 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.3.9 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.3.9 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.3.9 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.3.9 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.3.9 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.3.9 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.4.1 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.4.1 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.4.1 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.4.1 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.4.1 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.4.1 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.4.1 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.4.2 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.4.2 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.4.2 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.4.2 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.4.2 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.4.2 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.4.2 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.4.3 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.4.3 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.4.3 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.4.3 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.4.3 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.4.3 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.4.3 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.4.4 on 4.08 had its build status changed: partially failing to passing
gapi-ocaml.0.4.4 on 4.09 had its build status changed: partially failing to passing
gapi-ocaml.0.4.4 on 4.10 had its build status changed: partially failing to passing
gapi-ocaml.0.4.4 on 4.11 had its build status changed: partially failing to passing
gapi-ocaml.0.4.4 on 4.12 had its build status changed: partially failing to passing
gapi-ocaml.0.4.4 on 4.13 had its build status changed: partially failing to passing
gapi-ocaml.0.4.4 on 4.14 had its build status changed: partially failing to passing
gapi-ocaml.0.4.5 on 4.08 is now installable. Current state is: passing
gapi-ocaml.0.4.5 on 4.09 is now installable. Current state is: passing
gapi-ocaml.0.4.5 on 4.10 is now installable. Current state is: passing
gapi-ocaml.0.4.5 on 4.11 is now installable. Current state is: passing
gapi-ocaml.0.4.5 on 4.12 is now installable. Current state is: passing
gapi-ocaml.0.4.5 on 4.13 is now installable. Current state is: passing
gapi-ocaml.0.4.5 on 4.14 is now installable. Current state is: passing
gapi-ocaml.0.4.5 on 5.0 is now installable. Current state is: passing
gapi-ocaml.0.4.5 on 5.1 is now installable. Current state is: passing
geojson.0.2.0 on 4.08 is now installable. Current state is: passing
geojson.0.2.0 on 4.09 is now installable. Current state is: passing
geojson.0.2.0 on 4.10 is now installable. Current state is: passing
geojson.0.2.0 on 4.11 is now installable. Current state is: passing
geojson.0.2.0 on 4.12 is now installable. Current state is: passing
geojson.0.2.0 on 4.13 is now installable. Current state is: passing
geojson.0.2.0 on 4.14 is now installable. Current state is: passing
geojson.0.2.0 on 5.0 is now installable. Current state is: passing
geojson.0.2.0 on 5.1 is now installable. Current state is: passing
geojsone.0.2.0 on 4.08 is now installable. Current state is: passing
geojsone.0.2.0 on 4.09 is now installable. Current state is: passing
geojsone.0.2.0 on 4.10 is now installable. Current state is: passing
geojsone.0.2.0 on 4.11 is now installable. Current state is: passing
geojsone.0.2.0 on 4.12 is now installable. Current state is: passing
geojsone.0.2.0 on 4.13 is now installable. Current state is: passing
geojsone.0.2.0 on 4.14 is now installable. Current state is: passing
geojsone.0.2.0 on 5.0 is now installable. Current state is: passing
geojsone.0.2.0 on 5.1 is now installable. Current state is: passing
get_line.1.0.0 on 4.08 had its build status changed: partially failing to passing
get_line.1.0.0 on 4.09 had its build status changed: partially failing to passing
get_line.1.0.0 on 4.10 had its build status changed: partially failing to passing
get_line.1.0.0 on 4.11 had its build status changed: partially failing to passing
get_line.1.0.0 on 4.12 had its build status changed: partially failing to passing
get_line.1.0.0 on 4.13 had its build status changed: partially failing to passing
get_line.1.0.0 on 4.14 had its build status changed: partially failing to passing
get_line.1.0.0 on 5.0 had its build status changed: partially failing to passing
get_line.2.1.1 on 4.08 had its build status changed: partially failing to passing
get_line.2.1.1 on 4.09 had its build status changed: partially failing to passing
get_line.2.1.1 on 4.10 had its build status changed: partially failing to passing
get_line.2.1.1 on 4.11 had its build status changed: partially failing to passing
get_line.2.1.1 on 4.12 had its build status changed: partially failing to passing
get_line.2.1.1 on 4.13 had its build status changed: partially failing to passing
get_line.2.1.1 on 4.14 had its build status changed: partially failing to passing
get_line.2.1.1 on 5.0 had its build status changed: partially failing to passing
get_line.3.0.0 on 4.08 had its build status changed: partially failing to passing
get_line.3.0.0 on 4.09 had its build status changed: partially failing to passing
get_line.3.0.0 on 4.10 had its build status changed: partially failing to passing
get_line.3.0.0 on 4.11 had its build status changed: partially failing to passing
get_line.3.0.0 on 4.12 had its build status changed: partially failing to passing
get_line.3.0.0 on 4.13 had its build status changed: partially failing to passing
get_line.3.0.0 on 4.14 had its build status changed: partially failing to passing
get_line.3.0.0 on 5.0 had its build status changed: partially failing to passing
gettext.0.3.8 on 4.08 had its build status changed: partially failing to passing
gettext.0.3.8 on 4.09 had its build status changed: partially failing to passing
gettext.0.3.8 on 4.10 had its build status changed: partially failing to passing
gettext.0.3.8 on 4.11 had its build status changed: partially failing to passing
gettext.0.3.8 on 4.12 had its build status changed: partially failing to passing
gettext.0.3.8 on 4.13 had its build status changed: partially failing to passing
gettext.0.3.8 on 4.14 had its build status changed: partially failing to passing
git-mirage.2.0.0 on 4.08 had its build status changed: partially failing to passing
git-mirage.2.0.0 on 4.09 had its build status changed: partially failing to passing
git-mirage.2.0.0 on 4.10 had its build status changed: partially failing to passing
git-mirage.2.0.0 on 4.11 had its build status changed: partially failing to passing
git-mirage.2.1.0 on 4.08 had its build status changed: partially failing to passing
git-mirage.2.1.0 on 4.09 had its build status changed: partially failing to passing
git-mirage.2.1.0 on 4.10 had its build status changed: partially failing to passing
git-mirage.2.1.0 on 4.11 had its build status changed: partially failing to passing
git-mirage.2.1.1 on 4.08 had its build status changed: partially failing to passing
git-mirage.2.1.1 on 4.09 had its build status changed: partially failing to passing
git-mirage.2.1.1 on 4.10 had its build status changed: partially failing to passing
git-mirage.2.1.1 on 4.11 had its build status changed: partially failing to passing
goblint-cil.2.0.3 on 4.08 is now installable. Current state is: passing
goblint-cil.2.0.3 on 4.09 is now installable. Current state is: passing
goblint-cil.2.0.3 on 4.10 is now installable. Current state is: passing
goblint-cil.2.0.3 on 4.11 is now installable. Current state is: passing
goblint-cil.2.0.3 on 4.12 is now installable. Current state is: passing
goblint-cil.2.0.3 on 4.13 is now installable. Current state is: passing
goblint-cil.2.0.3 on 4.14 is now installable. Current state is: passing
goblint-cil.2.0.3 on 5.0 is now installable. Current state is: passing
goblint-cil.2.0.3 on 5.1 is now installable. Current state is: passing
goblint.2.3.0 on 4.10 is now installable. Current state is: passing
goblint.2.3.0 on 4.11 is now installable. Current state is: passing
goblint.2.3.0 on 4.12 is now installable. Current state is: passing
goblint.2.3.0 on 4.13 is now installable. Current state is: passing
goblint.2.3.0 on 4.14 is now installable. Current state is: passing
goblint.2.3.0 on 5.0 is now installable. Current state is: passing
goblint.2.3.0 on 5.1 is now installable. Current state is: passing
google-drive-ocamlfuse.0.6.22 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.22 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.22 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.22 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.22 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.22 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.22 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.23 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.23 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.23 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.23 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.23 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.23 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.23 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.26 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.26 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.26 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.26 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.26 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.26 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.6.26 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.1 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.1 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.1 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.1 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.1 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.1 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.1 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.11 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.11 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.11 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.11 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.11 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.11 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.11 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.13 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.13 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.13 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.13 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.13 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.13 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.13 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.14 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.14 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.14 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.14 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.14 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.14 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.14 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.15 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.15 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.15 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.15 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.15 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.15 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.15 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.16 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.16 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.16 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.16 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.16 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.16 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.16 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.17 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.17 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.17 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.17 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.17 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.17 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.17 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.18 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.18 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.18 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.18 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.18 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.18 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.18 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.19 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.19 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.19 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.19 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.19 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.19 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.19 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.2 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.2 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.2 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.2 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.2 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.2 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.2 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.20 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.20 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.20 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.20 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.20 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.20 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.20 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.21 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.21 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.21 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.21 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.21 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.21 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.21 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.22 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.22 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.22 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.22 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.22 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.22 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.22 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.23 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.23 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.23 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.23 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.23 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.23 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.23 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.24 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.24 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.24 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.24 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.24 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.24 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.24 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.25 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.25 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.25 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.25 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.25 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.25 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.25 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.26 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.26 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.26 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.26 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.26 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.26 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.26 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.27 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.27 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.27 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.27 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.27 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.27 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.27 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.28 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.28 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.28 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.28 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.28 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.28 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.28 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.29 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.29 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.29 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.29 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.29 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.29 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.29 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.3 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.3 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.3 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.3 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.3 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.3 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.3 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.30 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.30 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.30 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.30 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.30 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.30 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.30 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.31 on 4.08 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.31 on 4.09 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.31 on 4.10 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.31 on 4.11 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.31 on 4.12 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.31 on 4.13 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.31 on 4.14 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.31 on 5.0 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.31 on 5.1 is now installable. Current state is: passing
google-drive-ocamlfuse.0.7.4 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.4 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.4 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.4 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.4 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.4 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.4 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.5 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.5 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.5 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.5 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.5 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.5 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.5 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.6 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.6 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.6 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.6 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.6 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.6 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.6 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.7 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.7 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.7 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.7 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.7 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.7 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.7 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.8 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.8 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.8 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.8 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.8 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.8 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.8 on 4.14 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.9 on 4.08 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.9 on 4.09 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.9 on 4.10 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.9 on 4.11 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.9 on 4.12 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.9 on 4.13 had its build status changed: partially failing to passing
google-drive-ocamlfuse.0.7.9 on 4.14 had its build status changed: partially failing to passing
gpx.1.0 on 4.08 had its build status changed: failing to passing
gpx.1.0 on 4.09 had its build status changed: failing to passing
gpx.1.0 on 4.10 had its build status changed: failing to passing
gpx.1.0 on 4.11 had its build status changed: failing to passing
gpx.1.0 on 4.12 had its build status changed: failing to passing
gpx.1.0 on 4.13 had its build status changed: failing to passing
gpx.1.0 on 4.14 had its build status changed: failing to passing
gpx.1.0 on 5.0 had its build status changed: failing to passing
gpx.1.0 on 5.1 had its build status changed: failing to passing
gpx.1.0.1 on 4.08 had its build status changed: failing to passing
gpx.1.0.1 on 4.09 had its build status changed: failing to passing
gpx.1.0.1 on 4.10 had its build status changed: failing to passing
gpx.1.0.1 on 4.11 had its build status changed: failing to passing
gpx.1.0.1 on 4.12 had its build status changed: failing to passing
gpx.1.0.1 on 4.13 had its build status changed: failing to passing
gpx.1.0.1 on 4.14 had its build status changed: failing to passing
gpx.1.0.1 on 5.0 had its build status changed: failing to passing
gpx.1.0.1 on 5.1 had its build status changed: failing to passing
gpx.1.0.2 on 4.08 had its build status changed: failing to passing
gpx.1.0.2 on 4.09 had its build status changed: failing to passing
gpx.1.0.2 on 4.10 had its build status changed: failing to passing
gpx.1.0.2 on 4.11 had its build status changed: failing to passing
gpx.1.0.2 on 4.12 had its build status changed: failing to passing
gpx.1.0.2 on 4.13 had its build status changed: failing to passing
gpx.1.0.2 on 4.14 had its build status changed: failing to passing
gpx.1.0.2 on 5.0 had its build status changed: failing to passing
gpx.1.0.2 on 5.1 had its build status changed: failing to passing
gpx.1.1.0 on 4.08 had its build status changed: failing to passing
gpx.1.1.0 on 4.09 had its build status changed: failing to passing
gpx.1.1.0 on 4.10 had its build status changed: failing to passing
gpx.1.1.0 on 4.11 had its build status changed: failing to passing
gpx.1.1.0 on 4.12 had its build status changed: failing to passing
gpx.1.1.0 on 4.13 had its build status changed: failing to passing
gpx.1.1.0 on 4.14 had its build status changed: failing to passing
gpx.1.1.0 on 5.0 had its build status changed: failing to passing
gpx.1.1.0 on 5.1 had its build status changed: failing to passing
gpx.1.1.1 on 4.08 had its build status changed: failing to passing
gpx.1.1.1 on 4.09 had its build status changed: failing to passing
gpx.1.1.1 on 4.10 had its build status changed: failing to passing
gpx.1.1.1 on 4.11 had its build status changed: failing to passing
gpx.1.1.1 on 4.12 had its build status changed: failing to passing
gpx.1.1.1 on 4.13 had its build status changed: failing to passing
gpx.1.1.1 on 4.14 had its build status changed: failing to passing
gpx.1.1.1 on 5.0 had its build status changed: failing to passing
gpx.1.1.1 on 5.1 had its build status changed: failing to passing
grid.0.1.0 on 4.08 is now installable. Current state is: passing
grid.0.1.0 on 4.09 is now installable. Current state is: passing
grid.0.1.0 on 4.10 is now installable. Current state is: passing
grid.0.1.0 on 4.11 is now installable. Current state is: passing
grid.0.1.0 on 4.12 is now installable. Current state is: passing
grid.0.1.0 on 4.13 is now installable. Current state is: passing
grid.0.1.0 on 4.14 is now installable. Current state is: passing
grid.0.1.0 on 5.0 is now installable. Current state is: passing
grid.0.1.0 on 5.1 is now installable. Current state is: passing
gsl.1.25.0 on 4.12 is now installable. Current state is: passing
gsl.1.25.0 on 4.13 is now installable. Current state is: passing
gsl.1.25.0 on 4.14 is now installable. Current state is: passing
gsl.1.25.0 on 5.0 is now installable. Current state is: passing
gsl.1.25.0 on 5.1 is now installable. Current state is: passing
h2-mirage.0.1.0 on 4.08 had its build status changed: partially failing to passing
h2-mirage.0.1.0 on 4.09 had its build status changed: partially failing to passing
h2-mirage.0.1.0 on 4.10 had its build status changed: partially failing to passing
h2-mirage.0.1.0 on 4.11 had its build status changed: partially failing to passing
h2-mirage.0.2.0 on 4.08 had its build status changed: partially failing to passing
h2-mirage.0.2.0 on 4.09 had its build status changed: partially failing to passing
h2-mirage.0.2.0 on 4.10 had its build status changed: partially failing to passing
h2-mirage.0.2.0 on 4.11 had its build status changed: partially failing to passing
h2-mirage.0.3.0 on 4.08 had its build status changed: partially failing to passing
h2-mirage.0.3.0 on 4.09 had its build status changed: partially failing to passing
h2-mirage.0.3.0 on 4.10 had its build status changed: partially failing to passing
h2-mirage.0.3.0 on 4.11 had its build status changed: partially failing to passing
hacl-star-raw.0.1 on 4.10 had its build status changed: failing to passing
hacl-star-raw.0.2.1 on 4.12 had its build status changed: failing to passing
hacl-star.0.2.0 on 4.08 had its build status changed: partially failing to passing
hacl-star.0.2.1 on 4.11 had its build status changed: partially failing to passing
hacl-star.0.2.1 on 4.14 had its build status changed: partially failing to passing
hashset.1.0.0 on 4.08 had its build status changed: partially failing to passing
hashset.1.0.0 on 4.09 had its build status changed: partially failing to passing
hashset.1.0.0 on 4.10 had its build status changed: partially failing to passing
hashset.1.0.0 on 4.11 had its build status changed: partially failing to passing
hashset.1.0.0 on 4.12 had its build status changed: partially failing to passing
hashset.1.0.0 on 4.13 had its build status changed: partially failing to passing
hashset.1.0.0 on 4.14 had its build status changed: partially failing to passing
haxe.3.4.7 on 4.08 had its build status changed: partially failing to passing
haxe.3.4.7 on 4.09 had its build status changed: partially failing to passing
heptagon.1.03.03 on 4.08 had its build status changed: partially failing to passing
heptagon.1.03.03 on 4.09 had its build status changed: partially failing to passing
heptagon.1.03.03 on 4.10 had its build status changed: partially failing to passing
heptagon.1.03.03 on 4.11 had its build status changed: partially failing to passing
heptagon.1.03.03 on 4.12 had its build status changed: partially failing to passing
heptagon.1.03.03 on 4.13 had its build status changed: partially failing to passing
heptagon.1.03.03 on 4.14 had its build status changed: partially failing to passing
heptagon.1.03.04 on 4.08 had its build status changed: partially failing to passing
heptagon.1.03.04 on 4.09 had its build status changed: partially failing to passing
heptagon.1.03.04 on 4.10 had its build status changed: partially failing to passing
heptagon.1.03.04 on 4.11 had its build status changed: partially failing to passing
heptagon.1.03.04 on 4.12 had its build status changed: partially failing to passing
heptagon.1.03.04 on 4.13 had its build status changed: partially failing to passing
heptagon.1.03.04 on 4.14 had its build status changed: partially failing to passing
heptagon.1.04.00 on 4.08 had its build status changed: partially failing to passing
heptagon.1.04.00 on 4.09 had its build status changed: partially failing to passing
heptagon.1.04.00 on 4.10 had its build status changed: partially failing to passing
heptagon.1.04.00 on 4.11 had its build status changed: partially failing to passing
heptagon.1.04.00 on 4.12 had its build status changed: partially failing to passing
heptagon.1.04.00 on 4.13 had its build status changed: partially failing to passing
heptagon.1.04.00 on 4.14 had its build status changed: partially failing to passing
heptagon.1.05.00 on 4.08 had its build status changed: partially failing to passing
heptagon.1.05.00 on 4.09 had its build status changed: partially failing to passing
heptagon.1.05.00 on 4.10 had its build status changed: partially failing to passing
heptagon.1.05.00 on 4.11 had its build status changed: partially failing to passing
heptagon.1.05.00 on 4.12 had its build status changed: partially failing to passing
heptagon.1.05.00 on 4.13 had its build status changed: partially failing to passing
heptagon.1.05.00 on 4.14 had its build status changed: partially failing to passing
hidapi-lwt.1.2 on 4.08 is now installable. Current state is: passing
hidapi-lwt.1.2 on 4.09 is now installable. Current state is: passing
hidapi-lwt.1.2 on 4.10 is now installable. Current state is: passing
hidapi-lwt.1.2 on 4.11 is now installable. Current state is: passing
hidapi-lwt.1.2 on 4.12 is now installable. Current state is: passing
hidapi-lwt.1.2 on 4.13 is now installable. Current state is: passing
hidapi-lwt.1.2 on 4.14 is now installable. Current state is: passing
hidapi-lwt.1.2 on 5.0 is now installable. Current state is: passing
hidapi-lwt.1.2 on 5.1 is now installable. Current state is: passing
hidapi.1.2 on 4.08 is now installable. Current state is: passing
hidapi.1.2 on 4.09 is now installable. Current state is: passing
hidapi.1.2 on 4.10 is now installable. Current state is: passing
hidapi.1.2 on 4.11 is now installable. Current state is: passing
hidapi.1.2 on 4.12 is now installable. Current state is: passing
hidapi.1.2 on 4.13 is now installable. Current state is: passing
hidapi.1.2 on 4.14 is now installable. Current state is: passing
hidapi.1.2 on 5.0 is now installable. Current state is: passing
hidapi.1.2 on 5.1 is now installable. Current state is: passing
highlexer.0.1 on 4.10 is now installable. Current state is: passing
highlexer.0.1 on 4.11 is now installable. Current state is: passing
highlexer.0.1 on 4.12 is now installable. Current state is: passing
highlexer.0.1 on 4.13 is now installable. Current state is: passing
highlexer.0.1 on 4.14 is now installable. Current state is: passing
highlexer.0.1 on 5.0 is now installable. Current state is: passing
highlexer.0.1 on 5.1 is now installable. Current state is: passing
higlo.0.1 on 4.08 had its build status changed: partially failing to passing
higlo.0.1 on 4.09 had its build status changed: partially failing to passing
higlo.0.1 on 4.10 had its build status changed: partially failing to passing
higlo.0.1 on 4.11 had its build status changed: partially failing to passing
higlo.0.1 on 4.12 had its build status changed: partially failing to passing
higlo.0.1 on 4.13 had its build status changed: partially failing to passing
higlo.0.1 on 4.14 had its build status changed: partially failing to passing
higlo.0.2 on 4.08 had its build status changed: partially failing to passing
higlo.0.2 on 4.09 had its build status changed: partially failing to passing
higlo.0.2 on 4.10 had its build status changed: partially failing to passing
higlo.0.2 on 4.11 had its build status changed: partially failing to passing
higlo.0.2 on 4.12 had its build status changed: partially failing to passing
higlo.0.2 on 4.13 had its build status changed: partially failing to passing
higlo.0.2 on 4.14 had its build status changed: partially failing to passing
higlo.0.4 on 4.08 had its build status changed: partially failing to passing
higlo.0.4 on 4.09 had its build status changed: partially failing to passing
higlo.0.4 on 4.10 had its build status changed: partially failing to passing
higlo.0.4 on 4.11 had its build status changed: partially failing to passing
higlo.0.4 on 4.12 had its build status changed: partially failing to passing
higlo.0.4 on 4.13 had its build status changed: partially failing to passing
higlo.0.4 on 4.14 had its build status changed: partially failing to passing
higlo.0.5 on 4.12 had its build status changed: partially failing to passing
higlo.0.5 on 4.13 had its build status changed: partially failing to passing
higlo.0.5 on 4.14 had its build status changed: partially failing to passing
higlo.0.6 on 4.12 had its build status changed: partially failing to passing
higlo.0.6 on 4.13 had its build status changed: partially failing to passing
higlo.0.6 on 4.14 had its build status changed: partially failing to passing
hilite.0.4.0 on 4.14 is now installable. Current state is: passing
hilite.0.4.0 on 5.0 is now installable. Current state is: passing
hilite.0.4.0 on 5.1 is now installable. Current state is: passing
hol2dk.0.0.0 on 4.13 is now installable. Current state is: passing
hol2dk.0.0.0 on 4.14 is now installable. Current state is: passing
hol2dk.0.0.0 on 5.0 is now installable. Current state is: passing
hol2dk.0.0.0 on 5.1 is now installable. Current state is: passing
hol2dk.0.0.1 on 4.13 is now installable. Current state is: passing
hol2dk.0.0.1 on 4.14 is now installable. Current state is: passing
hol2dk.0.0.1 on 5.0 is now installable. Current state is: passing
hol2dk.0.0.1 on 5.1 is now installable. Current state is: passing
hooke.0.0.1 on 5.1 is now installable. Current state is: passing
hsluv.0.1.0 on 4.08 is now installable. Current state is: passing
hsluv.0.1.0 on 4.09 is now installable. Current state is: passing
hsluv.0.1.0 on 4.10 is now installable. Current state is: passing
hsluv.0.1.0 on 4.11 is now installable. Current state is: passing
hsluv.0.1.0 on 4.12 is now installable. Current state is: passing
hsluv.0.1.0 on 4.13 is now installable. Current state is: passing
hsluv.0.1.0 on 4.14 is now installable. Current state is: passing
hsluv.0.1.0 on 5.0 is now installable. Current state is: passing
hsluv.0.1.0 on 5.1 is now installable. Current state is: passing
hts_shrink.1.0.0 on 4.08 had its build status changed: partially failing to passing
hts_shrink.1.0.0 on 4.09 had its build status changed: partially failing to passing
hts_shrink.1.0.0 on 4.10 had its build status changed: partially failing to passing
hts_shrink.1.0.0 on 4.11 had its build status changed: partially failing to passing
hts_shrink.2.1.0 on 4.08 had its build status changed: partially failing to passing
hts_shrink.2.1.0 on 4.09 had its build status changed: partially failing to passing
hts_shrink.2.1.0 on 4.10 had its build status changed: partially failing to passing
hts_shrink.2.1.0 on 4.11 had its build status changed: partially failing to passing
hts_shrink.2.1.0 on 4.12 had its build status changed: partially failing to passing
hts_shrink.2.1.0 on 4.13 had its build status changed: partially failing to passing
hts_shrink.2.1.0 on 4.14 had its build status changed: partially failing to passing
hts_shrink.3.0.1 on 4.08 is now installable. Current state is: passing
hts_shrink.3.0.1 on 4.09 is now installable. Current state is: passing
hts_shrink.3.0.1 on 4.10 is now installable. Current state is: passing
hts_shrink.3.0.1 on 4.11 is now installable. Current state is: passing
hts_shrink.3.0.1 on 4.12 is now installable. Current state is: passing
hts_shrink.3.0.1 on 4.13 is now installable. Current state is: passing
hts_shrink.3.0.1 on 4.14 is now installable. Current state is: passing
hts_shrink.3.0.1 on 5.0 is now installable. Current state is: passing
hts_shrink.3.0.1 on 5.1 is now installable. Current state is: passing
httpaf.0.2.0 on 4.11 had its build status changed: partially failing to passing
httpaf.0.5.0 on 4.14 had its build status changed: internal failure to passing
httpaf.0.6.5 on 5.1 had its build status changed: internal failure to passing
httpaf.0.7.1 on 4.08 had its build status changed: internal failure to passing
httpaf_caged.1.0.1 on 4.10 had its build status changed: internal failure to passing
inotify.2.5 on 4.08 is now installable. Current state is: passing
inotify.2.5 on 4.09 is now installable. Current state is: passing
inotify.2.5 on 4.10 is now installable. Current state is: passing
inotify.2.5 on 4.11 is now installable. Current state is: passing
inotify.2.5 on 4.12 is now installable. Current state is: passing
inotify.2.5 on 4.13 is now installable. Current state is: passing
inotify.2.5 on 4.14 is now installable. Current state is: passing
inotify.2.5 on 5.0 is now installable. Current state is: passing
inotify.2.5 on 5.1 is now installable. Current state is: passing
integration1d.0.5 on 4.08 had its build status changed: partially failing to passing
integration1d.0.5 on 4.09 had its build status changed: partially failing to passing
integration1d.0.5 on 4.10 had its build status changed: partially failing to passing
integration1d.0.5 on 4.11 had its build status changed: partially failing to passing
integration1d.0.5 on 4.12 had its build status changed: partially failing to passing
integration1d.0.5 on 4.13 had its build status changed: partially failing to passing
integration1d.0.5 on 4.14 had its build status changed: partially failing to passing
io.0.2.0 on 4.08 had its build status changed: partially failing to passing
io.0.2.0 on 4.09 had its build status changed: partially failing to passing
io.0.2.0 on 4.10 had its build status changed: partially failing to passing
io.0.2.0 on 4.11 had its build status changed: partially failing to passing
io.0.2.0 on 4.12 had its build status changed: partially failing to passing
io.0.2.0 on 4.13 had its build status changed: partially failing to passing
io.0.2.0 on 4.14 had its build status changed: partially failing to passing
irc-client-tls.0.6.0 on 4.08 had its build status changed: partially failing to passing
irc-client-tls.0.6.0 on 4.09 had its build status changed: partially failing to passing
irc-client-tls.0.6.0 on 4.10 had its build status changed: partially failing to passing
irc-client-tls.0.6.0 on 4.11 had its build status changed: partially failing to passing
irc-client-tls.0.6.1 on 4.08 had its build status changed: partially failing to passing
irc-client-tls.0.6.1 on 4.09 had its build status changed: partially failing to passing
irc-client-tls.0.6.1 on 4.10 had its build status changed: partially failing to passing
irc-client-tls.0.6.1 on 4.11 had its build status changed: partially failing to passing
irc-client-tls.0.6.2 on 4.08 had its build status changed: partially failing to passing
irc-client-tls.0.6.2 on 4.09 had its build status changed: partially failing to passing
irc-client-tls.0.6.2 on 4.10 had its build status changed: partially failing to passing
irc-client-tls.0.6.2 on 4.11 had its build status changed: partially failing to passing
iter.1.8 on 4.08 is now installable. Current state is: passing
iter.1.8 on 4.09 is now installable. Current state is: passing
iter.1.8 on 4.10 is now installable. Current state is: passing
iter.1.8 on 4.11 is now installable. Current state is: passing
iter.1.8 on 4.12 is now installable. Current state is: passing
iter.1.8 on 4.13 is now installable. Current state is: passing
iter.1.8 on 4.14 is now installable. Current state is: passing
iter.1.8 on 5.0 is now installable. Current state is: passing
iter.1.8 on 5.1 is now installable. Current state is: passing
jasmin.2023.06.2 on 4.11 is now installable. Current state is: passing
jasmin.2023.06.2 on 4.12 is now installable. Current state is: passing
jasmin.2023.06.2 on 4.13 is now installable. Current state is: passing
jasmin.2023.06.2 on 4.14 is now installable. Current state is: passing
jasmin.2023.06.2 on 5.0 is now installable. Current state is: passing
jasmin.2023.06.2 on 5.1 is now installable. Current state is: passing
javalib.2.3.6 on 4.08 had its build status changed: partially failing to passing
javalib.2.3.6 on 4.09 had its build status changed: partially failing to passing
javalib.2.3.6 on 4.10 had its build status changed: partially failing to passing
javalib.2.3.6 on 4.11 had its build status changed: partially failing to passing
javalib.2.3.6 on 4.12 had its build status changed: partially failing to passing
javalib.2.3.6 on 4.13 had its build status changed: partially failing to passing
javalib.2.3.6 on 4.14 had its build status changed: partially failing to passing
javalib.3.0 on 4.08 had its build status changed: partially failing to passing
javalib.3.0 on 4.09 had its build status changed: partially failing to passing
javalib.3.0 on 4.10 had its build status changed: partially failing to passing
javalib.3.0 on 4.11 had its build status changed: partially failing to passing
javalib.3.0 on 4.12 had its build status changed: partially failing to passing
javalib.3.0 on 4.13 had its build status changed: partially failing to passing
javalib.3.0 on 4.14 had its build status changed: partially failing to passing
javalib.3.1 on 4.08 had its build status changed: partially failing to passing
javalib.3.1 on 4.09 had its build status changed: partially failing to passing
javalib.3.1 on 4.10 had its build status changed: partially failing to passing
javalib.3.1 on 4.11 had its build status changed: partially failing to passing
javalib.3.1 on 4.12 had its build status changed: partially failing to passing
javalib.3.1 on 4.13 had its build status changed: partially failing to passing
javalib.3.1 on 4.14 had its build status changed: partially failing to passing
jekyll-format.0.3.3 on 4.08 is now installable. Current state is: passing
jekyll-format.0.3.3 on 4.09 is now installable. Current state is: passing
jekyll-format.0.3.3 on 4.10 is now installable. Current state is: passing
jekyll-format.0.3.3 on 4.11 is now installable. Current state is: passing
jekyll-format.0.3.3 on 4.12 is now installable. Current state is: passing
jekyll-format.0.3.3 on 4.13 is now installable. Current state is: passing
jekyll-format.0.3.3 on 4.14 is now installable. Current state is: passing
jekyll-format.0.3.3 on 5.0 is now installable. Current state is: passing
jekyll-format.0.3.3 on 5.1 is now installable. Current state is: passing
jhupllib.0.2.2 on 4.08 had its build status changed: internal failure to passing
jhupllib.0.2.2 on 4.09 had its build status changed: internal failure to passing
jhupllib.0.2.2 on 4.10 had its build status changed: internal failure to passing
jhupllib.0.2.2 on 4.11 had its build status changed: internal failure to passing
jhupllib.0.2.2 on 4.12 had its build status changed: internal failure to passing
jhupllib.0.2.2 on 4.14 had its build status changed: internal failure to passing
jingoo.1.5.0 on 4.08 is now installable. Current state is: passing
jingoo.1.5.0 on 4.09 is now installable. Current state is: passing
jingoo.1.5.0 on 4.10 is now installable. Current state is: passing
jingoo.1.5.0 on 4.11 is now installable. Current state is: passing
jingoo.1.5.0 on 4.12 is now installable. Current state is: passing
jingoo.1.5.0 on 4.13 is now installable. Current state is: passing
jingoo.1.5.0 on 4.14 is now installable. Current state is: passing
jingoo.1.5.0 on 5.0 is now installable. Current state is: passing
jingoo.1.5.0 on 5.1 is now installable. Current state is: passing
js_of_ocaml-camlp4.3.0 on 4.08 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0 on 4.09 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0 on 4.10 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0 on 4.11 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0 on 4.12 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0 on 4.13 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0 on 4.14 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.1 on 4.08 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.1 on 4.09 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.1 on 4.10 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.1 on 4.11 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.1 on 4.12 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.1 on 4.13 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.1 on 4.14 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.2 on 4.08 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.2 on 4.09 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.2 on 4.10 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.2 on 4.11 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.2 on 4.12 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.2 on 4.13 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.0.2 on 4.14 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.1.0 on 4.08 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.1.0 on 4.09 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.1.0 on 4.10 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.1.0 on 4.11 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.1.0 on 4.12 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.1.0 on 4.13 had its build status changed: partially failing to passing
js_of_ocaml-camlp4.3.1.0 on 4.14 had its build status changed: partially failing to passing
js_of_ocaml-compiler.5.5.2 on 4.08 is now installable. Current state is: passing
js_of_ocaml-compiler.5.5.2 on 4.09 is now installable. Current state is: passing
js_of_ocaml-compiler.5.5.2 on 4.10 is now installable. Current state is: passing
js_of_ocaml-compiler.5.5.2 on 4.11 is now installable. Current state is: passing
js_of_ocaml-compiler.5.5.2 on 4.12 is now installable. Current state is: passing
js_of_ocaml-compiler.5.5.2 on 4.13 is now installable. Current state is: passing
js_of_ocaml-compiler.5.5.2 on 4.14 is now installable. Current state is: passing
js_of_ocaml-compiler.5.5.2 on 5.0 is now installable. Current state is: passing
js_of_ocaml-compiler.5.5.2 on 5.1 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 4.08 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 4.09 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 4.10 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 4.11 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 4.12 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 4.13 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 4.14 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 5.0 is now installable. Current state is: passing
js_of_ocaml-lwt.5.5.2 on 5.1 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 4.08 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 4.09 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 4.10 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 4.11 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 4.12 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 4.13 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 4.14 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 5.0 is now installable. Current state is: passing
js_of_ocaml-ppx.5.5.2 on 5.1 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 4.08 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 4.09 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 4.10 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 4.11 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 4.12 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 4.13 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 4.14 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 5.0 is now installable. Current state is: passing
js_of_ocaml-ppx_deriving_json.5.5.2 on 5.1 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 4.08 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 4.09 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 4.10 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 4.11 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 4.12 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 4.13 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 4.14 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 5.0 is now installable. Current state is: passing
js_of_ocaml-toplevel.5.5.2 on 5.1 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 4.08 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 4.09 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 4.10 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 4.11 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 4.12 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 4.13 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 4.14 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 5.0 is now installable. Current state is: passing
js_of_ocaml-tyxml.5.5.2 on 5.1 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 4.08 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 4.09 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 4.10 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 4.11 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 4.12 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 4.13 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 4.14 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 5.0 is now installable. Current state is: passing
js_of_ocaml.5.5.2 on 5.1 is now installable. Current state is: passing
json-static.0.9.8 on 4.08 had its build status changed: partially failing to passing
json-static.0.9.8 on 4.09 had its build status changed: partially failing to passing
json-static.0.9.8 on 4.10 had its build status changed: partially failing to passing
json-static.0.9.8 on 4.11 had its build status changed: partially failing to passing
json-static.0.9.8 on 4.12 had its build status changed: partially failing to passing
json-static.0.9.8 on 4.13 had its build status changed: partially failing to passing
json-static.0.9.8 on 4.14 had its build status changed: partially failing to passing
json-wheel.1.0.6+safe-string on 4.08 had its build status changed: partially failing to passing
json-wheel.1.0.6+safe-string on 4.09 had its build status changed: partially failing to passing
json-wheel.1.0.6+safe-string on 4.10 had its build status changed: partially failing to passing
json-wheel.1.0.6+safe-string on 4.11 had its build status changed: partially failing to passing
json-wheel.1.0.6+safe-string on 4.12 had its build status changed: partially failing to passing
json-wheel.1.0.6+safe-string on 4.13 had its build status changed: partially failing to passing
json-wheel.1.0.6+safe-string on 4.14 had its build status changed: partially failing to passing
jsonrpc.1.17.0 on 4.08 is now installable. Current state is: passing
jsonrpc.1.17.0 on 4.09 is now installable. Current state is: passing
jsonrpc.1.17.0 on 4.10 is now installable. Current state is: passing
jsonrpc.1.17.0 on 4.11 is now installable. Current state is: passing
jsonrpc.1.17.0 on 4.12 is now installable. Current state is: passing
jsonrpc.1.17.0 on 4.13 is now installable. Current state is: passing
jsonrpc.1.17.0 on 4.14 is now installable. Current state is: passing
jsonrpc.1.17.0 on 5.0 is now installable. Current state is: passing
jsonrpc.1.17.0 on 5.1 is now installable. Current state is: passing
jupyter-archimedes.2.3.2 on 4.08 had its build status changed: partially failing to passing
jupyter-archimedes.2.3.2 on 4.09 had its build status changed: partially failing to passing
jupyter-archimedes.2.3.2 on 4.10 had its build status changed: partially failing to passing
jupyter-archimedes.2.3.2 on 4.11 had its build status changed: partially failing to passing
jupyter-archimedes.2.3.2 on 4.12 had its build status changed: partially failing to passing
jupyter-archimedes.2.3.2 on 4.13 had its build status changed: partially failing to passing
kind2.2.1.0 on 4.09 is now installable. Current state is: passing
kind2.2.1.0 on 4.10 is now installable. Current state is: passing
kind2.2.1.0 on 4.11 is now installable. Current state is: passing
kind2.2.1.0 on 4.12 is now installable. Current state is: passing
kind2.2.1.0 on 4.13 is now installable. Current state is: passing
kind2.2.1.0 on 4.14 is now installable. Current state is: passing
kind2.2.1.0 on 5.0 is now installable. Current state is: passing
kind2.2.1.0 on 5.1 is now installable. Current state is: passing
kind2.2.1.1 on 4.09 is now installable. Current state is: passing
kind2.2.1.1 on 4.10 is now installable. Current state is: passing
kind2.2.1.1 on 4.11 is now installable. Current state is: passing
kind2.2.1.1 on 4.12 is now installable. Current state is: passing
kind2.2.1.1 on 4.13 is now installable. Current state is: passing
kind2.2.1.1 on 4.14 is now installable. Current state is: passing
kind2.2.1.1 on 5.0 is now installable. Current state is: passing
kind2.2.1.1 on 5.1 is now installable. Current state is: passing
kkmarkdown.1.1.0 on 4.14 is now installable. Current state is: passing
kkmarkdown.1.1.0 on 5.0 is now installable. Current state is: passing
kkmarkdown.1.1.0 on 5.1 is now installable. Current state is: passing
lablgl.1.04.20120306 on 4.08 had its build status changed: partially failing to passing
lablgl.1.04.20120306 on 4.09 had its build status changed: partially failing to passing
lablgl.1.04.20120306 on 4.10 had its build status changed: partially failing to passing
lablgl.1.04.20120306 on 4.11 had its build status changed: partially failing to passing
lablgl.1.04.20120306 on 4.12 had its build status changed: partially failing to passing
lablgl.1.04.20120306 on 4.13 had its build status changed: partially failing to passing
lablgl.1.04.20120306 on 4.14 had its build status changed: partially failing to passing
lablgl.1.05 on 4.08 had its build status changed: partially failing to passing
lablgl.1.05 on 4.09 had its build status changed: partially failing to passing
lablgl.1.05 on 4.10 had its build status changed: partially failing to passing
lablgl.1.05 on 4.11 had its build status changed: partially failing to passing
lablgl.1.05 on 4.12 had its build status changed: partially failing to passing
lablgl.1.05 on 4.13 had its build status changed: partially failing to passing
lablgl.1.05 on 4.14 had its build status changed: partially failing to passing
lablgl.1.06 on 4.09 had its build status changed: failing to passing
lablgtk.2.18.13 on 5.0 had its build status changed: not available to passing
lablgtk.2.18.13 on 5.1 had its build status changed: not available to passing
lambda-runtime.0.1.0 on 4.08 had its build status changed: partially failing to passing
lambda-runtime.0.1.0 on 4.09 had its build status changed: partially failing to passing
lambda-runtime.0.1.0 on 4.10 had its build status changed: partially failing to passing
lambda-runtime.0.1.0 on 4.11 had its build status changed: partially failing to passing
lambda-runtime.0.1.0 on 4.12 had its build status changed: partially failing to passing
lambda-runtime.0.1.0 on 4.13 had its build status changed: partially failing to passing
lambda-runtime.0.1.0 on 4.14 had its build status changed: partially failing to passing
lambda.0.1.7 on 4.08 had its build status changed: failing to passing
lambda.0.1.7 on 4.09 had its build status changed: failing to passing
lambda.0.1.7 on 4.10 had its build status changed: failing to passing
lambda.0.1.7 on 4.11 had its build status changed: failing to passing
lambda.0.1.7 on 4.12 had its build status changed: failing to passing
lambda.0.1.7 on 4.13 had its build status changed: failing to passing
lambda.0.1.7 on 4.14 had its build status changed: failing to passing
lambda.0.1.7 on 5.0 had its build status changed: failing to passing
lambda.0.1.7 on 5.1 had its build status changed: failing to passing
lambdapi.2.0.0 on 4.12 had its build status changed: partially failing to passing
lambdapi.2.0.0 on 4.13 had its build status changed: partially failing to passing
lambdapi.2.4.1 on 4.08 is now installable. Current state is: passing
lambdapi.2.4.1 on 4.09 is now installable. Current state is: passing
lambdapi.2.4.1 on 4.10 is now installable. Current state is: passing
lambdapi.2.4.1 on 4.11 is now installable. Current state is: passing
lambdapi.2.4.1 on 4.12 is now installable. Current state is: passing
lambdapi.2.4.1 on 4.13 is now installable. Current state is: passing
lambdapi.2.4.1 on 4.14 is now installable. Current state is: passing
lambdapi.2.4.1 on 5.0 is now installable. Current state is: passing
lambdapi.2.4.1 on 5.1 is now installable. Current state is: passing
lascar.0.5 on 4.08 had its build status changed: partially failing to passing
lascar.0.5 on 4.09 had its build status changed: partially failing to passing
lascar.0.5 on 4.10 had its build status changed: partially failing to passing
lascar.0.5 on 4.11 had its build status changed: partially failing to passing
lascar.0.5 on 4.12 had its build status changed: partially failing to passing
lascar.0.5 on 4.13 had its build status changed: partially failing to passing
lascar.0.5 on 4.14 had its build status changed: partially failing to passing
lbfgs.0.9 on 4.08 had its build status changed: partially failing to passing
lbfgs.0.9 on 4.09 had its build status changed: partially failing to passing
lbfgs.0.9 on 4.10 had its build status changed: partially failing to passing
lbfgs.0.9 on 4.11 had its build status changed: partially failing to passing
lbfgs.0.9.1 on 4.08 had its build status changed: partially failing to passing
lbfgs.0.9.1 on 4.09 had its build status changed: partially failing to passing
lbfgs.0.9.1 on 4.10 had its build status changed: partially failing to passing
lbfgs.0.9.1 on 4.11 had its build status changed: partially failing to passing
lbfgs.0.9.1 on 4.12 had its build status changed: partially failing to passing
lbfgs.0.9.1 on 4.13 had its build status changed: partially failing to passing
lbfgs.0.9.1 on 4.14 had its build status changed: partially failing to passing
lbfgs.0.9.1 on 5.0 had its build status changed: partially failing to passing
lbfgs.0.9.2 on 4.08 had its build status changed: partially failing to passing
lbfgs.0.9.2 on 4.09 had its build status changed: partially failing to passing
lbfgs.0.9.2 on 4.10 had its build status changed: partially failing to passing
lbfgs.0.9.2 on 4.11 had its build status changed: partially failing to passing
lbfgs.0.9.2 on 4.12 had its build status changed: partially failing to passing
lbfgs.0.9.2 on 4.13 had its build status changed: partially failing to passing
lbfgs.0.9.2 on 4.14 had its build status changed: partially failing to passing
lbfgs.0.9.2 on 5.0 had its build status changed: partially failing to passing
ldap.2.4.0 on 4.08 had its build status changed: partially failing to passing
ldap.2.4.0 on 4.09 had its build status changed: partially failing to passing
ldap.2.4.0 on 4.10 had its build status changed: partially failing to passing
ldap.2.4.0 on 4.11 had its build status changed: partially failing to passing
ldap.2.4.0 on 4.12 had its build status changed: partially failing to passing
ldap.2.4.0 on 4.13 had its build status changed: partially failing to passing
ldap.2.4.0 on 4.14 had its build status changed: partially failing to passing
ldap.2.4.1 on 4.08 had its build status changed: partially failing to passing
ldap.2.4.1 on 4.09 had its build status changed: partially failing to passing
ldap.2.4.1 on 4.10 had its build status changed: partially failing to passing
ldap.2.4.1 on 4.11 had its build status changed: partially failing to passing
ldap.2.4.1 on 4.12 had its build status changed: partially failing to passing
ldap.2.4.1 on 4.13 had its build status changed: partially failing to passing
ldap.2.4.1 on 4.14 had its build status changed: partially failing to passing
ldap.2.4.2 on 4.08 had its build status changed: partially failing to passing
ldap.2.4.2 on 4.09 had its build status changed: partially failing to passing
ldap.2.4.2 on 4.10 had its build status changed: partially failing to passing
ldap.2.4.2 on 4.11 had its build status changed: partially failing to passing
ldap.2.4.2 on 4.12 had its build status changed: partially failing to passing
ldap.2.4.2 on 4.13 had its build status changed: partially failing to passing
ldap.2.4.2 on 4.14 had its build status changed: partially failing to passing
learn-ocaml-client.0.16.0 on 4.12 is now installable. Current state is: passing
learn-ocaml.0.16.0 on 4.12 is now installable. Current state is: passing
leaves.0.0.1 on 5.1 is now installable. Current state is: passing
leaves.0.0.2 on 5.1 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 4.08 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 4.09 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 4.10 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 4.11 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 4.12 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 4.13 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 4.14 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 5.0 is now installable. Current state is: passing
ledgerwallet-tezos.0.4.0 on 5.1 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 4.08 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 4.09 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 4.10 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 4.11 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 4.12 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 4.13 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 4.14 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 5.0 is now installable. Current state is: passing
ledgerwallet.0.4.0 on 5.1 is now installable. Current state is: passing
lem.2020-06-03 on 4.08 had its build status changed: failing to passing
lem.2020-06-03 on 4.09 had its build status changed: failing to passing
lem.2020-06-03 on 4.10 had its build status changed: failing to passing
lem.2020-06-03 on 4.11 had its build status changed: failing to passing
lem.2020-06-03 on 4.12 had its build status changed: failing to passing
lem.2020-06-03 on 4.13 had its build status changed: failing to passing
lem.2020-06-03 on 4.14 had its build status changed: failing to passing
lem.2022-12-10 on 4.08 had its build status changed: failing to passing
lem.2022-12-10 on 4.09 had its build status changed: failing to passing
lem.2022-12-10 on 4.10 had its build status changed: failing to passing
lem.2022-12-10 on 4.11 had its build status changed: failing to passing
lem.2022-12-10 on 4.12 had its build status changed: failing to passing
lem.2022-12-10 on 4.13 had its build status changed: failing to passing
lem.2022-12-10 on 4.14 had its build status changed: failing to passing
lem.2022-12-10 on 5.0 had its build status changed: failing to passing
lem.2022-12-10 on 5.1 had its build status changed: failing to passing
letters.0.1.0 on 4.08 had its build status changed: partially failing to passing
letters.0.1.0 on 4.09 had its build status changed: partially failing to passing
letters.0.1.0 on 4.10 had its build status changed: partially failing to passing
letters.0.1.0 on 4.11 had its build status changed: partially failing to passing
letters.0.1.0 on 4.12 had its build status changed: partially failing to passing
letters.0.1.0 on 4.13 had its build status changed: partially failing to passing
letters.0.1.0 on 4.14 had its build status changed: partially failing to passing
letters.0.1.0 on 5.0 had its build status changed: partially failing to passing
letters.0.1.0 on 5.1 had its build status changed: partially failing to passing
letters.0.1.1 on 4.08 had its build status changed: partially failing to passing
letters.0.1.1 on 4.09 had its build status changed: partially failing to passing
letters.0.1.1 on 4.10 had its build status changed: partially failing to passing
letters.0.1.1 on 4.11 had its build status changed: partially failing to passing
letters.0.1.1 on 4.12 had its build status changed: partially failing to passing
letters.0.1.1 on 4.13 had its build status changed: partially failing to passing
letters.0.1.1 on 4.14 had its build status changed: partially failing to passing
letters.0.1.1 on 5.0 had its build status changed: partially failing to passing
letters.0.1.1 on 5.1 had its build status changed: partially failing to passing
letters.0.2.0 on 4.08 had its build status changed: partially failing to passing
letters.0.2.0 on 4.09 had its build status changed: partially failing to passing
letters.0.2.0 on 4.10 had its build status changed: partially failing to passing
letters.0.2.0 on 4.11 had its build status changed: partially failing to passing
letters.0.2.0 on 4.12 had its build status changed: partially failing to passing
letters.0.2.0 on 4.13 had its build status changed: partially failing to passing
letters.0.2.0 on 4.14 had its build status changed: partially failing to passing
letters.0.2.0 on 5.0 had its build status changed: partially failing to passing
letters.0.2.0 on 5.1 had its build status changed: partially failing to passing
libbinaryen.115.0.0 on 4.12 is now installable. Current state is: passing
libbinaryen.115.0.0 on 4.13 is now installable. Current state is: passing
libbinaryen.115.0.0 on 4.14 is now installable. Current state is: passing
libbinaryen.115.0.0 on 5.0 is now installable. Current state is: passing
libbinaryen.115.0.0 on 5.1 is now installable. Current state is: passing
libsail.0.15 on 4.08 had its build status changed: partially failing to passing
libsail.0.15 on 4.09 had its build status changed: partially failing to passing
libsail.0.15 on 4.10 had its build status changed: partially failing to passing
libsail.0.15 on 4.11 had its build status changed: partially failing to passing
libsail.0.15 on 4.12 had its build status changed: partially failing to passing
libsail.0.15 on 4.13 had its build status changed: partially failing to passing
libsail.0.15 on 4.14 had its build status changed: partially failing to passing
libsail.0.15 on 5.0 had its build status changed: partially failing to passing
libsail.0.15 on 5.1 had its build status changed: partially failing to passing
libsail.0.16 on 4.08 had its build status changed: partially failing to passing
libsail.0.16 on 4.09 had its build status changed: partially failing to passing
libsail.0.16 on 4.10 had its build status changed: partially failing to passing
libsail.0.16 on 4.11 had its build status changed: partially failing to passing
libsail.0.16 on 4.12 had its build status changed: partially failing to passing
libsail.0.16 on 4.13 had its build status changed: partially failing to passing
libsail.0.16 on 4.14 had its build status changed: partially failing to passing
libsail.0.16 on 5.0 had its build status changed: partially failing to passing
libsail.0.16 on 5.1 had its build status changed: partially failing to passing
libsail.0.17.1 on 4.08 is now installable. Current state is: passing
libsail.0.17.1 on 4.09 is now installable. Current state is: passing
libsail.0.17.1 on 4.10 is now installable. Current state is: passing
libsail.0.17.1 on 4.11 is now installable. Current state is: passing
libsail.0.17.1 on 4.12 is now installable. Current state is: passing
libsail.0.17.1 on 4.13 is now installable. Current state is: passing
libsail.0.17.1 on 4.14 is now installable. Current state is: passing
libsail.0.17.1 on 5.0 is now installable. Current state is: passing
libsail.0.17.1 on 5.1 is now installable. Current state is: passing
links-postgresql.0.9.8 on 4.14 is now installable. Current state is: passing
links-postgresql.0.9.8 on 5.0 is now installable. Current state is: passing
links-postgresql.0.9.8 on 5.1 is now installable. Current state is: passing
links-sqlite3.0.9.8 on 4.14 is now installable. Current state is: passing
links-sqlite3.0.9.8 on 5.0 is now installable. Current state is: passing
links-sqlite3.0.9.8 on 5.1 is now installable. Current state is: passing
links.0.9.4 on 4.14 had its build status changed: internal failure to passing
links.0.9.8 on 4.14 is now installable. Current state is: passing
links.0.9.8 on 5.0 is now installable. Current state is: passing
links.0.9.8 on 5.1 is now installable. Current state is: passing
linksem.0.7 on 4.08 had its build status changed: partially failing to passing
linksem.0.7 on 4.09 had its build status changed: partially failing to passing
linksem.0.7 on 4.10 had its build status changed: partially failing to passing
linksem.0.7 on 4.11 had its build status changed: partially failing to passing
linksem.0.7 on 4.12 had its build status changed: partially failing to passing
linksem.0.7 on 4.13 had its build status changed: partially failing to passing
linksem.0.7 on 4.14 had its build status changed: partially failing to passing
linksem.0.8 on 4.08 had its build status changed: partially failing to passing
linksem.0.8 on 4.09 had its build status changed: internal failure to passing
linksem.0.8 on 4.10 had its build status changed: partially failing to passing
linksem.0.8 on 4.11 had its build status changed: partially failing to passing
linksem.0.8 on 4.12 had its build status changed: partially failing to passing
linksem.0.8 on 4.13 had its build status changed: partially failing to passing
linksem.0.8 on 4.14 had its build status changed: partially failing to passing
linksem.0.8 on 5.0 had its build status changed: partially failing to passing
linksem.0.8 on 5.1 had its build status changed: partially failing to passing
linol-lwt.0.2 on 4.09 had its build status changed: internal failure to passing
linol-lwt.0.4 on 4.08 had its build status changed: internal failure to passing
linol.0.2 on 4.08 had its build status changed: partially failing to passing
lintcstubs-arity.0.2.1 on 4.09 had its build status changed: internal failure to passing
linwrap.0.0.1 on 4.08 had its build status changed: partially failing to passing
linwrap.0.0.1 on 4.09 had its build status changed: partially failing to passing
linwrap.0.0.1 on 4.10 had its build status changed: partially failing to passing
linwrap.0.0.1 on 4.11 had its build status changed: partially failing to passing
linwrap.0.0.1 on 4.12 had its build status changed: partially failing to passing
linwrap.0.0.1 on 4.13 had its build status changed: partially failing to passing
linwrap.0.0.1 on 4.14 had its build status changed: partially failing to passing
linwrap.2.0.0 on 4.08 had its build status changed: partially failing to passing
linwrap.2.0.0 on 4.09 had its build status changed: partially failing to passing
linwrap.2.0.0 on 4.10 had its build status changed: partially failing to passing
linwrap.2.0.0 on 4.11 had its build status changed: partially failing to passing
linwrap.2.0.0 on 4.12 had its build status changed: partially failing to passing
linwrap.2.0.0 on 4.13 had its build status changed: partially failing to passing
linwrap.2.0.0 on 4.14 had its build status changed: partially failing to passing
linwrap.4.0.0 on 4.08 had its build status changed: partially failing to passing
linwrap.4.0.0 on 4.09 had its build status changed: partially failing to passing
linwrap.4.0.0 on