Home|Differences with the last checks|Previous runs

Differences between b1ed080 and 8ac7f16 (git diff)

Packages now failing:

• 0install.2.10 on 4.02 had its build status changed: internal failure to failing
• 0install.2.12 on 4.04 had its build status changed: internal failure to failing
• 0install.2.12.1 on 4.05 had its build status changed: internal failure to failing
• 0install.2.15.2 on 4.09 had its build status changed: passing to failing
• 0install.2.6.2 on 4.04 had its build status changed: internal failure to failing
• 0install.2.6.2 on 4.05 had its build status changed: internal failure to failing
• bap-ghidra.2.4.0 on 4.08 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.09 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.10 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.11 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.12 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.13 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.14 is now installable. Current state is: failing
• binsec.0.3 on 4.04 had its build status changed: passing to failing
• binsec.0.3 on 4.05 had its build status changed: passing to failing
• binsec.0.3 on 4.06 had its build status changed: passing to failing
• binsec.0.3 on 4.07 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.05 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.07 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.08 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.11 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.12 had its build status changed: passing to failing
• combine.0.55 on 4.03 had its build status changed: passing to failing
• combine.0.55 on 4.04 had its build status changed: passing to failing
• combine.0.55 on 4.05 had its build status changed: passing to failing
• conf-bison.1 on 4.08 had its build status changed: passing to failing
• conf-bison.2 on 4.06 had its build status changed: passing to failing
• conf-bison.2 on 4.10 had its build status changed: passing to failing
• coq.8.12.1 on 4.07 had its build status changed: passing to failing
• coq.8.12.2 on 4.11 had its build status changed: passing to failing
• coq.8.13.0 on 4.05 had its build status changed: passing to failing
• coq.8.13.1 on 4.08 had its build status changed: passing to failing
• coq.8.14.0 on 4.05 had its build status changed: passing to failing
• coq.8.14.0 on 4.12 had its build status changed: passing to failing
• coq.8.7.0 on 4.05 had its build status changed: passing to failing
• coqide.8.11.0 on 4.05 had its build status changed: passing to failing
• coqide.8.12.1 on 4.05 had its build status changed: passing to failing
• doc-ock-xml.1.0.0 on 4.03 had its build status changed: passing to failing
• electrod.0.2.1 on 4.04 had its build status changed: passing to failing
• frama-c.23.0 on 4.09 had its build status changed: passing to failing
• frama-c.23.1 on 4.09 had its build status changed: passing to failing
• frama-c.24.0 on 4.09 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.12 had its build status changed: passing to failing
• gopcaml-mode.0.0.2 on 4.14 had its build status changed: not available to failing
• irmin-layers.2.4.0 on 4.14 had its build status changed: not available to failing
• irmin-layers.2.5.0 on 4.14 had its build status changed: not available to failing
• irmin-pack.2.5.0 on 4.08 had its build status changed: passing to failing
• irmin-pack.2.7.2 on 4.14 had its build status changed: not available to failing
• irmin-pack.2.8.0 on 4.14 had its build status changed: not available to failing
• mccs.1.1+10 on 4.04 had its build status changed: passing to failing
• mccs.1.1+10 on 4.09 had its build status changed: passing to failing
• mccs.1.1+11 on 4.04 had its build status changed: passing to failing
• mccs.1.1+11 on 4.08 had its build status changed: passing to failing
• mccs.1.1+3 on 4.04 had its build status changed: passing to failing
• mccs.1.1+3 on 4.08 had its build status changed: passing to failing
• mccs.1.1+3 on 4.09 had its build status changed: passing to failing
• mccs.1.1+4 on 4.04 had its build status changed: passing to failing
• mccs.1.1+4 on 4.06 had its build status changed: passing to failing
• mccs.1.1+5 on 4.04 had its build status changed: passing to failing
• mccs.1.1+5 on 4.05 had its build status changed: passing to failing
• mccs.1.1+6 on 4.09 had its build status changed: passing to failing
• mccs.1.1+9 on 4.03 had its build status changed: passing to failing
• mccs.1.1+9 on 4.05 had its build status changed: passing to failing
• mccs.1.1+9 on 4.09 had its build status changed: passing to failing
• metaquot.0.5.0 on 4.14 had its build status changed: not available to failing
• mldonkey.3.1.6 on 4.02 had its build status changed: passing to failing
• mldonkey.3.1.6 on 4.04 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.06 had its build status changed: passing to failing
• mysql8.1.0 on 4.14 had its build status changed: not available to failing
• nuscr.1.0.0 on 4.04 had its build status changed: passing to failing
• nuscr.1.0.0 on 4.05 had its build status changed: passing to failing
• nuscr.1.0.0 on 4.06 had its build status changed: passing to failing
• nuscr.1.0.0 on 4.07 had its build status changed: passing to failing
• nuscr.1.0.0 on 4.08 had its build status changed: passing to failing
• nuscr.1.0.0 on 4.09 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.04 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.05 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.06 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.07 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.08 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.09 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.10 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.11 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.12 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.02 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.03 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.04 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.05 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.06 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.07 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.08 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.09 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.10 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.11 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.12 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.13 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.14 had its build status changed: passing to failing
• odoc.2.0.0 on 4.14 had its build status changed: not available to failing
• ojs-base.0.5.0 on 4.03 had its build status changed: partially failing to failing
• ojs-base.0.5.0 on 4.04 had its build status changed: partially failing to failing
• oplsr.8.0.1 on 4.13 had its build status changed: not available to failing
• petr4.0.1 on 4.04 had its build status changed: passing to failing
• petr4.0.1 on 4.05 had its build status changed: passing to failing
• petr4.0.1 on 4.06 had its build status changed: passing to failing
• petr4.0.1 on 4.07 had its build status changed: passing to failing
• petr4.0.1 on 4.08 had its build status changed: passing to failing
• petr4.0.1 on 4.09 had its build status changed: passing to failing
• petr4.0.1.1 on 4.04 had its build status changed: passing to failing
• petr4.0.1.1 on 4.05 had its build status changed: passing to failing
• petr4.0.1.1 on 4.06 had its build status changed: passing to failing
• petr4.0.1.1 on 4.07 had its build status changed: passing to failing
• petr4.0.1.1 on 4.08 had its build status changed: passing to failing
• petr4.0.1.1 on 4.09 had its build status changed: passing to failing
• pfff.0.40.4 on 4.07 had its build status changed: passing to failing
• pfff.0.40.4 on 4.08 had its build status changed: passing to failing
• pfff.0.40.4 on 4.09 had its build status changed: passing to failing
• pfff.0.40.4 on 4.10 had its build status changed: passing to failing
• pfff.0.40.4 on 4.11 had its build status changed: passing to failing
• rdf.0.11.0 on 4.08 had its build status changed: passing to failing
• rdf.0.11.0 on 4.09 had its build status changed: passing to failing
• rdf.0.11.0 on 4.10 had its build status changed: passing to failing
• rdf.0.12.0 on 4.12 had its build status changed: passing to failing
• rdf.0.6.0 on 4.03 had its build status changed: passing to failing
• rdf.0.6.0 on 4.04 had its build status changed: passing to failing
• rdf.0.6.0 on 4.05 had its build status changed: passing to failing
• rdf.0.7.0 on 4.02 had its build status changed: passing to failing
• reason.3.5.0 on 4.03 had its build status changed: passing to failing
• reason.3.5.0 on 4.04 had its build status changed: passing to failing
• reason.3.5.0 on 4.05 had its build status changed: passing to failing
• reason.3.5.0 on 4.06 had its build status changed: passing to failing
• reason.3.5.0 on 4.07 had its build status changed: passing to failing
• reason.3.5.0 on 4.08 had its build status changed: passing to failing
• reason.3.5.2 on 4.03 had its build status changed: passing to failing
• reason.3.5.2 on 4.04 had its build status changed: passing to failing
• reason.3.5.2 on 4.05 had its build status changed: passing to failing
• reason.3.5.2 on 4.06 had its build status changed: passing to failing
• reason.3.5.2 on 4.07 had its build status changed: passing to failing
• reason.3.5.2 on 4.08 had its build status changed: passing to failing
• reason.3.5.2 on 4.09 had its build status changed: passing to failing
• spotlib.4.0.3 on 4.08 had its build status changed: passing to failing
• spotlib.4.0.3 on 4.09 had its build status changed: passing to failing
• spotlib.4.0.3 on 4.10 had its build status changed: passing to failing
• spotlib.4.0.3 on 4.11 had its build status changed: passing to failing
• sqlgg.0.2.5 on 4.03 had its build status changed: passing to failing
• sqlgg.0.2.5 on 4.04 had its build status changed: passing to failing
• sqlgg.0.2.5 on 4.05 had its build status changed: passing to failing
• sqlgg.0.2.5 on 4.06 had its build status changed: passing to failing
• sqlgg.0.2.5 on 4.07 had its build status changed: passing to failing
• sqlgg.0.3.0 on 4.03 had its build status changed: passing to failing
• sqlgg.0.3.0 on 4.04 had its build status changed: passing to failing
• sqlgg.0.3.0 on 4.05 had its build status changed: passing to failing
• sqlgg.0.3.0 on 4.06 had its build status changed: passing to failing
• sqlgg.0.3.0 on 4.07 had its build status changed: passing to failing
• sqlgg.0.4.3 on 4.03 had its build status changed: passing to failing
• sqlgg.0.4.3 on 4.04 had its build status changed: passing to failing
• sqlgg.0.4.3 on 4.05 had its build status changed: passing to failing
• sqlgg.0.4.3 on 4.06 had its build status changed: passing to failing
• sqlgg.0.4.3 on 4.07 had its build status changed: passing to failing
• stog-writing.0.11.0 on 4.03 had its build status changed: passing to failing
• stog-writing.0.11.0 on 4.04 had its build status changed: passing to failing
• stog-writing.0.11.0 on 4.05 had its build status changed: passing to failing
• stog.0.19.0 on 4.12 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.14 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.14 is now installable. Current state is: failing
• unmagic.1.0.4 on 4.08 had its build status changed: passing to failing
• unmagic.1.0.4 on 4.09 had its build status changed: passing to failing
• unmagic.1.0.4 on 4.10 had its build status changed: passing to failing
• unmagic.1.0.4 on 4.11 had its build status changed: passing to failing
• why3-ide.1.3.0 on 4.09 had its build status changed: passing to failing
• why3-ide.1.3.1 on 4.09 had its build status changed: passing to failing
• why3-ide.1.3.2 on 4.09 had its build status changed: passing to failing
• why3-ide.1.3.3 on 4.09 had its build status changed: passing to failing
• why3-ide.1.4.0 on 4.09 had its build status changed: passing to failing
• xapi-stdext-threads.4.14.0 on 4.14 had its build status changed: not available to failing
• xapi-stdext-threads.4.16.0 on 4.14 had its build status changed: not available to failing

Packages now partially failing:

• aws-s3.2.0.0 on 4.05 had its build status changed: passing to partially failing
• bap-extra.2.4.0 on 4.08 is now installable. Current state is: partially failing
• bap-extra.2.4.0 on 4.09 is now installable. Current state is: partially failing
• bap-extra.2.4.0 on 4.10 is now installable. Current state is: partially failing
• bap-extra.2.4.0 on 4.11 is now installable. Current state is: partially failing
• bap-extra.2.4.0 on 4.12 is now installable. Current state is: partially failing
• camels.0.0.3 on 4.14 had its build status changed: not available to partially failing
• camels.0.0.4 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-mirage.0.7.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-mirage.0.8.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-mirage.0.9.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-mirage.1.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-mirage.1.1 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-mirage.1.2 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-mirage.1.2.1 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-net.0.7.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-net.0.8.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-net.0.9.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-net.1.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-net.1.1 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-net.1.2 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-net.1.2.1 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-unix.0.7.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-unix.0.8.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-unix.0.9.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-unix.1.0 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-unix.1.1 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-unix.1.2 on 4.14 had its build status changed: not available to partially failing
• capnp-rpc-unix.1.2.1 on 4.14 had its build status changed: not available to partially failing
• caqti-driver-mariadb.1.2.0 on 4.14 had its build status changed: not available to partially failing
• caqti-driver-mariadb.1.2.1 on 4.14 had its build status changed: not available to partially failing
• caqti-driver-mariadb.1.2.3 on 4.14 had its build status changed: not available to partially failing
• clangml-transforms.0.26 on 4.14 had its build status changed: not available to partially failing
• clangml.4.5.0 on 4.14 had its build status changed: not available to partially failing
• coq-serapi.8.8.0+0.5.6 on 4.07 had its build status changed: passing to partially failing
• current_examples.0.2 on 4.14 had its build status changed: not available to partially failing
• current_examples.0.3 on 4.14 had its build status changed: not available to partially failing
• current_examples.0.4 on 4.14 had its build status changed: not available to partially failing
• current_examples.0.5 on 4.14 had its build status changed: not available to partially failing
• current_ocluster.0.1 on 4.14 had its build status changed: not available to partially failing
• hardcaml_waveterm.v0.14.0 on 4.14 had its build status changed: not available to partially failing
• irmin-bench.2.4.0 on 4.14 had its build status changed: not available to partially failing
• irmin-bench.2.5.0 on 4.14 had its build status changed: not available to partially failing
• irmin-bench.2.5.2 on 4.14 had its build status changed: not available to partially failing
• irmin-bench.2.5.3 on 4.14 had its build status changed: not available to partially failing
• irmin-bench.2.7.0 on 4.14 had its build status changed: not available to partially failing
• irmin-bench.2.9.0 on 4.14 had its build status changed: not available to partially failing
• irmin-containers.2.6.0 on 4.14 had its build status changed: not available to partially failing
• irmin-containers.2.7.2 on 4.14 had its build status changed: not available to partially failing
• irmin-containers.2.9.0 on 4.14 had its build status changed: not available to partially failing
• irmin-git.2.7.1 on 4.14 had its build status changed: not available to partially failing
• irmin-graphql.2.1.0 on 4.07 had its build status changed: passing to partially failing
• irmin-graphql.2.4.0 on 4.14 had its build status changed: not available to partially failing
• irmin-graphql.2.5.1 on 4.14 had its build status changed: not available to partially failing
• irmin-http.1.3.3 on 4.07 had its build status changed: passing to partially failing
• irmin-http.2.3.0 on 4.10 had its build status changed: passing to partially failing
• irmin-layers.2.5.2 on 4.14 had its build status changed: not available to partially failing
• irmin-layers.2.5.4 on 4.09 had its build status changed: passing to partially failing
• irmin-layers.2.5.4 on 4.14 had its build status changed: not available to partially failing
• irmin-layers.2.9.0 on 4.11 had its build status changed: passing to partially failing
• irmin-mirage-git.2.2.0 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage-git.2.5.0 on 4.13 had its build status changed: passing to partially failing
• irmin-mirage-graphql.2.0.0 on 4.12 had its build status changed: passing to partially failing
• irmin-mirage-graphql.2.2.0 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage-graphql.2.5.2 on 4.08 had its build status changed: passing to partially failing
• irmin-mirage-graphql.2.5.3 on 4.14 had its build status changed: not available to partially failing
• irmin-mirage-graphql.2.6.0 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage-graphql.2.8.0 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage.2.0.0 on 4.07 had its build status changed: passing to partially failing
• irmin-mirage.2.2.0 on 4.12 had its build status changed: passing to partially failing
• irmin-mirage.2.5.0 on 4.14 had its build status changed: not available to partially failing
• irmin-mirage.2.6.0 on 4.11 had its build status changed: passing to partially failing
• irmin-mirage.2.6.1 on 4.14 had its build status changed: not available to partially failing
• irmin-mirage.2.7.1 on 4.11 had its build status changed: passing to partially failing
• irmin-mirage.2.7.1 on 4.14 had its build status changed: not available to partially failing
• irmin-pack.2.5.0 on 4.14 had its build status changed: not available to partially failing
• irmin-pack.2.5.2 on 4.13 had its build status changed: passing to partially failing
• irmin-pack.2.5.2 on 4.14 had its build status changed: not available to partially failing
• irmin-test.2.5.1 on 4.14 had its build status changed: not available to partially failing
• irmin-test.2.7.0 on 4.14 had its build status changed: not available to partially failing
• irmin-tezos.2.9.0 on 4.13 had its build status changed: passing to partially failing
• irmin-tezos.2.9.0 on 4.14 had its build status changed: not available to partially failing
• irmin-unix.1.2.0 on 4.05 had its build status changed: passing to partially failing
• irmin-unix.2.0.0 on 4.07 had its build status changed: passing to partially failing
• irmin-unix.2.3.0 on 4.09 had its build status changed: passing to partially failing
• irmin-unix.2.3.0 on 4.11 had its build status changed: passing to partially failing
• irmin-unix.2.5.1 on 4.11 had its build status changed: passing to partially failing
• irmin-unix.2.6.0 on 4.14 had its build status changed: not available to partially failing
• irmin-unix.2.6.1 on 4.08 had its build status changed: passing to partially failing
• irmin-unix.2.7.1 on 4.08 had its build status changed: passing to partially failing
• irmin-unix.2.7.2 on 4.11 had its build status changed: passing to partially failing
• irmin-unix.2.8.0 on 4.14 had its build status changed: not available to partially failing
• irmin-unix.2.9.0 on 4.09 had its build status changed: passing to partially failing
• irmin-watcher.0.1.1 on 4.04 had its build status changed: passing to partially failing
• irmin-watcher.0.3.0 on 4.14 had its build status changed: passing to partially failing
• irmin-watcher.0.4.0 on 4.06 had its build status changed: passing to partially failing
• irmin-watcher.0.4.1 on 4.07 had its build status changed: passing to partially failing
• irmin.1.1.0 on 4.05 had its build status changed: failing to partially failing
• irmin.1.3.2 on 4.08 had its build status changed: passing to partially failing
• irmin.2.1.0 on 4.11 had its build status changed: passing to partially failing
• irmin.2.2.0 on 4.07 had its build status changed: passing to partially failing
• irmin.2.2.0 on 4.09 had its build status changed: passing to partially failing
• lbvs_consent.1.1.2 on 4.13 had its build status changed: not available to partially failing
• lbvs_consent.1.1.3 on 4.13 had its build status changed: not available to partially failing
• lbvs_consent.2.1.0 on 4.13 had its build status changed: not available to partially failing
• lbvs_consent.2.1.1 on 4.13 had its build status changed: not available to partially failing
• lbvs_consent.2.1.2 on 4.13 had its build status changed: not available to partially failing
• memcad.1.1.0 on 4.14 had its build status changed: not available to partially failing
• notty_async.v0.14.0 on 4.14 had its build status changed: not available to partially failing
• ocluster-api.0.1 on 4.14 had its build status changed: not available to partially failing
• ocluster.0.1 on 4.14 had its build status changed: not available to partially failing
• odiff-gtk.1.0 on 4.02 had its build status changed: passing to partially failing
• odiff-gtk.1.0 on 4.03 had its build status changed: passing to partially failing
• odiff-gtk.1.0 on 4.04 had its build status changed: passing to partially failing
• odiff-gtk.1.0 on 4.05 had its build status changed: passing to partially failing
• override.0.4.0 on 4.14 had its build status changed: not available to partially failing
• owl-ode-sundials.0.5.0 on 4.14 is now installable. Current state is: partially failing
• pattern.0.3.0 on 4.14 had its build status changed: not available to partially failing
• pattern.0.3.1 on 4.14 had its build status changed: not available to partially failing
• pyast.0.1.0 on 4.14 had its build status changed: not available to partially failing
• pyast.0.1.1 on 4.14 had its build status changed: not available to partially failing
• refl.0.4.0 on 4.14 had its build status changed: not available to partially failing
• shared-block-ring.2.3.0 on 4.02 had its build status changed: passing to partially failing
• stog-writing.0.19.0 on 4.12 had its build status changed: passing to partially failing
• tezos-context-hash-irmin.1.0.0 on 4.14 had its build status changed: not available to partially failing
• tezos-context.11.0 on 4.14 had its build status changed: not available to partially failing
• tezos-embedded-protocol-003-PsddFKi3.7.3 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-commands.11.0 on 4.14 had its build status changed: not available to partially failing
• tezos-mockup-commands.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-proxy.11.0 on 4.14 had its build status changed: not available to partially failing
• tezos-shell-context.11.0 on 4.14 had its build status changed: not available to partially failing
• traverse.0.3.0 on 4.14 had its build status changed: not available to partially failing
• vpnkit.0.1.1 on 4.04 had its build status changed: passing to partially failing
• vpnkit.0.1.1 on 4.05 had its build status changed: passing to partially failing
• xapi-inventory.1.2.1 on 4.14 had its build status changed: not available to partially failing

Packages now not available:

• 0install-gtk.2.15.2 on 4.02 had its build status changed: internal failure to not available
• 0install-gtk.2.15.2 on 4.04 had its build status changed: internal failure to not available
• 0install-solver.2.17 on 4.03 had its build status changed: internal failure to not available
• 0install-solver.2.17 on 4.05 had its build status changed: internal failure to not available
• 0install-solver.2.17 on 4.07 had its build status changed: internal failure to not available
• 0install.2.10 on 4.06 had its build status changed: internal failure to not available
• 0install.2.10 on 4.11 had its build status changed: internal failure to not available
• 0install.2.10 on 4.13 had its build status changed: internal failure to not available
• 0install.2.10 on 4.14 had its build status changed: internal failure to not available
• 0install.2.11 on 4.06 had its build status changed: internal failure to not available
• 0install.2.11 on 4.09 had its build status changed: internal failure to not available
• 0install.2.12 on 4.09 had its build status changed: internal failure to not available
• 0install.2.12 on 4.11 had its build status changed: internal failure to not available
• 0install.2.12.1 on 4.13 had its build status changed: internal failure to not available
• 0install.2.12.3 on 4.07 had its build status changed: internal failure to not available
• 0install.2.12.3 on 4.11 had its build status changed: internal failure to not available
• 0install.2.14 on 4.10 had its build status changed: internal failure to not available
• 0install.2.14 on 4.11 had its build status changed: internal failure to not available
• 0install.2.15.1 on 4.04 had its build status changed: internal failure to not available
• 0install.2.17 on 4.06 had its build status changed: internal failure to not available
• 0install.2.6.2 on 4.12 had its build status changed: internal failure to not available
• 0install.2.9.1 on 4.08 had its build status changed: internal failure to not available
• 0install.2.9.1 on 4.09 had its build status changed: internal failure to not available
• conjury.2.0 on 4.13 had its build status changed: passing to not available
• conjury.2.0 on 4.14 had its build status changed: passing to not available
• conjury.2.0.1 on 4.13 had its build status changed: passing to not available
• conjury.2.0.1 on 4.14 had its build status changed: passing to not available
• containers.0.15 on 4.12 had its build status changed: internal failure to not available
• containers.0.17 on 4.14 had its build status changed: internal failure to not available
• containers.0.19 on 4.08 had its build status changed: internal failure to not available
• containers.0.20 on 4.14 had its build status changed: internal failure to not available
• containers.0.22 on 4.08 had its build status changed: internal failure to not available
• raw_spacetime.base on 4.12 had its build status changed: passing to not available
• raw_spacetime.base on 4.13 had its build status changed: passing to not available
• raw_spacetime.base on 4.14 had its build status changed: passing to not available
• termbox.0.1.0 on 4.02 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.03 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.04 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.05 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.06 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.07 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.08 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.09 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.10 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.11 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.12 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.13 is not available anymore. Previous state was: passing
• termbox.0.1.0 on 4.14 is not available anymore. Previous state was: passing

Packages now failing with an internal failure:

• build_path_prefix_map.0.2 on 4.04 had its build status changed: passing to internal failure
• build_path_prefix_map.0.2 on 4.08 had its build status changed: passing to internal failure
• build_path_prefix_map.0.2 on 4.09 had its build status changed: passing to internal failure
• build_path_prefix_map.0.2 on 4.13 had its build status changed: passing to internal failure
• build_path_prefix_map.0.2 on 4.14 had its build status changed: passing to internal failure
• cowabloga.0.0.1 on 4.02 had its build status changed: partially failing to internal failure
• cowabloga.0.0.2 on 4.02 had its build status changed: partially failing to internal failure
• cowabloga.0.0.4 on 4.02 had its build status changed: partially failing to internal failure
• cowabloga.0.0.5 on 4.02 had its build status changed: passing to internal failure
• cowabloga.0.0.6 on 4.02 had its build status changed: passing to internal failure
• dose.3.2.2 on 4.02 had its build status changed: failing to internal failure
• dose.3.2.2 on 4.04 had its build status changed: failing to internal failure
• dose.3.2.2 on 4.05 had its build status changed: failing to internal failure
• dose.3.2.2+opam on 4.02 had its build status changed: passing to internal failure
• dose.3.2.2+opam on 4.03 had its build status changed: passing to internal failure
• dose.3.2.2+opam on 4.04 had its build status changed: passing to internal failure
• elina.1.3 on 4.09 had its build status changed: passing to internal failure
• frag.0.1.0 on 4.02 had its build status changed: failing to internal failure
• frag.0.1.0 on 4.03 had its build status changed: failing to internal failure
• frag.0.1.0 on 4.04 had its build status changed: failing to internal failure
• frag.0.1.0 on 4.05 had its build status changed: failing to internal failure
• glical.0.0.1 on 4.03 had its build status changed: passing to internal failure
• glical.0.0.2 on 4.02 had its build status changed: passing to internal failure
• glical.0.0.2 on 4.04 had its build status changed: passing to internal failure
• glical.0.0.2 on 4.05 had its build status changed: passing to internal failure
• glical.0.0.3 on 4.04 had its build status changed: passing to internal failure
• glical.0.0.3 on 4.09 had its build status changed: passing to internal failure
• glical.0.0.3 on 4.12 had its build status changed: passing to internal failure
• glical.0.0.4 on 4.05 had its build status changed: passing to internal failure
• glical.0.0.4 on 4.09 had its build status changed: passing to internal failure
• glical.0.0.4 on 4.10 had its build status changed: passing to internal failure
• glical.0.0.5 on 4.02 had its build status changed: passing to internal failure
• glical.0.0.5 on 4.11 had its build status changed: passing to internal failure
• glical.0.0.5 on 4.13 had its build status changed: passing to internal failure
• glical.0.0.7 on 4.05 had its build status changed: passing to internal failure
• glical.0.0.7 on 4.06 had its build status changed: passing to internal failure
• glical.0.0.7 on 4.08 had its build status changed: passing to internal failure
• glical.0.0.7 on 4.10 had its build status changed: passing to internal failure
• heptagon.1.00.06 on 4.02 had its build status changed: passing to internal failure
• heptagon.1.00.06 on 4.03 had its build status changed: passing to internal failure
• heptagon.1.00.06 on 4.04 had its build status changed: passing to internal failure
• http-cookie.3.0.0 on 4.10 had its build status changed: passing to internal failure
• http-cookie.3.0.0 on 4.11 had its build status changed: passing to internal failure
• http-cookie.3.0.0 on 4.12 had its build status changed: passing to internal failure
• http-cookie.3.0.0 on 4.13 had its build status changed: passing to internal failure
• irmin-bench.2.5.1 on 4.14 had its build status changed: not available to internal failure
• irmin-bench.2.5.4 on 4.14 had its build status changed: not available to internal failure
• irmin-bench.2.6.0 on 4.14 had its build status changed: not available to internal failure
• irmin-bench.2.6.1 on 4.14 had its build status changed: not available to internal failure
• irmin-bench.2.7.2 on 4.14 had its build status changed: not available to internal failure
• irmin-bench.2.8.0 on 4.14 had its build status changed: not available to internal failure
• irmin-containers.2.4.0 on 4.14 had its build status changed: not available to internal failure
• irmin-containers.2.5.0 on 4.14 had its build status changed: not available to internal failure
• irmin-containers.2.6.1 on 4.14 had its build status changed: not available to internal failure
• irmin-containers.2.7.0 on 4.14 had its build status changed: not available to internal failure
• irmin-containers.2.7.1 on 4.14 had its build status changed: not available to internal failure
• irmin-containers.2.8.0 on 4.14 had its build status changed: not available to internal failure
• irmin-git.2.6.1 on 4.10 had its build status changed: passing to internal failure
• irmin-git.2.9.0 on 4.14 had its build status changed: not available to internal failure
• irmin-graphql.2.1.0 on 4.11 had its build status changed: passing to internal failure
• irmin-graphql.2.3.0 on 4.08 had its build status changed: passing to internal failure
• irmin-graphql.2.5.0 on 4.09 had its build status changed: passing to internal failure
• irmin-graphql.2.5.0 on 4.14 had its build status changed: not available to internal failure
• irmin-graphql.2.5.3 on 4.14 had its build status changed: not available to internal failure
• irmin-graphql.2.6.0 on 4.14 had its build status changed: not available to internal failure
• irmin-graphql.2.6.1 on 4.09 had its build status changed: passing to internal failure
• irmin-graphql.2.7.0 on 4.11 had its build status changed: passing to internal failure
• irmin-graphql.2.7.1 on 4.06 had its build status changed: not available to internal failure
• irmin-graphql.2.8.0 on 4.02 had its build status changed: not available to internal failure
• irmin-http.2.5.3 on 4.10 had its build status changed: passing to internal failure
• irmin-http.2.6.1 on 4.12 had its build status changed: passing to internal failure
• irmin-http.2.7.0 on 4.10 had its build status changed: passing to internal failure
• irmin-http.2.7.1 on 4.09 had its build status changed: passing to internal failure
• irmin-http.2.7.2 on 4.14 had its build status changed: not available to internal failure
• irmin-http.2.9.0 on 4.14 had its build status changed: not available to internal failure
• irmin-indexeddb.0.1 on 4.02 had its build status changed: passing to internal failure
• irmin-indexeddb.0.3 on 4.04 had its build status changed: passing to internal failure
• irmin-layers.2.6.1 on 4.12 had its build status changed: passing to internal failure
• irmin-layers.2.6.1 on 4.14 had its build status changed: not available to internal failure
• irmin-layers.2.7.0 on 4.12 had its build status changed: passing to internal failure
• irmin-layers.2.7.2 on 4.12 had its build status changed: passing to internal failure
• irmin-layers.2.8.0 on 4.14 had its build status changed: not available to internal failure
• irmin-mem.1.2.0 on 4.03 had its build status changed: passing to internal failure
• irmin-mem.1.3.0 on 4.13 had its build status changed: passing to internal failure
• irmin-mem.2.3.0 on 4.03 had its build status changed: not available to internal failure
• irmin-mirage-git.2.4.0 on 4.06 had its build status changed: not available to internal failure
• irmin-mirage-git.2.5.0 on 4.14 had its build status changed: not available to internal failure
• irmin-mirage-git.2.5.3 on 4.14 had its build status changed: not available to internal failure
• irmin-mirage-git.2.6.0 on 4.07 had its build status changed: not available to internal failure
• irmin-mirage-git.2.7.0 on 4.11 had its build status changed: passing to internal failure
• irmin-mirage-graphql.2.5.2 on 4.10 had its build status changed: passing to internal failure
• irmin-mirage-graphql.2.6.0 on 4.13 had its build status changed: passing to internal failure
• irmin-mirage-graphql.2.7.2 on 4.12 had its build status changed: passing to internal failure
• irmin-mirage-graphql.2.9.0 on 4.07 had its build status changed: not available to internal failure
• irmin-mirage.1.2.0 on 4.02 had its build status changed: not available to internal failure
• irmin-pack.2.2.0 on 4.09 had its build status changed: passing to internal failure
• irmin-pack.2.4.0 on 4.14 had its build status changed: not available to internal failure
• irmin-pack.2.5.1 on 4.14 had its build status changed: not available to internal failure
• irmin-pack.2.5.3 on 4.14 had its build status changed: not available to internal failure
• irmin-pack.2.5.4 on 4.14 had its build status changed: not available to internal failure
• irmin-pack.2.6.0 on 4.14 had its build status changed: not available to internal failure
• irmin-pack.2.6.1 on 4.14 had its build status changed: not available to internal failure
• irmin-pack.2.7.0 on 4.14 had its build status changed: not available to internal failure
• irmin-pack.2.7.1 on 4.14 had its build status changed: not available to internal failure
• irmin-pack.2.9.0 on 4.14 had its build status changed: not available to internal failure
• irmin-test.2.0.0 on 4.08 had its build status changed: passing to internal failure
• irmin-test.2.4.0 on 4.13 had its build status changed: passing to internal failure
• irmin-test.2.5.0 on 4.10 had its build status changed: passing to internal failure
• irmin-test.2.5.1 on 4.08 had its build status changed: passing to internal failure
• irmin-test.2.5.3 on 4.14 had its build status changed: not available to internal failure
• irmin-test.2.5.4 on 4.12 had its build status changed: passing to internal failure
• irmin-test.2.5.4 on 4.14 had its build status changed: not available to internal failure
• irmin-test.2.6.0 on 4.10 had its build status changed: passing to internal failure
• irmin-test.2.6.1 on 4.09 had its build status changed: passing to internal failure
• irmin-test.2.7.0 on 4.08 had its build status changed: passing to internal failure
• irmin-test.2.7.0 on 4.12 had its build status changed: passing to internal failure
• irmin-test.2.7.2 on 4.08 had its build status changed: passing to internal failure
• irmin-test.2.8.0 on 4.11 had its build status changed: passing to internal failure
• irmin-test.2.8.0 on 4.14 had its build status changed: not available to internal failure
• irmin-tezos.2.9.0 on 4.09 had its build status changed: passing to internal failure
• irmin-tezos.2.9.0 on 4.12 had its build status changed: passing to internal failure
• irmin-unix.1.0.0 on 4.03 had its build status changed: partially failing to internal failure
• irmin-unix.1.3.0 on 4.03 had its build status changed: passing to internal failure
• irmin-unix.1.3.3 on 4.10 had its build status changed: not available to internal failure
• irmin-unix.1.3.3 on 4.11 had its build status changed: not available to internal failure
• irmin-unix.2.1.0 on 4.06 had its build status changed: passing to internal failure
• irmin-unix.2.1.0 on 4.07 had its build status changed: passing to internal failure
• irmin-unix.2.3.0 on 4.02 had its build status changed: not available to internal failure
• irmin-unix.2.4.0 on 4.11 had its build status changed: passing to internal failure
• irmin-unix.2.4.0 on 4.14 had its build status changed: not available to internal failure
• irmin-unix.2.5.0 on 4.11 had its build status changed: passing to internal failure
• irmin-unix.2.5.0 on 4.14 had its build status changed: not available to internal failure
• irmin-unix.2.5.3 on 4.12 had its build status changed: passing to internal failure
• irmin-unix.2.5.4 on 4.10 had its build status changed: passing to internal failure
• irmin-unix.2.6.0 on 4.12 had its build status changed: passing to internal failure
• irmin-unix.2.6.1 on 4.09 had its build status changed: passing to internal failure
• irmin-unix.2.6.1 on 4.14 had its build status changed: not available to internal failure
• irmin-unix.2.7.0 on 4.14 had its build status changed: not available to internal failure
• irmin-unix.2.7.1 on 4.14 had its build status changed: not available to internal failure
• irmin-unix.2.7.2 on 4.13 had its build status changed: passing to internal failure
• irmin-unix.2.7.2 on 4.14 had its build status changed: not available to internal failure
• irmin-unix.2.8.0 on 4.12 had its build status changed: passing to internal failure
• irmin-unix.2.9.0 on 4.14 had its build status changed: not available to internal failure
• irmin-watcher.0.1.0 on 4.07 had its build status changed: passing to internal failure
• irmin-watcher.0.1.4 on 4.06 had its build status changed: passing to internal failure
• irmin-watcher.0.1.4 on 4.12 had its build status changed: not available to internal failure
• irmin-watcher.0.4.0 on 4.03 had its build status changed: passing to internal failure
• irmin-watcher.0.4.1 on 4.08 had its build status changed: passing to internal failure
• irmin-watcher.0.5.0 on 4.14 had its build status changed: passing to internal failure
• irmin.0.11.1 on 4.04 had its build status changed: failing to internal failure
• irmin.0.12.0 on 4.03 had its build status changed: passing to internal failure
• irmin.0.8.0 on 4.02 had its build status changed: passing to internal failure
• irmin.0.8.1 on 4.05 had its build status changed: not available to internal failure
• irmin.0.8.2 on 4.12 had its build status changed: not available to internal failure
• irmin.0.8.3 on 4.02 had its build status changed: passing to internal failure
• irmin.0.9.10 on 4.03 had its build status changed: not available to internal failure
• irmin.0.9.5 on 4.02 had its build status changed: passing to internal failure
• irmin.0.9.5 on 4.06 had its build status changed: not available to internal failure
• irmin.0.9.6 on 4.11 had its build status changed: not available to internal failure
• irmin.0.9.7 on 4.02 had its build status changed: passing to internal failure
• irmin.0.9.9 on 4.03 had its build status changed: not available to internal failure
• irmin.0.9.9 on 4.12 had its build status changed: not available to internal failure
• irmin.1.0.0 on 4.03 had its build status changed: passing to internal failure
• irmin.1.0.0 on 4.11 had its build status changed: not available to internal failure
• irmin.1.0.1 on 4.03 had its build status changed: passing to internal failure
• irmin.1.0.1 on 4.10 had its build status changed: not available to internal failure
• irmin.1.0.2 on 4.03 had its build status changed: passing to internal failure
• irmin.1.0.2 on 4.09 had its build status changed: not available to internal failure
• irmin.1.1.0 on 4.10 had its build status changed: not available to internal failure
• irmin.1.2.0 on 4.11 had its build status changed: not available to internal failure
• irmin.1.3.2 on 4.11 had its build status changed: passing to internal failure
• irmin.1.4.0 on 4.12 had its build status changed: passing to internal failure
• irmin.2.0.0 on 4.09 had its build status changed: passing to internal failure
• irmin.2.1.0 on 4.08 had its build status changed: passing to internal failure
• irmin.2.1.0 on 4.14 had its build status changed: passing to internal failure
• irmin.2.2.0 on 4.13 had its build status changed: passing to internal failure
• irmin.2.3.0 on 4.11 had its build status changed: passing to internal failure
• irmin.2.4.0 on 4.11 had its build status changed: passing to internal failure
• irmin.2.5.0 on 4.10 had its build status changed: passing to internal failure
• irmin.2.5.0 on 4.14 had its build status changed: not available to internal failure
• irmin.2.5.1 on 4.09 had its build status changed: passing to internal failure
• irmin.2.5.2 on 4.02 had its build status changed: not available to internal failure
• irmin.2.5.2 on 4.05 had its build status changed: not available to internal failure
• irmin.2.5.2 on 4.11 had its build status changed: passing to internal failure
• irmin.2.5.3 on 4.08 had its build status changed: passing to internal failure
• irmin.2.5.3 on 4.13 had its build status changed: passing to internal failure
• irmin.2.5.4 on 4.11 had its build status changed: passing to internal failure
• irmin.2.5.4 on 4.14 had its build status changed: not available to internal failure
• irmin.2.6.0 on 4.12 had its build status changed: passing to internal failure
• irmin.2.6.1 on 4.06 had its build status changed: not available to internal failure
• irmin.2.6.1 on 4.13 had its build status changed: passing to internal failure
• irmin.2.6.1 on 4.14 had its build status changed: not available to internal failure
• irmin.2.7.0 on 4.07 had its build status changed: not available to internal failure
• irmin.2.7.0 on 4.13 had its build status changed: passing to internal failure
• irmin.2.7.1 on 4.12 had its build status changed: passing to internal failure
• irrlicht.0.0.5 on 4.07 had its build status changed: passing to internal failure
• itv-tree.2.1 on 4.02 had its build status changed: passing to internal failure
• ivy.1.3.1 on 4.02 had its build status changed: failing to internal failure
• jane-street-headers.v0.14.0 on 4.08 had its build status changed: passing to internal failure
• javalib.2.3.1 on 4.02 had its build status changed: passing to internal failure
• javalib.2.3.1 on 4.03 had its build status changed: passing to internal failure
• javalib.2.3.3 on 4.05 had its build status changed: passing to internal failure
• javalib.2.3.4 on 4.03 had its build status changed: passing to internal failure
• javalib.2.3.4 on 4.06 had its build status changed: passing to internal failure
• javalib.2.3.4 on 4.07 had its build status changed: not available to internal failure
• javalib.2.3.5 on 4.05 had its build status changed: passing to internal failure
• javalib.2.3.5 on 4.06 had its build status changed: passing to internal failure
• javalib.2.3.5 on 4.07 had its build status changed: passing to internal failure
• javalib.2.3.5 on 4.08 had its build status changed: passing to internal failure
• javalib.2.3.5 on 4.09 had its build status changed: passing to internal failure
• javalib.2.3.5 on 4.10 had its build status changed: passing to internal failure
• javalib.2.3.5 on 4.11 had its build status changed: passing to internal failure
• javalib.2.3.5 on 4.12 had its build status changed: passing to internal failure
• javalib.3.0 on 4.11 had its build status changed: passing to internal failure
• javalib.3.1.1 on 4.02 had its build status changed: not available to internal failure
• javalib.3.1.1 on 4.06 had its build status changed: passing to internal failure
• javalib.3.2 on 4.07 had its build status changed: passing to internal failure
• javalib.3.2.1 on 4.13 had its build status changed: passing to internal failure
• jbuilder.1.0+beta10 on 4.02 had its build status changed: passing to internal failure
• jbuilder.1.0+beta11 on 4.04 had its build status changed: passing to internal failure
• jbuilder.1.0+beta12 on 4.12 had its build status changed: not available to internal failure
• jenga.112.17.00 on 4.02 had its build status changed: partially failing to internal failure
• jenga.113.00.00 on 4.02 had its build status changed: partially failing to internal failure
• jenga.v0.9.0 on 4.03 had its build status changed: partially failing to internal failure
• jhupllib.0.1 on 4.03 had its build status changed: passing to internal failure
• jhupllib.0.1.1 on 4.06 had its build status changed: passing to internal failure
• jingoo.1.2.10 on 4.02 had its build status changed: passing to internal failure
• jingoo.1.2.11 on 4.04 had its build status changed: passing to internal failure
• jingoo.1.2.16 on 4.13 had its build status changed: passing to internal failure
• jingoo.1.2.18 on 4.07 had its build status changed: passing to internal failure
• jingoo.1.2.19 on 4.10 had its build status changed: passing to internal failure
• jingoo.1.2.21 on 4.04 had its build status changed: passing to internal failure
• jingoo.1.3.0-1 on 4.03 had its build status changed: not available to internal failure
• jingoo.1.3.1 on 4.09 had its build status changed: passing to internal failure
• jingoo.1.3.2 on 4.02 had its build status changed: not available to internal failure
• mirage-www.1.1.0 on 4.02 had its build status changed: partially failing to internal failure
• misuja.0.0.0 on 4.03 had its build status changed: passing to internal failure
• misuja.0.0.0 on 4.06 had its build status changed: passing to internal failure
• misuja.0.0.0 on 4.07 had its build status changed: passing to internal failure
• misuja.0.0.0 on 4.08 had its build status changed: passing to internal failure
• misuja.0.0.0 on 4.10 had its build status changed: passing to internal failure
• misuja.0.0.0 on 4.12 had its build status changed: passing to internal failure
• misuja.0.0.0 on 4.13 had its build status changed: passing to internal failure
• misuja.0.0.0 on 4.14 had its build status changed: passing to internal failure
• mpp.0.1.0 on 4.05 had its build status changed: passing to internal failure
• mpp.0.1.1 on 4.02 had its build status changed: passing to internal failure
• mpp.0.1.1 on 4.03 had its build status changed: passing to internal failure
• mpp.0.1.1 on 4.04 had its build status changed: passing to internal failure
• mpp.0.1.1 on 4.05 had its build status changed: passing to internal failure
• mpp.0.1.2 on 4.02 had its build status changed: passing to internal failure
• mpp.0.1.2 on 4.03 had its build status changed: passing to internal failure
• mpp.0.1.2 on 4.04 had its build status changed: passing to internal failure
• mpp.0.1.2 on 4.05 had its build status changed: passing to internal failure
• mpp.0.1.3 on 4.02 had its build status changed: passing to internal failure
• mpp.0.1.3 on 4.03 had its build status changed: passing to internal failure
• mpp.0.1.3 on 4.04 had its build status changed: passing to internal failure
• mpp.0.1.3 on 4.05 had its build status changed: passing to internal failure
• mpp.0.1.4 on 4.02 had its build status changed: passing to internal failure
• mpp.0.1.4 on 4.03 had its build status changed: passing to internal failure
• mpp.0.1.4 on 4.05 had its build status changed: passing to internal failure
• mpp.0.1.5 on 4.02 had its build status changed: passing to internal failure
• mpp.0.1.5 on 4.03 had its build status changed: passing to internal failure
• mpp.0.1.5 on 4.04 had its build status changed: passing to internal failure
• mpp.0.1.5 on 4.05 had its build status changed: passing to internal failure
• mpp.0.1.7 on 4.02 had its build status changed: passing to internal failure
• mpp.0.1.7 on 4.03 had its build status changed: passing to internal failure
• mpp.0.1.7 on 4.04 had its build status changed: passing to internal failure
• mpp.0.1.8 on 4.05 had its build status changed: passing to internal failure
• mpp.0.2.0 on 4.02 had its build status changed: passing to internal failure
• mpp.0.2.0 on 4.03 had its build status changed: passing to internal failure
• mpp.0.2.0 on 4.04 had its build status changed: passing to internal failure
• mpp.0.2.0 on 4.05 had its build status changed: passing to internal failure
• mpp.0.2.1 on 4.02 had its build status changed: passing to internal failure
• mpp.0.2.1 on 4.03 had its build status changed: passing to internal failure
• mpp.0.2.1 on 4.04 had its build status changed: passing to internal failure
• mpp.0.3.0 on 4.02 had its build status changed: passing to internal failure
• mpp.0.3.0 on 4.03 had its build status changed: passing to internal failure
• mpp.0.3.0 on 4.04 had its build status changed: passing to internal failure
• ocf.0.1.0 on 4.02 had its build status changed: failing to internal failure
• ocf.0.3.0 on 4.02 had its build status changed: failing to internal failure
• odig.0.0.1 on 4.05 had its build status changed: passing to internal failure
• odnnr.2.0.0 on 4.13 had its build status changed: not available to internal failure
• ojs-base.0.1.0 on 4.02 had its build status changed: partially failing to internal failure
• omd.0.2 on 4.03 had its build status changed: passing to internal failure
• omd.0.2 on 4.04 had its build status changed: passing to internal failure
• omd.0.2 on 4.05 had its build status changed: passing to internal failure
• omd.0.3 on 4.04 had its build status changed: passing to internal failure
• omd.0.3 on 4.05 had its build status changed: passing to internal failure
• omd.0.4 on 4.02 had its build status changed: passing to internal failure
• omd.0.4 on 4.03 had its build status changed: passing to internal failure
• omd.0.4 on 4.04 had its build status changed: passing to internal failure
• omd.0.5 on 4.02 had its build status changed: passing to internal failure
• omd.0.5 on 4.04 had its build status changed: passing to internal failure
• omd.0.5 on 4.05 had its build status changed: passing to internal failure
• omd.0.5.4 on 4.03 had its build status changed: passing to internal failure
• omd.0.5.4 on 4.04 had its build status changed: passing to internal failure
• omd.0.5.4 on 4.05 had its build status changed: passing to internal failure
• omd.0.5.5 on 4.04 had its build status changed: passing to internal failure
• omd.0.5.5 on 4.05 had its build status changed: passing to internal failure
• omd.0.6.0 on 4.02 had its build status changed: passing to internal failure
• omd.0.6.0 on 4.03 had its build status changed: passing to internal failure
• omd.0.6.0 on 4.04 had its build status changed: passing to internal failure
• omd.0.6.0 on 4.05 had its build status changed: passing to internal failure
• omd.0.6.1 on 4.02 had its build status changed: passing to internal failure
• omd.0.6.1 on 4.03 had its build status changed: passing to internal failure
• omd.0.6.1 on 4.04 had its build status changed: passing to internal failure
• omd.0.6.1 on 4.05 had its build status changed: passing to internal failure
• omd.0.6.2 on 4.02 had its build status changed: passing to internal failure
• omd.0.6.2 on 4.03 had its build status changed: passing to internal failure
• omd.0.6.2 on 4.04 had its build status changed: passing to internal failure
• omd.0.6.2 on 4.05 had its build status changed: passing to internal failure
• omd.0.6.3 on 4.02 had its build status changed: passing to internal failure
• omd.0.6.3 on 4.03 had its build status changed: passing to internal failure
• omd.0.6.3 on 4.05 had its build status changed: passing to internal failure
• omd.0.6.4 on 4.02 had its build status changed: passing to internal failure
• omd.0.6.4 on 4.03 had its build status changed: passing to internal failure
• omd.0.6.4 on 4.04 had its build status changed: passing to internal failure
• omd.0.6.4 on 4.05 had its build status changed: passing to internal failure
• omd.0.6.5 on 4.02 had its build status changed: passing to internal failure
• omd.0.6.5 on 4.03 had its build status changed: passing to internal failure
• omd.0.6.5 on 4.04 had its build status changed: passing to internal failure
• omd.0.6.5 on 4.05 had its build status changed: passing to internal failure
• omd.0.7.0 on 4.02 had its build status changed: passing to internal failure
• omd.0.7.0 on 4.03 had its build status changed: passing to internal failure
• omd.0.7.0 on 4.04 had its build status changed: passing to internal failure
• omd.0.7.1 on 4.02 had its build status changed: passing to internal failure
• omd.0.7.1 on 4.03 had its build status changed: passing to internal failure
• omd.0.7.1 on 4.04 had its build status changed: passing to internal failure
• omd.0.7.1 on 4.05 had its build status changed: passing to internal failure
• omd.0.7.2 on 4.02 had its build status changed: passing to internal failure
• omd.0.7.2 on 4.03 had its build status changed: passing to internal failure
• omd.0.7.2 on 4.04 had its build status changed: passing to internal failure
• omd.0.7.2 on 4.05 had its build status changed: passing to internal failure
• omd.0.7.3 on 4.03 had its build status changed: passing to internal failure
• omd.0.7.3 on 4.04 had its build status changed: passing to internal failure
• omd.0.7.3 on 4.05 had its build status changed: passing to internal failure
• omd.0.7.4 on 4.02 had its build status changed: passing to internal failure
• omd.0.7.4 on 4.03 had its build status changed: passing to internal failure
• omd.0.7.4 on 4.04 had its build status changed: passing to internal failure
• omd.0.7.4 on 4.05 had its build status changed: passing to internal failure
• omd.0.7.5 on 4.02 had its build status changed: passing to internal failure
• omd.0.7.5 on 4.03 had its build status changed: passing to internal failure
• omd.0.7.5 on 4.04 had its build status changed: passing to internal failure
• omd.0.7.5 on 4.05 had its build status changed: passing to internal failure
• omd.0.8.0 on 4.02 had its build status changed: passing to internal failure
• omd.0.8.0 on 4.03 had its build status changed: passing to internal failure
• omd.0.8.0 on 4.04 had its build status changed: passing to internal failure
• omd.0.8.0 on 4.05 had its build status changed: passing to internal failure
• omd.0.8.1 on 4.02 had its build status changed: passing to internal failure
• omd.0.8.1 on 4.04 had its build status changed: passing to internal failure
• omd.0.8.1 on 4.05 had its build status changed: passing to internal failure
• omd.0.8.2 on 4.02 had its build status changed: passing to internal failure
• omd.0.8.2 on 4.04 had its build status changed: passing to internal failure
• omd.0.9.0 on 4.02 had its build status changed: passing to internal failure
• omd.0.9.0 on 4.03 had its build status changed: passing to internal failure
• omd.0.9.0 on 4.04 had its build status changed: passing to internal failure
• omd.0.9.0 on 4.05 had its build status changed: passing to internal failure
• omd.0.9.1 on 4.02 had its build status changed: passing to internal failure
• omd.0.9.1 on 4.03 had its build status changed: passing to internal failure
• omd.0.9.1 on 4.04 had its build status changed: passing to internal failure
• omd.0.9.1 on 4.05 had its build status changed: passing to internal failure
• omd.0.9.3 on 4.02 had its build status changed: passing to internal failure
• omd.0.9.3 on 4.04 had its build status changed: passing to internal failure
• omd.0.9.3 on 4.05 had its build status changed: passing to internal failure
• omd.0.9.4 on 4.02 had its build status changed: passing to internal failure
• omd.0.9.4 on 4.03 had its build status changed: passing to internal failure
• omd.0.9.4 on 4.04 had its build status changed: passing to internal failure
• omd.0.9.4 on 4.05 had its build status changed: passing to internal failure
• omd.0.9.5 on 4.02 had its build status changed: passing to internal failure
• omd.0.9.5 on 4.03 had its build status changed: passing to internal failure
• omd.0.9.5 on 4.05 had its build status changed: passing to internal failure
• omd.0.9.6 on 4.02 had its build status changed: passing to internal failure
• omd.0.9.6 on 4.03 had its build status changed: passing to internal failure
• omd.0.9.6 on 4.04 had its build status changed: passing to internal failure
• omd.0.9.7 on 4.02 had its build status changed: passing to internal failure
• omd.0.9.7 on 4.03 had its build status changed: passing to internal failure
• omd.0.9.7 on 4.04 had its build status changed: passing to internal failure
• omd.0.9.7 on 4.05 had its build status changed: passing to internal failure
• omd.1.0.0 on 4.03 had its build status changed: passing to internal failure
• omd.1.0.0 on 4.05 had its build status changed: passing to internal failure
• omd.1.0.1 on 4.02 had its build status changed: passing to internal failure
• omd.1.0.1 on 4.03 had its build status changed: passing to internal failure
• omd.1.0.1 on 4.04 had its build status changed: passing to internal failure
• omd.1.0.1 on 4.05 had its build status changed: passing to internal failure
• omd.1.1.0 on 4.02 had its build status changed: passing to internal failure
• omd.1.1.0 on 4.03 had its build status changed: passing to internal failure
• omd.1.1.0 on 4.04 had its build status changed: passing to internal failure
• omd.1.1.0 on 4.05 had its build status changed: passing to internal failure
• omd.1.1.1 on 4.03 had its build status changed: passing to internal failure
• omd.1.1.1 on 4.04 had its build status changed: passing to internal failure
• omd.1.1.1 on 4.05 had its build status changed: passing to internal failure
• omd.1.1.2 on 4.02 had its build status changed: passing to internal failure
• omd.1.1.2 on 4.03 had its build status changed: passing to internal failure
• omd.1.1.2 on 4.04 had its build status changed: passing to internal failure
• omd.1.1.2 on 4.05 had its build status changed: passing to internal failure
• omd.1.1.3 on 4.02 had its build status changed: passing to internal failure
• omd.1.1.3 on 4.03 had its build status changed: passing to internal failure
• omd.1.1.3 on 4.04 had its build status changed: passing to internal failure
• omd.1.1.3 on 4.05 had its build status changed: passing to internal failure
• omd.1.2.0 on 4.02 had its build status changed: passing to internal failure
• omd.1.2.0 on 4.04 had its build status changed: passing to internal failure
• omd.1.2.0 on 4.05 had its build status changed: passing to internal failure
• omd.1.2.1 on 4.02 had its build status changed: passing to internal failure
• omd.1.2.1 on 4.04 had its build status changed: passing to internal failure
• omd.1.2.1 on 4.05 had its build status changed: passing to internal failure
• omd.1.2.2 on 4.02 had its build status changed: passing to internal failure
• omd.1.2.2 on 4.03 had its build status changed: passing to internal failure
• omd.1.2.2 on 4.04 had its build status changed: passing to internal failure
• omd.1.2.2 on 4.05 had its build status changed: passing to internal failure
• omd.1.2.3 on 4.02 had its build status changed: passing to internal failure
• omd.1.2.3 on 4.03 had its build status changed: passing to internal failure
• omd.1.2.3 on 4.04 had its build status changed: passing to internal failure
• omd.1.2.3 on 4.05 had its build status changed: passing to internal failure
• omd.1.2.4 on 4.02 had its build status changed: passing to internal failure
• omd.1.2.4 on 4.03 had its build status changed: passing to internal failure
• omd.1.2.4 on 4.04 had its build status changed: passing to internal failure
• omd.1.2.4 on 4.05 had its build status changed: passing to internal failure
• omd.1.2.5 on 4.02 had its build status changed: passing to internal failure
• omd.1.2.5 on 4.04 had its build status changed: passing to internal failure
• omd.1.2.5 on 4.05 had its build status changed: passing to internal failure
• omd.1.2.6 on 4.02 had its build status changed: passing to internal failure
• omd.1.2.6 on 4.05 had its build status changed: passing to internal failure
• omd.1.3.0 on 4.02 had its build status changed: passing to internal failure
• omd.1.3.0 on 4.03 had its build status changed: passing to internal failure
• omd.1.3.0 on 4.05 had its build status changed: passing to internal failure
• opam-lib.1.2.0 on 4.02 had its build status changed: passing to internal failure
• opam-lib.1.2.1 on 4.05 had its build status changed: passing to internal failure
• opam-publish.0.2.1 on 4.02 had its build status changed: partially failing to internal failure
• opam-query.1.0 on 4.05 had its build status changed: passing to internal failure
• opam-query.1.1 on 4.05 had its build status changed: passing to internal failure
• opam-query.1.2 on 4.05 had its build status changed: passing to internal failure
• opam-sync-github-prs.1.0.0 on 4.04 had its build status changed: not available to internal failure
• opam2web.1.4.0 on 4.04 had its build status changed: failing to internal failure
• opamfu.0.1.3 on 4.05 had its build status changed: passing to internal failure
• opium.0.6.1 on 4.02 had its build status changed: partially failing to internal failure
• orewa.0.1.1 on 4.07 had its build status changed: passing to internal failure
• orewa.0.2.1 on 4.05 had its build status changed: passing to internal failure
• orm.0.7.0 on 4.13 had its build status changed: passing to internal failure
• orsetto.1.0.2 on 4.08 had its build status changed: passing to internal failure
• orsvm_e1071.3.0.2 on 4.08 had its build status changed: passing to internal failure
• osbx.1.1.1 on 4.08 had its build status changed: not available to internal failure
• osbx.1.2.2 on 4.03 had its build status changed: passing to internal failure
• pds.3.0.4 on 4.08 had its build status changed: passing to internal failure
• pds.5.16 on 4.13 had its build status changed: passing to internal failure
• proverif.1.96pl1 on 4.05 had its build status changed: passing to internal failure
• proverif.1.97 on 4.02 had its build status changed: passing to internal failure
• proverif.1.97 on 4.04 had its build status changed: passing to internal failure
• proverif.1.97 on 4.05 had its build status changed: passing to internal failure
• proverif.1.97pl1 on 4.04 had its build status changed: passing to internal failure
• proverif.1.97pl1 on 4.05 had its build status changed: passing to internal failure
• proverif.1.97pl3 on 4.02 had its build status changed: passing to internal failure
• proverif.1.97pl3 on 4.03 had its build status changed: passing to internal failure
• proverif.1.97pl3 on 4.04 had its build status changed: passing to internal failure
• proverif.1.97pl3 on 4.07 had its build status changed: passing to internal failure
• proverif.1.97pl3 on 4.11 had its build status changed: passing to internal failure
• proverif.1.97pl3 on 4.12 had its build status changed: passing to internal failure
• proverif.1.97pl3 on 4.14 had its build status changed: passing to internal failure
• proverif.1.98 on 4.02 had its build status changed: passing to internal failure
• proverif.1.98 on 4.03 had its build status changed: passing to internal failure
• proverif.1.98 on 4.08 had its build status changed: passing to internal failure
• proverif.1.98 on 4.09 had its build status changed: passing to internal failure
• proverif.1.98 on 4.10 had its build status changed: passing to internal failure
• proverif.1.98 on 4.11 had its build status changed: passing to internal failure
• proverif.1.98 on 4.12 had its build status changed: passing to internal failure
• proverif.1.98pl1 on 4.02 had its build status changed: passing to internal failure
• proverif.1.98pl1 on 4.05 had its build status changed: passing to internal failure
• proverif.1.98pl1 on 4.06 had its build status changed: passing to internal failure
• proverif.1.98pl1 on 4.07 had its build status changed: passing to internal failure
• proverif.1.98pl1 on 4.10 had its build status changed: passing to internal failure
• proverif.1.98pl1 on 4.11 had its build status changed: passing to internal failure
• proverif.1.98pl1 on 4.12 had its build status changed: passing to internal failure
• publish.0.3.3 on 4.05 had its build status changed: passing to internal failure
• qfs.0.12 on 4.14 had its build status changed: not available to internal failure
• rdf.0.9.0 on 4.02 had its build status changed: passing to internal failure
• reparse.1.0.2 on 4.12 had its build status changed: passing to internal failure
• river.0.1.2 on 4.05 had its build status changed: passing to internal failure
• rml.1.09.04 on 4.03 had its build status changed: passing to internal failure
• sawja.1.5 on 4.02 had its build status changed: failing to internal failure
• sawja.1.5 on 4.04 had its build status changed: failing to internal failure
• sawja.1.5.2 on 4.02 had its build status changed: passing to internal failure
• sawja.1.5.2 on 4.05 had its build status changed: passing to internal failure
• sawja.1.5.3 on 4.02 had its build status changed: passing to internal failure
• sawja.1.5.3 on 4.03 had its build status changed: passing to internal failure
• sawja.1.5.3 on 4.04 had its build status changed: passing to internal failure
• sawja.1.5.4 on 4.03 had its build status changed: passing to internal failure
• sawja.1.5.4 on 4.04 had its build status changed: passing to internal failure
• sawja.1.5.4 on 4.05 had its build status changed: passing to internal failure
• sawja.1.5.4 on 4.10 had its build status changed: passing to internal failure
• solo5-elftool.0.1.0 on 4.08 is now installable. Current state is: internal failure
• solo5-elftool.0.1.0 on 4.09 is now installable. Current state is: internal failure
• solo5-elftool.0.1.0 on 4.10 is now installable. Current state is: internal failure
• solo5-elftool.0.1.0 on 4.11 is now installable. Current state is: internal failure
• solo5-elftool.0.1.0 on 4.12 is now installable. Current state is: internal failure
• solo5-elftool.0.1.0 on 4.13 is now installable. Current state is: internal failure
• solo5-elftool.0.1.0 on 4.14 is now installable. Current state is: internal failure
• spotify-web-api.0.2.1 on 4.08 had its build status changed: passing to internal failure
• stog-writing.0.13.0 on 4.02 had its build status changed: partially failing to internal failure
• stog-writing.0.13.0 on 4.03 had its build status changed: partially failing to internal failure
• stog-writing.0.13.0 on 4.04 had its build status changed: partially failing to internal failure
• stog-writing.0.13.0 on 4.05 had its build status changed: partially failing to internal failure
• stog.0.13.0 on 4.02 had its build status changed: failing to internal failure
• stog.0.13.0 on 4.03 had its build status changed: failing to internal failure
• stog.0.13.0 on 4.04 had its build status changed: failing to internal failure
• stog.0.13.0 on 4.05 had its build status changed: failing to internal failure
• stone.0.3.1 on 4.02 had its build status changed: passing to internal failure
• stone.0.3.1 on 4.03 had its build status changed: passing to internal failure
• stone.0.3.1 on 4.04 had its build status changed: passing to internal failure
• stone.0.3.1 on 4.05 had its build status changed: passing to internal failure
• taglog.0.1.0 on 4.02 had its build status changed: partially failing to internal failure
• taglog.0.2.0 on 4.02 had its build status changed: partially failing to internal failure
• taglog.0.2.0 on 4.03 had its build status changed: passing to internal failure
• taglog.0.2.0 on 4.04 had its build status changed: passing to internal failure
• taglog.0.2.0 on 4.05 had its build status changed: passing to internal failure
• taglog.0.2.0 on 4.06 had its build status changed: passing to internal failure
• taglog.0.2.0 on 4.07 had its build status changed: passing to internal failure
• taglog.0.3.0 on 4.02 had its build status changed: partially failing to internal failure
• taglog.0.3.0 on 4.03 had its build status changed: passing to internal failure
• taglog.0.3.0 on 4.04 had its build status changed: passing to internal failure
• taglog.0.3.0 on 4.05 had its build status changed: passing to internal failure
• taglog.0.3.0 on 4.06 had its build status changed: passing to internal failure
• taglog.0.3.0 on 4.07 had its build status changed: passing to internal failure
• tezos-client-base-unix.11.0 on 4.14 had its build status changed: not available to internal failure
• tezos-client-demo-counter.9.7 on 4.10 had its build status changed: partially failing to internal failure
• tezos-client-genesis-carthagenet.8.2 on 4.10 had its build status changed: partially failing to internal failure
• tezos-client.9.3 on 4.10 had its build status changed: partially failing to internal failure
• tezos-codec.11.0 on 4.14 had its build status changed: not available to internal failure
• tezos-codec.7.0 on 4.09 had its build status changed: passing to internal failure
• tezos-codec.8.3 on 4.11 had its build status changed: partially failing to internal failure
• tezos-codec.9.4 on 4.08 had its build status changed: partially failing to internal failure
• tezos-context.10.2 on 4.11 had its build status changed: passing to internal failure
• tezos-crypto.10.2 on 4.10 had its build status changed: passing to internal failure
• tezos-crypto.7.3 on 4.12 had its build status changed: passing to internal failure
• tezos-crypto.8.3 on 4.09 had its build status changed: partially failing to internal failure
• tezos-crypto.9.4 on 4.10 had its build status changed: partially failing to internal failure
• tezos-embedded-protocol-000-Ps9mPmXa.7.1 on 4.08 had its build status changed: not available to internal failure
• tezos-embedded-protocol-000-Ps9mPmXa.7.3 on 4.02 had its build status changed: not available to internal failure
• tezos-embedded-protocol-000-Ps9mPmXa.7.4 on 4.10 had its build status changed: not available to internal failure
• tezos-embedded-protocol-002-PsYLVpVv.8.3 on 4.09 had its build status changed: partially failing to internal failure
• tezos-embedded-protocol-003-PsddFKi3.10.2 on 4.10 had its build status changed: passing to internal failure
• tezos-embedded-protocol-003-PsddFKi3.8.0 on 4.09 had its build status changed: partially failing to internal failure
• tezos-embedded-protocol-004-Pt24m4xi.8.1 on 4.09 had its build status changed: partially failing to internal failure
• tezos-embedded-protocol-005-PsBABY5H.9.7 on 4.10 had its build status changed: partially failing to internal failure
• tezos-embedded-protocol-005-PsBabyM1.7.4 on 4.09 had its build status changed: passing to internal failure
• tezos-embedded-protocol-005-PsBabyM1.8.1 on 4.04 had its build status changed: not available to internal failure
• tezos-embedded-protocol-005-PsBabyM1.8.2 on 4.13 had its build status changed: not available to internal failure
• tezos-embedded-protocol-005-PsBabyM1.9.0 on 4.12 had its build status changed: not available to internal failure
• tezos-embedded-protocol-005-PsBabyM1.9.2 on 4.06 had its build status changed: not available to internal failure
• tezos-embedded-protocol-005-PsBabyM1.9.4 on 4.02 had its build status changed: not available to internal failure
• tezos-embedded-protocol-005-PsBabyM1.9.4 on 4.14 had its build status changed: not available to internal failure
• tezos-embedded-protocol-006-PsCARTHA.7.3 on 4.10 had its build status changed: not available to internal failure
• tezos-embedded-protocol-006-PsCARTHA.8.0 on 4.04 had its build status changed: not available to internal failure
• tezos-embedded-protocol-006-PsCARTHA.8.1 on 4.11 had its build status changed: not available to internal failure
• tezos-embedded-protocol-006-PsCARTHA.8.3 on 4.08 had its build status changed: not available to internal failure
• tezos-embedded-protocol-006-PsCARTHA.9.1 on 4.03 had its build status changed: not available to internal failure
• tezos-mockup-proxy.11.0 on 4.14 had its build status changed: not available to internal failure
• tezos-mockup-registration.11.0 on 4.14 had its build status changed: not available to internal failure
• tezos-mockup-registration.8.0 on 4.11 had its build status changed: partially failing to internal failure
• tezos-mockup-registration.9.1 on 4.08 had its build status changed: passing to internal failure
• tezos-mockup.10.2 on 4.10 had its build status changed: passing to internal failure
• tezos-mockup.9.0 on 4.09 had its build status changed: passing to internal failure
• tezos-node.8.0 on 4.09 had its build status changed: partially failing to internal failure
• tezos-p2p-services.10.2 on 4.08 had its build status changed: passing to internal failure
• tezos-p2p-services.11.0 on 4.14 had its build status changed: not available to internal failure
• tezos-p2p-services.8.0 on 4.04 had its build status changed: not available to internal failure
• tezos-protocol-environment-structs.9.4 on 4.09 had its build status changed: partially failing to internal failure
• tezos-protocol-plugin-007-PsDELPH1.9.0 on 4.10 had its build status changed: passing to internal failure
• tezos-protocol-updater.11.0 on 4.12 had its build status changed: passing to internal failure
• tezos-protocol-updater.9.1 on 4.10 had its build status changed: passing to internal failure
• tezos-proxy.9.3 on 4.10 had its build status changed: partially failing to internal failure
• tezos-requester.8.2 on 4.11 had its build status changed: partially failing to internal failure
• tezos-requester.9.2 on 4.08 had its build status changed: partially failing to internal failure
• tezos-rpc-http-client-unix.7.0 on 4.02 had its build status changed: not available to internal failure
• tezos-rpc-http-client-unix.7.1 on 4.12 had its build status changed: passing to internal failure
• tezos-rpc-http-client-unix.7.3 on 4.14 had its build status changed: not available to internal failure
• tezos-signer.11.0 on 4.14 had its build status changed: not available to internal failure
• tezos-signer.8.1 on 4.10 had its build status changed: partially failing to internal failure
• tezos-stdlib.8.2 on 4.10 had its build status changed: passing to internal failure
• tezos-stdlib.9.0 on 4.11 had its build status changed: passing to internal failure
• tezos-stdlib.9.7 on 4.11 had its build status changed: passing to internal failure
• tezos-storage.7.1 on 4.06 had its build status changed: not available to internal failure
• tezos-storage.7.3 on 4.02 had its build status changed: not available to internal failure
• torch.0.12 on 4.10 had its build status changed: passing to internal failure
• torch.0.2 on 4.14 had its build status changed: not available to internal failure
• torch.0.3 on 4.14 had its build status changed: not available to internal failure
• uwt.0.3.3 on 4.09 had its build status changed: passing to internal failure
• vecosek.0.0.0 on 4.03 had its build status changed: passing to internal failure
• vecosek.0.0.0 on 4.08 had its build status changed: passing to internal failure
• vecosek.0.0.0 on 4.10 had its build status changed: passing to internal failure
• vecosek.0.0.0 on 4.12 had its build status changed: passing to internal failure
• vecosek.0.0.0 on 4.13 had its build status changed: passing to internal failure
• vimebac.0.0.0 on 4.03 had its build status changed: passing to internal failure
• vimebac.0.0.0 on 4.04 had its build status changed: passing to internal failure

Packages now passing:

• 0install-gtk.2.15.2 on 4.11 had its build status changed: internal failure to passing
• 0install-gtk.2.15.2 on 4.14 had its build status changed: not available to passing
• 0install-gtk.2.16 on 4.06 had its build status changed: internal failure to passing
• 0install-gtk.2.16 on 4.07 had its build status changed: internal failure to passing
• 0install-gtk.2.16 on 4.11 had its build status changed: internal failure to passing
• 0install-gtk.2.16 on 4.13 had its build status changed: internal failure to passing
• 0install-gtk.2.16 on 4.14 had its build status changed: not available to passing
• 0install-gtk.2.17 on 4.08 had its build status changed: internal failure to passing
• 0install-gtk.2.17 on 4.12 had its build status changed: internal failure to passing
• 0install-gtk.2.17 on 4.14 had its build status changed: not available to passing
• 0install.2.12.3 on 4.03 had its build status changed: internal failure to passing
• 0install.2.12.3 on 4.06 had its build status changed: internal failure to passing
• 0install.2.14 on 4.06 had its build status changed: internal failure to passing
• 0install.2.14.1 on 4.06 had its build status changed: internal failure to passing
• 0install.2.14.1 on 4.08 had its build status changed: internal failure to passing
• 0install.2.14.1 on 4.10 had its build status changed: internal failure to passing
• 0install.2.15.1 on 4.08 had its build status changed: internal failure to passing
• 0install.2.15.1 on 4.12 had its build status changed: internal failure to passing
• 0install.2.15.1 on 4.14 had its build status changed: failing to passing
• 0install.2.15.2 on 4.05 had its build status changed: internal failure to passing
• 0install.2.15.2 on 4.10 had its build status changed: internal failure to passing
• 0install.2.15.2 on 4.14 had its build status changed: internal failure to passing
• 0install.2.16 on 4.09 had its build status changed: internal failure to passing
• 0install.2.16 on 4.12 had its build status changed: internal failure to passing
• 0install.2.16 on 4.14 had its build status changed: not available to passing
• 0install.2.17 on 4.11 had its build status changed: internal failure to passing
• 0install.2.17 on 4.13 had its build status changed: internal failure to passing
• 0install.2.17 on 4.14 had its build status changed: not available to passing
• DAGaml.0.01 on 4.12 had its build status changed: failing to passing
• DrawGrammar.0.1.0 on 4.03 had its build status changed: partially failing to passing
• DrawGrammar.0.2.0 on 4.05 had its build status changed: partially failing to passing
• OCanren-ppx.0.2.0 on 4.14 had its build status changed: not available to passing
• SZXX.0.1.0 on 4.14 had its build status changed: not available to passing
• SZXX.1.0.0 on 4.14 had its build status changed: not available to passing
• SZXX.1.1.0 on 4.14 had its build status changed: not available to passing
• SZXX.2.0.0 on 4.14 had its build status changed: not available to passing
• accessor.v0.14.1 on 4.14 had its build status changed: not available to passing
• accessor_base.v0.14.1 on 4.14 had its build status changed: not available to passing
• acgtk.1.5.0 on 4.14 had its build status changed: not available to passing
• acpc.1.1.1 on 4.13 had its build status changed: not available to passing
• acpc.1.2.3 on 4.13 had its build status changed: not available to passing
• albatross.1.0.1 on 4.14 had its build status changed: not available to passing
• albatross.1.1.0 on 4.14 had its build status changed: not available to passing
• albatross.1.1.1 on 4.14 had its build status changed: not available to passing
• albatross.1.2.0 on 4.14 had its build status changed: not available to passing
• albatross.1.3.0 on 4.14 had its build status changed: not available to passing
• albatross.1.3.1 on 4.14 had its build status changed: not available to passing
• alcotest-async.0.8.2 on 4.14 had its build status changed: not available to passing
• alcotest-async.0.8.5 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.0.0 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.0.1 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.1.0 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.2.0 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.2.1 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.2.2 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.2.3 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.3.0 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.4.0 on 4.14 had its build status changed: not available to passing
• alcotest-async.1.5.0 on 4.14 had its build status changed: not available to passing
• alg_structs.0.1.3 on 4.14 had its build status changed: not available to passing
• alg_structs_qcheck.0.1.3 on 4.14 had its build status changed: not available to passing
• amqp-client-async.2.0.3 on 4.14 had its build status changed: not available to passing
• amqp-client-async.2.1.0 on 4.14 had its build status changed: not available to passing
• amqp-client-async.2.2.0 on 4.14 had its build status changed: not available to passing
• amqp-client-async.2.2.1 on 4.14 had its build status changed: not available to passing
• amqp-client-async.2.2.2 on 4.14 had its build status changed: not available to passing
• anders.0.12.1 on 4.10 is now installable. Current state is: passing
• anders.0.12.1 on 4.11 is now installable. Current state is: passing
• anders.0.12.1 on 4.12 is now installable. Current state is: passing
• anders.0.12.1 on 4.13 is now installable. Current state is: passing
• anders.0.12.1 on 4.14 is now installable. Current state is: passing
• angstrom-async.0.10.0 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.11.0 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.11.1 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.11.2 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.12.1 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.13.0 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.14.0 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.14.1 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.15.0 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.7.0 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.8.0 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.8.1 on 4.14 had its build status changed: not available to passing
• angstrom-async.0.9.0 on 4.14 had its build status changed: not available to passing
• archetype.0.1.10 on 4.14 had its build status changed: not available to passing
• archetype.0.1.11 on 4.14 had its build status changed: not available to passing
• archetype.0.1.12 on 4.14 had its build status changed: not available to passing
• archetype.0.1.13 on 4.14 had its build status changed: not available to passing
• archetype.0.1.14 on 4.14 had its build status changed: not available to passing
• archetype.0.1.3 on 4.14 had its build status changed: not available to passing
• archetype.0.1.4 on 4.14 had its build status changed: not available to passing
• archetype.0.1.5 on 4.14 had its build status changed: not available to passing
• archetype.0.1.6 on 4.14 had its build status changed: not available to passing
• archetype.0.1.8 on 4.14 had its build status changed: not available to passing
• archetype.0.1.9 on 4.14 had its build status changed: not available to passing
• archetype.1.0.0 on 4.14 had its build status changed: not available to passing
• archetype.1.1.0 on 4.14 had its build status changed: not available to passing
• archetype.1.1.1 on 4.14 had its build status changed: not available to passing
• archetype.1.1.2 on 4.14 had its build status changed: not available to passing
• archetype.1.2.0 on 4.14 had its build status changed: not available to passing
• archetype.1.2.1 on 4.14 had its build status changed: not available to passing
• archetype.1.2.11 on 4.08 is now installable. Current state is: passing
• archetype.1.2.11 on 4.09 is now installable. Current state is: passing
• archetype.1.2.11 on 4.10 is now installable. Current state is: passing
• archetype.1.2.11 on 4.11 is now installable. Current state is: passing
• archetype.1.2.11 on 4.12 is now installable. Current state is: passing
• archetype.1.2.11 on 4.13 is now installable. Current state is: passing
• archetype.1.2.2 on 4.14 had its build status changed: not available to passing
• archetype.1.2.3 on 4.14 had its build status changed: not available to passing
• archetype.1.2.4 on 4.14 had its build status changed: not available to passing
• archetype.1.2.5 on 4.14 had its build status changed: not available to passing
• archetype.1.2.6 on 4.14 had its build status changed: not available to passing
• archi-async.0.1.0 on 4.14 had its build status changed: not available to passing
• arp-mirage.1.0.0 on 4.14 had its build status changed: not available to passing
• arp-mirage.2.0.0 on 4.14 had its build status changed: not available to passing
• arp-mirage.2.1.0 on 4.14 had its build status changed: not available to passing
• arp-mirage.2.2.0 on 4.14 had its build status changed: not available to passing
• arp-mirage.2.2.1 on 4.14 had its build status changed: not available to passing
• arp.0.2.1 on 4.14 had its build status changed: not available to passing
• arp.0.2.2 on 4.14 had its build status changed: not available to passing
• arp.2.3.1 on 4.14 had its build status changed: not available to passing
• arp.2.3.2 on 4.14 had its build status changed: not available to passing
• arp.3.0.0 on 4.08 is now installable. Current state is: passing
• arp.3.0.0 on 4.09 is now installable. Current state is: passing
• arp.3.0.0 on 4.10 is now installable. Current state is: passing
• arp.3.0.0 on 4.11 is now installable. Current state is: passing
• arp.3.0.0 on 4.12 is now installable. Current state is: passing
• arp.3.0.0 on 4.13 is now installable. Current state is: passing
• arp.3.0.0 on 4.14 is now installable. Current state is: passing
• ask-integrator.0.2.0 on 4.14 had its build status changed: not available to passing
• ask.0.2.0 on 4.14 had its build status changed: not available to passing
• async-uri.0.1 on 4.14 had its build status changed: not available to passing
• async-uri.0.2.1 on 4.14 had its build status changed: not available to passing
• async-uri.0.3.0 on 4.14 had its build status changed: not available to passing
• async.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_durable.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_extra.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_find.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_graphics.0.7.0 on 4.14 had its build status changed: not available to passing
• async_inotify.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_interactive.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_kernel.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_rpc_kernel.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_sendfile.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_shell.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_smtp.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_ssl.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_udp.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_unix.v0.14.0 on 4.14 had its build status changed: not available to passing
• async_websocket.v0.14.0 on 4.14 had its build status changed: not available to passing
• avro-compiler.0.1 on 4.08 is now installable. Current state is: passing
• avro-compiler.0.1 on 4.09 is now installable. Current state is: passing
• avro-compiler.0.1 on 4.10 is now installable. Current state is: passing
• avro-compiler.0.1 on 4.11 is now installable. Current state is: passing
• avro-compiler.0.1 on 4.12 is now installable. Current state is: passing
• avro-compiler.0.1 on 4.13 is now installable. Current state is: passing
• avro-compiler.0.1 on 4.14 is now installable. Current state is: passing
• avro.0.1 on 4.08 is now installable. Current state is: passing
• avro.0.1 on 4.09 is now installable. Current state is: passing
• avro.0.1 on 4.10 is now installable. Current state is: passing
• avro.0.1 on 4.11 is now installable. Current state is: passing
• avro.0.1 on 4.12 is now installable. Current state is: passing
• avro.0.1 on 4.13 is now installable. Current state is: passing
• avro.0.1 on 4.14 is now installable. Current state is: passing
• awa-lwt.0.0.1 on 4.14 had its build status changed: not available to passing
• awa-lwt.0.0.2 on 4.14 had its build status changed: not available to passing
• awa-lwt.0.0.3 on 4.14 had its build status changed: not available to passing
• awa-lwt.0.0.4 on 4.14 had its build status changed: not available to passing
• awa-lwt.0.0.5 on 4.08 is now installable. Current state is: passing
• awa-lwt.0.0.5 on 4.09 is now installable. Current state is: passing
• awa-lwt.0.0.5 on 4.10 is now installable. Current state is: passing
• awa-lwt.0.0.5 on 4.11 is now installable. Current state is: passing
• awa-lwt.0.0.5 on 4.12 is now installable. Current state is: passing
• awa-lwt.0.0.5 on 4.13 is now installable. Current state is: passing
• awa-lwt.0.0.5 on 4.14 is now installable. Current state is: passing
• awa-mirage.0.0.1 on 4.14 had its build status changed: not available to passing
• awa-mirage.0.0.2 on 4.14 had its build status changed: not available to passing
• awa-mirage.0.0.3 on 4.14 had its build status changed: not available to passing
• awa-mirage.0.0.4 on 4.14 had its build status changed: not available to passing
• awa-mirage.0.0.5 on 4.08 is now installable. Current state is: passing
• awa-mirage.0.0.5 on 4.09 is now installable. Current state is: passing
• awa-mirage.0.0.5 on 4.10 is now installable. Current state is: passing
• awa-mirage.0.0.5 on 4.11 is now installable. Current state is: passing
• awa-mirage.0.0.5 on 4.12 is now installable. Current state is: passing
• awa-mirage.0.0.5 on 4.13 is now installable. Current state is: passing
• awa-mirage.0.0.5 on 4.14 is now installable. Current state is: passing
• awa.0.0.1 on 4.14 had its build status changed: not available to passing
• awa.0.0.2 on 4.14 had its build status changed: not available to passing
• awa.0.0.3 on 4.14 had its build status changed: not available to passing
• awa.0.0.4 on 4.14 had its build status changed: not available to passing
• awa.0.0.5 on 4.08 is now installable. Current state is: passing
• awa.0.0.5 on 4.09 is now installable. Current state is: passing
• awa.0.0.5 on 4.10 is now installable. Current state is: passing
• awa.0.0.5 on 4.11 is now installable. Current state is: passing
• awa.0.0.5 on 4.12 is now installable. Current state is: passing
• awa.0.0.5 on 4.13 is now installable. Current state is: passing
• awa.0.0.5 on 4.14 is now installable. Current state is: passing
• aws-async.1.2 on 4.14 had its build status changed: not available to passing
• aws-autoscaling.0.1.0 on 4.14 had its build status changed: not available to passing
• aws-cloudformation.0.1.0 on 4.14 had its build status changed: not available to passing
• aws-cloudtrail.0.1.0 on 4.14 had its build status changed: not available to passing
• aws-ec2.0.1.0 on 4.14 had its build status changed: not available to passing
• aws-elasticloadbalancing.0.1.0 on 4.14 had its build status changed: not available to passing
• aws-lwt.1.2 on 4.14 had its build status changed: not available to passing
• aws-s3-async.4.4.0 on 4.14 had its build status changed: not available to passing
• aws-s3-async.4.4.1 on 4.14 had its build status changed: not available to passing
• aws-s3-async.4.5.1 on 4.14 had its build status changed: not available to passing
• aws-s3-lwt.4.4.0 on 4.14 had its build status changed: not available to passing
• aws-s3-lwt.4.4.1 on 4.14 had its build status changed: not available to passing
• aws-s3-lwt.4.5.1 on 4.14 had its build status changed: not available to passing
• aws-s3.4.4.0 on 4.14 had its build status changed: not available to passing
• aws-s3.4.4.1 on 4.14 had its build status changed: not available to passing
• aws-s3.4.5.1 on 4.14 had its build status changed: not available to passing
• aws-sdb.0.1.0 on 4.14 had its build status changed: not available to passing
• aws-ssm.0.1.0 on 4.14 had its build status changed: not available to passing
• aws-sts.0.1.0 on 4.14 had its build status changed: not available to passing
• aws.1.0.0 on 4.14 had its build status changed: not available to passing
• aws.1.0.1 on 4.14 had its build status changed: not available to passing
• aws.1.0.2 on 4.14 had its build status changed: not available to passing
• azblob-async.0.1.0 on 4.14 had its build status changed: not available to passing
• azblob.0.1.0 on 4.14 had its build status changed: not available to passing
• azure-cosmos-db.0.1.2 on 4.14 had its build status changed: not available to passing
• azure-cosmos-db.0.1.3 on 4.14 had its build status changed: not available to passing
• azure-cosmos-db.0.1.4 on 4.14 had its build status changed: not available to passing
• azure-cosmos-db.0.1.5 on 4.14 had its build status changed: not available to passing
• azure-cosmos-db.0.1.6 on 4.14 had its build status changed: not available to passing
• bap-abi.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-abi.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-abi.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-abi.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-abi.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-abi.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-abi.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-abi.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-abi.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-analyze.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-analyze.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-analyze.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-analyze.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-analyze.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-analyze.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-analyze.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-analyze.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-analyze.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-api.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-api.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-api.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-api.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-api.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-api.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-api.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-api.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-api.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-arm.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-arm.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-arm.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-arm.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-arm.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-arm.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-arm.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-arm.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-arm.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-beagle-strings.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-beagle-strings.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-beagle-strings.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-beagle-strings.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-beagle-strings.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-beagle-strings.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-beagle-strings.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-beagle-strings.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-beagle-strings.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-beagle.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-beagle.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-beagle.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-beagle.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-beagle.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-beagle.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-beagle.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-beagle.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-beagle.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-bil.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-bil.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-bil.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-bil.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-bil.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-bil.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-bil.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-bil.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-bil.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-build.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-build.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-build.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-build.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-build.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-build.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-build.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-build.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-build.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-bundle.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-bundle.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-bundle.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-bundle.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-bundle.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-bundle.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-bundle.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-bundle.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-bundle.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-byteweight-frontend.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-byteweight-frontend.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-byteweight-frontend.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-byteweight-frontend.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-byteweight-frontend.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-byteweight-frontend.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-byteweight-frontend.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-byteweight-frontend.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-byteweight-frontend.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-byteweight.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-byteweight.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-byteweight.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-byteweight.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-byteweight.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-byteweight.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-byteweight.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-byteweight.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-byteweight.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-c.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-c.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-c.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-c.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-c.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-c.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-c.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-c.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-c.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-cache.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-cache.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-cache.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-cache.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-cache.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-cache.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-cache.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-cache.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-cache.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-callgraph-collator.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-callgraph-collator.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-callgraph-collator.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-callgraph-collator.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-callgraph-collator.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-callgraph-collator.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-callgraph-collator.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-callgraph-collator.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-callgraph-collator.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-callsites.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-callsites.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-callsites.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-callsites.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-callsites.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-callsites.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-callsites.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-callsites.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-callsites.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-constant-tracker.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-constant-tracker.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-constant-tracker.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-constant-tracker.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-constant-tracker.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-constant-tracker.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-constant-tracker.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-constant-tracker.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-constant-tracker.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-core-theory.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-core-theory.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-core-theory.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-core-theory.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-core-theory.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-core-theory.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-core-theory.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-core-theory.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-core-theory.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-core.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-core.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-core.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-core.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-core.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-core.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-core.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-cxxfilt.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-cxxfilt.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-cxxfilt.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-cxxfilt.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-cxxfilt.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-cxxfilt.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-cxxfilt.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-cxxfilt.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-cxxfilt.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-demangle.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-demangle.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-demangle.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-demangle.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-demangle.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-demangle.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-demangle.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-demangle.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-demangle.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-dependencies.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-dependencies.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-dependencies.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-dependencies.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-dependencies.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-dependencies.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-dependencies.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-dependencies.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-disassemble.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-disassemble.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-disassemble.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-disassemble.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-disassemble.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-disassemble.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-disassemble.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-disassemble.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-disassemble.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-dump-symbols.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-dump-symbols.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-dump-symbols.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-dump-symbols.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-dump-symbols.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-dump-symbols.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-dump-symbols.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-dump-symbols.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-dump-symbols.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-dwarf.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-dwarf.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-dwarf.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-dwarf.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-dwarf.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-dwarf.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-dwarf.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-dwarf.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-dwarf.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-elementary.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-elementary.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-elementary.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-elementary.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-elementary.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-elementary.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-elementary.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-elementary.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-elementary.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-elf.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-elf.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-elf.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-elf.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-elf.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-flatten.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-flatten.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-flatten.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-flatten.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-flatten.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-flatten.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-flatten.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-frontc.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-frontc.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-frontc.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-frontc.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-frontc.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-frontc.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-frontc.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-frontc.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-frontc.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-frontend.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-frontend.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-frontend.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-frontend.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-frontend.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-frontend.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-frontend.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-frontend.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-frontend.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-future.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-future.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-future.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-future.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-future.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-future.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-future.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-future.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-future.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-glibc-runtime.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-glibc-runtime.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-glibc-runtime.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-glibc-runtime.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-glibc-runtime.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-glibc-runtime.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-glibc-runtime.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-glibc-runtime.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-glibc-runtime.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-ida-plugin.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-ida-plugin.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-ida-plugin.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-ida-plugin.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-ida-plugin.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-ida-plugin.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-ida-plugin.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-knowledge.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-knowledge.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-knowledge.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-knowledge.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-knowledge.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-knowledge.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-knowledge.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-knowledge.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-knowledge.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-llvm.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-llvm.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-llvm.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-llvm.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-llvm.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-llvm.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-llvm.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-llvm.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-llvm.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-main.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-main.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-main.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-main.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-main.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-main.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-main.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-main.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-main.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-mc.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-mc.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-mc.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-mc.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-mc.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-mc.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-mc.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-mc.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-mc.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-microx.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-microx.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-microx.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-microx.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-microx.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-microx.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-microx.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-microx.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-microx.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-mips.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-mips.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-mips.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-mips.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-mips.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-mips.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-mips.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-mips.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-mips.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-objdump.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-objdump.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-objdump.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-objdump.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-objdump.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-objdump.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-objdump.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-objdump.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-objdump.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-optimization.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-optimization.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-optimization.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-optimization.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-optimization.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-optimization.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-optimization.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-optimization.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-optimization.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-patterns.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-patterns.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-patterns.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-patterns.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-patterns.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-patterns.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-patterns.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-phoenix.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-phoenix.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-phoenix.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-phoenix.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-phoenix.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-phoenix.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-phoenix.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-phoenix.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-phoenix.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-piqi.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-piqi.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-piqi.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-piqi.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-piqi.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-piqi.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-piqi.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-piqi.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-piqi.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-plugins.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-plugins.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-plugins.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-plugins.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-plugins.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-plugins.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-plugins.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-plugins.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-plugins.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-powerpc.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-powerpc.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-powerpc.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-powerpc.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-powerpc.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-powerpc.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-powerpc.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-powerpc.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-powerpc.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-dictionary.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-dictionary.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-dictionary.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-dictionary.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-dictionary.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-dictionary.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-dictionary.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-dictionary.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-dictionary.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-exploring-scheduler.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-exploring-scheduler.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-exploring-scheduler.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-exploring-scheduler.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-exploring-scheduler.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-exploring-scheduler.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-exploring-scheduler.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-exploring-scheduler.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-exploring-scheduler.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-greedy-scheduler.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-greedy-scheduler.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-greedy-scheduler.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-greedy-scheduler.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-greedy-scheduler.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-greedy-scheduler.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-greedy-scheduler.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-greedy-scheduler.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-greedy-scheduler.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-limit.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-limit.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-limit.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-limit.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-limit.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-limit.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-limit.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-limit.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-limit.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-lisp.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-lisp.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-lisp.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-lisp.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-lisp.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-lisp.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-lisp.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-lisp.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-lisp.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-loader.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-loader.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-loader.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-loader.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-loader.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-loader.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-loader.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-loader.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-loader.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-mark-visited.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-mark-visited.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-mark-visited.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-mark-visited.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-mark-visited.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-mark-visited.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-mark-visited.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-mark-visited.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-mark-visited.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-powerpc.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-powerpc.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-powerpc.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-powerpc.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-powerpc.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-powerpc.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-powerpc.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-powerpc.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-powerpc.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-print.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-print.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-print.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-print.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-print.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-print.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-print.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-print.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-print.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-promiscuous.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-promiscuous.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-promiscuous.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-promiscuous.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-promiscuous.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-promiscuous.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-promiscuous.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-promiscuous.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-promiscuous.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-propagate-taint.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-propagate-taint.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-propagate-taint.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-propagate-taint.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-propagate-taint.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-propagate-taint.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-propagate-taint.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-propagate-taint.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-propagate-taint.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-random.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-random.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-random.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-random.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-random.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-random.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-random.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-random.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-random.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-region.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-region.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-region.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-region.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-region.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-region.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-region.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-region.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-region.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-round-robin-scheduler.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-round-robin-scheduler.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-round-robin-scheduler.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-round-robin-scheduler.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-round-robin-scheduler.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-round-robin-scheduler.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-round-robin-scheduler.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-round-robin-scheduler.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-round-robin-scheduler.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-support.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-support.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-support.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-support.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-support.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-support.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-support.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-support.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-support.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-symbolic-executor.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-symbolic-executor.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-symbolic-executor.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-symbolic-executor.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-symbolic-executor.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-symbolic-executor.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-symbolic-executor.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-symbolic-executor.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-symbolic-executor.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-systems.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-systems.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-systems.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-systems.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-systems.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-systems.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-systems.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-systems.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-systems.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-taint.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-taint.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-taint.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-taint.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-taint.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-taint.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-taint.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-taint.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-taint.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-test.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-test.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-test.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-test.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-test.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-test.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-test.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-test.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-test.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-track-visited.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-track-visited.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-track-visited.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-track-visited.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-track-visited.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-track-visited.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-track-visited.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-track-visited.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-track-visited.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-wandering-scheduler.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-wandering-scheduler.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-wandering-scheduler.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-wandering-scheduler.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-wandering-scheduler.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-wandering-scheduler.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-wandering-scheduler.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-wandering-scheduler.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-wandering-scheduler.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus-x86.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus-x86.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus-x86.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus-x86.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus-x86.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus-x86.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus-x86.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus-x86.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus-x86.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-primus.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-primus.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-primus.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-primus.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-primus.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-primus.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-primus.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-primus.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-primus.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-print.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-print.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-print.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-print.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-print.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-print.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-print.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-print.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-print.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-radare2.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-radare2.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-radare2.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-radare2.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-radare2.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-radare2.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-radare2.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-radare2.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-radare2.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-raw.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-raw.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-raw.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-raw.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-raw.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-raw.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-raw.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-raw.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-raw.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-recipe-command.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-recipe-command.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-recipe-command.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-recipe-command.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-recipe-command.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-recipe-command.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-recipe-command.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-recipe-command.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-recipe-command.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-recipe.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-recipe.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-recipe.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-recipe.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-recipe.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-recipe.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-recipe.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-relation.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-relation.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-relation.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-relation.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-relation.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-relation.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-relation.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-relocatable.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-relocatable.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-relocatable.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-relocatable.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-relocatable.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-relocatable.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-relocatable.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-relocatable.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-relocatable.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-report.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-report.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-report.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-report.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-report.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-report.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-report.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-report.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-report.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-riscv.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-riscv.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-riscv.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-riscv.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-riscv.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-riscv.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-riscv.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-riscv.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-run.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-run.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-run.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-run.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-run.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-run.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-run.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-run.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-run.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-signatures.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-signatures.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-signatures.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-signatures.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-signatures.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-signatures.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-signatures.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-specification.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-specification.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-specification.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-specification.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-specification.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-specification.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-specification.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-specification.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-specification.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-ssa.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-ssa.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-ssa.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-ssa.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-ssa.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-ssa.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-ssa.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-ssa.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-ssa.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-std.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-std.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-std.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-std.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-std.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-std.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-std.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-std.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-std.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-strings.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-strings.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-strings.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-strings.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-strings.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-strings.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-strings.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-strings.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-strings.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-stub-resolver.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-stub-resolver.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-stub-resolver.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-stub-resolver.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-stub-resolver.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-stub-resolver.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-stub-resolver.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-stub-resolver.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-stub-resolver.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-symbol-reader.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-symbol-reader.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-symbol-reader.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-symbol-reader.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-symbol-reader.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-symbol-reader.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-symbol-reader.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-symbol-reader.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-symbol-reader.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-systemz.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-systemz.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-systemz.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-systemz.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-systemz.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-systemz.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-systemz.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-systemz.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-systemz.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-taint-propagator.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-taint-propagator.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-taint-propagator.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-taint-propagator.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-taint-propagator.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-taint-propagator.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-taint-propagator.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-taint-propagator.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-taint-propagator.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-taint.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-taint.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-taint.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-taint.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-taint.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-taint.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-taint.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-taint.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-taint.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-term-mapper.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-term-mapper.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-term-mapper.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-term-mapper.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-term-mapper.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-term-mapper.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-term-mapper.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-term-mapper.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-term-mapper.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-thumb.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-thumb.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-thumb.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-thumb.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-thumb.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-thumb.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-thumb.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-thumb.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-thumb.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-toplevel.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-toplevel.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-toplevel.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-toplevel.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-toplevel.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-toplevel.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-toplevel.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-trace.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-trace.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-trace.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-trace.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-trace.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-trace.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-trace.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-trace.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-trace.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-traces.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-traces.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-traces.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-traces.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-traces.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-traces.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-traces.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-traces.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-traces.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-trivial-condition-form.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-trivial-condition-form.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-trivial-condition-form.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-trivial-condition-form.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-trivial-condition-form.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-trivial-condition-form.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-trivial-condition-form.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-trivial-condition-form.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-trivial-condition-form.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-warn-unused.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-warn-unused.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-warn-unused.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-warn-unused.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-warn-unused.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-warn-unused.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-warn-unused.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-warn-unused.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-warn-unused.2.4.0 on 4.14 is now installable. Current state is: passing
• bap-x86.2.2.0 on 4.14 had its build status changed: not available to passing
• bap-x86.2.3.0 on 4.14 had its build status changed: not available to passing
• bap-x86.2.4.0 on 4.08 is now installable. Current state is: passing
• bap-x86.2.4.0 on 4.09 is now installable. Current state is: passing
• bap-x86.2.4.0 on 4.10 is now installable. Current state is: passing
• bap-x86.2.4.0 on 4.11 is now installable. Current state is: passing
• bap-x86.2.4.0 on 4.12 is now installable. Current state is: passing
• bap-x86.2.4.0 on 4.13 is now installable. Current state is: passing
• bap-x86.2.4.0 on 4.14 is now installable. Current state is: passing
• bap.2.4.0 on 4.08 is now installable. Current state is: passing
• bap.2.4.0 on 4.09 is now installable. Current state is: passing
• bap.2.4.0 on 4.10 is now installable. Current state is: passing
• bap.2.4.0 on 4.11 is now installable. Current state is: passing
• bap.2.4.0 on 4.12 is now installable. Current state is: passing
• bap.2.4.0 on 4.13 is now installable. Current state is: passing
• bap.2.4.0 on 4.14 is now installable. Current state is: passing
• bare.2.2.0 on 4.14 had its build status changed: not available to passing
• bare.2.3.0 on 4.14 had its build status changed: not available to passing
• bare.2.4.0 on 4.08 is now installable. Current state is: passing
• bare.2.4.0 on 4.09 is now installable. Current state is: passing
• bare.2.4.0 on 4.10 is now installable. Current state is: passing
• bare.2.4.0 on 4.11 is now installable. Current state is: passing
• bare.2.4.0 on 4.12 is now installable. Current state is: passing
• bare.2.4.0 on 4.13 is now installable. Current state is: passing
• bare.2.4.0 on 4.14 is now installable. Current state is: passing
• base_bigstring.v0.14.0 on 4.14 had its build status changed: not available to passing
• base_quickcheck.v0.14.1 on 4.14 had its build status changed: not available to passing
• bastet.2.0.0 on 4.14 had its build status changed: not available to passing
• bastet_async.0.1.0 on 4.14 had its build status changed: not available to passing
• bastet_lwt.0.1.0 on 4.14 had its build status changed: not available to passing
• batsat.0.7 on 4.07 is now installable. Current state is: passing
• batsat.0.7 on 4.08 is now installable. Current state is: passing
• batsat.0.7 on 4.09 is now installable. Current state is: passing
• batsat.0.7 on 4.10 is now installable. Current state is: passing
• batsat.0.7 on 4.11 is now installable. Current state is: passing
• batsat.0.7 on 4.12 is now installable. Current state is: passing
• batsat.0.7 on 4.13 is now installable. Current state is: passing
• batsat.0.7 on 4.14 is now installable. Current state is: passing
• batteries.3.4.0 on 4.02 is now installable. Current state is: passing
• batteries.3.4.0 on 4.03 is now installable. Current state is: passing
• batteries.3.4.0 on 4.04 is now installable. Current state is: passing
• batteries.3.4.0 on 4.05 is now installable. Current state is: passing
• batteries.3.4.0 on 4.06 is now installable. Current state is: passing
• batteries.3.4.0 on 4.07 is now installable. Current state is: passing
• batteries.3.4.0 on 4.08 is now installable. Current state is: passing
• batteries.3.4.0 on 4.09 is now installable. Current state is: passing
• batteries.3.4.0 on 4.10 is now installable. Current state is: passing
• batteries.3.4.0 on 4.11 is now installable. Current state is: passing
• batteries.3.4.0 on 4.12 is now installable. Current state is: passing
• batteries.3.4.0 on 4.13 is now installable. Current state is: passing
• beluga.1.0 on 4.14 had its build status changed: not available to passing
• bignum.v0.14.0 on 4.14 had its build status changed: not available to passing
• bimage-display.0.5.0 on 4.08 is now installable. Current state is: passing
• bimage-display.0.5.0 on 4.09 is now installable. Current state is: passing
• bimage-display.0.5.0 on 4.10 is now installable. Current state is: passing
• bimage-display.0.5.0 on 4.11 is now installable. Current state is: passing
• bimage-display.0.5.0 on 4.12 is now installable. Current state is: passing
• bimage-display.0.5.0 on 4.13 is now installable. Current state is: passing
• bimage-display.0.5.0 on 4.14 is now installable. Current state is: passing
• bimage-io.0.5.0 on 4.08 is now installable. Current state is: passing
• bimage-io.0.5.0 on 4.09 is now installable. Current state is: passing
• bimage-io.0.5.0 on 4.10 is now installable. Current state is: passing
• bimage-io.0.5.0 on 4.11 is now installable. Current state is: passing
• bimage-io.0.5.0 on 4.12 is now installable. Current state is: passing
• bimage-io.0.5.0 on 4.13 is now installable. Current state is: passing
• bimage-io.0.5.0 on 4.14 is now installable. Current state is: passing
• bimage-unix.0.5.0 on 4.08 is now installable. Current state is: passing
• bimage-unix.0.5.0 on 4.09 is now installable. Current state is: passing
• bimage-unix.0.5.0 on 4.10 is now installable. Current state is: passing
• bimage-unix.0.5.0 on 4.11 is now installable. Current state is: passing
• bimage-unix.0.5.0 on 4.12 is now installable. Current state is: passing
• bimage-unix.0.5.0 on 4.13 is now installable. Current state is: passing
• bimage-unix.0.5.0 on 4.14 is now installable. Current state is: passing
• bimage.0.5.0 on 4.08 is now installable. Current state is: passing
• bimage.0.5.0 on 4.09 is now installable. Current state is: passing
• bimage.0.5.0 on 4.10 is now installable. Current state is: passing
• bimage.0.5.0 on 4.11 is now installable. Current state is: passing
• bimage.0.5.0 on 4.12 is now installable. Current state is: passing
• bimage.0.5.0 on 4.13 is now installable. Current state is: passing
• bimage.0.5.0 on 4.14 is now installable. Current state is: passing
• bimap.20201231 on 4.14 had its build status changed: not available to passing
• bin_prot.v0.14.0 on 4.14 had its build status changed: not available to passing
• binaryen_dsl.0.7 on 4.12 is now installable. Current state is: passing
• binaryen_dsl.0.7 on 4.13 is now installable. Current state is: passing
• binaryen_dsl.0.7 on 4.14 is now installable. Current state is: passing
• binsec.0.4.1 on 4.08 is now installable. Current state is: passing
• binsec.0.4.1 on 4.09 is now installable. Current state is: passing
• binsec.0.4.1 on 4.10 is now installable. Current state is: passing
• binsec.0.4.1 on 4.11 is now installable. Current state is: passing
• binsec.0.4.1 on 4.12 is now installable. Current state is: passing
• binsec.0.4.1 on 4.13 is now installable. Current state is: passing
• binsec.0.4.1 on 4.14 is now installable. Current state is: passing
• bio_io.0.1.1 on 4.14 had its build status changed: not available to passing
• bio_io.0.1.2 on 4.14 had its build status changed: not available to passing
• bio_io.0.2.1 on 4.14 had its build status changed: not available to passing
• bio_io.0.3.0 on 4.14 had its build status changed: not available to passing
• bio_io.0.4.0 on 4.08 is now installable. Current state is: passing
• bio_io.0.4.0 on 4.09 is now installable. Current state is: passing
• bio_io.0.4.0 on 4.10 is now installable. Current state is: passing
• bio_io.0.4.0 on 4.11 is now installable. Current state is: passing
• bio_io.0.4.0 on 4.12 is now installable. Current state is: passing
• bio_io.0.4.0 on 4.13 is now installable. Current state is: passing
• bio_io.0.4.0 on 4.14 is now installable. Current state is: passing
• biocaml.0.11.0 on 4.14 had its build status changed: not available to passing
• biocaml.0.11.1 on 4.14 had its build status changed: not available to passing
• bisect_ppx-ocamlbuild.1.0.1 on 4.14 had its build status changed: not available to passing
• bisect_ppx.2.6.0 on 4.14 had its build status changed: not available to passing
• bisect_ppx.2.7.0 on 4.14 had its build status changed: not available to passing
• bistro.0.6.0 on 4.14 had its build status changed: not available to passing
• bitvec-binprot.2.2.0 on 4.14 had its build status changed: not available to passing
• bitvec-binprot.2.3.0 on 4.14 had its build status changed: not available to passing
• bitvec-binprot.2.4.0 on 4.08 is now installable. Current state is: passing
• bitvec-binprot.2.4.0 on 4.09 is now installable. Current state is: passing
• bitvec-binprot.2.4.0 on 4.10 is now installable. Current state is: passing
• bitvec-binprot.2.4.0 on 4.11 is now installable. Current state is: passing
• bitvec-binprot.2.4.0 on 4.12 is now installable. Current state is: passing
• bitvec-binprot.2.4.0 on 4.13 is now installable. Current state is: passing
• bitvec-binprot.2.4.0 on 4.14 is now installable. Current state is: passing
• bitvec-order.2.4.0 on 4.08 is now installable. Current state is: passing
• bitvec-order.2.4.0 on 4.09 is now installable. Current state is: passing
• bitvec-order.2.4.0 on 4.10 is now installable. Current state is: passing
• bitvec-order.2.4.0 on 4.11 is now installable. Current state is: passing
• bitvec-order.2.4.0 on 4.12 is now installable. Current state is: passing
• bitvec-order.2.4.0 on 4.13 is now installable. Current state is: passing
• bitvec-order.2.4.0 on 4.14 is now installable. Current state is: passing
• bitvec-sexp.2.4.0 on 4.08 is now installable. Current state is: passing
• bitvec-sexp.2.4.0 on 4.09 is now installable. Current state is: passing
• bitvec-sexp.2.4.0 on 4.10 is now installable. Current state is: passing
• bitvec-sexp.2.4.0 on 4.11 is now installable. Current state is: passing
• bitvec-sexp.2.4.0 on 4.12 is now installable. Current state is: passing
• bitvec-sexp.2.4.0 on 4.13 is now installable. Current state is: passing
• bitvec-sexp.2.4.0 on 4.14 is now installable. Current state is: passing
• bitvec.2.4.0 on 4.08 is now installable. Current state is: passing
• bitvec.2.4.0 on 4.09 is now installable. Current state is: passing
• bitvec.2.4.0 on 4.10 is now installable. Current state is: passing
• bitvec.2.4.0 on 4.11 is now installable. Current state is: passing
• bitvec.2.4.0 on 4.12 is now installable. Current state is: passing
• bitvec.2.4.0 on 4.13 is now installable. Current state is: passing
• bitvec.2.4.0 on 4.14 is now installable. Current state is: passing
• bitwuzla-bin.0.0.0 on 4.02 had its build status changed: failing to passing
• bitwuzla-bin.0.0.0 on 4.09 had its build status changed: failing to passing
• bitwuzla-bin.0.0.0 on 4.10 had its build status changed: failing to passing
• bitwuzla-c.1.0.1 on 4.08 is now installable. Current state is: passing
• bitwuzla-c.1.0.1 on 4.09 is now installable. Current state is: passing
• bitwuzla-c.1.0.1 on 4.10 is now installable. Current state is: passing
• bitwuzla-c.1.0.1 on 4.11 is now installable. Current state is: passing
• bitwuzla-c.1.0.1 on 4.12 is now installable. Current state is: passing
• bitwuzla-c.1.0.1 on 4.13 is now installable. Current state is: passing
• bitwuzla-c.1.0.1 on 4.14 is now installable. Current state is: passing
• bitwuzla.1.0.1 on 4.08 is now installable. Current state is: passing
• bitwuzla.1.0.1 on 4.09 is now installable. Current state is: passing
• bitwuzla.1.0.1 on 4.10 is now installable. Current state is: passing
• bitwuzla.1.0.1 on 4.11 is now installable. Current state is: passing
• bitwuzla.1.0.1 on 4.12 is now installable. Current state is: passing
• bitwuzla.1.0.1 on 4.13 is now installable. Current state is: passing
• bitwuzla.1.0.1 on 4.14 is now installable. Current state is: passing
• bls12-381-gen.0.4.4 on 4.08 is now installable. Current state is: passing
• bls12-381-gen.0.4.4 on 4.09 is now installable. Current state is: passing
• bls12-381-gen.0.4.4 on 4.10 is now installable. Current state is: passing
• bls12-381-gen.0.4.4 on 4.11 is now installable. Current state is: passing
• bls12-381-gen.0.4.4 on 4.12 is now installable. Current state is: passing
• bls12-381-gen.0.4.4 on 4.13 is now installable. Current state is: passing
• bls12-381-gen.0.4.4 on 4.14 is now installable. Current state is: passing
• bls12-381-legacy.0.4.4 on 4.08 is now installable. Current state is: passing
• bls12-381-legacy.0.4.4 on 4.09 is now installable. Current state is: passing
• bls12-381-legacy.0.4.4 on 4.10 is now installable. Current state is: passing
• bls12-381-legacy.0.4.4 on 4.11 is now installable. Current state is: passing
• bls12-381-legacy.0.4.4 on 4.12 is now installable. Current state is: passing
• bls12-381-legacy.0.4.4 on 4.13 is now installable. Current state is: passing
• bls12-381-legacy.0.4.4 on 4.14 is now installable. Current state is: passing
• bookaml.2.1 on 4.13 had its build status changed: not available to passing
• bookaml.4.0 on 4.13 had its build status changed: not available to passing
• bpf.0.1 on 4.14 had its build status changed: not available to passing
• bpf.0.2 on 4.14 had its build status changed: not available to passing
• bst.5.0.0 on 4.13 had its build status changed: not available to passing
• bst.6.0.0 on 4.13 had its build status changed: not available to passing
• bst.6.1.0 on 4.13 had its build status changed: not available to passing
• bst.7.0.0 on 4.13 had its build status changed: not available to passing
• build_path_prefix_map.0.2 on 4.10 had its build status changed: internal failure to passing
• builder-web.0.1.0 on 4.14 had its build status changed: not available to passing
• builder.0.1.0 on 4.14 had its build status changed: not available to passing
• builder.0.1.1 on 4.14 had its build status changed: not available to passing
• builder.0.1.2 on 4.14 had its build status changed: not available to passing
• builder.0.2.0 on 4.14 had its build status changed: not available to passing
• builder.0.3.0 on 4.14 had its build status changed: not available to passing
• bytebuffer.0.0.2 on 4.14 had its build status changed: not available to passing
• cactus.1.0.0 on 4.14 had its build status changed: not available to passing
• caldav.0.1.0 on 4.14 had its build status changed: not available to passing
• caldav.0.1.1 on 4.14 had its build status changed: not available to passing
• camyll.0.1.0 on 4.14 had its build status changed: not available to passing
• camyll.0.2.0 on 4.14 had its build status changed: not available to passing
• camyll.0.3.0 on 4.14 had its build status changed: not available to passing
• camyll.0.4.0 on 4.14 had its build status changed: not available to passing
• caqti-async.1.2.2 on 4.14 had its build status changed: not available to passing
• caqti-async.1.3.0 on 4.14 had its build status changed: not available to passing
• caqti-async.1.6.0 on 4.14 had its build status changed: not available to passing
• caqti-driver-postgresql.1.2.0 on 4.14 had its build status changed: not available to passing
• caqti-driver-postgresql.1.2.1 on 4.14 had its build status changed: not available to passing
• caqti-driver-postgresql.1.2.3 on 4.14 had its build status changed: not available to passing
• caqti-driver-postgresql.1.2.4 on 4.14 had its build status changed: not available to passing
• caqti-driver-sqlite3.1.2.0 on 4.14 had its build status changed: not available to passing
• caqti-driver-sqlite3.1.2.1 on 4.14 had its build status changed: not available to passing
• caqti-driver-sqlite3.1.2.3 on 4.14 had its build status changed: not available to passing
• caqti-dynload.1.2.0 on 4.14 had its build status changed: not available to passing
• caqti-lwt.1.2.0 on 4.14 had its build status changed: not available to passing
• caqti.1.2.0 on 4.14 had its build status changed: not available to passing
• caqti.1.2.1 on 4.14 had its build status changed: not available to passing
• caqti.1.2.3 on 4.14 had its build status changed: not available to passing
• catala.0.2.0 on 4.14 had its build status changed: not available to passing
• certify.0.2 on 4.14 had its build status changed: not available to passing
• certify.0.3.0 on 4.14 had its build status changed: not available to passing
• certify.0.3.1 on 4.14 had its build status changed: not available to passing
• certify.0.3.2 on 4.14 had its build status changed: not available to passing
• cfml.20211215 on 4.08 is now installable. Current state is: passing
• cfml.20211215 on 4.09 is now installable. Current state is: passing
• cfml.20211215 on 4.10 is now installable. Current state is: passing
• cfml.20211215 on 4.11 is now installable. Current state is: passing
• cfml.20211215 on 4.12 is now installable. Current state is: passing
• cfml.20211215 on 4.13 is now installable. Current state is: passing
• cfml.20211215 on 4.14 is now installable. Current state is: passing
• cfstream.1.3.1 on 4.14 had its build status changed: not available to passing
• charrua-client-lwt.1.2.0 on 4.14 had its build status changed: not available to passing
• charrua-client-lwt.1.2.1 on 4.14 had its build status changed: not available to passing
• charrua-client-lwt.1.2.2 on 4.14 had its build status changed: not available to passing
• charrua-client-mirage.1.2.0 on 4.14 had its build status changed: not available to passing
• charrua-client-mirage.1.2.1 on 4.14 had its build status changed: not available to passing
• charrua-client-mirage.1.2.2 on 4.14 had its build status changed: not available to passing
• charrua-client.1.1.0 on 4.14 had its build status changed: not available to passing
• charrua-client.1.2.0 on 4.14 had its build status changed: not available to passing
• charrua-client.1.2.1 on 4.14 had its build status changed: not available to passing
• charrua-client.1.2.2 on 4.14 had its build status changed: not available to passing
• charrua-client.1.3.0 on 4.14 had its build status changed: not available to passing
• charrua-client.1.4.0 on 4.14 had its build status changed: not available to passing
• charrua-client.1.4.1 on 4.14 had its build status changed: not available to passing
• charrua-client.1.5.0 on 4.08 is now installable. Current state is: passing
• charrua-client.1.5.0 on 4.09 is now installable. Current state is: passing
• charrua-client.1.5.0 on 4.10 is now installable. Current state is: passing
• charrua-client.1.5.0 on 4.11 is now installable. Current state is: passing
• charrua-client.1.5.0 on 4.12 is now installable. Current state is: passing
• charrua-client.1.5.0 on 4.13 is now installable. Current state is: passing
• charrua-client.1.5.0 on 4.14 is now installable. Current state is: passing
• charrua-server.1.1.0 on 4.14 had its build status changed: not available to passing
• charrua-server.1.2.0 on 4.14 had its build status changed: not available to passing
• charrua-server.1.2.1 on 4.14 had its build status changed: not available to passing
• charrua-server.1.2.2 on 4.14 had its build status changed: not available to passing
• charrua-server.1.3.0 on 4.14 had its build status changed: not available to passing
• charrua-server.1.4.0 on 4.14 had its build status changed: not available to passing
• charrua-server.1.4.1 on 4.14 had its build status changed: not available to passing
• charrua-server.1.5.0 on 4.08 is now installable. Current state is: passing
• charrua-server.1.5.0 on 4.09 is now installable. Current state is: passing
• charrua-server.1.5.0 on 4.10 is now installable. Current state is: passing
• charrua-server.1.5.0 on 4.11 is now installable. Current state is: passing
• charrua-server.1.5.0 on 4.12 is now installable. Current state is: passing
• charrua-server.1.5.0 on 4.13 is now installable. Current state is: passing
• charrua-server.1.5.0 on 4.14 is now installable. Current state is: passing
• charrua-unix.1.1.0 on 4.14 had its build status changed: not available to passing
• charrua-unix.1.2.0 on 4.14 had its build status changed: not available to passing
• charrua-unix.1.2.1 on 4.14 had its build status changed: not available to passing
• charrua-unix.1.2.2 on 4.14 had its build status changed: not available to passing
• charrua-unix.1.3.0 on 4.14 had its build status changed: not available to passing
• charrua-unix.1.4.0 on 4.14 had its build status changed: not available to passing
• charrua-unix.1.4.1 on 4.14 had its build status changed: not available to passing
• charrua-unix.1.5.0 on 4.08 is now installable. Current state is: passing
• charrua-unix.1.5.0 on 4.09 is now installable. Current state is: passing
• charrua-unix.1.5.0 on 4.10 is now installable. Current state is: passing
• charrua-unix.1.5.0 on 4.11 is now installable. Current state is: passing
• charrua-unix.1.5.0 on 4.12 is now installable. Current state is: passing
• charrua-unix.1.5.0 on 4.13 is now installable. Current state is: passing
• charrua-unix.1.5.0 on 4.14 is now installable. Current state is: passing
• charrua.1.1.0 on 4.14 had its build status changed: not available to passing
• charrua.1.2.0 on 4.14 had its build status changed: not available to passing
• charrua.1.2.1 on 4.14 had its build status changed: not available to passing
• charrua.1.2.2 on 4.14 had its build status changed: not available to passing
• charrua.1.3.0 on 4.14 had its build status changed: not available to passing
• charrua.1.4.0 on 4.14 had its build status changed: not available to passing
• charrua.1.4.1 on 4.14 had its build status changed: not available to passing
• charrua.1.5.0 on 4.08 is now installable. Current state is: passing
• charrua.1.5.0 on 4.09 is now installable. Current state is: passing
• charrua.1.5.0 on 4.10 is now installable. Current state is: passing
• charrua.1.5.0 on 4.11 is now installable. Current state is: passing
• charrua.1.5.0 on 4.12 is now installable. Current state is: passing
• charrua.1.5.0 on 4.13 is now installable. Current state is: passing
• charrua.1.5.0 on 4.14 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.06 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.07 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.08 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.09 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.10 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.11 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.12 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.13 is now installable. Current state is: passing
• cloudi.2.0.4 on 4.14 is now installable. Current state is: passing
• clp_operations.0.0.1 on 4.13 had its build status changed: not available to passing
• clp_operations.0.0.1 on 4.14 had its build status changed: not available to passing
• clz.0.1.0 on 4.08 is now installable. Current state is: passing
• clz.0.1.0 on 4.09 is now installable. Current state is: passing
• clz.0.1.0 on 4.10 is now installable. Current state is: passing
• clz.0.1.0 on 4.11 is now installable. Current state is: passing
• clz.0.1.0 on 4.12 is now installable. Current state is: passing
• clz.0.1.0 on 4.13 is now installable. Current state is: passing
• clz.0.1.0 on 4.14 is now installable. Current state is: passing
• cmarker.0.3.0 on 4.14 had its build status changed: not available to passing
• cohttp-async.2.5.4 on 4.14 had its build status changed: not available to passing
• cohttp-async.2.5.5 on 4.14 had its build status changed: not available to passing
• cohttp-async.2.5.6 on 4.08 is now installable. Current state is: passing
• cohttp-async.2.5.6 on 4.09 is now installable. Current state is: passing
• cohttp-async.2.5.6 on 4.10 is now installable. Current state is: passing
• cohttp-async.2.5.6 on 4.11 is now installable. Current state is: passing
• cohttp-async.2.5.6 on 4.12 is now installable. Current state is: passing
• cohttp-async.2.5.6 on 4.13 is now installable. Current state is: passing
• cohttp-async.2.5.6 on 4.14 is now installable. Current state is: passing
• cohttp-async.4.0.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-jsoo.2.5.6 on 4.04 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.05 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.06 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.07 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.08 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.09 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.10 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.11 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.12 is now installable. Current state is: passing
• cohttp-lwt-jsoo.2.5.6 on 4.13 is now installable. Current state is: passing
• cohttp-lwt-unix.1.2.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.0.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.1.3 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.2.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.3.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.4.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.5.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.5.1 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.5.2-1 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.5.4 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.5.5 on 4.14 had its build status changed: not available to passing
• cohttp-lwt-unix.2.5.6 on 4.04 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.05 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.06 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.07 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.08 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.09 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.10 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.11 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.12 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.13 is now installable. Current state is: passing
• cohttp-lwt-unix.2.5.6 on 4.14 is now installable. Current state is: passing
• cohttp-lwt-unix.4.0.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.1.2.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.0.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.1.3 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.2.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.3.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.4.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.5.0 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.5.1 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.5.2-1 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.5.4 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.5.5 on 4.14 had its build status changed: not available to passing
• cohttp-lwt.2.5.6 on 4.04 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.05 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.06 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.07 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.08 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.09 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.10 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.11 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.12 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.13 is now installable. Current state is: passing
• cohttp-lwt.2.5.6 on 4.14 is now installable. Current state is: passing
• cohttp-lwt.4.0.0 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.4.0 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.5.0 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.5.1 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.5.2 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.5.2-1 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.5.3 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.5.4 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.5.5 on 4.14 had its build status changed: not available to passing
• cohttp-mirage.2.5.6 on 4.07 is now installable. Current state is: passing
• cohttp-mirage.2.5.6 on 4.08 is now installable. Current state is: passing
• cohttp-mirage.2.5.6 on 4.09 is now installable. Current state is: passing
• cohttp-mirage.2.5.6 on 4.10 is now installable. Current state is: passing
• cohttp-mirage.2.5.6 on 4.11 is now installable. Current state is: passing
• cohttp-mirage.2.5.6 on 4.12 is now installable. Current state is: passing
• cohttp-mirage.2.5.6 on 4.13 is now installable. Current state is: passing
• cohttp-mirage.2.5.6 on 4.14 is now installable. Current state is: passing
• cohttp-mirage.4.0.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.1.0.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.1.0.2 on 4.14 had its build status changed: not available to passing
• cohttp-top.1.1.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.1.1.1 on 4.14 had its build status changed: not available to passing
• cohttp-top.1.2.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.0.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.1.3 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.2.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.3.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.4.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.5.0 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.5.1 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.5.2-1 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.5.4 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.5.5 on 4.14 had its build status changed: not available to passing
• cohttp-top.2.5.6 on 4.04 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.05 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.06 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.07 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.08 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.09 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.10 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.11 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.12 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.13 is now installable. Current state is: passing
• cohttp-top.2.5.6 on 4.14 is now installable. Current state is: passing
• cohttp-top.4.0.0 on 4.14 had its build status changed: not available to passing
• cohttp.1.2.0 on 4.14 had its build status changed: not available to passing
• cohttp.2.0.0 on 4.14 had its build status changed: not available to passing
• cohttp.2.1.2 on 4.14 had its build status changed: not available to passing
• cohttp.2.1.3 on 4.14 had its build status changed: not available to passing
• cohttp.2.2.0 on 4.14 had its build status changed: not available to passing
• cohttp.2.3.0 on 4.14 had its build status changed: not available to passing
• cohttp.2.4.0 on 4.14 had its build status changed: not available to passing
• cohttp.2.5.0 on 4.14 had its build status changed: not available to passing
• cohttp.2.5.1 on 4.14 had its build status changed: not available to passing
• cohttp.2.5.2-1 on 4.14 had its build status changed: not available to passing
• cohttp.2.5.4 on 4.14 had its build status changed: not available to passing
• cohttp.2.5.5 on 4.14 had its build status changed: not available to passing
• cohttp.2.5.6 on 4.04 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.05 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.06 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.07 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.08 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.09 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.10 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.11 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.12 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.13 is now installable. Current state is: passing
• cohttp.2.5.6 on 4.14 is now installable. Current state is: passing
• cohttp.4.0.0 on 4.14 had its build status changed: not available to passing
• colombe.0.1.0 on 4.14 had its build status changed: not available to passing
• combinat.1.0 on 4.14 had its build status changed: not available to passing
• comby-kernel.1.4.1 on 4.14 had its build status changed: not available to passing
• comby-kernel.1.7.0 on 4.14 had its build status changed: not available to passing
• comby-semantic.1.7.0 on 4.09 had its build status changed: internal failure to passing
• comby-semantic.1.7.0 on 4.10 had its build status changed: internal failure to passing
• comby-semantic.1.7.0 on 4.14 had its build status changed: not available to passing
• comby.1.2.2 on 4.14 had its build status changed: not available to passing
• comby.1.3.0 on 4.14 had its build status changed: not available to passing
• comby.1.4.0 on 4.14 had its build status changed: not available to passing
• comby.1.4.1 on 4.14 had its build status changed: not available to passing
• comby.1.7.0 on 4.14 had its build status changed: not available to passing
• command_rpc.v0.14.0 on 4.14 had its build status changed: not available to passing
• conduit-async.1.3.0 on 4.14 had its build status changed: not available to passing
• conduit-async.1.4.0 on 4.14 had its build status changed: not available to passing
• conduit-async.1.5.0 on 4.14 had its build status changed: not available to passing
• conduit-async.2.0.0 on 4.14 had its build status changed: not available to passing
• conduit-async.2.0.1 on 4.14 had its build status changed: not available to passing
• conduit-async.2.0.2 on 4.14 had its build status changed: not available to passing
• conduit-async.2.1.0 on 4.14 had its build status changed: not available to passing
• conduit-async.2.3.0 on 4.14 had its build status changed: not available to passing
• conduit-async.4.0.0 on 4.14 had its build status changed: not available to passing
• conduit-async.4.0.1 on 4.14 had its build status changed: not available to passing
• conduit-async.4.0.2 on 4.14 had its build status changed: not available to passing
• conduit-async.5.0.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.1.3.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.1.4.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.1.5.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.2.0.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.2.0.1 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.2.0.2 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.2.1.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.2.2.2 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.2.3.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.4.0.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.4.0.1 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.4.0.2 on 4.14 had its build status changed: not available to passing
• conduit-lwt-unix.5.0.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt.1.3.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt.1.4.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt.1.5.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt.2.0.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt.2.0.1 on 4.14 had its build status changed: not available to passing
• conduit-lwt.2.0.2 on 4.14 had its build status changed: not available to passing
• conduit-lwt.2.1.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt.2.3.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt.4.0.0 on 4.14 had its build status changed: not available to passing
• conduit-lwt.4.0.1 on 4.14 had its build status changed: not available to passing
• conduit-lwt.4.0.2 on 4.14 had its build status changed: not available to passing
• conduit-lwt.5.0.0 on 4.14 had its build status changed: not available to passing
• conduit-mirage.2.1.0 on 4.14 had its build status changed: not available to passing
• conduit-mirage.2.2.1 on 4.14 had its build status changed: not available to passing
• conduit-mirage.2.3.0 on 4.14 had its build status changed: not available to passing
• conduit-mirage.4.0.0 on 4.14 had its build status changed: not available to passing
• conduit-mirage.4.0.1 on 4.14 had its build status changed: not available to passing
• conduit-mirage.4.0.2 on 4.14 had its build status changed: not available to passing
• conduit-mirage.5.0.0 on 4.14 had its build status changed: not available to passing
• conduit.1.3.0 on 4.14 had its build status changed: not available to passing
• conduit.1.4.0 on 4.14 had its build status changed: not available to passing
• conduit.1.5.0 on 4.14 had its build status changed: not available to passing
• conduit.2.0.0 on 4.14 had its build status changed: not available to passing
• conduit.2.0.1 on 4.14 had its build status changed: not available to passing
• conduit.2.0.2 on 4.14 had its build status changed: not available to passing
• conduit.2.1.0 on 4.14 had its build status changed: not available to passing
• conduit.2.3.0 on 4.14 had its build status changed: not available to passing
• conduit.4.0.0 on 4.14 had its build status changed: not available to passing
• conduit.4.0.1 on 4.14 had its build status changed: not available to passing
• conduit.4.0.2 on 4.14 had its build status changed: not available to passing
• conduit.5.0.0 on 4.14 had its build status changed: not available to passing
• conex-nocrypto.0.10.0 on 4.14 had its build status changed: not available to passing
• conex-nocrypto.0.10.1 on 4.14 had its build status changed: not available to passing
• conex-nocrypto.0.11.0 on 4.14 had its build status changed: not available to passing
• conex.0.9.2 on 4.14 had its build status changed: not available to passing
• conf-bison.1 on 4.03 had its build status changed: failing to passing
• conf-bison.1 on 4.10 had its build status changed: failing to passing
• conf-bison.2 on 4.02 had its build status changed: failing to passing
• conf-bison.2 on 4.11 had its build status changed: failing to passing
• conf-bison.2 on 4.12 had its build status changed: failing to passing
• conf-glpk.1 on 4.04 had its build status changed: internal failure to passing
• conf-lame.1 on 4.02 is now installable. Current state is: passing
• conf-lame.1 on 4.03 is now installable. Current state is: passing
• conf-lame.1 on 4.04 is now installable. Current state is: passing
• conf-lame.1 on 4.05 is now installable. Current state is: passing
• conf-lame.1 on 4.06 is now installable. Current state is: passing
• conf-lame.1 on 4.07 is now installable. Current state is: passing
• conf-lame.1 on 4.08 is now installable. Current state is: passing
• conf-lame.1 on 4.09 is now installable. Current state is: passing
• conf-lame.1 on 4.10 is now installable. Current state is: passing
• conf-lame.1 on 4.11 is now installable. Current state is: passing
• conf-lame.1 on 4.12 is now installable. Current state is: passing
• conf-lame.1 on 4.13 is now installable. Current state is: passing
• conf-lame.1 on 4.14 is now installable. Current state is: passing
• conf-openblas.0.2.0 on 4.04 had its build status changed: failing to passing
• conf-openblas.0.2.1 on 4.09 had its build status changed: failing to passing
• conf-sundials.2 on 4.02 is now installable. Current state is: passing
• conf-sundials.2 on 4.03 is now installable. Current state is: passing
• conf-sundials.2 on 4.04 is now installable. Current state is: passing
• conf-sundials.2 on 4.05 is now installable. Current state is: passing
• conf-sundials.2 on 4.06 is now installable. Current state is: passing
• conf-sundials.2 on 4.07 is now installable. Current state is: passing
• conf-sundials.2 on 4.08 is now installable. Current state is: passing
• conf-sundials.2 on 4.09 is now installable. Current state is: passing
• conf-sundials.2 on 4.10 is now installable. Current state is: passing
• conf-sundials.2 on 4.11 is now installable. Current state is: passing
• conf-sundials.2 on 4.12 is now installable. Current state is: passing
• conf-sundials.2 on 4.13 is now installable. Current state is: passing
• conf-sundials.2 on 4.14 is now installable. Current state is: passing
• config-file.1.2 on 4.05 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
• configurator.v0.9.0 on 4.04 had its build status changed: partially failing to passing
• conformist.0.2.0 on 4.14 had its build status changed: partially failing to passing
• conformist.0.4.0 on 4.14 had its build status changed: partially failing to passing
• conformist.0.6.0 on 4.08 had its build status changed: partially failing to passing
• conformist.0.7.0 on 4.14 had its build status changed: partially failing to passing
• conjury.2.1 on 4.08 is now installable. Current state is: passing
• conjury.2.1 on 4.09 is now installable. Current state is: passing
• conjury.2.1 on 4.10 is now installable. Current state is: passing
• conjury.2.1 on 4.11 is now installable. Current state is: passing
• conjury.2.1 on 4.12 is now installable. Current state is: passing
• conjury.2.1 on 4.13 is now installable. Current state is: passing
• conjury.2.1 on 4.14 is now installable. Current state is: passing
• containers-data.3.4 on 4.10 had its build status changed: internal failure to passing
• containers-thread.3.4 on 4.03 had its build status changed: internal failure to passing
• containers-thread.3.5 on 4.09 had its build status changed: internal failure to passing
• containers-thread.3.6 on 4.03 had its build status changed: internal failure to passing
• containers-thread.3.6.1 on 4.10 had its build status changed: internal failure to passing
• containers.0.11 on 4.04 had its build status changed: internal failure to passing
• containers.0.14 on 4.05 had its build status changed: internal failure to passing
• containers.0.16.1 on 4.06 had its build status changed: internal failure to passing
• cookies.1.0.0 on 4.14 had its build status changed: not available to passing
• coq-serapi.8.13.0+0.13.0 on 4.12 had its build status changed: partially failing to passing
• coq-serapi.8.14.0+0.14.0 on 4.09 had its build status changed: partially failing to passing
• coq-serapi.8.14.0+0.14.0 on 4.11 had its build status changed: partially failing to passing
• coq-serapi.8.7.1+0.4.8 on 4.06 had its build status changed: partially failing to passing
• coq-serapi.8.8.0+0.5.2 on 4.06 had its build status changed: partially failing to passing
• coq-serapi.8.8.0+0.5.4 on 4.06 had its build status changed: partially failing to passing
• coq-serapi.8.8.0+0.5.5 on 4.07 had its build status changed: partially failing to passing
• coq-serapi.8.8.0+0.5.5 on 4.08 had its build status changed: partially failing to passing
• coq-serapi.8.9.0+0.6.0 on 4.07 had its build status changed: partially failing to passing
• coq.8.10.0 on 4.05 had its build status changed: failing to passing
• coq.8.11.0 on 4.06 had its build status changed: failing to passing
• coq.8.11.0 on 4.09 had its build status changed: failing to passing
• coq.8.11.1 on 4.10 had its build status changed: failing to passing
• coq.8.11.2 on 4.05 had its build status changed: failing to passing
• coq.8.12.0 on 4.05 had its build status changed: failing to passing
• coq.8.12.0 on 4.06 had its build status changed: failing to passing
• coq.8.12.1 on 4.11 had its build status changed: failing to passing
• coq.8.13.0 on 4.07 had its build status changed: failing to passing
• coq.8.13.0 on 4.13 had its build status changed: failing to passing
• coq.8.13.1 on 4.12 had its build status changed: failing to passing
• coq.8.13.1 on 4.14 had its build status changed: failing to passing
• coq.8.13.2 on 4.07 had its build status changed: failing to passing
• coq.8.14.0 on 4.06 had its build status changed: failing to passing
• coq.8.14.0 on 4.14 had its build status changed: failing to passing
• coq.8.14.1 on 4.11 had its build status changed: failing to passing
• coq.8.14.1 on 4.13 had its build status changed: failing to passing
• coq.8.7.1+2 on 4.05 had its build status changed: failing to passing
• coqide.8.11.1 on 4.09 had its build status changed: partially failing to passing
• coqide.8.12.1 on 4.10 had its build status changed: partially failing to passing
• coqide.8.13.1 on 4.12 had its build status changed: partially failing to passing
• cordova-plugin-activity-indicator.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-barcode-scanner.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-battery-status.1.0 on 4.13 had its build status changed: partially failing to passing
• cordova-plugin-camera.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-clipboard.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-device-orientation.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-device.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-dialogs.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-email-composer.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-fcm.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-file-opener.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-file-transfer.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-file.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-geolocation.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-image-picker.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-inappbrowser.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-insomnia.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-keyboard.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-loading-spinner.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-media-capture.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-media.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-network-information.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-progress.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-push-notifications.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-push-notifications.1.1 on 4.14 had its build status changed: not available to passing
• cordova-plugin-push-notifications.1.1.1 on 4.14 had its build status changed: not available to passing
• cordova-plugin-push-notifications.1.1.2 on 4.14 had its build status changed: not available to passing
• cordova-plugin-qrscanner.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-screen-orientation.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-sms.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-social-sharing.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-statusbar.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-toast.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-touch-id.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-vibration.1.0 on 4.14 had its build status changed: not available to passing
• cordova-plugin-videoplayer.1.0 on 4.14 had its build status changed: not available to passing
• core-and-more.0.0.1 on 4.14 had its build status changed: not available to passing
• core.v0.14.1 on 4.14 had its build status changed: not available to passing
• core_bench.v0.14.0 on 4.14 had its build status changed: not available to passing
• core_extended.v0.14.0 on 4.14 had its build status changed: not available to passing
• core_kernel.v0.14.1 on 4.14 had its build status changed: not available to passing
• core_kernel.v0.14.2 on 4.14 had its build status changed: not available to passing
• core_profiler.v0.14.0 on 4.14 had its build status changed: not available to passing
• core_unix.v0.14.0 on 4.08 is now installable. Current state is: passing
• core_unix.v0.14.0 on 4.09 is now installable. Current state is: passing
• core_unix.v0.14.0 on 4.10 is now installable. Current state is: passing
• core_unix.v0.14.0 on 4.11 is now installable. Current state is: passing
• core_unix.v0.14.0 on 4.12 is now installable. Current state is: passing
• core_unix.v0.14.0 on 4.13 is now installable. Current state is: passing
• core_unix.v0.14.0 on 4.14 is now installable. Current state is: passing
• cpm.1.0.0 on 4.13 had its build status changed: not available to passing
• cpm.10.0.0 on 4.13 had its build status changed: not available to passing
• cpm.10.2.1 on 4.13 had its build status changed: not available to passing
• cpm.11.0.0 on 4.13 had its build status changed: not available to passing
• cpm.12.0.0 on 4.13 had its build status changed: not available to passing
• cpm.2.0.0 on 4.13 had its build status changed: not available to passing
• cpm.3.0.0 on 4.13 had its build status changed: not available to passing
• cpm.4.0.0 on 4.13 had its build status changed: not available to passing
• cpm.5.0.0 on 4.13 had its build status changed: not available to passing
• cpm.6.0.0 on 4.13 had its build status changed: not available to passing
• cpm.7.0.0 on 4.13 had its build status changed: not available to passing
• cpm.8.0.0 on 4.13 had its build status changed: not available to passing
• cpm.9.0.0 on 4.13 had its build status changed: not available to passing
• crc.2.1.0 on 4.14 had its build status changed: not available to passing
• css-parser.0.2.2 on 4.14 had its build status changed: not available to passing
• css-parser.0.2.3 on 4.14 had its build status changed: not available to passing
• css-parser.0.2.4 on 4.14 had its build status changed: not available to passing
• css-parser.0.2.5 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.0.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.0.1 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.0.2 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.1.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.1.1 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.2.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.2.1 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.3.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.4.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.5.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.6.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.3.7.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.4.0.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.5.0.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.5.1.1 on 4.14 had its build status changed: not available to passing
• cstruct-async.5.2.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.6.0.0 on 4.14 had its build status changed: not available to passing
• cstruct-async.6.0.1 on 4.14 had its build status changed: not available to passing
• csvfields.v0.14.0 on 4.14 had its build status changed: not available to passing
• ctypes.0.20.0 on 4.03 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.04 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.05 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.06 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.07 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.08 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.09 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.10 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.11 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.12 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.13 is now installable. Current state is: passing
• ctypes.0.20.0 on 4.14 is now installable. Current state is: passing
• cuid.0.1 on 4.14 had its build status changed: not available to passing
• current.0.1 on 4.14 had its build status changed: not available to passing
• current.0.2 on 4.14 had its build status changed: not available to passing
• current.0.3 on 4.14 had its build status changed: not available to passing
• current.0.4 on 4.14 had its build status changed: not available to passing
• current.0.5 on 4.14 had its build status changed: not available to passing
• current_docker.0.1 on 4.14 had its build status changed: not available to passing
• current_docker.0.2 on 4.14 had its build status changed: not available to passing
• current_docker.0.3 on 4.14 had its build status changed: not available to passing
• current_docker.0.4 on 4.14 had its build status changed: not available to passing
• current_docker.0.5 on 4.14 had its build status changed: not available to passing
• current_git.0.1 on 4.14 had its build status changed: not available to passing
• current_git.0.2 on 4.14 had its build status changed: not available to passing
• current_git.0.3 on 4.14 had its build status changed: not available to passing
• current_git.0.4 on 4.14 had its build status changed: not available to passing
• current_git.0.5 on 4.14 had its build status changed: not available to passing
• current_github.0.2 on 4.14 had its build status changed: not available to passing
• current_github.0.3 on 4.14 had its build status changed: not available to passing
• current_github.0.4 on 4.14 had its build status changed: not available to passing
• current_github.0.5 on 4.14 had its build status changed: not available to passing
• current_slack.0.1 on 4.14 had its build status changed: not available to passing
• current_slack.0.2 on 4.14 had its build status changed: not available to passing
• current_slack.0.3 on 4.14 had its build status changed: not available to passing
• current_slack.0.4 on 4.14 had its build status changed: not available to passing
• current_slack.0.5 on 4.14 had its build status changed: not available to passing
• current_web.0.1 on 4.14 had its build status changed: not available to passing
• current_web.0.2 on 4.14 had its build status changed: not available to passing
• current_web.0.3 on 4.14 had its build status changed: not available to passing
• current_web.0.4 on 4.14 had its build status changed: not available to passing
• current_web.0.5 on 4.14 had its build status changed: not available to passing
• daft.0.0.3 on 4.03 had its build status changed: failing to passing
• daft.0.0.3 on 4.04 had its build status changed: failing to passing
• daft.0.0.3 on 4.05 had its build status changed: failing to passing
• daft.0.0.3 on 4.06 had its build status changed: failing to passing
• daft.0.0.3 on 4.07 had its build status changed: failing to passing
• daft.0.0.3 on 4.08 had its build status changed: failing to passing
• daft.0.0.3 on 4.09 had its build status changed: failing to passing
• daft.0.0.3 on 4.10 had its build status changed: failing to passing
• daft.0.0.3 on 4.11 had its build status changed: failing to passing
• daft.0.0.3 on 4.12 had its build status changed: failing to passing
• daft.0.0.3 on 4.13 had its build status changed: not available to passing
• dap.1.0.0 on 4.14 had its build status changed: not available to passing
• dap.1.0.1 on 4.14 had its build status changed: not available to passing
• dap.1.0.2 on 4.14 had its build status changed: not available to passing
• dap.1.0.3 on 4.14 had its build status changed: not available to passing
• dap.1.0.4 on 4.14 had its build status changed: not available to passing
• dap.1.0.5 on 4.14 had its build status changed: not available to passing
• dap.1.0.6 on 4.14 had its build status changed: not available to passing
• datakit-server-9p.0.12.0 on 4.14 had its build status changed: not available to passing
• datakit-server-9p.0.12.2 on 4.14 had its build status changed: not available to passing
• datakit-server-9p.0.12.3 on 4.14 had its build status changed: not available to passing
• datakit-server-9p.1.0.0 on 4.14 had its build status changed: not available to passing
• dbf.0.1.1 on 4.14 had its build status changed: not available to passing
• delimited_parsing.v0.14.0 on 4.14 had its build status changed: not available to passing
• devkit.1.2 on 4.14 had its build status changed: not available to passing
• devkit.1.20210120 on 4.14 had its build status changed: not available to passing
• devkit.1.20210517 on 4.14 had its build status changed: not available to passing
• devkit.1.3 on 4.14 had its build status changed: not available to passing
• diet.0.2 on 4.14 had its build status changed: not available to passing
• diet.0.3 on 4.14 had its build status changed: not available to passing
• dirsift.0.0.5 on 4.08 is now installable. Current state is: passing
• dirsift.0.0.5 on 4.09 is now installable. Current state is: passing
• dirsift.0.0.5 on 4.10 is now installable. Current state is: passing
• dirsift.0.0.5 on 4.11 is now installable. Current state is: passing
• dirsift.0.0.5 on 4.12 is now installable. Current state is: passing
• dirsift.0.0.5 on 4.13 is now installable. Current state is: passing
• dirsift.0.0.5 on 4.14 is now installable. Current state is: passing
• dirsp-exchange-kbb2017.0.1.0 on 4.14 had its build status changed: not available to passing
• dirsp-exchange.0.1.0 on 4.14 had its build status changed: not available to passing
• dirsp-proscript-mirage.0.1.0 on 4.14 had its build status changed: not available to passing
• dirsp-proscript.0.1.0 on 4.14 had its build status changed: not available to passing
• dkim-mirage.0.3.0 on 4.14 had its build status changed: not available to passing
• dkim-mirage.0.3.1 on 4.14 had its build status changed: not available to passing
• dkim.0.3.0 on 4.14 had its build status changed: not available to passing
• dkim.0.3.1 on 4.14 had its build status changed: not available to passing
• dns-certify.4.4.0 on 4.14 had its build status changed: not available to passing
• dns-certify.4.4.1 on 4.14 had its build status changed: not available to passing
• dns-certify.4.5.0 on 4.14 had its build status changed: not available to passing
• dns-certify.4.6.0 on 4.14 had its build status changed: not available to passing
• dns-certify.4.6.1 on 4.14 had its build status changed: not available to passing
• dns-certify.4.6.2 on 4.14 had its build status changed: not available to passing
• dns-certify.4.6.3 on 4.14 had its build status changed: not available to passing
• dns-certify.5.0.0 on 4.14 had its build status changed: not available to passing
• dns-certify.6.1.3 on 4.08 is now installable. Current state is: passing
• dns-certify.6.1.3 on 4.09 is now installable. Current state is: passing
• dns-certify.6.1.3 on 4.10 is now installable. Current state is: passing
• dns-certify.6.1.3 on 4.11 is now installable. Current state is: passing
• dns-certify.6.1.3 on 4.12 is now installable. Current state is: passing
• dns-certify.6.1.3 on 4.13 is now installable. Current state is: passing
• dns-certify.6.1.3 on 4.14 is now installable. Current state is: passing
• dns-cli.4.4.0 on 4.14 had its build status changed: not available to passing
• dns-cli.4.4.1 on 4.14 had its build status changed: not available to passing
• dns-cli.4.5.0 on 4.14 had its build status changed: not available to passing
• dns-cli.4.6.1 on 4.14 had its build status changed: not available to passing
• dns-cli.4.6.2 on 4.14 had its build status changed: not available to passing
• dns-cli.4.6.3 on 4.14 had its build status changed: not available to passing
• dns-cli.5.0.0 on 4.14 had its build status changed: not available to passing
• dns-cli.6.0.0 on 4.14 had its build status changed: not available to passing
• dns-cli.6.0.1 on 4.14 had its build status changed: not available to passing
• dns-cli.6.0.2 on 4.14 had its build status changed: not available to passing
• dns-cli.6.1.0 on 4.14 had its build status changed: not available to passing
• dns-cli.6.1.1 on 4.14 had its build status changed: not available to passing
• dns-cli.6.1.2 on 4.14 had its build status changed: not available to passing
• dns-cli.6.1.3 on 4.08 is now installable. Current state is: passing
• dns-cli.6.1.3 on 4.09 is now installable. Current state is: passing
• dns-cli.6.1.3 on 4.10 is now installable. Current state is: passing
• dns-cli.6.1.3 on 4.11 is now installable. Current state is: passing
• dns-cli.6.1.3 on 4.12 is now installable. Current state is: passing
• dns-cli.6.1.3 on 4.13 is now installable. Current state is: passing
• dns-cli.6.1.3 on 4.14 is now installable. Current state is: passing
• dns-client.6.0.0 on 4.14 had its build status changed: not available to passing
• dns-client.6.0.1 on 4.14 had its build status changed: not available to passing
• dns-client.6.0.2 on 4.14 had its build status changed: not available to passing
• dns-client.6.1.0 on 4.14 had its build status changed: not available to passing
• dns-client.6.1.1 on 4.14 had its build status changed: not available to passing
• dns-client.6.1.2 on 4.14 had its build status changed: not available to passing
• dns-client.6.1.3 on 4.08 is now installable. Current state is: passing
• dns-client.6.1.3 on 4.09 is now installable. Current state is: passing
• dns-client.6.1.3 on 4.10 is now installable. Current state is: passing
• dns-client.6.1.3 on 4.11 is now installable. Current state is: passing
• dns-client.6.1.3 on 4.12 is now installable. Current state is: passing
• dns-client.6.1.3 on 4.13 is now installable. Current state is: passing
• dns-client.6.1.3 on 4.14 is now installable. Current state is: passing
• dns-mirage.6.1.3 on 4.08 is now installable. Current state is: passing
• dns-mirage.6.1.3 on 4.09 is now installable. Current state is: passing
• dns-mirage.6.1.3 on 4.10 is now installable. Current state is: passing
• dns-mirage.6.1.3 on 4.11 is now installable. Current state is: passing
• dns-mirage.6.1.3 on 4.12 is now installable. Current state is: passing
• dns-mirage.6.1.3 on 4.13 is now installable. Current state is: passing
• dns-mirage.6.1.3 on 4.14 is now installable. Current state is: passing
• dns-resolver.6.0.0 on 4.14 had its build status changed: not available to passing
• dns-resolver.6.0.1 on 4.14 had its build status changed: not available to passing
• dns-resolver.6.0.2 on 4.14 had its build status changed: not available to passing
• dns-resolver.6.1.0 on 4.14 had its build status changed: not available to passing
• dns-resolver.6.1.1 on 4.14 had its build status changed: not available to passing
• dns-resolver.6.1.2 on 4.14 had its build status changed: not available to passing
• dns-resolver.6.1.3 on 4.08 is now installable. Current state is: passing
• dns-resolver.6.1.3 on 4.09 is now installable. Current state is: passing
• dns-resolver.6.1.3 on 4.10 is now installable. Current state is: passing
• dns-resolver.6.1.3 on 4.11 is now installable. Current state is: passing
• dns-resolver.6.1.3 on 4.12 is now installable. Current state is: passing
• dns-resolver.6.1.3 on 4.13 is now installable. Current state is: passing
• dns-resolver.6.1.3 on 4.14 is now installable. Current state is: passing
• dns-server.6.1.3 on 4.08 is now installable. Current state is: passing
• dns-server.6.1.3 on 4.09 is now installable. Current state is: passing
• dns-server.6.1.3 on 4.10 is now installable. Current state is: passing
• dns-server.6.1.3 on 4.11 is now installable. Current state is: passing
• dns-server.6.1.3 on 4.12 is now installable. Current state is: passing
• dns-server.6.1.3 on 4.13 is now installable. Current state is: passing
• dns-server.6.1.3 on 4.14 is now installable. Current state is: passing
• dns-stub.6.0.0 on 4.14 had its build status changed: not available to passing
• dns-stub.6.0.1 on 4.14 had its build status changed: not available to passing
• dns-stub.6.0.2 on 4.14 had its build status changed: not available to passing
• dns-stub.6.1.0 on 4.14 had its build status changed: not available to passing
• dns-stub.6.1.1 on 4.14 had its build status changed: not available to passing
• dns-stub.6.1.2 on 4.14 had its build status changed: not available to passing
• dns-stub.6.1.3 on 4.08 is now installable. Current state is: passing
• dns-stub.6.1.3 on 4.09 is now installable. Current state is: passing
• dns-stub.6.1.3 on 4.10 is now installable. Current state is: passing
• dns-stub.6.1.3 on 4.11 is now installable. Current state is: passing
• dns-stub.6.1.3 on 4.12 is now installable. Current state is: passing
• dns-stub.6.1.3 on 4.13 is now installable. Current state is: passing
• dns-stub.6.1.3 on 4.14 is now installable. Current state is: passing
• dns-tsig.4.0.0 on 4.14 had its build status changed: not available to passing
• dns-tsig.4.1.0 on 4.14 had its build status changed: not available to passing
• dns-tsig.4.2.0 on 4.14 had its build status changed: not available to passing
• dns-tsig.4.3.0 on 4.14 had its build status changed: not available to passing
• dns-tsig.4.3.1 on 4.14 had its build status changed: not available to passing
• dns-tsig.6.1.3 on 4.08 is now installable. Current state is: passing
• dns-tsig.6.1.3 on 4.09 is now installable. Current state is: passing
• dns-tsig.6.1.3 on 4.10 is now installable. Current state is: passing
• dns-tsig.6.1.3 on 4.11 is now installable. Current state is: passing
• dns-tsig.6.1.3 on 4.12 is now installable. Current state is: passing
• dns-tsig.6.1.3 on 4.13 is now installable. Current state is: passing
• dns-tsig.6.1.3 on 4.14 is now installable. Current state is: passing
• dns.6.1.3 on 4.08 is now installable. Current state is: passing
• dns.6.1.3 on 4.09 is now installable. Current state is: passing
• dns.6.1.3 on 4.10 is now installable. Current state is: passing
• dns.6.1.3 on 4.11 is now installable. Current state is: passing
• dns.6.1.3 on 4.12 is now installable. Current state is: passing
• dns.6.1.3 on 4.13 is now installable. Current state is: passing
• dns.6.1.3 on 4.14 is now installable. Current state is: passing
• dockerfile-cmd.6.0.0 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.6.1.0 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.6.1.1 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.6.2.0 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.6.3.0 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.6.4.0 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.6.6.0 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.6.6.1 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.7.0.0 on 4.14 had its build status changed: not available to passing
• dockerfile-cmd.7.1.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.3.0.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.3.1.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.6.0.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.6.1.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.6.1.1 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.6.2.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.6.3.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.6.4.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.6.6.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.6.6.1 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.7.0.0 on 4.14 had its build status changed: not available to passing
• dockerfile-opam.7.1.0 on 4.14 had its build status changed: not available to passing
• dockerfile.1.7.2 on 4.14 had its build status changed: not available to passing
• dockerfile.2.0.0 on 4.14 had its build status changed: not available to passing
• dockerfile.2.2.0 on 4.14 had its build status changed: not available to passing
• dockerfile.2.2.1 on 4.14 had its build status changed: not available to passing
• dockerfile.2.2.2 on 4.14 had its build status changed: not available to passing
• dockerfile.2.2.3 on 4.14 had its build status changed: not available to passing
• dockerfile.6.0.0 on 4.14 had its build status changed: not available to passing
• dockerfile.6.1.0 on 4.14 had its build status changed: not available to passing
• dockerfile.6.1.1 on 4.14 had its build status changed: not available to passing
• dockerfile.6.2.0 on 4.14 had its build status changed: not available to passing
• dockerfile.6.3.0 on 4.14 had its build status changed: not available to passing
• dockerfile.6.4.0 on 4.14 had its build status changed: not available to passing
• dockerfile.6.6.0 on 4.14 had its build status changed: not available to passing
• dockerfile.6.6.1 on 4.14 had its build status changed: not available to passing
• dockerfile.7.0.0 on 4.14 had its build status changed: not available to passing
• dockerfile.7.1.0 on 4.14 had its build status changed: not available to passing
• docteur-unix.0.0.2 on 4.14 had its build status changed: not available to passing
• docteur.0.0.2 on 4.14 had its build status changed: not available to passing
• doi2bib.0.1.4 on 4.14 had its build status changed: not available to passing
• doi2bib.0.2.1 on 4.14 had its build status changed: not available to passing
• doi2bib.0.3.0 on 4.14 had its build status changed: not available to passing
• doi2bib.0.3.1 on 4.14 had its build status changed: not available to passing
• doi2bib.0.4.0 on 4.14 had its build status changed: not available to passing
• doi2bib.0.5.1 on 4.14 had its build status changed: not available to passing
• doi2bib.0.5.2 on 4.08 is now installable. Current state is: passing
• doi2bib.0.5.2 on 4.09 is now installable. Current state is: passing
• doi2bib.0.5.2 on 4.10 is now installable. Current state is: passing
• doi2bib.0.5.2 on 4.11 is now installable. Current state is: passing
• doi2bib.0.5.2 on 4.12 is now installable. Current state is: passing
• doi2bib.0.5.2 on 4.13 is now installable. Current state is: passing
• doi2bib.0.5.2 on 4.14 is now installable. Current state is: passing
• dokeysto.1.0.1 on 4.14 had its build status changed: not available to passing
• dokeysto.2.0.0 on 4.14 had its build status changed: not available to passing
• dokeysto.3.0.1 on 4.14 had its build status changed: not available to passing
• dokeysto.3.0.2 on 4.14 had its build status changed: not available to passing
• dokeysto.4.0.0 on 4.14 had its build status changed: not available to passing
• dokeysto_camltc.3.0.1 on 4.14 had its build status changed: not available to passing
• dokeysto_camltc.3.0.2 on 4.14 had its build status changed: not available to passing
• dokeysto_camltc.4.0.0 on 4.14 had its build status changed: not available to passing
• dokeysto_lz4.2.0.0 on 4.14 had its build status changed: not available to passing
• dokeysto_lz4.2.0.1 on 4.14 had its build status changed: not available to passing
• dokeysto_lz4.3.0.2 on 4.14 had its build status changed: not available to passing
• dokeysto_lz4.4.0.0 on 4.14 had its build status changed: not available to passing
• dream-cli.0.1.0 on 4.14 had its build status changed: not available to passing
• dream-encoding.0.1.0 on 4.14 had its build status changed: not available to passing
• dream-livereload.0.1.0 on 4.14 had its build status changed: not available to passing
• dream-serve.1.0.0 on 4.14 had its build status changed: not available to passing
• dream.1.0.0~alpha1 on 4.14 had its build status changed: not available to passing
• dream.1.0.0~alpha2 on 4.14 had its build status changed: not available to passing
• dropbox.0.2 on 4.14 had its build status changed: not available to passing
• dropbox_lwt_unix.0.2 on 4.14 had its build status changed: not available to passing
• dune-expand.0.0.1 on 4.11 is now installable. Current state is: passing
• dune-expand.0.0.1 on 4.12 is now installable. Current state is: passing
• dune-expand.0.0.1 on 4.13 is now installable. Current state is: passing
• dune-expand.0.0.1 on 4.14 is now installable. Current state is: passing
• dune-release.1.3.0 on 4.14 had its build status changed: not available to passing
• dune-release.1.3.1 on 4.14 had its build status changed: not available to passing
• dune-release.1.3.2 on 4.14 had its build status changed: not available to passing
• dune-release.1.3.3 on 4.14 had its build status changed: not available to passing
• dune-release.1.4.0 on 4.14 had its build status changed: not available to passing
• dune-release.1.5.0 on 4.14 had its build status changed: not available to passing
• dune-release.1.5.1 on 4.14 had its build status changed: not available to passing
• dune-release.1.5.2 on 4.14 had its build status changed: not available to passing
• easy_logging_yojson.0.8.1 on 4.14 had its build status changed: not available to passing
• easy_logging_yojson.0.8.2 on 4.14 had its build status changed: not available to passing
• ecaml.v0.14.0 on 4.14 had its build status changed: not available to passing
• ego.0.0.5 on 4.14 had its build status changed: not available to passing
• ego.0.0.6 on 4.14 had its build status changed: not available to passing
• elasticsearch-cli.0.5 on 4.14 had its build status changed: not available to passing
• elasticsearch-cli.1.0 on 4.14 had its build status changed: not available to passing
• elasticsearch-cli.1.1 on 4.14 had its build status changed: not available to passing
• elasticsearch-cli.1.2 on 4.14 had its build status changed: not available to passing
• electrod.0.2.3 on 4.14 had its build status changed: not available to passing
• electrod.0.3.2 on 4.14 had its build status changed: not available to passing
• electrod.0.4.1 on 4.14 had its build status changed: not available to passing
• electrod.0.5 on 4.14 had its build status changed: not available to passing
• electrod.0.6 on 4.14 had its build status changed: not available to passing
• electrod.0.6.2 on 4.14 had its build status changed: not available to passing
• electrod.0.7.1 on 4.14 had its build status changed: not available to passing
• electrod.0.8.0 on 4.14 had its build status changed: not available to passing
• electrod.0.9.0 on 4.14 had its build status changed: not available to passing
• electrod.1.0.0 on 4.14 had its build status changed: not available to passing
• eliom.9.3.0 on 4.08 is now installable. Current state is: passing
• eliom.9.3.0 on 4.09 is now installable. Current state is: passing
• eliom.9.3.0 on 4.10 is now installable. Current state is: passing
• eliom.9.3.0 on 4.11 is now installable. Current state is: passing
• eliom.9.3.0 on 4.12 is now installable. Current state is: passing
• eliom.9.3.0 on 4.13 is now installable. Current state is: passing
• email_message.v0.14.0 on 4.14 had its build status changed: not available to passing
• embedded_ocaml_templates.0.1.4 on 4.14 had its build status changed: not available to passing
• embedded_ocaml_templates.0.2 on 4.14 had its build status changed: not available to passing
• embedded_ocaml_templates.0.7 on 4.14 had its build status changed: not available to passing
• erlang.0.0.14 on 4.14 had its build status changed: not available to passing
• erssical.1.1.0 on 4.12 is now installable. Current state is: passing
• erssical.1.1.0 on 4.13 is now installable. Current state is: passing
• erssical.1.1.0 on 4.14 is now installable. Current state is: passing
• esgg.20190322 on 4.14 had its build status changed: not available to passing
• ethernet.1.0.0 on 4.14 had its build status changed: not available to passing
• ethernet.2.0.0 on 4.14 had its build status changed: not available to passing
• ethernet.2.1.0 on 4.14 had its build status changed: not available to passing
• ethernet.2.2.0 on 4.14 had its build status changed: not available to passing
• ethernet.2.2.1 on 4.14 had its build status changed: not available to passing
• ethernet.3.0.0 on 4.08 is now installable. Current state is: passing
• ethernet.3.0.0 on 4.09 is now installable. Current state is: passing
• ethernet.3.0.0 on 4.10 is now installable. Current state is: passing
• ethernet.3.0.0 on 4.11 is now installable. Current state is: passing
• ethernet.3.0.0 on 4.12 is now installable. Current state is: passing
• ethernet.3.0.0 on 4.13 is now installable. Current state is: passing
• ethernet.3.0.0 on 4.14 is now installable. Current state is: passing
• expect.0.0.6 on 4.13 had its build status changed: not available to passing
• expect_test_helpers_async.v0.14.0 on 4.14 had its build status changed: not available to passing
• expect_test_helpers_core.v0.14.0 on 4.14 had its build status changed: not available to passing
• extunix.0.3.1 on 4.14 had its build status changed: not available to passing
• extunix.0.3.2 on 4.14 had its build status changed: not available to passing
• ez_api.1.0.0 on 4.08 is now installable. Current state is: passing
• ez_api.1.0.0 on 4.09 is now installable. Current state is: passing
• ez_api.1.0.0 on 4.10 is now installable. Current state is: passing
• ez_api.1.0.0 on 4.11 is now installable. Current state is: passing
• ez_api.1.0.0 on 4.12 is now installable. Current state is: passing
• ez_api.1.0.0 on 4.13 is now installable. Current state is: passing
• ez_api.1.0.0 on 4.14 is now installable. Current state is: passing
• ez_pgocaml.1.0.0 on 4.14 had its build status changed: not available to passing
• ez_search.0.2.1 on 4.07 is now installable. Current state is: passing
• ez_search.0.2.1 on 4.08 is now installable. Current state is: passing
• ez_search.0.2.1 on 4.09 is now installable. Current state is: passing
• ez_search.0.2.1 on 4.10 is now installable. Current state is: passing
• ez_search.0.2.1 on 4.11 is now installable. Current state is: passing
• ez_search.0.2.1 on 4.12 is now installable. Current state is: passing
• ez_search.0.2.1 on 4.13 is now installable. Current state is: passing
• ez_search.0.2.1 on 4.14 is now installable. Current state is: passing
• faraday-async.0.7.2 on 4.14 had its build status changed: not available to passing
• faraday-async.0.7.3 on 4.14 had its build status changed: not available to passing
• faraday-async.0.8.1 on 4.14 had its build status changed: not available to passing
• fasmifra.1.0.0 on 4.13 had its build status changed: not available to passing
• fasmifra.1.1.0 on 4.13 had its build status changed: not available to passing
• fat-filesystem.0.13.0 on 4.14 had its build status changed: not available to passing
• fat-filesystem.0.14.0 on 4.14 had its build status changed: not available to passing
• fat-filesystem.0.15.0 on 4.14 had its build status changed: not available to passing
• feat-core.20211224 on 4.03 is now installable. Current state is: passing
• feat-core.20211224 on 4.04 is now installable. Current state is: passing
• feat-core.20211224 on 4.05 is now installable. Current state is: passing
• feat-core.20211224 on 4.06 is now installable. Current state is: passing
• feat-core.20211224 on 4.07 is now installable. Current state is: passing
• feat-core.20211224 on 4.08 is now installable. Current state is: passing
• feat-core.20211224 on 4.09 is now installable. Current state is: passing
• feat-core.20211224 on 4.10 is now installable. Current state is: passing
• feat-core.20211224 on 4.11 is now installable. Current state is: passing
• feat-core.20211224 on 4.12 is now installable. Current state is: passing
• feat-core.20211224 on 4.13 is now installable. Current state is: passing
• feat-core.20211224 on 4.14 is now installable. Current state is: passing
• feat-core.20220101 on 4.03 is now installable. Current state is: passing
• feat-core.20220101 on 4.04 is now installable. Current state is: passing
• feat-core.20220101 on 4.05 is now installable. Current state is: passing
• feat-core.20220101 on 4.06 is now installable. Current state is: passing
• feat-core.20220101 on 4.07 is now installable. Current state is: passing
• feat-core.20220101 on 4.08 is now installable. Current state is: passing
• feat-core.20220101 on 4.09 is now installable. Current state is: passing
• feat-core.20220101 on 4.10 is now installable. Current state is: passing
• feat-core.20220101 on 4.11 is now installable. Current state is: passing
• feat-core.20220101 on 4.12 is now installable. Current state is: passing
• feat-core.20220101 on 4.13 is now installable. Current state is: passing
• feat-core.20220101 on 4.14 is now installable. Current state is: passing
• feat-num.20211224 on 4.03 is now installable. Current state is: passing
• feat-num.20211224 on 4.04 is now installable. Current state is: passing
• feat-num.20211224 on 4.05 is now installable. Current state is: passing
• feat-num.20211224 on 4.06 is now installable. Current state is: passing
• feat-num.20211224 on 4.07 is now installable. Current state is: passing
• feat-num.20211224 on 4.08 is now installable. Current state is: passing
• feat-num.20211224 on 4.09 is now installable. Current state is: passing
• feat-num.20211224 on 4.10 is now installable. Current state is: passing
• feat-num.20211224 on 4.11 is now installable. Current state is: passing
• feat-num.20211224 on 4.12 is now installable. Current state is: passing
• feat-num.20211224 on 4.13 is now installable. Current state is: passing
• feat-num.20211224 on 4.14 is now installable. Current state is: passing
• feat-num.20220101 on 4.03 is now installable. Current state is: passing
• feat-num.20220101 on 4.04 is now installable. Current state is: passing
• feat-num.20220101 on 4.05 is now installable. Current state is: passing
• feat-num.20220101 on 4.06 is now installable. Current state is: passing
• feat-num.20220101 on 4.07 is now installable. Current state is: passing
• feat-num.20220101 on 4.08 is now installable. Current state is: passing
• feat-num.20220101 on 4.09 is now installable. Current state is: passing
• feat-num.20220101 on 4.10 is now installable. Current state is: passing
• feat-num.20220101 on 4.11 is now installable. Current state is: passing
• feat-num.20220101 on 4.12 is now installable. Current state is: passing
• feat-num.20220101 on 4.13 is now installable. Current state is: passing
• feat-num.20220101 on 4.14 is now installable. Current state is: passing
• feat.20211224 on 4.03 is now installable. Current state is: passing
• feat.20211224 on 4.04 is now installable. Current state is: passing
• feat.20211224 on 4.05 is now installable. Current state is: passing
• feat.20211224 on 4.06 is now installable. Current state is: passing
• feat.20211224 on 4.07 is now installable. Current state is: passing
• feat.20211224 on 4.08 is now installable. Current state is: passing
• feat.20211224 on 4.09 is now installable. Current state is: passing
• feat.20211224 on 4.10 is now installable. Current state is: passing
• feat.20211224 on 4.11 is now installable. Current state is: passing
• feat.20211224 on 4.12 is now installable. Current state is: passing
• feat.20211224 on 4.13 is now installable. Current state is: passing
• feat.20211224 on 4.14 is now installable. Current state is: passing
• feat.20220101 on 4.03 is now installable. Current state is: passing
• feat.20220101 on 4.04 is now installable. Current state is: passing
• feat.20220101 on 4.05 is now installable. Current state is: passing
• feat.20220101 on 4.06 is now installable. Current state is: passing
• feat.20220101 on 4.07 is now installable. Current state is: passing
• feat.20220101 on 4.08 is now installable. Current state is: passing
• feat.20220101 on 4.09 is now installable. Current state is: passing
• feat.20220101 on 4.10 is now installable. Current state is: passing
• feat.20220101 on 4.11 is now installable. Current state is: passing
• feat.20220101 on 4.12 is now installable. Current state is: passing
• feat.20220101 on 4.13 is now installable. Current state is: passing
• feat.20220101 on 4.14 is now installable. Current state is: passing
• feather.0.1.0 on 4.14 had its build status changed: not available to passing
• feather.0.2.0 on 4.14 had its build status changed: not available to passing
• feather.0.3.0 on 4.14 had its build status changed: not available to passing
• feather_async.0.1.0 on 4.14 had its build status changed: not available to passing
• feather_async.0.2.0 on 4.14 had its build status changed: not available to passing
• feather_async.0.3.0 on 4.14 had its build status changed: not available to passing
• ff-bench.0.6.2 on 4.14 had its build status changed: not available to passing
• ffmpeg-av.1.1.1 on 4.08 is now installable. Current state is: passing
• ffmpeg-av.1.1.1 on 4.09 is now installable. Current state is: passing
• ffmpeg-av.1.1.1 on 4.10 is now installable. Current state is: passing
• ffmpeg-av.1.1.1 on 4.11 is now installable. Current state is: passing
• ffmpeg-av.1.1.1 on 4.12 is now installable. Current state is: passing
• ffmpeg-av.1.1.1 on 4.13 is now installable. Current state is: passing
• ffmpeg-av.1.1.1 on 4.14 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.1 on 4.08 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.1 on 4.09 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.1 on 4.10 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.1 on 4.11 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.1 on 4.12 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.1 on 4.13 is now installable. Current state is: passing
• ffmpeg-avcodec.1.1.1 on 4.14 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.1 on 4.08 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.1 on 4.09 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.1 on 4.10 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.1 on 4.11 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.1 on 4.12 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.1 on 4.13 is now installable. Current state is: passing
• ffmpeg-avdevice.1.1.1 on 4.14 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.1 on 4.08 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.1 on 4.09 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.1 on 4.10 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.1 on 4.11 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.1 on 4.12 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.1 on 4.13 is now installable. Current state is: passing
• ffmpeg-avfilter.1.1.1 on 4.14 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.1 on 4.08 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.1 on 4.09 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.1 on 4.10 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.1 on 4.11 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.1 on 4.12 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.1 on 4.13 is now installable. Current state is: passing
• ffmpeg-avutil.1.1.1 on 4.14 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.1 on 4.08 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.1 on 4.09 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.1 on 4.10 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.1 on 4.11 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.1 on 4.12 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.1 on 4.13 is now installable. Current state is: passing
• ffmpeg-swresample.1.1.1 on 4.14 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.1 on 4.08 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.1 on 4.09 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.1 on 4.10 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.1 on 4.11 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.1 on 4.12 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.1 on 4.13 is now installable. Current state is: passing
• ffmpeg-swscale.1.1.1 on 4.14 is now installable. Current state is: passing
• ffmpeg.1.1.1 on 4.08 is now installable. Current state is: passing
• ffmpeg.1.1.1 on 4.09 is now installable. Current state is: passing
• ffmpeg.1.1.1 on 4.10 is now installable. Current state is: passing
• ffmpeg.1.1.1 on 4.11 is now installable. Current state is: passing
• ffmpeg.1.1.1 on 4.12 is now installable. Current state is: passing
• ffmpeg.1.1.1 on 4.13 is now installable. Current state is: passing
• ffmpeg.1.1.1 on 4.14 is now installable. Current state is: passing
• fiat-p256.0.1.0 on 4.14 had its build status changed: not available to passing
• finch.0.1 on 4.14 had its build status changed: not available to passing
• fit.1.0.2 on 4.08 is now installable. Current state is: passing
• fit.1.0.2 on 4.09 is now installable. Current state is: passing
• fit.1.0.2 on 4.10 is now installable. Current state is: passing
• fit.1.0.2 on 4.11 is now installable. Current state is: passing
• fit.1.0.2 on 4.12 is now installable. Current state is: passing
• fit.1.0.2 on 4.13 is now installable. Current state is: passing
• fit.1.0.2 on 4.14 is now installable. Current state is: passing
• fix.20211231 on 4.03 is now installable. Current state is: passing
• fix.20211231 on 4.04 is now installable. Current state is: passing
• fix.20211231 on 4.05 is now installable. Current state is: passing
• fix.20211231 on 4.06 is now installable. Current state is: passing
• fix.20211231 on 4.07 is now installable. Current state is: passing
• fix.20211231 on 4.08 is now installable. Current state is: passing
• fix.20211231 on 4.09 is now installable. Current state is: passing
• fix.20211231 on 4.10 is now installable. Current state is: passing
• fix.20211231 on 4.11 is now installable. Current state is: passing
• fix.20211231 on 4.12 is now installable. Current state is: passing
• fix.20211231 on 4.13 is now installable. Current state is: passing
• fix.20211231 on 4.14 is now installable. Current state is: passing
• fmlib.0.1.0 on 4.14 had its build status changed: not available to passing
• fmlib.0.2.0 on 4.14 had its build status changed: not available to passing
• fmlib.0.3.0 on 4.14 had its build status changed: not available to passing
• fmlib.0.3.1 on 4.14 had its build status changed: not available to passing
• fmlib.0.4.0 on 4.08 is now installable. Current state is: passing
• fmlib.0.4.0 on 4.09 is now installable. Current state is: passing
• fmlib.0.4.0 on 4.10 is now installable. Current state is: passing
• fmlib.0.4.0 on 4.11 is now installable. Current state is: passing
• fmlib.0.4.0 on 4.12 is now installable. Current state is: passing
• fmlib.0.4.0 on 4.13 is now installable. Current state is: passing
• fmlib.0.4.0 on 4.14 is now installable. Current state is: passing
• fmlib_js.0.4.0 on 4.08 is now installable. Current state is: passing
• fmlib_js.0.4.0 on 4.09 is now installable. Current state is: passing
• fmlib_js.0.4.0 on 4.10 is now installable. Current state is: passing
• fmlib_js.0.4.0 on 4.11 is now installable. Current state is: passing
• fmlib_js.0.4.0 on 4.12 is now installable. Current state is: passing
• fmlib_js.0.4.0 on 4.13 is now installable. Current state is: passing
• fmlib_parse.0.3.0 on 4.14 had its build status changed: not available to passing
• fmlib_parse.0.3.1 on 4.14 had its build status changed: not available to passing
• fmlib_parse.0.4.0 on 4.08 is now installable. Current state is: passing
• fmlib_parse.0.4.0 on 4.09 is now installable. Current state is: passing
• fmlib_parse.0.4.0 on 4.10 is now installable. Current state is: passing
• fmlib_parse.0.4.0 on 4.11 is now installable. Current state is: passing
• fmlib_parse.0.4.0 on 4.12 is now installable. Current state is: passing
• fmlib_parse.0.4.0 on 4.13 is now installable. Current state is: passing
• fmlib_parse.0.4.0 on 4.14 is now installable. Current state is: passing
• fmlib_pretty.0.3.0 on 4.14 had its build status changed: not available to passing
• fmlib_pretty.0.3.1 on 4.14 had its build status changed: not available to passing
• fmlib_pretty.0.4.0 on 4.08 is now installable. Current state is: passing
• fmlib_pretty.0.4.0 on 4.09 is now installable. Current state is: passing
• fmlib_pretty.0.4.0 on 4.10 is now installable. Current state is: passing
• fmlib_pretty.0.4.0 on 4.11 is now installable. Current state is: passing
• fmlib_pretty.0.4.0 on 4.12 is now installable. Current state is: passing
• fmlib_pretty.0.4.0 on 4.13 is now installable. Current state is: passing
• fmlib_pretty.0.4.0 on 4.14 is now installable. Current state is: passing
• fmlib_std.0.3.0 on 4.14 had its build status changed: not available to passing
• fmlib_std.0.3.1 on 4.14 had its build status changed: not available to passing
• fmlib_std.0.4.0 on 4.08 is now installable. Current state is: passing
• fmlib_std.0.4.0 on 4.09 is now installable. Current state is: passing
• fmlib_std.0.4.0 on 4.10 is now installable. Current state is: passing
• fmlib_std.0.4.0 on 4.11 is now installable. Current state is: passing
• fmlib_std.0.4.0 on 4.12 is now installable. Current state is: passing
• fmlib_std.0.4.0 on 4.13 is now installable. Current state is: passing
• fmlib_std.0.4.0 on 4.14 is now installable. Current state is: passing
• frenetic.5.0.5 on 4.14 had its build status changed: not available to passing
• fromager.0.4.0 on 4.14 had its build status changed: not available to passing
• fromager.0.5.0 on 4.08 is now installable. Current state is: passing
• fromager.0.5.0 on 4.09 is now installable. Current state is: passing
• fromager.0.5.0 on 4.10 is now installable. Current state is: passing
• fromager.0.5.0 on 4.11 is now installable. Current state is: passing
• fromager.0.5.0 on 4.12 is now installable. Current state is: passing
• fromager.0.5.0 on 4.13 is now installable. Current state is: passing
• fromager.0.5.0 on 4.14 is now installable. Current state is: passing
• fsml.0.2.1 on 4.14 had its build status changed: not available to passing
• fsml.0.3.0 on 4.14 had its build status changed: not available to passing
• gdbprofiler.0.4 on 4.14 had its build status changed: not available to passing
• gen-bs.0.0.0 on 4.13 had its build status changed: