Home|Differences with the last checks|Previous runs

Differences between 7af4b29 and acdf0fd (git diff)

Packages now failing:

• DrawGrammar.0.1.0 on 4.02 had its build status changed: partially failing to failing
• DrawGrammar.0.1.0 on 4.03 had its build status changed: partially failing to failing
• DrawGrammar.0.1.0 on 4.04 had its build status changed: partially failing to failing
• DrawGrammar.0.1.0 on 4.05 had its build status changed: partially failing to failing
• DrawGrammar.0.2.0 on 4.02 had its build status changed: partially failing to failing
• DrawGrammar.0.2.0 on 4.03 had its build status changed: partially failing to failing
• DrawGrammar.0.2.0 on 4.05 had its build status changed: partially failing to failing
• ISO8601.0.2.6 on 5.0 is now installable. Current state is: failing
• angstrom-unix.0.11.1 on 5.0 is now installable. Current state is: failing
• angstrom-unix.0.11.2 on 5.0 is now installable. Current state is: failing
• angstrom-unix.0.12.1 on 5.0 is now installable. Current state is: failing
• angstrom-unix.0.13.0 on 5.0 is now installable. Current state is: failing
• angstrom-unix.0.14.0 on 5.0 is now installable. Current state is: failing
• angstrom-unix.0.14.1 on 5.0 is now installable. Current state is: failing
• angstrom-unix.0.15.0 on 5.0 is now installable. Current state is: failing
• aws-s3.4.1.0 on 4.05 had its build status changed: passing to failing
• aws-s3.4.1.0 on 4.06 had its build status changed: passing to failing
• aws-s3.4.1.0 on 4.07 had its build status changed: passing to failing
• aws-s3.4.2.0 on 4.05 had its build status changed: passing to failing
• aws-s3.4.2.0 on 4.06 had its build status changed: passing to failing
• aws-s3.4.2.0 on 4.07 had its build status changed: passing to failing
• aws-s3.4.3.0 on 4.05 had its build status changed: passing to failing
• aws-s3.4.3.0 on 4.06 had its build status changed: passing to failing
• aws-s3.4.3.0 on 4.07 had its build status changed: passing to failing
• aws-s3.4.4.0 on 4.07 had its build status changed: passing to failing
• aws-s3.4.4.1 on 4.07 had its build status changed: passing to failing
• aws-s3.4.5.1 on 4.07 had its build status changed: passing 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
• bark.0.1.3 on 5.0 is now installable. Current state is: failing
• bark.0.1.4 on 5.0 is now installable. Current state is: failing
• benchmark.1.6 on 5.0 is now installable. Current state is: failing
• bigstring-unix.0.3 on 5.0 is now installable. Current state is: failing
• bigstringaf.0.5.0 on 5.0 is now installable. Current state is: failing
• bigstringaf.0.5.2 on 5.0 is now installable. Current state is: failing
• bigstringaf.0.5.3 on 5.0 is now installable. Current state is: failing
• bimage.0.1 on 5.0 is now installable. Current state is: failing
• bimage.0.1.1 on 5.0 is now installable. Current state is: failing
• bimage.0.1.2 on 5.0 is now installable. Current state is: failing
• bimage.0.2.1 on 5.0 is now installable. Current state is: failing
• bimage.0.3.0 on 5.0 is now installable. Current state is: failing
• bimage.0.3.1 on 5.0 is now installable. Current state is: failing
• bimage.0.4.0 on 5.0 is now installable. Current state is: failing
• bimage.0.5.0 on 5.0 is now installable. Current state is: failing
• bimage.0.6.0 on 5.0 is now installable. Current state is: failing
• biniou.1.2.1 on 5.0 is now installable. Current state is: failing
• binsec.0.3 on 4.04 had its build status changed: passing to failing
• bisect_ppx.2.6.0 on 5.0 is now installable. Current state is: failing
• bisect_ppx.2.7.0 on 5.0 is now installable. Current state is: failing
• bisect_ppx.2.7.1 on 5.0 is now installable. Current state is: failing
• bisect_ppx.2.8.0 on 5.0 is now installable. Current state is: failing
• bisect_ppx.2.8.1 on 5.0 is now installable. Current state is: failing
• bitstring.4.0.0 on 5.0 is now installable. Current state is: failing
• bitstring.4.0.1 on 5.0 is now installable. Current state is: failing
• bitstring.4.1.0 on 5.0 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.02 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.03 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.04 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.05 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.06 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.07 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.08 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.09 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.10 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.11 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.12 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.13 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.14 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 5.0 is now installable. Current state is: failing
• blake3.0.1 on 4.09 had its build status changed: passing to failing
• blake3.0.1 on 4.10 had its build status changed: passing to failing
• blake3.0.1 on 4.11 had its build status changed: passing to failing
• blake3.0.1 on 4.12 had its build status changed: passing to failing
• blake3.0.1 on 4.13 had its build status changed: passing to failing
• blake3.0.1 on 4.14 is now installable. Current state is: failing
• blake3.0.1 on 5.0 is now installable. Current state is: failing
• boltzgen.0.9 on 5.0 is now installable. Current state is: failing
• boltzgen.0.9.2 on 5.0 is now installable. Current state is: failing
• boltzgen.0.9.3 on 5.0 is now installable. Current state is: failing
• camlidl.1.05 on 5.0 is now installable. Current state is: failing
• camlidl.1.07 on 5.0 is now installable. Current state is: failing
• camlidl.1.09 on 5.0 is now installable. Current state is: failing
• camlmix.1.3.0 on 5.0 is now installable. Current state is: failing
• camlon.3.0.0 on 5.0 is now installable. Current state is: failing
• camlrack.0.10.1 on 5.0 is now installable. Current state is: failing
• camltc.0.9.3 on 4.02 had its build status changed: passing to failing
• camltc.0.9.3 on 4.03 had its build status changed: passing to failing
• camltc.0.9.3 on 4.04 had its build status changed: passing to failing
• camltc.0.9.3 on 4.05 had its build status changed: passing to failing
• camltc.0.9.4 on 4.02 had its build status changed: passing to failing
• camltc.0.9.4 on 4.03 had its build status changed: passing to failing
• camltc.0.9.4 on 4.04 had its build status changed: passing to failing
• camltc.0.9.4 on 4.05 had its build status changed: passing to failing
• camltc.0.9.5 on 4.02 had its build status changed: passing to failing
• camltc.0.9.5 on 4.03 had its build status changed: passing to failing
• camltc.0.9.5 on 4.04 had its build status changed: passing to failing
• camltc.0.9.5 on 4.05 had its build status changed: passing to failing
• camltc.0.9.6 on 4.02 had its build status changed: passing to failing
• camltc.0.9.6 on 4.03 had its build status changed: passing to failing
• camltc.0.9.6 on 4.04 had its build status changed: passing to failing
• camltc.0.9.6 on 4.05 had its build status changed: passing to failing
• camltc.0.9.6 on 4.06 had its build status changed: passing to failing
• camltc.0.9.6 on 4.07 had its build status changed: passing to failing
• camomile.1.0.2 on 5.0 is now installable. Current state is: failing
• capnp-rpc-net.1.1 on 4.08 is now installable. Current state is: failing
• capnp-rpc-net.1.1 on 4.09 is now installable. Current state is: failing
• capnp-rpc-net.1.1 on 4.10 is now installable. Current state is: failing
• capnp-rpc-net.1.1 on 4.11 is now installable. Current state is: failing
• capnp-rpc-net.1.1 on 4.12 is now installable. Current state is: failing
• capnp-rpc-net.1.1 on 4.13 is now installable. Current state is: failing
• capnp-rpc-net.1.2 on 4.08 is now installable. Current state is: failing
• capnp-rpc-net.1.2 on 4.09 is now installable. Current state is: failing
• capnp-rpc-net.1.2 on 4.10 is now installable. Current state is: failing
• capnp-rpc-net.1.2 on 4.11 is now installable. Current state is: failing
• capnp-rpc-net.1.2 on 4.12 is now installable. Current state is: failing
• capnp-rpc-net.1.2 on 4.13 is now installable. Current state is: failing
• catapult.0.1 on 5.0 is now installable. Current state is: failing
• cdrom.0.9.4 on 5.0 is now installable. Current state is: failing
• cfstream.1.2.1 on 4.03 had its build status changed: passing to failing
• cfstream.1.2.1 on 4.04 had its build status changed: passing to failing
• cfstream.1.2.1 on 4.05 had its build status changed: passing to failing
• cfstream.1.2.2 on 4.03 had its build status changed: passing to failing
• cfstream.1.2.2 on 4.04 had its build status changed: passing to failing
• cfstream.1.2.2 on 4.05 had its build status changed: passing to failing
• cinaps.v0.14.0 on 5.0 is now installable. Current state is: failing
• cinaps.v0.15.0 on 5.0 is now installable. Current state is: failing
• cinaps.v0.15.1 on 5.0 is now installable. Current state is: failing
• coclobas.0.0.0 on 4.03 had its build status changed: passing to failing
• coclobas.0.0.0 on 4.04 had its build status changed: passing to failing
• coclobas.0.0.1 on 4.03 had its build status changed: passing to failing
• coclobas.0.0.1 on 4.04 had its build status changed: passing to failing
• coclobas.0.0.2 on 4.03 had its build status changed: passing to failing
• coclobas.0.0.2 on 4.04 had its build status changed: passing to failing
• cohttp-lwt-jsoo.2.1.3 on 4.08 had its build status changed: passing to failing
• coin.0.1.0 on 4.08 had its build status changed: passing to failing
• coin.0.1.1 on 4.08 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
• conex.0.10.0 on 5.0 is now installable. Current state is: failing
• conex.0.10.1 on 5.0 is now installable. Current state is: failing
• conex.0.11.0 on 5.0 is now installable. Current state is: failing
• conex.0.11.1 on 5.0 is now installable. Current state is: failing
• conf-libclang.12 on 4.02 had its build status changed: passing to failing
• conf-libclang.12 on 4.03 had its build status changed: passing to failing
• conf-libclang.12 on 4.04 had its build status changed: passing to failing
• conf-libclang.12 on 4.05 had its build status changed: passing to failing
• conf-libclang.12 on 4.06 had its build status changed: passing to failing
• conf-libclang.12 on 4.07 had its build status changed: passing to failing
• conf-libclang.12 on 4.08 had its build status changed: passing to failing
• conf-libclang.12 on 4.09 had its build status changed: passing to failing
• conf-libclang.12 on 4.10 had its build status changed: passing to failing
• conf-libclang.12 on 4.11 had its build status changed: passing to failing
• conf-libclang.12 on 4.12 had its build status changed: passing to failing
• conf-libclang.12 on 4.13 had its build status changed: passing to failing
• conf-libclang.12 on 4.14 is now installable. Current state is: failing
• conf-libclang.12 on 5.0 is now installable. Current state is: failing
• conf-npm.1 on 4.02 had its build status changed: passing to failing
• conf-npm.1 on 4.03 had its build status changed: passing to failing
• conf-npm.1 on 4.04 had its build status changed: passing to failing
• conf-npm.1 on 4.05 had its build status changed: passing to failing
• conf-npm.1 on 4.06 had its build status changed: passing to failing
• conf-npm.1 on 4.07 had its build status changed: passing to failing
• conf-npm.1 on 4.08 had its build status changed: passing to failing
• conf-npm.1 on 4.09 had its build status changed: passing to failing
• conf-npm.1 on 4.10 had its build status changed: passing to failing
• conf-npm.1 on 4.11 had its build status changed: passing to failing
• conf-npm.1 on 4.12 had its build status changed: passing to failing
• conf-npm.1 on 4.13 had its build status changed: passing to failing
• conf-npm.1 on 4.14 is now installable. Current state is: failing
• conf-npm.1 on 5.0 is now installable. Current state is: failing
• coq.8.11.0 on 4.07 had its build status changed: passing to failing
• coq.8.13.0 on 4.06 had its build status changed: passing to failing
• coq.8.7.0 on 4.05 had its build status changed: passing to failing
• cpdf.2.2.1 on 4.02 had its build status changed: passing to failing
• cpdf.2.2.1 on 4.03 had its build status changed: passing to failing
• cpdf.2.2.1 on 4.04 had its build status changed: passing to failing
• cpdf.2.2.1 on 4.05 had its build status changed: passing to failing
• cppo.1.6.6 on 5.0 is now installable. Current state is: failing
• cppo.1.6.7 on 5.0 is now installable. Current state is: failing
• cppo.1.6.8 on 5.0 is now installable. Current state is: failing
• cppo.1.6.9 on 5.0 is now installable. Current state is: failing
• crontab.0.1 on 5.0 is now installable. Current state is: failing
• crunch.2.2.0 on 5.0 is now installable. Current state is: failing
• cry.0.6.5 on 5.0 is now installable. Current state is: failing
• cry.0.6.6 on 5.0 is now installable. Current state is: failing
• cry.0.6.7 on 5.0 is now installable. Current state is: failing
• cstruct-unix.5.0.0 on 5.0 is now installable. Current state is: failing
• cstruct-unix.5.1.1 on 5.0 is now installable. Current state is: failing
• cstruct-unix.5.2.0 on 5.0 is now installable. Current state is: failing
• cstruct-unix.6.0.0 on 5.0 is now installable. Current state is: failing
• cstruct-unix.6.0.1 on 5.0 is now installable. Current state is: failing
• cstruct.4.0.0 on 5.0 is now installable. Current state is: failing
• curly.0.2.0 on 5.0 is now installable. Current state is: failing
• datakit-client-9p.0.12.0 on 4.12 had its build status changed: passing to failing
• datakit-client-9p.0.12.0 on 4.13 had its build status changed: not available to failing
• datakit-client-9p.0.12.2 on 4.08 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.09 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.10 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.11 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.12 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.13 had its build status changed: not available to failing
• datakit-client-9p.0.12.3 on 4.08 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.09 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.10 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.11 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.12 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.13 had its build status changed: not available to failing
• datakit-client-9p.1.0.0 on 4.08 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.09 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.10 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.11 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.12 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.13 had its build status changed: not available to failing
• datalog.0.6 on 5.0 is now installable. Current state is: failing
• depyt.0.2.0 on 4.12 had its build status changed: passing to failing
• depyt.0.2.0 on 4.13 had its build status changed: passing to failing
• directories.0.2 on 5.0 is now installable. Current state is: failing
• directories.0.3 on 5.0 is now installable. Current state is: failing
• directories.0.4 on 5.0 is now installable. Current state is: failing
• directories.0.5 on 5.0 is now installable. Current state is: failing
• distributed.0.6.0 on 5.0 is now installable. Current state is: failing
• diy.5.01 on 5.0 is now installable. Current state is: failing
• dolog.4.0.0 on 5.0 is now installable. Current state is: failing
• dolog.6.0.0 on 5.0 is now installable. Current state is: failing
• domainslib.0.3.0 on 5.0 is now installable. Current state is: failing
• domainslib.0.3.1 on 5.0 is now installable. Current state is: failing
• domainslib.0.4.0 on 5.0 is now installable. Current state is: failing
• domainslib.0.4.1 on 5.0 is now installable. Current state is: failing
• dtools.0.4.2 on 5.0 is now installable. Current state is: failing
• dtools.0.4.3 on 5.0 is now installable. Current state is: failing
• dtools.0.4.4 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.7.0 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.7.1 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.8.0 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.8.1 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.8.2 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.8.4 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.8.5 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.9.0 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.9.1 on 5.0 is now installable. Current state is: failing
• dune-configurator.2.9.3 on 5.0 is now installable. Current state is: failing
• dune-configurator.3.0.2 on 5.0 is now installable. Current state is: failing
• dune-configurator.3.0.3 on 5.0 is now installable. Current state is: failing
• dune-configurator.3.1.0 on 5.0 is now installable. Current state is: failing
• dune-configurator.3.1.1 on 5.0 is now installable. Current state is: failing
• dune-configurator.3.2.0 on 5.0 is now installable. Current state is: failing
• dune-private-libs.2.9.3 on 5.0 is now installable. Current state is: failing
• dune-release.1.1.0 on 4.08 had its build status changed: passing to failing
• dune-release.1.1.0 on 4.09 had its build status changed: passing to failing
• dune-release.1.1.0 on 4.10 had its build status changed: passing to failing
• dune-release.1.1.0 on 4.11 had its build status changed: passing to failing
• dune-release.1.2.0 on 4.08 had its build status changed: passing to failing
• dune-release.1.2.0 on 4.09 had its build status changed: passing to failing
• dune-release.1.2.0 on 4.10 had its build status changed: passing to failing
• dune-release.1.2.0 on 4.11 had its build status changed: passing to failing
• earley.3.0.0 on 5.0 is now installable. Current state is: failing
• earlybird.0.1.0 on 4.06 had its build status changed: passing to failing
• earlybird.0.1.1 on 4.06 had its build status changed: passing to failing
• earlybird.0.1.1 on 4.07 had its build status changed: passing to failing
• earlybird.0.1.2 on 4.05 had its build status changed: passing to failing
• earlybird.0.1.2 on 4.06 had its build status changed: passing to failing
• earlybird.0.1.2 on 4.07 had its build status changed: passing to failing
• earlybird.0.1.3 on 4.05 had its build status changed: passing to failing
• earlybird.0.1.3 on 4.06 had its build status changed: passing to failing
• earlybird.0.1.3 on 4.07 had its build status changed: passing to failing
• earlybird.0.1.4 on 4.05 had its build status changed: passing to failing
• earlybird.0.1.4 on 4.06 had its build status changed: passing to failing
• earlybird.0.1.4 on 4.07 had its build status changed: passing to failing
• easy-format.1.3.2 on 5.0 is now installable. Current state is: failing
• easy_logging.0.4 on 5.0 is now installable. Current state is: failing
• easy_logging.0.5 on 5.0 is now installable. Current state is: failing
• easy_logging.0.5.2 on 5.0 is now installable. Current state is: failing
• facile.1.1 on 5.0 is now installable. Current state is: failing
• farmhash.0.4 on 5.0 is now installable. Current state is: failing
• fat-filesystem.0.6.2 on 4.02 had its build status changed: internal failure to failing
• fat-filesystem.0.6.2 on 4.03 had its build status changed: passing to failing
• fat-filesystem.0.6.2 on 4.04 had its build status changed: passing to failing
• fd-send-recv.2.0.1 on 5.0 is now installable. Current state is: failing
• frama-c.22.0 on 4.08 had its build status changed: passing to failing
• frama-c.22.0 on 4.09 had its build status changed: passing to failing
• frama-c.22.0 on 4.10 had its build status changed: passing to failing
• frama-c.22.0 on 4.11 had its build status changed: passing to failing
• frama-c.22.0 on 4.12 had its build status changed: passing to failing
• frama-c.22.0 on 4.13 had its build status changed: passing to failing
• frama-c.22.0 on 4.14 is now installable. Current state is: failing
• fstar.0.9.6.0 on 4.04 had its build status changed: passing to failing
• fstar.0.9.6.0 on 4.05 had its build status changed: passing to failing
• fstar.0.9.6.0 on 4.06 had its build status changed: passing to failing
• fstar.0.9.6.0 on 4.07 had its build status changed: passing to failing
• fstar.0.9.6.0~alpha1 on 4.04 had its build status changed: passing to failing
• fstar.0.9.6.0~alpha1 on 4.05 had its build status changed: passing to failing
• fstar.0.9.6.0~alpha1 on 4.06 had its build status changed: passing to failing
• fstar.0.9.7.0-alpha1 on 4.04 had its build status changed: passing to failing
• fstar.0.9.7.0-alpha1 on 4.05 had its build status changed: passing to failing
• fstar.0.9.7.0-alpha1 on 4.06 had its build status changed: passing to failing
• fstar.0.9.7.0-alpha1 on 4.07 had its build status changed: passing to failing
• functoria-runtime.2.0.0 on 4.08 had its build status changed: passing to failing
• functoria-runtime.2.0.0 on 4.09 had its build status changed: passing to failing
• functoria-runtime.2.0.0 on 4.10 had its build status changed: passing to failing
• functoria-runtime.2.0.0 on 4.11 had its build status changed: passing to failing
• functoria-runtime.2.1.0 on 4.08 had its build status changed: passing to failing
• functoria-runtime.2.1.0 on 4.09 had its build status changed: passing to failing
• functoria-runtime.2.1.0 on 4.10 had its build status changed: passing to failing
• functoria-runtime.2.1.0 on 4.11 had its build status changed: passing to failing
• functoria-runtime.2.2.0 on 4.08 had its build status changed: passing to failing
• functoria-runtime.2.2.0 on 4.09 had its build status changed: passing to failing
• functoria-runtime.2.2.0 on 4.10 had its build status changed: passing to failing
• functoria-runtime.2.2.0 on 4.11 had its build status changed: passing to failing
• functoria-runtime.2.2.1 on 4.08 had its build status changed: passing to failing
• functoria-runtime.2.2.1 on 4.09 had its build status changed: passing to failing
• functoria-runtime.2.2.1 on 4.10 had its build status changed: passing to failing
• functoria-runtime.2.2.1 on 4.11 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.12 had its build status changed: passing to failing
• genprint.0.3 on 4.04 is now installable. Current state is: failing
• genprint.0.3 on 4.05 is now installable. Current state is: failing
• genprint.0.3 on 4.06 is now installable. Current state is: failing
• genprint.0.3 on 4.07 is now installable. Current state is: failing
• genprint.0.3 on 4.08 is now installable. Current state is: failing
• genprint.0.3 on 4.09 is now installable. Current state is: failing
• genprint.0.3 on 4.10 is now installable. Current state is: failing
• genspio.0.0.0 on 4.03 had its build status changed: passing to failing
• genspio.0.0.0 on 4.04 had its build status changed: passing to failing
• genspio.0.0.0 on 4.05 had its build status changed: passing to failing
• git-mirage.1.11.2 on 4.04 had its build status changed: partially failing to failing
• git-mirage.1.11.2 on 4.05 had its build status changed: partially failing to failing
• git-mirage.1.11.4 on 4.04 had its build status changed: partially failing to failing
• git.1.10.0 on 4.03 had its build status changed: passing to failing
• git.1.8.0 on 4.03 had its build status changed: passing to failing
• git.1.8.0 on 4.04 had its build status changed: passing to failing
• git.1.8.0 on 4.05 had its build status changed: passing to failing
• git.1.9.0 on 4.03 had its build status changed: passing to failing
• git.1.9.1 on 4.03 had its build status changed: passing to failing
• git.1.9.2 on 4.03 had its build status changed: passing to failing
• git.1.9.3 on 4.03 had its build status changed: passing to failing
• git.3.2.0 on 4.08 had its build status changed: passing to failing
• git.3.2.0 on 4.09 had its build status changed: passing to failing
• git.3.2.0 on 4.10 had its build status changed: passing to failing
• git.3.2.0 on 4.11 had its build status changed: passing to failing
• git.3.2.0 on 4.12 had its build status changed: passing to failing
• git.3.3.0 on 4.08 had its build status changed: passing to failing
• git.3.3.0 on 4.09 had its build status changed: passing to failing
• git.3.3.0 on 4.10 had its build status changed: passing to failing
• git.3.3.0 on 4.11 had its build status changed: passing to failing
• git.3.3.0 on 4.12 had its build status changed: passing to failing
• git.3.3.1 on 4.08 had its build status changed: passing to failing
• git.3.3.1 on 4.09 had its build status changed: passing to failing
• git.3.3.1 on 4.10 had its build status changed: passing to failing
• git.3.3.1 on 4.11 had its build status changed: passing to failing
• git.3.3.1 on 4.12 had its build status changed: passing to failing
• git.3.3.2 on 4.08 had its build status changed: passing to failing
• git.3.3.2 on 4.09 had its build status changed: passing to failing
• git.3.3.2 on 4.10 had its build status changed: passing to failing
• git.3.3.2 on 4.11 had its build status changed: passing to failing
• git.3.3.2 on 4.12 had its build status changed: passing to failing
• git.3.3.3 on 4.08 had its build status changed: passing to failing
• git.3.3.3 on 4.09 had its build status changed: passing to failing
• git.3.3.3 on 4.10 had its build status changed: passing to failing
• git.3.3.3 on 4.11 had its build status changed: passing to failing
• git.3.3.3 on 4.12 had its build status changed: passing to failing
• glfw-ocaml.3.2.1 on 5.0 is now installable. Current state is: failing
• glfw-ocaml.3.2.1~rc1 on 5.0 is now installable. Current state is: failing
• glfw-ocaml.3.2.1~rc2 on 5.0 is now installable. Current state is: failing
• goblint.1.0.0 on 4.05 had its build status changed: internal failure to failing
• goblint.1.0.0 on 4.06 had its build status changed: internal failure to failing
• gperftools.0.5 on 5.0 is now installable. Current state is: failing
• h2.0.1.0 on 5.0 is now installable. Current state is: failing
• h2.0.2.0 on 5.0 is now installable. Current state is: failing
• h2.0.3.0 on 5.0 is now installable. Current state is: failing
• h2.0.4.0 on 5.0 is now installable. Current state is: failing
• h2.0.5.0 on 5.0 is now installable. Current state is: failing
• h2.0.6.0 on 5.0 is now installable. Current state is: failing
• h2.0.6.1 on 5.0 is now installable. Current state is: failing
• h2.0.7.0 on 5.0 is now installable. Current state is: failing
• h2.0.8.0 on 5.0 is now installable. Current state is: failing
• hack_parallel.0.1.1 on 4.07 had its build status changed: passing to failing
• hack_parallel.0.1.1 on 4.08 had its build status changed: passing to failing
• hack_parallel.0.1.1 on 4.09 had its build status changed: passing to failing
• herdtools7.7.42 on 5.0 is now installable. Current state is: failing
• herdtools7.7.42-beta.3 on 5.0 is now installable. Current state is: failing
• herdtools7.7.43 on 5.0 is now installable. Current state is: failing
• herdtools7.7.44 on 5.0 is now installable. Current state is: failing
• herdtools7.7.45 on 5.0 is now installable. Current state is: failing
• herdtools7.7.46 on 5.0 is now installable. Current state is: failing
• herdtools7.7.47 on 5.0 is now installable. Current state is: failing
• herdtools7.7.48 on 5.0 is now installable. Current state is: failing
• herdtools7.7.49 on 5.0 is now installable. Current state is: failing
• herdtools7.7.50 on 5.0 is now installable. Current state is: failing
• herdtools7.7.51 on 5.0 is now installable. Current state is: failing
• herdtools7.7.52 on 5.0 is now installable. Current state is: failing
• hevea.2.25 on 5.0 is now installable. Current state is: failing
• hevea.2.28 on 5.0 is now installable. Current state is: failing
• hevea.2.29 on 5.0 is now installable. Current state is: failing
• hevea.2.32 on 5.0 is now installable. Current state is: failing
• hevea.2.35 on 5.0 is now installable. Current state is: failing
• hlarp.0.0.1 on 4.08 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.09 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.10 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.11 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.12 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.08 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.09 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.10 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.11 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.12 had its build status changed: passing to failing
• htmlfromtexbooks.3.3.2 on 5.0 is now installable. Current state is: failing
• http-cookie.2.0.0 on 5.0 is now installable. Current state is: failing
• hweak.1.1 on 5.0 is now installable. Current state is: failing
• imagemagick.0.34 on 4.02 had its build status changed: internal failure to failing
• imagemagick.0.34 on 4.03 had its build status changed: internal failure to failing
• imagemagick.0.34 on 4.04 had its build status changed: internal failure to failing
• imagemagick.0.34 on 4.05 had its build status changed: internal failure to failing
• inquire.0.3.0 on 5.0 is now installable. Current state is: failing
• integers.0.3.0 on 5.0 is now installable. Current state is: failing
• integers.0.4.0 on 5.0 is now installable. Current state is: failing
• integers.0.5.0 on 5.0 is now installable. Current state is: failing
• integers.0.5.1 on 5.0 is now installable. Current state is: failing
• ipaddr.5.0.0 on 5.0 is now installable. Current state is: failing
• ipaddr.5.0.1 on 5.0 is now installable. Current state is: failing
• ipaddr.5.1.0 on 5.0 is now installable. Current state is: failing
• ipaddr.5.2.0 on 5.0 is now installable. Current state is: failing
• ipaddr.5.3.0 on 5.0 is now installable. Current state is: failing
• irmin.1.3.2 on 4.12 had its build status changed: passing to failing
• irmin.1.3.2 on 4.13 had its build status changed: passing to failing
• irmin.1.4.0 on 4.12 had its build status changed: passing to failing
• irmin.1.4.0 on 4.13 had its build status changed: passing to failing
• ivy.1.2.2 on 4.02 had its build status changed: internal failure to failing
• ivy.1.2.2 on 4.03 had its build status changed: internal failure to failing
• ivy.1.2.2 on 4.04 had its build status changed: internal failure to failing
• ivy.1.2.2 on 4.05 had its build status changed: internal failure to failing
• ivy.1.3.1 on 4.02 had its build status changed: internal failure to failing
• ivy.1.3.1 on 4.03 had its build status changed: internal failure to failing
• ivy.1.3.1 on 4.04 had its build status changed: internal failure to failing
• ivy.1.3.1 on 4.05 had its build status changed: internal failure to failing
• js_of_ocaml-ocamlbuild.3.10.0 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.11.0 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.5.0 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.5.1 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.5.2 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.6.0 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.7.0 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.7.1 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.8.0 on 5.0 is now installable. Current state is: failing
• js_of_ocaml-ocamlbuild.3.9.0 on 5.0 is now installable. Current state is: failing
• jsonxt.1.0.0 on 5.0 is now installable. Current state is: failing
• jsonxt.1.0.1 on 5.0 is now installable. Current state is: failing
• jupyter.2.1.0 on 4.02 had its build status changed: passing to failing
• kappa-agents.4.1.0 on 4.08 had its build status changed: internal failure to failing
• kappa-agents.4.1.0 on 4.09 had its build status changed: internal failure to failing
• kappa-agents.4.1.0 on 4.10 had its build status changed: internal failure to failing
• kappa-agents.4.1.0 on 4.11 had its build status changed: internal failure to failing
• ketrew.3.2.1 on 4.03 had its build status changed: passing to failing
• ketrew.3.2.1 on 4.04 had its build status changed: passing to failing
• ketrew.3.2.1 on 4.05 had its build status changed: passing to failing
• lablgl.1.06 on 5.0 is now installable. Current state is: failing
• lablgtk3-extras.3.0 on 4.12 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.03 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.04 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.05 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.06 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.07 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.08 is now installable. Current state is: failing
• lablqml.0.6 on 4.04 is now installable. Current state is: failing
• lablqml.0.6 on 4.05 is now installable. Current state is: failing
• lablqml.0.6 on 4.06 is now installable. Current state is: failing
• lablqml.0.6 on 4.07 is now installable. Current state is: failing
• lablqml.0.6 on 4.08 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.04 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.05 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.06 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.07 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.08 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.09 is now installable. Current state is: failing
• landmarks.1.4 on 5.0 is now installable. Current state is: failing
• lascar.0.6-alpha on 5.0 is now installable. Current state is: failing
• lascar.0.6.0 on 5.0 is now installable. Current state is: failing
• leveldb.1.3.0 on 5.0 is now installable. Current state is: failing
• lreplay.0.1 on 5.0 is now installable. Current state is: failing
• lua-ml.0.9 on 5.0 is now installable. Current state is: failing
• lua-ml.0.9.3 on 5.0 is now installable. Current state is: failing
• lua-ml.0.9.4 on 5.0 is now installable. Current state is: failing
• luv.0.5.0 on 4.02 had its build status changed: passing to failing
• luv.0.5.0 on 4.03 had its build status changed: passing to failing
• luv.0.5.0 on 4.04 had its build status changed: passing to failing
• luv.0.5.0 on 4.05 had its build status changed: passing to failing
• luv.0.5.0 on 4.06 had its build status changed: passing to failing
• luv.0.5.0 on 4.07 had its build status changed: passing to failing
• luv.0.5.0 on 4.08 had its build status changed: passing to failing
• luv.0.5.0 on 4.09 had its build status changed: passing to failing
• luv.0.5.0 on 4.10 had its build status changed: passing to failing
• luv.0.5.0 on 4.11 had its build status changed: passing to failing
• luv.0.5.0 on 4.12 had its build status changed: passing to failing
• luv.0.5.0 on 4.13 had its build status changed: passing to failing
• luv.0.5.0 on 4.14 is now installable. Current state is: failing
• lwt-zmq.2.0.1 on 4.04 had its build status changed: passing to failing
• lwt-zmq.2.0.1 on 4.05 had its build status changed: passing to failing
• lwt-zmq.2.1.0 on 4.04 had its build status changed: passing to failing
• lwt-zmq.2.1.0 on 4.05 had its build status changed: passing to failing
• magic-mime.1.1.2 on 5.0 is now installable. Current state is: failing
• magic-mime.1.1.3 on 5.0 is now installable. Current state is: failing
• magic-mime.1.2.0 on 5.0 is now installable. Current state is: failing
• mariadb.0.10.0 on 4.07 had its build status changed: passing to failing
• mariadb.0.9.0 on 4.07 had its build status changed: passing to failing
• mariadb.1.0.0 on 4.07 had its build status changed: passing to failing
• mariadb.1.0.1 on 4.07 had its build status changed: passing to failing
• mariadb.1.1.0 on 4.07 had its build status changed: passing to failing
• mariadb.1.1.1 on 4.07 had its build status changed: passing to failing
• mariadb.1.1.2 on 4.07 had its build status changed: passing to failing
• mccs.1.1+10 on 4.02 had its build status changed: passing to failing
• mccs.1.1+10 on 4.03 had its build status changed: passing to failing
• mccs.1.1+10 on 4.04 had its build status changed: passing to failing
• mccs.1.1+10 on 4.05 had its build status changed: passing to failing
• mccs.1.1+10 on 4.06 had its build status changed: passing to failing
• mccs.1.1+10 on 4.07 had its build status changed: passing to failing
• mccs.1.1+10 on 4.08 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.02 had its build status changed: passing to failing
• mccs.1.1+11 on 4.03 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.05 had its build status changed: passing to failing
• mccs.1.1+11 on 4.06 had its build status changed: passing to failing
• mccs.1.1+11 on 4.07 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+11 on 4.09 had its build status changed: passing to failing
• mccs.1.1+11 on 4.10 had its build status changed: passing to failing
• mccs.1.1+11 on 4.11 had its build status changed: passing to failing
• mccs.1.1+11 on 4.12 had its build status changed: passing to failing
• mccs.1.1+11 on 4.13 had its build status changed: passing to failing
• mccs.1.1+11 on 4.14 is now installable. Current state is: failing
• mccs.1.1+3 on 4.02 had its build status changed: passing to failing
• mccs.1.1+3 on 4.03 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.05 had its build status changed: passing to failing
• mccs.1.1+3 on 4.06 had its build status changed: passing to failing
• mccs.1.1+3 on 4.07 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.02 had its build status changed: passing to failing
• mccs.1.1+4 on 4.03 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.05 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+4 on 4.07 had its build status changed: passing to failing
• mccs.1.1+4 on 4.08 had its build status changed: passing to failing
• mccs.1.1+4 on 4.09 had its build status changed: passing to failing
• mccs.1.1+5 on 4.02 had its build status changed: passing to failing
• mccs.1.1+5 on 4.03 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+5 on 4.06 had its build status changed: passing to failing
• mccs.1.1+5 on 4.07 had its build status changed: passing to failing
• mccs.1.1+5 on 4.08 had its build status changed: passing to failing
• mccs.1.1+5 on 4.09 had its build status changed: passing to failing
• mccs.1.1+6 on 4.02 had its build status changed: passing to failing
• mccs.1.1+6 on 4.03 had its build status changed: passing to failing
• mccs.1.1+6 on 4.04 had its build status changed: passing to failing
• mccs.1.1+6 on 4.05 had its build status changed: passing to failing
• mccs.1.1+6 on 4.06 had its build status changed: passing to failing
• mccs.1.1+6 on 4.07 had its build status changed: passing to failing
• mccs.1.1+6 on 4.08 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+8 on 4.02 had its build status changed: passing to failing
• mccs.1.1+8 on 4.03 had its build status changed: passing to failing
• mccs.1.1+8 on 4.04 had its build status changed: passing to failing
• mccs.1.1+8 on 4.05 had its build status changed: passing to failing
• mccs.1.1+8 on 4.06 had its build status changed: passing to failing
• mccs.1.1+8 on 4.07 had its build status changed: passing to failing
• mccs.1.1+8 on 4.08 had its build status changed: passing to failing
• mccs.1.1+8 on 4.09 had its build status changed: passing to failing
• mccs.1.1+9 on 4.02 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.04 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.06 had its build status changed: passing to failing
• mccs.1.1+9 on 4.07 had its build status changed: passing to failing
• mccs.1.1+9 on 4.08 had its build status changed: passing to failing
• mccs.1.1+9 on 4.09 had its build status changed: passing to failing
• mdx.1.7.0 on 4.02 had its build status changed: passing to failing
• mdx.1.7.0 on 4.03 had its build status changed: passing to failing
• mdx.1.7.0 on 4.04 had its build status changed: passing to failing
• mdx.1.7.0 on 4.05 had its build status changed: passing to failing
• mdx.1.7.0 on 4.06 had its build status changed: passing to failing
• mdx.1.7.0 on 4.07 had its build status changed: passing to failing
• mdx.1.7.0 on 4.08 had its build status changed: passing to failing
• mdx.1.7.0 on 4.09 had its build status changed: passing to failing
• mdx.1.7.0 on 4.10 had its build status changed: passing to failing
• mdx.1.7.0 on 4.11 had its build status changed: passing to failing
• memprof-limits.0.2.0 on 5.0 is now installable. Current state is: failing
• memtrace.0.1 on 5.0 is now installable. Current state is: failing
• memtrace_viewer.v0.14.0 on 4.11 had its build status changed: passing to failing
• memtrace_viewer.v0.14.1 on 4.11 had its build status changed: passing to failing
• menhir.20200123 on 5.0 is now installable. Current state is: failing
• menhir.20200211 on 5.0 is now installable. Current state is: failing
• menhir.20200525 on 5.0 is now installable. Current state is: failing
• menhir.20200612 on 5.0 is now installable. Current state is: failing
• menhir.20200619 on 5.0 is now installable. Current state is: failing
• menhir.20200624 on 5.0 is now installable. Current state is: failing
• menhir.20201122 on 5.0 is now installable. Current state is: failing
• menhir.20201201 on 5.0 is now installable. Current state is: failing
• menhir.20201214 on 5.0 is now installable. Current state is: failing
• menhir.20201216 on 5.0 is now installable. Current state is: failing
• menhir.20210310 on 5.0 is now installable. Current state is: failing
• menhir.20210419 on 5.0 is now installable. Current state is: failing
• menhir.20210929 on 5.0 is now installable. Current state is: failing
• menhir.20211012 on 5.0 is now installable. Current state is: failing
• menhir.20220210 on 5.0 is now installable. Current state is: failing
• message-switch.0.10.4 on 4.02 had its build status changed: passing to failing
• mezzo.0.0.m8 on 4.02 had its build status changed: passing to failing
• mezzo.0.0.m8 on 4.03 had its build status changed: passing to failing
• mezzo.0.0.m8 on 4.04 had its build status changed: passing to failing
• mezzo.0.0.m8 on 4.05 had its build status changed: passing to failing
• mirage-block-xen.1.7.0 on 4.08 had its build status changed: passing to failing
• mirage-block-xen.1.7.0 on 4.09 had its build status changed: passing to failing
• mirage-block-xen.1.7.0 on 4.10 had its build status changed: passing to failing
• mirage-block-xen.1.7.0 on 4.11 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.0 on 4.08 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.0 on 4.09 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.0 on 4.10 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.0 on 4.11 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.1 on 4.08 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.1 on 4.09 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.1 on 4.10 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.1 on 4.11 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.2 on 4.08 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.2 on 4.09 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.2 on 4.10 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.2 on 4.11 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.3 on 4.08 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.3 on 4.09 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.3 on 4.10 had its build status changed: passing to failing
• mirage-console-xen-backend.2.4.3 on 4.11 had its build status changed: passing to failing
• mirage-console-xen-backend.3.0.2 on 4.08 had its build status changed: passing to failing
• mirage-console-xen-backend.3.0.2 on 4.09 had its build status changed: passing to failing
• mirage-console-xen-backend.3.0.2 on 4.10 had its build status changed: passing to failing
• mirage-console-xen-backend.3.0.2 on 4.11 had its build status changed: passing to failing
• mirage-console-xen.2.4.2 on 4.08 had its build status changed: passing to failing
• mirage-console-xen.2.4.2 on 4.09 had its build status changed: passing to failing
• mirage-console-xen.2.4.2 on 4.10 had its build status changed: passing to failing
• mirage-console-xen.2.4.2 on 4.11 had its build status changed: passing to failing
• mirage-console-xen.2.4.3 on 4.08 had its build status changed: passing to failing
• mirage-console-xen.2.4.3 on 4.09 had its build status changed: passing to failing
• mirage-console-xen.2.4.3 on 4.10 had its build status changed: passing to failing
• mirage-console-xen.2.4.3 on 4.11 had its build status changed: passing to failing
• mirage-console-xen.3.0.2 on 4.08 had its build status changed: passing to failing
• mirage-console-xen.3.0.2 on 4.09 had its build status changed: passing to failing
• mirage-console-xen.3.0.2 on 4.10 had its build status changed: passing to failing
• mirage-console-xen.3.0.2 on 4.11 had its build status changed: passing to failing
• mkocaml.1.2 on 5.0 is now installable. Current state is: failing
• mldonkey.3.1.6 on 4.02 had its build status changed: passing to failing
• mldonkey.3.1.6 on 4.03 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.6 on 4.05 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.02 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.03 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.04 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.05 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.06 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.07 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.08 had its build status changed: passing to failing
• mldonkey.3.1.7-2 on 4.09 had its build status changed: passing to failing
• mmap.1.0.2 on 5.0 is now installable. Current state is: failing
• mmap.1.1.0 on 5.0 is now installable. Current state is: failing
• mmap.1.2.0 on 5.0 is now installable. Current state is: failing
• mock.0.1.1 on 5.0 is now installable. Current state is: failing
• monolith.20200609 on 5.0 is now installable. Current state is: failing
• monolith.20201026 on 5.0 is now installable. Current state is: failing
• monolith.20210525 on 5.0 is now installable. Current state is: failing
• monomorphic.2.0 on 5.0 is now installable. Current state is: failing
• mperf.0.1.0 on 5.0 is now installable. Current state is: failing
• mpp.0.3.4 on 5.0 is now installable. Current state is: failing
• mpp.0.3.5 on 5.0 is now installable. Current state is: failing
• multicont.1.0.0~rc.1 on 5.0 is now installable. Current state is: failing
• mysql8.1.0 on 4.13 had its build status changed: not available to failing
• mysql8.1.0 on 4.14 is now installable. Current state is: failing
• named-pipe.0.4.0 on 4.08 had its build status changed: passing to failing
• named-pipe.0.4.0 on 4.09 had its build status changed: passing to failing
• named-pipe.0.4.0 on 4.10 had its build status changed: passing to failing
• named-pipe.0.4.0 on 4.11 had its build status changed: passing to failing
• netchannel.1.10.2 on 4.08 had its build status changed: passing to failing
• netchannel.1.10.2 on 4.09 had its build status changed: passing to failing
• netchannel.1.10.2 on 4.10 had its build status changed: passing to failing
• netchannel.1.10.2 on 4.11 had its build status changed: passing to failing
• netchannel.1.11.0 on 4.08 had its build status changed: passing to failing
• netchannel.1.11.0 on 4.09 had its build status changed: passing to failing
• netchannel.1.11.0 on 4.10 had its build status changed: passing to failing
• netchannel.1.11.0 on 4.11 had its build status changed: passing to failing
• netchannel.1.12.0 on 4.08 had its build status changed: passing to failing
• netchannel.1.12.0 on 4.09 had its build status changed: passing to failing
• netchannel.1.12.0 on 4.10 had its build status changed: passing to failing
• netchannel.1.12.0 on 4.11 had its build status changed: passing to failing
• netchannel.1.13.0 on 4.08 had its build status changed: passing to failing
• netchannel.1.13.0 on 4.09 had its build status changed: passing to failing
• netchannel.1.13.0 on 4.10 had its build status changed: passing to failing
• netchannel.1.13.0 on 4.11 had its build status changed: passing to failing
• netchannel.1.13.1 on 4.08 had its build status changed: passing to failing
• netchannel.1.13.1 on 4.09 had its build status changed: passing to failing
• netchannel.1.13.1 on 4.10 had its build status changed: passing to failing
• netchannel.1.13.1 on 4.11 had its build status changed: passing to failing
• netkat.0.1 on 4.08 had its build status changed: passing 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
• obuild.0.1.10 on 5.0 is now installable. Current state is: failing
• obuild.0.1.9 on 5.0 is now installable. Current state is: failing
• ocaml-freestanding.0.1.1 on 4.02 had its build status changed: passing to failing
• ocaml-freestanding.0.1.1 on 4.03 had its build status changed: passing to failing
• ocaml-lua.1.1 on 4.02 had its build status changed: passing to failing
• ocaml-lua.1.2 on 4.02 had its build status changed: passing to failing
• ocaml-lua.1.3 on 4.02 had its build status changed: passing to failing
• ocaml-lua.1.4 on 4.02 had its build status changed: passing to failing
• ocaml-lua.1.5 on 4.02 had its build status changed: passing to failing
• ocaml-lua.1.6 on 4.02 had its build status changed: passing to failing
• ocaml-lua.1.6 on 4.03 had its build status changed: passing to failing
• ocaml-lua.1.6 on 4.04 had its build status changed: passing to failing
• ocaml-lua.1.6 on 4.05 had its build status changed: passing to failing
• ocaml-lua.1.7 on 4.02 had its build status changed: passing to failing
• ocaml-lua.1.7 on 4.03 had its build status changed: passing to failing
• ocaml-lua.1.7 on 4.04 had its build status changed: passing to failing
• ocaml-lua.1.7 on 4.05 had its build status changed: passing to failing
• ocaml-lua.1.7 on 4.06 had its build status changed: passing to failing
• ocaml-lua.1.7 on 4.07 had its build status changed: passing to failing
• ocaml-lua.1.8 on 5.0 is now installable. Current state is: failing
• ocaml-makefile.6.37.0 on 4.02 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.03 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.04 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.05 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.06 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.07 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.08 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.09 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.10 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.11 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.12 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.13 had its build status changed: passing to failing
• ocaml-makefile.6.37.0 on 4.14 is now installable. Current state is: failing
• ocaml-makefile.6.37.0 on 5.0 is now installable. Current state is: failing
• ocaml-makefile.6.38.0 on 4.02 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.03 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.04 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.05 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.06 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.07 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.08 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.09 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.10 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.11 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.12 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.13 had its build status changed: passing to failing
• ocaml-makefile.6.38.0 on 4.14 is now installable. Current state is: failing
• ocaml-makefile.6.38.0 on 5.0 is now installable. Current state is: failing
• ocaml-makefile.6.39.0 on 4.02 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.03 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.04 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.05 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.06 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.07 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.08 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.09 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.10 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.11 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.12 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.13 had its build status changed: passing to failing
• ocaml-makefile.6.39.0 on 4.14 is now installable. Current state is: failing
• ocaml-makefile.6.39.0 on 5.0 is now installable. Current state is: failing
• ocaml-protoc-plugin.1.0.0 on 5.0 is now installable. Current state is: failing
• ocaml-protoc.2.0.1 on 5.0 is now installable. Current state is: failing
• ocaml-protoc.2.0.2 on 5.0 is now installable. Current state is: failing
• ocaml-protoc.2.1 on 5.0 is now installable. Current state is: failing
• ocaml-protoc.2.2 on 5.0 is now installable. Current state is: failing
• ocaml-r.0.1.0 on 4.03 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.04 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.05 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.06 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.07 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.03 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.04 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.05 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.06 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.07 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.03 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.04 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.05 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.06 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.07 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.03 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.04 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.05 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.06 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.07 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.07 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.12 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.13 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.14 is now installable. Current state is: failing
• ocaml-r.0.4.0 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.4.0 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.4.0 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.4.0 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.4.0 on 4.12 had its build status changed: passing to failing
• ocaml-r.0.4.0 on 4.13 had its build status changed: passing to failing
• ocaml-r.0.4.0 on 4.14 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 4.08 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 4.09 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 4.10 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 4.11 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 4.12 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 4.13 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 4.14 is now installable. Current state is: failing
• ocaml-twt.0.93 on 5.0 is now installable. Current state is: failing
• ocaml-twt.0.93.2 on 5.0 is now installable. Current state is: failing
• ocaml-twt.0.94.0 on 5.0 is now installable. Current state is: failing
• ocamlbuild.0.14.0 on 5.0 is now installable. Current state is: 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 is now installable. Current state is: failing
• ocamlfind.1.9.1 on 5.0 is now installable. Current state is: failing
• ocamlfind.1.9.2 on 5.0 is now installable. Current state is: failing
• ocamlfind.1.9.3 on 5.0 is now installable. Current state is: failing
• ocamlformat-rpc.0.18.0 on 4.08 had its build status changed: passing to failing
• ocamlformat-rpc.0.18.0 on 4.09 had its build status changed: passing to failing
• ocamlformat-rpc.0.18.0 on 4.10 had its build status changed: passing to failing
• ocamlformat-rpc.0.18.0 on 4.11 had its build status changed: passing to failing
• ocamlformat-rpc.0.18.0 on 4.12 had its build status changed: passing to failing
• ocamlog.0.1 on 5.0 is now installable. Current state is: failing
• ocamlog.0.2 on 5.0 is now installable. Current state is: failing
• ocamlviz.1.01 on 4.02 had its build status changed: internal failure to failing
• ocamlviz.1.01 on 4.03 had its build status changed: internal failure to failing
• ocamlviz.1.01 on 4.04 had its build status changed: internal failure to failing
• ocamlviz.1.01 on 4.05 had its build status changed: internal failure to failing
• ocf.0.2.0 on 4.02 had its build status changed: internal failure to failing
• ocf.0.4.0 on 4.02 had its build status changed: internal failure to failing
• ocp-indent.0.6.1 on 4.02 had its build status changed: passing to failing
• ocp-indent.0.6.1 on 4.03 had its build status changed: passing to failing
• ocp-indent.0.6.1 on 4.04 had its build status changed: passing to failing
• ocp-indent.0.6.1 on 4.05 had its build status changed: passing to failing
• ocp-pack-split.1.0.1 on 5.0 is now installable. Current state is: failing
• ocplib_stuff.0.2.0 on 5.0 is now installable. Current state is: failing
• ocplib_stuff.0.3.0 on 5.0 is now installable. Current state is: failing
• ocsigen-i18n.4.0.0 on 5.0 is now installable. Current state is: failing
• odepack.0.6.9 on 4.14 is now installable. Current state is: failing
• odepack.0.7 on 4.14 is now installable. Current state is: failing
• odig.0.0.3 on 4.08 had its build status changed: passing to failing
• odig.0.0.3 on 4.09 had its build status changed: passing to failing
• odig.0.0.3 on 4.10 had its build status changed: passing to failing
• odig.0.0.3 on 4.11 had its build status changed: passing to failing
• offheap.0.1.0 on 5.0 is now installable. Current state is: failing
• offheap.0.1.1 on 5.0 is now installable. Current state is: failing
• offheap.0.1.2 on 5.0 is now installable. Current state is: 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
• opam-depext.1.2.0 on 5.0 is now installable. Current state is: failing
• opam-file-format.2.1.2 on 5.0 is now installable. Current state is: failing
• opam-file-format.2.1.3 on 5.0 is now installable. Current state is: failing
• opam-file-format.2.1.4 on 5.0 is now installable. Current state is: failing
• opam-monorepo.0.2.3 on 5.0 is now installable. Current state is: failing
• opam-monorepo.0.2.4 on 5.0 is now installable. Current state is: failing
• opam-monorepo.0.2.5 on 5.0 is now installable. Current state is: failing
• opam-monorepo.0.2.6 on 5.0 is now installable. Current state is: failing
• opam-monorepo.0.2.7 on 5.0 is now installable. Current state is: failing
• opam-monorepo.0.3.0 on 5.0 is now installable. Current state is: failing
• opam-monorepo.0.3.1 on 5.0 is now installable. Current state is: failing
• opam-sync-github-prs.1.1.0 on 4.02 had its build status changed: partially failing to failing
• opam-sync-github-prs.1.1.0 on 4.03 had its build status changed: partially failing to failing
• opam2web.1.5.0 on 4.06 had its build status changed: passing to failing
• operf-micro.1.1.1 on 5.0 is now installable. Current state is: failing
• oplsr.5.0.1 on 4.02 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.03 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.04 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.05 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.06 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.07 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.08 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.09 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.10 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.11 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.12 had its build status changed: passing to failing
• oplsr.5.0.1 on 4.13 had its build status changed: not available to failing
• oplsr.5.0.1 on 4.14 is now installable. Current state is: failing
• oplsr.8.0.1 on 4.13 had its build status changed: not available to failing
• oplsr.8.0.1 on 4.14 is now installable. Current state is: failing
• optint.0.0.2 on 5.0 is now installable. Current state is: failing
• orun.0.0.1 on 4.07 had its build status changed: passing to failing
• orun.0.0.1 on 4.08 had its build status changed: passing to failing
• orun.0.0.1 on 4.09 had its build status changed: passing to failing
• orun.0.0.1 on 4.10 had its build status changed: passing to failing
• orun.0.0.1 on 4.11 had its build status changed: passing to failing
• orun.0.0.1 on 4.12 had its build status changed: passing to failing
• orun.0.0.1 on 4.13 had its build status changed: passing to failing
• orun.0.0.1 on 4.14 is now installable. Current state is: failing
• otf.0.1 on 5.0 is now installable. Current state is: failing
• ott.0.26 on 5.0 is now installable. Current state is: failing
• ott.0.27 on 5.0 is now installable. Current state is: failing
• ott.0.28 on 5.0 is now installable. Current state is: failing
• ott.0.29 on 5.0 is now installable. Current state is: failing
• ott.0.30 on 5.0 is now installable. Current state is: failing
• ott.0.31 on 5.0 is now installable. Current state is: failing
• ott.0.32 on 5.0 is now installable. Current state is: failing
• override.0.4.0 on 4.14 is now installable. Current state is: failing
• owee.0.4 on 5.0 is now installable. Current state is: failing
• owee.0.5 on 5.0 is now installable. Current state is: failing
• owee.0.6 on 5.0 is now installable. Current state is: failing
• owl-base.0.10.0 on 5.0 is now installable. Current state is: failing
• owl-base.0.4.0 on 5.0 is now installable. Current state is: failing
• owl-base.0.7.0 on 5.0 is now installable. Current state is: failing
• owl-base.0.7.1 on 5.0 is now installable. Current state is: failing
• owl-base.0.7.2 on 5.0 is now installable. Current state is: failing
• owl-base.0.8.0 on 5.0 is now installable. Current state is: failing
• owl-base.0.9.0 on 5.0 is now installable. Current state is: failing
• owl-base.1.0.0 on 5.0 is now installable. Current state is: failing
• owl-base.1.0.1 on 5.0 is now installable. Current state is: failing
• owl-base.1.0.2 on 5.0 is now installable. Current state is: failing
• owl-zoo.1.0.2 on 4.10 is now installable. Current state is: failing
• owl-zoo.1.0.2 on 4.11 is now installable. Current state is: failing
• owl-zoo.1.0.2 on 4.12 is now installable. Current state is: failing
• owl-zoo.1.0.2 on 4.13 is now installable. Current state is: failing
• pa_ppx_ag.0.07.02 on 4.10 had its build status changed: passing to failing
• pa_ppx_ag.0.07.02 on 4.11 had its build status changed: not available to failing
• pa_ppx_ag.0.07.02 on 4.12 had its build status changed: passing to failing
• papi.0.1.0 on 4.14 is now installable. Current state is: failing
• papi.0.1.1 on 4.14 is now installable. Current state is: failing
• papi.0.1.1 on 5.0 is now installable. Current state is: failing
• parany.10.0.2 on 5.0 is now installable. Current state is: failing
• parany.11.0.2 on 5.0 is now installable. Current state is: failing
• parany.12.0.2 on 5.0 is now installable. Current state is: failing
• parany.12.0.3 on 5.0 is now installable. Current state is: failing
• parany.12.1.1 on 5.0 is now installable. Current state is: failing
• parany.12.1.2 on 5.0 is now installable. Current state is: failing
• parany.12.2.0 on 5.0 is now installable. Current state is: failing
• patoline.0.1 on 4.03 had its build status changed: internal failure to failing
• patoline.0.1 on 4.04 had its build status changed: internal failure to failing
• patoline.0.1 on 4.05 had its build status changed: internal failure 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.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
• polly.0.2.2 on 5.0 is now installable. Current state is: failing
• ppx_monad.0.1.0 on 5.0 is now installable. Current state is: failing
• ppx_overload.1.0.0 on 4.02 had its build status changed: internal failure to failing
• ppx_overload.1.4 on 4.06 had its build status changed: internal failure to failing
• ppx_test.0.0.1 on 4.02 had its build status changed: internal failure to failing
• ppx_test.1.0.1 on 4.02 had its build status changed: internal failure to failing
• ppx_test.1.1.0 on 4.02 had its build status changed: internal failure to failing
• ppx_test.1.2.0 on 4.02 had its build status changed: internal failure to failing
• ppx_test.1.2.1 on 4.02 had its build status changed: internal failure to failing
• pratter.0.1.1 on 5.0 is now installable. Current state is: failing
• pratter.1.0 on 5.0 is now installable. Current state is: failing
• pratter.1.1 on 5.0 is now installable. Current state is: failing
• pratter.1.2 on 5.0 is now installable. Current state is: failing
• prbnmcn-gnuplot.0.0.1 on 5.0 is now installable. Current state is: failing
• prbnmcn-gnuplot.0.0.2 on 5.0 is now installable. Current state is: failing
• prbnmcn-gnuplot.0.0.3 on 5.0 is now installable. Current state is: failing
• profound.0.4.2 on 4.02 had its build status changed: passing to failing
• profound.0.4.2 on 4.03 had its build status changed: passing to failing
• profound.0.4.2 on 4.04 had its build status changed: passing to failing
• profound.0.4.2 on 4.05 had its build status changed: passing to failing
• profound.0.4.2 on 4.06 had its build status changed: passing to failing
• profound.0.4.2 on 4.07 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 is now installable. Current state is: 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
• reparse-unix.2.0.0 on 5.0 is now installable. Current state is: failing
• rfsm.1.0 on 4.03 had its build status changed: passing to failing
• rfsm.1.0 on 4.04 had its build status changed: passing to failing
• rfsm.1.0 on 4.05 had its build status changed: passing to failing
• rfsm.1.0 on 4.06 had its build status changed: passing to failing
• rfsm.1.0 on 4.07 had its build status changed: passing to failing
• rfsm.1.0 on 4.08 had its build status changed: passing to failing
• rfsm.1.0 on 4.09 had its build status changed: passing to failing
• rfsm.1.0 on 4.10 had its build status changed: passing to failing
• rfsm.1.0 on 4.11 had its build status changed: passing to failing
• rfsm.1.0 on 4.12 had its build status changed: passing to failing
• rfsm.1.0 on 4.13 had its build status changed: not available to failing
• rfsm.1.0 on 4.14 is now installable. Current state is: failing
• rfsm.1.4.2 on 4.03 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.04 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.05 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.06 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.07 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.08 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.09 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.10 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.11 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.12 had its build status changed: passing to failing
• rfsm.1.4.2 on 4.13 had its build status changed: not available to failing
• rfsm.1.4.2 on 4.14 is now installable. Current state is: failing
• rfsm.1.5 on 4.03 had its build status changed: passing to failing
• rfsm.1.5 on 4.04 had its build status changed: passing to failing
• rfsm.1.5 on 4.05 had its build status changed: passing to failing
• rfsm.1.5 on 4.06 had its build status changed: passing to failing
• rfsm.1.5 on 4.07 had its build status changed: passing to failing
• rfsm.1.5 on 4.08 had its build status changed: passing to failing
• rfsm.1.5 on 4.09 had its build status changed: passing to failing
• rfsm.1.5 on 4.10 had its build status changed: passing to failing
• rfsm.1.5 on 4.11 had its build status changed: passing to failing
• rfsm.1.5 on 4.12 had its build status changed: passing to failing
• rfsm.1.5 on 4.13 had its build status changed: not available to failing
• rfsm.1.5 on 4.14 is now installable. Current state is: failing
• ringo.0.1 on 5.0 is now installable. Current state is: failing
• ringo.0.4 on 5.0 is now installable. Current state is: failing
• ringo.0.5 on 5.0 is now installable. Current state is: failing
• ringo.0.6 on 5.0 is now installable. Current state is: failing
• ringo.0.7 on 5.0 is now installable. Current state is: failing
• ringo.0.8 on 5.0 is now installable. Current state is: failing
• ringo.0.9 on 5.0 is now installable. Current state is: failing
• rmlbuild.0.14.0-00 on 5.0 is now installable. Current state is: failing
• rosetta.0.1.0 on 4.08 had its build status changed: passing to failing
• rosetta.0.1.0 on 4.09 had its build status changed: passing to failing
• rosetta.0.1.0 on 4.10 had its build status changed: passing to failing
• rosetta.0.1.0 on 4.11 had its build status changed: passing to failing
• rtop.3.6.2 on 4.03 had its build status changed: passing to failing
• rtop.3.6.2 on 4.04 had its build status changed: passing to failing
• rtop.3.6.2 on 4.05 had its build status changed: passing to failing
• rtop.3.6.2 on 4.06 had its build status changed: passing to failing
• rtop.3.6.2 on 4.07 had its build status changed: passing to failing
• rtop.3.6.2 on 4.08 had its build status changed: passing to failing
• rtop.3.6.2 on 4.09 had its build status changed: passing to failing
• rtop.3.6.2 on 4.10 had its build status changed: passing to failing
• rtop.3.6.2 on 4.11 had its build status changed: passing to failing
• rtop.3.7.0 on 4.03 had its build status changed: passing to failing
• rtop.3.7.0 on 4.04 had its build status changed: passing to failing
• rtop.3.7.0 on 4.05 had its build status changed: passing to failing
• rtop.3.7.0 on 4.06 had its build status changed: passing to failing
• rtop.3.7.0 on 4.07 had its build status changed: passing to failing
• rtop.3.7.0 on 4.08 had its build status changed: passing to failing
• rtop.3.7.0 on 4.09 had its build status changed: passing to failing
• rtop.3.7.0 on 4.10 had its build status changed: passing to failing
• rtop.3.7.0 on 4.11 had its build status changed: passing to failing
• rtop.3.7.0 on 4.12 had its build status changed: passing to failing
• semaphore-compat.1.0.0 on 5.0 is now installable. Current state is: failing
• semaphore-compat.1.0.1 on 5.0 is now installable. Current state is: failing
• sequoia.0.1.0 on 4.04 had its build status changed: passing to failing
• sequoia.0.1.0 on 4.05 had its build status changed: passing to failing
• sequoia.0.1.0 on 4.06 had its build status changed: passing to failing
• sequoia.0.1.0 on 4.07 had its build status changed: passing to failing
• sexplib0.v0.12.0 on 5.0 is now installable. Current state is: failing
• sexplib0.v0.13.0 on 5.0 is now installable. Current state is: failing
• sexplib0.v0.14.0 on 5.0 is now installable. Current state is: failing
• sexplib0.v0.15.0 on 5.0 is now installable. Current state is: failing
• sha.1.13 on 5.0 is now installable. Current state is: failing
• sha.1.14 on 5.0 is now installable. Current state is: failing
• sha.1.15.1 on 5.0 is now installable. Current state is: failing
• sibylfs.0.5.0 on 4.02 had its build status changed: internal failure to failing
• sill.1.3 on 4.02 had its build status changed: internal failure to failing
• sill.1.3.1 on 4.02 had its build status changed: internal failure to failing
• sill.1.4 on 4.02 had its build status changed: internal failure to failing
• snappy.0.1.2 on 5.0 is now installable. Current state is: failing
• spacetime_lib.0.1.0 on 4.06 had its build status changed: passing to failing
• spacetime_lib.0.1.0 on 4.07 had its build status changed: passing to failing
• spacetime_lib.0.3.0 on 4.06 had its build status changed: passing to failing
• spacetime_lib.0.3.0 on 4.07 had its build status changed: passing to failing
• spacetime_lib.0.3.0 on 4.08 had its build status changed: passing to failing
• spacetime_lib.0.3.0 on 4.09 had its build status changed: passing to failing
• spacetime_lib.0.3.0 on 4.10 had its build status changed: passing to failing
• spacetime_lib.0.3.0 on 4.11 had its build status changed: passing to failing
• spawn.0.14.0 on 5.0 is now installable. Current state is: failing
• spawn.v0.13.0 on 5.0 is now installable. Current state is: failing
• spawn.v0.14.0 on 5.0 is now installable. Current state is: failing
• spawn.v0.15.0 on 5.0 is now installable. Current state is: failing
• spawn.v0.15.1 on 5.0 is now installable. Current state is: 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
• stdcompat.15 on 5.0 is now installable. Current state is: failing
• stdcompat.16 on 5.0 is now installable. Current state is: failing
• stdcompat.17 on 5.0 is now installable. Current state is: failing
• stdcompat.18 on 5.0 is now installable. Current state is: failing
• stdune.3.0.2 on 5.0 is now installable. Current state is: failing
• stdune.3.0.3 on 5.0 is now installable. Current state is: failing
• stdune.3.1.0 on 5.0 is now installable. Current state is: failing
• stdune.3.1.1 on 5.0 is now installable. Current state is: failing
• stdune.3.2.0 on 5.0 is now installable. Current state is: failing
• stog-writing.0.19.0 on 4.12 is now installable. Current state is: failing
• stog.0.16.0 on 4.04 had its build status changed: internal failure to failing
• stog.0.16.0 on 4.05 had its build status changed: internal failure to failing
• stog.0.16.0 on 4.06 had its build status changed: internal failure to failing
• stog.0.16.0 on 4.07 had its build status changed: internal failure to failing
• stog.0.19.0 on 4.12 is now installable. Current state is: failing
• stog_server.0.20.0 on 4.12 is now installable. Current state is: failing
• syndic.1.5 on 4.03 had its build status changed: passing to failing
• syndic.1.5 on 4.04 had its build status changed: passing to failing
• syndic.1.5 on 4.05 had its build status changed: passing to failing
• syndic.1.5 on 4.06 had its build status changed: passing to failing
• syndic.1.5 on 4.07 had its build status changed: passing to failing
• syndic.1.5.1 on 4.03 had its build status changed: passing to failing
• syndic.1.5.1 on 4.04 had its build status changed: passing to failing
• syndic.1.5.1 on 4.05 had its build status changed: passing to failing
• syndic.1.5.1 on 4.06 had its build status changed: passing to failing
• syndic.1.5.1 on 4.07 had its build status changed: passing to failing
• syndic.1.5.2 on 4.03 had its build status changed: passing to failing
• syndic.1.5.2 on 4.04 had its build status changed: passing to failing
• syndic.1.5.2 on 4.05 had its build status changed: passing to failing
• syndic.1.5.2 on 4.06 had its build status changed: passing to failing
• syndic.1.5.2 on 4.07 had its build status changed: passing to failing
• syndic.1.5.3 on 4.03 had its build status changed: passing to failing
• syndic.1.5.3 on 4.04 had its build status changed: passing to failing
• syndic.1.5.3 on 4.05 had its build status changed: passing to failing
• syndic.1.5.3 on 4.06 had its build status changed: passing to failing
• syndic.1.5.3 on 4.07 had its build status changed: passing to failing
• syndic.1.6.0 on 4.04 had its build status changed: passing to failing
• syndic.1.6.0 on 4.05 had its build status changed: passing to failing
• syndic.1.6.0 on 4.06 had its build status changed: passing to failing
• syndic.1.6.0 on 4.07 had its build status changed: passing to failing
• syndic.1.6.1 on 4.03 had its build status changed: passing to failing
• syndic.1.6.1 on 4.04 had its build status changed: passing to failing
• syndic.1.6.1 on 4.05 had its build status changed: passing to failing
• syndic.1.6.1 on 4.06 had its build status changed: passing to failing
• syndic.1.6.1 on 4.07 had its build status changed: passing to failing
• syslog.2.0.0 on 5.0 is now installable. Current state is: failing
• syslog.2.0.1 on 5.0 is now installable. Current state is: failing
• syslog.2.0.2 on 5.0 is now installable. Current state is: failing
• taglib.0.2.0 on 4.02 had its build status changed: passing to failing
• taglib.0.2.0 on 4.03 had its build status changed: passing to failing
• taglib.0.2.0 on 4.04 had its build status changed: passing to failing
• taglib.0.2.0 on 4.05 had its build status changed: passing to failing
• taglib.0.2.0 on 4.06 had its build status changed: passing to failing
• taglib.0.2.0 on 4.07 had its build status changed: passing to failing
• taglib.0.2.0 on 4.08 had its build status changed: passing to failing
• taglib.0.2.0 on 4.09 had its build status changed: passing to failing
• taglib.0.3.0 on 4.02 had its build status changed: passing to failing
• taglib.0.3.0 on 4.03 had its build status changed: passing to failing
• taglib.0.3.0 on 4.04 had its build status changed: passing to failing
• taglib.0.3.0 on 4.05 had its build status changed: passing to failing
• taglib.0.3.0 on 4.06 had its build status changed: passing to failing
• taglib.0.3.0 on 4.07 had its build status changed: passing to failing
• taglib.0.3.0 on 4.08 had its build status changed: passing to failing
• taglib.0.3.0 on 4.09 had its build status changed: passing to failing
• taglib.0.3.2 on 4.02 had its build status changed: passing to failing
• taglib.0.3.2 on 4.03 had its build status changed: passing to failing
• taglib.0.3.2 on 4.04 had its build status changed: passing to failing
• taglib.0.3.2 on 4.05 had its build status changed: passing to failing
• taglib.0.3.2 on 4.06 had its build status changed: passing to failing
• taglib.0.3.2 on 4.07 had its build status changed: passing to failing
• taglib.0.3.2 on 4.08 had its build status changed: passing to failing
• taglib.0.3.2 on 4.09 had its build status changed: passing to failing
• taglib.0.3.3 on 4.02 had its build status changed: passing to failing
• taglib.0.3.3 on 4.03 had its build status changed: passing to failing
• taglib.0.3.3 on 4.04 had its build status changed: passing to failing
• taglib.0.3.3 on 4.05 had its build status changed: passing to failing
• taglib.0.3.3 on 4.06 had its build status changed: passing to failing
• taglib.0.3.3 on 4.07 had its build status changed: passing to failing
• taglib.0.3.3 on 4.08 had its build status changed: passing to failing
• taglib.0.3.3 on 4.09 had its build status changed: passing to failing
• taglib.0.3.6 on 4.02 had its build status changed: passing to failing
• taglib.0.3.6 on 4.03 had its build status changed: passing to failing
• taglib.0.3.6 on 4.04 had its build status changed: passing to failing
• taglib.0.3.6 on 4.05 had its build status changed: passing to failing
• taglib.0.3.6 on 4.06 had its build status changed: passing to failing
• taglib.0.3.6 on 4.07 had its build status changed: passing to failing
• taglib.0.3.6 on 4.08 had its build status changed: passing to failing
• taglib.0.3.6 on 4.09 had its build status changed: passing to failing
• taglib.0.3.6 on 4.10 had its build status changed: passing to failing
• taglib.0.3.6 on 4.11 had its build status changed: passing to failing
• taglib.0.3.6 on 4.12 had its build status changed: passing to failing
• taglib.0.3.6 on 4.13 had its build status changed: passing to failing
• taglib.0.3.6 on 4.14 is now installable. Current state is: failing
• tar-format.0.2.0 on 4.02 had its build status changed: passing to failing
• tar-format.0.2.0 on 4.03 had its build status changed: passing to failing
• tar-format.0.2.0 on 4.04 had its build status changed: passing to failing
• tar-format.0.2.0 on 4.05 had its build status changed: passing to failing
• tar-format.0.2.1 on 4.02 had its build status changed: passing to failing
• tar-format.0.2.1 on 4.03 had its build status changed: passing to failing
• tar-format.0.2.1 on 4.04 had its build status changed: passing to failing
• tar-format.0.2.1 on 4.05 had its build status changed: passing to failing
• tcpip.4.0.0 on 4.08 had its build status changed: passing to failing
• tcpip.4.0.0 on 4.09 had its build status changed: passing to failing
• tcpip.4.0.0 on 4.10 had its build status changed: passing to failing
• tcpip.4.0.0 on 4.11 had its build status changed: passing to failing
• thrift.0.10.0 on 5.0 is now installable. Current state is: failing
• tidy.1-4.9.30-0.1.1 on 4.02 had its build status changed: internal failure to failing
• tidy.1-4.9.30-0.1.1 on 4.03 had its build status changed: internal failure to failing
• tidy.1-4.9.30-0.1.1 on 4.04 had its build status changed: internal failure to failing
• tidy.1-4.9.30-0.1.1 on 4.05 had its build status changed: internal failure to failing
• tidy.1-4.9.30-0.1.1 on 4.06 had its build status changed: internal failure to failing
• tidy.1-4.9.30-0.1.1 on 4.07 had its build status changed: internal failure to failing
• tidy.1-4.9.30-0.1.1 on 4.08 had its build status changed: internal failure to failing
• tidy.1-4.9.30-0.1.1 on 4.09 had its build status changed: internal failure to failing
• tiny_httpd.0.1 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.10 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.11 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.12 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.2 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.3 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.4 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.5 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.6 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.7 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.8 on 5.0 is now installable. Current state is: failing
• tiny_httpd.0.9 on 5.0 is now installable. Current state is: failing
• travis-opam.1.0.0 on 5.0 is now installable. Current state is: failing
• travis-opam.1.0.2 on 5.0 is now installable. Current state is: failing
• travis-opam.1.0.3 on 5.0 is now installable. Current state is: failing
• travis-opam.1.1.0 on 5.0 is now installable. Current state is: failing
• typpx.1.2.1 on 4.04 had its build status changed: internal failure to failing
• typpx.1.3.0 on 4.05 had its build status changed: internal failure to failing
• ubpf.0.1 on 4.08 had its build status changed: passing to failing
• ubpf.0.1 on 4.09 had its build status changed: passing to failing
• ubpf.0.1 on 4.10 had its build status changed: passing to failing
• ubpf.0.1 on 4.11 had its build status changed: passing to failing
• ubpf.0.1 on 4.12 had its build status changed: passing to failing
• ubpf.0.1 on 4.13 had its build status changed: passing to failing
• ubpf.0.1 on 4.14 is now installable. Current state is: failing
• ubpf.0.2 on 5.0 is now installable. Current state is: failing
• ucaml.0.1 on 5.0 is now installable. Current state is: failing
• unisim_archisec.0.0.0 on 5.0 is now installable. Current state is: failing
• unisim_archisec.0.0.1 on 5.0 is now installable. Current state is: failing
• unisim_archisec.0.0.2 on 5.0 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
• usbmux.0.3 on 4.02 had its build status changed: passing to failing
• usbmux.0.3 on 4.03 had its build status changed: passing to failing
• usbmux.0.5 on 4.02 had its build status changed: passing to failing
• usbmux.0.5 on 4.03 had its build status changed: passing to failing
• usbmux.0.6 on 4.02 had its build status changed: passing to failing
• usbmux.0.6 on 4.03 had its build status changed: passing to failing
• usbmux.0.7 on 4.02 had its build status changed: passing to failing
• usbmux.0.7 on 4.03 had its build status changed: passing to failing
• usbmux.0.8 on 4.02 had its build status changed: passing to failing
• usbmux.0.8 on 4.03 had its build status changed: passing to failing
• usbmux.0.9 on 4.02 had its build status changed: passing to failing
• usbmux.0.9 on 4.03 had its build status changed: passing to failing
• usbmux.1.0 on 4.02 had its build status changed: passing to failing
• usbmux.1.0 on 4.03 had its build status changed: passing to failing
• usbmux.1.1.0 on 4.02 had its build status changed: passing to failing
• usbmux.1.1.0 on 4.03 had its build status changed: passing to failing
• usbmux.1.1.1 on 4.02 had its build status changed: passing to failing
• usbmux.1.1.1 on 4.03 had its build status changed: passing to failing
• usbmux.1.2.0 on 4.02 had its build status changed: passing to failing
• usbmux.1.3.1 on 4.02 had its build status changed: passing to failing
• usbmux.1.3.2 on 4.03 had its build status changed: passing to failing
• usbmux.1.3.2 on 4.04 had its build status changed: passing to failing
• usbmux.1.3.2 on 4.05 had its build status changed: passing to failing
• uuuu.0.1.0 on 4.08 had its build status changed: passing to failing
• uuuu.0.1.1 on 4.08 had its build status changed: passing to failing
• validator.0.2.3 on 5.0 is now installable. Current state is: failing
• vhd-format.0.12.0 on 4.08 had its build status changed: passing to failing
• vhd-format.0.12.0 on 4.09 had its build status changed: passing to failing
• vhd-format.0.12.0 on 4.10 had its build status changed: passing to failing
• vhd-format.0.12.0 on 4.11 had its build status changed: passing to failing
• vhd-format.0.12.0 on 4.12 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.08 is now installable. Current state is: failing
• vhd-format.0.12.1 on 4.09 is now installable. Current state is: failing
• vhd-format.0.12.1 on 4.10 is now installable. Current state is: failing
• vhd-format.0.12.1 on 4.11 is now installable. Current state is: failing
• vhd-format.0.12.1 on 4.12 is now installable. Current state is: failing
• vlq.0.2.1 on 5.0 is now installable. Current state is: failing
• wcs-lib.2017-05-26.05 on 4.08 had its build status changed: passing to failing
• wcs-lib.2017-05-26.05 on 4.09 had its build status changed: passing to failing
• wcs-lib.2017-05-26.05 on 4.10 had its build status changed: passing to failing
• wcs-lib.2017-05-26.05 on 4.11 had its build status changed: passing to failing
• wcs-lib.2017-05-26.05 on 4.12 had its build status changed: passing to failing
• websocket.2.3 on 4.03 had its build status changed: passing to failing
• websocket.2.3 on 4.04 had its build status changed: passing to failing
• websocket.2.3 on 4.05 had its build status changed: passing to failing
• websocket.2.3 on 4.06 had its build status changed: passing to failing
• xen-gnt.2.2.1 on 4.03 had its build status changed: internal failure to failing
• xen-gnt.2.2.1 on 4.04 had its build status changed: internal failure to failing
• xoshiro.0.1 on 5.0 is now installable. Current state is: failing
• xtmpl.0.13.0 on 4.02 had its build status changed: internal failure to failing
• xtmpl.0.14.0 on 4.03 had its build status changed: internal failure to failing
• xtmpl.0.14.0 on 4.04 had its build status changed: internal failure to failing
• yaml.0.2.1 on 4.08 had its build status changed: passing to failing
• yaml.0.2.1 on 4.09 had its build status changed: passing to failing
• yaml.0.2.1 on 4.10 had its build status changed: passing to failing
• yaml.0.2.1 on 4.11 had its build status changed: passing to failing
• yuscii.0.2.0 on 4.08 had its build status changed: passing to failing
• yuscii.0.2.0 on 4.09 had its build status changed: passing to failing
• yuscii.0.2.0 on 4.10 had its build status changed: passing to failing
• yuscii.0.2.0 on 4.11 had its build status changed: passing to failing
• zbar.0.9 on 4.04 had its build status changed: internal failure to failing
• zbar.0.9 on 4.05 had its build status changed: passing to failing
• zenon.0.7.1 on 4.02 had its build status changed: passing to failing
• zenon.0.7.1 on 4.03 had its build status changed: passing to failing
• zenon.0.7.1 on 4.04 had its build status changed: passing to failing
• zenon.0.7.1 on 4.05 had its build status changed: passing to failing
• zenon.0.8.4 on 5.0 is now installable. Current state is: failing
• zlib.0.6 on 5.0 is now installable. Current state is: failing